Privacy management policy hub

• US 9,367,884 B2
• Filed: 12/09/2013
• Issued: 06/14/2016
• Est. Priority Date: 10/19/2007
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Yeap, Hwee Har, You, Catherine, Lu, Qin, Li, Jane, Hsieh, Weiwei, Chan, Lindy H.
• Primary Examiner(s): Richardson, James E
• Application Number:
  US14/100,325
• Publication Number:
  US 20140222706A1
• Time in Patent Office: 918 Days
• Field of Search: 707/602, 707/603, 707/689, 707/694, 707/695, 707/942, 707/999.102, 707/999.107, 726/1, 726/26, 726/27
• US Class Current: 1/1
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
• CPC Class Codes: G06Q 30/01 Customer relationship services
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety

Abstract

A system architecture is disclosed that includes a privacy management system. In particular, the privacy management system provides a policy hub for maintaining and managing customer privacy information. The privacy management system maintains a master data database for customer information and customer privacy preferences, and a rules database for privacy rules. The privacy management system captures, synchronizes, and stores customer privacy data. Privacy rules may be authored using a privacy management vocabulary, and can be customized for an enterprise'"'"'s privacy policies.

Claims

1. A computer implemented method comprising:

evaluating, by a processor of a computer system, a privacy rule by accessing a privacy knowledgebase;

in response to the evaluating, storing a privacy preference in a privacy database, wherein

the privacy database is stored in a computer readable storage medium of the computer system,

a privacy process module is communicatively coupled to the privacy database,

the privacy preference corresponds to the privacy rule;

generating, by the processor, a cleansed record by cleansing a legacy record, wherein

generating the cleansed record comprises;

retrieving the legacy record, wherein the privacy process module receives the legacy record from a legacy computer system as part of an insert operation, and wherein the privacy process module determines if a best version record associated with the legacy computer system exists in the database,

determining, by the processor, that the insert operation is a real-time insert operation;

determining, by the processor, whether customer data management (CDM) is active,

if the CDM is not active,

inserting the legacy record into the best version record; and

if the CDM is active,

performing the cleansing of the legacy record based at least in part on the privacy preference, and

inserting the cleansed legacy record into the best version record if no match for the legacy record is found in the best version record.

2. The method of claim 1, wherein

the legacy record is retrieved from a legacy database via a business integration system,

the legacy record is transformed into a common format record, and

the generating the cleansed record further comprises

cleansing the common format record using a data quality module, and

processing the common format record according to a privacy workflow.

3. The method of claim 1, further comprising:

determining whether the match is a manual match;

if the match is the manual match,

temporarily inserting the source into a source data and history table,

inserting the cleansed legacy record into the source data and history table, and

removing the source from the source data and history table after performing a deduplication operation in the CDM.

4. The method of claim 3, further comprising:

determining that survivorship is active if the match is an auto match by accessing a survivorship engine comprised in the privacy process module;

performing survivorship processing according to one or more survivorship rules; and

updating the best version record.

5. The method of claim 4, wherein processing the survivorship further comprises:

determining whether the source is trusted, and

if the source is trusted, determining whether privacy data received from the source as part of the legacy record can be used to update one or more fields of the best version record based one or more survivorship rules.

6. A privacy management system comprising:

one or more processors;

a computer readable storage medium coupled to the one or more processors;

a privacy database stored in the computer readable storage medium; and

instructions stored in the computer readable storage medium executable by the one or more processors to

evaluate a privacy rule by accessing a privacy knowledgebase;

in response to the evaluating, store a privacy preference in the privacy database, wherein

a privacy process module is communicatively coupled to the privacy database,

the privacy preference corresponds to the privacy rule;

generate a cleansed record by cleansing a legacy record, wherein the generating the cleansed record comprises;

retrieving the legacy record, wherein the privacy process module receives the legacy record from a legacy computer system as part of an insert operation, and wherein the privacy process module determines if a best version record associated with the legacy computer system exists in the privacy database,

determine that the insert operation is a real-time insert operation;

determine whether customer data management (CDM) is active,

if the CDM is not active,

insert the legacy record into the best version record; and

if the CDM is active,

perform the cleansing of the legacy record based at least in part on the privacy preference, and

insert the cleansed legacy record into the best version record if no match for the legacy record is found in the best version record.

7. The privacy management system of claim 6, wherein

the legacy record is retrieved from a legacy database via a business integration system,

the legacy record is transformed into a common format record, and

the generating the cleansed record further comprises

cleansing the common format record using a data quality module, and

processing the common format record according to a privacy workflow.

8. The privacy management system of claim 6, further comprising:

determining whether the match is a manual match;

if the match is the manual match,

temporarily inserting the source into a source data and history table,

inserting the cleansed legacy record into the source data and history table, and

removing the source from the source data and history table after performing a deduplication operation in the CDM.

9. The privacy management system of claim 8, further comprising:

determining that survivorship is active if the match is an auto match by accessing a survivorship engine comprised in the privacy process module;

performing survivorship processing according to one or more survivorship rules; and

updating the best version record.

10. The privacy management system of claim 9, wherein processing the survivorship further comprises:

determining whether the source is trusted, and

if the source is trusted, determining whether privacy data received from the source as part of the legacy record can be used to update one or more fields of the best version record based one or more survivorship rules.

11. A non-transitory computer program product comprising non-transitory computer readable storage media comprising a plurality of instructions executable on a computer system, wherein the plurality of instructions are configured to

evaluate, by a processor of the computer system, a privacy rule by accessing a privacy knowledgebase;

in response to the evaluating, store a privacy preference in a privacy database, wherein

the privacy database is stored in the computer readable storage medium of the computer system,

a privacy process module is communicatively coupled to the privacy database,

the privacy preference corresponds to the privacy rule;

generate, by the processor, a cleansed record by cleansing a legacy record, wherein generating the cleansed record comprises

retrieving the legacy record, wherein the privacy process module receives the legacy record from a legacy computer system as part of an insert operation, and wherein the privacy process module determines if a best version record associated with the legacy computer system exists in the privacy database;

determine, by the processor, that, the insert operation is a real-time insert operation;

determine, by the processor, whether customer data management (CDM) is active,

if the CDM is not active,

insert the legacy record into the best version record; and

if the CDM is active,

perform the cleansing of the legacy record based at least in part on the privacy preference, and

insert the cleansed legacy record into the best version record if no match for the legacy record is found in the best version record.

12. The non-transitory computer program product of claim 11, wherein

the legacy record is retrieved from a legacy database via a business integration system,

the legacy record is transformed into a common format record, and

the generating the cleansed record further comprises

cleansing the common format record using a data quality module, and

processing the common format record according to a privacy workflow.

13. The non-transitory computer program product of claim 11, further comprising:

determining whether the match is a manual match;

if the match is the manual match,

temporarily inserting the source into a source data and history table,

inserting the cleansed legacy record into the source data and history table, and

removing the source from the source data and history table after performing a deduplication operation in the CDM.

14. The non-transitory computer program product of claim 13, further comprising:

determining that survivorship is active if the match is an auto match by accessing a survivorship engine comprised in the privacy process module;

performing survivorship processing according to one or more survivorship rules, wherein the survivorship processing comprises

determining whether the source is trusted, and

if the source is trusted, determining whether privacy data received from the source as part of the legacy record can be used to update one or more fields of the best version record based one or more survivorship rules; and

updating the best version record.