Service-oriented architecture (SOA) management of data repository

• US 8,589,338 B2
• Filed: 01/24/2008
• Issued: 11/19/2013
• Est. Priority Date: 01/24/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Maes, Stephane H.
• Primary Examiner(s): Boccio, Vincent F
• Application Number:
  US12/019,299
• Publication Number:
  US 20090193057A1
• Time in Patent Office: 2,126 Days
• Field of Search: 707/600, 707/602, 707/608, 707/706, 707/707, 707/733, 709/206, 709/219, 709/224, 709/225, 709/228, 715/741, 715/742, 715/743, 715/745
• US Class Current: 707/608
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers

Abstract

A data repository includes information for multiple data systems, which can each control data in this and a number of other domains. A business process can be launched by one of the data systems to update the target data and any related data in the repository or any other related repository. Any request to update data is intercepted and the business process can launch workflows and apply policies as needed to process the request. Workflows can be associated with the fields being updated or process being executed, such that any update to the target data is also accurately reflected in any other related system. Further, launching a workflow allows processes to be run before the data is updated, such that the data can be modified, added to, rejected, or otherwise processed before being added to the appropriate repositories.

Claims

1. A method of managing data in a data system, comprising:

executing by a Service Delivery Platform (SDP) a data management tool comprising an access layer providing an Application Program Interface (API) to one or more data management functions of the data management tool and a virtual directory layer providing a virtual directory representing a unified view of customer data related to a user of a service from each of a plurality of data repositories, each data repository within a different service domain of a plurality of service domains, each service domain controlled by at least one of a plurality of different data systems, wherein the customer data of each service domain comprises identity information for the user and information related to usage of the service of that domain by the user, wherein an identity of the user is different in each service domain, wherein the virtual directory federates the different identities of the user in the different domains by mapping the different identities to a unified identifier, and wherein the API of the virtual directory provides a single interface to the customer data from the plurality of service domains using the unified identifier;

receiving at the SDP a request from an application to update target customer data represented in the virtual directory and using the unified identifier, the target customer data being owned by one of the data systems and the request comprising a request from the application made through the API of the data management tool in a protocol of the API; and

launching by the SDP a business process in response to receiving the request, the business process being programmed to trigger at least one condition or action, or combination thereof, needed to update the target customer data represented in the virtual directory and related customer data in the plurality of service domains through the single interface of the virtual directory as a result of the request.

2. A method according to claim 1, wherein the request to update target customer data is further able result in at least one of triggering a workflow or policy that updates the customer data represented in the virtual directory, updating customer data and having a workflow triggered as a result, and causing a workflow or policy to be triggered that does not update the customer data represented in the virtual directory.

3. A method according to claim 1, wherein:

the business process is programmed to trigger at least one condition or action, or combination thereof, for any of the multiple data systems needed to update the target customer data and any related customer data in the plurality of service domains in order to process the request.

4. A method according to claim 1, further comprising:

generating by the SDP a notification when the target customer data and any related customer data is updated in response to the request.

5. A method according to claim 4, wherein:

generating a notification includes displaying a message at the source of the request.

6. A method according to claim 1, further comprising:

starting by the SDP a workflow to coordinate processing.

7. A method according to claim 1, further comprising:

storing by the SDP customer data in one of a distributed cache and a replicated cache for processing.

8. A method according to claim 1, wherein:

generating a notification is controlled by a policy.

9. A method according to claim 1, wherein:

launching a business process includes kicking off a workflow selected the workflow is a service-oriented architecture (SOA)-based workflow.

10. A method according to claim 1, further comprising:

obtaining by the SDP access to each of the plurality of data systems using a unified user profile the different identities for the user across the plurality of data repositories.

11. A method according to claim 1, wherein:

a timing of an update of any related customer data relative to the updating of the target customer data is determined by a policy.

12. A method according to claim 1, wherein:

launching a business process further includes applying a policy to reconcile the target customer data with related customer data stored in the plurality of service domains.

13. A method according to claim 1, wherein:

the business process is operable to kick off a workflow that is a service-oriented architecture (SOA)-based workflow.

14. A method according to claim 1, further comprising:

maintaining by the SDP policies defining which operations and updates are executed by the business process.

15. A method according to claim 1, wherein:

the plurality of data systems includes at least one of each of a business support system (BSS), an operations support system (OSS), a billing system, and a subscription system.

16. A method according to claim 15, wherein:

the customer data of each domain is related to a subscription to the service of the domain; and

the customer data is viewed in the virtual directory as aggregated from the BSS and OSS systems.

17. A method according to claim 16, wherein:

requests to change the customer data related to the subscription are consistent with related customer data in the BSS and OSS systems.

18. A method according to claim 17, further comprising:

executing by the SDP at least one SOA workflow to delegate to the BSS and OSS systems to update the relevant customer data to ensure consistency.

19. A method according to claim 1, wherein:

any update to the target customer data and any related customer data occur in real time.

20. The method of claim 1, wherein the protocol of the API comprises one of Java, Simple Object Access Protocol (SOAP), Lightweight Directory Access Protocol (LDAP), Diameter, Open Mobile Alliance Global System for Mobile communication (OMA GSM), and XML Configuration Access Protocol (XCAP).

21. A system for managing data across multiple data systems, comprising:

a plurality of different data systems, each data system maintaining a different data repository of a plurality of data repositories and each data system within a different service domain of a plurality of service domains wherein each repository maintains customer data related to a user of the service of that service domain, wherein the customer data of each service domain comprises identity information for the user and information related to usage of the service of that domain by the user and wherein an identity of the user is different in each service domain; and

a Service Delivery Platform (SDP) executing a data management tool comprising an access layer operable to provide an Application Program Interface (API) to one or more data management functions of the data management tool and a virtual directory layer providing a shared, unified view of customer data from the plurality of data repositories that federates the different identities of the user in the different domains by mapping the different identities to a unified identifier and providing through the API a single interface to customer data from the plurality of different data repositories, the data management tool operable to receive a request from an application through the API to update target customer data represented in the virtual directory using the unified identifier, the request comprising a request from the application made through the API of the data management tool in a protocol of the API, the data management tool being programmed to launch a business process in response to receiving the request, the business process being programmed to trigger an action for any of the plurality of data systems needed to update the target customer data represented in the virtual directory and any related customer data in the plurality of different data repositories through the single interface of the virtual directory in order to process the request.

22. A computer-readable memory device having stored thereon a sequence of instructions which, when executed by a processor, cause the processor to manage data across multiple different data systems by:

executing a data management tool comprising an access layer providing an Application Program Interface (API) to one or more data management functions of the data management tool and a virtual directory layer providing a virtual directory representing a unified view of customer data related to a user of a service from each of a plurality of data repositories, each data repository within a different service domain of a plurality of service domains, each service domain controlled by at least one of a plurality of different data systems, wherein the customer data of each service domain comprises identity information for the user and information related to usage of the service of that domain by the user, wherein an identity of the user is different in each service domain, wherein the virtual directory federates the different identities of the user in the different domains by mapping the different identities to a unified identifier, and wherein the API of the virtual directory provides a single interface to the customer data from the plurality of service domains using the unified identifier;

receiving a request from an application to update target customer data represented in the virtual directory using the unified identifier, the target customer data being owned by one of the data systems and the request comprising a request from the application made through the API of the data management tool in a protocol of the API; and

launching a business process in response to receiving the request, the business process being programmed to trigger an action for any of the multiple data systems needed to update the target customer data and any related customer data in the plurality of different data repositories through the single interface of the virtual directory in order to process the request.