Browse Prior Art Database

Cloud Aware Assets. In a cloud environment, applications will become smart so that only those linked assets that are required will be downloaded & uploaded to cloud.

IP.com Disclosure Number: IPCOM000220232D
Publication Date: 2012-Jul-26
Document File: 4 page(s) / 82K

Publishing Venue

The IP.com Prior Art Database

Abstract

Consider a file package with file size X MB having multiple pages, linked assets of size Y MB and N number of fonts. Thus the total package size is File + Linked assets + fonts = [X+Y+N*(size of font file)]. After creation of this file, the file is uploaded to cloud. Now a specific page (say p) needs to be edited.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 4

Title

Cloud Aware Assets. In a cloud environment, applications will become smart so that only those linked assets that are required will be downloaded & uploaded to cloud.

Inventors/Authors

Ashish Duggal Priyanka Chitkara

Summary

This method allows for the management of external assets like fonts and links of a file in cloud environment by the applications. Uploading and downloading heavy files from internet is a costly operation. It provides techniques to fetch only those assets which are currently in demand and ways to merge back the changes in original file.

Background

There are many applications which allow creation of files having multiple linked files and size of these linked files is typically greater than the original file size. Also, files can have text with multiple fonts. These two, linked files and fonts, are referred here as assets of the file. Currently, most of the files are uploaded and downloaded from cloud based system in atomic mode i.e. entire file is downloaded and uploaded in the cloud. During the download process, all the linked files are also downloaded. Also, if the fonts used in the file are not installed on the machine, the alerts are presented to the user for the absence of required font. This can be expensive in terms of bandwidth and time.

Consider a use case when a user has created a file having 25 pages and placed it on cloud. Size of this file is 1 MB. It has a different font in each page and has got 20 linked files each of 1MB. Now if only page 25 needs to be edited, then, conventionally, entire file along with 20 linked files would be downloaded making a total download of 21MB. If the file is being opened on a different machine than on which it was created, then alert for unavailability of font might be shown and in order to view the file correctly, user might need to install all the unavailable fonts. All this was done to view and edit page 25 correctly. After editing page 25, the entire content needs to be uploaded again on the cloud. This is a common workflow but no wise solution for the utilization of resources is present today.


Page 02 of 4

Prior Art/Solutions

There are no specific solution to the current problem and conventionally entire file is uploaded and downloaded by cloud based (server based) systems.

Description

Consider a file package with file size X MB having multiple pages, linked assets of size Y MB and N number of fonts. Thus the total package size is File + Linked assets + fonts = [X+Y+N*(size of font file)]. After creation of this file, the file is uploaded to cloud. Now a specific page (say p) needs to be edited.

Consider the following solution

Check whether page p can be isolated and extracted from the file.


1. If yes, then extract the page and move to next step.

2. If it cannot be extracted in isolation and is sharing content with other pages say p+1 and p+2, then extract page p and other connected pages.

  3. If the page is sharing content with the entire file, then downlo...