Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L12/2803—Home automation networks
  • H04L12/283—Processing of data at an internetworking point of a home automation network
  • H04L12/2836—Protocol conversion between an external network and a home network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L12/2803—Home automation networks
  • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/08—Configuration management of networks or network elements
  • H04L41/0803—Configuration setting
  • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
  • H04L41/0809—Plug-and-play configuration

Definitions

• the present invention relates to the field of managing framework in a network. More specifically, the present invention relates to a method and system for handling shutdown of a framework in a network. Background Art
• a framework must be started before any services can be provided in a network.
• a framework can be started by some command line initiation or by reading startup information from a configuration file.
• Some events that take place when a framework is started are, handling of events, entering of system bundle in starting state, staring previously stalled bundles, wrapping up an exception that occur during startup, publishing the exception, entering of the system bundle in a start state, and broadcasting a framework event that indicates the framework has started.
• the framework implementation can select an appropriate ordering for stopping of bundles in the start- level. This may include stopping bundles in reverse dependency order such that all bundles which depend on a given bundle are shutdown before the given bundle. At any point of time when a framework shuts down, all controllers that are using the framework needs to be informed about the shutdown.
• a method for handling shutdown of a framework in a network 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 includes delivering the converted event to one or more controllers present in the network.
• the method also includes decrementing the start- level of framework to zero during the framework shutdown.
• the method includes determining whether the shutdown is abrupt.
• the method also includes receiving by the framework a poll from an entity external to the framework at a regular interval of time and informing the controllers of the abrupt shutdown.
• the framework is an Open Service Gateway initiative framework and the event is of type Frame workEvent. SHUTDOWN.
• central server in another embodiment, includes 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 server also includes a transmitter configured to deliver the converted event to one or more controllers present in the network.
• the central server also includes a receiver configured to receive a poll from an entity external to the framework at a regular interval of time. The one or more controllers in the network are informed about an abrupt shutdown based on the poll.
• the framework is an Open Service Gateway initiative framework and the event is of type Frame- workEventSHUTDOWN.
• FIG. 1 illustrates a network where various embodiments of the present invention can be practiced.
• FIG. 2 illustrates a central server, in accordance with one embodiment of the present invention.
• FIG. 3 illustrates a flow chart depicting a method for handling shutdown of a framework the network, in accordance with one embodiment of the present invention.
• FIG. 4 illustrates a flow chart depicting a method for handling shutdown of a framework the network, in accordance with another embodiment of the present invention.
• Mode for the Invention [13] The terms used to describe various embodiments are exemplary. It should be understood that these are provided to merely aid the understanding of the description, and that their use and definitions in no way limit the scope of the invention.
• FIG. 1 illustrates a network 100, where various embodiments of the present invention can be practiced.
• the network 100 can include a central server and one or more controllers.
• Examples of the network 100 include, but are not limited to, a Local Area Network (LAN) and Wireless Local Area Network (WLAN).
• the network 100 is shown to include a central server 102, a controller 104, and a controller 106.
• Examples of a central server and controllers include, but are not limited to, mobile phones, laptops, personal computers, personal digital assistants, printers, access points, televisions, media players, internet gateway devices. This embodiment will be explained with the help of the central server 102 and the controllers 104 and 106. However, it will be apparent to a person ordinarily skilled in the art that the present embodiment can be implemented by using any other central server and controllers in the network 100.
• the central server 102 is shown to include a framework 108.
• the framework 108 provides execution environment to application or services registered with the framework 108.
• the framework 108 provides these services to other devices, the controllers 104 and 106 in the network 100.
• the framework 108 can get shutdown or restarted once optional extension bundles for system bundles are refreshed or updated.
• the framework 108 must be re-launched when the extension bundles are updated.
• the framework 108 can also get shutdown abruptly due to some dependency failure.
• As the framework 108 provides services registered with it to other devices (controllers), devices in the network 100 must be informed about the shutdown of the framework 108.
• the central server 102 notifies the shutdown of the framework 108 to the controllers 104 and 106 connected to it.
• FIG. 2 illustrates the central server 102, in accordance with one embodiment of the present invention.
• the central server 102 is capable of informing a framework shutdown to other devices/controllers in the network 100.
• An example of the framework includes, but is not limited to, an Open Services Gateway initiative (OSGi) framework.
• the central server 102 includes a processor 202 and a transmitter 204.
• the processor 202 is configured to generate an event related to a framework shutdown.
• An example of the event includes, but is not limited to, Frame- workEvent.SHUTDOWN.
• the processor 202 also converts the event as a Universal Plug and Play (UPnP) event.
• the processor 202 then provides the converted event to the transmitter 204.
• UPF Universal Plug and Play
• the transmitter 204 delivers the converted event to one or more controllers present in the network 100.
• the transmitter 204 can deliver the converted event to the controllers 104 and 106 that are connected to the central server 102.
• the framework shutdown is abrupt.
• the central server 102 also includes a receiver 206 to receive poll from an entity external to the framework at regular interval of time. The external entity receives an acknowledgement from the framework in response to the poll. If the external entity does not receive the acknowledgement from the framework, the framework is determined to be shutdown. This helps the central server 102 to inform the controllers 104 and 106 in the network 100 about the abrupt shutdown of the framework.
• the transmitter 204 and the receiver 206 can be integrated as a transceiver.
• the processor 202 is also configured to stop a system bundle and a plurality of active bundles to prepare the framework 108 for a normal shutdown.
• the framework is shutdown when the system bundle and the plurality of active bundles are stopped.
• the central server 102 can also include a memory module 208.
• the memory module 208 stores state of each of the plurality of active bundles at the shutdown. The state indicates a state of the bundle from where each bundle must be restarted when the framework 108 is restarted. The process of handling shutdown of a framework is explained with the help of FIG. 3 and FIG. 4.
• FIG. 3 illustrates a flowchart depicting a method 300 for handling framework of a shutdown in the network 100, in accordance with an embodiment of the present invention.
• the method 300 can also include more number of steps as depicted in FIG. 3.
• the method 300 is initiated.
• an event related to a framework shutdown is generated by the processor 202. Examples of some mechanism for generating event are Call-Back mechanism and Listener- Notify mechanism.
• the framework can be an OSGi framework and the event can be a FrameEvent.
• the event is converted as a UPnP event by the processor 202.
• the event is converted to the UPnP event, as the controllers 104 and 106 present in the network 100 may be UPnP controllers. Conversion of the event enables the controllers (UPnP) in the network 100 to interpret the event.
• the converted event is delivered to one or more controllers, for example, the controllers 104 and 106 in the network 100.
• the event related to a framework shutdown enables the controllers 104 and 106 to have information about the framework shutdown.
• the controllers 104 and 106 can use this information and stop sending network messages to the framework, as the framework is shutdown and will not be able to respond to these network messages. Further, the controllers can start researching other devices for an alternative framework.
• the framework shutdown can either be normal shutdown or an abrupt shutdown. For the abrupt framework shutdown a poll is received from an entity external to the framework at a regular interval of time. The controllers are then informed about the abrupt shutdown based on the poll. Thereafter, the method 300 is terminated at step 310.
• the method for handling of a framework shutdown is explained in detail with the help of FIG. 4.
• FIG. 4 illustrates a flowchart depicting a method 400 for handling of a framework shutdown in the network 100, in accordance with another embodiment of the present invention.
• the method 400 is initiated.
• a state of each bundle of a plurality of active bundles is recorded at a framework shutdown. The state of each bundle indicates a point from where each bundle of the plurality of bundle must be restarted. This helps a bundle to re-start from the same state (a state at which the bundle was during the shutdown), when the framework is re-started.
• the framework 108 can be shutdown by decrementing a start- level of the framework 108 to zero.
• the plurality of active bundles are stopped.
• the plurality of active bundles can be stopped in a reverse dependency order.
• reverse dependency order consider an example in which a bundle A is dependent on a bundle B, and the bundle B is dependent on a bundle C.
• the bundle A is shutdown before the bundle B; and the bundles A and B are shutdown (A shuts down before B) before the bundle C.
• a system bundle is stopped.
• an event related to a framework shutdown is generated.
• the event is converted as a UPnP event.
• the converted event is delivered to one or more controllers in the network 100.
• the method 400 also includes wrapping an exception in a Bundle-
• Exception that occurs during the framework shutdown.
• Examples of exception include, but are not limited to, illegal arguments exception, out of memory exception, and input/output exception.
• the BundleException is published as a framework event of type FrameworkEvent.Error. Thereafter, the method 400 is terminated at step 416.
• the present invention provides a technique by which controllers get information about framework shutdown in a network. Further, the present invention provides proper handling of normal framework shutdown and abrupt framework shutdown. The present invention also provides ease of handling framework shutdown scenarios by using framework eventing mechanism, for example, a Call- Back mechanism and a Listener- Notify mechanism. The present invention also enables the controller to stop sending unnecessary messages to a framework, used by the controller, which is shutdown. Further, the present invention helps the controllers to research for an alternative framework when a framework the controller is using is shutdown.

Landscapes

• Engineering & Computer Science (AREA)
• Automation & Control Theory (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Multimedia (AREA)
• Computing Systems (AREA)
• Computer And Data Communications (AREA)
• Telephonic Communication Services (AREA)
• Stored Programmes (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (2)

Family

ID=40667984

Family Applications (1)

Country Status (5)

Families Citing this family (1)

Family Cites Families (8)

• 2008
  • 2008-10-07 KR KR1020080098350A patent/KR101504363B1/ko not_active IP Right Cessation
  • 2008-11-19 US US12/743,750 patent/US8429679B2/en active Active
  • 2008-11-19 WO PCT/KR2008/006801 patent/WO2009066924A2/en active Application Filing
  • 2008-11-19 EP EP08852676A patent/EP2220817A4/en not_active Withdrawn
  • 2008-11-19 CN CN200880117223A patent/CN101868942A/zh active Pending

Non-Patent Citations (3)

Also Published As

Similar Documents

Legal Events