Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
  • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
  • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
  • G06F9/5055—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering software capabilities, i.e. software resources associated or available to the machine
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
  • G06Q10/063—Operations research, analysis or management
  • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2209/00—Indexing scheme relating to G06F9/00
  • G06F2209/50—Indexing scheme relating to G06F9/50
  • G06F2209/5015—Service provider selection

Definitions

• the present invention relates to a method, system, and program for selecting a resource manager to satisfy a service request.
• a catalog is maintained indicating resource manager systems capable of providing services to subscribers.
• a subscriber connects to the content manager and requests a particular service listed in the catalog.
• the content manager locates a resource manager in the catalog capable of providing the service and routes the service request to the resource manger.
• the service may comprise a file to download and the resource manager may comprise a node or system in the network indicated in the catalog that is capable of serving that requested file/service to the requesting subscriber.
• the file is routed to a resource manager to store.
• a catalog indicating a plurality of resource managers and at least one service offered by the resource managers is provided. Further provided is resource manager information indicating resource availability information for resource managers offering at least one service. A request for a requested service from a subscriber is received. The catalog is processed to identify resource managers publishing the requested service and the resource manager information is processed to determine at least one identified resource manager publishing the requested service that also satisfies at least one rule applicable to the service request.
• Figure 1 illustrates an embodiment of a network environment providing access to services.
• Figure 2 illustrates an embodiment of a catalog entry.
• Figure 3 illustrates an embodiment of resource manager information.
• Figure 4 illustrates an embodiment of the content of a rule.
• Figures 5a and 5b illustrate an embodiment of operations to select one resource manager to provide a service to a subscriber requesting the service .
• Figure 6 illustrates an embodiment of operations performed to implement a business process rule to select a resource manager to provide a service to the subscriber.
• Figure 1 illustrates a network environment comprising a network 2 connecting resource managers 4a, 4b, 4c, a coordinator 6, and subscribers, 8a, 8b.
• the network may comprise a suitable network known in the art, such as a Local Area Network (LAN) , Storage Area Network (SAN), Cluster File System, a grid, etc.
• a resource manager 4a, 4b, 4c is a computer system that publishes or provides access to one or more services 10a, 10b, 10c.
• a service may comprise a data service (e.g., storage or retrieval of objects, files, etc.) or a computational service (e.g., a search engine, database application, etc.).
• a subscriber 8a, 8b comprises a system 6a, 6b that requests a service.
• a coordinator 6 tries to link up the subscriber 8a, 8b service request with a resource manager 4a, 4b, 4c publishing the requested service.
• the coordinator 6 includes a catalog 12 identifying services offered by the resource managers 6a, 6b, 6c, resource manager information 14 providing performance information and technical properties on the resource managers 6a, 6b, 6c registered in the catalog 12, and an inference engine 16 that processes rules 18 to select one resource manager 6a, 6b, 6c publishing the requested service to use to provide the service in a manner that complies with the rules 18.
• Figure 2 illustrates an embodiment of a catalog entry 50 providing information on an available service, e.g., data or computational service.
• the service 10a, 10b, 10c may comprise: a storage service providing storage capacity to store requested files or objects; objects that a user may want to access, where each object accessible through a catalog 12 may comprise a separate service, such as multi-media files or programs to download; storage archival and retention services; and computational services, such as a search engine, database application, etc.
• Each catalog entry 50 may include a service field 52 indicating the type of service available through the catalog 12, e.g., data or computational service.
• the service parameters 54 provide information about the service.
• the service parameters provide information on the file, such as file name, size, type, access frequency, availability, etc. If the service comprises available storage, then the service parameters 54 may indicate information on the type of storage, e.g., RAID level, hardware redundancy, etc. If the service comprises a computational resource, then the service parameters 54 provide information on the type of computational resource, such as a search engine, database application, etc.
• the catalog entry 50 may also indicate resource managers 56 publishing the service.
• Figure 3 illustrates information 70 for a resource manager 4a, 4b, 4c maintained in the resource manager information 14, including: a resource manager identifier (ID) 72 and available resources 74 at the identified resource manager, such as available storage space, available computational resources, available bandwidth, number of users accessing the resource manager, hardware redundancy, technical specifications, such as supported protocols and interfaces, etc.
• ID resource manager identifier
• available resources 74 at the identified resource manager such as available storage space, available computational resources, available bandwidth, number of users accessing the resource manager, hardware redundancy, technical specifications, such as supported protocols and interfaces, etc.
• Figure 4 illustrates a rule entry 80 in the rules 18 including a rule identifier (ID) 82 and a rule statement 84 specifying one or more actions to take based on a certain condition concerning resource manager and/or subscriber properties.
• ID a rule identifier
• Rule statement 84 specifying one or more actions to take based on a certain condition concerning resource manager and/or subscriber properties.
• the rule may be used to specify a resource manager that can provide the service by specifying certain required storage conditions, such as available space, hardware and data redundancy (e.g., RAID level), availability of the storage device, etc.
• a file storage service rule may also specify a resource manager based on properties of the object being stored, such as the object's access frequency, size, compression, etc.
• the rule may consider conditions of the subscriber, such as their account level or status, and determine a resource manager that the subscriber may use for the requested service that supports the subscriber status and/or service level.
• the rule may consider properties of the resource manager providing/publishing the service, the subscriber requesting the service, and any object or file processed by the service request to determine action to take based on such considered properties.
• the rule 80 may further indicate applicable services 86 to which the rule applies, such that for the identified service 86, the inference engine 16 applies the rule 80 when the identified service 86 is requested.
• the inference engine 16 may apply the rules 18 dynamically during runtime to dynamically control the allocation of resources to ensure the conditions required by the rules 18 are satisfied.
• the rules may further specify service level agreements (SLAs) comprised of quality of service rules (QOS), technical rules, and/or business rules.
• SLAs service level agreements
• the rules may also provide for the balancing of hardware and software resources.
• the rules may further provide for the provisioning of network resources to offer faster transmissions of data, ensure fault recovery of data transmissions by provisioning the receipt of data from multiple providers, dispatching requests to redundant services to offer fault protection and recovery in the event of a hardware or software failure, and capturing and evaluating the state of hardware resources in realtime (CPU, Memory, I/O, Network) within a system.
• the coordinator 6 maintains and uses the catalog 12, resource manager information 14, and rules 18 to determine how to process service requests from subscribers 8a, 8b.
• Figures 5a and 5b illustrates an embodiment of operations performed by the coordinator 6 to process a service request from a subscriber 8a, 8b.
• the coordinator 6 Upon receiving (at block 100) a request for a requested service from a subscriber 8a, 8b, the coordinator 6 processes (at block 102) the catalog 12 to identify resource managers 4a, 4b...4n publishing the requested service.
• the coordinator 6, or inference engine 16 further processes (at block 104) the resource manager information 14 to determine at least one identified resource manager 4a, 4b, 4c publishing the requested service in a manner that satisfies at least one rule 80 applicable to the service request.
• the inference engine 16 may process the rules 18 to determine action to take based on the outcome of the rule processing.
• One rule may indicate a technical parameter, such as a technical property that must be supported or available at the resource manager 4a, 4b, 4c.
• Technical parameters may include a minimum amount of available resources (e.g., storage, computational, etc.) at the resource manager 4a, 4b, 4c, minimum connection bandwidth, supported protocols and required features, etc.
• technical parameter specifies a technical feature that is a prerequisite for the resource manager 4a, 4b, 4c to be available to provide the requested service. If (at block 106) there is least one rule 80 applicable to the service request having a technical parameter, then a determination is made (at block 108) whether a least one resource manager publishing the requested service satisfies the technical parameter.
• the resource manager information 70 for the resource managers 4a, 4b, 4c may be processed to determine whether a certain technical parameter is satisfied. If not, an error message is returned (at block 110) that the service is not available.
• a quality of service parameter specifies a requirement that the resource manager 4a, 4b, 4c must satisfy to provide a certain level of performance to the subscriber, such as a required connection bandwidth, a maximum number of currently connected users, a minimum amount of available computational resources, a specified hardware redundancy, performance requirements of the resource manager hardware, etc.
• the quality of service parameter may specify both a minimum amount of performance or service as well as a maximum.
• the coordinator 6 determines (at block 114) whether at least one resource manager publishing the requested service satisfies the quality of service parameter.
• the resource manager information 70 for the resource managers 4a, 4b, 4c may be reviewed to determine whether a certain quality of service parameter is satisfied. If not, control proceeds to block 110 to return the message that the service is not available .
• the coordinator 6 may also check (at blocks 116 and 120 in Figure 5b) whether there are any rules 80 applicable to the requested service having business parameters.
• a business parameter may specify a security level or group membership that the subscriber 4a, 4b and/or resource manager 4a, 4b, 4c must satisfy in order to access and/or be selected to provide, respectively, the requested service.
• a business parameter may also specify other corporate or organizational policies, such as requiring that certain files being archived in storage be stored in a specific location depending on the type, size, access frequency, classification, etc. of the file.
• the resource manager information 70 for the resource managers 4a, 4b, 4c may be processed to determine whether a certain business parameter is satisfied.
• the coordinator 6 selects (at block 124) one determined resource manager 4a, 4b, 4c satisfying all the applicable rules to provide the requested service to the subscriber 8a, 8b. If there are multiple resource managers 4a, 4b, 4c satisfying the applicable rules, then the coordinator 6 may use a selection technique to select one resource provider, such as round robin, load balancing based on resource availability and usage at the resource managers 4a, 4b, 4c, etc.
• Figure 6 illustrates an embodiment of operations performed by the coordinator 6 to implement a business process rule that is used to determine the processing and handling of an object.
• Control begins at block 150 when the coordinator 6 receives (at block 150) a request from a subscriber 8a, 8b to process an object.
• the subscriber 8a, 8b may comprise a program interfacing with a file system, database application, mail server, data repository, etc., to determine how to process objects, files, etc., within the repository
• the business process rules provide policies, such as archival and retention policies, to determine whether any special handling of the objects are required.
• the subscriber may comprise a "grabber" that accesses emails and requests a service from the coordinator 6 to determine whether the emails need to be archived, stored, flagged or otherwise handled according to the archival and retention policies of the organization. Additionally, the subscriber may interface with a file system that requests a service from the coordinator 6 to apply archival and retention policies to files in the file system to implement business objectives.
• the coordinator 6 Upon receiving the service request with respect to an object (e.g., file, record, email, etc.) having an applicable business process rule, the coordinator 6 processes (at block 152) the catalog 12 to identify resource managers 4a, 4b, 4c capable of processing the object according to the requested service. The coordinator 6 further processes (at block 154) object parameters and the business process rule to select at least one resource manager 4a, 4b, 4c to process the object. The business process rule may further specify requirements of the resource manager 4a, 4b, 4c to receive the object for archival or storage. The object is then transmitted (at block 156) to the determined resource manager.
• an object e.g., file, record, email, etc.
• the resource managers 4a, 4b, 4c may comprise computer readable devices, wherein the business process rule specifies retention and archival policies that selects one computer readable media in which to store the object based on the object parameters.
• the object parameters of the object may indicate the object size, access frequency (e.g., very high, high, frequent, low, etc.), desired availability (high availability, on-line, near online,, etc.), coding (e.g., file format, compression, encryption, etc.), subject matter, etc.
• the business process rule may then specify different types of computer readable media, e.g., tape, hard disk drive, memory, etc., in which to store the object based on conditions related to the object parameters.
• the object access frequency is relatively high, then the object may be stored in memory; if the size is large or the access frequency is low, then the object may be stored on tape; if the access frequency is high and the object is of a certain type, then the object may be stored in a file system; if the object access frequency is high and the object is required to be highly available, then the object may be stored in a disaster recovery or mirror site.
• the object parameters indicate that the object is related to a certain subject matter, e.g., litigation or transactional related, then the object may be archived for a period of time as specified by the business policy requirements. In this way, a business process rule specifies conditions and target storage and memory locations to store objects subject to a service request so as to implement archival and retention policies.
• the service may comprise an online file sharing service and the catalog 12 provides information on files, e.g., multi-media files, programs, etc., that subscribers 8a, 8b may download.
• the rules 18 may then be used to select an appropriate resource manager
• the service may comprise a request to upload files to a content management system, where a business process rule based on the object parameters of the file being uploaded routes the file to an appropriate storage location in the content management system based on the object parameters, such as file size, access frequency, and other classifications .
• the described operations may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof.
• article of manufacture refers to code or logic implemented in a tangible medium, where such tangible medium may comprise hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.) or a computer readable medium, such as magnetic storage medium (e.g., hard disk drives, floppy disks,, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.).
• hardware logic e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.
• a computer readable medium such as magnetic storage medium (e.g., hard disk drives, floppy disk
• Code in the computer readable medium is accessed and executed by a processor.
• the tangible medium in which the code or logic is encoded may also comprise transmission signals propagating through space or a transmission media, such as an optical fiber, copper wire, etc.
• the transmission signal in which the code or logic is encoded may further comprise a wireless signal, satellite transmission, radio waves, infrared signals, etc.
• the transmission signal in which the code or logic is encoded is capable of being transmitted by one station and received by another station, where the code or logic encoded in the transmission signal may be decoded and stored in hardware or a computer readable medium.
• the "article of manufacture” may comprise a combination of hardware and software components in which the code is embodied, processed, and executed. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without and that the article of manufacture may comprise any information bearing medium known in the art.
• the described embodiment provided specific example of rules that may be used to select a resource manager to provide a requested service.
• additional types of rules and combinations of rules may be implemented and used to select a resource manager based on properties and qualities of the resource manager and/or subscriber.
• Figures 2, 3, and 4 illustrate information provided with catalog entries, resource manager information entries and rules.
• different and additional types of information and information in different formats may be provided in the catalog, resource manager information, and rules than shown.
• the illustrated operations of Figures 5 and 6 show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified or removed. Moreover, steps may be added to the above described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Human Resources & Organizations (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• Strategic Management (AREA)
• General Physics & Mathematics (AREA)
• Entrepreneurship & Innovation (AREA)
• Economics (AREA)
• Educational Administration (AREA)
• Development Economics (AREA)
• Game Theory and Decision Science (AREA)
• General Engineering & Computer Science (AREA)
• Marketing (AREA)
• Operations Research (AREA)
• Quality & Reliability (AREA)
• Tourism & Hospitality (AREA)
• General Business, Economics & Management (AREA)
• Management, Administration, Business Operations System, And Electronic Commerce (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Priority Applications (2)

Applications Claiming Priority (2)

Publications (1)

Family

ID=36218276

Family Applications (1)

Country Status (4)

Cited By (8)

Families Citing this family (22)

Citations (3)

Family Cites Families (22)

• 2005
  • 2005-03-23 US US11/089,094 patent/US8126914B2/en not_active Expired - Fee Related
• 2006
  • 2006-03-14 JP JP2008502379A patent/JP5160408B2/ja not_active Expired - Fee Related
  • 2006-03-14 CN CN2006800090232A patent/CN101147130B/zh not_active Expired - Fee Related
  • 2006-03-14 WO PCT/EP2006/060688 patent/WO2006100194A1/en not_active Ceased
• 2011
  • 2011-11-03 US US13/288,913 patent/US10977088B2/en not_active Expired - Fee Related

Patent Citations (3)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events