WO2003036579A2 - System, method and device for data transfer - Google Patents

Abstract

The invention concerns a data transfer system, dedicated to distribution and comprising: a transmission machine (6) using a first main application (65); a reception machine (4) using a second main application (45); and means for automatically transferring data to be transferred derived from the first main application of the transmission machine to the reception machine; the automatic transfer means including: in the transmission machine, a transmission buffer (66); in the first main application, means for writing in the transmission buffer data to be transferred; and a transfer application (67) separate from the main application and itself comprising means for reading data stored in the transmission buffer and means for transfer to the reception machine.

Description

 Data transfer system, method and device.

The present invention relates to the field of data transfer used and managed by entities for the distribution of goods and / or services (such as for example points of sale, warehouses, ...) and more specifically to data transfer distributed on several machines.

Traditionally, in a network comprising several independent machines processing information, there are communication needs between the machines and communication incidents between these machines can alter their main information processing activity, which is not linked the transfer of this information to other machines.

Thus, commercial entities have one or more sales channels, notably stores, e-commerce websites and / or mail-order entities. The management of data relating to each point of sale, (for example orders, stocks, inputs / outputs of each point of sale) is often distributed or even centralized. This centralization is done at one or more levels and requires means of communication between the different parts of the management system. For example, a supermarket includes several cash registers for collecting customer payments. Each cash register accounts for sales and sends all of its sales data to a central cash register, which in particular makes it possible to manage store stocks. This operation is carried out by a main application mainly responsible for accounting for each customer's purchases and also managing the transfer of sales data to the central cash register. However, for various reasons (communication line cut, occupancy of the transmission channel, central cash register faulty, etc.), the transfer of data to the central cash register may be slowed down or blocked, thus resulting in slowing or blocking of the application and therefore accounting for purchases at each checkout (also creating a reduction in sales and longer waiting times at checkouts).

When several points of sale are managed centrally, the same problem occurs again. Thus, if several central cash registers are linked to the same management center, the inventory management application charged to each central cash register may be slowed down or blocked because a data transfer is poor between the central cash register and the management center.

One drawback of this prior art technique is that blocking or slowing down the transfer of data results in a blocking or slowing down of the main application of a point of sale (for example, a shop cashier or a cash register central store). Thus, a transfer task is likely to handicap the proper functioning of the main task, which can in particular be blocked or slowed down in the event of a transfer incident.

Another drawback of this technique of the prior art is its lack of flexibility.

Another known approach of client-server type consists in having the data transfer carried out at the request of a server which scans the various entities generating data in order to retrieve them. This approach is not satisfactory, especially when the entities generating data are numerous (case, for example, of a chain of stores, of large size). Indeed, a major drawback of this technique is that it is relatively heavy to implement and that there is a collapse of performance as soon as the load becomes too high.

The invention according to its different aspects aims in particular to overcome these drawbacks of the prior art.

More specifically, an objective of the invention is to provide a system and a method for transferring data used and managed by entities for the distribution of goods and / or services (for example from points of sale) which do not block or do not slow down or, more generally, do not interfere with the elements a data management system, the main application of which is not data transfer.

Another objective of the invention is to implement a system for transferring this data, which is very reliable and simple to implement. The invention also aims to provide flexibility of use.

The invention also aims to optimize the overall management of data, especially in the field of distribution (in particular the sale and / or storage of goods and / or supplies of services).

The invention further aims to avoid any blockage of a management system of a distribution network, being linked to the malfunction of a communication link in one or more links of a distribution chain.

The invention also aims to avoid any loss of data in a distribution system

These objectives and others which will appear subsequently are achieved according to the invention, using a data transfer system, said system being of the type dedicated to one or more goods distribution entities and / or of services and comprising at least one basic structure itself comprising:

- a transmitting machine implementing a first main application;

- a receiving machine implementing a second main application and connected to the transmitting machine by at least one transmission network; and

means for automatic transfer of data from the first main application and said data to be transferred, from the sending machine to the receiving machine; remarkable in that the automatic transfer means include:

- in the transmitting machine, a buffer transmission memory;

- In the first main application, means for writing, in the buffer transmission memory, data to be transferred; and a transfer application distinct from the main application and itself comprising means for reading the data stored in the buffer transmission memory and means for transfer to the receiving machine. Note that the main applications are, for example, data processing applications. The data from a main application are in particular data generated and / or received by the main application.

We also note that here, the transmitting and receiving machines are taken in a very broad sense and do not include only the machines dedicated to trade. Likewise, the data does not necessarily come from points of sale.

We also note that the term “network” is understood in a broad sense: it can be a link, a local network element or not, a bus between two remote machines belonging or not to a same site.

It is further noted that by definition, the buffer transmission memory contains only the data to be transferred. The buffer transmission memory can in particular be implemented in the form of a memory type component as such, but also of a particular memory area in a component or of a portion of hard disk or of support. data storage.

According to a particular characteristic, the system is remarkable in that the automatic transfer means further comprise:

- in the receiving machine, a buffer reception memory intended to receive the data transmitted by the transfer means to the receiving machine;

- In the means of transfer to the receiving machine, means for writing to the buffer reception memory; and

- In the second main application, means for reading, in the buffer reception memory, the data received. According to a particular characteristic, the system is remarkable in that the transfer application itself comprises transfer triggering means according to a mode belonging to the group:

- real time # l: - planned; and

- sets off.

It is noted that the “real time” mode is a mode allowing a very fast reaction time, H is particularly preferred in the case where the communications between the enietrix and receiver machine are at a low fixed cost, even zero (case, for example , where the link is local or specialized). The “real time” mode is implemented, by definition, as soon as new data is ready for a transfer.

The planned mode is advantageous when, in particular, the link (for example, of the ISDN type) is chargeable. According to this mode, a data transfer is planned for words costed in advance, for example during the week or fixed hours, which is relatively simple to manage.

Triggered mode provides flexibility of use, for example, when the transmitting machines are used at unusual conditions or at times. It is implemented in particular by human intervention and / or by an external device (for example, application generating a cookie at the end of the store closing operation, so as to be sure that all the data will be transferred to the receiving machine, in particular in the event that the store is closed beyond the last scheduled time).

According to a particular characteristic, the system is remarkable in that the transfer application further comprises means for verifying that the data to be transferred have been correctly transferred to the receiving machine.

According to a particular characteristic, the system is remarkable in that the writing means write the data in the form of at least one file in the buffer reception memory and that the verification means include means for renaming the files within the receiving memory.

This verification is relatively simple to implement and effective. It can be considered that the file or files transferred are correctly written in the reception memory if and only if the renaming of the file or files transferred is carried out correctly.

According to a particular characteristic, the system is remarkable in that the transfer application further comprises means for erasing from the transmission buffer memory, data which has been correctly transferred to the receiving machine.

According to a particular characteristic, the system is remarkable in that the transfer application is implemented in the transmitting machine.

It should be noted that, according to this characteristic, while being implemented in the transmitting machine and forming an inseparable whole, the transfer application uses means specific to the receiving machine, in particular the means necessary for reserving a memory location and writing data to the receiving machine (memory, management means specific to the operating system of the receiving machine, etc.).

This characteristic is particularly advantageous as opposed to an implementation:

- in a third party machine which adds a potentially disruptive element; and

- to the implementation in the receiving machine which must regularly scan the transmission memory without guarantee of having data to transfer (the link between the machines and the resources of the receiving machine can thus be unnecessarily busy and, if necessary incur unnecessary costs). According to a particular characteristic, the system is remarkable in that the transfer application is implemented in the receiving machine. It should be noted that, according to this characteristic, while being implemented in the receiving machine and forming an inseparable whole, the transfer application uses means specific to the sending machine, in particular the means necessary for reading and erasing. data in the sending machine (memory, management means specific to the operating system of the sending machine, ...).

According to a particular characteristic, the system is remarkable in that the transfer application is implemented in a remote machine distinct from the transmitting machine and the receiving machine. It is noted that, according to this characteristic, while being implemented in a remote machine and forming an inseparable whole, the transfer application uses means specific to the transmitting and receiving machines, in particular the means necessary for reading and erasure of data in the transmitting machine as well as the means necessary for reserving a memory location and for writing data in the receiving machine.

According to a particular characteristic, the system is remarkable in that the transmitting machine and / or the receiving machine belong to the group comprising: the store cases; - store management centers; mail order management centers; and e-commerce management centers. According to a particular characteristic, the system is remarkable in that it comprises several basic structures in parallel and / or cascaded. We note that two cascaded basic structures include:

- a first transmitting machine (belonging to the first basic structure);

a second machine both receiving data from the first transmitting machine (this first receiving machine therefore belonging to the first basic structure) and transmitting (this machine which is second transmitting machine therefore also belonging to the second basic structure); and

- a third machine (belonging to the second basic structure) receiving data from the second machine. We also note that two basic structures in parallel include:

- a first transmitting machine (belonging to the first basic structure);

- a second transmitting machine (belonging to the second basic structure); and - a third receiving machine (belonging to both the first and the second basic structure).

In the latter case, the various means (in particular, where appropriate, buffer reception memory and main application reading the data) may be common to the two structures or separated in whole or in part. In a preferred embodiment, there is, in each receiving machine, a buffer reception memory associated with each transmitting machine, while there is only one main application in charge of reading all the memories of buffer reception.

Of course, the invention can be implemented according to numerous architectures, for example: in a system with two hierarchy levels (a single basic structure or several basic structures in parallel);

- in a system with more than two levels with at each level a single machine (the basic structure is simply cascaded); or - in a system with more than two levels, each level comprising one or more machines (the basic structure is both cascaded and paralleled).

It is also noted that the machines in the different structures can be similar (for example, the transmitting machines can all be store cases) or very different (for example, the transmitting machines may be store cash registers while others are computers for managing an e-commerce site).

It is further noted that the sending machine and the receiving machine can be one and the same machine, and that, in this case, the sending application, the transfer application and the receiving application coexist.

The invention also relates to a data transfer method, said method being of the type dedicated to one or more entities for the distribution of goods and / or services and comprising steps of automatic transfer of data, called data to be transferred, from a sending machine to a receiving machine:

- the transmitting machine implementing a first main application;

- the receiving machine implementing a second main application and being connected to the transmitting machine by at least one transmission network; and

- the data to be transferred coming from the first main application; remarkable in that the automatic transfer steps include:

- steps for writing to a buffer transmission memory present in the sending machine, data to be transferred, the writing steps being implemented in the first main application; and

steps for reading the data stored in the buffer transmission memory and steps for transferring to the receiving machine, the steps for reading and transferring being implemented in a transfer application distinct from the main application.

The invention also relates to a data transfer device, said device being of the type dedicated to one or more entities for the distribution of goods and / or services, implementing a first main application and comprising means for automatic data transfer, say data to be transferred from the main application, to a receiving machine connected to the transmitting device by at least one transmission network, remarkable in that the transfer means include:

- a buffer transmission memory; - In the first main application, means for writing, in the buffer transmission memory, data to be transferred; and

a transfer application distinct from the main application and itself comprising means for reading the data stored in the buffer transmission memory and means for transfer to the receiving machine.

The invention further relates to a computer program comprising program code instructions for executing the steps of the data transfer method when the program is executed on a computer.

The invention also relates to a computer program product comprising program code instructions recorded on a medium usable in a computer, said computer program product being of the type dedicated to one or more entities for the distribution of goods and / or services and comprising computer-readable programming means for performing automatic data transfer steps, called data to be transferred from a transmitting machine to a receiving machine: -

- the transmitting machine implementing a first main application;

- the receiving machine implementing a second main application and being connected to the transmitting machine by at least one transmission network; and

- the data to be transferred coming from the first main application; automatic transfer steps including:

- steps for writing to a buffer transmission memory present in the sending machine, data to be transferred, the steps of writing being implemented in the first main application; and

- steps for reading the data stored in the buffer transmission memory and steps for transferring to the receiving machine, the steps for reading and transferring to the receiving machine being implemented in a transfer application separate from the application main.

The advantages of the method and of the transfer device as well as of the computer programs are the same as those of the data transfer system, they are not described in more detail.

Other characteristics and advantages of the invention will appear more clearly on reading the following description of a preferred embodiment, given by way of simple illustrative and nonlimiting example, and of the appended drawings, among which: - the figure 1 presents a data management system, in accordance with the invention according to a particular embodiment;

- Figure 2 illustrates more precisely the main applications and data transfer applications implemented within the elements illustrated in Figure 1; FIG. 3 describes a data transmission algorithm, implemented in transfer applications illustrated in FIG. 2.

The general principle of the invention therefore consists in providing distributed management means with data transfer, implementing a buffer memory mechanism on transmission, combined with the use of a dedicated transfer application external to the main application. In this way, any situation of blocking and / or slowing down of the main application is avoided since, within the framework of the transfer of data, the main application is content to write data in a hosted buffer transmission memory, also by the transmitting machine. It is up to the transfer application to read the information present in the transmission memory and to transfer it to a receiving machine, and preferably in a non-volatile reception memory present in this receiving machine. The invention applied to commercial management is thus based, for example, on the separation of the main sales applications and applications dedicated to the transfer of data from the main applications.

More specifically, a transmitting machine (for example, a cash register) has a main application or function which in particular generates or retrieves sales data and which, in order to transfer the data to a receiving machine (for example, a central cash register), simply stores the data to be transmitted in a buffer transmission memory.

Thus, even if the transfer of data between the transmission memory and the receiving machine is slowed down or blocked, this in no way affects the proper functioning of the main application which is, according to the example, sales.

In addition, in general, the mechanism may be cascaded. Thus, the receiving machine can itself have a transmission memory. The data to be transmitted which can be received or generated by the receiving machine are transferred very simply by an application from the receiving machine to its buffer transmission memory. A dedicated application then takes care of transferring the data from the transmission memory of the receiving machine to a second receiving machine (for example, a central server).

The mechanism can also be parallelized. Thus, two transmitting machines can transfer data to the same receiving machine. Referring to FIG. 1, an embodiment of a system for managing data from points of sale is presented.

This system with three hierarchical levels of machines notably includes:

- a central server 2; - store servers 3, 4, 5; and - boxes 6, 7 and 8.

The central server 2 is connected to the store servers 3, 4, 5 by links 9, 10 and 11 respectively. These links are communications links allowing the transfer of data between each store server and the central server. These are, for example, ISDN type links (or

Integrated Service Digital Network), “Frame Relay”, and / or specialized.

Note that the central server is distant from the store servers.

According to a first variant, the central server and some or all of the store servers are on the same site (the links connecting them are then, for example, of the Ethernet local area network type).

Each store server 3, 4 or 5 is connected to one or more cash registers.

Thus, the store server 4 is connected to the boxes 6, 7, 8 by respectively

Reasons 12, 13 and 14. These links are communications links allowing the transfer of data between the boxes 6, 7, 8 and the store server 4. These are, for example, local network links.

Note that the store server and the cash registers are on the same site and in different machines.

According to a second variant (which may possibly be combined with the first variant), the central server and some or all of the store servers are on remote sites (the links connecting them are then, for example, of the ISDN type, "Frame Relay" and / or specialized) or, on the contrary, on the same machine (the links connecting them are then, for example, bus type links internal to the machine).

FIG. 2 illustrates more precisely the main applications and the data transfer applications implemented within the central server 2, the store servers 3, 4 and 5 and the cash registers 6, 7, 8.

The boxes 6, 7 and 8 are very similar and, for the sake of clarity, only the box 6 will be described more precisely.

Box 6 comprises several elements, in particular a microprocessor, memories and a man-machine interface (for example in the form of a screen and keyboard). Each of the elements illustrated in Figure 2 is well known to those skilled in the art. These common elements are not described here.

It is observed that the word "memory" used throughout the description designates in each of the memories mentioned, both a low-capacity memory zone (some binary data) and a large-capacity memory zone (allowing the storage of a program or file integer).

The box 6 includes in particular a local data processing memory Mem-Box 64 and a data transfer memory

Caisse-TX 66, the two memories being distinct, the distinction being able to be physical (separate components) and / or logical (the address areas being different).

Note that the Cash-TX 66 memory is preferably non-volatile so that important data is not lost in the event, in particular, of interruption of the operation of the cash register 6. This memory is for example made up of a magnetic support of the type floppy disk or disk, a rewritable CD-ROM type optical medium, or a Flash-EEPROM type memory (seen as a writable shared resource).

The microprocessor in box 6 runs two separate applications:

- a main data processing application 65 (for example, cash collection, accounting of goods sold, etc.) which is necessary for the smooth running of sales to a customer; and

- a transfer application 67. The main application 65 uses:

- the Mem-Caisse 64 memory for its processing tasks; and - the Cash-TX memory 66 to allow the transmission of data that the cash register 6 must transfer to the store server 4 on which it depends.

Thus, as soon as the main application 65 must transmit information to the store server 4, it places this information in the Cash-TX memory

66 without worrying about its actual emission. In this way, if the broadcast is disrupted for any reason, the main application continues to operate normally.

The transfer application 67 is responsible for transferring the data stored in the Caisse-TX memory 66 by the main application 65 to the store server 4. The transfer application 67 operates according to the transfer algorithm described opposite Figure 3.

The store servers 3, 4 and 5 are very similar and, for the sake of clarity, only the server 4 will be described more precisely.

The server 4 notably comprises a microprocessor, memories and a man-machine interface (for example in the form of a screen and a keyboard).

The server 4 includes in particular:

- a local data processing memory Mem-Mag 44;

- Mag-RXl 41, Mag-RX2 42 and Mag-RX343 reception memories associated with boxes 6, 7 and 8 respectively; and - a Mag-TX 6 data transfer memory.

The memories are distinct, the distinction being able to be physical (separate components) and / or logical (the address areas being different).

Note that the Mag-RXl 41, Mag-RX2 42 and Mag-RX3 43 and Mag-TX 46 data transfer memories are preferably non-volatile so that important data is not lost in the event, in particular, of interruption of the operation of the store server 4. Each of these memories consists for example of a magnetic support of the floppy or disc type, of an optical support of the rewritable CD-ROM type, or of a memory of the Flash-EEPROM type (seen as a writable shared resource).

The microprocessor of the store server 4 runs two separate applications:

a main application 45 for processing data specific to the store (for example, consolidation of the store turnover, computerized reception of goods, inventories, ...) which is necessary for the proper management of the store; and

- a transfer application 47. The main application 45 uses: - the Mem-Mag memory 44 for its processing tasks;

- the Mag-RXl 41, Mag-RX2 42 and Mag-RX343 reception memories for recovering the data from boxes 6, 7 and 8 in order to process them and possibly transfer them to the Mag-TX data transfer memory 46; and the Mag-TX data transfer memory 46 to allow the transmission of data that the store server 4 must transfer to the central server 2 on which it depends (this data being able to come from the reception memories 41, 42, 43 or generated by main application 45). Thus, as soon as the main application 45 has to transmit information to the central server 2, it places this information in the Mag-TX memory 46 without being concerned with its actual transmission. In this way, if the transmission of data to the central server 2 is disturbed for any reason, the main application continues to operate normally. Likewise, the main application 45 is not sensitive to potential disturbances in the transfer of data between the boxes 6, and 8 and the store server 4.

The transfer application 47 is responsible for transferring the data stored in the Mag-TX memory 46 by the main application 45 to the central server 2. The transfer application 47 operates according to the transfer algorithm described with regard to the figure 3.

The central server 2 notably comprises a microprocessor, memories and a man-machine interface (for example in the form of a screen and a keyboard). The central server 2 comprises in particular: - a local data processing memory Mem-SC 24; and

- reception memories SC-RX1 21, SC-RX2 22 and SC-RX3 23 associated respectively with the store servers 3, 4 and 5.

The memories are distinct, the distinction being able to be physical (separate components) and or logical (the address areas being different).

It is noted that the reception memories SC-RX1 21, SC-RX2 22 and SC-RX3 23 are preferably non-volatile so that important data is not lost in the event, in particular, of interruption of the operation of the central server 2. Each of these memories is, for example, made up of a magnetic support of floppy or disc type, of an optical support of rewritable CD-ROM type, or of a memory of Flash-EEPROM type (seen as a writable shared resource ).

The microprocessor of the central server 2 executes a main application 25 for processing data specific to the central server (for example, consolidation of the turnover of the stores, preparation of the restocking of the stores, consultation of the outstanding deliveries of the stores, ...) which is necessary for the proper management of the central server which is in charge of several stores.

The main application 25 uses: the Mem-SC memory 24 for its processing tasks;

- the reception memories SC-RX1 21, SC-RX2 22 and SC-RX3 23 to retrieve the data from the store servers 3, 4 and 5 in order to process them.

Thus, the main application 25 is not sensitive to potential disturbances in the transfer of data between the store servers 3, 4 and 5 and the central server 2.

According to a variant, the transfer applications are executed in the corresponding receiving machine (according to this variant, the application 67 (respectively 47) is executed in the store server 4 (respectively in the central server 2)). According to another variant, the transfer applications are executed in a remote machine connected to the transmitting machine and to the receiving machine.

FIG. 3 describes an algorithm for transmitting data from sales, implemented in transfer applications 47 and 67 illustrated in FIG. 2. During a first step 70 of launching the application, the different variables ( for example, addresses of the transmission memories, etc.) of the transfer application are initialized.

Then, during a step 71, the transfer application loads the configuration parameters (for initialization or update) and waits for a trigger which can be in one of the modes described below depending on configuration parameters.

Three transfer trigger modes, defined by the user and / or by a remote entity (for example, by the central server 2) are possible:

- in real time, by detecting data in the transmission memory;

- scheduled at, for example, agreed times; and or

- triggered in particular on detection of a marker (for example witness file) for example by human intervention or an external device. These data are, according to a preferred embodiment of the invention, organized in the form of one or more files.

Then, during a step 72, the transfer application 67

(respectively 47) cut the file containing all the data to be transferred into N blocks in order to make the operation of the transmitting machine more fluid. Thus, the system is not blocked, because the transfer application is not exclusive. It is noted that the file is present in the buffer transmission zone of the transmitting machine and that it named for example “123.ech”.

Then, during a step 72, the transfer application 67 (respectively

47) reserves an area in the reception memory Mag-RXl 41 (respectively SC-RX2 22) for a transfer of the file under the name "123. $$$" different from the name original "123.ech". The assigned name is coded so that other applications cannot read the file (the transfer application 67 (respectively 47) prohibiting the use of the file by other applications during the transfer).

Then, during a step 73, the transfer application 67 (respectively 47) initializes a counter i to 1.

Then, during a step 74, the transfer application 67 (respectively 47) copies the i ^th data block from the transmission memory 66 (respectively 46) to the associated reception memory 41 (respectively 22). With each block copied, the transfer operation may fail. Also, if during a step 75, the transfer of the file is assumed to have failed and the operating system of the receiving machine returns an error signal, the step 73 is repeated (which means that starts transferring the file again).

Otherwise (the operating system of the receiving machine not having returned an error signal), during a step 76, the counter is incremented by one.

Then, during a test 77 at the end of transfer of the file, the transfer application 67 (respectively 47) determines whether the counter i is strictly greater than the number N of blocks in the file to be transferred. If not, step 74 is repeated.

If so, during a step 78, the transfer application 67 (respectively 47) renames the file under its original name "123.ech".

If this operation fails, there is a doubt, and in this case, the transfer is deemed to have failed and it is started again by repeating step 73. If the operation to rename the file is not accepted by the receiving machine 4 (respectively 2), the writing operation did not go well and the operation 72 is repeated.

If the name change operation is accepted by the receiving machine 4 (respectively 2), the write operation has gone well and during an operation 79, the transfer application 67 (respectively 47) , clears the file “123.ech” transferred from the transmission memory 66 (respectively 46). Thus, the file “123.ech” could be moved from the transmission memory 67 (respectively 47) to the reception memory 41 (respectively 22). Then, operation 71 is repeated. According to a preferred embodiment, the transfer applications are software. Updating the transfer applications or their configuration is then relatively simple to implement, for example from the central server. In fact, the transfer applications are preferably identical in the store servers and the cash registers. It is then possible to download, for example, updates to the store servers and to the cash registers from the central server without any particular intervention.

Of course, the invention is not limited to the embodiments mentioned above.

In particular, the person skilled in the art can make any variant in the architecture of the system. Thus, the number of hierarchical levels can be reduced (we then have, for example, a central server directly associated with transmitting machines generating data to be transferred) or increased (machines similar to the store server then being inserted between the different levels). Likewise, the hierarchical levels are not necessarily homogeneous and, for example, an element of central server type can directly receive data from one or more checkouts as well as from one or more store servers. The architecture of the network is not necessarily tree-like, the invention applying equally well when the network is meshed and includes, for example, loops or redundant links. In addition, the elements of the system themselves can be of different types. Thus, when the invention is applied to sales, the cases can be replaced by in particular internet servers in the case of electronic commerce or order processing machines in the case of mail-order sales. In addition, according to a variant, a transfer application can be hosted by a receiving machine (the receiving machine can then access the transmission memories remotely) or by a third-party machine (links between the third-party machine and, on the one hand, the transmission memory and, on the other hand, the reception memory then having to be established).

It should also be noted that the invention is not limited to data of the sales data type but extends to any type of information processed locally and having to be transferred to another entity, the processing application not to be disturbed by transfer incidents. Thus, the invention can in particular apply to the management of a warehouse, which after each reception (for example, goods from a supplier) or shipment (for example, goods to customers) needs to transmit the IT slip to the central management system. The warehouse can be: - within the company, and therefore connected to the central management system via a local network; or relocated, and therefore connected to the central management system via a remote network (for example of the ISDN, Frame Relay or dedicated link type). The warehouse management application then deposits its data sheets in a transmission memory, the transfer application according to the invention being adapted to the transfer of data from the transmission memory to a reception memory.

The invention also applies to the management of production in distributed workshops, with several work stations per workshop, reporting production data in real time or planned (deferred time). The work stations of the workshops are, for the implementation of the invention, equivalent to cases and each workshop to a store.

It will be noted that the invention can be implemented in a purely material form but that it can also be implemented in the form of a sequence of instructions from a computer program or any form mixing a hardware part and a software part. In the case where the invention is implemented partially or completely in software form, the corresponding sequence of instructions may be stored in a removable storage means (such as for example a floppy disk, a CD-ROM or a DVD-ROM) or no, this storage means being partially or totally readable by a computer or a microprocessor.

Claims

1. Data transfer system, said system being of the type dedicated to one or more entities for the distribution of goods and / or services and comprising at least one basic structure itself comprising: - an emitting machine (6) implementing a first main application (65); - a receiving machine (4) implementing a second main application (45) and connected to said transmitting machine by at least one transmission network (12); and means for automatic transfer of data from said first main application and said data to be transferred, from said transmitting machine to said receiving machine; characterized in that said automatic transfer means comprise: - in said transmitting machine, a buffer transmission memory (66); - In said first main application, means for writing, in said buffer transmission memory, said data to be transferred; and - a transfer application (67) distinct from said first and second main applications and itself comprising means for reading said data stored in said buffer transmission memory and means for transfer to said receiving machine; - in said receiving machine, a buffer reception memory (41) intended to receive the data transmitted by said transfer means to said receiving machine; and - In said transfer means to the receiving machine, means for writing to said buffer reception memory. 2. System according to claim 1, characterized in that said automatic transfer means further comprise in said second application main, means for reading, in said buffer reception memory, the data received. 3. System according to any one of claims 1 and 2, characterized in that said transfer application itself comprises transfer triggering means according to a mode belonging to the group: - real time : - planned; and - sets off. 4. System according to any one of claims 1 to 3, characterized in that said transfer application further comprises verification means (75,78) that the data to be transferred have been correctly transferred to said receiving machine. 5. System according to claim 4 dependent on claim 2, characterized in that said writing means write the data in the form of at least one file in said buffer reception memory and that said verification means comprise means for renaming said files within said reception memory. 6. System according to any one of claims 4 and 5, characterized in that said transfer application further comprises means for erasing (79) of said transmission buffer, data which have been correctly transferred. to said receiving machine. 7. System according to any one of claims 1 to 6, characterized in that said transfer application is implemented in said transmitting machine. 8. System according to any one of claims 1 to 7, characterized in that said transfer application is implemented in said receiving machine. 9. System according to any one of claims 1 to 8, characterized in that said transfer application is implemented in a remote machine separate from said transmitting machine and said receiving machine. 10. System according to any one of claims 1 to 9, characterized in that said transmitting machine and / or said receiving machine belong to the group comprising: store cases; - store management centers; mail order management centers; and e-commerce management centers. 11. System according to any one of claims 1 to 10, characterized in that it comprises several of said basic structures in parallel and / or cascaded. 12. Data transfer method, said method being of the type dedicated to one or more entities for the distribution of goods and / or services and comprising steps for automatic transfer of data, said data to be transferred, from a transmitting machine (6 ) to a receiving machine (4): - said transmitting machine implementing a first main application (65); - said receiving machine implementing a second main application (45) and being connected to said transmitting machine by at least one transmission network (12); and - said data to be transferred coming from said first main application; characterized in that said automatic transfer steps include: - steps for writing in a buffer transmission memory (66) present in said transmitting machine, said data to be transferred, said steps for writing in a buffer transmission memory being implemented in said first main application; steps for reading said data stored in said buffer transmission memory and steps for transferring (74) to said receiving machine, said steps for reading and transferring being implemented in a transfer application separate from said first and second main applications; and - In said steps of transfer to said receiving machine, sub-steps of writing to a buffer reception memory (41) present in said receiving machine and intended to receive the data transmitted in said steps of transfer to said receiving machine. 13. Device (6) for transferring data, said device being of the type dedicated to one or more entities for the distribution of goods and / or services, implementing a first main application (65) and comprising means for automatic transfer of data, said data to be transferred from said main application, to a receiving machine (4) connected to said transmitting device by at least one transmission network (12), characterized in that said automatic transfer means comprise: - a buffer transmission memory (66); - In said first main application, means for writing, in said buffer transmission memory, said data to be transferred; - a transfer application (67) distinct from said first and second main applications and itself comprising means for reading said data stored in said buffer transmission memory and means for transfer to said receiving machine; - in said receiving machine, a buffer reception memory (41) intended to receive the data transmitted by said transfer means to said receiving machine; and - In said transfer means to the receiving machine, means for writing to said buffer reception memory. 14. A computer program comprising program code instructions for executing the steps of the data transfer method according to claim 12 when said program is executed on a computer. 15. Computer program product comprising program code instructions recorded on a medium usable in a computer, said product computer program being of the type dedicated to one or more entities for the distribution of goods and / or services and comprising programming means readable by computer for performing steps of automatic transfer of data, said data to be transferred from a transmitting machine to a receiving machine: - said transmitting machine implementing a first main application; - said receiving machine implementing a second main application and being connected to said transmitting machine by at least one transmission network; and - said data to be transferred being from said first main application; said automatic transfer steps comprising: - steps for writing in a buffer transmission memory present in said transmitting machine, said data to be transferred, said writing steps being implemented in said first main application; and - steps for reading said data stored in said buffer transmission memory and steps for transferring to said receiving machine, said steps for reading and transferring being implemented in a transfer application distinct from said first and second main applications; and - In said steps of transfer to said receiving machine, sub-steps of writing to a buffer reception memory (41) present in said receiving machine and intended to receive the data transmitted in said steps of transfer to said receiving machine.