EP1346541B1 - Procede et systeme de communications avec des applications integrees distantes - Google Patents

Procede et systeme de communications avec des applications integrees distantes Download PDF

Info

Publication number
EP1346541B1
EP1346541B1 EP01974457A EP01974457A EP1346541B1 EP 1346541 B1 EP1346541 B1 EP 1346541B1 EP 01974457 A EP01974457 A EP 01974457A EP 01974457 A EP01974457 A EP 01974457A EP 1346541 B1 EP1346541 B1 EP 1346541B1
Authority
EP
European Patent Office
Prior art keywords
server
controller
embedded application
remote
file transfer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP01974457A
Other languages
German (de)
English (en)
Other versions
EP1346541A1 (fr
Inventor
Stephen Craig Whitehead
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Amscreen Group Ltd
Original Assignee
Amscreen Group Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Amscreen Group Ltd filed Critical Amscreen Group Ltd
Publication of EP1346541A1 publication Critical patent/EP1346541A1/fr
Application granted granted Critical
Publication of EP1346541B1 publication Critical patent/EP1346541B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0442—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption

Definitions

  • This invention relates to communications with remote embedded applications.
  • remote embedded application means any remote process or device which operates under the control of a local controller (e.g. microprocessor), and has a requirement to exchange data with a central site from time to time.
  • a local controller e.g. microprocessor
  • a vending machine One example (of many) of a remote embedded application is a vending machine. These days, a vending machine will typically operate under local microprocessor control. However, in order to monitor such data as status, performance and/or stock levels in a vending machine, it is common practice for a communications link to be provided between the remote vending machine and a central site. In this way, the central site can communicate with the vending machine and maintain a check on its status, performance, stock levels, etc.
  • such a vending machine will have an intelligent communications module (which may be part of the microprocessor of the vending machine).
  • a module will be programmed to dial up a specific central site (or connect via a non dial-up link, e.g. Ethernet) in the event of a reportable condition arising at the vending machine, or at predetermined periodic intervals.
  • the communications module has to be programmed with specific data as to how to establish a communications link with the central site, and also how to exchange data with the central site. In short, this requires a certain amount of intelligence in the communications module within the vending machine, together with a certain amount of setting up of the module, which will generally be specific to each machine.
  • Preferred embodiments of the present invention aim to provide communications modules and communications techniques which may be generally improved in the foregoing respects, affording significantly simpler communications control requirements at the remote embedded application, and providing relatively cheap communication between the remote embedded application and a central site.
  • US Patent 5,778,368 discloses a communications system comprising a computer network server which is arranged to communicate simultaneously with a plurality of remote computers. Its aim is to provide a central repository of Real-Time Embedded Software, so that human developers can readily locate and take advantage of software that has already been created.
  • a communications system comprising a computer network server which is arranged to communicate simultaneously with a plurality of remote computers; and a remote embedded application having a controller which is arranged to communicate with said computer network server such that file transfer sessions are carried out between said computer network server and said remote embedded application:
  • said database is provided by said computer network server.
  • said controller communicates with said server via a modem at said remote embedded application.
  • said controller communicates with said server via a global computer network.
  • said global computer network comprises the Internet.
  • each said file transfer session is a File Transfer Protocol (FTP) session.
  • FTP File Transfer Protocol
  • said controller is arranged to initiate a connection between said controller and said server and, once that connection is made, said controller exchanges data with said remote embedded application under the control of said server.
  • connection initiated between said module and said server is by way of a simple terminal emulation session.
  • said simple terminal emulation is byway of Telnet protocol.
  • said server is arranged to look up ID data in response to a connection initiated by said controller and use that ID data to establish a file transfer session with said remote embedded application.
  • said server is arranged to transmit to said remote embedded application during each said file transfer session a new public encryption key such that, for each subsequent file transfer session, said server communicates with said controller using the new public encryption key that was transmitted to said remote embedded application during a previous file transfer session.
  • said server logs on to said controller using the new public encryption key that was transmitted to said remote embedded application during the immediately previous file transfer session.
  • said server is arranged to transmit to said remote embedded application, prior to at least an initial file transfer session, real time clock data in order to synchronise a clock local to said controller with a clock local to said server or another reference clock which is used by said server, thereby to synchronise date and time data as between said server and said remote embedded application.
  • Said controller may be arranged to transmit said real time clock data to said remote embedded application during only an initial set up procedure of said controller.
  • Said server may be arranged to transmit said real time clock data to said controller prior to each said file transfer session after x prior file transfer sessions, where x is 1 or greater than 1.
  • Said server may be arranged to compare the local time at said controller with the local time at said server and to make a decision, based on the result of that comparison, whether to transmit real time clock data to said remote embedded application, thereby to synchronise date and time data as between said server and said remote embedded application.
  • said computer network server and said remote embedded application are comprised in a system in accordance with any of the preceding aspects of the invention.
  • FIG. 1 illustrates a remote embedded application, in the form of a vending machine 1, which is arranged to communicate with a central site, in the form of an Internet Service Provider (ISP) Server 2, over the Internet.
  • ISP Internet Service Provider
  • the vending machine 1 incorporates an intelligent controller 10 which controls the normal functions of the vending machine 1 and also maintains a local database 11 which maintains a record of various parameters at the vending machine 1 - e.g. current operating status, performance, stock levels, currency levels, etc. (Some applications may have more than one controller such as 10 to perform and/or control different functions but, for simplicity, reference is made here just to one controller 10, it being well understood by those skilled in the art that this may represent a plurality of controllers.)
  • the vending machine 1 also incorporates a communications module 12 which includes a module controller 121, a modem 122 and i/o ports 123. Although in Figure 1 the module controller 121, modem 122 and i/o ports 123 are shown separately from the vending machine controller 10, any or all could alternatively be integrated with it.
  • the ISP server 2 is in effect a computer network server which is arranged to communicate simultaneously with a plurality of remote computers 201, 202 Vietnamese networkn.
  • the ISP server 2 further comprises a database 21, a controller 22, i/o ports 223, a modem 23 and a clock 24.
  • the modem 23 is shown as within the ISP Server 2 although, in an Internet configuration, the modem 23 may typically be located at a different site than the database 21, as illustrated in Figure 2 , which is described in more detail below.
  • a communications link 3 is provided between the vending machine 1 and the ISP server 2.
  • the communications link 3 may take any suitable form but, in this example, utilises the Internet, which is accessed by both the vending machine 1 and the ISP server 2 via their respective modems 122 and 23. However, it is to be understood that the communications link 3 could take any convenient form, which does not necessarily require the use of a modem such as 122 or 23 at either end of the link. Both hard wired and wireless links may be employed, as may both dial-up and permanent connections (e.g. Ethernet, ADSL, Intranet, WAN, etc.).
  • the module controller 121 When it is desired for the vending machine 1 to communicate with the central database 21, either upon a reportable condition arising at the vending machine 1 or at predetermined periodic intervals, the module controller 121 initiates an Internet dial-up session via the modem 122, and establishes a link with the ISP server 2 (of known IP address). This may be, for example, by way of a Telnet session, with the module controller 121 providing an ID (username/password) to log onto the database 21.
  • ISP server 2 of known IP address
  • the ISP server 2 synchronises a local clock 14 of the vending machine 1 with the clock 24 of the ISP server 2. Updating the local vending machine clock 14 in this way enables any necessary time adjustment at the vending machine 1, to provide more accurate synchronisation as to time and date, as between the vending machine 1 and the ISP server database 21.
  • the clock 14 of the vending machine 1 may need to be synchronised with the clock 24 of the ISP server 2, only when the module 12 is first installed and powered up (see below).
  • the communications link 3 having thus been set up, the ISP server 2 establishes an FTP (File Transfer Protocol) session back to the vending machine module 12, which is set up to operate as an FTP Server.
  • FTP File Transfer Protocol
  • the ISP server 2 looks up from the database 21 an appropriate ID (username/password) for the particular vending machine module 12, to establish the FTP session.
  • the ISP server 2 takes control of any necessary exchange of files with the vending machine module 12. It is important to appreciate that, in order to establish such an FTP session, it has not been necessary for the ISP server 2 to initiate a call to the remote embedded application of the vending machine 1. On the contrary, it is the vending machine 1 that has initiated the call. But once the initial (e.g.) Telnet session has been set up, the ISP server 2 then takes over and sets up the FTP session.
  • control of the exchange of files in the FTP session between the database 21 and the vending machine module 12 rests entirely with the ISP server 2, substantially all intelligence and control may remain at the ISP server 2, with the vending machine module 12 having only minimal requirements.
  • This arrangement provides substantial flexibility, since "decision making" software need not be embedded in the remote module 12. This allows for much simpler software upgrades to the system. In most case, software upgrades can be accomplished entirely by a single operation at the ISP server 2, rather than at many remote modules such as 12. The absence or minimisation of decision-making software at the remote unit 12 minimises code downloads when new decisions need to be made.
  • the remote unit 12 can request the database server 2 for certain actions - for example, download a specific file. However, the database server 2 can override any requests due to other events - for example, if a PC user (see below) has requested a specific function which takes priority.
  • files can be exchanged between the ISP server database 21 and the vending machine database 11 as necessary.
  • latest vending machine prices may be downloaded from the ISP server database 21 to the vending machine database 11, when the time and date stamping of files indicates that the files at the vending machine 1 require updating.
  • the ISP server database 21, under the control of controller 22, will automatically upload the latest collected data files from the vending machine 1 - for example, vending machine stock levels, currency levels, etc.
  • File transfers may take place in response to requests from the module 12 (or a remote computer 201, 2027-820n) - for example, in response to a flag set at the module 12 (or remote computer) to indicate a file transfer request.
  • the ISP server 2 can then teardown the FTP session.
  • the modem access may typically be more distributed than shown in Figure 1 .
  • the remote module 12 connects with an ISP modem server 23a, which provides a local point of presence, and communicates over the Internet 30 with database server 2a, which contains database 21, controller 22 and clock 24.
  • the clock could be local to the database 21 as shown, or derived from another clock source on the Internet network - e.g. an atomic clock source.
  • remote computer 201 (202...20n) connects with another ISP modem server 23b, which provides another local point of presence, and communicates over the Internet 30 with database server 2a.
  • the modems and Remote Access Servers of Figure 2 can be dispensed with and the various components permanently connected, e.g. by way of an Ethernet or Intranet configuration.
  • Either or both of the remote module 12 and remote computer could have respective databases which are either local or remotely connected over the network
  • the structure of the ISP server 2 is such as to facilitate the look up of Public Encryption Keys, which will be different for the Telnet and FTP sessions.
  • the Telnet Public Key will be a key which is common to the ISP server 2, which typically will service a large number of embedded applications, such as the vending machine 1.
  • the FTP Public Key can be unique to the vending machine module 12. The latter feature enables a particularly advantageous encryption method, which combines simplicity with high security. This operates as follows.
  • the ISP server 2 can send to the vending machine module 12 a new Public Encryption Key for the next FTP session on the next call from the vending machine module 12.
  • a new FTP session is initiated by the ISP server 2
  • Figure 4 is a simple flow chart to illustrate the above-described method of establishing a file transfer session between remote embedded application 1 and ISP Server 2, with dynamic Public Key assignment.
  • step 41 an event occurs to trigger a connection request between vending machine 1 and ISP Server 2. For example, this may be due to a particular event arising at the vending machine 1, or to a particular time event arising, which requires a routine connection to the ISP Server 2.
  • step 42 the communications module 12 dials up the respective Internet Service Provider and, in step 43, logs on to the ISP Server 2 with appropriate ID, by way of a Telnet session.
  • step 44 the ISP Server 2 looks up the ID received in the initial Telnet session, in order to identify the particular communications module 12. In step 44, the ISP Server 2 logs on to the communications module 12 to establish an FTP session, using the FTP Public Key as sent to the module 12 during the last file transfer session.
  • step 46 file transfer proceeds between the ISP database 21 and the remote application database 11, under control of the ISP Server 2 and, during that file transfer process or at the end of it, the ISP Server 2 sends, in step 47, a new Public Encryption Key to the module 12 for the next FTP session.
  • the ISP Server 2 terminates the FTP session in step 48.
  • Another preferred and advantageous feature of the illustrated communications system concerns the procedure for first installing the vending machine module 12.
  • the vending machine module 12 When installed, the vending machine module 12 is 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. In other words, as a new item of equipment, the vending machine module 12 requires only minimal programming. Many similar modules 12 can be programmed in almost exactly the same way with almost exactly the same information, each differing only in its own, unique serial number.
  • 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 FTP passwords, FTP 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 the ISP server 2 over the communications link 3, as described above, for regular Telnet/FTP sessions.
  • the installation process for the vending machine module 12 is substantially automated.
  • the initial registration procedure can include an initial clock synchronisation step between a central clock such as 24 and the clock 14 of the module 12.
  • the registration procedure for the remote module 12 is carried out in just the same way as the above-described ISP server access - that is an initial Telnet session followed by an FTP session. This is a real benefit of centralised decision-making as described above.
  • the remote module 12 purely has files transferred through it. It does not need to know whether these are configuration files, as in the case of initial registration, or whether they are data files for normal operation.
  • the registration database could be totally separate from the usual "application" database 21, or it could actually be the same database.
  • FIG. 5 is a simple flow diagram to illustrate the steps in the above-described registration procedure.
  • step 51 the communications module 12 is installed in the remote embedded application 1 and, in step 52, it is powered up for the first time.
  • the communications module 12 dials up the registration database and in step 54 logs on to it with its predetermined ID which, as described above, may be its unique serial number, in order to establish a Telnet session.
  • step 55 the registration database looks up the ID supplied from the module 12 in order to identify the particular module and then, in step 56, it synchronises its own local clock (or the clock that it uses) with that of the module 12.
  • step 57 the registration database logs on to the communications module 12 to establish an FTP session and, in step 58, it transfers the necessary set up and configuration files to the module 12. When all of this is completed, the registration database terminates the FTP session in step 59.
  • the ISP server 2 also provides Internet service for a large number of remote computers 201, 202....20n which, so far as the ISP server 2 is concerned, will typically be connected as PC Browsers.
  • a user on remote computer 201 subject to submission of appropriate ID (username/password), can gain access to the database 21 and therefore obtain information as to the current state of the vending machine 1 at the last time a dial up session was established between the vending machine 1 and the ISP server 2. This might be regarded as a "snapshot" in time of the status of the vending machine 1.
  • an owner of a number of vending machines (or other embedded applications) can view their status conveniently via the database 21, over a relatively cheap and simple Internet connection via the ISP server 2.
  • the user of remote computer 201 can look directly at the vending machine 1. This operates as follows.
  • the user of computer 201 can cause the ISP server to dial up the vending machine module 12, which is provided with Calling Line Identification (CLI) Service, to indicate to the called module 12 the identity of the calling party.
  • the ISP server 2 will cause the vending machine modem 122 to be called for one or more ring periods (or for a predetermined time, particularly if the CLI comes before the first ring, such that no-ring calls can be supported).
  • the communications module 12 detects from the CLI that the ISP server 2 has called, and is programmed not to answer the call. However, the communications module 12 is programmed to dial back after a short duration to establish a Telnet session (generally as described above) with the ISP server 2, which then in turn establishes an FTP session with the communications module 12, also generally as described above.
  • the ISP server 2 connects the remote computer 201 directly with the vending machine 1, via the communications module 12. This enables the user of remote computer 201 to view the data in the remote embedded application in real time, and optionally, exchange data files with it and/or the ISP server 2.
  • remote computer 201 (202....20n) can dial up and view any desired remote embedded application at will, using a communications link established over the Internet.
  • CLI the CLI
  • the dynamically assigned IP address of the remote module 12 is captured at the database 21 and forwarded to the remote computer 201.
  • This allows the remote computer 201 to browse the module 12 directly, since the module has its own embedded web server. Therefore, this provides a mechanism for the remote computer 201 to interrogate the remote module 12 in real time. So far as the remote module 12 is concerned, it has had a request to synchronise with the database 21, using Telnet/FTP sessions.
  • the database controller 22 can make the appropriate decisions as to whether to transfer files and/or "connect" the remote computer 201 to the remote module 12. For example, the remote computer 201 may update some configuration at the database 21, request that this be transferred immediately to the remote module 12, and request that it view the module 12 in real time to see the effect of the configuration changes. This is another significant benefit of centralised decision-making as described above.
  • CLI can be expended such that the ISP server 2 may dial any desired remote embedded application at any desired time, in order to initiate a return call from the communications module 12, to establish a Telnet session followed by a FTP session, generally as described above.
  • the use of CLI is not just reserved for connecting remote computers 201, etc to remote module 12.
  • the remote computer 201 can make changes at the database 21, for one or more remote modules 12.
  • the ISP server 2 could then subsequernly use CLI to request that the remote modules 12 synchronise immediately, rather than waiting for predetermined dial up times.
  • Figure 6 is a simple flow diagram to illustrate the initial steps in establishing a connection between ISP Server 2 and remote application 1 by use of CLI, as described above.
  • a PC e.g. remote computer 201 logs on to the ISP Server 2, to establish a typical web browsing session.
  • the PC requests the ISP Server 2 to connect to the remote embedded application 1 and, in step 63, the ISP Server 2 dials up the module 12 using CLI.
  • the module 12 detects the CLI but does not answer the incoming call. After a predetermined time, the module dials back to the ISP Server 2 in step 65.
  • a file transfer session may be implemented, using techniques as described above, and involving the remote application 1, ISP Server 2 and, optionally, remote computer such as 201. Alternatively or additionally, the remote computer such as 201 may be connected directly to the remote embedded application 1.
  • a direct communication channel could be opened with the remote embedded application 1, thereby allowing real time data to be captured from equipment of the remote embedded application 1, rather than the data as last stored in the local database 11.
  • One way of providing such a channel is described below.
  • Figure 3 illustrates an advantageous option for providing data transfer between the ISP database 21 and the vending machine database 11, via their respective controllers 22 and 121.
  • the modems 23 and 122 are not shown in Figure 3 and, as is evident from the above description, modems are not invariably required anyway, depending upon the kind of network employed.
  • FIG 3 illustrates schematically the use of TCP ports and sockets (e.g. Telnet) 125, 126 at the module controller 121 and 225, 226 at the database controller 22, to establish separate CONTROL and CLEAR channels. These are similar to the D-channel and B-channel in an ISDN environment.
  • 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.
  • the remote module controller 121 may connect to the database controller 22, using the CONTROL channel established between TCP ports and sockets 125 and 225.
  • a data transfer command or request is transmitted between the database controller 22 and the remote module controller 121 (in either direction) to indicate that it is wished to transfer data from the remote database 11 into a file on the ISP database 21.
  • the CLEAR channel is set up between TCP ports and sockets 126 and 226, and data is them streamed over the CLEAR channel to the database controller 22, which captures the data in a file in the database 21.
  • the CONTROL channel between TCP ports and sockets 125 and 225 provides end-to-end control - for example, STOP, START, PAUSE, etc; or can provide remote control commands to attached equipment - e.g. PAN/TILT commands whilst capturing real compressed video images.
  • the above basic mechanism allows the ISP server 2 to act as a kind of "telephone exchange" between remote computers 201, 202, etc and remote embedded applications such as 1 which have no direct human control. It may be particularly advantageous when used in conjunction with the CLI ring back procedure that is described above. It may enable higher levels of service to be provided, which may be similar to telephony environments - for example, automatic divert of a TCP/IP session from the database 21 to remote computer 201, 202, etc - under the control of decision making at the database server 2.
  • vending machine has been conveniently described above as an example of a remote embedded application, it will appreciated that such applications may take very many different forms. As just a few further examples of many, one may also consider fuel level monitoring, utility automatic metering reading, security systems, data logging, electronic point of sale terminal, industrial control, logistic management, domestic appliances, digital tv / set-top boxes and remote telemetry systems.
  • the Internet has been given as one very convenient example, it is to be understood that the ISP server 2 may be replaced by any computer network server which effectively is arranged to communicate simultaneously with a plurality of remote computers, whether on a local, large area, national, international, or global network
  • Embodiments of the invention may be used with advantage in environments which include Internet, Extranet, Intranet, and private or public packet switched or circuit switched networks.
  • the protocols of Telnet and FTP are just examples or many different kinds of protocols that may be utilised.
  • UDP User Datagram Protocol
  • Telnet any file transfer protocol, mechanism or procedure may be used.
  • FTP any standard or proprietary protocol transferred over a TCP or UDP port or socket.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Control Of Vending Devices And Auxiliary Devices For Vending Devices (AREA)
  • Computer And Data Communications (AREA)
  • Hydrogenated Pyridines (AREA)
  • Transition And Organic Metals Composition Catalysts For Addition Polymerization (AREA)
  • Polymers With Sulfur, Phosphorus Or Metals In The Main Chain (AREA)
  • Selective Calling Equipment (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Claims (20)

  1. Système de communication comprenant un serveur (2) de réseau d'ordinateurs conçu pour communiquer simultanément avec une pluralité d'ordinateurs à distance (201), et une application (1) intégrée à distance, ayant un contrôleur (12) conçu pour communiquer avec ledit serveur (2) de réseau d'ordinateurs de façon que les sessions de transfert de fichiers sont réalisées entre ledit serveur (2) de réseau d'ordinateurs et ladite application (1) intégrée à distance ;
    Caractérisé en ce que ledit contrôleur (12) est programmé, lors de l'installation du contrôleur (12) pour établir une communication avec, et s'enregistrer dans, une base de données d'enregistrement centrale, afin de transférer les fichiers de données de ladite base de données à ladite application (1) intégrée à distance, afin d'appliquer une configuration sur mesure audit contrôleur, incluant initialiser et configurer ledit contrôleur (12) pour des sessions subséquentes de transfert de fichiers avec ledit serveur (2) de réseau d'ordinateurs.
  2. Système de communication selon la revendication 1, caractérisé en ce que ladite base de données est fournie par ledit serveur (2) de réseau d'ordinateurs.
  3. Système de communication selon les revendications 1 ou 2, caractérisé en ce que ledit contrôleur (12) communique avec ledit serveur par un modem à ladite application (1) intégrée à distance.
  4. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que ledit contrôleur (12) communique avec ledit serveur par l'intermédiaire d'un réseau global d'ordinateurs (30).
  5. Système de communication selon la revendication 4, caractérisé en ce que ledit réseau global d'ordinateurs (30) comporte l'Internet.
  6. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que ladite session de transfert de fichiers est une session dite (FTP) « File Transfer Protocol ».
  7. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que ledit contrôleur (12) est conçu pour déclencher une connexion (12) entre ledit contrôleur et ledit serveur (2), et une fois que la connexion est réalisée, ledit contrôleur (12) échange des données avec ladite application (1) intégrée à distance sous le contrôle dudit serveur.
  8. Système de communication selon la revendication 7, caractérisé en ce que ladite connexion déclenchée entre ledit module et ledit serveur (2) est réalisé par une simple session d'émulation de terminal.
  9. Système de communication selon la revendication 8, caractérisé en ce que la simple émulation de terminal est réalisée par un protocole Telnet.
  10. Système de communication selon l'une des revendications 7, 8 ou 9, caractérisé en ce que ledit serveur (2) est conçu pour rechercher des données ID en réponse à une connexion déclenchée par ledit contrôleur (12) et utiliser cette donnée ID pour établir une session de transfert de fichiers avec ladite application (1) intégrée à distance.
  11. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que ledit serveur (2) est conçu pour transmettre à ladite application intégrée à distance, lors de chaque transfert de fichiers, une nouvelle clé de cryptage publique, de façon que, pour chaque session de transfert de fichiers subséquentes, ledit serveur communique avec ledit contrôleur (12) en utilisant la nouvelle clé de cryptage publique qui a été transmise à ladite application intégrée à distance, lors d'une session précédente de transfert de fichiers.
  12. Système de communication selon la revendication 11, caractérisé en ce que pour chaque session de transfert de fichiers subséquentes, ledit serveur se connecte sur ledit contrôleur (12) en utilisant la nouvelle clé de cryptage publique qui a été transmise à ladite application intégrée à distance lors de la session immédiatement précédente de transfert de fichiers.
  13. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que ledit serveur (2) est conçu pour transmettre, à ladite application intégrée à distance (1), avant au moins une session de transfert de fichiers initial, des données d'horloge de temps réel afin de synchroniser l'horloge locale audit contrôleur (12), avec une horloge locale au serveur, ou une autre horloge de référence qui est utilisée par ledit serveur (2), pour ainsi synchroniser les données de date et de temps entre ledit serveur (2) et ladite application intégrée à distance (1).
  14. Système de communication selon la revendication 13, caractérisé en ce que ledit contrôleur (12) est conçu pour transmettre lesdites données d'horloge de temps réel à ladite application (1) intégrée à distance durant seulement une procédure d'initialisation initiale dudit contrôleur (12).
  15. Système de communication selon la revendication 13, caractérisé en ce que ledit serveur (2) est conçu pour transmettre lesdites données d'horloge de temps réel audit contrôleur (12), avant chaque session de transfert de fichiers, après x sessions de transfert de fichiers précédentes où x est égal ou supérieur à 1.
  16. Système de communication selon l'une des revendications 13, 14 ou 15,
    caractérisé en ce que ledit serveur (2) es conçu pour comparer ledit temps local audit contrôleur (12) avec le temps local audit serveur (2) et pour réaliser une décision, basée sur le résultat de cette comparaison, pour transmettre ou non lesdites données d'horloge de temps réel à ladite application (1) intégrée à distance, pour ainsi synchroniser les données de temps et de date entre ledit serveur (2) et ladite application (1) intégrée à distance.
  17. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que ladite initialisation et ladite configuration dudit contrôleur (12) incluent l'initialisation et la configuration d'un ou plus du groupe comprenant les mots de passe Telnet et FTP, les clés de cryptage publiques FTP, les numéros de téléphone pour des accès locaux ISP, le nom du client, des pages web sur mesure, une nouvelle configuration d'utilisateur et des adresses IP subséquentes de la base de données.
  18. Système de communication selon l'une des revendications précédentes,
    caractérisé en ce que la communication entre ledit serveur de réseau d'ordinateurs (2), ladite pluralité d'ordinateurs (201) à distance, et ladite application (1) intégrée à distance, est réalisée dans un environnement choisi parmi le groupe comprenant des connexions filaires, des connexions sans fil, Ethernet, Extranet, Intranet, WAN, des réseaux privés, des réseaux publics, des réseaux à commutation par paquets, et des réseaux à commutations par circuit.
  19. Méthode de communication entre un serveur (2) de réseau d'ordinateurs, qui est conçu pour communiquer simultanément avec une pluralité d'ordinateurs à distance (201), et une application intégrée à distance, ayant un contrôleur (12) qui est conçu pour communication avec ledit serveur de réseau d'ordinateurs de façon que des sessions de transfert de fichiers sont réalisées entre ledit serveur (2) de réseau d'ordinateurs et ladite application (1) intégrée à distance, tandis que, lors de l'installation dudit contrôleur (12), ce dernier établit une communication avec et s'enregistre dans, une base de données d'enregistrement centrale, et les fichiers de données sont transférés depuis ladite base de données vers ladite application intégrée à distance, afin d'appliquer une configuration sur mesure audit contrôleur, incluant l'initialisation et la configuration dudit contrôleur (12), pour des sessions de transfert de fichiers subséquentes avec ledit serveur de réseau d'ordinateurs (2).
  20. Méthode de communication selon la revendication 19, caractérisée en ce que ledit serveur de réseau d'ordinateurs et ladite application (1) intégrée sont compris dans un système selon l'une des revendications 1 à 18.
EP01974457A 2000-10-07 2001-10-05 Procede et systeme de communications avec des applications integrees distantes Expired - Lifetime EP1346541B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
GB0024621 2000-10-07
GB0024621A GB2367709B (en) 2000-10-07 2000-10-07 Improvements in or relating to communications
PCT/GB2001/004449 WO2002032075A1 (fr) 2000-10-07 2001-10-05 Procédé et système de communications avec des applications hors site incluses

Publications (2)

Publication Number Publication Date
EP1346541A1 EP1346541A1 (fr) 2003-09-24
EP1346541B1 true EP1346541B1 (fr) 2009-12-16

Family

ID=9900871

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01974457A Expired - Lifetime EP1346541B1 (fr) 2000-10-07 2001-10-05 Procede et systeme de communications avec des applications integrees distantes

Country Status (7)

Country Link
US (1) US8612608B2 (fr)
EP (1) EP1346541B1 (fr)
AT (1) ATE452499T1 (fr)
AU (1) AU2001293972A1 (fr)
DE (1) DE60140820D1 (fr)
GB (1) GB2367709B (fr)
WO (1) WO2002032075A1 (fr)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2367709B (en) * 2000-10-07 2003-05-21 Complementary Tech Ltd Improvements in or relating to communications
GB2367727B (en) * 2000-10-07 2002-10-09 Complementary Tech Ltd Communications with remote embedded applications
WO2004057823A2 (fr) * 2002-12-19 2004-07-08 Sonic Mobility Inc. Procede mandataire et systeme permettant de securiser l'administration sans fil d'entites gerees
US7454785B2 (en) 2002-12-19 2008-11-18 Avocent Huntsville Corporation Proxy method and system for secure wireless administration of managed entities
US7394761B2 (en) 2003-04-29 2008-07-01 Avocent Huntsville Corporation System and method for delivering messages using alternate modes of communication
US7406696B2 (en) 2004-02-24 2008-07-29 Dialogic Corporation System and method for providing user input information to multiple independent, concurrent applications
US7885272B2 (en) * 2004-02-24 2011-02-08 Dialogic Corporation Remote control of device by telephone or other communication devices
US7990998B2 (en) * 2004-12-22 2011-08-02 Qualcomm Incorporated Connection setup using flexible protocol configuration
US8452553B2 (en) 2006-11-30 2013-05-28 Freescale Semiconductor, Inc. Device and method for testing a circuit
US7894370B2 (en) * 2007-03-09 2011-02-22 Nbc Universal, Inc. Media content distribution system and method
US20080219158A1 (en) * 2007-03-09 2008-09-11 Nbc Universal, Inc. Media content distribution system and method
NO20084135A (no) * 2008-09-30 2009-10-12 Rosberg System As Dataenhet og fremgangsmåte for etablering av en nettforbindelse
US9426185B1 (en) * 2013-06-03 2016-08-23 Ayla Networks, Inc. Proximity based communication with embedded system
GB2558876A (en) * 2016-12-02 2018-07-25 Eseye Ltd Provision and retrieval of device status information
US11645029B2 (en) 2018-07-12 2023-05-09 Manufacturing Resources International, Inc. Systems and methods for remotely monitoring electronic displays
US10908863B2 (en) 2018-07-12 2021-02-02 Manufacturing Resources International, Inc. System and method for providing access to co-located operations data for an electronic display
US10860726B2 (en) * 2018-12-12 2020-12-08 American Express Travel Related Peer-to-peer confidential document exchange
US11402940B2 (en) 2019-02-25 2022-08-02 Manufacturing Resources International, Inc. Monitoring the status of a touchscreen
US11921010B2 (en) 2021-07-28 2024-03-05 Manufacturing Resources International, Inc. Display assemblies with differential pressure sensors
US11965804B2 (en) 2021-07-28 2024-04-23 Manufacturing Resources International, Inc. Display assemblies with differential pressure sensors
US11972672B1 (en) 2022-10-26 2024-04-30 Manufacturing Resources International, Inc. Display assemblies providing open and unlatched alerts, systems and methods for the same

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5922054A (en) * 1994-08-19 1999-07-13 Canon Kabushiki Kaisha System for managing external applications and files
EP0720412A2 (fr) * 1994-12-27 1996-07-03 AT&T Corp. Architecture de réseau pour kiosques de télécommunication
US5754830A (en) * 1996-04-01 1998-05-19 Openconnect Systems, Incorporated Server and web browser terminal emulator for persistent connection to a legacy host system and method of operation
US5778368A (en) 1996-05-03 1998-07-07 Telogy Networks, Inc. Real-time embedded software respository with attribute searching apparatus and method
US6523111B1 (en) * 1996-09-09 2003-02-18 International Business Machines Corporation Remote configuration/setup of computer systems operated as embedded controllers without keyboard or video display resources
US5956487A (en) * 1996-10-25 1999-09-21 Hewlett-Packard Company Embedding web access mechanism in an appliance for user interface functions including a web server and web browser
US6150955A (en) * 1996-10-28 2000-11-21 Tracy Corporation Ii Apparatus and method for transmitting data via a digital control channel of a digital wireless network
US6578146B2 (en) * 1996-11-19 2003-06-10 R. Brent Johnson System, method and article of manufacture to remotely configure and utilize an emulated device controller via an encrypted validation communication protocol
US6195694B1 (en) * 1997-03-13 2001-02-27 International Business Machines Corporation Server for reconfiguring control of a subset of devices on one or more kiosks
US6356934B1 (en) * 1997-04-28 2002-03-12 Sabre Inc. Intermediate server having control program for storing content accessed during browsing sessions and playback program for asynchronously replaying browsing sessions
US6338150B1 (en) * 1997-05-13 2002-01-08 Micron Technology, Inc. Diagnostic and managing distributed processor system
US6073172A (en) * 1997-07-14 2000-06-06 Freegate Corporation Initializing and reconfiguring a secure network interface
US7043532B1 (en) * 1998-05-07 2006-05-09 Samsung Electronics Co., Ltd. Method and apparatus for universally accessible command and control information in a network
US6199136B1 (en) * 1998-09-02 2001-03-06 U.S. Philips Corporation Method and apparatus for a low data-rate network to be represented on and controllable by high data-rate home audio/video interoperability (HAVi) network
US7039688B2 (en) * 1998-11-12 2006-05-02 Ricoh Co., Ltd. Method and apparatus for automatic network configuration
US6483906B1 (en) * 1999-01-22 2002-11-19 Pointset Corporation Method and apparatus for setting programmable features of an appliance
US7281036B1 (en) * 1999-04-19 2007-10-09 Cisco Technology, Inc. Method and apparatus for automatic network address assignment
US6345294B1 (en) * 1999-04-19 2002-02-05 Cisco Technology, Inc. Methods and apparatus for remote configuration of an appliance on a network
US6272402B1 (en) * 1999-07-15 2001-08-07 Navistar International Transportation Corp. Remote interface modules with programmable functions
US7783508B2 (en) * 1999-09-20 2010-08-24 Numerex Corp. Method and system for refining vending operations based on wireless data
AU2000240547A1 (en) * 2000-03-31 2001-10-15 Telogy Networks, Inc. Proxy internet browsing
US6754811B1 (en) * 2000-06-16 2004-06-22 International Business Machines Corporation Operating system device centric agent
US7472394B1 (en) * 2000-07-07 2008-12-30 Paymentech, L.P. System and method for programming point of sale devices
GB2367709B (en) * 2000-10-07 2003-05-21 Complementary Tech Ltd Improvements in or relating to communications

Also Published As

Publication number Publication date
US20050262247A1 (en) 2005-11-24
GB2367709B (en) 2003-05-21
AU2001293972A1 (en) 2002-04-22
US8612608B2 (en) 2013-12-17
WO2002032075A1 (fr) 2002-04-18
DE60140820D1 (de) 2010-01-28
GB2367709A (en) 2002-04-10
EP1346541A1 (fr) 2003-09-24
ATE452499T1 (de) 2010-01-15
GB0024621D0 (en) 2000-11-22

Similar Documents

Publication Publication Date Title
EP1346541B1 (fr) Procede et systeme de communications avec des applications integrees distantes
EP1340357B1 (fr) Communications a applications distantes integrees
EP1031220B1 (fr) Appareils et procede de commande d'acces a un service via un systeme de communication
EP1346542B1 (fr) Proc d et syst me de communications avec des applications hors site incluses
US20020178295A1 (en) Distributed gateways for remote management of USB-compatible devices
US6938089B1 (en) Apparatus and method for controlling access to a service over a communications system
CN100391176C (zh) 用于远端更新家用设备功能的方法和系统
US6023724A (en) Apparatus and methods for use therein for an ISDN LAN modem that displays fault information to local hosts through interception of host DNS request messages
US6425000B1 (en) System and method for triggering actions at a host computer by telephone
US6118768A (en) Apparatus and methods for use therein for an ISDN LAN modem utilizing browser-based configuration with adaptation of network parameters
US6094659A (en) Web server for use in a LAN modem
US7688964B2 (en) Communications module for controlling the operation of a private branch exchange
US20080059640A1 (en) Sip Terminal Control System
CN103201689B (zh) 具有嵌入式网络服务器的现场面板及其访问方法
CA2281374C (fr) Interface de securite d'information de ligne pour fournisseur de services tapi
CN110166547A (zh) 终端远程访问控制方法
GB2367708A (en) Communications with remote embedded applications
GB2367726A (en) Encrypted communications with remote embedded applications
GB2369904A (en) Web page, database and program creation
CN201213268Y (zh) 具有监控远端设备的信息服务服务器
KR100365796B1 (ko) 웹서버를 이용한 간이 교환 시스템용 사용자 프로그래밍시스템
KR100939130B1 (ko) 업그레이드 프로토콜 지원 시스템 및 그 방법
US20040054759A1 (en) Method for transferring files between service appliances and a remote management server
KR20030005466A (ko) 아이피 키폰 시스템의 원격 업그레이드 장치 및 방법
JP4522942B2 (ja) 端末設定システム、ＶｏＩＰ端末、及びプログラム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030507

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RIN1 Information on inventor provided before grant (corrected)

Inventor name: WHITEHEAD, STEPHEN, CRAIG

17Q First examination report despatched

Effective date: 20061116

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: AMSCREEN GROUP LIMITED

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAC Information related to communication of intention to grant a patent modified

Free format text: ORIGINAL CODE: EPIDOSCIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

RBV Designated contracting states (corrected)

Designated state(s): AT BE CH CY DE DK ES FI FR GR IE IT LI LU MC NL PT SE TR

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GR IE IT LI LU MC NL PT SE TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60140820

Country of ref document: DE

Date of ref document: 20100128

Kind code of ref document: P

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: NL

Ref legal event code: T3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100416

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100327

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100317

26N No opposition filed

Effective date: 20100917

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101031

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101031

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101005

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20101005

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20091216

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20141031

Year of fee payment: 14

Ref country code: SE

Payment date: 20141030

Year of fee payment: 14

Ref country code: DE

Payment date: 20141030

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20141029

Year of fee payment: 14

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60140820

Country of ref document: DE

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

REG Reference to a national code

Ref country code: NL

Ref legal event code: MM

Effective date: 20151101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160503

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20160630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151102

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151006

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20151101