KR20090117482A - System and method for managing osgi framework devices in the private ip network - Google Patents

Abstract

PURPOSE: A system and a method for managing OSGi framework devices in a private IP network environment are provided to remotely manage OSGi devices of the private IP network environment. CONSTITUTION: A master OSGi device registers information of another OSGi deice through broadcasting to a local network. A slave OSGi device is connected to an external network through the master OSGi device. The slave OSGi device registers device information of the slave OSGi device according to a provisioning process between OSGi management servers. The slave OSGi device registers the information of another OSGi device through broadcasting to a local network.

Description

System and method for managing OSGi framework devices in the private IP network

The present invention relates to an OSGi device management system and a method thereof, and more particularly, to a device equipped with an OSGi framework in a private IP network environment such as a home network (also known as a NAT environment; performing a private IP address / authorized IP address translation function). The present invention relates to an OSGi device management system and a method of a private IP network environment for allowing (eg, OSGi devices, eg, home gateways, home terminals) to be remotely managed.

The OSGi device proposed in the present invention refers to a device equipped with an OSGi (Open Service Gateway initiative) framework. A private IP network environment refers to interworking between an external public IP network (for example, the Internet) and an internal private IP network. This refers to a network environment in which a function of converting a private IP address assigned to an OSGi device on a private IP network into a public IP address is performed.

In addition, the present invention includes any network environment such as a home network, a telematics network, an industrial automation network, a building automation network, a grid computing network, a robot network, and the like as an example of a private IP network environment.

In particular, the OSGi device of the present invention may have different performance functions depending on the type of the corresponding private IP network environment, for example, the OSGi device of the home network may be an indoor home appliance or an indoor home monitoring device. The device can be an intelligent robot.

In addition, the OSGi device of the present invention is divided into a master OSGi device and a slave OSGi device according to the hierarchical position of the corresponding private IP network. For example, in a home network, a master OSGi device is a home gateway, and a slave OSGi device is a lower home terminal. do. Here, the private IP address / public IP address translation function is performed in the master OSGi device, the master OSGi device has a public IP address.

Hereinafter, the present invention will be described by taking a home network as an example of a private IP network environment, a home gateway as an example of a master OSGi device, and various indoor terminals as an example of a slave OSGi device.

Intelligent home network technology is a collection of all ubiquitous technologies, and all home appliances can be connected to wired and wireless networks so that anyone can provide various services such as distance education, home automation, and multimedia to users regardless of time and place. .

In the intelligent home network technology, OSGi (Open Service Gateway), a non-profit standardization organization, is a service platform technology that arbitrates various wired and wireless networks and interfaces within a home network and enables remote management and dynamic distribution of various services based on this. There is an OSGi framework proposed by the initiative.

On the other hand, IP address shortage is spreading with the advent of the IP convergence era, such as owning 2 PCs, Internet telephony (VoIP), and Internet TV (IPTV). Services over private IP network environments are becoming common.

For example, in a home network of a private IP network environment, home terminals having a private IP address may be assigned through a NAT function of the home gateway by assigning a public IP address to a home gateway and assigning a private IP address to lower indoor terminals. Make the connection possible.

However, in the conventional technology as described above, the use of the NAT function in a private IP network environment prevents the application service or application provided through the Internet from operating normally because the NAT function acts as a firewall that blocks a session from an external network. In particular, the deployment, installation, start, stop, update, and removal of applications through the OSGi framework are being prevented.

On the other hand, there is a prior art in which the OSGi framework is applied to the aforementioned home network. However, the prior art only suggests that each OSGi framework is installed in the home gateway and the indoor terminals. There is no specific plan for the remote management scheme for each OSGi device included in the home network.

That is, if the prior art is applied to a home network using a NAT function of a private IP network environment, a management command transmitted from an OSGi management server on the Internet to an OSGi device in a home is blocked by NAT to implement a home network service remotely. There is a problem that can not be achieved for the control.

Accordingly, the present invention has been proposed to solve the above problems and to meet the above requirements, OSGi of a private IP network environment (a NAT environment; performing a private IP address / public IP address translation function) such as a home network An object of the present invention is to provide an OSGi device management system and method for a private IP network environment for allowing devices equipped with a framework (hereinafter, OSGi devices, such as home gateways and home terminals) to be managed remotely.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention which are not mentioned above can be understood by the following description, and will be more clearly understood by the embodiments of the present invention. Also, it will be readily appreciated that the objects and advantages of the present invention may be realized by the means and combinations thereof indicated in the claims.

In the first system of the present invention for achieving the above object, in the system for managing the OSGi device, a master OSGi device and a slave OSGi device is provided as a OSGi device in a local network of a private IP network environment, the master OSGi The device performs a private IP address / authorized IP address translation function for the slave OSGi device, registers its own device information according to provisioning processing between OSGi management servers on an external network, and broadcasts to the local network. Registering information of another OSGi device, the slave OSGi device connects to an external network through the master OSGi device, registers its device information according to provisioning processing between the OSGi management servers, and broadcasts to the local network. It is characterized by registering the information of the other OSGi device through.

The first system of the present invention may further include a local network service control server for giving a local network service control command to the OSGi device, wherein the local network service control server includes OSGi device information and a local network service control command. To the OSGi management server, and the OSGi management server acquires the public IP address of the master OSGi device of the corresponding private IP network by using the OSGi device information received from the local network service control server, and executes the local network service control command. It is characterized in that for transmitting to the master OSGi device.

Meanwhile, the second system of the present invention is a system for managing OSGi devices, wherein a master OSGi device and a slave OSGi device are provided as OSGi devices in a local network of a private IP network environment, and the master OSGi device and the slave OSGi devices are provided. Each device registers its own device information according to a provisioning process between OSGi management servers on an external network, and when the OSGi management server receives a provisioning request from the OSGi device, a public IP is based on the IP address of the OSGi device. It is determined whether it is located in the address area, and the OSGi device is registered as a master OSGi device or a slave OSGi device of the corresponding private IP network.

The second system of the present invention may further include a local network service control server for giving a local network service control command to the OSGi device, wherein the local network service control server includes OSGi device information and a local network service control command. To the OSGi management server, and the OSGi management server acquires the public IP address of the master OSGi device of the corresponding private IP network by using the OSGi device information received from the local network service control server, and executes the local network service control command. It is characterized in that for transmitting to the master OSGi device.

Meanwhile, in the first method of the present invention, in the method of managing an OSGi device, a plurality of OSGi devices are provided in a local network of a private IP network environment, and the OSGi device externally provides a provisioning request packet including a device IP address. Transmitting to the OSGi management server on the network; If the OSGi device receives an IP address from the OSGi management server as a result of the provisioning request packet transmission, broadcasting the first packet to the local network based on the returned IP address to notify another OSGi device of its existence; And registering the information of the corresponding OSGi device based on the received second packet when the OSGi device receives a second packet from another OSGi device as a result of broadcasting the second packet of another OSGi device.

Further, in the first method of the present invention, when the OSGi device receives specific data from the OSGi management server or another OSGi device, the registered OSGi device information is queried based on the destination IP address of the specific data and the OSGi of the corresponding destination. Delivering said specific data to a device.

Meanwhile, in the method of managing an OSGi device, a second method of the present invention includes a plurality of OSGi devices in a local network of a private IP network environment, and when the OSGi management server receives a provisioning request packet from the OSGi device, Determining whether a source IP address of an IP header of a provisioning request packet and a device IP address included in the provisioning request packet are the same; And if the determination result is the same, the OSGi management server registers the OSGi device as a master OSGi device on a corresponding private IP network. If the determination result is different, the OSGi management server registers the OSGi device under the master OSGi device. OSGi device registration step of registering as a slave OSGi device.

Also, in the second method of the present invention, when the OSGi management server receives a local network service control command from a local network service control server, the master OSGi device of the corresponding private IP network is configured using OSGi device information of the local network service control command. Obtaining a public IP address of the; And setting, by the OSGi management server, the obtained public IP address as a destination, and transmitting the local network service control command.

The present invention as described above has the effect of allowing OSGi devices in a private IP network environment (aka NAT environment) to be managed remotely.

The present invention also provides a remote OSGi management server, a corresponding service control server (eg, a home network service control server), and the like, to send OSGi management commands and corresponding service control commands to OSGi devices in a private IP network environment. This has the effect of enabling the implementation of the corresponding service.

In addition, the present invention can easily check the network structure, etc. for the private IP network in the remote OSGi management server, the effect of smoothly performing communication such as data transmission and reception between devices through the device mutual information table between OSGi devices There is.

The above objects, features, and advantages will become more apparent from the detailed description given hereinafter with reference to the accompanying drawings, and accordingly, those skilled in the art to which the present invention pertains may share the technical idea of the present invention. It will be easy to implement. In addition, in describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of an embodiment of a communication network to which the present invention is applied.

As shown in FIG. 1, a communication network to which the present invention is applied includes an external network (for example, the Internet) and a home network that is a local network (internal network), and includes an OSGi management server 10 and the like on the external network. The home network includes a home gateway 20 and a plurality of premises terminals 30 such as computers, robots, information devices, home appliances, and the like. Here, the external network is a public IP address area and the home network is a private IP address area.

Hereinafter, the present invention will be described in detail with reference to FIG. 2.

2 is a configuration diagram of an OSGi device management system in a private IP network environment according to the present invention.

As shown in FIG. 2, the OSGi device management system in a private IP network environment according to the present invention includes an OSGi management server 10 and a home network service control server (or home network device management server) 50 on an external network, Home gateway 20 on the home network, and a plurality of premises terminals (first premises terminal 30, the second premises terminal 40).

The OSGi management server 10 is a server that manages OSGi devices. The OSGi management server 10 includes a policy rule manager 11, a profile manager 12, a provisioning processor 13, a remote command processor 14, and an OSGi device information table 15. Include.

The home gateway 20 is a master OSGi device [Master] and includes a management agent (MA) 21, an OSGi framework module 22, an operating system module 23, a NAT processing unit 24, and device mutual information. The table 25 is included. Of course, it is preferable that the NAT mapping table is provided in the NAT processing unit 24.

The first indoor terminal 30 is a first slave OSGi device [Slave-01], and includes a management agent (MA) 31, an OSGi framework module 32, an operating system module 33, and a device mutual information table 34. The second indoor terminal 40 is a second slave OSGi device [Slave-02], and includes a management agent (MA) 41, an OSGi framework module 42, an operating system module 43, and a device. A mutual information table 44 is included.

The home gateway 20 is assigned a public IP address (eg, 61.xxx, 51.50) through equipment (not shown) on the Internet operator side, and the first indoor terminal 30 and the second indoor terminal 40. Each is given a private IP address (eg, 192.168.0.10, 192.168.0.22, respectively) through the home gateway 20.

In addition, the home gateway 20 performs a NAT function so that the first indoor terminal 30 and the second indoor terminal 40 on the home network in a private IP network environment can be connected to an external network, thereby providing a public IP address / private IP. Perform address translation.

In the present invention, a device (hereinafter OSGi device) equipped with an OSGi framework in a private IP network environment (also referred to as a NAT environment) such as the home network, for example, a home gateway 20, a first indoor terminal 30, and a second indoor terminal. 40 allows the OSGi framework to be managed by the OSGi management server 10 on the remote external network, and the home gateway 20, the first premises terminal 30 and the second premises terminal 40 are remote. Service control is performed by the home network service control server (or home network device management server) 50 on the external network.

For example, the present invention is based on the open OSGi service platform, each OS having this private IP address when the OSGi service platform is implemented in the home gateway and a plurality of terminals or hosts are implemented in the NAT environment provided by the home gateway. The OSGi framework and home network service functions provided in the terminal can be controlled and managed by a remote OSGi management server and a home network service control server. Here, it will be easily understood that the home gateway can be an OSGi framework management terminal and a home network service control terminal because it has both a private IP address and a public IP address.

First, the function of each component of the present invention will be briefly described.

The OSGi management server 10 receives a (initial) provisioning request from an OSGi device such as a home gateway 20, a first indoor terminal 30, and a second indoor terminal 40 on a home network through an external network. It is determined whether the OSGi device is located in the public IP address area, and transmits the corresponding (initial) provisioning result according to the (initial) provisioning processing process. In addition, the OSGi management server 10 transmits an OSGi framework management command to the corresponding OSGi device.

In addition, when the OSGi management server 10 receives a home network service control command from the home network service control server 50, the home gateway 20, which is a higher master OSGi device of the target OSGi device, corresponding to the home network service control command. The home network service control command is transmitted.

Between the OSGi management server 10 and the home gateway 20 that is the master OSGi device, between the home gateway 20 and each of the indoor terminals 30 and 40 that are slave OSGi devices, and between the indoor terminals 30 and 40. (Initial) Provisioning data, OSGi framework management commands, home network service control commands, and mutual transmission and reception data are performed through a management agent loaded on the OSGi framework. Here, each management agent is implemented as a bundle. In particular, such a management agent may operate as a master management agent or a slave management agent according to software component settings.

The home gateway 20 includes a NAT processing unit 24, and assigns a private IP address to each of the lower-terminal terminals 30 and 40 on the home network, and traffic (packet) originating inside the home network is external to the external network. In case of outgoing traffic, private IP address / official IP address translation is performed. Here, the private IP address / public IP address translation information is recorded in the NAT mapping table on the home gateway, so that traffic that does not exist through NAT mapping table lookup for traffic coming from the external network may be blocked according to a preset traffic processing policy. have. Meanwhile, the traffic processing policy may vary depending on the NAT function setting.

In addition, the home gateway 20 includes an OSGi framework module 22 to perform a master OSGi framework function, and has an interface for each of a local network and an external network (that is, has a public IP address and a private IP address). Through the OSGi management server 10, and communicates with each of the premises terminal (30, 40).

In addition, the home gateway 20 includes a management agent 21 to perform functions such as OSGi framework discovery and information management existing on the same local network.

Each of the indoor terminals 30 and 40 includes an OSGi framework module, respectively, to perform a slave OSGi framework function, and communicate with an external network through the home gateway 20 using a private IP address.

In addition, each indoor terminal (30, 40) has a management agent, respectively, and performs functions such as OSGi framework discovery and information management existing on the same local network.

Next, the OSGi device management scheme of the private IP network environment proposed by the present invention will be described in more detail.

First, the OSGi management server 10 will be described.

The policy rule manager 11 of the OSGi management server 10 manages a rule based OSGi framework provisioning policy regarding OSGi devices. For example, it is possible to define an action for an event in advance by an administrator device and to perform a predefined action when the event occurs.

In the present invention, a series of actions such as installation, configuration, and update checking of a service bundle (service component) to be processed when a (initial) provisioning request is received from an OSGi device are defined in advance. The OSGi management server 10 obtains an action to be performed through the rule manager 11.

The profile manager 12 of the OSGi management server 10 manages access, creation, inquiry, and change of a subscriber profile, a service profile, and an OSGi device profile stored in an integrated service infrastructure DB (not shown).

In the present invention, when the profile management unit 12 of the OSGi management server 10 receives a (initial) provisioning request from an OSGi device, information necessary for (initial) provisioning to be performed by the provisioning processing unit 13, for example, an OSGi device profile. OSGi device ID (ID) confirmation, OSGi device information inquiry and registration, subscriber profile information matching to OSGi device, service profile information inquiry, OSGi device-related changes are updated, especially with the OSGi device (initial ) In order to send provisioning data, OSGi framework management command, and home network service control command, a search for a public IP address of a higher OSGi device of the OSGi device, that is, a master OSGi device located in a public IP address area, is performed. According to the public IP address search performed by the profile manager 12 of the OSGi management server 10, the slave OSGi device in the private IP network environment returns the public IP address (the public IP address of the home gateway) of the upper OSGi device.

When the provisioning processing unit 13 of the OSGi management server 10 receives the (initial) provisioning request from the OSGi device, the profile management unit 12 through the profile management unit 12 information on the subscriber profile, service profile, OSGi device profile on the integrated service infrastructure DB To obtain the necessary actions through the policy rule management unit 11 to determine the provisioning policy on the OSGi device, and to perform OSGi device update, service bundle provision, and execution commands, so that the OSGi device can perform OSGi service and home network service. Be in a state where you can be provided.

In the present invention, when the provisioning processing unit 13 of the OSGi management server 10 receives an (initial) provisioning request from an OSGi device, the management agent IP address and (initial) provisioning request of the OSGi framework included in the OSGi device. The IP header of the packet is compared to determine whether the OSGi device is located in the public IP address area or the private IP address area, and the result of the public / private IP address area determination and the IP address of the (initial) provisioning request packet are determined. Returns to the device. For example, the OSGi device includes a management agent IP address of its OSGi framework in order to make an (initial) provisioning request. The OSGi device provides a (initial) provisioning request, and the home gateway 20, which is a higher master OSGi device, performs NAT function. In this case, the (initial) provisioning request packet of the OSGi device is converted into a public IP address of its own [home gateway] and transmitted to the provisioning processing unit 13 of the OSGi management server 10. Accordingly, the OSGi device receives its management agent IP address changed by the NAT function from the provisioning processing unit 13 of the OSGi management server 10.

The remote command processor 14 of the OSGi management server 10 receives a home network service control command from the home network service control server 50 when an OSGi framework management command is issued by an administrator device. Obtain the public IP address of the target OSGi device or the public IP address of the upper OSGi device [home gateway] of the target OSGi device through the profile manager 12 and request the relevant OSGi device to execute the command, and the corresponding OSGi device It receives the response from the side and delivers it to the administrator side device or home network service control server 50.

Next, the OSGi devices 20, 30, and 40 will be described.

The OSGi device on the home network includes a management agent, an OSGi framework module, an operating system module, and a device mutual information table. Of course, the home gateway of the OSGi device further includes a NAT processing unit and a NAT mapping table.

The OSGi device of the OSGi device manages computing resources such as a CPU, a main memory device, and an input / output device while performing an interface function between device hardware and an application program.

The OSGi framework module of the OSGi device performs a gateway function for various services provided by the device and manages various services operated on the OSGi framework. Such OSGi framework modules conform to known OSGi standards.

The management agent of the OSGi device provides an external interface so that various services on the OSGi framework module can be managed and controlled remotely.

In the present invention, the management agent of the OSGi device requests (initial) provisioning to the OSGi management server 10 through a TCP packet using HTTP when the device is assigned (granted) an IP address and connected to a network. As a result, the OSGi management server 10 receives the public / private IP address area determination result and the converted IP address of the [OSGi device]. Then, the management agent of the OSGi device transmits the UDP packet through broadcasting to the surrounding OSGi device while the UDP packet receiving daemon is executed based on the returned IP address, thereby transmitting its presence to another network on the home network (local network). Notify the OSGi device. This UDP packet transmission is also performed by other OSGi devices. In terms of other OSGi devices, when receiving a UDP packet from another OSGi device through the UDP packet receiving daemon, the management agent of the OSGi device recognizes that there is another OSGi device on its home network, and thus has its own device mutual information table. Stores the IP address and ID information of the other OSGi device recognized as present.

In addition, in the present invention, when the management agent of the OSGi device is requested to execute a specific command from an external device (for example, an OSGi management server, a home gateway, or another OSGi device), the management agent checks whether the command is a command coming to itself, and thus, the target OSGi is a target OSGi. If it is a device, it executes a corresponding command, and if the device is not a target OSGi device, the device mutual information table is searched using the OSGi device ID to search for a target OSGi device, and the command is transmitted to the corresponding OSGi device.

OSGi device management scheme of the private IP network environment proposed in the present invention is the function, operation, and process is performed by the management agent of the OSGi device, which is easy to implement through an application running on the OSGi framework, such as the management agent One consideration was given. Of course, in the present invention, such a function of the management agent may be implemented in an operating system module, an OSGi framework module, or the like of the OSGi device.

An OSGi device management scheme of a private IP network environment according to the present invention as described above will be described with reference to FIG. 2 as an example.

The home gateway 20 becomes a master OSGi device to perform the gateway functions of the public IP address area and the private IP address area, and has a public IP address such as '61 .xxx.51.50 '.

Each premises terminal 30, 40 becomes a slave OSGi device by discovering that it is located in the private IP address area through (initial) provisioning request and broadcasting, and information of another OSGi device located on the home network [OSGi device ID]. And IP address] are recorded and maintained in the device mutual information table.

For example, the home gateway 20 holds information of the first slave OSGi device [Slave-01] and information of the second slave OSGi device [Slave-02] in its device mutual information table.

The OSGi management server 10 holds the information of the OSGi device of the private IP network environment, that is, the information of the master OSGi device and the information of each slave OSGi device in the OSGi device information table through (initial) provisioning request processing.

3 is a flowchart illustrating a method of managing an OSGi device in a private IP network environment according to the present invention.

The home gateway [master OSGi device] 20 provisions (initial) to the OSGi management server 10 using HTTP-based TCP packets based on its device ID and public IP address [preferably its management agent IP address]. Request (301).

The OSGi management server 10 then processes the (initial) provisioning request from the home gateway 20, and the management agent IP address included in the (initial) provisioning request packet from the home gateway 20 and the The IP header of the (initial) provisioning request packet is compared to determine whether the home gateway 20 is located in the public IP address area or the private IP address area (302). Here, the OSGi management server 10 processes the (initial) provisioning request from the home gateway 20 according to a known (initial) provisioning processing procedure, and a detailed description thereof will be omitted.

Thereafter, the OSGi management server 10 returns a result of determining the authorized / private IP address area position of the home gateway 20 and a management agent IP address of the (initial) provisioning request packet to the home gateway 20 ( 303). Of course, the OSGi management server 10 also returns the (initial) provisioning processing result to the home gateway 20.

Then, the home gateway 10 transmits a UDP packet through a broadcast on a home network, for example, to a nearby OSGi device while the UDP packet reception daemon is executed based on the IP address returned from the OSGi management server 10. Notify other OSGi devices on the home network (local network) of the presence of (304).

Meanwhile, the first indoor terminal [slave OSGi device] 30 uses the HTTP-based TCP packet based on its device ID and private IP address [preferably its management agent IP address] through the home gateway 20. The OSGi management server 10 requests (initial) provisioning (305). Here, the first premise terminal 30 includes its management agent IP address in the (initial) provisioning request packet and sets its private IP address as a source in the (initial) provisioning request packet header to the home gateway (20). To send. In addition, it can be confirmed that the management agent IP address and the private IP address (source IP address) of the (initial) provisioning request packet header are the same with respect to the first indoor terminal 30.

Then, the home gateway 20 performs a NAT function on the (initial) provisioning request packet received from the first indoor terminal 30 and transmits the (initial) provisioning request packet of the first indoor terminal 30 to itself. ] Is converted into a public IP address and transmitted to the OSGi management server 10 (306). For example, the source IP address of the (initial) provisioning request packet header of the first indoor terminal 30 is converted into the public IP address of the home gateway by the NAT function of the home gateway 20.

Then, the OSGi management server 10 processes the (initial) provisioning request of the first indoor terminal 30 received from the home gateway 20, and receives the first indoor terminal 30 received from the home gateway 20. The first premises terminal 30 is located in the public IP address area by comparing the management agent IP address included in the (initial) provisioning request packet with the IP header of the (initial) provisioning request packet of the first premises terminal 30. It is determined whether or not located in the private IP address area (307). Here, the OSGi management server 10 processes the (initial) provisioning request of the first indoor terminal 30 according to a known (initial) provisioning processing procedure.

Thereafter, the OSGi management server 10 determines a result of determining the authorized / private IP address area of the first indoor terminal 30 and the management agent IP address of the (initial) provisioning request packet of the first indoor terminal 30. Returning to the first indoor terminal 30 through the home gateway 20 (308). Of course, the OSGi management server 10 also returns the (initial) provisioning processing result to the first indoor terminal 30 through the home gateway 20.

Then, the first indoor terminal 30 transmits a UDP packet through a broadcast to a home network, for example, a neighboring OSGi device while the UDP packet reception daemon is executed based on the IP address returned from the OSGi management server 10. The solution notifies its presence to other OSGi devices on the home network (local network) (309).

According to the broadcasting of the home gateway 20 and the broadcasting of the first indoor terminal 30 as described above, the first indoor terminal 30 uses another OSGi device (ie, a home gateway) through its UDP packet reception daemon. Receiving a UDP packet from the home network recognizes that there is another OSGi device on the home network and stores the IP address and ID information of the other OSGi device recognized in the device mutual information table (310, 311), the home When the gateway 20 receives a UDP packet from another OSGi device (i.e., the first home terminal) through its UDP packet reception daemon, the gateway 20 recognizes that another OSGi device exists on the home network and displays the same in the device mutual information table. The IP address and ID information of another OSGi device recognized as being present are stored (312 and 313).

FIG. 4 is a detailed flowchart illustrating an OSGi device registration process according to the determination of a public / private IP address region location of FIG. 3.

When the OSGi management server 10 waits for an (initial) provisioning request from an OSGi device and receives a (initial) provisioning request packet from a specific OSGi device, the OSGi management server 10 extracts an IP header of the (initial) provisioning request packet. Initially, the management agent IP address included in the provisioning request packet is extracted (401, 402, 403).

The OSGi management server 10 then compares whether the source IP address of the extracted (initial) provisioning request packet IP header and the extracted management agent IP address are the same (404).

As a result of the comparison, if the source IP address and the management agent IP address of the (initial) provisioning request packet IP header are identical to each other (if it is determined that the OSGi device is located in the public IP address area), the OSGi management server 10 (initial) In step 405, the OSGi device requesting provisioning is regarded as a master OSGi device on a corresponding private IP network, and the OSGi device is registered as a master OSGi device on a corresponding private IP network in the own OSGi device information table (405).

On the other hand, if the source IP address and the management agent IP address of the (initial) provisioning request packet IP header is different from each other (if it is determined that the OSGi device is located in the private IP address area), the OSGi management server 10 itself. The OSGi device information table is searched for a master OSGi device having a source IP address of the (initial) provisioning request packet IP header (406).

Thereafter, the OSGi management server 10 registers the OSGi device as a slave OSGi device under its searched master OSGi device in its OSGi device information table (407).

5 is a flowchart illustrating an example of a process of transmitting a command to an OSGi device according to the present invention.

When the home network service control server 50 needs to issue a home network service control command to the home gateway 20 on the home network in a private IP network environment, the device ID of the home gateway 20 and the corresponding home network service control command To the OSGi management server 10 (501 and 502).

The OSGi management server 10 queries the OSGi device information table using the home gateway device ID received from the home network service control server 50 to obtain a public IP address of the master OSGi device of the corresponding private IP network. The acquired public IP address is set as a destination, and the home network service control command is transmitted to the home gateway 20 which is the corresponding destination (503, 504).

Then, the home gateway 20 checks the device ID included in the home network service control command received from the OSGi management server 10 to determine whether it is a home network service control command or a home network service control command to be sent to another OSGi device. Determine (505).

As a result of the determination, the home gateway 20 performs a process corresponding to the home network service control command and confirms that the home network service control command targets the OSGi management server 10. Respond to the home network service control server 50 via (506, 507).

On the other hand, when the home network service control server 50 is to give a home network service control command to the first indoor terminal 30 on the home network in a private IP network environment, the device ID of the first indoor terminal 30 And transmitting the corresponding home network service control command to the OSGi management server 10 (511, 512).

Then, the OSGi management server 10 obtains the public IP address of the master OSGi device of the corresponding private IP network by querying the OSGi device information table by using the first home terminal device ID received from the home network service control server 50. In operation 513 and 514, the acquired public IP address is set as a destination and the home network service control command is transmitted to the corresponding home gateway 20.

Then, the home gateway 20 checks the device ID included in the home network service control command received from the OSGi management server 10 to determine whether it is a home network service control command or a home network service control command to be sent to another OSGi device. Determine (515).

As a result of the determination, it is confirmed that the home network service control command targets another OSGi device, and the home gateway 20 queries the device mutual information table to determine the private IP address of the corresponding home network service control command target OSGi device. In operation 516, the home network service control command is transmitted to the first indoor terminal 30, which is the corresponding destination.

Then, the first indoor terminal 30 performs a process corresponding to the home network service control command received through the home gateway 20 and returns the processing result to the home through the home gateway 20 and the OSGi management server 10. The network service control server 50 responds (517 and 518).

On the other hand, the method of the present invention as described above can be written in a computer program. And the code and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the written program is stored in a computer-readable recording medium (information storage medium), and read and executed by a computer to implement the method of the present invention. The recording medium may include any type of computer readable recording medium.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the technical spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited by the drawings.

1 is a configuration diagram of an embodiment of a communication network to which the present invention is applied;

2 is a configuration diagram of an OSGi device management system in a private IP network environment according to the present invention;

3 is a flowchart illustrating a method of managing an OSGi device in a private IP network environment according to the present invention;

FIG. 4 is a detailed flowchart illustrating an OSGi device registration process according to the determination of a public / private IP address region location of FIG. 3.

5 is a flowchart illustrating an example of a process of transmitting a command to an OSGi device according to the present invention.

* Explanation of symbols on the main parts of the drawing

10: OSGi Management Server

15: home network service control server

20: home gateway [master OSGi device]

30: first indoor terminal [first slave OSGi device]

40: second indoor terminal [second slave OSGi device]

Claims (17)

In a system for managing OSGi devices, The OSGi device and the master OSGi device and the slave OSGi device are provided in the local network of the private IP network environment. The master OSGi device, Performs a private IP address / authorized IP address translation function for the slave OSGi device, registers its own device information according to a provisioning process between OSGi management servers on an external network, and other OSGi devices through broadcasting to the local network. Registers information from, The slave OSGi device, A private IP connected to an external network through the master OSGi device to register its own device information according to provisioning processing between the OSGi management servers, and to register information of another OSGi device through broadcasting to the local network. OSGi device management system in a network environment. In a system for managing OSGi devices, A master OSGi device and a slave OSGi device are provided as OSGi devices in a local network of a private IP network environment. Each of the master OSGi device and the slave OSGi device registers its own device information according to provisioning processing between OSGi management servers on an external network. The OSGi management server, When the provisioning request is received from the OSGi device, the OSGi device is determined to be located in a public IP address area based on the IP address of the OSGi device, and the OSGi device is registered as a master OSGi device or a slave OSGi device of the corresponding private IP network. OSGi device management system in a private IP network environment. The method according to claim 1 or 2, Further comprising a local network service control server for giving a local network service control command to the OSGi device, The local network service control server, Transmit OSGi device information and local network service control commands to the OSGi management server; The OSGi management server, Private IP network, characterized in that to obtain the public IP address of the master OSGi device of the private IP network using the OSGi device information received from the local network service control server and to transmit the local network service control command to the master OSGi device. OSGi device management system in the environment. The method of claim 3, wherein The master OSGi device, Private IP, characterized in that to check the local network service control command target OSGi device based on the OSGi device information included in the local network service control command received from the OSGi management server and deliver the local network service control command to the corresponding OSGi device. OSGi device management system in a network environment. The method of claim 3, wherein The OSGi management server, And comparing a source IP address of an IP header of a provisioning request packet received from the OSGi device with a device IP address included in the provisioning request packet to determine whether the OSGi device is located in a public IP address area. OSGi device management system in the environment. The method of claim 5, wherein The OSGi management server, An OSGi device located in the public IP address area is registered in the OSGi device information table as a master OSGi device on a corresponding private IP network, and an OSGi device not located in the public IP address area [OSGi device located in the private IP address area] ] As a slave OSGi device below the master OSGi device in the OSGi device information table. The method of claim 3, wherein The OSGi device, Send a provisioning request packet to the OSGi management server based on the device ID and device IP address, OSGi device management system in a private IP network environment, characterized in that the first packet is broadcast to the local network based on the IP address returned from the OSGi management server to inform the other OSGi device of its existence. The method of claim 3, wherein The OSGi device, OSGi device management system of a private IP network environment, characterized in that to register the information of the OSGi device in the device mutual information table based on the second packet received from the other OSGi device as a result of the second packet broadcast by the other OSGi device . The method of claim 8, The OSGi device, OSGi device in a private IP network environment, wherein the device mutual information table is queried based on the destination IP address of the specific data received from the OSGi management server or another OSGi device and the specific data is transmitted to the OSGi device of the corresponding destination. Management system. The method of claim 9, The specific data includes at least one of provisioning data, OSGi framework management command, and local network service control command. The method of claim 7, wherein The OSGi device, OSGi device management system in a private IP network environment, characterized in that driven by a master OSGi device or a slave OSGi device by a bundled management agent implemented on the OSGi framework. In a method for managing an OSGi device, The local network of the private IP network environment is equipped with a number of OSGi devices, Sending, by the OSGi device, a provisioning request packet including a device IP address to an OSGi management server on an external network; If the OSGi device receives an IP address from the OSGi management server as a result of the provisioning request packet transmission, broadcasting the first packet to the local network based on the returned IP address to notify another OSGi device of its existence; And Registering the information of the corresponding OSGi device based on the received second packet when the OSGi device receives the second packet from another OSGi device as a result of broadcasting the second packet of another OSGi device. OSGi device management method of a private IP network environment including a. The method of claim 12, When the OSGi device receives the specific data from the OSGi management server or another OSGi device, inquiring the registered OSGi device information based on the destination IP address of the specific data and delivering the specific data to the OSGi device of the corresponding destination. OSGi device management method of the private IP network environment further comprising. The method of claim 13, The specific data includes at least one of provisioning data, OSGi framework management command, and local network service control command. In a method for managing an OSGi device, The local network of the private IP network environment is equipped with a number of OSGi devices, When the OSGi management server receives the provisioning request packet from the OSGi device, determining whether the source IP address of the IP header of the provisioning request packet and the device IP address included in the provisioning request packet are the same; And If the determination result is the same, the OSGi management server registers the OSGi device as a master OSGi device on a corresponding private IP network. If the determination result is different, the OSGi management server registers the OSGi device as a slave below the master OSGi device. OSGi device registration step to register as an OSGi device OSGi device management method of a private IP network environment including a. The method of claim 15, The slave OSGi device registration process of the OSGi device registration step, Searching for a master OSGi device having a source IP address of the provisioning request packet IP header by querying the OSGi device information table by the OSGi management server; And The OSGi management server registering the OSGi device as a slave OSGi device under the searched master OSGi device OSGi device management method in a private IP network environment including a. The method according to claim 15 or 16, When the OSGi management server receives a local network service control command from a local network service control server, acquiring a public IP address of a master OSGi device of a corresponding private IP network using OSGi device information of the local network service control command; And Transmitting, by the OSGi management server, the local network service control command by setting the obtained public IP address as a destination; OSGi device management method of the private IP network environment further comprising.

Images