US7747643B2 - Installed base data hub - Google Patents
Installed base data hub Download PDFInfo
- Publication number
- US7747643B2 US7747643B2 US11/775,425 US77542507A US7747643B2 US 7747643 B2 US7747643 B2 US 7747643B2 US 77542507 A US77542507 A US 77542507A US 7747643 B2 US7747643 B2 US 7747643B2
- Authority
- US
- United States
- Prior art keywords
- data
- installed base
- base data
- spoke
- hub
- 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.)
- Active, expires
Links
Images
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Definitions
- Embodiments of the present invention generally relate to data management, and more particularly relate to an installed base data hub for centrally managing information about the installed customer base of a business or enterprise.
- a data hub, or master data management (“MDM”) solution is a collection of software and/or hardware components that enables a business or enterprise (i.e., source enterprise) to maintain a single, “master” source of data that is accessible across multiple, heterogeneous information management systems.
- MDM master data management
- software vendors such as Oracle Corporation and IBM offer two types of data hubs: a “Customer” hub and a “Product” hub. These hubs provide a centralized view of a source enterprise's customer and product data respectively.
- the software industry has thus far failed to provide a solution for centrally managing the intersection of information between customers and products—in other words, the installed customer base.
- Each contractor or subcontractor in this multi-tiered network needs access to consistent and up-to-date installed base information (e.g., customer names, addresses, warranty terms, part/model/serial numbers of products sold/deployed/installed, etc.) to properly service the manufacturer's customers.
- installed base information e.g., customer names, addresses, warranty terms, part/model/serial numbers of products sold/deployed/installed, etc.
- a manufacturer may also work with a number of reselling partners to sell its products through various retail channels.
- the reselling partners may wish to leverage installed base information to accurately identify the demographics of the manufacturer's installed customer base and target marketing and/or up-selling campaigns accordingly.
- Another solution is to create a proprietary, point-to-point interface between the information management systems of a partner and manufacturer.
- the partner and manufacturer may contract with a developer to develop a custom interface that will enable their systems to intercommunicate.
- the creation of custom interfaces is generally a slow process as the developer must design and test the interface for the specific systems being connected.
- Such interfaces are also fragile, in that modifications to either system (e.g., updating versions of software) may break the communication path until such time as modifications to the interface are made.
- a point-to-point interface is specific to the particular partner for which it is developed, and thus cannot be leveraged by all external partners interested in accessing and updating the manufacturer's installed base data.
- Embodiments of the present invention address the foregoing and other such problems by providing an installed base data hub that can interoperate with multiple, heterogeneous systems (i.e., “spoke systems”) and thus serve as a centralized data source for all parties (i.e., “partners”) interested in the installed customer base data of a source enterprise.
- spoke systems that interface with the hub may be operated by partners that are internal or external to the source enterprise.
- an installed base data hub includes a central data repository/dictionary, a data librarian, a security module, a set of programmatic subscription/publication interfaces, and an administrative module.
- the central data repository is configured to store installed base master data.
- the data librarian is a software and/or hardware module that is configured to “cleanse” data that is imported or published into the data repository. Data “cleansing” may include resolving data conflicts, removing duplicate data entries, and augmenting incoming data with new fields or categorizations.
- the security module is configured to define and enforce security rules (e.g., read-only, write, read and write, etc.) associated with spoke systems that interact with the hub.
- the programmatic subscription/publication interfaces provide a mechanism for spoke systems to read (i. e., subscribe) and write (i.e., publish) information to the central data repository.
- the subscription/publication interfaces are implemented as Web Services.
- the administrative module provides an interface for managing aspects of the data repository, data librarian, and security module.
- Embodiments of the present invention significantly reduce the operational inefficiencies associated with maintaining mirrored sets of installed base data across the systems of external partners.
- Embodiments of the present invention also provide a single, consistent data source for intra-enterprise systems that may require access installed base data (e.g., marketing, product research, accounting/billing, etc.).
- FIG. 1 illustrates an exemplary operating environment for an installed base data hub in accordance with one embodiment of the present invention.
- FIG. 2 illustrates a simplified block diagram of an installed base data hub in accordance with one embodiment of the present invention.
- FIG. 4 illustrates components of an exemplary system environment that can be used in accordance with one embodiment of the present invention.
- FIG. 5 illustrates components of a computerized device that can be used in accordance with one embodiment of the present invention.
- Embodiments of the present invention provide an installed base data hub that enables multiple, heterogeneous spoke systems to access a centralized data source describing the installed customer base of a source enterprise. Specific embodiments may be particularly useful for product and service providers who must share installed base information with a number of external business partners, each running disparate information management systems. Current methods of information sharing via data replication or proprietary interfaces are problematic because they can be cumbersome, inefficient, and costly. Embodiments of the present invention overcome these problems and thus facilitate the sharing of installed base data across the disparate systems of multiple businesses/enterprises.
- FIG. 1 illustrates an exemplary operating environment for an installed base data hub in accordance with an embodiment of the present invention.
- environment 100 includes an installed base data hub 102 communicatively coupled to spoke systems 104 , 106 , 108 , 110 , 112 , 114 (extra-enterprise systems 104 , 106 , 108 and intra-enterprise systems 110 , 112 , 114 ).
- Installed base data hub 102 is operated by a source enterprise 116 .
- installed base data hub 102 acts as a centralized source of information regarding the installed customer base of enterprise 116 .
- extra-enterprise systems 104 , 106 , 108 are operated by one or more external partners of source enterprise 116 that are interested in installed base information. These include, for example, service contractors, reselling partners, and the like.
- Intra-enterprise systems 110 , 112 , 114 are run by various internal business units or groups of source enterprise 116 that may need to populate data into, or read data from, installed base data hub 102 .
- hub 102 may receive data regarding customer purchases from accounting system 110 and customer sales system 114 .
- hub 102 may receive data regarding the specifications of a purchased product (e.g., color, size, serial number, manufacture date, etc.) from product manufacturing system 112 .
- a purchased product e.g., color, size, serial number, manufacture date, etc.
- spoke systems 104 , 106 , 108 , 110 , 112 , 114 may run any one of a number of different (i.e., heterogeneous) application platforms.
- accounting/billing system 110 may run an Oracle ERP application
- product manufacturing system 112 may run an SAP application
- customer sales system 114 may run a Siebel CRM application.
- systems 104 , 106 , 108 may each run any of the above mentioned platforms or any other application platform.
- Installed base data hub 102 is configured to interoperate with each of these disparate systems/platforms.
- FIG. 2 is a simplified block diagram of installed base data hub 102 in accordance with one embodiment of the present invention.
- Installed base data hub 102 includes installed base repository 204 , data librarian module 206 , security module 208 , subscription/publication interfaces 210 , and administrative module 212 .
- installed base repository 204 is implemented as a relational database or a collection of relational databases.
- repository 204 may be implemented using any other logical storage format (e.g., flat file, etc.).
- installed base repository 204 is shown in FIG. 2 as an integral part of hub 102 , repository 204 may reside on storage that is local or remote to the other components of hub 102 .
- Data librarian module 206 consists of one or more software and/or hardware components that are configured to “cleanse” the installed base data stored in installed base repository 204 .
- Data “cleansing,” or reconciliation is designed to improve the quality and integrity of installed base data since such data is typically imported/updated from a number of different systems.
- One type of data cleansing that may be performed by data librarian 206 is the resolution of data conflicts.
- a data conflict occurs when hub 102 receives conflicting information from two or more spoke systems. For example, accounting/billing spoke system 110 may publish data to hub 102 regarding customer number 1000 that includes a customer name value of “Lee Smith.” Service contractor spoke system 104 may also publish data to hub 102 regarding customer number 1000 , but with a customer name value of “L.
- data librarian 206 may resolve the data conflict using one or more predefined business rules. For example, one business rule may give priority to a data value received from an intra-enterprise system over a conflicting value received from an extra-enterprise system. As described in further detail below, conflict resolution business rules may be defined by a user with appropriate privileges via administrative module 212 .
- a second type of data cleansing that may be performed by data librarian 206 is the elimination of duplicate data entries.
- Duplicate entries typically appear when data is merged or assimilated into installed base repository 204 from a number of different systems for the first time.
- accounting/billing spoke system 110 and customer sales spoke system 114 may each contain a data record for customer number 1000 .
- the data needs to be filtered for duplicate information so that only a single record for customer number 1000 is stored in installed base repository 204 .
- a third type of data cleansing that may be performed by data librarian 206 is the augmentation of data received from spoke systems.
- augmentation includes adding additional qualifiers or categorizations to the data that were not present in the original system, merging existing categories and values, and the like. This allows incoming data to be formatted and stored in a standardized form in installed base repository 204 .
- Data librarian 206 may be implemented as any type of software/hardware component or combination of software/hardware components.
- data librarian 206 may be implemented as one or more PL/SQL packages resident in installed base repository 204 .
- data librarian 206 may be implemented as one or more Java programs resident in an application server.
- data librarian 206 operates in real-time and cleanses data as it is imported/published into installed base data hub 102 .
- data librarian operates as a batch process and processes installed base data stored in repository 204 at predefined intervals.
- One of ordinary skill in the art would recognize many variations, modifications, and alternatives.
- Security module 208 comprises one or more rules defining the security privileges of end-users (e.g., spoke systems) and administrators of installed base data hub 102 .
- Exemplary rules include read-only access to installed base repository 204 , read-write access, and the like.
- one or more rules are associated with a security role, and one or more roles are associated with a hub user.
- a spoke system e.g., hub user
- a system administrator may be assigned a “super user” role consisting of additional privileges such as the ability to modify the configuration of security module 208 and data librarian 206 .
- security module 208 also includes one or more software and/or hardware components for managing access (e.g., authenticating and authorizing users) to hub 102 according to the security rules defined.
- Security module 208 may implement any one of a number of known authentication/authorization mechanisms, such as username/password, cryptographic keys, and the like.
- a role may comprise additional options defining the operation of hub 102 .
- an “end-user” role associated with spoke systems may include a “notification” option that controls how a spoke system is notified when data is updated in installed base repository 204 .
- a spoke system may be notified by e-mail when an update occurs.
- an “update” flag may be set in installed base repository 204 indicating that a change has been made.
- Subscription and publication interfaces 210 enable spoke systems such as 104 , 106 , 108 , 110 , 112 , 114 to read and write data to installed base repository 204 respectively.
- interfaces 210 are implemented as Application Programming Interfaces (“APIs”) using a standardized invocation format and parameter model, thereby allowing any heterogeneous system following the standardized format and model to access hub 102 .
- APIs Application Programming Interfaces
- subscription/publication interfaces 210 are implemented as Web Services. Interface 210 may also be implemented using any other standardized remote invocation interface such as CORBA, Java Remote Method Invocation (“RMI”), and the like.
- CORBA Java Remote Method Invocation
- RMI Java Remote Method Invocation
- Administrative module 212 consists of a user interface for managing aspects of hub 102 including installed base repository 204 , data librarian module 206 , and security module 208 .
- administrative module 212 may include functions for manually modifying the installed base data in the repository and changing the data model.
- data librarian 206 administrative module 212 may include functions for defining business rules/logic for resolving data conflicts, data merging, and data augmentation.
- security module 208 administrative module 212 may include functions for creating security rules, roles, and users, and defining the associations between each.
- the user interface of administrative module 212 is implemented as a Web-based form.
- the user interface may be implemented as any other type of software-based interface such as a proprietary application window, etc.
- FIG. 3 illustrates the steps performed in deploying an installed base data hub in accordance with one embodiment of the present invention.
- installed base data from various internal and external systems is consolidated. This step includes identifying the systems that contain relevant installed base data and importing/merging the data from those systems into installed base repository 204 . Importation can be performed using a streaming loader program (e.g., XML-based loader), a batch-based program, or through manual entry of data.
- a streaming loader program e.g., XML-based loader
- a batch-based program e.g., XML-based program
- data cleansing includes resolving data conflicts, removing duplicates, and augmenting the data to conform to a consistent format.
- security rules, roles, and users are defined.
- method 300 may be performed in an automated or semi-automated fashion.
- a deployment process or script may automatically consolidate data from a predefined list of source systems, cleanse the consolidated data, and setup a default set of security rules, roles, and users.
- each step ( 302 , 304 , 306 ) may be executed or initiated manually by a hub administrator.
- FIG. 3 provides a particular method of deploying an installed base data hub according to an embodiment of the present invention.
- Other sequences of steps may also be performed according to alternative embodiments.
- alternative embodiments of the present invention may perform the steps outlined above in a different order.
- the individual steps illustrated in FIG. 3 may include multiple sub-steps that may be performed in various sequences as appropriate to the individual step.
- additional steps may be added or removed depending on the particular applications.
- One of ordinary skill in the art would recognize many variations, modifications, and alternatives.
- FIG. 4 is a block diagram illustrating components of an exemplary system environment in which various embodiments of the present invention may be implemented.
- System 400 includes one or more hub servers 402 , one or more extra-enterprise application servers 406 , 410 , and one or more intra-enterprise application servers 414 , 418 .
- hub server 402 is configured to operate portions of an installed base data hub as described herein, such as the data librarian module, the security module, the subscription/publication interfaces, and the administrative module. Although only one hub server is shown, one of ordinary skill in the art will appreciate that any number of hub servers may be supported.
- Extra-enterprise servers 406 , 410 are configured to operate the information management systems of external partners such as service contractors and resellers.
- Intra-enterprise servers 414 , 418 are configured to operate various internal IT systems such as accounting/billing, product manufacturing, CRM, and the like. As shown in FIG. 4 , hub server 402 and intra-enterprise servers 414 , 418 are “internal” to source enterprise 426 (i.e., they reside inside the enterprise network boundary), whereas extra-enterprise servers 406 , 410 are “external” to source enterprise 426 (i.e., they reside outside the enterprise network boundary). In alternative embodiments, server computers 402 , 406 , 410 , 414 , 418 may all be resident on the same network.
- Server computers 402 , 406 , 410 , 414 , 418 may be general purpose computers, specialized server computers (including, merely by way of example, PC servers, UNIX servers, mid-range servers, mainframe computers rack-mounted servers, etc.), server farms, server clusters, or any other appropriate arrangement and/or combination.
- Each server 402 , 406 , 410 , 414 , 418 may run an operating system including various versions of Microsoft Windows and/or Apple Macintosh operating systems, UNIX or UNIX-like operating systems (including without limitation, the variety of GNU/Linux operating systems), as well as any other commercially-available server operating systems.
- Servers 402 , 406 , 410 , 414 , 418 may also run any of a variety of additional server applications and/or mid-tier applications, including HTTP servers, FTP servers, CGI servers, Java servers, database servers, and the like.
- Exemplary database servers include without limitation those commercially available from Oracle, Microsoft, Sybase, IBM and the like.
- extra-enterprise servers 406 , 410 and hub server 402 communicate via network 422 .
- intra-enterprise servers 414 , 418 and hub server 402 communicate via network 424 .
- Networks 422 , 424 may represent any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like.
- networks 422 , 424 can be a local area network (“LAN”), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth protocol known in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks.
- LAN local area network
- VPN virtual private network
- PSTN public switched telephone network
- wireless network e.g., a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth protocol known in the art, and/or any other wireless protocol
- System environment 400 may also include one or more databases 404 , 408 , 412 , 416 , 420 .
- database 404 represents a central data repository for installed base data hub 402 as described in the foregoing disclosure.
- Databases 404 , 408 , 412 , 416 , 420 may reside in a variety of locations.
- databases 404 , 408 , 412 , 416 , 420 may reside on a storage medium local to (and/or resident in) one or more of the server computers 402 , 406 , 410 , 414 , 418 .
- databases 404 , 408 , 412 , 416 , 420 may reside in one or more storage-area networks (“SAN”) familiar to those skilled in the art.
- SAN storage-area networks
- any necessary files for performing the functions attributed to the server computers 402 , 406 , 410 , 414 , 418 may be stored locally on the respective computer and/or remotely, as appropriate.
- databases 404 , 408 , 412 , 416 , 420 may be relational databases, such as Oracle 10g, that are adapted to store, update, and retrieve data in response to SQL-formatted commands.
- FIG. 5 illustrates an exemplary computer system 500 , in which various embodiments of the present invention may be implemented.
- the system 500 may be used to implement any of the computer systems described above.
- the computer system 500 is shown comprising hardware elements that may be electrically coupled via a bus 524 .
- the hardware elements may include one or more central processing units (CPUs) 502 , one or more input devices 504 (e.g., a mouse, a keyboard, etc.), and one or more output devices 506 (e.g., a display device, a printer, etc.).
- the computer system 500 may also include one or more storage devices 508 .
- the storage device(s) 508 may include devices such as disk drives, optical storage devices, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.
- RAM random access memory
- ROM read-only memory
- the computer-readable storage media reader 512 can further be connected to a computer-readable storage medium 510 , together (and, optionally, in combination with storage device(s) 508 ) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information.
- the communications system 514 may permit data to be exchanged with the network and/or any other computer described above with respect to the system environment 400 .
- the computer system 500 may also comprise software elements, shown as being currently located within a working memory 518 , including an operating system 520 and/or other code 522 , such as an application program (which may be a client application, Web browser, mid-tier application, RDBMS, etc.). It should be appreciated that alternative embodiments of a computer system 500 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
- an application program which may be a client application, Web browser, mid-tier application, RDBMS, etc.
- Storage media and computer readable media for containing code, or portions of code can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, data signals, data transmissions, or any other medium which can be used to store or transmit the desired information and which can be accessed by the computer.
- RAM random access memory
- ROM read only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory electrically erasable programmable read-only memory
- CD-ROM compact disc read-only memory
- DVD digital versatile disk
- magnetic cassettes magnetic tape
- magnetic disk storage magnetic disk storage devices
- data signals
Abstract
Description
Claims (16)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/775,425 US7747643B2 (en) | 2007-07-10 | 2007-07-10 | Installed base data hub |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/775,425 US7747643B2 (en) | 2007-07-10 | 2007-07-10 | Installed base data hub |
Publications (2)
Publication Number | Publication Date |
---|---|
US20090019434A1 US20090019434A1 (en) | 2009-01-15 |
US7747643B2 true US7747643B2 (en) | 2010-06-29 |
Family
ID=40254188
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/775,425 Active 2029-02-25 US7747643B2 (en) | 2007-07-10 | 2007-07-10 | Installed base data hub |
Country Status (1)
Country | Link |
---|---|
US (1) | US7747643B2 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8852921B2 (en) * | 2009-06-19 | 2014-10-07 | University Of Maryland Baltimore County | Non-invasive sensing of bioprocess parameters |
US20150010994A1 (en) * | 2012-02-15 | 2015-01-08 | University Of Maryland Baltimore County | Non-invasive sensing of bioprocess parameters |
US9582555B2 (en) * | 2012-09-06 | 2017-02-28 | Sap Se | Data enrichment using business compendium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6014641A (en) * | 1996-12-11 | 2000-01-11 | Walker Asset Management Limited Partnership | Method and apparatus for providing open-ended subscriptions to commodity items normally available only through term-based subscriptions |
US20030097330A1 (en) * | 2000-03-24 | 2003-05-22 | Amway Corporation | System and method for detecting fraudulent transactions |
US20070239858A1 (en) * | 2006-02-13 | 2007-10-11 | Infosys Technologies, Ltd. | Business to business integration software as a service |
US7343006B2 (en) * | 2003-09-25 | 2008-03-11 | Americas's Drive-In Corp. | Drive-in restaurant credit-card transaction system |
US7478058B2 (en) * | 2000-11-15 | 2009-01-13 | Spc Holdings Pty Limited | Collaborative commerce hub |
-
2007
- 2007-07-10 US US11/775,425 patent/US7747643B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6014641A (en) * | 1996-12-11 | 2000-01-11 | Walker Asset Management Limited Partnership | Method and apparatus for providing open-ended subscriptions to commodity items normally available only through term-based subscriptions |
US20030097330A1 (en) * | 2000-03-24 | 2003-05-22 | Amway Corporation | System and method for detecting fraudulent transactions |
US7478058B2 (en) * | 2000-11-15 | 2009-01-13 | Spc Holdings Pty Limited | Collaborative commerce hub |
US7343006B2 (en) * | 2003-09-25 | 2008-03-11 | Americas's Drive-In Corp. | Drive-in restaurant credit-card transaction system |
US20070239858A1 (en) * | 2006-02-13 | 2007-10-11 | Infosys Technologies, Ltd. | Business to business integration software as a service |
Non-Patent Citations (1)
Title |
---|
Oracle, Oracle Installed Base Concepts and Procedures, Release 11i, Apr. 2000. * |
Also Published As
Publication number | Publication date |
---|---|
US20090019434A1 (en) | 2009-01-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11782892B2 (en) | Method and system for migrating content between enterprise content management systems | |
JP7200259B2 (en) | Data retention handling for data object stores | |
US9646169B2 (en) | Systems, methods, and apparatuses for implementing cross organizational data sharing | |
US8874455B2 (en) | Convergence of customer and internal assets | |
US7580946B2 (en) | Smart integration engine and metadata-oriented architecture for automatic EII and business integration | |
US8694465B2 (en) | System and method for context sensitive mobile data and software update | |
US9110895B2 (en) | System and method for a serialized data service | |
US20160217423A1 (en) | Systems and methods for automatically generating application software | |
CN103827908A (en) | Systems and methods for a large-scale credit data processing architecture | |
JP2020053051A (en) | Integrated entity view across distributed systems | |
US20110219046A1 (en) | System, method and computer program product for managing data storage and rule-driven communications for a plurality of tenants | |
CN113704247A (en) | Method executed by database platform, database platform and medium | |
US20220138328A1 (en) | Validation of transaction ledger content using java script object notation schema definition | |
US9026623B2 (en) | Layered architectures for remote dynamic administration of distributed client configurations | |
US8726286B2 (en) | Modeling and consuming business policy rules | |
US7747643B2 (en) | Installed base data hub | |
US20150106151A1 (en) | Systems and Methods for Creating a Maturity Model Based Roadmap and Business Information Framework for Managing Enterprise Business Information | |
US9806969B2 (en) | Infrastructure trending tool | |
US9477821B2 (en) | Generic feature-licensing framework | |
US11323532B1 (en) | Data stream packaging | |
US11593509B1 (en) | Native applications using database roles | |
US20240037077A1 (en) | Self-service data mesh | |
US20230306126A1 (en) | Limiting cloud permissions in deployment pipelines | |
US20240054026A1 (en) | Federated distributed mutation | |
US20240078140A1 (en) | APPLICATION PROGRAMMING INTERFACE (API) ENABLER FOR UPDATED APIs |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GOSAIN, SUNNY HEMANT;REEL/FRAME:019665/0317 Effective date: 20070621 Owner name: ORACLE INTERNATIONAL CORPORATION,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:GOSAIN, SUNNY HEMANT;REEL/FRAME:019665/0317 Effective date: 20070621 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |