Systems and methods for receiving and sending messages about changes to data attributes

• US 8,584,140 B2
• Filed: 09/19/2008
• Issued: 11/12/2013
• Est. Priority Date: 09/21/2007
• Status: Expired due to Fees

• Current Assignee: Presenceid Incorporated
• Original Assignee: Presenceid Incorporated
• Inventors: Walker, Douglas Jock, Van Ommeren, Reinier
• Primary Examiner(s): Truong, Lechi
• Assistant Examiner(s): Kraft, Shih-Wei
• Application Number:
  US12/234,256
• Publication Number:
  US 20090183175A1
• Time in Patent Office: 1,880 Days
• Field of Search: None
• US Class Current: 719/313
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Systems and methods for receiving and sending messages about changes to data attributes are described. A message that includes all common data attributes associated with a first reference object is received. The data attributes in the message are mapped to common data attributes in a second reference object. The type of the message is determined, where the message is either a synchronization message or a key change message. The common data attributes in the second reference object are updated to match the common data attributes in the first reference object if the message is a synchronization message. A unique data attribute in the second reference object is updated if the message is a key change message.

Claims

1. A method for receiving and sending messages about changes to data attributes, comprising:

receiving, by a computing device comprising a processor and memory, a message that includes all common data attributes associated with a first reference object and a unique data attribute associated with the first reference object, wherein the message includes all common data attributes;

mapping, by the computing device, the data attributes in the message to common data attributes in a second reference object, wherein the mapping comprises determining how data from one schema can be copied into another schema;

determining, by the computing device, whether the message is a synchronization message or a key change message

updating, by the computing device, the common data attributes in the second reference object to match the common data attributes in the first reference object if the message is a synchronization message;

updating, by the computing device, a unique data attribute in the second reference object if the message is a key change message;

sending an acknowledgement message acknowledging receipt of the message; and

sending a completion message in response to updating the second reference object, wherein the acknowledgement message and the completion message are sent only in response to a request that is received by the computing device,

wherein the computing device further comprises a queue record that indicates that a change has been made to a common data attribute in the first reference object, wherein the change in the queue record is accepted or rejected by an authenticator that has been programmed to accept or reject the queue record based upon the common data attribute in the first reference object being a particular common data attribute that is being changed.

2. The method of claim 1, wherein the mapping comprises standard data mapping, and wherein at least one common data attribute value in the second reference object is identical to at least one common data attribute value in the first reference object.

3. The method of claim 1, wherein the mapping comprises disjointed data mapping, and wherein at least one common data attribute value in the second reference object is not identical to at least one common data attribute value in the first reference object.

4. The method of claim 1, wherein the mapping comprises static value mapping, and wherein at least one common data attribute value in the second reference object is chosen from a predetermined list and is not identical to at least one common data attribute value in the first reference object.

5. The method of claim 4, wherein the mapping further comprises using a table to identify an equivalent value for each of the at least one common data attribute value in the first reference object.

6. The method of claim 1, wherein the second reference object comprises fewer common data attributes than the first reference object.

7. The method of claim 6, wherein the message is received using the Simple Object Access Protocol (SOAP).

8. The method of claim 7, wherein a message indicating the change will be constructed if the queue record is accepted but will not be constructed if the queue record is rejected.

9. An apparatus for receiving and sending messages about changes to data attributes, comprising:

a processor;

memory in electronic communication with the processor;

instructions stored in the memory, the instructions being executable by the processor to;

receive a message that includes all common data attributes associated with a first reference object and a unique data attribute associated with the first reference object, wherein the message includes all common data attributes;

map the data attributes in the message to common data attributes in a second reference object, wherein the instructions for mapping are further executable to determine how data from one schema can be copied into another schema;

determine whether the message is a synchronization message or a key change message;

update the common data attributes in the second reference object to match the common data attributes in the first reference object if the message is a synchronization message;

update a unique data attribute in the second reference object if the message is a key change message;

send an acknowledgement message acknowledging receipt of the message; and

send a completion message in response to updating the second reference object, wherein the acknowledgement message and the completion message are sent only in response to a request that is received,

wherein the instructions are further executable by the processor to form a queue record that indicates that a change has been made to a common data attribute in the first reference object, wherein the change in the queue record is accepted or rejected by an authenticator that has been programmed to accept or reject the queue record based upon the common data attribute in the first reference object being a particular common data attribute that is being changed.

10. The apparatus of claim 9, wherein the instructions for mapping are further executable to perform standard data mapping, and wherein at least one common data attribute value in the second reference object is identical to at least one common data attribute value in the first reference object.

11. The apparatus of claim 9, wherein the instructions for mapping are further executable to perform disjointed data mapping, and wherein at least one common data attribute value in the second reference object is not identical to at least one common data attribute value in the first reference object.

12. The apparatus of claim 9, wherein the instructions for mapping are further executable to perform static value mapping, and wherein at least one common data attribute value in the second reference object is chosen from a predetermined list and is not identical to at least one common data attribute value in the first reference object.

13. The apparatus of claim 12, wherein the instructions for mapping are further executable to use a table to identify an equivalent value for each of the at least one common data attribute value in the first reference object.

14. The apparatus of claim 9, wherein the second reference object comprises fewer common data attributes than the first reference object.

15. The apparatus of claim 9, wherein the instructions for receiving are further executable to receive using the Simple Object Access Protocol (SOAP).

16. A non-transitory computer-readable medium for receiving and sending messages about changes to data attributes, the computer readable medium comprising executable instructions for:

receiving a message that includes all common data attributes associated with a first reference object and a unique data attribute associated with the first reference object, wherein the message includes all common data attributes;

mapping the data attributes in the message to common data attributes in a second reference object, wherein the mapping comprises determining how data from one schema can be copied into another schema;

determining whether the message is a synchronization message or a key change message;

updating the common data attributes in the second reference object to match the common data attributes in the first reference object if the message is a synchronization message;

updating a unique data attribute in the second reference object if the message is a key change message;

sending an acknowledgement message acknowledging receipt of the message; and

sending a completion message in response to updating the second reference object, wherein the acknowledgement message and the completion message are sent only in response to a request that is received,

wherein the computer readable medium further comprises instructions for forming a queue record that indicates that a change has been made to a common data attribute in the first reference object, wherein the change in the queue record is accepted or rejected by an authenticator that has been programmed to accept or reject the queue record based upon the common data attribute in the first reference object being a particular common data attribute that is being changed.