CLIAMS:CLAIMS
What is claimed is:
1. A method for dynamic bandwidth optimization in a communication network, said method comprising:
identifying at least one file transfer requirement, dynamically, by a transmitting client in said communication network;
communicating said at least one file transfer requirement to a receiving client in said communication network, by said transmitting client;
negotiating at least one file transfer parameter, dynamically, with said transmitting client, based on said file transfer requirement, by said receiving client;
preparing a final set of transfer parameters, based on said negotiation, by said transmitting client and receiving client; and
transmitting at least one file, based on said final set of transfer parameters, by said transmitting client.
2. The method as claimed in claim 1, wherein said file transfer requirement comprises of at least one of chunk size, and file part information.
3. The method as claimed in claim 2, wherein said file part information is measured based on at least one of chunk size, and network bandwidth.
4. The method as claimed in claim 1, wherein said file transfer requirement varies based on file handling capability of said transmitting client.
5. The method as claimed in claim 1, wherein negotiating said file transfer parameter with said transmitting client further comprises:
comparing said at least one file transfer requirement with at least one of own file handling capacity and network bandwidth, by said receiving client;
modifying said file transfer requirement by said receiving client, if said at least one file transfer requirement does not match said at least one of own file handling capacity and network bandwidth, by said receiving client;
communicating said modified file transfer requirement to said transmitting client, by said receiving client; and
accepting said modified file transfer requirement, by said transmitting client.
6. The method as claimed in claim 1, wherein said final set of transfer parameters comprises of at least one of a Message Session Relay Protocol (MSRP) chunk size, information pertaining to number of file parts, and bandwidth information.
7. A system for dynamic bandwidth optimization in a communication network, said system configured for:
identifying at least one file transfer requirement, dynamically, by a transmitting client in said communication network;
communicating said at least one file transfer requirement to a receiving client in said communication network, by said transmitting client;
negotiating at least one file transfer parameter, dynamically, with said transmitting client, based on said at least one file transfer requirement, by said receiving client;
preparing a final set of transfer parameters, based on said negotiation, by said transmitting client and receiving client; and
transmitting at least one file, based on said final set of transfer parameters, by said transmitting client.
8. The system as claimed in claim 7, wherein said transmitting client is configured to identify said file transfer requirement in terms of at least one of a chunk size, and file part information.
9. The system as claimed in claim 8, wherein said transmitting client is further configured to measure said file part information, based on at least one of a chunk size, and network bandwidth.
10. The system as claimed in claim 7, wherein said receiving client is configured to negotiate said file transfer parameter with said transmitting client by:
comparing said at least one file transfer requirement with at least one of own file handling capacity and network bandwidth, by a requirement assessment module in said receiving client;
modifying said file transfer requirement by said receiving client, if said at least one file transfer requirement does not match said at least one of own file handling capacity and network bandwidth, by said requirement assessment module;
communicating said modified file transfer requirement to said transmitting client, by said requirement assessment module; and
accepting said modified file transfer requirement, by said transmitting client.

Date: 10th June 2015

Signature: Kalyan Chakravarthy
,TagSPECI:FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005

COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)

TITLE OF THE INVENTION
“METHOD AND SYSTEM FOR DYNAMIC BANDWIDTH OPTIMIZATION IN A COMMUNICATION NETWORK”

APPLICANTS:
Name Nationality Address
SAMSUNG R&D Institute India - Bangalore Private Limited India # 2870, Orion Building, Bagmane Constellation Business Park, Outer Ring Road, Doddanekundi Circle, Marathahalli Post, Bangalore-560 037, India

The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-

TECHNICAL FIELD
[001] The embodiments herein relate to communication networks and, more particularly, to dynamic bandwidth optimization in communication networks.
BACKGROUND
[002] Internet protocol multimedia subsystems (IMS) or IP Multimedia Core Network Subsystem is an open architecture for mobile and fixed services. IMS was designed by 3rd generation partnership project (3GPP). It is a next generation network system for telecoms to provide mobile and fixed multimedia services. It runs on the standard internet protocol, uses voice over IP based on 3GPP and implements standardized Session Initiation Protocol (SIP). The existing telecommunication systems, both packet and circuit switch, supports IMS.
[003] Rich Communications Suite (RCS) in Internet Protocol (IP) Multimedia Subsystem (IMS) is a recently developed service-type in the IMS domain. RCS is a Global System for Mobile Communication Association (GSMA) initiative and was created based on IMS inter-operator services. This service prioritizes the interoperability of services across network operators and handset manufacturers. RCS enables ‘rich communication’ services such as enriched calls that enable multimedia content sharing during a voice call, enhanced phone books that enable information about a contact registered to the phone book to be obtained in real time, enriched messaging that enables file sharing during texting, while supporting traditional functionalities such as voice and short message services. RCS marks the transition of messaging and voice capabilities to an all-IP world.
[004] IMS (GSMA RCS) specifies methods to transfer files between two devices over IMS network. Data communication or file transfer is achieved by using SIP and Message Session Relay Protocol (MSRP). SIP is an application layer protocol defines the messages that are sent between endpoints, govern establishment, termination and other essential elements of a call. SIP can be used for creating, modifying and terminating sessions consisting of one or several media streams. It is a text-based protocol with elements such as Hypertext Transfer Protocol (HTTP) and the Simple Mail Transfer Protocol (SMTP). MSRP is a protocol for transmitting a series of related instant messages during communication session. MSRP is used within SIP: to one-to-one or one-to- many devices, to do attachment file transfer, to do some photo sharing based on prior exchange of capabilities between the devices.
[005] The existing mechanism in IMS uses single TCP connection and file content is transferred serially over MSRP. Currently, by using already available enhanced hardware and network, both network and client can send/receive data more than being handled with the serial transmission being adopted by the existing mechanism. This results in inefficient bandwidth utilization, and in turn on wastage of resources. Further, the serial transmission of data, being adopted by existing IMS based mechanisms are slow in nature, especially when data in bulk needs to be communicated/transmitted over the network.
OBJECT OF INVENTION
[006] An object of the embodiments herein is to dynamically identify file transfer requirements of a transmitting client in a communication network.
[007] Another object of the embodiments herein is to negotiate file transfer parameters between the transmitting client and a receiving client in the communication network.
[008] Another object of the embodiments herein is to transmit data, based on file transfer parameters decided during negotiation between the transmitting and receiving clients in the communication network.

SUMMARY
[009] In view of the foregoing, an embodiment herein provides a method for dynamic bandwidth optimization in a communication network. At least one file transfer requirement is identified dynamically by a transmitting client in the communication network. Further, the file transfer requirement is communicated to a receiving client in the communication network. The receiving client then negotiates at least one file transfer parameter, dynamically, with the transmitting client, based on the file transfer requirement. Further, a final set of transfer parameters is prepared based on the negotiation, by the transmitting client and receiving client, and at least one file is transmitted based on the final set of transfer parameters, by the transmitting client.
[0010] Embodiments further disclose a system for dynamic bandwidth optimization in a communication network. A transmitting client in the system is configured for identifying at least one file transfer requirement, dynamically. Further, the file transfer requirement is communicated to a receiving client. The receiving client, upon receiving the file transfer requirement, negotiates at least one file transfer parameter, dynamically, with the transmitting client. Further, based on the negotiation, a final set of transfer parameters is prepared by the transmitting client and receiving client. The transmitting client then transmits at least one file, based on the final set of transfer parameters.

BRIEF DESCRIPTION OF THE FIGURES
[0011] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[0012] FIG. 1 illustrates a block diagram of dynamic bandwidth optimization system, as disclosed in the embodiments herein;
[0013] FIG. 2 is a block diagram that depicts components of a transmitting client, as disclosed in the embodiments herein;
[0014] FIG. 3 is a block diagram that depicts components of a receiving client, as disclosed in the embodiments herein; and
[0015] FIG. 4 is a flow diagram that depicts steps involved in the process of dynamically optimizing network bandwidth, using the dynamic bandwidth optimization system, as disclosed in the embodiments herein.

DETAILED DESCRIPTION OF EMBODIMENTS
[0016] 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. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0017] The embodiments herein disclose a method and system for dynamic network bandwidth optimization in a communication network by dynamically synchronizing functions of transmitting and receiving clients in the communication network. Referring now to the drawings, and more particularly to FIGS. 1 through 4, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0018] FIG. 1 illustrates a block diagram of dynamic bandwidth optimization system, as disclosed in the embodiments herein. The dynamic bandwidth optimization system 100 comprises of a transmitting client 101, and a receiving client 102.
[0019] The transmitting client 101 can be any communication device that can be configured to establish a communication with the receiving client 102, for the purpose of file transfer. For example, the transmitting client 101 can be a mobile phone. The transmitting client 101 can be further configured to identify, based on at least one of a chunk size of Message Session Relay Protocol (MSRP), and/or bandwidth of the communication network, number of file parts that can be transmitted to the receiving client 102. The transmitting client 101 can be further configured to transmit the chunk size and the file part information to the receiving client 102, as file transfer requirements. The transmitting client 101 can be further configured to negotiate file transfer parameter(s) with the receiving client, to generate a final set of transfer parameters. The transmitting client 101 can be further configured to transmit the data to the receiving client, using at least one suitable communication channel that connects the transmitting client 101 with the receiving client 102. In a preferred embodiment, the transmitting client 101 transmits the file parts, using a parallel communication established with the receiving client 102.
[0020] The receiving client 102 can be any communication device that can be configured to establish a communication with the transmitting client 101, for the purpose of file transfer. For example, the receiving client 102 can be a mobile phone, a tablet, a laptop, and/or any similar device that can negotiate at least one file transfer parameter with the transmitting client 101. The receiving client 102 can be configured to receive file transfer requirements from the transmitting client 101, and negotiate, if required, at least one file transfer parameter with the transmitting client 101. The receiving client 102 further receives file parts from the transmitting client 101, concatenates the file parts, and displays to the user.
[0021] FIG. 2 is a block diagram that depicts components of a transmitting client, as disclosed in the embodiments herein. The transmitting client 101 comprises of an Input/Output (I/O) interface 201, a file part assessment module 202, and a resource allocator module 203.
[0022] The I/O interface 201 can be configured to provide at least one channel with suitable communication protocol for the transmitting client 101 to communicate with at least one external entity such as the receiving client 102. The I/O interface 201 can be further configured to facilitate communication between the transmitting client 101 and the receiving client 102, using any suitable network type such as, but not limited to networks that support single SIP connection, multiple SIP connections, and single SIP connection with multiple lines.
[0023] The file part assessment module 202 can be configured to identify, based on MSRP chunk size and bandwidth availability, number of file parts in which the data can be transmitted to the receiving client. The file part assessment module 202 can be further configured to consider data processing capabilities of at least one resource in the transmitting client 101, while calculating number of file parts. The file part assessment module 202 can be further configured to generate a data transfer requirement, based on the number of file parts and the MSRP chunk size information, and transmit the file transfer requirements to the receiving client 102. The file part assessment module 202 can be further configured to receive a response from the receiving client 102, for the file transfer requirement, negotiate if required, and agree on a specific number of file parts, as requested by the receiving client. The file part assessment module 202 can be further configured to transmit the file part information to the resource allocator module 203.
[0024] The resource allocator module 203 can be configured to fetch from the file part assessment module 202, information pertaining to number of file parts being decided based on negotiation with the receiving client 102, and prepares a final set of transfer parameters, based on which the data transfer takes place between the transmitting client 101 and the receiving client 102. The resource allocator module 203 can be further configured to split the data to ‘n’ number of file parts, wherein the value of ‘n’ is decided based on negotiation between the transmitting client 101 and the receiving client 102, and transmit the file parts using available resources. In a preferred embodiment, the resource allocator module 203 assigns a unique Id to all file parts of the data being transmitted so that the receiving client can differentiate between file parts of different data being received from the transmitting module 101.
[0025] FIG. 3 is a block diagram that depicts components of a receiving client, as disclosed in the embodiments herein. The receiving client 102 comprises of an Input/Output (I/O) interface 301, a requirement assessment module 302, and a data assembling module 303.
[0026] The I/O interface 301 can be configured to provide at least one channel with suitable communication protocol for the receiving client 102 to communicate with at least one external entity such as the transmitting client 101. The I/O interface 301 can be further configured to facilitate communication between the receiving client 102 and the transmitting client 101, using any suitable network type such as, but not limited to networks that support single SIP connection, multiple SIP connections, and single SIP connection with multiple lines.
[0027] The requirement assessment module 302 can be configured to collect the data transfer requirements transmitted by the transmitting client 101, and assess data transfer and data processing requirements of the transmitting client 101. The requirement assessment module 302 further checks if the data transfer requirements of the transmitting client 101 matches at least one of own data processing capabilities, and network bandwidth availability. The requirement assessment module 302 can be further configured to negotiate at least one data transfer parameter with the transmitting client, if the data transfer requirement of the transmitting client 101 is not matching at least one of the data processing capabilities, and network bandwidth availability of the receiving client 102. The requirement assessment module 302 can be further configured to communicate with the resource allocator module 203 to form the final set of transfer parameters.
[0028] The data assembling module 303 can be configured to receive file parts being transmitted by the transmitting module 101, and concatenate the file parts pertaining to each data being transmitted. In a preferred embodiment, the data assembling module 303 checks the unique Id value associated with the file parts, to identify file parts that belong to the data being transmitted by the transmitting client 101. The data assembling module 303 can be further configured to provide the concatenated data to the I/O interface 301, so that the data can be presented to the user in at least one suitable format, using at least one suitable user interface.
[0029] FIG. 4 is a flow diagram that depicts steps involved in the process of dynamically optimizing network bandwidth utilization, using the dynamic bandwidth optimization system, as disclosed in the embodiments herein. Initially, the transmitting client 101 analyzes amount of data to be transmitted to the receiving client 102, and identifies (402) file transfer requirements. In an embodiment, the file transfer requirement comprises of at least one of the MSRP chunk size, and file part information. The chunk size is preset by the user or by any authorized person. In a preferred embodiment¸ the chunk size includes MSRP header size, and is a fixed value.
[0030] In a preferred embodiment, the file part information is dynamically measured by the transmitting client 101. For example, assume that the total size of data to be transmitted is 100K, and that the network bandwidth supports transmission of 100K data at once. Now the transmitting client 101 checks capacity of the resource available. Assume that the resource can process 10K data, then 10 such resources in parallel can be used to transmit the 100K data.
[0031] The transmitting client 101 further generates file transfer requirements, based on the chunk size, and the file part information, and communicates (404) the file transfer requirement to the receiving client 102. The receiving client 102, by processing the file transfer requirement received from the transmitting client 101, checks (406) whether the file transfer requirement matches (408) at least one capability of the receiving client 102. The capability of the receiving client 102 can be defined based on at least one parameter such as, but not limited to bandwidth availability, and data processing capacity of resources available at the receiving client 102.
[0032] Upon identifying that at least one of the data transfer requirements of the transmitting client 101 do not match capabilities of the receiving client 102, the receiving client 102 responds to the transmitting client 101, with information pertaining to own capabilities. The receiving client 102 further negotiates (410) with the transmitting client 101, in terms of at least one file transfer requirement. For example, if the resources at the receiving client 102 are unable to match the data processing capability requested by the transmitting client 101, then the receiving client 102 can negotiate with the transmitting client 101 to reduce the requirement to a level that is less than or equal to the capability of the receiving client 102.
[0033] By negotiating at least one transfer requirement, the transmitting client 101 and the receiving client 102 prepares (412) a final set of transfer parameters. The final set of transfer parameters can include, but not limited to MSRP chunk size, information pertaining to number of file parts, and bandwidth information. Further, based on the values of final set of transfer parameters, the transmitting client 101 prepares the data for transmission. In this stage, based on the number of file parts (n) mutually agreed by the transmitting client 101 and the receiving client 102, the transmitting client 101 splits the data to be transferred to ‘n’ file parts. Further, a unique Id that represents the data is added to each file part. Further, the file parts are transmitted (414) to the receiving client 102. At the receiving end, the receiving client receives the file parts, concatenates the file parts, and is provided to the user, in a suitable format.
[0034] In an embodiment, the dynamic bandwidth optimization system 100 can be used with different types of networks, and the data and control flow can vary from network to network. The communication between a transmitting client 101 and a receiving client 101, for dynamic bandwidth optimization, in different networks, is narrated below:
1) Single SIP (Session Initiation Protocol) Session:
[0035] In this scenario, the transmitting client 101 sends an INVITE message with a Session Description Protocol (SDP) containing a file-selector attribute. The file selector attribute further comprises of file name, file type, size, chunk size (total MSRP packet size to be transmitted), and file parts (i.e. number of file parts to be transmitted) fields. As a response to the INVITE message, the receiving client 102 sends information pertaining to minimum of own parameters, device capability, and network bandwidth, to the transmitting client 101, along with the 200 OK message.
[0036] After successful negotiation, the sending client 101 and the receiving client 102 then creates individual resources (threads) for transmitting/receiving each file part. A fixed MSRP packet size as decided based on chunk-size negotiated is used to solve TCP fragmentation/reassembly problem. Each MSRP packet carries file-part number so that the receiving client 102 can pass the packets to corresponding resource (thread) for processing. In an embodiment, after successful negotiation, the transmitting client 101 and the receiving client 102 decides resource that is to be used to handle each file part. The receiving client 102, on receiving each file-part using different resources, stores the file parts in a temporary location and once all parts are received, concatenates and a single file is presented to the user.
2) Multiple SIP Sessions
[0037] The transmitting client 101 sends a file transfer request in a single SIP INVITE with file-range attribute in SDP. The file-range carries complete file range (e.g. if file size is 4K is the file-range: 1-4K). The receiving client 102 accepts the file-range and sends 200 OK SDP with same file-range, in response to the INVITE message. Further, a file transfer session is established between the transmitting client 101 and the receiving client 102, and the transmitting client 101 sends the file.
[0038] In this scenario, even after beginning the data transmission, if the transmitting client 101 realizes that it can send more data than being transferred currently based on hardware capability and network bandwidth, then the transmitting client accordingly decides on the number of file-parts it can send, and sends a new SIP INVITE for each of the parts with file-range attribute set to the range of each file-parts. The receiving client 102, on receiving these subsequent INVITE, can choose to accept/reject each of the parts based on its capability to handle the file-parts. In an embodiment, the decision of the receiving client 102 to accept/reject a file part is not informed to the user. If the receiving client 102 accepts a file part, it is transferred in a new TCP connection negotiated as part of the new INVITE. If the receiving client 102 rejects a file part, then the file part is sent as part of the first SIP Session and TCP connection established as part of it. Each SIP Session ensures that a new TCP connection is created to transfer each file-part. The received file parts can be saved in a temporary location, concatenated, and can be presented to the user.
3) Single SIP Session with multiple media (m) lines
[0039] In this scenario, the transmitting client 101 decides on the number of file parts it can handle, and adds same number of media lines in SDP of Outgoing SIP INVITE. Each m-line carries same file-name, File Type and size. Each m-line also carries file-range attribute with no values filled (for example, First m-line -> file-range: 1-*, remaining m-lines -> file-range :*-*).
[0040] The receiving client 102, based on own capability to handle file-parts, chooses the number of m-lines and sets the file-range attribute with the range of each of the file parts. For example, if receiving client 102 can handle three file parts, it sets each m-line with 33% of the complete file-range. The transmitting client 101, on receiving the SDP in 200 OK from receiving client 102, creates the number of TCP connections same as the number as that of the m-line. Each file-part is then transferred using individual TCP connections. Each of the file-parts received can be kept in a temporary location, concatenated, and can be presented to the user in a suitable format.
[0041] The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
[0042] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0043] The embodiments disclosed herein specify a system for dynamic bandwidth utilization in a communication network. The mechanism allows bandwidth utilization, providing a system thereof. Therefore, it is understood synchronization of working of transmitting and receiving clients to improve that the scope of protection is extended to such a system and by extension, to a computer readable means having a message therein, said computer readable means containing a program code for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment using the system together with a software program written in, for ex. Very high speed integrated circuit Hardware Description Language (VHDL), another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including, for ex. any kind of a computer like a server or a personal computer, or the like, or any combination thereof, for ex. one processor and two FPGAs. The device may also include means which could be for ex. hardware means like an ASIC or a combination of hardware and software means, an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means are at least one hardware means or at least one hardware-cum-software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. Alternatively, the embodiment may be implemented on different hardware devices, for ex. using a plurality of CPUs.
[0044] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims as described herein.

CLAIMS
What is claimed is:
1. A method for dynamic bandwidth optimization in a communication network, said method comprising:
identifying at least one file transfer requirement, dynamically, by a transmitting client in said communication network;
communicating said at least one file transfer requirement to a receiving client in said communication network, by said transmitting client;
negotiating at least one file transfer parameter, dynamically, with said transmitting client, based on said file transfer requirement, by said receiving client;
preparing a final set of transfer parameters, based on said negotiation, by said transmitting client and receiving client; and
transmitting at least one file, based on said final set of transfer parameters, by said transmitting client.
2. The method as claimed in claim 1, wherein said file transfer requirement comprises of at least one of chunk size, and file part information.
3. The method as claimed in claim 2, wherein said file part information is measured based on at least one of chunk size, and network bandwidth.
4. The method as claimed in claim 1, wherein said file transfer requirement varies based on file handling capability of said transmitting client.
5. The method as claimed in claim 1, wherein negotiating said file transfer parameter with said transmitting client further comprises:
comparing said at least one file transfer requirement with at least one of own file handling capacity and network bandwidth, by said receiving client;
modifying said file transfer requirement by said receiving client, if said at least one file transfer requirement does not match said at least one of own file handling capacity and network bandwidth, by said receiving client;
communicating said modified file transfer requirement to said transmitting client, by said receiving client; and
accepting said modified file transfer requirement, by said transmitting client.
6. The method as claimed in claim 1, wherein said final set of transfer parameters comprises of at least one of a Message Session Relay Protocol (MSRP) chunk size, information pertaining to number of file parts, and bandwidth information.
7. A system for dynamic bandwidth optimization in a communication network, said system configured for:
identifying at least one file transfer requirement, dynamically, by a transmitting client in said communication network;
communicating said at least one file transfer requirement to a receiving client in said communication network, by said transmitting client;
negotiating at least one file transfer parameter, dynamically, with said transmitting client, based on said at least one file transfer requirement, by said receiving client;
preparing a final set of transfer parameters, based on said negotiation, by said transmitting client and receiving client; and
transmitting at least one file, based on said final set of transfer parameters, by said transmitting client.
8. The system as claimed in claim 7, wherein said transmitting client is configured to identify said file transfer requirement in terms of at least one of a chunk size, and file part information.
9. The system as claimed in claim 8, wherein said transmitting client is further configured to measure said file part information, based on at least one of a chunk size, and network bandwidth.
10. The system as claimed in claim 7, wherein said receiving client is configured to negotiate said file transfer parameter with said transmitting client by:
comparing said at least one file transfer requirement with at least one of own file handling capacity and network bandwidth, by a requirement assessment module in said receiving client;
modifying said file transfer requirement by said receiving client, if said at least one file transfer requirement does not match said at least one of own file handling capacity and network bandwidth, by said requirement assessment module;
communicating said modified file transfer requirement to said transmitting client, by said requirement assessment module; and
accepting said modified file transfer requirement, by said transmitting client.

Date: 10th June 2015

Signature: Kalyan Chakravarthy

ABSTRACT
A method and a system for dynamic bandwidth optimization in a communication network. A transmitting client in the system, based on chunk size and network bandwidth, calculates number of file parts. The transmitting client then communicates the chunk size and file part information to a receiving client, as file transfer requirements. The receiving client compares the file transfer requirements with own capabilities, and checks if the file transfer requirements own capability. If the file transfer requirements and capabilities are not matching, the receiving client negotiates at least one file transfer parameter with the transmitting client, and a final set of parameters is prepared. Further, the transmitting client transmits data, based on the final set of parameters. The receiving client collects the file parts of the data being transmitted, concatenates the file parts, and displays the data to the user.

FIG. 4