CA2899404C - Communications management - Google Patents
Communications management Download PDFInfo
- Publication number
- CA2899404C CA2899404C CA2899404A CA2899404A CA2899404C CA 2899404 C CA2899404 C CA 2899404C CA 2899404 A CA2899404 A CA 2899404A CA 2899404 A CA2899404 A CA 2899404A CA 2899404 C CA2899404 C CA 2899404C
- Authority
- CA
- Canada
- Prior art keywords
- application
- server
- component
- client
- emulator
- 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.)
- Active
Links
- 238000004891 communication Methods 0.000 title claims abstract description 85
- 230000002093 peripheral effect Effects 0.000 claims abstract description 170
- 238000000034 method Methods 0.000 claims abstract description 29
- 238000012545 processing Methods 0.000 claims description 8
- 238000013519 translation Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
Abstract
The present invention relates to a system (300) and method for managing communication between a server (100') and peripheral devices (250, 260, 270, 280) associated with at least one client (200) deployed with an airport environment so that a virtualised application (130') running on the server (100') can be connected with at least one of the peripheral devices (250, 260, 270, 280). A communications link (310) is established between the server (100') and the client (200) associated with the peripheral devices (250, 260, 270, 280) and the application (130') is directed to one of the peripheral devices (250, 260, 270, 280) via a virtual channel (320) established between a server peripheral manager simulator component (160) and a client peripheral manager simulator component (245) and passing through the communications link (310). The client peripheral manager simulator (245) is associated with a peripheral manager (240) in the client (200) which controls the peripheral devices (250, 260, 270, 280).
Description
COMMUNICATIONS MANAGEMENT
Field of the Invention The present invention relates to communications management and is more particularly, although not exclusively, concerned with the management of communication between peripheral devices within a virtualised communications system for airports.
Background to the Invention In airport communication systems, a peripheral manager containing device drivers forms part of a client computer system which is geographically local to and is directly connected to one or more peripherals via a local communications system. Such a peripheral manager is constrained in establishing communications with central server-based applications due to the use of non-static internet protocol (IF) addresses and the requirement for IF address translation when the communication needs to traverse networks comprising a mix of public and private addressing schemes.
Within airport environments, workstations (including thin client devices, mobile/tablet devices) and peripheral devices may be shared for multiple airline usage. However, different airlines tend to utilise different systems and a problem arises where the same peripheral devices need to communicate with those different systems. One way of providing such communication requires the adaptation of existing client applications and print emulators to target remote hostnames in conjunction with addressing schemes based on fixed IP addresses.
Field of the Invention The present invention relates to communications management and is more particularly, although not exclusively, concerned with the management of communication between peripheral devices within a virtualised communications system for airports.
Background to the Invention In airport communication systems, a peripheral manager containing device drivers forms part of a client computer system which is geographically local to and is directly connected to one or more peripherals via a local communications system. Such a peripheral manager is constrained in establishing communications with central server-based applications due to the use of non-static internet protocol (IF) addresses and the requirement for IF address translation when the communication needs to traverse networks comprising a mix of public and private addressing schemes.
Within airport environments, workstations (including thin client devices, mobile/tablet devices) and peripheral devices may be shared for multiple airline usage. However, different airlines tend to utilise different systems and a problem arises where the same peripheral devices need to communicate with those different systems. One way of providing such communication requires the adaptation of existing client applications and print emulators to target remote hostnames in conjunction with addressing schemes based on fixed IP addresses.
- 2 -However, this is problematic for a number of reasons, including: the limited availability of public IP addresses; the complexity associated with security, firewalls and mobile data modes where 3G and/or 4G networks are used; the need for many routing configurations that need to be established and effectively managed; and the need to manage multiple stakeholders providing different elements of the communications, for example, airport authorities, network providers, airport information technology providers etc.
US-B-8032353 describes a bridged computer system in which a host computer executes peripheral driver software associated with a remote client computer and communications between the host computer and the remote client is processed using peripheral emulation of an audio codec. Audio signals are communicated between the host and remote computer using network interfaces provided in both the host and the remote computer. In the host computer, an audio interface is provided which connects to a communications network, and, in the remote computer, interfaces are provided for connecting to speakers and a microphone associated with the remote computer. In one embodiment, a peripheral emulator including an audio controller emulator and a codec emulator is provided in the host computer for connecting to the host computer network interface, the peripheral emulator implementing transcoding functions, such as, compression of outbound audio data samples and/or decompression of inbound audio samples. At the remote computer, a link interface is provided which terminates audio links by providing a physical interface, bus transceiver logic and transport layer termination, the link interface transmitting output audio data and commands, receiving input audio data and responses, communicating codec control information to codec modules, distributing a sample clock, executing a power mode state machine, and providing bus reset and initialisation functions. Registers associated with the link interface maintain the configuration states of the codec modules and these
US-B-8032353 describes a bridged computer system in which a host computer executes peripheral driver software associated with a remote client computer and communications between the host computer and the remote client is processed using peripheral emulation of an audio codec. Audio signals are communicated between the host and remote computer using network interfaces provided in both the host and the remote computer. In the host computer, an audio interface is provided which connects to a communications network, and, in the remote computer, interfaces are provided for connecting to speakers and a microphone associated with the remote computer. In one embodiment, a peripheral emulator including an audio controller emulator and a codec emulator is provided in the host computer for connecting to the host computer network interface, the peripheral emulator implementing transcoding functions, such as, compression of outbound audio data samples and/or decompression of inbound audio samples. At the remote computer, a link interface is provided which terminates audio links by providing a physical interface, bus transceiver logic and transport layer termination, the link interface transmitting output audio data and commands, receiving input audio data and responses, communicating codec control information to codec modules, distributing a sample clock, executing a power mode state machine, and providing bus reset and initialisation functions. Registers associated with the link interface maintain the configuration states of the codec modules and these
- 3 -registers are emulated at the host computer so that audio software on the host computer has rapid access to codec state information during driver initialisation or when the remote computer is disconnected. In another embodiment, a peripheral interface including a peripheral emulator in the 5 host computer is connected to the network, and a peripheral controller is provided in the remote computer for controlling a peripheral. The peripheral emulator in this case interacts with the driver software to emulate the interface of the peripheral. The peripheral interface interacts through the network with the peripheral controller within the remote client 10 computer, the peripheral controller comprising a remote driver or other software and/or hardware for coupling to the peripheral.
However, whilst the system described in US-B-8032353 uses peripheral emulation in a peripheral interface in the host computer, interfaces need to be provided on both sides of the communications 15 network to convert the audio signals into and from appropriate data signals for transmittal over the communications network. Whilst this can readily be implemented over a known communications network, it is difficult to implement this over different types of networks where the communications network is not known, and more importantly, where .=
20 several different types of networks need to be negotiated in a single communications link.
In systems where a host computer is required to be in communication with a remote client computer, multiple addressing schemes and translation across heterogeneous local and wide area 25 networks, including mobile carrier networks, are required to enable communications between the host computer and the remote client computer. In this case, it is difficult to establish a reliable link irrespective of the multiple addressing schemes and the different types of networks required for the necessary communication.
= WO
However, whilst the system described in US-B-8032353 uses peripheral emulation in a peripheral interface in the host computer, interfaces need to be provided on both sides of the communications 15 network to convert the audio signals into and from appropriate data signals for transmittal over the communications network. Whilst this can readily be implemented over a known communications network, it is difficult to implement this over different types of networks where the communications network is not known, and more importantly, where .=
20 several different types of networks need to be negotiated in a single communications link.
In systems where a host computer is required to be in communication with a remote client computer, multiple addressing schemes and translation across heterogeneous local and wide area 25 networks, including mobile carrier networks, are required to enable communications between the host computer and the remote client computer. In this case, it is difficult to establish a reliable link irrespective of the multiple addressing schemes and the different types of networks required for the necessary communication.
= WO
- 4 -Summary of the Invention .=
It is therefore an object of the present invention to provide a system and method for virtualising applications between a host computer and at least one remote client computer.
It is another object of the present invention to provide a method for managing the communication of peripheral devices deployed within an airport environment via a virtualised communications protocol.
It is a further object of the present invention to enable virtualised applications running on a server to establish communications with client-based peripheral managers and their associated peripheral devices.
In accordance with a first aspect of the present invention, there is provided a system for operating a peripheral device associated with a client from a server, the system comprising:-a server being configured for running at least one application;
at least one client being configured to be connected to the server via a communications link;
at least one peripheral device associated with each client;
and =
a peripheral manager associated with each client and being configured for controlling each associated peripheral device;
characterised in that the server comprises an application virtualisation platform for virtualising at least one application running thereon; and each client comprises a client virtualisation platform for =
interacting with the application virtualisation platform;
and in that the system further comprises at least one peripheral manager simulator configured to establish a virtual channel through which communication is enabled between at least one =
application running on the server and at least one peripheral device associated with at least one client.
=
=
=
It is therefore an object of the present invention to provide a system and method for virtualising applications between a host computer and at least one remote client computer.
It is another object of the present invention to provide a method for managing the communication of peripheral devices deployed within an airport environment via a virtualised communications protocol.
It is a further object of the present invention to enable virtualised applications running on a server to establish communications with client-based peripheral managers and their associated peripheral devices.
In accordance with a first aspect of the present invention, there is provided a system for operating a peripheral device associated with a client from a server, the system comprising:-a server being configured for running at least one application;
at least one client being configured to be connected to the server via a communications link;
at least one peripheral device associated with each client;
and =
a peripheral manager associated with each client and being configured for controlling each associated peripheral device;
characterised in that the server comprises an application virtualisation platform for virtualising at least one application running thereon; and each client comprises a client virtualisation platform for =
interacting with the application virtualisation platform;
and in that the system further comprises at least one peripheral manager simulator configured to establish a virtual channel through which communication is enabled between at least one =
application running on the server and at least one peripheral device associated with at least one client.
=
=
=
- 5 -Advantageously, the provision of the virtualisation platforms on the server and each client enables applications running on the server to interact with one or more clients at the same time via virtual channels established between each client and the server. This means that the server can be located at any suitable location with the clients located at various remote locations with respect to the server.
In addition, by the establishment of effectively dedicated virtual channels between each client and the server, different applications on the server can be accessed by each client and connected to relevant client-associated peripheral devices without having to compensate for different types of multiple addressing schemes and translation across heterogeneous local and wide area networks, including mobile carrier networks.
Each peripheral manager simulator preferably comprises at least one client peripheral manager simulator component associated with each client and a server peripheral manager simulator component associated with the server, the virtual channel being established between the server peripheral manager simulator component and the client peripheral manager simulator component.
In one embodiment, each server peripheral manager simulator component may be embedded in at least one application on the server. In another embodiment, each server peripheral manager may be connected to at least one application on the server.
Each application may further comprise a peripheral emulator and each server peripheral manager simulator component connects with each application by way of the peripheral emulator.
The system may further comprise an interface provided between the peripheral emulator and the server peripheral manager simulator component. In one embodiment, the interface may comprise a common use passenger processing system.
In addition, by the establishment of effectively dedicated virtual channels between each client and the server, different applications on the server can be accessed by each client and connected to relevant client-associated peripheral devices without having to compensate for different types of multiple addressing schemes and translation across heterogeneous local and wide area networks, including mobile carrier networks.
Each peripheral manager simulator preferably comprises at least one client peripheral manager simulator component associated with each client and a server peripheral manager simulator component associated with the server, the virtual channel being established between the server peripheral manager simulator component and the client peripheral manager simulator component.
In one embodiment, each server peripheral manager simulator component may be embedded in at least one application on the server. In another embodiment, each server peripheral manager may be connected to at least one application on the server.
Each application may further comprise a peripheral emulator and each server peripheral manager simulator component connects with each application by way of the peripheral emulator.
The system may further comprise an interface provided between the peripheral emulator and the server peripheral manager simulator component. In one embodiment, the interface may comprise a common use passenger processing system.
- 6 -In one embodiment, the peripheral emulator may comprise a print emulator and at least one of the peripheral devices connected to at least one client comprises a printer.
The communication link may comprise at least a 3G or a 4G
mobile telecommunications network.
In accordance with another aspect of the present invention, there is provided a method of connecting at least one application on a server to at least one peripheral device associated with at least one client connected to the server, the server having an application virtualisation platform and each client having a client virtualisation platform, the method comprising the steps of:
a) establishing a communications link between the server and at least one client;
b) virtualising communication protocols associated with each client and making the virtualised communications protocols available to the application virtualisation platform on the server; and c) connecting at least one application on the server to at least one client using the client communication protocol;
characterised in that the method further comprises the steps of:-d) establishing a virtual channel between a server peripheral manager simulator component and at least one client peripheral manager simulator component within the communications link;
and e) operating at least one peripheral device associated with at least one client using the established virtual channel between the server peripheral manager simulator component and each client peripheral manager simulator component.
By establishing the virtual channel within the communications link, a reliable connection can be provided between the
The communication link may comprise at least a 3G or a 4G
mobile telecommunications network.
In accordance with another aspect of the present invention, there is provided a method of connecting at least one application on a server to at least one peripheral device associated with at least one client connected to the server, the server having an application virtualisation platform and each client having a client virtualisation platform, the method comprising the steps of:
a) establishing a communications link between the server and at least one client;
b) virtualising communication protocols associated with each client and making the virtualised communications protocols available to the application virtualisation platform on the server; and c) connecting at least one application on the server to at least one client using the client communication protocol;
characterised in that the method further comprises the steps of:-d) establishing a virtual channel between a server peripheral manager simulator component and at least one client peripheral manager simulator component within the communications link;
and e) operating at least one peripheral device associated with at least one client using the established virtual channel between the server peripheral manager simulator component and each client peripheral manager simulator component.
By establishing the virtual channel within the communications link, a reliable connection can be provided between the
- 7 server and each client irrespective of the type(s) of communications network(s) at the locality of the client.
The method may further comprise the step of transferring data from at least one peripheral device connected to a client to the server using the established virtual channel between the client peripheral manager simulator component and the server peripheral manager simulator component.
Brief Description of the Drawinos For a better understanding of the present invention, reference will now be made, by way of example only, to the accompanying drawings in which:-Figure 1 illustrates a block diagram of a server in accordance with the present invention;
Figure 2 is similar to Figure 1 but illustrates another configuration of the server in accordance with the present invention;
Figure 3 illustrates a block diagram of a client in accordance with the present invention;
Figure 4 illustrates a block diagram of a system in accordance with the present invention utilising the server of Figure 2 and the client of Figure 3;
Figure 5 illustrates a block diagram of a system in accordance with the present invention which comprises a server and a plurality of clients; and Figure 6 is a flow chart illustrating the steps of operation of the system shown in Figure 4.
Description of the Invention The present invention will be described with respect to particular embodiments and with reference to certain drawings but the invention is not limited thereto. The drawings described are only
The method may further comprise the step of transferring data from at least one peripheral device connected to a client to the server using the established virtual channel between the client peripheral manager simulator component and the server peripheral manager simulator component.
Brief Description of the Drawinos For a better understanding of the present invention, reference will now be made, by way of example only, to the accompanying drawings in which:-Figure 1 illustrates a block diagram of a server in accordance with the present invention;
Figure 2 is similar to Figure 1 but illustrates another configuration of the server in accordance with the present invention;
Figure 3 illustrates a block diagram of a client in accordance with the present invention;
Figure 4 illustrates a block diagram of a system in accordance with the present invention utilising the server of Figure 2 and the client of Figure 3;
Figure 5 illustrates a block diagram of a system in accordance with the present invention which comprises a server and a plurality of clients; and Figure 6 is a flow chart illustrating the steps of operation of the system shown in Figure 4.
Description of the Invention The present invention will be described with respect to particular embodiments and with reference to certain drawings but the invention is not limited thereto. The drawings described are only
- 8 -schematic and are non-limiting. In the drawings, the size of some of the elements may be exaggerated and not drawn on scale for illustrative purposes.
The term "server" as used herein is intended to include any host computer that can connect to a communications network. In addition, the term "server" is also used to identify elements within the server.
The terms "remote client computer" or "client" as used herein are intended to include any computer or terminal that can connect to a server via a communications network. The term "client" is also used to identify elements within a remote client computer.
The term "emulator" as used herein refers to hardware or software that duplicates (emulates) the functions of a first computer system (for example, a client computer) in a second computer system (for example, a host computer) to provide an exact reproduction of the behaviour of the first computer system.
The term "simulator" as used herein refers to a hardware or software that provides a representation of the operation of a physical system over time using a model representing key characteristics and/or behaviours of the physical system.
The present invention is capable of exploitation by airports and any other parties that are involved in the provision of shared infrastructure to users in airport environments, including but not limited to, use in check-in and boarding areas, baggage claim desks and airline back offices. In addition, the present invention can also be utilised in non-airport environments.
This present invention provides a method for managing the communication with peripheral devices, such as printers, scanners and readers, deployed within an airport environment via a virtualised communications protocol extended over a network. Such a network may comprise of heterogeneous network types, including local area networks
The term "server" as used herein is intended to include any host computer that can connect to a communications network. In addition, the term "server" is also used to identify elements within the server.
The terms "remote client computer" or "client" as used herein are intended to include any computer or terminal that can connect to a server via a communications network. The term "client" is also used to identify elements within a remote client computer.
The term "emulator" as used herein refers to hardware or software that duplicates (emulates) the functions of a first computer system (for example, a client computer) in a second computer system (for example, a host computer) to provide an exact reproduction of the behaviour of the first computer system.
The term "simulator" as used herein refers to a hardware or software that provides a representation of the operation of a physical system over time using a model representing key characteristics and/or behaviours of the physical system.
The present invention is capable of exploitation by airports and any other parties that are involved in the provision of shared infrastructure to users in airport environments, including but not limited to, use in check-in and boarding areas, baggage claim desks and airline back offices. In addition, the present invention can also be utilised in non-airport environments.
This present invention provides a method for managing the communication with peripheral devices, such as printers, scanners and readers, deployed within an airport environment via a virtualised communications protocol extended over a network. Such a network may comprise of heterogeneous network types, including local area networks
9 ' and wide area networks, the latter including fixed networks or 3G/4G
data communications networks. (3G relates to the third generation of mobile communications for mobile telephones and comprises CDMA2000, a family of protocols that use code division multiple access systems, and 5 Universal Mobile Telecommunications System (UMTS). CDMA is also known as International Mobile Telecommunications Multi-Carrier (IMT-MC). 4G relates to the fourth generation which provides mobile ultra-broadband Internet access using, for example, Long Term Evolution (LIE).)
data communications networks. (3G relates to the third generation of mobile communications for mobile telephones and comprises CDMA2000, a family of protocols that use code division multiple access systems, and 5 Universal Mobile Telecommunications System (UMTS). CDMA is also known as International Mobile Telecommunications Multi-Carrier (IMT-MC). 4G relates to the fourth generation which provides mobile ultra-broadband Internet access using, for example, Long Term Evolution (LIE).)
10 In particular, a method will be described which overcomes the challenges associated with communication between a remote central server and peripheral devices associated with airport-based clients where the communication may include multiple addressing schemes and translation across heterogeneous local and wide area networks, including 15 mobile carrier networks. As mentioned above, the present invention can be implemented in any system in which communication is to be established where multiple addressing schemes are needed between a remote central server and a local client and associated peripheral devices.
20 In the system of the present invention, a server is in communication with at least one remote client computer. A peripheral manager simulator simulates a peripheral manager on the server to communicate with a client peripheral manager in each remote client computer. The peripheral manager simulator preferably comprises a 25 server peripheral manager simulator component and a client peripheral manager simulator component between which the virtual channel is established. The server peripheral manager simulator component and the client peripheral manager simulator component work together to simulate application communication from the server to each remote client 30 computer so that the peripheral manager associated with each remote client computer can control the operation of its associated peripheral - -devices. Additionally, the virtual channel can also be used for data transfer between a peripheral device connected to the client and the server. In effect, the virtual channel is bi-directional.
Referring initially to Figure 1, a server 100 in accordance with the present invention is shown which has a server-based application virtualisation platform 110. A plurality of applications 120, 130, 140 are shown running on the server 100 but which are virtualised on the application virtualisation platform 110. An emulator 150, for example, a print emulator, is associated with one particular application 130, for example, a print application. The application 130 interfaces with the print emulator 150 via connection 135 to provide print instructions for a peripheral device, for example, a printer (not shown) located at the location of the client.
In accordance with the present invention, a server peripheral manager simulator component 160 is provided at the server 100, the server peripheral manager simulator component 160 interfacing with the print emulator 150 via connection 155. The operation of the server 100 within the system of the present invention will be described in more detail with reference to Figures 4 to 6 below.
The application virtualisation platform 110 includes software which virtualises the applications 120, 130, 140 or an operation system (not shown) on which each application runs. The server peripheral manager simulator component 160 simulates a peripheral manager (as will be described in more detail below) to enable local communications with the application emulator 150, in this case, the print emulator. A
Common Use Passenger Processing System (CUPPS) or any other suitable interface type may be provided which enables communication between the print emulator and the server peripheral manager simulator component 160. (CUPPS is effectively the next generation of Common Use Terminal Equipment (CUTE) in accordance with IATA
Recommended Practice 1797.)
20 In the system of the present invention, a server is in communication with at least one remote client computer. A peripheral manager simulator simulates a peripheral manager on the server to communicate with a client peripheral manager in each remote client computer. The peripheral manager simulator preferably comprises a 25 server peripheral manager simulator component and a client peripheral manager simulator component between which the virtual channel is established. The server peripheral manager simulator component and the client peripheral manager simulator component work together to simulate application communication from the server to each remote client 30 computer so that the peripheral manager associated with each remote client computer can control the operation of its associated peripheral - -devices. Additionally, the virtual channel can also be used for data transfer between a peripheral device connected to the client and the server. In effect, the virtual channel is bi-directional.
Referring initially to Figure 1, a server 100 in accordance with the present invention is shown which has a server-based application virtualisation platform 110. A plurality of applications 120, 130, 140 are shown running on the server 100 but which are virtualised on the application virtualisation platform 110. An emulator 150, for example, a print emulator, is associated with one particular application 130, for example, a print application. The application 130 interfaces with the print emulator 150 via connection 135 to provide print instructions for a peripheral device, for example, a printer (not shown) located at the location of the client.
In accordance with the present invention, a server peripheral manager simulator component 160 is provided at the server 100, the server peripheral manager simulator component 160 interfacing with the print emulator 150 via connection 155. The operation of the server 100 within the system of the present invention will be described in more detail with reference to Figures 4 to 6 below.
The application virtualisation platform 110 includes software which virtualises the applications 120, 130, 140 or an operation system (not shown) on which each application runs. The server peripheral manager simulator component 160 simulates a peripheral manager (as will be described in more detail below) to enable local communications with the application emulator 150, in this case, the print emulator. A
Common Use Passenger Processing System (CUPPS) or any other suitable interface type may be provided which enables communication between the print emulator and the server peripheral manager simulator component 160. (CUPPS is effectively the next generation of Common Use Terminal Equipment (CUTE) in accordance with IATA
Recommended Practice 1797.)
- 11 -In the embodiment of the server 100 shown in Figure 1, the application emulator 150 (or print emulator) is located within the application virtualisation platform 110. It may be connected to more than one application (not shown) if similar or identical applications are running on the server 100 and which require the same type of application emulation.
In Figure 2, a modified embodiment of the server 100' is shown. Elements which have been described above with reference to Figure 1 have the same reference numerals and will not be described in detail again. In the embodiment of Figure 2, the application virtualisation platform 110' has been modified so that the print emulator 150' forms part of the application 130' itself and interfaces with the server peripheral manager simulator component 160 via connection 155'. In this case, a suitable interface is provided to enable communications between the print (or application) emulator 150' and the server peripheral manager simulator component 160.
In a further embodiment (not shown), the server peripheral manager simulator component may be embedded in the application itself.
In an airport implementation, the server 100 (or 100') is located remotely from the airport itself and is connected thereto by means of conventional communications links. A single server 100 (or 100') may be connected to more than one airport as well as to different areas, for example, check-in, boarding gates, baggage halls and other airport front and/or back offices.
Figure 3 illustrates a client 200 which is connectable to the server 100 (Figure 1) or server 100' (Figure 2) as will be described in more detail below with reference to Figures 4 to 6. The client 200 has a client virtualisation platform 210 which interfaces with a keyboard 220 and a display 230 as shown by respective links 225, 235. Although the keyboard 220 and display 230 are shown as separate elements, they may form part of a single module (not shown). The client 200 also
In Figure 2, a modified embodiment of the server 100' is shown. Elements which have been described above with reference to Figure 1 have the same reference numerals and will not be described in detail again. In the embodiment of Figure 2, the application virtualisation platform 110' has been modified so that the print emulator 150' forms part of the application 130' itself and interfaces with the server peripheral manager simulator component 160 via connection 155'. In this case, a suitable interface is provided to enable communications between the print (or application) emulator 150' and the server peripheral manager simulator component 160.
In a further embodiment (not shown), the server peripheral manager simulator component may be embedded in the application itself.
In an airport implementation, the server 100 (or 100') is located remotely from the airport itself and is connected thereto by means of conventional communications links. A single server 100 (or 100') may be connected to more than one airport as well as to different areas, for example, check-in, boarding gates, baggage halls and other airport front and/or back offices.
Figure 3 illustrates a client 200 which is connectable to the server 100 (Figure 1) or server 100' (Figure 2) as will be described in more detail below with reference to Figures 4 to 6. The client 200 has a client virtualisation platform 210 which interfaces with a keyboard 220 and a display 230 as shown by respective links 225, 235. Although the keyboard 220 and display 230 are shown as separate elements, they may form part of a single module (not shown). The client 200 also
- 12 -includes a peripheral manager 240 which is connected for controlling peripheral devices 250, 260, 270, 280 via link 290. Typical peripheral devices which may be controlled by the peripheral manager 240 include, but are not limited to, printers, scanners, and readers. Whilst link 290 may be a physical link, for example, using a universal serial bus (USB) connection, the link 290 may also be a wireless link forming part of a local area network (LAN) or a wide area network (WAN). It is also possible that the link 290 operates using mobile telecommunications, for example, forming part of a 3G or 4G network or is connected via Bluetooth.
(Bluetooth is a wireless technology standard managed by the Bluetooth Special Interest Group.) In accordance with the present invention, a client peripheral manager simulator component 245 is provided which is associated with the client peripheral manager 240. The client peripheral manager simulator component 245 is used to form a virtual channel (not shown) with the server peripheral manager simulator component 160 (Figures 1 and 2) as will be described in more detail below.
In an airport environment, a plurality of clients 200 would be provided within the airport itself, for example, at check-in desks, at boarding gates, in baggage halls etc. Each client 200 connects to the remote server 100 (or 100') to access applications running on the application virtualisation platform 110 (or 110') provided in the server 100 (or 100') as will be described in more detail below.
In Figure 4, a virtualisation system 300 in accordance with the present invention is shown. The system 300 comprises the server 100' as shown in Figure 2, but it will be appreciated that this is by way of example and the server 100 shown in Figure 1 could also be used.
Elements of the server 100' as described above have the same reference numerals and will not be described in detail again here. The system 300 also includes the client 200 which is connected to the server 100' via a communications link 310. Communications link 310 may comprise a
(Bluetooth is a wireless technology standard managed by the Bluetooth Special Interest Group.) In accordance with the present invention, a client peripheral manager simulator component 245 is provided which is associated with the client peripheral manager 240. The client peripheral manager simulator component 245 is used to form a virtual channel (not shown) with the server peripheral manager simulator component 160 (Figures 1 and 2) as will be described in more detail below.
In an airport environment, a plurality of clients 200 would be provided within the airport itself, for example, at check-in desks, at boarding gates, in baggage halls etc. Each client 200 connects to the remote server 100 (or 100') to access applications running on the application virtualisation platform 110 (or 110') provided in the server 100 (or 100') as will be described in more detail below.
In Figure 4, a virtualisation system 300 in accordance with the present invention is shown. The system 300 comprises the server 100' as shown in Figure 2, but it will be appreciated that this is by way of example and the server 100 shown in Figure 1 could also be used.
Elements of the server 100' as described above have the same reference numerals and will not be described in detail again here. The system 300 also includes the client 200 which is connected to the server 100' via a communications link 310. Communications link 310 may comprise a
- 13 -WAN or a LAN communications system which is capable of running a virtualisation protocol. As shown, the communications link 310 effectively connects the application virtualisation platform 110' to the client virtualisation platform 210. In particular, the communications link 310 comprises an intemet protocol (IP) connection. In one embodiment, the virtualisation protocol utilises Citrix XenServer on the server and Citrix XenApp on each remote client computer to provide the respective virtualisation platforms. (Citrix, XenServer and XenApp are trademarks of Citrix Systems Inc. of Fort Lauderdale, Florida, USA.) However, it will be appreciated that other virtualisation protocols may be used, for example, VMWare, and Citrix applications are given by way of example. (VMWare is a trademark of VMWare Inc. of Palo Alto, California, USA.) In addition, in accordance with the present invention, the communications link 310 effectively connects the server peripheral manager simulator component 160 with the client peripheral manager simulator component 245 forming part of the client peripheral manager 240 using a virtual channel 320 as indicated by dot-dash line as will be described in more detail below.
The client virtualisation platform 210 includes software which allows communications with the server 100 via the application virtualisation platform 110' and manages the delivery of the virtualised application or operating system to the peripheral manager 240 at the client 200. The peripheral manager 240 includes suitable device drivers (not shown) for each peripheral device 250, 260, 270, 280.
The client peripheral simulator component 245 enables communication between the client virtualisation platform 210 and the peripheral manager 240. As shown, the client peripheral manager simulator component 245 can be embedded within the peripheral manager 240. Alternatively, the client peripheral manager simulator component 245 may stand alone within the client 200 (not shown).
The client virtualisation platform 210 includes software which allows communications with the server 100 via the application virtualisation platform 110' and manages the delivery of the virtualised application or operating system to the peripheral manager 240 at the client 200. The peripheral manager 240 includes suitable device drivers (not shown) for each peripheral device 250, 260, 270, 280.
The client peripheral simulator component 245 enables communication between the client virtualisation platform 210 and the peripheral manager 240. As shown, the client peripheral manager simulator component 245 can be embedded within the peripheral manager 240. Alternatively, the client peripheral manager simulator component 245 may stand alone within the client 200 (not shown).
- 14 -In accordance with the present invention, the provision of the server peripheral manager simulator component 160 and the client peripheral manager simulator component 245 enables the virtualisation of the system as will be described below with reference to Figure 6.
Although not shown in Figure 4, it is to be noted that the virtual channel 320 extends through the communications link 310 via the application virtualisation platform 110' and the client virtualisation platform 210.
Figure 5 illustrates a system 400 in which a plurality of clients 2001, 2002, 2003, 2004, ..., 200, are connected to a single server 100. Each client 2001, 2002, 2003, 2004, ..., 200, has its own client virtualisation platform 2101, 2102, 2103, 2104, ..., 210, and own client peripheral manager and client peripheral manager simulator component.
For clarity, only the client peripheral manager 2401 and client peripheral manager simulator component 2451 for one client 2001 is referenced, but it will be appreciated that the other clients also have client peripheral manager and client peripheral manager simulator components as shown.
The server 100 may be located at a central remote location and each client 2001, 2002, 2003, 2004, 200, may be located at any suitable location. For example, clients may be located at one airport or at a plurality of different airports all over the globe. As described above, the clients could also be located at locations, for example, at hotels or conference centres, where passengers can check-in prior to leaving for the airport.
As shown, a communications link 410 may be established between each of the clients 2001, 2002, 2003, 2004, ..., 200, at the same time. A virtual channel 420 is also shown extending between the client peripheral manager simulator component 2451 and the server peripheral manager simulator component 160. Although not shown in Figure 5, it is to be noted that the virtual channel 420 extends through the communications link 410 via the application virtualisation platform 110 and the client virtualisation platform 210.
Although not shown in Figure 4, it is to be noted that the virtual channel 320 extends through the communications link 310 via the application virtualisation platform 110' and the client virtualisation platform 210.
Figure 5 illustrates a system 400 in which a plurality of clients 2001, 2002, 2003, 2004, ..., 200, are connected to a single server 100. Each client 2001, 2002, 2003, 2004, ..., 200, has its own client virtualisation platform 2101, 2102, 2103, 2104, ..., 210, and own client peripheral manager and client peripheral manager simulator component.
For clarity, only the client peripheral manager 2401 and client peripheral manager simulator component 2451 for one client 2001 is referenced, but it will be appreciated that the other clients also have client peripheral manager and client peripheral manager simulator components as shown.
The server 100 may be located at a central remote location and each client 2001, 2002, 2003, 2004, 200, may be located at any suitable location. For example, clients may be located at one airport or at a plurality of different airports all over the globe. As described above, the clients could also be located at locations, for example, at hotels or conference centres, where passengers can check-in prior to leaving for the airport.
As shown, a communications link 410 may be established between each of the clients 2001, 2002, 2003, 2004, ..., 200, at the same time. A virtual channel 420 is also shown extending between the client peripheral manager simulator component 2451 and the server peripheral manager simulator component 160. Although not shown in Figure 5, it is to be noted that the virtual channel 420 extends through the communications link 410 via the application virtualisation platform 110 and the client virtualisation platform 210.
- 15 -Naturally, a virtual channel can also be established for the other client peripheral manager simulator components of each client 2001, 2002, 2003, 2004, ..., 200. Each client 2001, 2002, 2003, 2004, 200n may access the same application at the same time, or alternatively, more than one application may be accessed by the same or different clients. It will be appreciated that each client 2001, 2002, 2003, 2004, 200n accesses the server 100 via its own dedicated virtual channel within the communications link 410, that is, a plurality of virtual channels can be established between the server peripheral manager simulator 160 and each client 2001, 2002, 2003, 2004, ..., 200,-, via the link 410.
By hosting all applications to be used by the clients on a common server, updates need only be applied once on the server without recourse to any of the clients. This reduces the complexity of keeping individual clients running the same application(s) up-to-date. In addition, as different applications can be hosted, in an airport environment, different airlines or other users of the system can use different applications but still use the same remote client computer to access their applications on the server.
In Figure 6, a flow chart 500 illustrating the basic steps of a method for operating the system is shown. Reference numerals relating to elements of the server 100' (Figure 2), the client 200 (Figure 3) and the system 300 (Figure 4) are also used in the following description. The flow chart 500 comprises four basic steps in addition to "start", step 510, and "end", step 560.
In step 510, a user logs onto the client using the keyboard 220 and the display 230 and initiates a session in which the client 200 is connected to the server 100' via communications link 310 (Figure 4). The connection between the client and the server initialises at least one graphic user interface (GUI) for one of more applications on the server 100' by calling the IP address of the server 100'. At the same time, the server peripheral simulator component 160 is also initialised.
By hosting all applications to be used by the clients on a common server, updates need only be applied once on the server without recourse to any of the clients. This reduces the complexity of keeping individual clients running the same application(s) up-to-date. In addition, as different applications can be hosted, in an airport environment, different airlines or other users of the system can use different applications but still use the same remote client computer to access their applications on the server.
In Figure 6, a flow chart 500 illustrating the basic steps of a method for operating the system is shown. Reference numerals relating to elements of the server 100' (Figure 2), the client 200 (Figure 3) and the system 300 (Figure 4) are also used in the following description. The flow chart 500 comprises four basic steps in addition to "start", step 510, and "end", step 560.
In step 510, a user logs onto the client using the keyboard 220 and the display 230 and initiates a session in which the client 200 is connected to the server 100' via communications link 310 (Figure 4). The connection between the client and the server initialises at least one graphic user interface (GUI) for one of more applications on the server 100' by calling the IP address of the server 100'. At the same time, the server peripheral simulator component 160 is also initialised.
- 16 -In step 520, the connection 310 is made between the client virtualisation platform 210 and the application virtualisation platform 110' on the server 100. A connection is established for the session via the virtualisation protocol according to the platform used, for example, using Citrix as described above, provided on the two platforms 110', 210 in step 530. Support for virtual channels within this protocol enables communications with peripherals to be reliably established and which are unaffected by network address translation and blocking due to the presence of firewalls.
In step 540, the client localhost/Transmission Control Protocol (TCP) is virtualised on the client virtualisation platform 210 and made available, via the connection 310 established in step 530, to the application 130' running on the virtualised platform 110' on the server 100'. In step 550, the virtual channel 320 is established between the initialised server peripheral manager simulator component 160 and the client peripheral manager simulator component 245. The application 130' connects to the client localhost/TCP made available on the application virtualisation platform 110' in step 540, is virtualised and redirected via the virtual channel 320 back to the client peripheral manager 240 via the client peripheral manager simulator component 245.
Once the virtual channel 320 is established, all communication between the application 130' and the peripheral device with which it is to communicate is performed via the virtual channel 320, that is, all data is transferred over the virtual channel 320, either from the server 100' to the client 200 or from the client 200 to the server 100'.
The virtual channel 320 can be established regardless of the type(s) of communications network(s) operating within the communications link 310 and effectively provides a channel of direct communication between the application 130' running on the application virtualisation platform 110' and one of the peripheral devices 250, 260, 270, 280 connected to the client 200 via link 290. As described above,
In step 540, the client localhost/Transmission Control Protocol (TCP) is virtualised on the client virtualisation platform 210 and made available, via the connection 310 established in step 530, to the application 130' running on the virtualised platform 110' on the server 100'. In step 550, the virtual channel 320 is established between the initialised server peripheral manager simulator component 160 and the client peripheral manager simulator component 245. The application 130' connects to the client localhost/TCP made available on the application virtualisation platform 110' in step 540, is virtualised and redirected via the virtual channel 320 back to the client peripheral manager 240 via the client peripheral manager simulator component 245.
Once the virtual channel 320 is established, all communication between the application 130' and the peripheral device with which it is to communicate is performed via the virtual channel 320, that is, all data is transferred over the virtual channel 320, either from the server 100' to the client 200 or from the client 200 to the server 100'.
The virtual channel 320 can be established regardless of the type(s) of communications network(s) operating within the communications link 310 and effectively provides a channel of direct communication between the application 130' running on the application virtualisation platform 110' and one of the peripheral devices 250, 260, 270, 280 connected to the client 200 via link 290. As described above,
- 17 -the application 130' may be a print application and the peripheral device connected to the client 200 may be a printer.
Naturally, other functionality may be provided by the peripheral devices, for example, scanning or reading. In this case, the scan or read is passed back from the relevant peripheral device 250,260, 270, 280 via link 290 to the server peripheral manager simulator component 160, via the associated client peripheral manager 240, the client peripheral manager simulator component 245 and the virtual channel 320. From the server peripheral manager simulator component 160, the scan or read is passed to an associated application within the application virtualisation platform 110'. The information relating to the scan or read may then be stored in a database or memory (not shown) if required.
In step 560, the session ends when the connection between the server 100' and the client 200 is terminated when the user logs off the client 200.
As described above, the server peripheral manager simulator component is launched each time the virtualised application is launched, that is, every time a client connects to the server. However, it is also possible to have a single server peripheral manager simulator component which provides a connection port for each instance of the virtualised application being launched on the server in response to the connection of a client with the server. The latter option is not preferred as all connections between clients and the server will be lost if the server peripheral manager simulator needs to be restarted for whatever reason.
A peripheral emulator is described above which is associated with the application on the server which needs to connect to a peripheral device on the client. However, this is not essential and its functionality can be included in the server peripheral manager simulator component.
Naturally, other functionality may be provided by the peripheral devices, for example, scanning or reading. In this case, the scan or read is passed back from the relevant peripheral device 250,260, 270, 280 via link 290 to the server peripheral manager simulator component 160, via the associated client peripheral manager 240, the client peripheral manager simulator component 245 and the virtual channel 320. From the server peripheral manager simulator component 160, the scan or read is passed to an associated application within the application virtualisation platform 110'. The information relating to the scan or read may then be stored in a database or memory (not shown) if required.
In step 560, the session ends when the connection between the server 100' and the client 200 is terminated when the user logs off the client 200.
As described above, the server peripheral manager simulator component is launched each time the virtualised application is launched, that is, every time a client connects to the server. However, it is also possible to have a single server peripheral manager simulator component which provides a connection port for each instance of the virtualised application being launched on the server in response to the connection of a client with the server. The latter option is not preferred as all connections between clients and the server will be lost if the server peripheral manager simulator needs to be restarted for whatever reason.
A peripheral emulator is described above which is associated with the application on the server which needs to connect to a peripheral device on the client. However, this is not essential and its functionality can be included in the server peripheral manager simulator component.
- 18 -Although the present invention has been described with reference to an airport environment in which airport-related applications are run with each client corresponding to a check-in terminal, for example, connected to a single server, it will be appreciated that the present invention can also be used in non-airport environments irrespective of worldwide location, for example, cruise liner terminals, ferry terminals, hotels, resorts and conference centres, that is, any application where multiple clients need to establish a connection with a server to access the same application over a communications link having multiple addressing schemes and translation across heterogeneous local and wide area networks, including mobile carrier networks, to enable communications between applications running on the server and peripheral devices associated with the clients.
=
=
Claims (40)
1. A system for remotely operating a printer, a scanner, or a reader comprising:
a server comprising a first virtualisation platform for virtualising at least one application comprising a print emulator, a scan emulator, or a read emulator;
a client configured to connect to the server via a communications link and comprising a second virtualisation platform for interacting with the first virtualisation platform, wherein the client is associated with the printer, the scanner, or the reader;
a peripheral manager associated with the client and including a device driver configured to control the printer, the scanner, or the reader; and a simulator configured to simulate the peripheral manager including the device driver on the first virtualisation platform and establish a virtual channel through which communication is enabled between the at least one application and the printer, the scanner, or the reader by a common use passenger processing system.
a server comprising a first virtualisation platform for virtualising at least one application comprising a print emulator, a scan emulator, or a read emulator;
a client configured to connect to the server via a communications link and comprising a second virtualisation platform for interacting with the first virtualisation platform, wherein the client is associated with the printer, the scanner, or the reader;
a peripheral manager associated with the client and including a device driver configured to control the printer, the scanner, or the reader; and a simulator configured to simulate the peripheral manager including the device driver on the first virtualisation platform and establish a virtual channel through which communication is enabled between the at least one application and the printer, the scanner, or the reader by a common use passenger processing system.
2. The system of claim 1, wherein the simulator comprises a first component associated with the server and a second component associated with the client, the first component and the second component being configured to simulate the peripheral manager for the first virtualisation platform and the second virtualisation platform respectively, and the virtual channel is established between the first component and the second component.
3. The system of claim 2, wherein the first component is embedded in the at least one application.
4. The system of claim 2, wherein the first component is connected to the at least one application.
5. The system of claim 4, wherein each application comprises an emulator for the printer, the scanner, or the reader, and the first component connects with each application by way of the emulator of the respective application.
6. The system of claim 5, further comprising:
an interface provided between the emulator of each application and the first component.
an interface provided between the emulator of each application and the first component.
7. The system of claim 6, wherein the emulator of each application is the print emulator, and the system remotely operates the printer.
8. The system of claim 5, wherein the emulator of each application is the print emulator, and the system remotely operates the printer.
9. The system of claim 1, wherein the communications link comprises a 3G
mobile telecommunications network.
mobile telecommunications network.
10. The system of claim 1, wherein the communications link comprises a 4G
mobile telecommunications network.
mobile telecommunications network.
11. A method for connecting at least one application on a server to a printer, a scanner, or a reader associated with a client, the server having a first virtualisation platform for virtualising the at least one application comprising a print emulator, a scan emulator, or a read emulator, the client having a second virtualisation platform for interacting with the first virtualisation platform, and the client being associated with a peripheral manager including a device driver configured to control the printer, the scanner, or the reader. the method comprising:
establishing a communications link between the server and the client;
virtualising a communication protocol associated with the client;
making the virtualised communications protocol available to the first virtualisation platform;
connecting the at least one application to the client via the communications protocol;
establishing, by a simulator configured to simulate the peripheral manager including the device driver, a virtual channel through which communication is enabled between the at least one application and the printer, the scanner, or the reader by a common use passenger processing system; and operating the printer, the scanner, or the reader via the common use passenger processing system.
establishing a communications link between the server and the client;
virtualising a communication protocol associated with the client;
making the virtualised communications protocol available to the first virtualisation platform;
connecting the at least one application to the client via the communications protocol;
establishing, by a simulator configured to simulate the peripheral manager including the device driver, a virtual channel through which communication is enabled between the at least one application and the printer, the scanner, or the reader by a common use passenger processing system; and operating the printer, the scanner, or the reader via the common use passenger processing system.
12. The method of claim 11 further comprising:
transferring data from the printer, the scanner, or the reader to the server via the virtual channel.
transferring data from the printer, the scanner, or the reader to the server via the virtual channel.
13. The system of claim 1, wherein the at least one application comprises a plurality of applications, each application being associated with a different airline.
14. The system of claim 13, wherein each application utilizes a different addressing scheme.
15, The system of claim 13, wherein the client is one of a plurality of clients, and the server is configured to launch a plurality of instances of each application, each instance being for a different client
16. The method of claim 11, wherein the simulator comprises a first component associated with the server and a second component associated with the client, the first component and the second component being configured to simulate the peripheral manager for the first virtualisation platform and the second virtualisation platform respectively, and further comprising:
establishing the virtual channel between the first component and the second component.
establishing the virtual channel between the first component and the second component.
17. The method of claim 16, wherein the first component is embedded in the at least one application.
18. The method of claim 16, wherein the first component is connected to the at least one application.
19. The method of claim 18, wherein each application comprises an emulator for the printer, the scanner, or the reader, and the first component connects with each application by way of the emulator of the respective application.
20. The method of claim 19, further comprising:
providing an interface between the emulator of each application and the first component.
providing an interface between the emulator of each application and the first component.
21. A system for remotely operating airport terminals comprising:
a server remote from an airport comprising a first virtualisation platform for virtualising applications associated with multiple airlines, a first application of the applications comprising a first emulator for a peripheral device; and airport terminals communicatively connected to the server, a first airport terminal of the airport terminals communicatively connected to the peripheral device and configured to establish a virtual channel for communication between the first application and the peripheral device by a common use passenger processing system, the first airport terminal comprising:
a second virtualisation platform for interacting with the first virtualisation platform, the second virtualisation platform configured to interface with at least one of a keyboard and display; and a peripheral manager associated with the first airport terminal and including a device driver configured to control the peripheral device.
a server remote from an airport comprising a first virtualisation platform for virtualising applications associated with multiple airlines, a first application of the applications comprising a first emulator for a peripheral device; and airport terminals communicatively connected to the server, a first airport terminal of the airport terminals communicatively connected to the peripheral device and configured to establish a virtual channel for communication between the first application and the peripheral device by a common use passenger processing system, the first airport terminal comprising:
a second virtualisation platform for interacting with the first virtualisation platform, the second virtualisation platform configured to interface with at least one of a keyboard and display; and a peripheral manager associated with the first airport terminal and including a device driver configured to control the peripheral device.
22. The system of claim 21, wherein a first component associated with the server and a second component associated with the first airport terminal, and the virtual channel is established between the first component and the second component.
23. The system of claim 22, wherein the first component is embedded in the first application.
24. The system of claim 22, wherein the first component is connected to the first application.
25. The system of claim 24, wherein each of the applications comprises an application-specific peripheral de-vice emulator, and the first component connects with each of the applications by way of the application-specific peripheral device emulator of the respective application.
26. The system of claim 25, further comprising:
an interface provided between the application-specific peripheral device emulators and the first component.
an interface provided between the application-specific peripheral device emulators and the first component.
27. The system of claim 21, wherein the first emulator is a print emulator, and the peripheral device is a printer.
28. The system of claim 21, wherein the first emulator is a scanner emulator, and the peripheral device is a scanner.
29. The system of claim 21, wherein the first airport terminal is communicatively connected to the peripheral device using a 3G mobile telecommunications network.
30. The system of claim 21, wherein the first airport terminal is communicatively connected to the peripheral device using a 4G mobile telecommunications network.
31. A method for connecting at least one application on a server remote from an airport to a peripheral device of an airport terminal, the server having a first virtualisation platform for virtualising the at least one application, the first virtualisation platform comprising a peripheral device emulator, the airport terminal including a second virtualisation platform for interacting with the first virtualisation platform and a peripheral manager including a device driver configured to control the peripheral device, the second virtualisation platform configured to interface with at least one of a keyboard and display, the method comprising:
establishing a communications link between the server and the airport terminal;
virtualising a communication protocol associated with the airport terminal;
making the virtualised communications protocol available to the first virtualisation platform;
connecting the at least one application to the airport terminal via the virtualised communications protocol;
establishing a virtual channel through which communication is enabled between the at least one application and the peripheral device by a common use passenger processing system; and operating the peripheral device via the common use passenger processing system.
establishing a communications link between the server and the airport terminal;
virtualising a communication protocol associated with the airport terminal;
making the virtualised communications protocol available to the first virtualisation platform;
connecting the at least one application to the airport terminal via the virtualised communications protocol;
establishing a virtual channel through which communication is enabled between the at least one application and the peripheral device by a common use passenger processing system; and operating the peripheral device via the common use passenger processing system.
32. The method of claim 31 further comprising:
transferring data from the peripheral device to the server via the virtual channel.
transferring data from the peripheral device to the server via the virtual channel.
33. The method of claim 31, wherein the at least one application comprises a plurality of applications, each of the applications being associated with a different airline.
34. The method of claim 33, wherein each of the applications utilizes a different addressing scheme.
35. The method of claim 33, wherein the airport terminal is one of a plurality, of airport terminals, and the server is configured to launch a plurality of instances of each of the applications, each instance being for a different airport terminal.
36. The method of claim 31, wherein the virtual channel is established by a first component associated with the server and a second component associated with the airport terminal.
37. The method of claim 36, wherein the first component is embedded in the at least one application.
38. The method of claim 36, wherein the first component is connected to the at least one application.
39. The method of claim 33, wherein each of the applications comprises an application-specific peripheral device emulator for the, and the peripheral device connects with each of the applications by way of the application-specific peripheral device emulator of the respective application.
40. The method of claim 39, further comprising:
providing an interface between the application-specific peripheral device emulator of each of the applications and the peripheral device.
providing an interface between the application-specific peripheral device emulator of each of the applications and the peripheral device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2996140A CA2996140C (en) | 2013-02-01 | 2014-01-31 | Communications management |
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP13305125.0A EP2763037B1 (en) | 2013-02-01 | 2013-02-01 | Communications management |
| US13/756,823 | 2013-02-01 | ||
| US13/756,823 US9141325B2 (en) | 2013-02-01 | 2013-02-01 | Communications management |
| EP13305125.0 | 2013-02-01 | ||
| PCT/EP2014/051969 WO2014118349A1 (en) | 2013-02-01 | 2014-01-31 | Communications management |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2996140A Division CA2996140C (en) | 2013-02-01 | 2014-01-31 | Communications management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2899404A1 CA2899404A1 (en) | 2014-08-07 |
| CA2899404C true CA2899404C (en) | 2018-02-27 |
Family
ID=50029061
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2996140A Active CA2996140C (en) | 2013-02-01 | 2014-01-31 | Communications management |
| CA2899404A Active CA2899404C (en) | 2013-02-01 | 2014-01-31 | Communications management |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2996140A Active CA2996140C (en) | 2013-02-01 | 2014-01-31 | Communications management |
Country Status (3)
| Country | Link |
|---|---|
| AU (1) | AU2014211318B2 (en) |
| CA (2) | CA2996140C (en) |
| WO (1) | WO2014118349A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9986040B2 (en) | 2015-07-21 | 2018-05-29 | Amadeus S.A.S. | Communications management system with a separate peripherals server |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060041651A1 (en) * | 2004-06-16 | 2006-02-23 | Air-Transport It Services, Inc. | Shared airport terminal equipment with peripheral management |
| US8032353B1 (en) | 2007-03-30 | 2011-10-04 | Teradici Corporation | Method and apparatus for providing peripheral connection management in a remote computing environment |
| US8479195B2 (en) * | 2007-05-16 | 2013-07-02 | Vmware, Inc. | Dynamic selection and application of multiple virtualization techniques |
| US20090043921A1 (en) * | 2007-08-09 | 2009-02-12 | Protip Roy | Method and System for Virtualization and Re-Direction of I/O Connections to Peripheral Devices |
| US8521915B2 (en) * | 2009-08-18 | 2013-08-27 | Fusion-Io, Inc. | Communicating between host computers and peripheral resources in an input/output (I/O) virtualization system |
| KR101253560B1 (en) * | 2009-11-05 | 2013-04-11 | 한국전자통신연구원 | System for managing a virtualization solution and Apparatus and Method for managing the same |
| US9015706B2 (en) * | 2010-07-08 | 2015-04-21 | Symantec Corporation | Techniques for interaction with a guest virtual machine |
| US9043754B2 (en) * | 2010-12-28 | 2015-05-26 | Microsoft Corporation | Virtualizing embedded devices |
-
2014
- 2014-01-31 CA CA2996140A patent/CA2996140C/en active Active
- 2014-01-31 WO PCT/EP2014/051969 patent/WO2014118349A1/en active Application Filing
- 2014-01-31 CA CA2899404A patent/CA2899404C/en active Active
- 2014-01-31 AU AU2014211318A patent/AU2014211318B2/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| AU2014211318B2 (en) | 2016-08-04 |
| CA2996140C (en) | 2022-05-24 |
| AU2014211318A1 (en) | 2015-08-13 |
| CA2996140A1 (en) | 2014-08-07 |
| WO2014118349A1 (en) | 2014-08-07 |
| CA2899404A1 (en) | 2014-08-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9141325B2 (en) | Communications management | |
| JP5037016B2 (en) | Network computing system, communication method, image projection apparatus, and image input / output apparatus | |
| US8762544B2 (en) | Selectively communicating data of a peripheral device to plural sending computers | |
| US20070255814A1 (en) | System for server consolidation and mobilization | |
| EP3741100A1 (en) | In-band voice-assistant/concierge for controlling online meetings | |
| US10587713B2 (en) | Proxy for sharing remote desktop sessions | |
| CN104050013B (en) | virtual desktop processing method, device and virtual desktop server | |
| CN106027882A (en) | Redirection method for camera arranged in virtual environment | |
| CN111385238B (en) | Data transmission method and device | |
| CN102118397B (en) | Teleconference communication method and system based on mobile phones | |
| EP3413199B1 (en) | Communications management | |
| CN112187718B (en) | Remote access cloud terminal and system of IDV cloud desktop | |
| CA2899404C (en) | Communications management | |
| CN113891380B (en) | Virtual wireless network processing system and method | |
| EP3319024A1 (en) | Communications management system with a separate peripherals server | |
| KR101326231B1 (en) | Virtualization software service system, and sevice server and user terminal therefor | |
| US10437608B2 (en) | Microminiature personal computer and method of using thereof | |
| CN108235822A (en) | The implementation method and device of virtual SIM card, storage medium, electronic equipment | |
| Attaby et al. | WiPi: A low-cost heterogeneous wireless testbed for next generation applications | |
| Ma et al. | Using Windows Printer Drivers for Solaris Applications–An Application of Multiagent System | |
| CN114218732A (en) | BIM design cloud platform architecture based on RDP (remote desktop protocol) | |
| Kallioniemi | Installing and Commissioning MCS Over an LTE-system | |
| CN108337240A (en) | A kind of office procedure, terminal and system for secrecy sex work | |
| CN106162217A (en) | A kind of method and apparatus realizing video playback |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |
Effective date: 20170427 |