Abstract: A vending machine module (12) is pre-programmed with a unique serial number. It is also programmed to dial up and connect to a specific registration database when first installed and powered up in the vending machine (1) which is one example of a remote embedded application. When the vending machine module (12) dials up the registration database for the first time, the registration database identifies the specific module (12) by means of its unique serial number, and then programs the module (12) with all of its relevant customised configuration—such as, for example, Telnet and PTP passwords, PTP Public Encryption Keys, telephone numbers for local ISP access (local telephone rates), customer name, customised web pages, new user configuration, subsequent database IP addresses, etc. Having been programmed with all of this data, the vending machine (12) is then ready to dial up an ISP server (2) over the Internet, for file transfer sessions.

Abstract: In a communications system, a computer network server (2) is arranged to communicate simultaneously with a plurality of remote computers 201 . . . 20n. A remote embedded application in the form of a vending machine (1) has a module (12) that is arranged to communicate with the computer network server (2) such that file transfer sessions are carried out between the server and the vending machine (1). The server (2) is arranged to cause call request data to be transmitted to the module (12) and the module (12) is arranged to initiate a call back to the server (2) or other designated server, in response to the call request data. The call request data is transmitted using calling line identification (CLI). The module (12) is arranged to detect the call and the CLI; to not answer the call; and to initiate a call back to the server (2) or other designated server, after having received the call with CLI.

Abstract: Data transfer occurs between an ISP database (21) and a vending machine database (11), via respective controllers (22 and 121). TCP ports and sockets (e.g. Telnet) (125, 126) at the module controller (121) and (225, 226) at the database controller (22) are used to establish separate CONTROL and CLEAR channels. The CONTROL channel provides end-to-end control information between the remote module controller (121) and the database controller (22), whilst the CLEAR channel is available to exchange pure end-to-end data.