Generic software state machine

• US 6,138,171 A
• Filed: 11/12/1997
• Issued: 10/24/2000
• Est. Priority Date: 11/14/1996
• Status: Expired due to Fees

• Current Assignee: Tumbleweed Holdings LLC (Equitable IP Corporation)
• Original Assignee: Alcatel USA Sourcing L.P. (Nokia Corporation)
• Inventors: Walker, Joseph E.
• Primary Examiner(s): Cabeca, John W.
• Assistant Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US08/968,997
• Time in Patent Office: 1,077 Days
• Field of Search: 709/300, 709/303, 709/328, 709/315, 709/316, 709/317, 709/320, 709/318
• US Class Current: 719/318
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 9/4498 Finite state machines
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A generic software state machine (10) for implementing a software application in an object oriented environment includes a set of entity objects (20, 30) defined for software elements of the software application, a set of state objects (26, 34, 38, 40) defined for each entity object representative of states that the software element may enter, and a set of event objects (36, 42) defined for each state object representative of inputs that the software element may receive or actions the software element may encounter while in the state represented by the state object.

Claims

1. A generic software state machine for implementing a software application in an object oriented environment, comprising:

a set of state objects defined for each software element of the software application that the software element may enter, the set of state objects representing a number of behavior states that a particular one of the software elements may express, the particular one of the software elements being associated with a particular one of the state objects; and

a set of event objects defined for each state object representative of inputs that the software element may receive or actions the software element may encounter while being associated with the particular one of the state objects, the software element operable to change its association to another one of the state objects in response to the inputs received or actions encountered.

2. The generic software state machine, as set forth in claim 1, further comprising a set of entity objects defined for the software elements, the entity objects being associated with the set of state objects.

3. The generic software state machine, as set forth in claim 1, wherein each state object includes a state ID attribute.

4. The generic software state machine, as set forth in claim 1, wherein each state object comprises:

an entry member function for the state object for performing functions associated with the entry of the state represented by the state object by the entity object; and

an exit member function for the state object for preforming functions associated with the exit of the state represented by the state object by the entity object.

5. The generic software state machine, as set forth in claim 1, wherein the set of entity objects are grouped into a collection.

6. The generic software state machine, as set forth in claim 1, wherein the set of entity objects are grouped into an array.

7. The generic software state machine, as set forth in claim 1, further comprising a thread object adapted for receiving an input and creating a message object encapsulating the input, the message object having a message ID.

8. The generic software state machine, as set forth in claim 1, further comprising a timer class adapted to provide a set of timers, the timer class including:

an init member function adapted to create an array of timer queue head objects linked in a circular list, the timer queue head objects each begin a queue of timer entry objects;

an add timer member function adapted to add a timer entry object to a queue;

a remove timer member function adapted to delete a timer entry object from a queue; and

a tick member function adapted to advance the state of timer entry objects in one queue one clock tick.

9. The generic software state machine, as set forth in claim 1, further comprising a queue entry class adapted to provide and maintain a queue of objects, the queue entry class including:

a get next member function adapted to return contents of an object after a current object in the queue;

a get previous member function adapted to return contents of an object before a current object in the queue;

a set next member function adapted to update contents of an object after a current object in the queue with a passed value;

a set previous member function adapted to update contents of an object before a current object in the queue with a passed value; and

a remove entry member function adapted to remove an object in the queue.

10. The generic software state machine, as set forth in claim 2, wherein each entity object, state object, and event object includes an object ID attribute.

11. The generic software state machine, as set forth in claim 2, further comprising an event dictionary containing a mapping of message IDs to the addresses of the event objects.

12. The generic software state machine, as set forth in claim 7, further comprising a FSM map object adapted for receiving the message object from the thread object, and translating the message ID into an address of an entity object assigned for processing the message object.

13. The generic software state machine, as set forth in claim 7, wherein the entity object includes a process event member function adapted for processing the message.

14. The generic software state machine, as set forth in claim 8, wherein the timer entry object includes a process time out pure virtual member function adapted to perform actions when timer entry count expires.

15. The generic software state machine, as set forth in claim 10, further comprising an object dictionary containing a mapping of object IDs to the entity objects, state objects, and event objects.

16. The generic software state machine, as set forth in claim 12, wherein the entity object assigned for processing the message object is one of a collection of entity objects, the entity object being identifiable by an FSM instance ID contained in the message object.

17. The generic software state machine, as set forth in claim 15, further comprising a state dictionary containing a mapping of state IDs of the state objects to the addresses of the state objects.

18. A generic software state machine for implementing a software application in an object oriented environment, comprising:

a set of entity objects defined for software elements of the software application;

a set of state objects defined for each entity object representative of states that the software element may enter, the set of state objects representing a number of behavior states that a particular one of the software elements may express, the particular one of the software elements being associated with a particular one of the state objects; and

a set of event objects defined for each state object representative of inputs that the software element may receive or actions the software element may encounter while being associated with the particular one of the state objects, the software element operable to change its association to another one of the state objects in response to the inputs received or actions encountered.

19. The generic software state machine, as set forth in claim 18, wherein each entity object, state object, and event object includes an object ID attribute.

20. The generic software state machine, as set forth in claim 18, wherein each state object includes a state ID attribute.

21. The generic software state machine, as set forth in claim 18, further comprising an event dictionary containing a mapping of message IDs to the addresses of the event objects.

22. The generic software state machine, as set forth in claim 18, wherein the set of entity objects are grouped into a collection.

23. The generic software state machine, as set forth in claim 18, wherein the set of entity objects are grouped into an array.

24. The generic software state machine, as set forth in claim 18, further comprising a thread object adapted for receiving an input and creating a message object encapsulating the input, the message object having a message ID.

25. The generic software state machine, as set forth in claim 18, further comprising a timer class adapted to provide a set of timers, the timer class including:

an init member function adapted to create an array of timer queue head objects linked in a circular list, the timer queue head objects each begin a queue of timer entry objects;

an add timer member function adapted to add a timer entry object to a queue;

a remove timer member function adapted to delete a timer entry object from a queue; and

a tick member function adapted to advance the state of timer entry objects in one queue one clock tick.

26. The generic software state machine, as set forth in claim 18, further comprising a queue entry class adapted to provide and maintain a queue of objects, the queue entry class including:

a get next member function adapted to return contents of an object after a current object in the queue;

a get previous member function adapted to return contents of an object before a current object in the queue;

a set next member function adapted to update contents of an object after a current object in the queue with a passed value;

a set previous member function adapted to update contents of an object before a current object in the queue with a passed value; and

a remove entry member function adapted to remove an object in the queue.

27. The generic software state machine, as set forth in claim 19, further comprising an object dictionary containing a mapping of object IDs to the entity objects, state objects, and event objects.

28. The generic software state machine, as set forth in claim 20, further comprising a state dictionary containing a mapping of state IDs of the state objects to the addresses of the state objects.

29. The generic software state machine, as set forth in claim 18, wherein each state object comprises:

an entry member function for the state object for performing functions associated with the entry of the state represented by the state object by the entity object; and

an exit member function for the state object for preforming functions associated with the exit of the state represented by the state object by the entity object.

30. The generic software state machine, as set forth in claim 24, further comprising a FSM map object adapted for receiving the message object from the thread object, and translating the message ID into an address of an entity object assigned for processing the message object.

31. The generic software state machine, as set forth in claim 24, wherein the entity object includes a process event member function adapted for processing the message.

32. The generic software state machine, as set forth in claim 25, wherein the timer entry object includes a process time out pure virtual member function adapted to perform actions when timer entry count expires.

33. The generic software state machine, as set forth in claim 30, wherein the entity object assigned for processing the message object is one of a collection of entity objects, the entity object being identifiable by an FSM instance ID contained in the message object.