Communication protocol for synchronizing animation

• US 7,265,758 B2
• Filed: 12/19/2005
• Issued: 09/04/2007
• Est. Priority Date: 10/24/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: David, Paul, Calkins, Matt, Baioura, Andrei, Blanco, Leonardo
• Primary Examiner(s): Nguyen; Phu K.
• Application Number:
  US11/275,211
• Publication Number:
  US 20060103656A1
• Time in Patent Office: 624 Days
• Field of Search: 345473-475, 345531-535, 345501-505, 715781-782, 715793-794
• US Class Current: 345/473
• CPC Class Codes: G06F 9/545 where tasks reside in different layers, e.g. user- and kernel-space
• CPC Class Codes: G06T 13/00 Animation

Abstract

A communications protocol is described that governs asynchronous exchange of data between a high level animation system and a low level animation system. The high level animation system has a variable, medium-frequency frame rate and is optimized for interactivity. The low level animation system has a constant, high frequency frame rate and is optimized for high refresh frame rate. The communications protocol includes messages that can be sent by the high-level animation system to the low-level animation system to designate an animation and how the animation is to change over a specified period of time. As a result, the low-level system can display the animation at the high refresh rate even if animation data is not received from the high-level system for every frame.

Claims

1. A system, comprising:

a high-level animation subsystem to receive animation information from an application;

a low-level animation subsystem to render one or more animations according to the animation information;

a first timing engine to monitor one or more clocks in the low-level animation subsystem and to synchronize the clocks with one or more clocks in the high-level animation subsystem;

a second timing engine to monitor the one or more clocks in the high-level animation subsystem according to one or more high-level animation objects and to transmit animation messages to the first timing engine, the animation messages conforming to a communication protocol and designating one or more animation objects and how the animation objects are to change over a specified period of time;

wherein a high-level animation object communicates with a low-level animation object through the communication protocol messages to create and update the low-level animation object to reflect the high-level animation object; and

wherein the clocks and the animation objects are created and updated though the messages received at a variable rate from the high-level animation subsystem in a manner that provides the low-level animation subsystem with several frames of animation data that can be displayed at a high, constant display frame refresh rate, including a synchronize message that identifies one of the clocks associated with an animation to synchronize with a clock of the high-level animation subsystem.

2. The system as recited in claim 1, wherein the first timing engine synchronizes a clock in the low-level animation subsystem with a clock in the high-level animation subsystem by sending a “

synchronize with media slip”

message.

3. The system as recited in claim 1, wherein the communication protocol further includes a message from the group of messages consisting of:

a create clock message that identifies clock properties,

an update properties message that identifies updated clock properties,

an add interval message that adds a timing interval to clock properties,

a remove intervals message tat removes timing intervals from clock properties, and

a delete clock message that deletes a clock.

4. The system as recited in claim 1, wherein the communication protocol further includes a message from the group of messages consisting of:

a create animation message that creates an animation,

an update animation message that updates an existing animation,

a create animation collection that identifies multiple animations to be grouped,

an add animation to collection message that identifies an animation to add to an identified animation collection, and

a remove animation to collection message that identifies an animation to remove from an identified animation collection.

5. The system as recited in claim 1, wherein the communication protocol further includes a message from the group of messages consisting of:

a create static value message that identifies a value type and an initial value to display, and

an update static value message that identifies a static value to update and a new value for the static value.

6. An animation rendering subsystem, comprising:

one or more clocks;

a timing engine to track the one or more clocks;

one or more animation objects that identify at least a portion of an animation;

means for transmitting animation data to a low-level animation subsystem according to messages that identify at least one animation object in the low-level animation subsystem and provide data for changing the at least one identified animation object over a specified period of time; and

wherein the messages include a message selected from the group of messages consisting of a create static value message that identifies a value type and an initial value to render, and an update static value message that identifies a static value to update and a new value for the static value.

7. The animation rending subsystem as recited in claim 6, wherein the group of messages further consists of:

a create clock message that identifies initial clock properties,

an update properties message that identifies updated clock properties,

an add interval message that identifies an interval to be added to a clock,

a remove all intervals message that identifies a clock from which all intervals are to be removed, and

a delete clock message that identifies a clock to be deleted.

8. The animation rendering subsystem as recited in claim 6, wherein the group of messages further consists of:

a create animation message that describes an animation to create, and

an update animation message that identifies an animation to update and updated properties.

9. The animation rendering subsystem as recited in claim 6, wherein the group of messages further consists of:

a create animation collection message that identifies multiple animations that are to be grouped as one animation collection,

an add animation to collection message that identifies an animation to be added to an identified animation collection, and

a remove animation from collection message that identifies an animation to be removed from an identified animation collection.

10. A low-level animation subsystem, comprising:

one or more clocks;

one or more animation objects that identify at least a portion of an animation;

a timing engine to track the one or more clocks with respect to the one or more animation objects;

wherein the clocks and the animation objects are-created and updated through messages received at a variable rate from a high-level animation subsystem in a manner that provides the low-level animation subsystem with several frames of animation data that can be displayed at a high, constant display frame refresh rate, including a synchronize message that identifies one of the clocks associated with an animation to synchronize with a clock of the high-level animation subsystem.

11. A display device for a computing device, comprising:

an interface for communicatively coupling to a computer monitor; and

an animation rendering subsystem, comprising;

one or more clocks;

a timing engine to track the one or more clocks;

one or more animation objects that identify at least a portion of an animation;

means for transmitting animation data to a low-level animation subsystem according to messages that identify at least one animation object in the low-level animation subsystem and provide data for changing the at least one identified animation object over a specified period of time; and

wherein the messages include a message selected from the group of messages consisting of a create static value message that identifies a value type and an initial value to render, and an update static value message that identifies a static value to update and a new value for the static value.

12. The display device as recited in claim 11, wherein the group of messages further consists of:

a create clock message that identifies initial clock properties,

an update properties message that identifies updated clock properties,

an add interval message that identifies an interval to be added to a clock,

a remove all intervals message that identifies a clock from which all intervals are to be removed, and

a delete clock message that identifies a clock to be deleted.

13. The display device as recited in claim 11, wherein the group of messages further consists of:

a create animation message that describes an animation to create, and

an update animation message that identifies an animation to update and updated properties.

14. The display device as recited in claim 11, wherein the group of messages further consists of:

a create animation collection message that identifies multiple animations that are to be grouped as one animation collection,

an add animation to collection message that identifies an animation to be added to an identified animation collection, and

a remove animation from collection message that identifies an animation to be removed from an identified animation collection.