A portion of the disclosure of this patent document may contain command formats and other computer language listings, all of which are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
This invention relates to Application and Information Movement in a Cloud Environment.
This Application is related to U.S. patent application Ser. No. 14/320,001 entitled “CONTENT FABRIC FOR A DISTRIBUTED FILESYSTEM”, Ser. No. 14,320,069 entitled “CONVERGED INFRASTRUCTURES COMPRISING DISAGGREGATED COMPONENTS”, Ser. No. 14/319,889 entitled “SOFTWARE OVERLAYS FOR DISAGGREGATED COMPONENTS”, Ser. No. 14/318,831 entitled “CLOUDBOOK”, and Ser. No. 14/319,773 entitled “MIGRATING PRIVATE INFRASTRUCTURE SERVICES TO A CLOUD”, filed on even date herewith, which are hereby incorporated herein by reference in their entirety.
As it is generally known, “cloud computing” typically refers to the use of remotely hosted resources to provide services to customers over one or more networks such as the Internet. Resources made available to customers are typically virtualized and dynamically scalable. Usually, cloud computing services may include any specific type of application. Conventionally, the software and data used to support cloud computing services are located on remote servers owned by a cloud computing service provider. Recently, use of the cloud computing service model has been growing due to the increasing availability of high bandwidth communication, making it possible to obtain response times from remotely hosted cloud-based services similar to those of services that are locally hosted.
Further, data storage demands continue to grow at a high rate. One area of growth that is testing information technology infrastructure is the billions of users and millions of applications supported in modern computing. As consumers and businesses alike adopt mobile devices, social platforms, cloud storage, and big data, the dynamics of how we store and protect data is changing as well. Some of these new platforms can be less trusted, less secure, and less resilient than the private cloud infrastructures operated by many enterprises. These private clouds have a set of hardened and reliable infrastructure services that make the data center trusted, secure and resilient.
However, there are benefits of storing, accessing, and utilizing data from the public cloud. For example, cost, flexibility, access to markets, and market trends all may make public clouds an attractive alternative for some storage needs and some applications. However, if consumers and businesses alike want to transition or migrate sensitive data, or data that must have a guaranteed level of resiliency, they need assurances that their needs will be met. Therefore, there exists a need to provide the same infrastructure services that make the private cloud trusted, secure, and resilient, in a public cloud environment.
A computer implemented method, system and computer program product comprising observing a mobile device's interaction with a set of resources, and creating a usage profile for the set of resources based on the mobile devices interactions with the resources; wherein the resources are ranked by the type an frequency of interactions with the mobile device; wherein the usage profile dictates what resources of the set of resources are to be migrated to a new location when the mobile device moves to a new location.
Usually, a mobile device connects to a network access point. Typically, if this is a cellular type device, this may be cellular tower. Conventionally, other common mobile connections may be through a wireless local area network. Currently, when a mobile device moves across geographies, the mobile devices data, data service, and processing capability may not move with the user in a granular way. Typically, mobile users run dozens of applications that can access thousands upon thousands of content depots. Usually, when these users travel, their access to the content may suffer due to latencies fetching (or storing) content to the IT infrastructure.
Generally, when a mobile device changes geographies, such as traveling from Boston to Beijing, the device may only have access to a data connection, which may connect back to where the mobile device's data and services are stored. Usually, such as on a plane flight, the device may exit connectivity in a first location and reconnect to a network in a second geographically disparate location. Typically, this would not allow the device's data or service to be migrated to the second location before the device turns on in the second location. Conventionally, once the device is switched on in a second location there is usually not a way to migrate specific data or services the user may want to use in the new location or even predictively make processing power available to the use. Usually, this leads to a degradation of service quality for a user. Sometimes, after a period of time in a second location, the experience for a user may increase as data may begin to be locally cached at the new location.
Typically, a mobile user working at corporate headquarters in the United States may leverage a variety of mobile applications from their mobile tablet or phone such as corporate email, personal email, online banking, personal social media sites (Facebook), content sharing of presentations and documents (e.g. Syncplicity). Usually, performance in the user's home territory is optimized because generated content is typically stored in a geographically close data center. Conventionally, however, when the mobile device connects to the same service provider in a different geography, the user experiences (or the service providers experience) a number of different problems.
Generally, performance is sluggish due to latencies extending back to the home geography. Usually, service providers are faced with “moving everything” closer to the user, unnecessarily using up network bandwidth between data centers and storage space at the remote data center. Typically, mobile users on multi-hop journeys can further aggravate data migration problems if they do not remain in their locale for a significant amount of time. Conventionally, there is no way for a service provider to prioritize which files or content to move first based on the needs of the mobile user. Usually, there is no way to determine if the user behavior for mobile apps is different when travelling and therefore certain content can be left behind and not moved.
In some embodiments, the current disclosure may enable leveraging per-user mobile application access patterns to trigger content migration for employees connecting into geographically distributed data centers. In an embodiment, the current disclosure may make a prediction of what data or services a user will use in a new location and migrate those service or data when the user goes to a new location. In some embodiments, the current disclosure may enable predictive migration of data and or services to have the services and/or data migrated to a second location by predicting both what services/data the device will use and where the device will be. In at least one embodiment, the predicted location on the device may be based on information on the device.
In most embodiments, information may be extracted from applications on a mobile device. In certain embodiments, location data such as calendar entries, e-mails, social network information, or agendas may provide the ability to predict where a device will be. In further embodiments, location data in the device may be used to predict a future device location. In still further embodiments, different types of commerce, such as a hotel, airplane, or rental car bookings may be used to predict s future location or future locations of the mobile device. In other embodiments, by observing application behavior of the device when it is in different locations, location based data/service prediction may be enabled. In further embodiments, the current disclosure may enable prediction of use of processing resources and may make those resources available to the user when they travel to a new location. In still further embodiments, prediction of what resources may be used by a mobile device may be based on the time of day.
In certain embodiments, a mobile device may have an application that creates a log to enable prediction. In other embodiments, a connection point may monitor the device to create a log to enable prediction. In some embodiments, a log may be used to create a profile that may enable specific data or services to be moved to the location based on the profile. In at least some embodiments, a profile may be time based, moving different data/services, to the second location at different times. In one embodiment, computer based reasoning may be performed on a profile or log to determine when the user needs what services. In certain embodiments, the log may be a “mobile application usage log” (MAUL) that may keep track of the access patterns for every application on a mobile device, including: application name, time of open, amount of activity, and geographic location while using the application. In certain embodiments, a mobile device's interaction with social applications may be used to enhance data availability such as when a mobile device interacts with other mobile devices that may shift location as well. In further embodiments, resource movement for a mobile device may be triaged with the movement of other mobile devices, such as those on a business team attending a meeting together.
In some embodiments, storage of mobile content (e.g. HTTP put) may occur with content being accompanied by one or more attributes from an access file (e.g. which app is storing the content and where the mobile user was located when it stored the content). In at least some embodiment, the request for mobile content (e.g. HTTP get, or HDFS query operation) may result in the infrastructure capturing and storing additional MAUL information within the data center. MAUL information for a particular user may be stored in a variety of places, including data centers and mobile devices. In many embodiments, log information may be versioned and shared/sent between data centers and mobile devices in an “eventually consistent” manner. In other embodiments, connection of mobile devices in a new location may result in leveraging a log to prioritize movement of the most important/relevant data, and the leaving behind of data not likely to be needed. In further embodiments, movement may be linked with “calendar flight itineraries” to recognize when a user is only in a new location for a short period of time (airport flight stopover) and adjust content migration accordingly. In still further embodiments, movement software may “learn” from incorrect movement policies by noticing that migration guesses resulted in moving content that was never accessed by the user in their new location (e.g. they never read any engineering specs but they checked their social network more frequently when travelling).
In most embodiments, intelligent movement of data and services may create quicker and better access to the data while minimizing bandwidth usage. In further embodiments, a profile may be created by monitoring the mobile device without putting software on the mobile device. In other embodiments, a log on a mobile device may periodically be moved to a service provider from the mobile device to the service provider for use. In certain embodiments, before a geographic based profile is established, a default profile may be used in other geographic locations. In many embodiments herein, the term resource or resources may refer to data, services, and/or processing power accessed by a mobile device.
Refer now to the embodiment of
Refer now to the example embodiment of
Refer now as well to the example embodiment of
Refer now to the example embodiments of
Refer now as well to the example embodiment of
In a particular embodiment, a user may heavily use certain services such as work e-mail and facebook access in a first location, such as a home work environment. In a second location, such as an office abroad in China, the user may heavily use certain services, such as work e-mail during all hours and a communication application, such as VIBER outside of work hours. In this particular embodiment, a device profile may, after observing the user travel between these geographic locations, that the data and services with work e-mail should be transferred with the user between the first location and second location with a high priority. Similarly, the device profile may dictate that the data and services associated with facebook should not be transferred to the China location, but additional processing power should be available to make VIBER accessible at the second location. Through the use of these location based profiles, data and service transferred can be prioritized to minimize bandwidth use.
Refer now to the example embodiment of
Refer as well to the example embodiment of
In a particular embodiment, it may be mined from a device that a user has bought a plane ticket from Boston to Shanghai for a particular date. In this embodiment, there would not be a way to track the movement of the mobile device as it would be shut off during flight. In this embodiment, the location prediction may enable data and services to be migrated from Boston to Shanghai based on a profile that has been developed for the user in Shanghai. If no profile has been developed for Shanghai, then data and services may be transferred to Shanghai based on a default profile. In certain embodiments, a location prediction may also dictate when services and data are no longer needed at a different geographic location, such as the date of the return for the plane ticket.
In a different embodiment, a usage profile may dictate that a user leverages compute power when in a particular geographic location. In this embodiment, a mobile device may use intensive compute when not in a home work location. In this embodiment, the mobile device may upload video content, such a marketing data, and real time data analytics may be performed on this video content. In this embodiment, when a user travels to the geographic location, compute resource may be made available to the mobile device. In further embodiments, mobile device data may indicate that other mobile devices, such as of business associates, are traveling to the same location as the mobile device and resources may be migrated to ensure that the mobile devices are able to work together well, such as to collaborate on an application.
The methods and apparatus of this invention may take the form, at least partially, of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, random access or read only-memory, or any other machine-readable storage medium. When the program code is loaded into and executed by a machine, such as the computer of
The logic for carrying out the method may be embodied as part of the system described below, which is useful for carrying out a method described with reference to embodiments shown in, for example,
A detailed description of one or more embodiments of the invention is provided above along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications, and equivalents. Numerous specific details are set forth in the above description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured. Accordingly, the above implementations are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5572221 | Marlevi | Nov 1996 | A |
6012052 | Altschuler | Jan 2000 | A |
6088718 | Altschuler | Jul 2000 | A |
6088732 | Smith | Jul 2000 | A |
6185598 | Farber | Feb 2001 | B1 |
6311065 | Ushiki | Oct 2001 | B1 |
7072845 | Law | Jul 2006 | B1 |
7953741 | Shih | May 2011 | B2 |
7984049 | Shih | Jul 2011 | B2 |
8079081 | Lavrik | Dec 2011 | B1 |
8156553 | Church | Apr 2012 | B1 |
8180782 | Shih | May 2012 | B2 |
8312004 | Shih | Nov 2012 | B2 |
8316098 | Luna | Nov 2012 | B2 |
8326793 | Bowers | Dec 2012 | B1 |
8380179 | Appaji | Feb 2013 | B2 |
8407335 | Church | Mar 2013 | B1 |
8429630 | Nickolov | Apr 2013 | B2 |
8468197 | Shih | Jun 2013 | B2 |
8483375 | Dhara | Jul 2013 | B2 |
8484343 | Shih | Jul 2013 | B2 |
8489615 | Dhara | Jul 2013 | B2 |
8645529 | Doddavula | Feb 2014 | B2 |
8832003 | Bowers | Sep 2014 | B1 |
8909749 | Branch | Dec 2014 | B2 |
8918787 | Ostojic | Dec 2014 | B2 |
8984058 | A Hummaida | Mar 2015 | B2 |
9009294 | Dawson | Apr 2015 | B2 |
9077863 | Patel | Jul 2015 | B2 |
9135048 | Klein | Sep 2015 | B2 |
9143460 | Dhara | Sep 2015 | B2 |
9152685 | Kavuri | Oct 2015 | B2 |
9167591 | Egner | Oct 2015 | B2 |
9210714 | Egner | Dec 2015 | B2 |
9438648 | Asenjo | Sep 2016 | B2 |
9614958 | Radermacher | Apr 2017 | B2 |
9629076 | Shaw | Apr 2017 | B2 |
9961625 | Shaw | May 2018 | B2 |
10048979 | Vincent | Aug 2018 | B2 |
20020198991 | Gopalakrishnan | Dec 2002 | A1 |
20040192342 | Ranganathan | Sep 2004 | A1 |
20040248583 | Satt | Dec 2004 | A1 |
20070150599 | Neogi | Jun 2007 | A1 |
20080097986 | Shih | Apr 2008 | A1 |
20080097987 | Shih | Apr 2008 | A1 |
20080098058 | Shih | Apr 2008 | A1 |
20080155086 | Jensen | Jun 2008 | A1 |
20080155386 | Jensen | Jun 2008 | A1 |
20080242286 | Appaji | Oct 2008 | A1 |
20090029692 | Radermacher | Jan 2009 | A1 |
20090094649 | Patel | Apr 2009 | A1 |
20090276771 | Nickolov | Nov 2009 | A1 |
20110010518 | Kavuri | Jan 2011 | A1 |
20110131224 | Bodin | Jun 2011 | A1 |
20110145392 | Dawson | Jun 2011 | A1 |
20110208756 | Shih | Aug 2011 | A1 |
20110228922 | Dhara | Sep 2011 | A1 |
20110231396 | Dhara | Sep 2011 | A1 |
20110231409 | Dhara | Sep 2011 | A1 |
20110231773 | Dhara | Sep 2011 | A1 |
20110238755 | Khan | Sep 2011 | A1 |
20110265089 | Ostojic | Oct 2011 | A1 |
20110270916 | Shih | Nov 2011 | A1 |
20110296505 | Perez | Dec 2011 | A1 |
20120023223 | Branch | Jan 2012 | A1 |
20120023226 | Petersen | Jan 2012 | A1 |
20120089726 | Doddavula | Apr 2012 | A1 |
20120155426 | Verma | Jun 2012 | A1 |
20130024508 | Sathish | Jan 2013 | A1 |
20130275591 | Kruglick | Oct 2013 | A1 |
20130304924 | Dhara | Nov 2013 | A1 |
20140032741 | Lau | Jan 2014 | A1 |
20140040343 | Nickolov | Feb 2014 | A1 |
20140082614 | Klein | Mar 2014 | A1 |
20140094208 | Egner | Apr 2014 | A1 |
20140099967 | Egner | Apr 2014 | A1 |
20140115514 | Hackborn | Apr 2014 | A1 |
20140172796 | Kavuri | Jun 2014 | A1 |
20140185581 | Senarath | Jul 2014 | A1 |
20140280485 | A Hummaida | Sep 2014 | A1 |
20140337429 | Asenjo | Nov 2014 | A1 |
20150031326 | Begin | Jan 2015 | A1 |
20150046516 | Tsuchida | Feb 2015 | A1 |
20150254248 | Burns | Sep 2015 | A1 |
20150254320 | Cowling | Sep 2015 | A1 |
20150339197 | Kavuri | Nov 2015 | A1 |
20160005005 | Dhara | Jan 2016 | A1 |
20160044692 | Egner | Feb 2016 | A1 |
20160150467 | Shaw | May 2016 | A1 |
20160173631 | McKay | Jun 2016 | A1 |
20160330291 | Asenjo | Nov 2016 | A1 |
20170215138 | Shaw | Jul 2017 | A1 |
20180074843 | Smith | Mar 2018 | A1 |
20190004859 | Bowers | Jan 2019 | A1 |
Number | Date | Country | |
---|---|---|---|
20150381525 A1 | Dec 2015 | US |