WO2011083127A1

WO2011083127A1 - System for expediting the transfer of data files between end systems in a packet network

Info

Publication number: WO2011083127A1
Application number: PCT/EP2011/050107
Authority: WO
Inventors: Adiseshu Hari; Dimitrios Stiliadis; Andrea Francini; Chandra Sekhar
Original assignee: Alcatel Lucent SAS
Current assignee: Alcatel Lucent SAS
Priority date: 2010-01-06
Filing date: 2011-01-05
Publication date: 2011-07-14
Anticipated expiration: 2012-07-06

Abstract

A system for expediting the transfer of data files between end systems in packet networks is disclosed. The application relates to data file transfers between end systems across a packet network and, more particularly, to expediting data file transfers in networks. Data file transfers may be slowed by lack of simultaneous availability of a network path between the end systems and of operational capability at either end system. The problem is addressed by incorporating an add-on module in the network path between the end systems. Data files are transferred to the add-on module from a source end system when the latter is capable of operation and connected to the former. Further, data files are transferred from the add-on module to the destination end system when the latter is capable of operation and connected to the former. As a result, time involved in completing data file transfers is reduced.

Description

SYSTEM FOR EXPEDITING THE TRANSFER OF DATA FILES BETWEEN END SYSTEMS IN A PACKET NETWORK TECHNICAL FIELD

[001] The present invention relates to communication networks and, more particularly, to data transfers in communication networks.

BACKGROUND

[002] In computing systems, data are organized, stored, and handled by computing applications as data files. Data files are transferred across the packet network in blocks called packets. The Internet-Protocol (IP) suite defines methods for the identification of end systems and intermediate network nodes and for the transfer of packets over network paths. A network path is a sequence of network links between two network nodes, where each of the two network nodes that terminate the path can be either an intermediate network node or an end system.

[003] Data transfers between end systems can occur only if the following two conditions are simultaneously satisfied. The first condition, called the network path integrity (NPI) condition, requires that a working network path exist between the two end systems. The second condition, called the end system availability (ESA) condition, requires that both end systems be powered on and capable of operation. There may be instances, for example, in which the transfer of a data file may not be possible at a time when the source end system is powered on and capable of operation and a working network path exists between source and destination end systems, only because the destination end system is not powered on. The need for the simultaneous satisfaction of both conditions may delay the transfer of data files and interfere with the normal operation of the end systems, degrading the performance of the computing applications that utilize the data files to be transferred and also of other applications that run on the end systems.

[004] Data caching is a method commonly employed to speed up data file transfers between end systems. When multiple end systems may be likely recipients of the same data file from a given source, data caching can be used to move the data file from the source to an alternate network node with a single transfer. If the alternate network node is properly located along the network paths from the source to the destination end systems, temporarily storing (or caching) the data file in the alternate node can dramatically reduce the consumption of network resources needed to complete the transfer of the data file to all destination end systems. However, data caching as commonly deployed works well for unidirectional transfers from one source to many destinations, but not for end-to-end communications where data files may be transferred in both directions. Another limitation of traditional data caching configurations is that the alternate network node used for temporary storage does not reside in the portion of network path between the end system that most frequently violates the ESA condition and the network link that most frequently violates the NPI condition, and therefore cannot remove the requirement that both conditions be satisfied at the same time in order for the data file transfers to proceed to completion.

SUMMARY

[005] In view of the foregoing, an embodiment herein provides a communication system for expediting the transfer of data files between two end systems in a packet switching network. The system comprises a Persistent End System (PES), which is assumed to be persistently powered on and capable of operation, a Sporadic End System (SES), which may not be powered on or capable of operation for extended periods of time, and an add-on module connected to the SES. The add-on module comprises at least one means configured for checking availability of data files at the PES upon availability of a network path between the PES and the add-on module, regardless of the status of the SES; for fetching the data files from the PES, if data files are available at the PES; for storing the data files in a storage area present in the add-on module; and for transferring the data files to the SES when the SES is powered on and capable of operation, regardless of the status of the network path between the add-on module and the PES. The add-on module may further comprise one means configured for checking availability of data files at the SES when the SES is powered on and capable of operation, regardless of the status of the network path between the add-on module and the PES; for fetching the data files from the SES, if data files are available at the SES; for storing the data files in a storage area present in the add-on module; and for transferring the data files to the PES when a network path is available between the add-on module and the PES. The add-on module may be connected to the SES by one of a Universal Serial Bus (USB) connection; a Personal Computer Memory Card International Association (PCMCIA) connection; an ExpressCard connection; or a highly available network path.

[006] Embodiments further disclose a Dedicated Computing

Module (DCM) in the PES, configured for handling data file transfers between the PES and the add-on module independent of the SES being powered on; a Dedicated Computing Module (DCM) in the add-on module, configured for handling data file transfers between the add-on module and the PES independent of the SES being powered on, and for handling data file transfers between the add-on module and the SES independent of the availability of a network path between the add-on module and the PES; and a Dedicated Computing Module (DCM) in the SES, configured for handling data file transfers between the add-on module and the SES independent of the availability of a working network path between the addon module and the PES.

[007] Embodiments herein also disclose an add-on module for expediting data file transfers in a communication system, the add-on module being connected to a Sporadic End System (SES) by one of a Universal Serial Bus (USB) connection; a Personal Computer Memory Card International Association (PCMCIA) connection; an ExpressCard connection; or a highly available network path, and further comprising at least one means configured for checking availability of data files at a Persistent End System (PES) upon availability of a network path between the PES and the add-on module, regardless of the status of the SES; for fetching the data files from the PES, if data files are available at the PES; for storing the data files in a storage area present in the add-on module; and for transferring the data files to the SES when the SES is powered on and capable of operation, regardless of the availability of a network path between the add-on module and the PES. The add-on module of the embodiments herein may also comprise one means configured for checking availability of data files on the SES when the SES is powered on and capable of operation, regardless of the status of the network path between the add-on module and the PES; for fetching the data files from the SES, if data files are available at the SES; for storing the data files in a storage area present in the add-on module; and for transferring the data files to the PES when a working network path is available between the add-on module and the PES. The storage means in the add-on module is any one of a buffer, a Random Access Memory (RAM), a flash memory, or any other device capable of storing digitally encoded data.

[008] Also disclosed herein is a method for expediting the transfer of data files between a Persistent End System (PES) and a Sporadic End System (SES) in a packet switching network. The method comprises steps of an add-on module checking availability of data files at a PES upon availability of a working network path between the PES and the add-on module, wherein the add-on module is connected to the SES and regardless of the status of the SES. The add-on module fetches the data files from the PES, if data files are available at the PES; stores the data files in a storage area present in the add-on module; and transfers the data files to the SES when the SES is powered on and capable of operation. The method also comprises steps of an add-on module checking availability of data files at an SES when the SES is powered on and capable of operation, regardless of the availability of a network path between the add-on module and the PES. The add-on module fetches the data files from the SES, if data files are available at the SES, and transfers the data files to the PES when the network path to the PES is working. The add-on module may be connected to the SES by one of a Universal Serial Bus (USB) connection, a Personal Computer Memory Card International Association (PCMCIA) connection, an ExpressCard connection, or a highly available network path.

[009] 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.

BRIEF DESCRIPTION OF THE FIGURES

[0010] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:

[0011] FIG. 1 illustrates a packet network including intermediate network nodes, network links, a Sporadic End System (SES), a Persistent End System (PES), and an add-on module, according to embodiments as disclosed herein; [0012] FIG. 2 illustrates a Sporadic Network Segment (SNS) included in the network path of FIG. 1, according to embodiments as disclosed herein;

[0013] FIG. 3 illustrates a block diagram of an add-on module, according to embodiments as disclosed herein;

[0014] FIG. 4 illustrates a block diagram of an SES dedicated computing module (DCM), according to embodiments as disclosed herein;

[0015] FIG. 5 illustrates a block diagram of a PES dedicated computing module (DCM), according to embodiments as disclosed herein;

[0016] FIG. 6 illustrates a block diagram of an add-on module dedicated computing module (DCM), according to embodiments as disclosed herein;

[0017] FIG. 7 depicts a flowchart describing a method of operation for the SES DCM, according to embodiments as disclosed herein;

[0018] FIG. 8 depicts a flowchart describing a method of operation for the PES DCM, according to embodiments as disclosed herein; and

[0019] FIG. 9a, 9b depicts a flowchart describing a method of operation for an add-on module DCM, according to embodiments as disclosed herein. DETAILED DESCRIPTION OF EMBODIMENTS

[0020] 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.

[0021] The embodiments herein disclose a system for expediting transfer of data files in a packet switched network by providing systems and methods thereof. Referring now to the drawings, and more particularly to FIGS. 1 through 9, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0022] A communication system for expediting transfer of data files between a sporadic end system (SES) and a persistent end system (PES) in a packet switched network is disclosed. The SES is a computing device that may be available at sporadic intervals. The PES is a computing device that is highly available. The SES and the PES may be any computing device such as a portable computer, a desktop computing device, a hand held computing device, a server, an enterprise management station, and so on. The add-on module is included in the network path between the PES and the SES and is reliably connected with the SES. In such a communication system, data files are transferred from the PES to the add-on module and from the add-on module to the PES when network connectivity is available between the PES and the add-on module, independent of the status of the SES. Also in such a communication system, data files are transferred from the add-on module to the SES and from the SES to the add-on module when the SES is powered on and capable of operation and independent of the availability of a network path between the add-on module and the PES. The add-on module is provided with intelligence, called Dedicated Computing Module (DCM), for managing the transfer and storage of data files on the add-on module. The add-on module includes a storage area for storage of the data files in transit from the SES to the PES and from the PES to the SES.

[0023] The network path that connects the SES and the PES includes one network link or a plurality of network links that may not be persistently available and thereby cause violations of the NPI condition. The portion of network path that includes such sporadic network links is called a Sporadic Network Segment (SNS). In an example, an SNS made of a single sporadic network link may consist of a wireless network link between a mobile terminal and a wireless base station, which may be available for connectivity only when the mobile terminal is within the signal coverage area of the base station and the base station has an unused wireless channel available for allocation to the mobile terminal, where the mobile terminal is an SES. In the same example, the sporadicity of the mobile terminal that causes violations of the ESA condition may derive from the necessity to switch off the mobile terminal for power-saving purposes when operation of the mobile terminal is not needed by a user. In a second example, the intermediate network node at the network end of the SNS may be a broadband router that is powered on only during business hours (e.g., between 8:00am and 5:00pm). Between 5:00pm and 8:00am, when the broadband router is powered off, the network link is not available for connecting the SES to the PES.

[0024] FIG. 1 illustrates a packet network including intermediate network nodes, network links, a Sporadic End System (SES) and a Persistent End System (PES), according to embodiments as disclosed herein. SES instances include systems such as desktop, laptops, tablet computers, handheld computing devices, mobile terminals and the like. The packet network comprises add-on modules 102, 102.1, intermediate network nodes 103, 103.1, 103.2, 103.3, network links, SES 101, 101.1, and PES 104, 104.1. Several SES 101, 101.1 and PES 104, 104.1 may be connected to the intermediate network nodes 103, 103.1.

[0025] As also shown in FIG. 2, the add-on module 102 is included in the network path between the SES 101 and the Sporadic Network Segment (SNS). The add-on module 102 comprises a processor unit, a facility for storage of program code and data files, an independent power supply, and two network interfaces, of which one faces the SES 101 and the other faces the Sporadic Network Segment. The connection between the add-on module 102 and the SES 101 may be a physical connection such as a Universal Serial Bus (USB) connection, a Personal Computer Memory Card International Association (PCMCIA) connection, an Express Card connection, or any suitable connection means. The connection between the add-on module 102 and the SES 101 may also be a network connection with highly available connectivity. The add-on module 102 may be placed outside the SES 101 or within the SES 101. In both cases, the add-on module 102 can be powered on independent of the power state of the SES 101. A data file transferred to the add-on module 102 is stored in the storage facility in the add-on module 102. Further, the add-on module 102 transfers the stored data files to the SES 101 when the SES 101 is powered on.

[0026] When a connection is established between an SES 101 and a PES 104, data files are transferred over the network links that compose the network path over which the connection between the PES 104 and SES 101 is established. Data files from the PES 104 may be transferred to the SES 101 via the intermediate network nodes 103, 103.1 provided in the network path. Intermediate network nodes 103, 103.1 are connected to other intermediate network nodes via network links. Distinct instances of an intelligent unit called the Dedicated Computing Module (DCM) are present in the add-on module 102, in the PES 104, and in the SES 101. The DCM in the add-on module 102 is referred to as the add-on module DCM; the DCM in the PES 104 is referred to as the PES DCM; and the DCM in the SES 101 is referred to as the SES DCM. [0027] Data files are transferred from the PES 104 to the SES 101 in two steps; in the first step, the data file transfer from the PES 104 to the add-on module 102 occurs after a new data file becomes available in the dedicated storage area maintained by the PES DCM, at a time when the sporadic network segment of the network path between the PES 104 and the add-on module 102 is available. In the second step, the data file transfer from the add-on module 102 to the SES 101 occurs after a new data file becomes available in the dedicated storage area maintained by the add-on module DCM, at a time when the SES 101 is powered on and capable of operation.

[0028] In a similar fashion, data files are transferred from the SES 101 to the PES 104 in two steps; a first data file transfer from the SES 101 to the add-on module 102 occurs after a new data file becomes available in the dedicated storage area maintained by the SES DCM, at a time when the SES 101 is powered on and capable of operation. Further, a second data file transfer from the add-on module 102 to the PES 104 occurs after a new data file becomes available in the dedicated storage area maintained by the add-on module DCM, at a time when the SNS in the network path between the add-on module 102 and the PES 104 is available.

[0029] FIG. 2 illustrates a Sporadic Network Segment (SNS) in the network path of FIG. 1, according to embodiments as disclosed herein. FIG. 2 depicts the add-on module 102 and three dedicated computing modules, a first one being the add-on module DCM 201, a second one the SES DCM 202, and a third one the PES DCM 203. When the SNS in the network path is available, the add-on module 102 can connect to the PES 104 independently of the power state and operational state of the SES 101. When the SES 101 is powered on and operational, the add-on module 102 can communicate with the SES 101 independently of the availability state of the SNS in the network path between the add-on module 102 and the PES 104.

[0030] The SES DCM 202 is capable of performing functions such as allocation and maintenance of a dedicated portion of a storage facility in the SES 101 for storage of data files to be transmitted to the PES 104. Also, the SES DCM 202 is capable of allocating and maintaining a dedicated portion of a storage facility in the SES 101 for storage of data files to be received from the PES 104. Further, when the SES 101 is in operation, the SES DCM 202 communicates with the add-on module DCM 201, to first verify the availability of new data files originating from the PES 104 and then request the transfer of new data files to the SES 101. When the SES 101 is in operation, the SES DCM 202 communicates with the add-on module DCM 201 to advertise the availability of new data files originating from the SES 101 and destined for the PES 104.

[0031] The add-on module DCM 201 allocates and maintains a dedicated portion of a storage facility in the add-on module 102 for storage of data files to be received from the PES 104. The add-on module DCM 201 further allocates and maintains a dedicated portion of a storage facility in the add-on module 102 for storage of data files to be received from the SES 101. When the SES 101 is powered on and capable of operation, the add-on module DCM 201 communicates with the SES DCM 202 to first verify the availability of new data files to be transferred to the PES 104 and then request the transfer of data files recognized as new to the add-on module 102. Further, when the Sporadic Network Segment (SNS) in the network path is available for network connectivity, the add-on module DCM 201 periodically communicates with the PES DCM 203 to first verify the availability of new data files to be transferred to the SES 101 and then request the transfer of the data files recognized as new to the add-on module 102.

[0032] The PES DCM 203 can allocate and maintain a dedicated portion of a storage facility in the PES 104 for storage of data files to be transmitted to the SES 101. The PES DCM 203 also allocates and maintains a dedicated portion of a storage facility in the PES 104 for storage of data files to be received from the SES 101. Further, while the network path is available for network connectivity, the PES DCM 203 communicates with the add-on module DCM 201 to first verify the availability of new data files originating from the SES 101 and then request the transfer to the PES 104 of the data files recognized as new. While the SNS in the network path between the add-on module 102 and the PES 104 is available for network connectivity, the PES DCM 203 communicates with the add-on module DCM 201 to advertise the availability of new data files originating from the PES 104 and destined for the SES 101.

[0033] FIG. 3 illustrates a block diagram of an add-on module, according to embodiments as disclosed herein. The add-on module 102 comprises a processor unit 301, an SES-facing network interface 302, a data/code storage facility 303, an SNS-facing network interface 304 and an independent power supply 305. The processor unit 301 controls the operation of the add-on module 102 by executing the code that is stored in data files/code storage facility 303. The data files/code storage facility 302 provides storage space for the code that defines operation of the add-on module 102 and for data files that are waiting for completion of their transfer to the SES 101 and the PES 104. The independent power supply 305 provides power supply to the add-on module 102 at times when the SES 101 is not powered on. The SES-facing network interface 302 supports network connectivity between the add-on module 102 and the SES 101. The SNS-facing network interface 304 supports network connectivity between the add-on module 102 and the SNS in the network path between the add-on module 102 and the PES 104.

[0034] The add-on module 102 remains in operational state independent of the availability of the SES 101. The add-on module 102 is provided with a power supply unit to maintain the add-on module in operation independent of the power state of the SES 101. The add-on module 102 also remains in operational state independent of the availability of the SNS in the network path between the add-on module 102 and the SNS in the network path between the add-on module 102 and the PES 104. The add-on module 102 may further extend the availability of the SNS in the network path between the add-on module 102 and the PES 104 by expansion of the set of networks that can be used for access connectivity. For example, the add-on module 102 may include a wireless network interface for connectivity to a broadband wireless network and an Ethernet interface for connectivity to a wired network. The add-on module 102 also establishes connectivity with the PES 104 when the SNS in the network path between the add-on module 102 and the PES 104 is available, independent of the availability of the SES 101. Further, the add-on module 102 establishes and maintains connectivity with the SES 101 every time the SES 101 becomes available, independent of the availability of the network path between the add-on module 102 and the PES 104.

[0035] FIG. 4 illustrates a block diagram of an SES dedicated computing module (DCM), according to embodiments as disclosed herein. The SES DCM 202 comprises a configuration interface 401, a data transport interface 402, an application configuration storage facility 403, a first application data set 404, which comprises an application identifier 405, a storage location 406, an access credentials set 407, a maximum storage space 408, and a transfer direction 408, a second application data set 410 (and possibly others), a data storage interface 411, and an add-on module DCM interface 412. The configuration interface 401 receives the configuration updates from the data transport interface 402 and passes them to the application configuration storage 403.

[0036] Data transport interface 402 handles all exchanges between the SES DCM 202 and the network protocol stack in the SES 101. The exchanges includes (i) the exchange of control data with the add-on module DCM 201 to prepare the transfer of data files to and from the add-on module 102; (ii) the inbound transfer of data files received from the PES 104 via the add-on module 102, and (iii) the outbound transfer of data files on their way to the PES 104 via the add-on module 102.

[0037] The application configuration storage facility 403 comprises a collection of application data sets, of which application data set 404 and application data set 410 constitute individual instances. Application data set 404 comprises a set of configuration parameters that define the handling in the SES DCM 202 of data files associated with a corresponding application. The configuration parameters include (i) an application identifier 405, which identifies the application and is unique for every application handled by the SES DCM 202; (ii) a storage location 406, which specifies the path in a storage facility accessible to the SES DCM 202 where data files associated with the application can be stored and found for retrieval; (iii) an access credentials set 407, which enables access for the SES DCM 202 to the persistent storage facility where data files associated with the application can be stored and found for retrieval; (iv) a maximum storage space 408, which quantifies the portion of the storage facility that is allocated for storage of data files associated with the application; and (v) a transfer direction 409, which indicates if the space in the storage facility is allocated to the application for data files to be transmitted to the PES 104 or for data files to be received from the PES 104. Application data set 410, like every other application data set stored in application configuration storage facility 403, comprises the same set of configuration parameters as application data set 404, only referring to a possibly different application and assuming possibly different values

[0038] The data storage interface 411 uses the configuration parameters retrieved from the application configuration storage facility 403 to (i) control the storage in persistent storage facilities of data files received from the PES 104 via the add-on module 102 and (ii) retrieve from persistent storage facilities data files destined for the PES 104 via the addon module 102.

[0039] The Add on module DCM interface 412 communicates with the add-on module DCM 201 through the data transport interface 402 and controls the data exchanges between the data transport interface 402 and the data storage interface 411 based on the configuration parameters stored in the application configuration storage facility 403 and on the control data received from the add-on module DCM 201. The data exchanges include (i) the inbound transfer of data files received from the PES 104 via the add-on module 102 and (ii) the outbound transfer of data files on their way to the PES 104 via the add-on module 102.

[0040] FIG. 5 illustrates the block diagram of a PES dedicated computing module (DCM), according to embodiments as disclosed herein. The PES DCM 203 comprises a configuration interface 501, a data transport interface 502, an application configuration storage facility 503, a first application data set 504, which comprises an application identifier 505, a storage location 506, an access credentials set 507, a maximum storage space 508, a transfer direction 509, and a data aging timeout 510, a second application data set 511 (and possibly other application data sets), a data storage interface 512 and an SES DCM interface 513.

[0041] The configuration interface 501 receives the configuration updates from the data transport interface 502 and passes the updates to the application configuration storage facility 503.

[0042] Data transport interface 502 handles all data exchanges between the PES DCM 203 and the network protocol stack in the PES 104. The data exchanges include (i) the exchange of control data with the add-on module DCM 201 to prepare the transfer of data files to and from the add- on module 102, (ii) the inbound transfer of data files received from the SES 101 via the add-on module 102, and (iii) the outbound transfer of data files on their way to the SES 101 via the add-on module 102.

[0043] The application configuration storage facility 503 comprises a collection of application data sets 504, 511, each application data set comprising a set of configuration parameters that define the handling in the PES DCM 203 of data files associated with a corresponding application. The configuration parameters in application data set 404 include (i) an application identifier 505, which identifies the application and is unique for every application handled by the PES DCM 203; (ii) a storage location 506, which specifies the path in a persistent storage facility accessible to the PES DCM 203 where data files associated with the application can be stored and found for retrieval; (iii) an access credentials set 507, which enables the PES DCM 203 to access the storage facility where data files associated with the application can be stored and found for retrieval; (iv) a maximum storage space 508, which quantifies the portion of the persistent storage facility that is allocated for storage of data files associated with the application; (v) a transfer direction 509, which indicates if the space in the storage facility is allocated to the application for data files to be transmitted to the SES 101 or for data files to be received from the SES 101; and (vi) a data aging timeout 510, which quantifies the minimum amount of time that a data file must be kept in the storage area allocated to the corresponding application before it is removed.

[0044] Data storage interface 512 uses the configuration parameters retrieved from the application configuration storage facility 503 to (i) control the storage in persistent storage facilities of data files received from SES 101 via the add-on module 102 and (ii) retrieve from persistent storage facilities data files destined for the SES 101 via the add-on module 102.

[0045] The add-on module DCM interface 513 communicates with the add-on module DCM 201 through the data transport interface 502 and controls the data exchanges between the data transport interface 502 and the data storage interface 512 based on the configuration parameters stored in the application configuration storage facility 503 and on the control data received from the add-on module DCM 201. The data exchanges include (i) the inbound transfer of data files received from the SES 101 via the add-on module 102 and (ii) the outbound transfer of data files on their way to the SES 101 via the add-on module 102.

[0046] FIG. 6 illustrates block diagram of an add-on module dedicated computing module (DCM), according to embodiments as disclosed herein. The add-on module DCM 201 comprises a configuration interface 601, a data transport interface 602, an application configuration storage facility 603, a first application data set 604, which comprises an application identifier 605, a maximum storage space 606, and a transfer direction 607, a second application data set 608 (and possibly other application data sets), a data storage interface 609, an SES DCM interface 610, and a PES DCM interface 611.

[0047] The configuration interface 601 receives the configuration updates from the data transport interface 602 and passes them to the application configuration storage facility 603.

[0048] The data transport interface 603 handles all data exchanges between the add-on module DCM 201 and the network protocol stack in the add-on module 102. The data exchanges include (i) the exchange of control data with the SES DCM 202 to prepare the transfer of data files to and from the SES 101, (ii) the exchange of control data with the PES DCM 203 to prepare the transfer of data files to and from the PES 104, (iii) the inbound transfer of data files received from the SES 101 and destined for the PES 104, (iv) the inbound transfer of data files received from the PES 104 and destined for the SES 101, (v) the outbound transfer of data files received from the SES 101 on the way to the PES 104, and (vi) the outbound transfer of data files received from the PES 104 on the way to the SES 101.

[0049] The application configuration storage facility 603 comprises a collection of application data sets 604, 608. Application data set 604 comprises a set of configuration parameters that define the handling in the add-on module DCM 201 of data files associated with a corresponding application. The configuration parameters include: (i) an application identifier 605, which identifies the application and is unique for every application handled by the add-on module DCM 201; (ii) a maximum storage space 606, which quantifies the portion of the storage facility that is allocated for storage of data files associated with the application; and (iii) a transfer direction 607, which indicates if the space in the persistent storage facility is allocated to application for data files going from the SES 101 to the PES 104 or for data files going from the PES 104 to the SES 101.

[0050] The data storage interface 609 uses the configuration parameters retrieved from the application configuration storage facility 603 to (i) control the storage in persistent storage facilities of data files received from the SES 101 and from the PES 104 and (ii) retrieve data files destined for the SES 101 and for the PES 104 from persistent storage facilities.

[0051] SES DCM interface 610 communicates with the SES DCM 202 through the data transport interface 602 and controls the data exchanges between the data transport interface 602 and the data storage interface 609 based on the configuration parameters stored in the application configuration storage 603 and on the control data received from the SES DCM 202. The data exchanges include (i) the inbound transfer of data files received from the SES 101 and destined for the PES 104 and (ii) the outbound transfer of data files received from the PES 104 on their way to the SES 101. [0052] PES DCM interface 611 communicates with the PES DCM 203 through the data transport interface 602 and controls the data exchanges between the data transport interface 602 and the data storage interface 609 based on the configuration parameters stored in the application configuration storage facility 603 and on the control data received from the PES DCM 203. The data exchanges include (i) the inbound transfer of data files received from the PES 104 and destined for the SES 101 and (ii) the outbound transfer of data files received from the SES 101 on their way to the PES 104.

[0053] FIG. 7 depicts a flowchart describing a method of operation for the SES DCM, according to embodiments as disclosed herein. At the beginning of the process the configuration interface 401 makes (701) a check with the data transport interface 402 for new configuration data. In case new configuration data have arrived, the configuration interface 401 uses (707) the new data to update the pertinent application data set in application configuration storage facility 403 and process returns to step 701. On the other hand, if new configuration data have not arrived at the data transport interface 402, the add-on module DCM interface 412 checks (702) with the data storage interface 411 if new application data have been stored in any of the storage areas allocated to the applications whose configuration is maintained in the application configuration storage 403. If new application data are found, then add-on module DCM interface 412 instructs the data storage interface 411 to mark (708) the new data as pending. Control then passes to step 703. [0054] If new application data are not found in step 702, the add-on module DCM 412 interface 306 checks (703) with the data storage interface 308 if there are any pending data in the storage area allocated to the applications whose configuration is maintained in application configuration storage 403. If there are no pending data, a check (704) is made by add-on module DCM interface 412 if the add-on module 102 has any data pending for transfer to the SES 101. If the add-on module 102 has no data pending for transfer to the SES 101 the control returns to step 701.

[0055] In case the add-on module DCM interface 412 finds pending data in the allocated storage area, then the add-on module DCM interface 412 contacts (709) the add-on module DCM 201 to verify if the pending data found are required to be transferred to the add-on module 102. In the next step, a check is made (710) if add-on module DCM interface 412 does not receive confirmation that the pending data must be transferred to the add-on module 102. If no confirmation is obtained the control returns to step 701. In case the add-on module DCM interface 412 receives confirmation that the pending data must be transferred to the add-on module 102, the add-on module DCM interface 412 initiates (711) the transfer from the SES 101 to the add-on module 102. After the transfer from the SES 101 to the add-on module 102 terminates (712), the data storage interface 411 removes (713) the portion of the data that was successfully transferred to the add-on module 102 from the allocated storage area. Control then returns to step 701. Further, in step 704, if the add-on module DCM interface 412 finds that there are pending data in the add-on module 102, the add-on module DCM 201 initiates (705) the transfer of the pending data from the add-on module 102 to the SES 101. After the transfer from the add-on module 102 to the SES 101 ends, the process of transfer is terminated (706), and control returns to 701. The various actions in the method of FIG. 7 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 7 may be omitted.

[0056] FIG. 8 depicts a flowchart describing a method of operation for the PES DCM, according to embodiments as disclosed herein. A check (801) is made to determine if new configuration data have arrived in the storage area. In case new configuration data have arrived, the configuration interface 501 uses (807) the new data to update the pertinent application data set in application configuration storage 503. If new configuration data have not arrived, the add-on module DCM interface 513 checks (802) with the data storage interface 408 if new application data have been stored in any of the storage areas allocated to the applications whose configuration is maintained in the application configuration storage facility 503. If new application data are found, the add-on module DCM interface 513 starts (808) a time count to track the aging of the new application data. Control then passes to step (803).

[0057] Further, if new application data are not found, the add-on module DCM 513 checks (803) if any data request has arrived from the add-on module 102. If no data request has arrived from the add-on module 102, the add-on module DCM interface 513 checks (804) if a notification of new data availability has arrived from the add-on module 102. If a data request from the add-on module 102 is found in step 803 or if a notification for new data availability from the add-on module 102 is found in step 804, the add-on module DCM interface 513 contacts the add-on module DCM 202 to verify (809) if a transfer in either direction between the PES 104 and the add-on module 102 is needed.

[0058] A check (810) is made if a confirmation for transfer is obtained. If add-on module DCM interface 513 does not receive confirmation that a transfer is needed, then control returns to step 801. If the add-on module DCM interface 513 receives confirmation that the pending data must be transferred to the add-on module 102, then add-on module DCM interface 513 and the add-on module DCM 201 initiate (811) the transfer from the PES 104 to the add-on module 102 or from the add-on module 102 to the PES 104. After the data transfer is complete, the process terminates (812) and control returns to step 801.

[0059] On the other hand, if in step 804 add-on module DCM interface 513 finds that no notification is obtained for the availability of new data from the add-on module 102, the add-on module DCM interface 513 checks (805) if any of the aging timeouts associated with data stored in the allocated storage areas has expired. In case the add-on module DCM interface 513 finds that no timer has expired, the control returns to step 801. On the other hand, in case the add-on module DCM interface 513 finds an expired timer, the data storage interface 512 removes (806) the associated data from the corresponding storage area. Control then returns to step 801. The various actions in the method of FIG. 8 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 8 may be omitted.

[0060] FIG. 9a, 9b depicts a flowchart describing a method of operation for add-on module DCM, according to embodiments as disclosed herein. At the beginning of the process a check (901) is made if any new configuration data have arrived. In case new configuration data have arrived, the configuration interface 601 uses the new data to update (907) the pertinent application data set in application configuration storage facility 603. The control then returns to step 901. If new configuration data are not present, the data storage interface 609 checks (902) if new application data have been stored in any of the storage areas allocated to the applications whose configuration is maintained in the application configuration storage 603. If new application data are found, the data storage interface 609 marks (912) the new application data as pending. Control then passes to step 903.

[0061] Further, PES DCM interface 611 checks (903) with the data storage interface 609 if there are any pending data that are destined for the PES 104. If pending data destined for the PES 104 are found, the PES DCM interface 611 contacts the PES DCM 203 to verify (913) if an outbound transfer of data from the add-on module 102 to the PES 104 must be executed. A check (914) is made if a confirmation is obtained for outbound transfer. If the PES DCM interface 611 does not receive confirmation that an outbound transfer is needed, then control returns to step 901. On the other hand, if the PES DCM interface 611 receives confirmation that the pending data must be transferred to the PES 104, the PES DCM interface 611 and the PES DCM 203 initiate (915) the transfer from the add-on module 102 to the PES 104. After the data are transferred, the outbound transfer is terminated (916). Further, the PES DCM interface 611 instructs the data storage interface 609 to remove (917) the transferred data from the storage area allocated to the corresponding application. Control then returns to step (901).

[0062] The add-on module DCM 201 checks (904) for any pending data for the SES 101. If the add-on module DCM 201 does not find pending data destined for the SES 101, control passes to step 905, where the PES DCM interface 611 checks if a notification for new data availability has arrived from the PES 104. If a notification for new data availability from the PES DCM 203 is found, the PES DCM interface 611 contacts the PES DCM 203 to verify (908) if an inbound transfer from the PES 104 to the add-on module 102 is indeed needed. Further, a check (909) is made if inbound transfer is confirmed with the source. If in step 909 the PES DCM interface 611 does not receive confirmation that an inbound transfer is needed, control returns to step 901. On the other hand, if the PES DCM interface 611 receives confirmation that data waiting in the PES 104 must be transferred to the add-on module 102, the PES DCM interface 611 and the PES DCM 203 initiate (910) the transfer from the PES 104 to the addon module 102. After the data transfer terminates (911) control returns to step 901. [0063] If in step 905 it is determined that no notification for new data availability has arrived from the PES 104, control passes to step 906, where the SES DCM interface 610 checks if a notification for new data availability has arrived from the SES 101. If a notification for new data availability from the SES 101 is found, the SES DCM interface 610 contacts the SES DCM 202 to verify (908) if an inbound transfer from the SES 101 to the add-on module 102 is needed. The SES DCM interface 610 checks (909) if a confirmation is received. If the SES DCM interface 610 does not receive confirmation that an inbound transfer is needed then control returns to step 901. In case the SES DCM interface 610 receives confirmation that data waiting in the SES 101 must be transferred to the add-on module 102, the SES DCM interface 610 and the SES DCM 202 initiate (910) the transfer from the SES 101 to the add-on module 102. After the transfer is complete (911) the control returns to step 901. The various actions in the method of FIG. 9 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 9 may be omitted.

[0064] 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 FIGs. 1, 2, 3, 4, 5 and 6 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0065] The embodiment disclosed herein specifies a system for expediting the transfer of data files in packet networks. The mechanism allows expedition of transfer of data files by providing a system thereof. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means containing program code means 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 hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof, e.g. one processor and two FPGAs. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. 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 and/or at least one software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. The device may also include only software means. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.

[0066] 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

CLAIMS What is claimed is:

1. A communication system for expediting the transfer of data files between two end systems in a packet switching network, said system comprising:

a Persistent End System (PES);

a Sporadic End System (SES); and

an add-on module connected to said SES, said add-on module comprising at least one means configured for:

checking availability of data files at said PES on availability of a network path between said PES and said add-on module, regardless of the status of said SES;

fetching said data files from said PES, if data files are available at said PES;

storing said data files in a storage area present in said add-on module; and

transferring said data files to said SES when said SES is powered on and capable of operation.

2. The communication system, as claimed in claim 1, wherein said add-on module further comprises at least one means configured for

checking availability of data files at said SES on availability of said SES, regardless of the availability of a network path between said add-on module and said PES;

fetching said data files from said SES, if data files are available at said SES;

storing said data files in a storage area present in said add-on module; and transferring said data files to said PES when a working network path between said add-on module and said PES becomes available.

3. The communication system, as claimed in claim 1, wherein said add-on module is configured to connect to said SES using a Universal Serial Bus (USB) connection.

4. The communication system, as claimed in claim 1, wherein said add-on module is configured to connect to said SES using a Personal Computer Memory Card International Association (PCMCIA) connection.

5. The communication system, as claimed in claim 2, wherein said PES further comprises of a Dedicated Computing Module (DCM) configured for handling data file transfers between said PES and said add-on module independent of said SES being powered on;

verifying the availability of new data files at said add-on module; and

advertising the availability of new data files at said PES.

6. The communication system, as claimed in claim 2, wherein a Dedicated Computing Module (DCM) in said add-on module is configured for

handling data files transfers between said add-on module and said PES independent of said SES being powered on; and

handling data files transfer between said add-on module and said SES independent of network connectivity between said add-on module and said PES;

verifying the availability of a new data files at said PES;

advertising the availability of said new data files at said PES to said

SES;

verifying the availability of new data files at said SES; and advertising the availability of said new data files at said SES to said

PES.

7. The communication system, as claimed in claim 2, wherein a Dedicated Computing Module (DCM) in said SES is configured for

handling data file transfers between said add-on module and said SES independent of network connectivity between said add-on module and said PES;

verifying availability of a new data files at said add-on module; and advertising the availability of new data files to said add-on module.

8. An add-on module for expediting data file transfers in a communication system, said add-on module being connected to a Sporadic End System (SES) and further comprising at least one means configured for

checking availability of new data files at a Persistent End System (PES) on availability of a network path between said PES and said add-on module, regardless of the status of said SES;

fetching said new data files from said PES, if new data files are available at said PES;

storing said new data files in a storage area present in said add-on module; and

transferring said new data files to said SES when said SES is powered on and capable of operation.

9. The add-on module, as claimed in claim 8, wherein said add-on module is configured to connect to said SES using a Universal Serial Bus (USB) connection.

10. The add-on module, as claimed in claim 8, wherein said add-on module is configured to connect to said SES using a Personal Computer Memory Card International Association (PCMCIA) connection.

11. The add-on module, as claimed in claim 8, wherein said storage means in said add-on module is any one of a buffer, a Random Access Memory (RAM), or a flash memory device.

12. The add-on module, as claimed in claim 8, wherein a Dedicated Computing Module (DCM) in said add-on module is configured for

handling data file transfers between said add-on module and said PES independent of said SES being powered on; and

handling data file transfers between said add-on module and said SES independent of network connectivity between said add-on module and said PES.;

verifying the availability of new data files at said PES;

advertising the availability of said new data files at said PES to said

SES;

PES.

13. A method for expediting the transfer of data files between a Persistent End System (PES) and a Sporadic End System (PES) in a packet switching network, said method comprising steps of

an add-on module checking availability of data files on said PES on availability of a network path between said PES and said add-on module, wherein said add-on module is connected to said SES and regardless of status of said SES; said add-on module fetching said data files from said PES, if data files are available at said PES;

said add-on module storing said data files in a storage area present in said add-on module; and

said add-on module transferring said data files to said SES when said SES is powered on and capable of operation.

14. The method, as claimed in claim 13, wherein said method comprises steps of

said add-on module checking availability of data files on said SES when said SES is powered on and capable of operation and regardless of network connectivity between said add-on module and said PES;

said add-on module fetching said data files from said SES, if data files are available at said SES;

said add-on module transferring said data files to said PES when network connectivity is available between said add-on module and said PES.

15. The method, as claimed in claim 13, wherein said add-on module is connected to said SES using a Universal Serial Bus (USB) connection.

16. The method, as claimed in claim 13, wherein said add-on module is connected to said SES using a Personal Computer Memory Card International Association (PCMCIA) connection.