1460777300-ad08f47c-da8b-411a-aea3-d5a46ee866fe

1. A method of determining an event instance in an event driven communications system, the method comprising the steps of:
receiving an event stream, the event stream comprising a plurality of events;
retrieving metadata for each event of the received event stream;
instantiating an event instance for each event of the received event stream based on the retrieved metadata; and
reading event data of each event of the received event stream into the instantiated event instance.
2. A method according claim 1, wherein the method further comprises:
retrieving an event class name for each event of the received event stream;
and wherein the step of instantiating an event instance comprises instantiating an event instance for each event of the received event stream based on the retrieved metadata and event class name.
3. A method according to claim 2, wherein the step of retrieving metadata and an event class name for each event comprises the steps of:
retrieving an identifier of each event of the received event stream;
retrieving metadata from an event metadata library associated with the retrieved identifier of each event of the received event stream; and
retrieving an event class name from an event class library associated with the retrieved identifier of each event of the received event stream.
4. A method according to claim 2, wherein the step of reading event data of the received event stream into the instantiated event instance comprises:
reading event data of each event into an event base class associated with the retrieved event class name.
5. A method according to claim 1, wherein the event may comprise different versions of events, and the step of retrieving metadata and an event class name for each event of the received event stream further comprises:
retrieving metadata and an event class name for each event of the received event stream for the version of event.
6. A method according to claim 3, wherein the method further comprises:
maintaining an event metadata library by:
loading all versions of event metadata XML files for all event sources and correlations;
extracting metadata from the event metadata XML files; and
updating an event metadata library with the extracted metadata.
7. A method according to claim 6, wherein the method further comprises:
generating event mappings comprising:
selecting fields from a base event for the event being mapped, the base event comprising all fields of all versions of the event from a source; and
generating the event mapping from the selected fields.
8. A method according to claim 7, wherein the method further comprises:
generating a base class for each event from each event source and storing the base class in the event class library; and
generating a sub class of the mapped event for every version of the event indicated by the metadata and storing the sub class in the event class library, associated with its corresponding base class.
9. A method of controlling event-driven communication between a plurality of nodes of a network, the method comprising the steps of:
establishing a session for communication, the session being defined by a plurality of event instances, the event instances being determined by the steps of:
receiving an event stream, the event stream comprising a plurality of events;
retrieving metadata for each event of the received event stream;
instantiating an event instance for each event of the received event stream based on the retrieved metadata; and
reading event data of each event of the received event stream into the instantiated event instance.
10. A method according to claim 1, wherein the method further comprises:
correlating at least two of the instantiated events by:
creating correlation rules between the at least two instantiated event instances using the metadata associated with each instantiated event instance; and

generating at least one correlated event instance from the at least two instantiated event instances by applying the created correlation rules.
11. A method according to claim 1, wherein the method further comprises:
buffering each instantiated event instance; and
publishing a plurality of the buffered instantiated event instances to a distributed event bus.
12. A method according to claim 11, wherein the method further comprises:
subscribing to and accessing event instances from the distributed bus.
13. A method according to claim 1, wherein the method further comprises:
storing instantiated event instances to a database management system.
14. A method according to claim 1, wherein the method further comprises:
forwarding event instances to external systems.
15. A method according to claim 1, wherein the method further comprises; filtering a predetermined type of events from the received event stream prior to the step of retrieving.
16. An apparatus for determining an event instance in an event driven communications system, the apparatus comprising:
a receiver configured to receive an event stream, the event stream comprising a plurality of events;
a library interface configured to retrieve metadata from an event metadata library for each event of the received event stream; and
an instantiator configured to instantiate an event instance for each event of the received event stream based on the retrieved metadata and to read event data of each event of the received event stream into the instantiated event instance.
17. An apparatus according to claim 16, wherein the receiver further comprises:
a filter configured to filter a predetermined type of events from the event stream.
18. A communication control module for controlling event-driven communication between a plurality of nodes of a network, the module comprising:
a session control module configured to establish a session for communication between a plurality of nodes, the session being defined by a plurality of event instances; and
an apparatus according to claim 16 for determining the plurality of event instances for each session.
19. A communication control module according to claim 18, wherein the module further comprises:
a correlator configured to correlate at least two of the instantiated events by
creating correlation rules between the at least two instantiated event instances using the metadata associated with each instantiated event instance; and

generating at least one correlated event instance from the at least two instantiated event instances by applying the created correlation rules.
20. A communication control module according to claim 18, wherein the module further comprises:
a publisher configured to publish a plurality of the instantiated event instances to a distributed event bus.
21. A communication control module according to claim 18, wherein the publisher further comprises:
a buffer configured to store a plurality of the instantiated event instances to a distributed event bus; and wherein the publisher is further configured to publish a buffered plurality of instantiated event instances.
22. A communication control module according to claim 18, wherein the module further comprises:
a subscriber configured to subscribe to and access event instances from the distributed bus.
23. A communication control module according to claim 18, wherein the module further comprises:
a persister configured to store instantiated event instances to a database management system.
24. A communication control module according to claim 18, wherein the module further comprises:
a forwarder configured to forward event instances to external systems.

The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.

1. A method for virtualization of physical storage, the method comprising:
mapping each of a plurality of virtual units in a virtual disk to a single one of a plurality of physical units in physical storage; and
mapping a virtual address within a virtual unit to any physical address within the single one of the plurality of physical units.
2. The method of claim 1, further comprising:
dividing data associated with a first write operation to a first virtual address within a first of the plurality of virtual units into chunks; and
allocating a first set of data blocks in a first physical unit mapped to the first of the plurality of virtual units for each chunk.
3. The method of claim 2, wherein each chunk is compressed before the allocating.
4. The method of claim 3, further comprising:
dividing data associated with a second write operation to the first virtual address into chunks;
compressing chunks associated with second write operation; and
allocating a second set of data blocks for each chunk from overflow reserve storage that is located within the first physical unit if the size of any of the compressed chunks associated with the second write operation exceeds the size of the previously allocated first set of data blocks.
5. The method of claim 4, wherein the overflow reserve storage is located within a page that also includes the first set of data blocks.
6. The method of claim 5, wherein the overflow reserve storage is located within a subpage of the page, wherein the subpage also includes the first set of data blocks.
7. The method of claim 3, further comprising:
allocating temporary data blocks associated with a third write operation to a third virtual address within the first virtual unit, wherein the address space in the first virtual unit associated with the third write operation includes pre-allocated chunks, wherein the third virtual address is unaligned with chunk boundaries of the pre-allocated chunks, and wherein the pre-allocated chunks are allocated a set of data blocks in a physical unit corresponding to the first virtual unit, the temporary data blocks being separate from the set of data blocks allocated to the pre-allocated chunks; and
overwriting the appropriate set of data blocks allocated to the pre-allocated chunks with data blocks from the temporary storage at a time after acknowledging completion of the third write operation.
8. The method of claim 7, wherein the overwriting comprises:
decompressing data blocks allocated to the pre-allocated chunks; and
replacing those decompressed data blocks allocated to the pre-allocated chunks that correspond to the virtual address space associated with the third write operation with data from the temporary data blocks.
9. The method of claim 1 further comprising:
maintaining a unit metadata data structure for each virtual unit for storing information describing mapping of the virtual unit to the physical unit and mapping of virtual addresses within the virtual unit to physical addresses in the physical unit.
10. The method of claim 9, wherein the metadata structure comprises a plurality of chunk structures, each chunk structure corresponding to a chunk in the virtual disk that has been allocated data blocks in the physical unit.
11. The method of claim 10, wherein each chunk structure includes a logical block address field indicating a physical address in the physical unit where the data associated with the chunk is stored, and a number of blocks field indicating the number of blocks allocated to the data associated with the chunk.
12. The method of claim 10, wherein the metadata structure further comprises a page header that includes a page index field identifying pages from the physical unit that have been allocated to the virtual unit and a per page block bitmap field identifying free and used data blocks within the pages from the physical unit.
13. The method of claim 1, further comprising:
dividing the data associated with a first write operation to a first virtual address in the virtual unit into chunks;
operating on at least one chunk to generate a signature associated with the at least one chunk;
comparing the signature associated with the at least one chunk with stored signatures of previously allocated chunks; and
if a match is found, copying physical disk allocation information associated with the previously allocated chunk corresponding to the matched signature to physical disk allocation information associated with the at least one chunk.
14. The method of claim 13, further comprising:
incrementing a counter associated with the matched signature of the previously stored chunk.
15. A virtualization device comprising:
a virtualization engine programmed for:
mapping each of a plurality of virtual units in a virtual disk to a single one of a plurality of physical units in physical storage; and
mapping a virtual address within a virtual unit to any physical address within the single of the plurality of physical units.
16. The virtualization device of claim 15, wherein the virtualization engine is further programmed for:
dividing data associated with a first write operation to a first virtual address within a first of the plurality of virtual units into chunks; and
allocating a first set of data blocks in a first physical unit mapped to the first of the plurality of virtual units for each chunk.
17. The virtualization device of claim 16, further comprising a compression engine coupled to the virtualization engine for compressing each chunk before the allocating.
18. The virtualization device of claim 17, the virtualization engine is further programmed for:
dividing data associated with a second write operation to the first virtual address into chunks; and
allocating a second set of data blocks for each chunk from overflow reserve storage that is located within the first physical unit if the size of any compressed chunk associated with the second write operation exceeds the size of the previously allocated first set of data blocks.
19. The virtualization device of claim 18, wherein the overflow reserve storage is located within a page that also includes the first set of data blocks.
20. The virtualization device of claim 19, wherein the overflow reserve storage is located within a subpage of the page, wherein the subpage also includes the first set of data blocks.
21. The virtualization device of claim 17, wherein the virtualization engine is further programmed for:
allocating temporary data blocks associated with a third write operation to a third virtual address within the first virtual unit, wherein the address space in the first virtual unit associated with the third write operation includes pre-allocated chunks, wherein the third virtual address is unaligned with chunk boundaries of the pre-allocated chunks, and wherein the pre-allocated chunks are allocated a set of data blocks in a physical unit corresponding to the first virtual unit, the temporary data blocks being separate from the set of data blocks allocated to the pre-allocated chunks; and
overwriting the appropriate set of data blocks allocated to the pre-allocated chunks with data blocks from the temporary storage at a time after acknowledging completion of the third write operation.
22. The virtualization device of claim 21, wherein the overwriting comprises:
decompressing data blocks allocated to the pre-allocated chunks; and
replacing those decompressed data blocks allocated to the pre-allocated chunks that correspond to the virtual address space associated with the third write operation with data from the temporary data blocks.
23. The virtualization device of claim 15, further comprising a metadata engine coupled to the virtualization engine, the metadata engine programmed for:
maintaining a unit metadata data structure for each virtual unit for storing information describing mapping of the virtual unit to the physical unit and mapping of virtual addresses within the virtual unit to physical addresses in the physical unit.
24. The virtualization device of claim 23, wherein the metadata structure comprises a plurality of chunk structures, each chunk structure corresponding to a chunk in the virtual disk that has been allocated data blocks in the physical unit.
25. The virtualization device of claim 24, wherein each chunk structure includes a logical block address field indicating a physical address in the physical unit where the data associated with the chunk is stored, and a number of blocks field indicating the number of blocks allocated to the data associated with the chunk.
26. The virtualization device of claim 24, wherein the metadata structure further comprises a page header that includes a page index field identifying pages from the physical unit that have been allocated to the virtual unit and a per page block bitmap field identifying free and used data blocks within the pages from the physical unit.
27. The virtualization device of claim 15, wherein the virtualization engine comprises a deduplication engine programmed for:
dividing the data associated with a first write operation to a first virtual address in the virtual unit into chunks;
operating on at least one chunk to generate a signature associated with the at least one chunk;
comparing the signature associated with the at least one chunk with stored signatures of previously allocated chunks; and
if a match is found, copying physical disk allocation information associated with the previously allocated chunk corresponding to the matched signature to physical disk allocation information associated with the at least one chunk.
28. The virtualization device of claim 27, wherein the deduplication engine is further programmed for:
incrementing a counter associated with the matched signature of the previously stored chunk.