Revision locking

• US 10,095,500 B2
• Filed: 03/06/2015
• Issued: 10/09/2018
• Est. Priority Date: 09/30/2014
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Pollack, Daniel B., Brown, Eric S., Novick, Gregory B., Chinn, Paul W., Donley, David C., Hawkins, Tyler D., Poumailloux, Julien A.
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): BERMAN, STEPHEN DAVID
• Application Number:
  US14/640,324
• Publication Number:
  US 20160092189A1
• Time in Patent Office: 1,313 Days
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

When a new version of a first program is to be installed on a first device, metadata supplied to that device specifies which versions of a second program stored on a second device are compatible with the new version. The first device uses this metadata to determine a compatibility classification that indicates how compatible the current version of the second program and the new version of the first program are, and transitions to a state representative of this compatibility classification. A process executing on the first device receives messages from applications executing on the first device. The process reads mappings between these applications and the message types these applications send. The process forwards an application'"'"'s message to the second device if the application sends a message type allowable in the first device'"'"'s state. Otherwise, the process queues that message at least until the first device transitions to a different state.

Claims

1. A method of varying delivery of different types of messages based on device state and message origin, the method comprising:

at a first device having one or more processors, performing, by a filter executing on the first device;

receiving a first message from a first application executing on the first device;

reading a set of stored mappings that includes a first mapping, wherein the first mapping maps the first application to a first set of two or more message types comprising at least one of an update message type, a configuration message type, or a compatibility message type;

determining, based on the first mapping and a program version of the first application, that the first application sends messages of the first set of two or more message types, the first message being of one of the first set of two or more message types;

determining a first state of the first device, the first state of the first device defining;

that messages of a first message type of the two or more message types are allowed to pass to or from the first device; and

that messages of a second message type of the two or more message types are prohibited from passing to or from the first device;

determining the first state corresponds to the first message type;

determining whether the first message type corresponding to the first state is a member of the first set of two or more message types;

in response to determining that the first message type is not a member of the first set of two or more message types, holding the first message in a queue until the first device transitions to a different state corresponding to a message type that is contained in the first set of two or more message types; and

in response to the first device transitioning to the different state corresponding to the message type that is contained in the first set of two or more message types, sending the first message from the queue.

2. The method of claim 1, further comprising, at the first device:

determining that the first device has transitioned from the different state to a second state different from the first state and the different state;

determining whether the second message type corresponding to the second state is a member of the first set of two or more message types; and

in response to determining that the second message type is a member of the first set of two or more message types, removing a second message from the queue and sending the second message from the first device to a second device separate from the first device.

3. The method of claim 1, further comprising, at the first device:

receiving a second message from a second application executing on the first device separately from the first application;

wherein the set of stored mappings further includes a second mapping, wherein the second mapping maps the second application to a second set of one or more message types;

determining, based on the second mapping and the program version of the second application, that the second application sends messages of the second set of one or more message types;

determining whether the first message type corresponding to the first state is a member of the second set of one or more message types; and

in response to determining that the first message type is a member of the second set of one or more message types, sending the second message from the first device to a second device separate from the first device.

4. The method of claim 1, further comprising, at the first device:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program;

determining that the particular compatibility classification indicates that the current version of the second program is compatible with the particular version of the first program but requires a user configuration of the second program on the second device;

transitioning the first device to a configuration state in which transmission of messages of the configuration message type from the first device to the second device is permitted;

transmitting the first message from the first device to the second device;

determining that the user configuration of the second program has been performed on the second device; and

in response determining that the user configuration of the second program has been performed, installing the particular version of the first program on the first device and transitioning the first device from the configuration state to a general state in which transmission of messages of all message types from the first device is permitted.

5. The method of claim 4, wherein determining that the user configuration of the second program has been performed on the second device comprises:

receiving user input that confirms that a user has set values of one or more parameters used by the second program.

6. The method of claim 1, further comprising, at the first device:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program;

determining that the particular compatibility classification indicates that the current version of the second program is incompatible with the particular version of the first program;

transitioning the first device to an update state in which transmission of messages of the update message type from the first device to the second device is permitted;

transmitting the first message from the first device to the second device;

determining that an update of the second program has been performed on the second device; and

in response determining that the update of the second program has been performed on the second device, rebooting the first device.

7. The method of claim 1, further comprising, at the first device:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program; and

determining that the particular compatibility classification indicates that the current version of the second program is compatible with the particular version of the first program;

installing the particular version of the first program on the first device; and

transitioning the first device to a general state in which transmission of messages of all message types from the first device is permitted.

23. The method of claim 1, wherein the first state includes one of an update state, a configuration state, a compatibility state, or a general state.

26. The method of claim 1, wherein the first device is in the first state at least during a program update procedure in which the application is updated from the program version to an updated program version.

27. The method of claim 1, further comprising:

receiving compatibility classification data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with the program version of the first application on the first device; and

transitioning the first device from a general state to the first state based at least in part on the compatibility classification data, the first device being configured to update the program version of the first application when in the first state.

8. A non-transitory computer-readable storage memory storing instructions which, when executed by one or more processors of a first device, cause the one or more processors to perform operations comprising:

receiving a first message from a first application executing on the first device;

reading a set of stored mappings that includes a first mapping, wherein the first mapping maps the first application to a first set of two or more message types comprising at least one of an update message type, a configuration message type, or a compatibility message type;

determining, based on the first mapping and a program version of the first application, that the first application sends messages of the first set of two or more message types, the first message being of one of the first set of two or more message types;

determining a first state of the first device, the first state of the first device defining;

that messages of the first message type of the two or more message types are allowed to pass to or from the first device; and

that messages of a second message type of the two or more message types are prohibited from passing to or from the first device;

determining the first state corresponds to the first message type;

determining whether the first message type corresponding to the first state is a member of the first set of two or more message types;

in response to determining that the first message type is not a member of the first set of two or more message types, holding the first message in a queue until the first device transitions to a different state corresponding to a message type that is contained in the first set of two or more message types; and

in response to the first device transitioning to the different state corresponding to the message type that is contained in the first set of two or more message types, sending the first message from the queue.

9. The non-transitory computer-readable storage memory of claim 8, wherein the operations further comprise:

determining that the first device has transitioned from the different state to a second state different from the first state and the different state;

determining whether the second message type corresponding to the second state is a member of the first set of two or more message types; and

in response to determining that the second message type is a member of the first set of two or more message types, removing a second message from the queue and sending the second message from the first device to a second device separate from the first device.

10. The non-transitory computer-readable storage memory of claim 8, wherein the operations further comprise:

receiving a second message from a second application executing on the first device separately from the first application;

wherein the set of stored mappings further includes a second mapping, wherein the second mapping maps the second application to a second set of one or more message types;

determining, based on the second mapping and the program version of the second application, that the second application sends messages of the second set of one or more message types;

determining whether the first message type corresponding to the first state is a member of the second set of one or more message types; and

in response to determining that the first message type is a member of the second set of one or more message types, sending the second message from the first device to a second device separate from the first device.

11. The non-transitory computer-readable storage memory of claim 8, wherein the operations further comprise:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program;

determining that the particular compatibility classification indicates that the current version of the second program is compatible with the particular version of the first program but requires a user configuration of the second program on the second device;

transitioning the first device to a configuration state in which transmission of messages of the configuration message type from the first device to the second device is permitted;

transmitting the first message from the first device to the second device;

determining that the user configuration of the second program has been performed on the second device; and

in response determining that the user configuration of the second program has been performed, installing the particular version of the first program on the first device and transitioning the first device from the configuration state to a general state in which transmission of messages of all message types from the first device is permitted.

12. The non-transitory computer-readable storage memory of claim 11, wherein determining that the user configuration of the second program has been performed on the second device comprises:

receiving user input that confirms that a user has set values of one or more parameters used by the second program.

13. The non-transitory computer-readable storage memory of claim 8, wherein the operations further comprise:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program;

determining that the particular compatibility classification indicates that the current version of the second program is incompatible with the particular version of the first program;

transitioning the first device to an update state in which transmission of messages of the update message type from the first device to the second device is permitted;

transmitting the first message from the first device to the second device;

determining that an update of the second program has been performed on the second device; and

in response determining that the update of the second program has been performed on the second device, rebooting the first device.

14. The non-transitory computer-readable storage memory of claim 8, wherein the operations further comprise:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program; and

determining that the particular compatibility classification indicates that the current version of the second program is compatible with the particular version of the first program;

installing the particular version of the first program on the first device; and

transitioning the first device to a general state in which transmission of messages of all message types from the first device is permitted.

24. The non-transitory computer-readable storage memory of claim 8, wherein the first state includes one of an update state, a configuration state, a compatibility state, or a general state.

15. A first device comprising:

one or more processors; and

a non-transitory computer-readable storage memory coupled to the one or more processors and storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising;

receiving a first message from a first application executing on the first device;

reading a set of stored mappings that includes a first mapping, wherein the first mapping maps the first application to a first set of two or more message types comprising at least one of an update message type, a configuration message type, or a compatibility message type;

determining, based on the first mapping and a program version of the first application, that the first application sends messages of the first set of two or more message types, the first message being of one of the first set of two or more message types;

determining a first state of the first device, the first state of the first device defining;

that messages of the first message type of the two or more message types are allowed to pass to or from the first device; and

that messages of a second message type of the two or more message types are prohibited from passing to or from the first device;

determining the first state corresponds to a first message type;

determining whether the first message type corresponding to the first state is a member of the first set of two or more message types;

in response to determining that the first message type is not a member of the first set of two or more message types, holding the first message in a queue until the first device transitions to a different state corresponding to a message type that is contained in the first set of two or more message types; and

in response to the first device transitioning to the different state corresponding to the message type that is contained in the first set of two or more message types, sending the first message from the queue.

16. The first device of claim 15, wherein the operations further comprise:

determining that the first device has transitioned from the different state to a second state different from the first state and the different state;

determining whether the second message type corresponding to the second state is a member of the first set of two or more message types; and

in response to determining that the second message type is a member of the first set of two or more message types, removing a second message from the queue and sending the second message from the first device to a second device separate from the first device.

17. The first device of claim 15, wherein the operations further comprise:

receiving a second message from a second application executing on the first device separately from the first application;

wherein the set of stored mappings further includes a second mapping, wherein the second mapping maps the second application to a second set of one or more message types;

determining, based on the second mapping and the program version of the second application, that the second application sends messages of the second set of one or more message types;

determining whether the first message type corresponding to the first state is a member of the second set of one or more message types; and

in response to determining that the first message type is a member of the second set of one or more message types, sending the second message from the first device to a second device separate from the first device.

18. The first device of claim 15, wherein the first message type is a configuration message type or an update message type.

19. The first device of claim 15, wherein the operations further comprise:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program;

determining that the particular compatibility classification indicates that the current version of the second program is compatible with the particular version of the first program but requires a user configuration of the second program on the second device;

transitioning the first device to a configuration state in which transmission of messages of the configuration message type from the first device to the second device is permitted;

transmitting the first message from the first device to the second device;

determining that the user configuration of the second program has been performed on the second device; and

in response determining that the user configuration of the second program has been performed, installing the particular version of the first program on the first device and transitioning the first device from the configuration state to a general state in which transmission of messages of all message types from the first device is permitted.

20. The first device of claim 19, wherein determining that the user configuration of the second program has been performed on the second device comprises:

receiving user input that confirms that a user has set values of one or more parameters used by the second program.

21. The first device of claim 15, wherein the operations further comprise:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program;

determining that the particular compatibility classification indicates that the current version of the second program is incompatible with the particular version of the first program;

transitioning the first device to an update state in which transmission of messages of the update message type from the first device to the second device is permitted;

transmitting the first message from the first device to the second device;

determining that an update of the second program has been performed on the second device; and

in response determining that the update of the second program has been performed on the second device, rebooting the first device.

22. The first device of claim 15, wherein the operations further comprise:

receiving compatibility data that indicates a set of compatibility classifications that indicate how compatible versions of a second program are with a particular version of a first program that is to be installed on the first device;

determining, based on the compatibility data, a particular compatibility classification that indicates how compatible a current version of the second program stored on a second device separate from the first device is with the particular version of the first program; and

determining that the particular compatibility classification indicates that the current version of the second program is compatible with the particular version of the first program;

installing the particular version of the first program on the first device; and

transitioning the first device to a general state in which transmission of messages of all message types from the first device is permitted.

25. The first device of claim 15, wherein the first state includes one of an update state, a configuration state, a compatibility state, or a general state.