EP2583167A1 - Contrôle de données et accès à des données sur la base de métadonnées - Google Patents

Contrôle de données et accès à des données sur la base de métadonnées

Info

Publication number
EP2583167A1
EP2583167A1 EP11796465.0A EP11796465A EP2583167A1 EP 2583167 A1 EP2583167 A1 EP 2583167A1 EP 11796465 A EP11796465 A EP 11796465A EP 2583167 A1 EP2583167 A1 EP 2583167A1
Authority
EP
European Patent Office
Prior art keywords
data
storage
rules
access
metadata
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.)
Withdrawn
Application number
EP11796465.0A
Other languages
German (de)
English (en)
Other versions
EP2583167A4 (fr
Inventor
Drew S. Johnson
Marcelo San Martin
Amit Sinha
Indranath Ghosh
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Unwired Planet International Ltd
Original Assignee
Unwired Planet Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/978,458 external-priority patent/US8425061B2/en
Application filed by Unwired Planet Inc filed Critical Unwired Planet Inc
Publication of EP2583167A1 publication Critical patent/EP2583167A1/fr
Publication of EP2583167A4 publication Critical patent/EP2583167A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/122—File system administration, e.g. details of archiving or snapshots using management policies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/14—Details of searching files based on file metadata

Definitions

  • the present invention relates generally to data access, and more specifically, to metadata- based storage of data for access.
  • client-based applications referred to herein as client applications
  • client applications interact with storage systems by providing primitive metadata such as file and folder name, read or write access restrictions, and sometimes an access control list.
  • client applications such as email and picture albums require storage systems to satisfy fast local access times yet be capable of appearing infinite since users do not delete their content.
  • a rules-based storage and access system controls the selective storage of data in a plurality of file systems, where different ones of the file systems are deployed on different types of file systems that have different characteristics, such as different input and output capacities.
  • the rules-based storage and access system includes a mobile device interface and an application interface. The interfaces interface with a multitude of disparate mobile devices and applications, such as mobile devices operated by different users over a wireless telephone network and applications that provide services to the users.
  • the rules- based storage and access system is configured, for each of a multitude of users, to receive data from a remote source, retrieve metadata-based data storage rules based upon metadata in the received data, and execute storage instructions in the retrieved data storage rules to select one of the plurality of file systems in which to store the data.
  • the rules-based storage and access system then communicates with the selected file systems to store the received data therein.
  • the rules-based storage and access system is responsive to requests for stored data (from an application and/or one of the mobile devices) as received via one of the interfaces, to direct the retrieval of data stored in accordance with the data storage rules for providing the data for communication to an application and/or one of the mobile devices via the corresponding interface.
  • Fig. 1 depicts a system for controlling data storage and access includes a mobile device interface, a client application interface, and a rules-based storage and access system.
  • FIG. 2 illustrates a system for storing content, according to another example embodiment of the present invention.
  • FIG. 3 illustrates a system for storing and retrieving content, according to another example embodiment of the present invention.
  • FIG. 4 illustrates a system for storing and providing content to mobile devices via a wireless communications system, according to another example embodiment of the present invention.
  • FIG. 5 illustrates a data storage controller circuit, according to an example embodiment of the present invention.
  • Fig. 6 depicts a method for controlling the selective storage of data in a plurality of file systems, different ones of the file systems having different data retrieval characteristics.
  • Fig. 7 depicts a computer that includes a processor, memory, and a communications interface.
  • An embodiment of the present invention relates to data access systems and approaches as described herein. While the present invention is not necessarily limited to such systems and approaches, various aspects of the invention may be appreciated through a discussion of examples using these and other contexts.
  • a data storage and access system is configured to interface with remote devices, such as mobile telephones and other hand-held devices, to provide multiple types of storage and retrieval functions, each type having characteristics such as cost and speed that are different than the other types, and which may change over time.
  • This storage and access system may operate using a single interface or link to users providing data to store, yet functions at multiple levels based upon the different supported types of storage and retrieval functions (e.g., high-speed systems, low-speed systems).
  • the type of storage and retrieval functions (and related systems) used for a particular set of data is selected based upon criteria relating to the data and/or a user of the data, such as by identifying a least-cost storage option that meets performance criteria assigned to the data being stored.
  • a data storage system controls the selective storage of data in a plurality of file systems, where different ones of the file systems have different data retrieval characteristics (e.g. , where each file system includes one or more databases).
  • data retrieval characteristics relate to various aspects of data storage and retrieval, such as the speed of access, number of accesses, reliability, size of data files to be individually retrieved, and others. Different types of storage may thus be tailored to
  • Data is stored and subsequently provided for access by each or a multitude of users, such as for subscribers to a mobile telephony carrier service.
  • a system 10 for controlling data storage and access includes a mobile device interface 12, a client application interface 14, and a rules-based storage and access system (RBSAAS) 16.
  • the rules-based storage and access system includes a storage broker 18, a data storage engine 20, a file system 22, a storage rules engine 24, a maintenance server 26, and an analytics engine 28.
  • the system interfaces with mobile devices 30 and various applications 32.
  • the mobile device interface is configured to interface with a multitude of disparate mobile devices operated by different users over a wireless communications network. Accordingly, the mobile device interface may include one or more of a variety of systems, devices, and/or circuits as may be appropriate, such as those involving a mobile telephony-type base station network and related mobile communications circuits and systems.
  • the rules-based storage and access system 16 is configured to receive data such as image data, an email message, or video data from a remote source, such as a user's hand-held mobile device, a message services provider, a user's PC, or a subscription-based content service. For each set of received data, the rules-based storage and access system retrieves metadata-based data storage rules based upon metadata in the received data. Using the retrieved data storage rules, the rules-based storage and access system executes storage instructions in the retrieved data storage rules to select one of a plurality of file systems in which to store the data. Once selected, the rules-based storage and access system stores the received data in the selected file system according to the data storage rules.
  • data such as image data, an email message, or video data from a remote source, such as a user's hand-held mobile device, a message services provider, a user's PC, or a subscription-based content service.
  • the rules-based storage and access system retrieves metadata-based data storage rules based upon metadata in the received data
  • the mobile device interface 12 processes the request and communicates information based upon the request to the rules-based storage and access system 16.
  • the rules-based storage and access system uses the request information to direct the retrieval of data stored in accordance with the data storage rules for providing the data for communication to the user at his/her mobile device, via the mobile device interface. Accordingly, the speed and other characteristics of the user's remote access are based upon the ability of the rules-based storage and access system to access the data from the file system selected for storing the data, which is further based upon metadata in and/or attributed to the stored data.
  • the rules-based storage and access system 16 is configured to read metadata assigned to the received data by a client application 32 by identifying the type of client application. For instance, when a client application provides email services, metadata in the received data that identifies the client application is used to further identify the data as email data.
  • the rules-based storage and access system uses the identified type of client application in retrieving metadata-based data storage rules for the type of data provided by the client application.
  • the client applications are hosted remotely from the rules-based storage and access system. That is, the client applications are hosted on an application server that is connected to the rules-based storage and access system via the Internet.
  • Metadata-based data storage rules are tailored to particular client applications. For instance, data storage rules may be tailored to email-based applications, in which recent email is maintained in a rapid-access file system, and older email is stored in a file system exhibiting slower access times, such as by archiving older email. Data storage rules may also be tailored to applications serving multiple users, where data used by more than one user is stored based upon the collective use of the data by the users. For example, more frequently accessed data is stored in a rapid-access file system and less frequently accessed data is stored in a relatively slower-access file system.
  • the rules-based storage and access system 16 is configured to execute the storage instructions using dynamic read/write characteristics assigned to the received data as an input to select one of the plurality of file systems in which to store data. For example, as discussed above, recent email may be assigned a high read/write rate due to expected access to the email for viewing, responding to, and/or forwarding. As the email ages, the expected access is assigned a lower read/write rate based upon an expected consideration that the email is less likely to be accessed, if at all. The rules-based storage and access system thus stores the data based upon a corresponding read/write characteristic of the selected file system.
  • the rules-based storage and access system 16 is configured to identify different sets of related data based upon metadata in the received data. For instance, related emails in a chain of emails may be linked, or audio data may be linked to a playlist.
  • the rules-based storage and access system uses the identified relationship in executing the storage instructions to select one of the plurality of file systems in which to store the different sets of related data, or to select file systems that are physically close to one another in which to store the related data (e.g., so a bulk- fetch operation can retrieve the data faster).
  • storage instructions may specify that the related data sets both be stored in the file system having a higher access priority level.
  • a set of data may be shared by a variety of client applications or users, and may have replicated versions of the data stored in multiple places; updates to the data can be tracked and used to update other versions of the data stored in different locations.
  • Another example embodiment is directed to data storage and access in accordance with metadata and user-specific storage and retrieval rules, to control the storage of data in different data storage arrangements according to expected use and/or user-specific storage requirements, as relative to the respective capabilities and other characteristics of the data storage arrangements (e.g., to store data needing fast/recurring access in those file systems that provide such access).
  • the storage rules engine 24 stores, in association with identity data for each of a multitude of users, data storage rules that define storage instructions for storing data based upon metadata-based information included with the data. These data storage rules may, for example, define a class of service for particular users, such that users can subscribe to different classes of service for storing data.
  • the access service may relate, for example, to capabilities of various file systems, or to the control of such systems, and related priority assigned to data associated with different classes of service (e.g. , data afforded a higher class of service may be stored in the same file system as data afforded a lower class of service, with the higher-class data having priority access over lower-class data with such access controlled by a system that bases such priority upon metadata in the data as associated with and/or identifying a particular class of service).
  • classes of service may relate, for example, to capabilities of various file systems, or to the control of such systems, and related priority assigned to data associated with different classes of service (e.g. , data afforded a higher class of service may be stored in the same file system as data afforded a lower class of service, with the higher-class data having priority access over lower-class data with such access controlled by a system that bases such priority upon metadata in the data as associated with and/or identifying a particular class of service).
  • the mobile device interface 12 interfaces with a multitude of disparate mobile devices operated by different users over a wireless communications network, for routing wireless communications and data to and from the mobile devices 30.
  • the rules-based storage and access system 16 is configured, for each of a multitude of users, to receive data from a remote data source for storing on behalf of the user, and for the received data, to use identity data of the user to retrieve data storage rules associated with the identity data.
  • the rules-based storage and access system then executes storage instructions in the retrieved data storage rules, using metadata in the received data as an input, to select a file system in which to store the data. This selection may, for example, be based upon a class of data storage as discussed above.
  • the rules- based storage and access system communicates with the selected file system to store the received data therein.
  • the rules-based storage and access system 16 responds to requests for stored data from the mobile devices 30 (as received via the mobile device interface) by retrieving data stored in accordance with the data storage rules for the particular mobile device. For example, a particular user's identification may be associated with a particular mobile device, and the mobile device's identification (as received with communications from the mobile device) may be linked to the user's identification, and accordingly linked to data storage rules to use for the particular mobile device. Such data storage rules may further specify data retrieval instructions that are based upon the capabilities of the mobile device itself and/or a service to which the mobile device subscribes for communications, as may pertain to speed of access, versions of data that is stored and other storage characteristics. The rules-based storage and access system then provides the data for communication to the one of the mobile devices via the mobile device interface 12.
  • the rules-based storage and access system 16 operates to provide data to and communicate with (as appropriate) the mobile devices 30 over a variety of types of communications links.
  • cellular communication schemes such as Global System for Mobile communications (GSM), Universal Mobile
  • UMTS Telecommunications System
  • CDMA Code Division Multiple Access
  • communications protocols such as defined by the 3 rd Generation Partnership Project (3GPP) or the 3 rd Generation Partnership Project 2 (3GPP2), 4G Long Term Evolution (LTE), for "xG” (further generations), and IEEE 802.16 standards bodies may also be used.
  • the mobile device interface 12 provides a data storage interface for access by each of the multitude of users, presents data storage and retrieval options to each user, and, in response to receiving data storage or retrieval option selections from a user, stores, in the storage rules engine 24, data storage rules in association with identity data for the user. For example, where a multitude of different types of file systems are available, each with their respective capabilities, the mobile device interface provides information to the users, via the rules-based storage and access system 16. In response to a user input presented at the mobile device 30, such as by a pointer/keyboard type of device or a touch screen, and communicated through a wireless communication network, the mobile device interface stores and/or alters data storage rules for the user providing the input.
  • the mobile device interface 12 provides a data storage interface to mobile device 30 via one or more types of communications approaches, such as web-based communications via a mobile device network, cellular-type communications, 3G (or related) communications systems, or one or more others are respectively capable of communicating with mobile devices.
  • the presentation of the data storage interface can be tailored to available communications links or other characteristics of communications with mobile devices, or may further interact with inputs received from applications running on mobile devices (e.g., such that the interface is presented using an onboard application at the mobile device).
  • the rules-based storage and access system 16 tags received data with metadata based upon rules for a user, and controls the storage of the received data based upon the metadata tag. For instance, when a new set of data such as messaging data or media content is received from a particular user, the rules-based storage and access system identifies the source of the data to identify the user. The rules-based storage and access system then tags the received data based upon the user identification. In one instance, the rules-based storage and access system tags the data with an identifier for the user, which can subsequently be used in looking up data storage and retrieval rules for the identified user. In another instance, the rules- based storage and access system retrieves metadata tag information based upon the user's identification, and tags the received data with the retrieved metadata tag information (e.g., to classify the received data into a particular category assigned to the user).
  • the rules-based storage and access system 16 controls the storage of data for a multitude of users, in two or more file systems.
  • the rules-based storage and access system communicates with the mobile devices 30 such as a mobile phone or tablet computer, and interfaces with data sources such as client applications 32, e.g., an email client and website clients that store and provide media content.
  • client applications 32 e.g., an email client and website clients that store and provide media content.
  • Each of the mobile devices, email clients, and website clients use the rules-based storage and access system to store data in the file systems 22 based upon expected access characteristics of the data and/or levels of data storage service attributed to the data.
  • These examples are only a few of a multitude of mobile device types and data sources that the rules-based storage and access system may communicate with.
  • the file system 22 includes a plurality of separate file systems, with three file systems shown by way of example.
  • the file system may, for example, include data storage circuits as well as one or more processors that control the storage of data in the data storage circuits.
  • the three file systems are depicted as within a single file system, it should be understood that the file systems can be distributed amongst storage devices that are both local and remote. For example, one file system may be located on a local server for fast access and another of the file systems may be located at an Internet-connected remote server for archived storage (e.g., with relatively slower access times).
  • one file system may be a RAM based system and another file system is a magnetic disk drive based storage system, both of which may be located on the same server device.
  • the storage rules engine 24 provides data storage rules for execution in storing data received on behalf of a multitude of disparate users.
  • the storage rules engine may include a metadata service (not shown) that operates to provide metadata information for use in identifying and storing different types of data.
  • the rules-based storage and access system 16 is configured to store data in different manners for various applications, which may include one or more of those as discussed above, based upon control inputs and information in data received to be stored, and further generated messaging type communications for communicating with external controllers.
  • Example applications that may utilize storage and access services include email, album (photo), POSIX (Portable Operating System Interface) file, calendar, wave-type collaboration applications and webdav (Web-based Distributed Authoring and Versioning) services.
  • the rules-based storage and access system controls data storage for these applications based upon use of the data, by specific applications or by users.
  • email services may be hosted via the storage and retrieval of email messages, based upon metadata such as that identifying the data as email data and indicating one or more relevant dates upon which future access to the email data may be estimated.
  • One such application involves storing recently-created and/or recently-accessed email data in a file system that provides rapid access to the email data, and correspondingly storing older or seldom-accessed email data in a file system that provides relatively slower access to data.
  • the storage rules engine 24 is configured to retrieve and implement rules for storing email data, such as by executing an algorithm with email metadata as an input to determine which file system, ranging from a relatively faster-access file system to a relatively slower-access file system, in which to store data within.
  • the rules-based storage and access system 16 may also be configured to determine a storage format of data, based upon an expected access (e.g., to archive/compress data that is not expected to be accessed often). In connection with these embodiments, the rules-based storage and access system is configured to respond to relevant dates to select from a file system in which to store data. The rules-based storage and access system is, in certain embodiments, also configured to select from a data format in which to store data, in some instances, for use in storing photo image data.
  • photo album-based data may be similarly managed, with photo image data stored in different file systems based upon the creation and last-access dates attributed to the photo image data, such as indicated in metadata associated with the photo-image data.
  • recently-created photos are stored in a fast-access file system and/or in a fast-access format
  • photos with older creation dates stored in a slower-access file system and/or slow-access format (e.g., compressed or archived).
  • Photo image data with an older creation date may also be upgraded to a faster-access file system (and a fast-access format, if appropriate) based upon access behavior, such as by monitoring access to the photo image data directly or via metadata in the photo image data.
  • Photo image data with an older creation date may further be upgraded to a faster-access file system (and a fast-access format, if appropriate) based on data linking the photo image data with other image data, such as by linking individual images in a photo album, with the rules-based storage and access system automatically upgrading linked photo image data based upon access characteristics for other linked image data (e.g., the rules-based storage and access system may be programmed to predict data access to all images in a particular photo album in response to access to one of the images in the album, and correspondingly upgrade all linked images to a faster-access file system based upon an access date of a most-recently accessed image).
  • the rules-based storage and access system may be programmed to predict data access to all images in a particular photo album in response to access to one of the images in the album, and correspondingly upgrade all linked images to a faster-access file system based upon an access date of a most-recently accessed image).
  • the accessing of a first data element triggers the immediate movement of linked data elements to a faster-access file system in anticipation of an access request for the linked data elements.
  • the rules-based storage and access system is configured to respond to photo image data creation and/or access dates to select from a file system, and from a data format in some instances, for use in storing photo image data.
  • applications 32 store and access data using the rules- based storage and access system 16 to provide services for use at mobile devices.
  • Such applications interact with the rules-based storage and access system for storing and retrieving data, and the rules-based storage and access system stores the data using metadata defined by the applications (e.g., access priority information, such as high, medium, and low access priority) and/or other metadata such as that related to creation of and/or last access times for stored data as discussed above.
  • the applications store and access stored data directly from the rules-based storage and access system, and in other implementations, mobile devices working with the applications store and access stored data from the rules-based storage and access system.
  • the rules-based storage and access system stores data for applications in a variety of manners, and can store different types of data for a single application using different storage approaches as appropriate (e.g. , data that is used infrequently by an application or that has low importance for operation of the application can be stored in a low- priority file system).
  • the rules-based storage and access system 16 is responsive to inputs from mobile device provider systems, such as those pertaining to mobile device analytics data that is used to characterize data storage needs, and uses the analytics-based data storage needs together with metadata in the stored data as inputs for determining an appropriate manner in which to store data.
  • the rules-based storage and access system may be implemented within a mobile carrier system that provides services to a multitude of mobile devices, or may be implemented as a web-based type of system that is accessed by one or more client applications such as described here.
  • the rules-based storage and access system 16 is selectively configurable to provide various services, such as locking, versioning, access control, tagging, search, and notification services, in connection with various implementations.
  • the rules-based storage and access system may notify a particular user when the rules-based storage and access system moves stored data from a high-priority storage to a low-priority storage, may actively tag data for storage, or may search for data pertaining to a particular data type (e.g., by searching metadata to identify related data) for modifying storage conditions.
  • the rules-based storage and access system may lock or limit access control to the data, such as for retrieving or modifying data, and can also execute versioning functions to ensure that an appropriate version of data is available (e.g.
  • the rules-based storage and access system may track updates and make related updates in other storage locations, or may store different versions of the data based upon different formats of the data as may be required by different applications or users). Where a particular user specifies that data be searchable, the rules-based storage and access system stores the data in a manner that facilitates such searches, such as by storing searchable data in a data storage format and/or location that is amenable to searching.
  • Fig. 2 illustrates a system 200 for storing content for a client application, according to another example embodiment of the present invention.
  • the system includes an application server 210, a storage broker 230, a data storage engine 250, a storage rules engine 240, and a file system 258 that includes three distinct file systems 260, 270, and 280, all of are similar to the corresponding elements described above with reference to Fig. 1.
  • a client application operating on the application server 210 submits content 220 including various data as used by the client application to provide services to a mobile device.
  • the data 220 is shown including metadata identifying characteristics of the content such as whether access to the content is read-only or read/write, desired availability of the data, frequency of read and/or write access to the data, and a class of service. These characteristics may be implemented as described above, such as with a class of service defined for data based upon a user's or client application's subscription level, with higher classes of service (e.g., better read/write speeds, higher quality) being assessed higher fees.
  • the storage broker 230 receives the incoming content 220 and accesses the storage rules engine 240 to retrieve data storage rules that correspond to metadata in the content 220.
  • the storage broker 230 submits the content 220 with retrieved the data storage rules to the data storage engine 250, which decides (at 255) which of a plurality of file systems to use based upon the data storage rules.
  • file systems 260, 270 and 280 are shown, respectively having fast, moderate, and slow classes of service applicable to fast, moderate, and slow access.
  • the data storage engine 250 selects one of the file systems based upon the data storage rules, which are in turn based upon the metadata, thus permitting tailored data storage to suit various needs such as those discussed herein.
  • Fig. 3 illustrates a system 300 for storing and accessing content, according to another example embodiment of the present invention.
  • the system includes the application server 310, a storage broker 320, a data storage engine 330, a storage rules engine 380, and a file system 338, as well as an analytics engine 370 and a maintenance server 390, all of which are similar to the corresponding elements described above with reference to Figs. 1 and 2.
  • the system 300 may, for example, be used for retrieving and/or modifying the storage of content stored in accordance with one or more approaches such as shown in and described above in connection with Fig. 2.
  • a client application 32 operating on application server 310 sends requests for stored content to the storage broker 320.
  • the storage broker 320 responds by sending a request for retrieving the content to the data storage engine 330, which interfaces with a plurality of file systems including file systems 340, 350 and 360.
  • file systems 340, 350 and 360 respectively represent systems exhibiting relatively slow, moderate, and relatively fast access speeds.
  • the data storage engine is responsive to content requests received from the storage broker 320 by retrieving the requested content from one of the plurality of file systems and providing the retrieved content to the storage broker 320.
  • the storage broker 320 provides the requested data back to the application server 310 and/or, in some implementations, to one of a plurality of mobile devices 312.
  • the content request originates from a mobile device and the corresponding content is provided to the mobile device.
  • the system 300 manages the storage of data in the respective file systems based upon one or more of a variety of conditions, such as those pertaining to expected or actual use of the stored data, and to classes of service to which users of the stored data subscribe.
  • the analytics engine 370 interfaces with the storage rules engine 380, using active characteristics of stored data as provided by the data storage engine 330 (e.g., read/write access frequency), to determine an appropriate type of file system in which to store data, based upon rules in the storage rules engine 380 and metadata-based characteristics of the stored data.
  • the storage rules engine 380 includes data identifying capabilities of various file systems including systems 340, 350 and 360, such as those pertaining to speed of access as described above, or other capabilities such as those relating to one or more of reliability, redundancy, and security (e.g. , with highly-sensitive data stored under higher security or with encryption, which may slow data access speed).
  • the analytics engine 370 determines that a particular data set should be moved or otherwise stored differently, the analytics engine submits a file move instruction to a
  • the storage broker 320 communicates with the storage broker 320 to instruct the storage broker to move the particular data set.
  • the storage broker 320 issues a move content instruction to the data storage engine 330, the instruction specifying a particular set of stored content and a new file system in which to store the content.
  • the data storage engine 330 responds by generating an instruction 335 that effects moving the particular set of stored content (by way of example, shown as moving from file system 360 to file system 350, such as to move data that is infrequently accessed to a slower and less expensive data file system).
  • Fig. 4 illustrates a system 400 for storing and providing content to mobile devices via a wireless communications system, according to another example embodiment of the present invention.
  • the system includes platform 410 that interacts with remote users/platforms (e.g., via the Internet at 430), and platforms 420 and 422 that respectively interact with or are part of wireless communications systems 440 and 450 (e.g., including mobile switches, base stations, radio towers and other devices/systems as appropriate).
  • Each of the wireless communications systems interfaces with a multitude of mobile devices, including mobile telephones and mobile computers 441-443 and 451-453 (e.g., laptop or pad computers) shown by way of example.
  • system 432 may also be used for storing data for the respective mobile devices, and accessed via platforms 420 and 422.
  • the system 400 may, for example, be implemented in connection with one or more approaches as described above, such as those shown in and described in connection with Figs. 1 - 3, with applications operating on and data stored at/via one or more of the Internet 430, platforms 410, 420 and 422, or at the exemplary mobile devices.
  • each of the application platforms is shown having its own respective analytics, storage/cache and other circuits, and platforms 420 and 422 are shown having respective data storage centers as well.
  • These functions may be implemented in connection with the above examples, for storing and accessing data for a multitude of mobile devices.
  • the respective platforms may serve other platforms (or one another) by storing and providing data in accordance with metadata-based rules and characteristics of the specific application for which data is stored.
  • One aspect of providing fast data access may involve, for example, storing data on an end-user side of a gateway at the platforms 420 and 422, to eliminate the need for passing requested data through a gateway and eliminating related protocol transformation (e.g., from Internet protocols to protocols supported by mobile (wireless) device networks).
  • data is cached within the network of the wireless communications network service provider in a protocol that is supported by mobile devices.
  • data can be provided to a mobile device without the data having to pass into the Internet and undergo the associated Internet protocol transformation.
  • data is cached at the evolved NodeB, GGSN, or SGSN so that the cached data can be providing to a mobile device without having to undergo the protocol transformations that are required to pass data through a gateway such as an Internet gateway.
  • mobile device 441 when the mobile device is communicating via the wireless communications system 440 (e.g., a user's mobile telephone is within range of a tower in system 440), data that the mobile device wants to access rapidly can be stored at platform 420, and data requiring less frequent access may be maintained at platform 410 or at another Internet-based data storage location such as at database 432.
  • the analytics circuit at the platform 420 may direct the movement of data between different data storage locations.
  • the system 400 stores data using location-based analytical information available for one or more mobile devices to which content is provided.
  • mobile device 441 as an example again, as the device moves out of range of the wireless communications system 440 and into range of the wireless communications system 450 (or between towers within the system 440), data requiring rapid access and stored relatively locally at platform 420 (or even closer to towers serving the device) is moved to match the location of the mobile device. For instance, data stored in a storage/cache of platform 420 can be moved to a storage/cache of platform 422 as the device 441 moves out of range of the mobile device communications system 440 and into the range of the system 450. Less -frequently used data can be maintained at remote systems that are further away from the device 441.
  • the storage location of data can be managed not only based upon the frequency of the use of the data but the location of one or more devices using the data.
  • the storage of media content that is accessed by two or more mobile devices is collectively managed based upon characteristics associated with both devices (e.g., with respective users of the mobile devices). For instance, where two users subscribe to a particular video, and where one user subscribes to a level of video service that is higher than the level of video service subscribed to by the other user, the subscribed-to video may be stored in a single data storage location to meet the higher subscription level.
  • data delivery systems e.g., 300 in Fig. 3 intentionally delay the delivery of such content to users subscribing to lower levels of service, where the content is stored in a higher-level file system, in order to mimic the delivery of the content from file systems to which the user is rightfully subscribed, to mitigate the tendency of such users to subscribe to lower levels of service yet benefit from higher service levels subscribed to by other subscribers.
  • a client application 32 providing data specifies metadata for the data, which is used to select and implement data storage as discussed above.
  • the metadata may, for example, be specified to set storage characteristics such as those pertaining to one or more of read versus write usage patterns, class of service, anticipated frequency of reads and/or writes, needs for data updates (e.g., for data susceptible to becoming out-of-date), and availability of the data.
  • a data storage and access system controls the selective storage of data in a plurality of file systems, where different ones of the file systems are deployed on different types of disks that have different characteristics, such as different input and output capacities.
  • the data storage and access system includes an interface circuit and a control circuit.
  • the interface circuit interfaces with a multitude of disparate mobile devices and/or applications, such as devices operated by different users over a wireless telephone network or applications that provide services to the users.
  • the control circuit is configured, for each of a multitude of users, to receive data from a remote source, retrieve metadata-based data storage rules based upon metadata in the received data, and execute storage instructions in the retrieved data storage rules to select one of the plurality of file systems in which to store the data.
  • the control circuit then communicates with the selected file systems to store the received data therein. Once stored, the control circuit is responsive to requests for stored data (from an application and/or one of the mobile devices) as received via the interface circuit, to direct the retrieval of data stored in accordance with the data storage rules for providing the data for communication to an application and/or one of the mobile devices via the interface circuit.
  • the interface circuit includes more than one interface, such as for interfacing with mobile devices (e.g., through a mobile telephone network) and for interfacing with remote applications operating on a packet-based network such as the Internet.
  • Another example embodiment is directed to a data storage and access system including a rules database, a mobile-device interface circuit and a data storage controller circuit.
  • the rules database stores, in association with identity data for each of a multitude of users, data storage rules that define storage instructions for storing data based upon metadata-based information included with the data.
  • the mobile-device interface circuit interfaces with a multitude of disparate mobile devices operated by different users over a wireless telephone network, for routing telephone communications and data to and from the mobile devices.
  • the data storage controller circuit is configured, for each of a multitude of users, to receive data from a remote data source for storing on behalf of the user, and for the received data, use identity data for the user to retrieve data storage rules associated with the identity data.
  • the data storage controller circuit then executes storage instructions in the retrieved data storage rules, using metadata in the received data as an input with the storage instructions, to select a file system in which to store the data and to further communicate with the selected file system to store the received data therein.
  • the data storage controller circuit retrieves data stored in accordance with the data storage rules and provides the retrieved data for communication to the one of the mobile devices via the mobile-device interface circuit.
  • a data storage and access system controls the selective storage of data in a plurality of file systems on behalf of remote client applications, where different ones of the file systems having different data retrieval
  • the storage circuit includes interface circuits including a client-application interface circuit and a mobile-device interface circuit.
  • the client-application interface circuit interfaces with a multitude of disparate client applications for storing data on behalf of each client application and for establishing metadata-based storage rules for the client applications.
  • the mobile-device interface circuit provides stored data to mobile devices subscribing to services provided by the client-application.
  • the storage circuit also includes a rules database that stores the established metadata-based storage rules, and a control circuit that stores and provides data for each of a multitude of client applications.
  • the control circuit receives data sets from a source, where the received data sets include different types of data having different access priorities associated with the respective types of data, and for each received data set, uses metadata in the data set to retrieve metadata-based data storage rules from the rules database.
  • the control circuit uses the retrieved data storage rules to select at least one file system in which to store the received data sets and to direct the storage of the data sets in the selected file system(s).
  • the control circuit is further configured to receive requests specifying stored data for delivery to a particular mobile device, and responds to each received request by identifying one or more file systems in which the specified data resides and directing the delivery of the specified data to the particular mobile device via the mobile device interface circuit.
  • Fig. 5 illustrates a data storage controller circuit 100, according to an example embodiment of the present invention.
  • the circuit 100 includes a content repository storage broker 110 (CRSB), which controls the storage of data for a multitude of users, in two or more file systems.
  • CRSB 110 communicates with mobile devices such as a mobile phone 120, and interfaces with data sources such as an email client 130 and website clients 140 that store and provide media content.
  • Each of the mobile phone 120, email client 130 and website clients 140 use the CRSB to store data in various file systems based upon expected access
  • the CRSB 110 uses a storage service 112 that includes a plurality of file systems, with three file systems shown by way of example.
  • the storage service may, for example, include data storage circuits as well as one or more processors that control the storage of data in the data storage circuits.
  • the CRSB 110 also includes a storage rules engine 114, which operates as part of the CRSB to provide storage rules for execution in storing data received on behalf of a multitude of disparate users.
  • the CRSB 110 further includes a metadata service 116, with three individual services shown by way of example, which operates to provide metadata information for use in identifying and storing different types of data.
  • the CRSB 110 is configured to store data in different manners for various applications, which may include one or more of those as discussed above, based upon control inputs and information in data received to be stored, and further generated messaging type communications for communicating with external controllers.
  • Example storage-based applications 111 as shown include email, album (photo), POSIX (Portable Operating System Interface) file, calendar, wave- type collaboration applications and webdav (Web-based Distributed Authoring and Versioning) services.
  • the CRSB 110 controls data storage for these applications based upon use of the data, by specific applications or by users.
  • email services may be hosted via the storage and retrieval of email messages, based upon metadata such as that identifying the data as email data and indicating one or more relevant dates upon which future access to the email data may be estimated.
  • One such application involves storing recently-created and/or recently-accessed email data in a file system that provides rapid access to the email data, and correspondingly storing older or seldom-accessed email data in a file system that provides relatively slower access to data.
  • the storage rules engine 1 14 is configured to retrieve and implement rules for storing email data, such as by executing an algorithm with email metadata as an input to determine which file system, ranging from relatively faster-access file systems to relatively slower-access file systems, in which to store data within.
  • the CRSB 1 10 may also be configured to determine a storage format of data, based upon an expected access (e.g. , to archive/compress data that is not expected to be accessed often). In connection with these embodiments, the CRSB 1 10 is configured to respond to relevant dates to select from a file system in which to store data. The CRSB 1 10 is, in certain embodiments, also configured to select from a data format in which to store data, in some instances, for use in storing photo image data.
  • photo album-based data may be similarly managed, with photo image data stored in different file systems based upon the creation and last-access dates attributed to the photo image data, such as indicated in metadata associated with the photo-image data.
  • recently-created photos are stored in a fast-access file system and/or in a fast-access format
  • photos with older creation dates stored in a slower-access file system and/or slow-access format (e.g., compressed or archived).
  • Photo image data with an older creation date may also be upgraded to a faster-access file system (and a fast-access format, if appropriate) based upon access behavior, such as by monitoring access to the photo image data directly or via metadata in the photo image data.
  • Photo image data with an older creation date may further be upgraded to a faster-access file system (and a fast-access format, if appropriate) based on data linking the photo image data with other image data, such as by linking individual images in a photo album, with the CRSB 1 10 automatically upgrading linked photo image data based upon access characteristics for other linked image data (e.g. , the CRSB 110 may be programmed to predict data access to all images in a particular photo album in response to access to one of the images in the album, and correspondingly upgrade all linked images to a faster-access file system based upon an access date of a most-recently accessed image).
  • the CRSB 1 10 is configured to respond to photo image data creation and/or access dates to select from a file system, and from a data format in some instances, for use in storing photo image data.
  • application-use type data one or more of a variety of applications, such as calendar applications, operating system interface applications and distributed/collaboration applications as identified above, store and access data using the CRSB 1 10 to provide services for use at mobile hand-held devices.
  • applications interact with the CRSB 1 10 for storing and retrieving data, and the CRSB 1 10 stores the data using metadata defined by the applications and/or other metadata such as that related to creation of and/or last access times for stored data as discussed above.
  • the applications store and access stored data directly from the CRSB 1 10, and in other implementations, mobile devices working with the applications store and access stored data from the CRSB 1 10.
  • the CRSB 1 10 stores data for applications in a variety of manners, and can store different types of data for a single application using different storage approaches as appropriate (e.g. , data that is used infrequently by an application or that has low importance for operation of the application can be stored in a low- priority file system).
  • the CRSB 1 10 is responsive to inputs from mobile device provider systems, such as those pertaining to mobile device analytics data that is used to characterize data storage needs, and uses the analytics-based data storage needs together with metadata in the stored data as inputs for determining an appropriate manner in which to store data.
  • the CRSB 1 10 may be implemented within a mobile carrier system that provides services to a multitude of mobile devices, or may be implemented as a web-based type of system that is accessed by one or more applications such as described here.
  • the CRSB 1 10 is selectively configurable to provide various services, in connection with various implementations. Locking, versioning, access control, tagging, search, and notification services are shown by way of example.
  • the CRSB 1 10 may notify a particular user when the CRSB moves stored data from a high-priority storage to a low-priority storage, may actively tag data for storage, or may search for data pertaining to a particular data type (e.g., by searching metadata to identify related data) for modifying storage conditions.
  • the CRSB 1 10 may lock or limit access control to the data, such as for retrieving or modifying data, and can also execute versioning functions to ensure that an appropriate version of data is available (e.g., where data is updated and stored at different storage locations, the CRSB 1 10 may track updates and make related updates in other storage locations, or may store different versions of the data based upon different formats of the data as may be required by different applications or users). Where a particular user specifies that data be searchable, the CRSB 110 stores the data in a manner that facilitates such searches, such as by storing searchable data in a data storage format and/or location that is amenable to searching.
  • Fig. 6 depicts a method for controlling the selective storage of data in a plurality of file systems, different ones of the file systems having different data retrieval characteristics.
  • data is received from a remote source at a rules-based storage and access system, the rules-based storage and access system including a mobile device interface configured to interface with a multitude of disparate mobile devices operated by different users over a wireless communications network.
  • data storage rules are retrieved based upon metadata in the received data.
  • storage instructions in the retrieved data storage rules are executed to select one of a plurality of file systems in which to store the data, wherein the plurality of file systems have different data retrieval characteristics.
  • the selected file system is communicated with to store the received data therein.
  • a request for stored data is received from one of the mobile devices as received via the mobile-device interface.
  • the retrieval of data stored is directed in accordance with the data storage rules.
  • the retrieved data is provided for communication to the one of the mobile devices via the mobile device interface.
  • Fig. 7 depicts a computer 700 that includes a processor 702, memory 704, and a communications interface 706.
  • the processor may include a multifunction processor and/or an application-specific processor. Examples of processors include the PowerPCTM family of processors by IBM and the x86 family of processors by Intel.
  • the memory within the computer may include, for example, storage medium such as read only memory (ROM), flash memory, RAM, and a large capacity permanent storage device such as a hard disk drive.
  • ROM read only memory
  • flash memory volatile and non-volatile memory
  • RAM random access memory
  • a large capacity permanent storage device such as a hard disk drive.
  • communications interface enables communications with other computers via communications protocols, for example, via the Internet Protocol (IP).
  • IP Internet Protocol
  • the computer executes computer readable instructions stored in the storage medium to implement various tasks as described above.
  • various embodiments directed to data storage controllers and/or data storage circuits may be implemented with a variety of circuits and/or systems.
  • Embodiments directed to the provision of data to applications may be used to provide data directly to users on mobile or other packet- based devices connected via one or more of a multitude of disparate types of communications networks, with modifications to data and/or the class of storage and retrieval selectively implemented based upon these networks.
  • various embodiments are directed to the integration of data storage and control into other systems, such as mobile communications systems.
  • communications for directing the storage of data and/or providing stored data for use may be made over a variety of networks and using a variety of protocols, such as packet-based networks using the Internet protocol as described herein (e.g., to receive media content), and telephony protocols such as the SS7 protocol, and others (e.g., to deliver content to mobile devices).
  • protocols such as packet-based networks using the Internet protocol as described herein (e.g., to receive media content), and telephony protocols such as the SS7 protocol, and others (e.g., to deliver content to mobile devices).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un accès à des données est contrôlé à l'aide de métadonnées dans les données stockées. Conformément à divers modes de réalisation donnés à titre d'exemple, les données sont stockées pour le compte d'un ou de plusieurs utilisateurs parmi une multitude d'utilisateurs disparates et/ou d'applications utilisant les données, sur la base de métadonnées dans les données mêmes et de règles de stockage destinées aux métadonnées. Dans un mode de réalisation, un système de stockage et d'accès basé sur des règles récupère des règles de stockage sur la base des métadonnées dans les données reçues, et exécute les règles de stockage afin de sélectionner un système de fichiers, dans lequel seront stockées les données reçues, parmi une pluralité de systèmes de fichiers ayant différentes caractéristiques de récupération de données telles que la vitesse, la sécurité et la qualité.
EP11796465.0A 2010-06-17 2011-06-16 Contrôle de données et accès à des données sur la base de métadonnées Withdrawn EP2583167A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US35603410P 2010-06-17 2010-06-17
US12/978,458 US8425061B2 (en) 2008-01-03 2010-12-24 Exterior rearview mirror for motor vehicles
PCT/US2011/040770 WO2011159946A1 (fr) 2010-06-17 2011-06-16 Contrôle de données et accès à des données sur la base de métadonnées

Publications (2)

Publication Number Publication Date
EP2583167A1 true EP2583167A1 (fr) 2013-04-24
EP2583167A4 EP2583167A4 (fr) 2017-03-22

Family

ID=45348553

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11796465.0A Withdrawn EP2583167A4 (fr) 2010-06-17 2011-06-16 Contrôle de données et accès à des données sur la base de métadonnées

Country Status (2)

Country Link
EP (1) EP2583167A4 (fr)
WO (1) WO2011159946A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014142919A1 (fr) * 2013-03-14 2014-09-18 Intel Corporation Gestion de données dans un environnement informatique en nuage au moyen de métadonnées de gestion
US11170044B2 (en) * 2019-01-02 2021-11-09 International Business Machines Corporation Personalized video and memories creation based on enriched images

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8417678B2 (en) * 2002-07-30 2013-04-09 Storediq, Inc. System, method and apparatus for enterprise policy management
US20050055433A1 (en) * 2003-07-11 2005-03-10 Boban Mathew System and method for advanced rule creation and management within an integrated virtual workspace
WO2005043323A2 (fr) * 2003-10-27 2005-05-12 Archivas, Inc. Gestion a base de politiques de reseaux redondants de noeuds independants
US7113981B2 (en) * 2003-12-29 2006-09-26 Mixxer, Inc. Cellular telephone download locker
US9451200B2 (en) * 2005-06-02 2016-09-20 Invention Science Fund I, Llc Storage access technique for captured data
US7761591B2 (en) * 2005-12-16 2010-07-20 Jean A. Graham Central work-product management system for coordinated collaboration with remote users

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2011159946A1 *

Also Published As

Publication number Publication date
EP2583167A4 (fr) 2017-03-22
WO2011159946A1 (fr) 2011-12-22

Similar Documents

Publication Publication Date Title
US20110314071A1 (en) Metadata-based data access and control
US8676194B2 (en) Method and apparatus for preconditioning mobile devices for network and other operations
US9119052B2 (en) Content sharing for mobile devices
US8117303B2 (en) Systems, methods, devices, and computer program products for downloading content for offline browsing
CA2615085C (fr) Procede, dispositif et progiciel fournissant une solution de recherche integree a une application pour dispositifs mobiles, utilisant des informations de contexte
US20050120050A1 (en) Enhanced storing of personal content
US9104758B2 (en) Methods, systems, and products for searching social networks
US11196802B2 (en) Contents management method and apparatus
US8116288B2 (en) Method for distributing data, adapted for mobile devices
US20110103357A1 (en) Back-channeled packeted data
US20070027857A1 (en) System and method for searching multimedia and download the search result to mobile devices
CN101501671B (zh) 经由分组交换网络共享数字内容
US20150139074A1 (en) Adaptive Generation of Network Scores From Crowdsourced Data
US20150033143A1 (en) User terminal and method for displaying integrated communication history of the user terminal
US8019325B2 (en) Podcasting on a mobile phone
EP2583167A1 (fr) Contrôle de données et accès à des données sur la base de métadonnées
WO2015073753A1 (fr) Génération adaptative de scores de réseau à partir de données ayant subi une externalisation ouverte
KR102193481B1 (ko) 프록시 서버, 상기 프록시 서버에서의 페이지 재구성 방법
JP2022060972A (ja) システム、サーバ、プログラム、及び情報処理方法
US8484182B1 (en) Wireless device content searching
US8447834B1 (en) Wireless content loading
US20230362268A1 (en) Apparatus, method and computer program
WO2020154271A1 (fr) Systèmes et procédés de fourniture d'échange de contacts et d'informations et gestion associée
WO2010057687A1 (fr) Transmission de fichiers de données déclenchée par requête d'utilisateur

Legal Events

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

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20130117

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

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

Owner name: UNWIRED PLANET, LLC

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: UNWIRED PLANET INTERNATIONAL LIMITED

RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20170222

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 17/30 20060101AFI20170216BHEP

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

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20170921