METHOD AND SYSTEM FOR HANDLING FRAMEWORK SHUTDOWN IN A NETWORK

• US 20100257542A1
• Filed: 11/19/2008
• Published: 10/07/2010
• Est. Priority Date: 11/21/2007
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Jung, Dong-Shin, Lee, Joo-Yeol, Krishnamurthy, Subramanian, Bharadwaj, Vedula Kiran, Sreekanth, Siddapur Channakeshava
• Granted Patent: US 8,429,679 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: H04L 12/2807 Exchanging configuration information on appliance services in a home automation network arrangements for maintenance or administration involving network analysis for automatically determining the actual topology of a network H04L41/12; hardware or software tools for network management using graphical user interfaces H04L41/22; address allocation H04L61/50
• CPC Class Codes: H04L 12/2836 Protocol conversion between an external network and a home network controlling appliance services of a home automation network from a device located outside the home and the home network H04L12/2818; protocol conversion H04L69/08; adaptation of digital video signals for transport over a specific home network H04N7/24
• CPC Class Codes: H04L 41/0809 Plug-and-play configuration

Abstract

Method and central server for handling of a framework shutdown in a network is disclosed. The method includes generating an event related to a framework shutdown. The method also includes converting the event as a Universal Plug and Play (UPnP) event. The method further includes delivering the converted event to one or more controllers present in the network. The central server includes a processor configured a processor configured to generate an event related to a framework shutdown and to convert the event as a Universal Plug and Play (UPnP) event. The central serve also includes a transmitter configured to deliver the converted event to one or more controllers present in the network.

Claims

1. A method for handling shutdown of a framework in a network, the method comprising:

generating an event related to a framework shutdown;

converting the event as a Universal Plug and Play (UPnP) event; and

delivering the converted event to one or more controllers present in the network.

2. The method of claim 1 further comprising decrementing a start-level of the framework to zero during the framework shutdown.

3. The method of claim 1 further comprising determining whether the event is related to at least one of an abrupt framework shutdown and a normal framework shutdown.

4. The method of claim 3 further comprising when the framework shutdown is determined to be the abrupt framework shutdown:

receiving by the framework a poll from an entity external to the framework at a regular interval of time; and

informing the one or more controllers of the abrupt shutdown.

5. The method of claim 1 further comprising:

stopping a system bundle; and

stopping a plurality of active bundles.

6. The method of claim 5 further comprising recording a state of each of the plurality of active bundles at the shutdown, the state of each of the plurality of bundles indicates restarting point of each of the plurality of bundles when the framework is restarted.

7. The method of claim 5 further comprising:

wrapping in a BundleException an exception that occurs during the framework shutdown; and

publishing the BundleException as a framework event of type Frame-workEvent.Error.

8. The method of claim 5, wherein the stopping of the plurality of active bundles comprises shutting down the plurality of active bundles in a reverse dependency order.

9. The method of claim 1, wherein the framework is an Open Service Gateway initiative framework and the event is of type FrameworkEvent.SHUTDOWN.

10. A central server comprising:

a processor configured;

to generate an event related to a framework shutdown; and

to convert the event as a Universal Plug and Play (UPnP) event; and

a transmitter configured to deliver the converted event to one or more controllers present in a network.

11. The central server of claim 10 further comprising a receiver configured to receive a poll from an entity external to the framework at a regular interval of time, wherein the one or more controllers in the network are informed about an abrupt shutdown based on the poll.

12. The central server of claim 11, wherein the transmitter and the receiver are integrated as a transceiver.

13. The central server of claim 10, wherein the processor is further configured to:

stop a system bundle; and

stop a plurality of active bundles.

14. The central server of claim 10 further comprising a memory module for storing a state of each of the plurality of active bundles at the shutdown, the state of each of the plurality of active bundles indicates restarting point of each of the plurality of bundles when the framework is restarted.

15. The central server of claim 10, wherein the framework is an Open Service Gateway initiative framework and the event is of type Frame-workEvent.SHUTDOWN.