HK1188049A - System for scalable processing of files in the cloud - Google Patents

Description

System for scalable processing of files in the cloud

Technical Field

The present invention relates to a system for the secure transmission of files generated by a first user located at a first client station connected to one or more local slave servers through a first Local Area Network (LAN), the first server performing communication with a plurality of computer systems connected to the first LAN.

Background

US2011/0078532a1 discloses a method and system for providing computer-generated output, in particular graphical output. The system includes a network configured to carry digital information. The system includes a server in communication with the network, the server configured to execute an application and a cloud engine module. The application provides graphical output. The output capture and encoding engine module is further configured to intercept graphical output from the application on the server. The output capture and encoding engine module is further configured to convert the graphical output into one of a graphics command and video codec data. The output capture and encoding engine module is further configured to transmit the converted output over a network. The system includes a client in communication with a server via a network, the client configured to execute a graphics and video decoding and rendering engine module. The graphics and video decoding and rendering engine module is configured to render a graphical output in response to receiving the transmitted converted output. The graphics and video decoding and rendering engine module is configured to intercept graphics and video decoding and rendering input at a client. The graphics and video decoding and rendering engine module is configured to send the intercepted user input to the output capture and encoding engine module.

The state of the art described above includes two main areas in which print control systems and techniques are applied.

An important family of print control systems covers standard systems that provide customer-centric deployment of the print control systems and provide control of user printing based on obtaining documents during a spooling (spooling) process.

The second family is cloud-based print control systems, where the system is user-centric, i.e., it focuses on providing print control system features to users using a (1 even) cloud infrastructure without imposing any maintenance costs to an organization such as the user's employer, and often provides different billing and revenue generation approaches, rather than by selling software licenses to customers. Examples of such systems are known under their marketing names google cloud printing, HP ePrint, etc.

Conventional print control systems do not provide the advantages of the cloud:

zero deployment of applications and services typically requires no or substantially reduced costs of purchasing software, hardware, or other resources as compared to traditional software and/or hardware products.

Different billing and payment modes such as pay-per-use, pay-per-click, pay-per-view. In the context of a print control system, this essentially means that the cost to purchase the system by the customer and the overall price of the solution is minimal or non-existent.

Current cloud-based print control systems bring many advantages typical for other cloud applications for printing, but suffer from additional drawbacks that complicate or disqualify deployment of cloud-based print control systems in real-world customer environments. The cloud-based print control system has substantially the same purpose as a conventional print control system: through a so-called spool process, a user document in digital form is sent through a series of actions and transitions to a desired or appropriate printer, copier or multifunction printer device. By extending to multifunction printer devices and scanners, the purpose of a cloud-based or traditional print control system is to send documents in hard copy form. The disadvantages of the cloud-based print control system are:

the print job is exposed. The print job is sent to the cloud, i.e., the print job data is always off the end-user organization's infrastructure and control. To maintain data integrity and confidentiality, print job encryption and digital signatures must be applied, which is currently uncommon and problematic. By deploying complete protection mechanisms, such as digital signatures, certain features such as print job transitions, grayscale or bi-directional implementations, etc., are simply not achievable because these transitions require modification of the print job data.

Wide area network bandwidth consumption when print jobs are transferred back and forth to the cloud. Print jobs can be very large files and their size typically varies from MB to GB. All of this data needs to be transmitted. Wide area network connections typically provide less bandwidth and increased latency in most cases when compared to LANs, and thus the user experience is hindered due to increased latency resulting from increased network latency, in addition to the costs incurred.

Strong dependence on clouds. Current cloud-based systems rely on internet connections and perform all operations online. When a network connection to the cloud (such as an internet connection) is not working or available, the cloud-based print control system will not be able to provide any service to the user.

Object of the Invention

The object of the present invention is to enable t scalable file transfer procedures worldwide without the need to transfer files over a wide area network, but to maintain full access to any file by the user. It is a further object of the present invention to prevent the storage of large numbers of files on multiple servers in a common or public data center during and after data transmission and processing.

Disclosure of Invention

This object is achieved by a system or method wherein a first server may generate and transmit at least one metadata file associated with a file stored in a data cache to a Master Server Unit (MSU) over the internet, the MSU being part of a common or public data center (CDC) with which a plurality of second servers communicate, wherein any user may access the metadata file by authorization to the associated spool file through a second LAN connection to each of the second servers and through a second client station.

Thus, it is achieved that a user can store files in a data cache at a server and possibly transmit them to elsewhere in the world, while the system has sent the metafile to one or more, possibly a group of, main server units, or to one or more, possibly a group of, servers, where the MSU or server may be part of a plurality of different common or public data centers around the world. Upon reaching the destination after transfer via the client station to the local slave server, the user may access the nearest master server unit or servers, depending on the system configuration, and in fact, at the same time, the metadata file has been sent, providing access to the metadata file in the appropriate MSU or server that is part of the family, or the metadata file transfer is initiated by user interaction with the nearest MSU or server, and the user will have to wait for the transfer to end before proceeding. The system will automatically notify the user when the transfer is complete. From the server where the user has access to the metafile and once the user has provided valid credentials, the user has access to his file, which may then be processed in a conventional manner or already processed (e.g., printed) in a conventional manner. In this way, a follow-me system is implemented that operates in an efficient manner because no files are sent; only the metadata file is sent to the host server unit worldwide. With the present invention it is also possible that a group of users have access to the same file simply because they already have a credential that they can use to access the file when they have received the metafile. In this way, it is possible to send, for example, documents in a large organization to a large number of sub-offices where the documents remain more or less always in the company, since the communication of perhaps protected documents is performed directly by the computer communication system without storage at a server somewhere in the world waiting for further transmission. Data transfer is performed in a much cheaper way, as there will be no payment for storing a large number of files on servers somewhere in the world, such as by using a cloud-based file storage service. With traditional cloud transmission of documents, for example, a user must pay for a large database somewhere in the cloud in order to have access to all files. With this co-pending application, only very small metafiles are transmitted through the cloud between different data centers. A metafile comprises only a small set of data compared to a file that has been transferred. The usage has already been sent. The use of storage in the cloud is reduced by more than 99% approximately. While saving storage space, a high degree of security and privacy is also achieved, since nobody can get the security information from the metafile itself, since it is not there at all.

The server includes a data cache that receives and executes a spooling process of files generated at the client station, the data cache performing temporary storage of spooled files.

In any case, since the metadata file has a limited size, there is no problem in storing the metadata file in thousands of servers around the world, however, the metadata file is only transferred to a server or MSU actually requiring it, such as an MSU and a server known to be frequently operated by respective users. The file is not sent until the user has logged into another server at the client station; however, the file is not stored in the server on its way to the client station. From a security point of view it is very important to say that the file sent to the cloud is not present there, only the metadata file is available in the cloud. Thus, a high degree of security is maintained, as only the user has the necessary credentials required to access the metafile first and then the file.

The server may communicate to and from the identity database over a LAN or a general computer network. For sending the meta-data file it is important that the slave server can exchange data with the identity database or with the associated MSU and in this way combine the user identifier, such as the login name, with further data being part of the meta-file.

A data cache in the server may receive the configuration data from the MSU. Hereby it is achieved that the data cache has received the data and in this way ensures that the MSU receiving the information is the correct MSU and that the data stream is transmitted in a language and form that the MSU can receive.

Communication from the server to the MSU and communication from the MSU to the server may be encrypted and authenticated at both ends. Thereby achieving a high degree of security, integrity and privacy for all transmitted data.

The communication from the server to the MSU and the communication from the MSU to the server are asynchronous. With asynchronous communication, data may be transmitted during a period in which data traffic is limited to have sufficient space for data transmission via the communication link. Asynchronous communication further helps maintain a high degree of security and scalability, as asynchronous communication allows data to be sent as packets on different routes in a data communication environment.

The user may access any server in roaming mode, the server recognizing the user access, and when the user connects, the server requesting data transmission from the server to the MSU or an appropriate server.

The patent application further relates to a method for scalable processing of files, the method comprising the steps of:

a. a first user generates a file at a first client station;

b. transmitting the file from the first client station to the server over the first LAN;

c. performing a spooling process at a server connected to the first LAN;

e. storing the spool file in a data cache memory of the server;

f. sending metadata associated with the spool file to the MSU;

g. the MSU gives access to the metadata file to any server that sends the relevant authentication information;

h. sending the spool file from the data cache of the first server to the MSU and further to the real server;

i. the spool file is transmitted from the server to the second client station over the LAN.

By the above-described method, if valid processes and valid credentials are provided when one or more users trigger a process, a high degree of security and scalability can be achieved in sending a file or other data packet from a user of a client station to any computer system for that process that is located elsewhere in the world for which the data file or files are ready for processing. Any user with valid credentials will in this way have access to files stored locally at a server, which may be located thousands of kilometers away. The file will be sent directly, using only the metafile and performing authorization. Thus, distribution of documents to a large group of users may be performed, or it may be possible that one user may travel from one place to another in the world and only have access to his own documents. By sending large files, it is important to perform file transfers directly and not perform storage in a data center somewhere in the world. It is very expensive to perform storage of large data volumes in a data center somewhere. Thus, with the present invention, only metafiles are sent to the data center for storage. Because the metafile contains only the authorization code and the reference to the file, the metafile contains only a relatively small amount of data compared to the actual file to be transmitted. It is likely that large files will also be transferred much faster, since there will be a direct connection link between servers that send files directly from a trace (chase) store to the receiver via the internet.

In this pending patent application, the word "file" is used for any data set, such as any computer-generated file, any digital image, or any computer program.

In this pending patent application, the word "client station" is any computer system, such as a mobile phone, tablet, digital camera.

Drawings

Fig. 1 shows a possible embodiment of an internet communication system as the system described in the pending application.

Detailed Description

Fig. 1 shows a first possible disclosure of a system 2 comprising a Local Area Network (LAN)4 followed by further indicated LANs 4A, 4B, 4C, but it is understood that the number of LANs may be very large and, by extension, the number of (slave) servers may be very large. The first LAN 4 includes a slave server 6, the server 6 including a data cache 8 and the server 6 being connected to a plurality of client stations 10, 10a-n operated by users 7, 7a-n, although it will be understood that each of the plurality of users may use their own client station. The server 6 is further connected to an identity database, such as an active directory 12, and to an SMTP mail server 14. Further, the server 6 is connected to a network printer 16, which includes a terminal 18. The server 6 is further connected to the cloud 22 through a communication line 20. The cloud 22 is a generally accepted description of the world wide web. The cloud 22 is further connected to only one of the plurality of common data centers 24, the plurality of common data centers 24 thus being indicated as common data centers 24a-24 n. The common data center includes at least one primary server unit that is responsible for communication to the cloud 22. The master server unit MSU 26 includes an SQL database 28. The MSU 26 communicates with a central reporting server 30 and further the server communicates with an SMTP mail server 32. The MSU 26 is further in communication with a plurality of servers 34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40 a-n. Each of these servers may be connected to a plurality of client stations as indicated by 42, 42 a-n. All of these client stations are operable by users 7, 7 a-n.

In operation, files generated by the user 7 at the client station 10 will be stored by the system in the database 8 at the server 6, and the server may generate metafiles through an identity management integration point involving the identity database 12. The metafile is then sent from the server 6 to the cloud 22 via the communication line 20. From the cloud, a large number of common data centers may have access to the metafile and obtain copies thereof stored on the servers. From there, the metafile may be further transmitted to a number of servers 34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n where at each server a plurality of client stations 42, 42a-n are connected.

In one possible embodiment, the present invention may be used for follow-me print roaming. In some environments where cloud printing systems are deployed to manage printing, copying, scanning, and facsimile security and billing over a wide area network of locations, it is often desirable to provide a local company-wide print-following system for roaming users anywhere within the company to print to any configurable printer anywhere using fixed workstations or portable computers. Another typical application of the system is optimized cloud printing, where print jobs (as files) are processed locally, but the system is managed by and from the cloud, so that the system provides advantages in terms of privacy, incurred transmission and storage costs over current cloud printing systems known in the art.

Claims (11)

1. A system for the transmission of files, said files being generated by a first user (7) at a first client station (10), the first client station (10) being connected to one or more local servers (6) over a first computer network, such as a Local Area Network (LAN) (4), the first server (6) performing communication with a plurality of computer systems (10a-n) connected to the first LAN (4), characterised in that the first server (6) generates and sends to at least one Main Server Unit (MSU) (26) over the Internet at least one metadata file associated with files stored in a data cache (8), the MSU being part of a common or public data centre (CDC) (24), a plurality of second servers (34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) is in communication with the CDC (24), a first user (7) or a plurality of users (7, 7a-n) may access a metadata file associated with the file through any client station (42) via any LAN connection to any second server (34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40 a-n).

2. The system of claim 1, wherein the system is a printing system.

3. The system according to claim 1 or 2, characterized in that the server (6) comprises a data cache (8) and performs a spooling process, the data cache (8) receiving spooled document files generated at the client station (10, 10 a-n).

4. A system according to any of claims 1-3, characterized in that the servers (34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) communicate to and from the identity database (12) via a communication system such as a LAN.

5. A system according to any of claims 1-4, characterized in that the data cache (8) in the server (6) receives configuration data or control data from the MSU (26).

6. The system according to any of the claims 1-5, characterized in that the communication from the server (6) to the MSU (26) and the communication from the MSU (26) to the server (6) are encrypted and authenticated at both ends.

7. The system according to any of the claims 1-6, characterized in that the communication from the server (6) to the MSU (26) and the communication from the MSU (26) to the server (6) are asynchronous.

8. The system according to any of the claims 1-7, characterized in that a user (7, 7a-n) has access to any server (6, 34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) in roaming mode, said server (6, 34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) identifying the user (7, 7a-n) access, when f users (7, 7a-n) are connected, said server requesting data transmission from the server (6, 34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) to said MSU (26).

9. The system of claim 8, wherein the first user has access to a metadata file associated with the file at any server (6, 34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n), the user having authorization to download the file to an actual client station or printer system.

10. A method for secure transmission of a file, the method comprising the steps of:

a. a first user generating a file at a first client station (10);

b. -sending said file from said first client station to a server (6) through a first LAN (4);

c. performing a stored procedure at a server (6) connected to the first LAN (4);

d. sending metadata related to the stored file to the MSU (26);

e. the MSU (26) gives access to the metadata file to any server (34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) that sends the relevant authentication information;

f. sending the stored files from a data cache (8) in a first server (6) to the MSU and further to actual servers (34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40 a-n);

g. the file is transmitted from the server (34, 34a-n, 36, 36a-n, 38, 38a-n, 40, 40a-n) to a second client station (42, 42a-n) or computer system over a communication system such as a LAN.

11. A method as claimed in claim 10, characterized in that the storing of the spool file is performed in a data cache (8) memory in the server (6).