Method and system for processing event of softswitch open type system

• US 20040158839A1
• Filed: 12/30/2003
• Published: 08/12/2004
• Est. Priority Date: 01/08/2003
• Status: Abandoned Application

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Lee, Seung-Hyun
• Application Number:
  US10/747,283
• Publication Number:
  US 20040158839A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

In a method and system for processing an event of a softswitch open type system, an OAMP operator can easily implement an event processing interface between different devices or different processes. If one alarm event is generated, in order for the application to transmit the event to a Relim, each element of the system event includes event handlers, an event related library, a DataRedirection element for performing a posting function between elements for an event object, and a CM which receives an event object transmitted from the application using a remote service. The Relim posts the event using the remote service and, if a generated event is an arbitrary event, not an alarm/fault event, the event is reposted to the relevant event processing element. With such a construction, realization of the software is facilitated from the standpoint of the application user, and an event can be transmitted to a relevant element by a single call with the use of an event processing function included in the element itself so that a separate interface with the relevant element is not required.

Claims

1. A method for processing an event of a softswitch open type system, the method comprising the steps of:

(a) calling an event handler using an event processing function, and transmitting generated events to a configuration management (CM) element designated as an event processing master when an event is generated at each of a plurality of applications;

(b) posting each of the generated events to a relevant module according to a type of said each of the events; and

(c) processing by calling up a relevant event handling class in order to process said each of the generated events posted to the relevant module.

2. The method according to claim 1, wherein step (a) comprises the sub-steps of:

detecting an event generated at an application;

constructing an event at the event handler and calling up an issueEvent;

calling up an eventTransport in order to search a Thread;

requesting a DataTransport for event posting;

calling a remote service generating function at a DataConsumer in order to post the event to the CM element; and

posting the event to the DataConsumer of the CM by means of remote service.

3. The method according to claim 1, wherein step (b) comprises the sub-steps of:

posting an event to a DataQueue;

transmitting an event to an eventThread;

performing, at a Thread, an infinite loop in order to receive another event, wherein process is overridden to a DataTransport class;

requesting posting of an event object;

determining to which function an event should be posted;

determining validity as to whether the event object is used at a relevant capsule through a filter when a class to which the event should be posted is determined;

calling up a remote service generating function in order to post the event to the relevant capsule; and

posting the event to a DataConsumer of the relevant capsule using the remote service.

4. The method according to claim 3, wherein the step of posting the event to the DataQueue comprises the sub-steps of:

determining whether a relevant event RemoteConsumer is set to master;

requesting generation of an independent thread so that an event object of its own can be processed when the master is set to true;

generating, at a DataConsumer of a DataRedirection framework, which is a parent of the relevant event RemoteConsumer, an event posting DataQueue for the relevant event RemoteConsumer; and

performing a member process for processing an event when the event is posted to the DataQueue of the relevant event RemoteConsumer.

5. The method according to claim 3, wherein the step of determining validity as to whether the event object is used at a relevant capsule through a filter when the class to which the event would be posted is determined, comprises the sub-steps of:

requesting, at a relevant event RemoteConsumer, registration of the relevant event RemoteConsumer and a relevant event Filter on a DataTransport used by an event by using an event handler in a relevant event capsule in order to register the relevant event on the relevant event capsule with filtering of the relevant event;

using the remote service in order to register certain information as to the RemoteConsumer and the relevant event Filter on a master capsule of an event processing function;

sending the certain information to a DataRedirection framework of a master capsule, and registering the relevant event DataConsumer required by the relevant event capsule at the event processing function of the master capsule; and

registering the relevant event Filter for filtering a relevant event object.

6. A system for processing an event of a softswitch open type system, the system comprising:

first means for calling an event handler using an event processing function, and transmitting generated events to a configuration management (CM) element designated as an event processing master when an event is generated at each of a plurality of applications;

second means for posting each of the generated events to a relevant module according to a type of said each of the events; and

third means for processing by calling up a relevant event handling class in order to process said each of the generated events posted to the relevant module.

7. The system according to claim 6, wherein said first means:

detects an event generated at an application;

constructs an event at the event handler and calls up an issueEvent;

calls up an eventTransport in order to search a Thread;

requests a DataTransport for event posting;

calls a remote service generating function at a DataConsumer in order to post the event to the CM element; and

posts the event to the DataConsumer of the CM by means of remote service.

8. The system according to claim 6, wherein said second means:

posts an event to a DataQueue;

transmits an event to an eventThread;

performs, at a Thread, an infinite loop in order to receive another event, wherein process is overridden to a DataTransport class;

requests posting of an event object;

determines to which function an event should be posted;

determines validity as to whether the event object is used at a relevant capsule through a filter when a class to which the event should be posted is determined;

calls up a remote service generating function in order to post the event to the relevant capsule; and

posts the event to a DataConsumer of the relevant capsule using the remote service.

9. The system according to claim 8, wherein the posting of the event to the DataQueue comprises:

determining whether a relevant event RemoteConsumer is set to master;

requesting generation of an independent thread so that an event object of its own can be processed when the master is set to true;

generating, at a DataConsumer of a DataRedirection framework, which is a parent of the relevant event RemoteConsumer, an event posting DataQueue for the relevant event RemoteConsumer; and

performing a member process for processing an event when the event is posted to the DataQueue of the relevant event RemoteConsumer.

10. The system according to claim 8, wherein the determining of validity as to whether the event object is used at a relevant capsule through a filter when the class to which the event would be posted is determined, comprises:

requesting, at a relevant event RemoteConsumer, registration of the relevant event RemoteConsumer and a relevant event Filter on a DataTransport used by an event by using an event handler in a relevant event capsule in order to register the relevant event on the relevant event capsule with filtering of the relevant event;

using the remote service in order to register certain information as to the RemoteConsumer and the relevant event Filter on a master capsule of an event processing function;

sending the certain information to a DataRedirection framework of a master capsule, and registering the relevant event DataConsumer required by the relevant event capsule at the event processing function of the master capsule; and

registering the relevant event Filter for filtering a relevant event object.