KR100983137B1 - Residential Gateway System over OSGi technology - Google Patents

Abstract

The present invention relates to a residential gateway (RG) system providing a home network service, and more particularly, to a system design such as a process structure and a protocol stack of an RG system based on an Open Service Gateway initiative (OSGi) technology. to be.

The present invention provides a residential gateway standard based on OSGi, and provides an RG system based on OSGi technology.

Home Network, Home Gateway, OSGi, Framework, Java, HNSN

Description

OSG based residential gateway system {Residential Gateway System over OSGi technology}

1 is a system configuration diagram of an entire network to which the RG of the present invention is applied.

2 shows the software structure of an OSGi based RG in accordance with the present invention.

3 shows an interface structure of OSGi-based RG according to the present invention.

4 shows an interworking model of a conventional OSGi-based home networking middleware.

Explanation of symbols on the main parts of the drawings

10: HNSN 20: home network

30: RG 40a, 40b: local network

31: RG hardware 32: operating system

33: Java Virtual Machine 34: OSGi Framework

35: virtual UPnP device 36: RG agent

37: HMS UI 38: OAM

The present invention relates to a residential gateway (RG) system for providing a home network service (hereinafter, referred to as an RG system), and more particularly, to a process of an RG system based on an Open Service Gateway initiative (OSGi) technology. This is a technology for system design such as structure and protocol stack.

The home networking market is currently converging with various home networking middleware, intelligent information appliances and residential gateways based on various wired and wireless network technologies, and there are numerous service development environments for different H / W platforms, OSs and network protocols. do.

Home networking middleware such as JINI, Home Wide Web (HWW), Home Audio Video Interoperability (HAVi), and Universal Plag and Play (UPnP) have the purpose of communication and control between intelligent information appliances in the home. It acts as a gateway that dynamically delivers services that are distributed by various service providers on a home network.

Under these circumstances, efforts have been made to link dynamic service management functions with control functions for intelligent information appliances of home networking middleware, and as an example, an interworking model of OSGi-based home networking middleware as shown in FIG. 4. Can be mentioned. In other words, by developing a service bundle for home networking middleware and installing it on OSGi, we intend to present an integrated model of both functions.

OSGi defines a standard for dynamic management of services through the same type of application program interface (API) and provides various network standards for internal and external networks by providing framework, which is Java's platform independent service execution environment. We want to integrate technology and technology as a system.

Integrating various network standards and technologies of OSGi-based internal and external networks as one system, the need for residential gateway standards may emerge. However, standardization of residential gateways is still insignificant.

The present invention has been made to solve the above problems, and an object of the present invention is to provide a residential gateway standard based on OSGi and to provide an RG system based on OSGi technology.

The present invention relates to RG hardware; An operating system; Java virtual machine; An OSGi framework; A virtual UPnP device; It provides an OSGi-based residential gateway system characterized in that it comprises an RG agent which is an agent interworking with the central server.

The present invention also provides an OSGi framework; An RG agent implemented in the form of a bundle installed on the OSGi framework; It provides an OSGi-based residential gateway system comprising a UPnP device service registered on the OSGi framework by the RG agent.

Hereinafter, with reference to the accompanying drawings, the configuration and operation of the embodiment of the present invention will be described in detail.

1 is a system configuration diagram of an entire network to which an RG of the present invention is applied, a home network serving node (hereinafter referred to as a 'HNSN') 10 that provides a home network service, and a home network 20 ) Is divided into RG 30 and local networks 40a and 40b.

The HNSN 10 serves as a central server that provides home network services in connection with a PC or SK-VM connected to a network capable of receiving home network services, or a WAP mobile terminal.

The RG 30 is connected to the HNSN 10 through a network or an internet network to receive various additional services. In particular, the RG 30 is responsible for controlling and monitoring home devices, updating and rebooting the RG S / W, and controlling home network devices and network settings using a registration gateway web service. .

The local network 20 may be composed of, for example, an UPnP network 40a and an RS-485 control network network 40b, which is a type of power line communication (PLC), and each of different types of home network devices (UPnP). Camera, PC, Web PAD, lighting device, security device, etc.) are connected to provide information sharing or control functions.

The HNSN 10 and the RG 30 communicate using the HNSN-RG protocol as described below.

2 shows a software structure of OSGi based RG according to the present invention.

The internal software of the RG 30 according to the present invention is an operating system 32, a Java virtual machine 33, an OSGi framework 34, a virtual UPnP device 35, and an RG on the RG hardware 31. It consists of an Agent 36, an HMS User Interface (UI) 37 supporting a graphical interface, and an OAM (Operation, Administration, and Maintenance) 38, which is responsible for setting up the network.

Linux 2.4.18 version is used as the operating system (32), Java virtual machine (33) uses cvm 1.0.1 that meets J2ME / CDC, Sun's Java virtual machine, OSGi framework (34) is Fordy Homenet Use 4DAgent ™.

The virtual UPnP device 35 performs the UPnP protocol like a real UPnP device on the local network instead of the UPnP bundle.

The RG agent 36 is an agent interworking with the HNSN 10 and is a bundle using the OSGi framework 34.

The HMS UI 37 is a bundle that supports a graphical interface, and the OAM 38 is a kind of network management bundle that is in charge of the operation, management, and maintenance of the network.

3 illustrates an interface structure of the OSGi-based RG according to the present invention, and an interface between the RG, a device connected thereto, and a user may be defined as follows.

The devices connected to the RG 30 interwork with the HNSN 10 existing in the HNSN, PC or Web PAD, UPnP device, and control IP network through the RG-H interface, and the registration and authentication of the RG 30 and periodic It provides RG keep-alive message delivery, control and monitoring of devices connected to RG 30, and reboot and update of RG 30.

In addition, RG 30 is connected to premises devices via the RG-D0 and RG-D1 interfaces.

The RG-D0 interface supports a standard UPnP as an interface for devices that support UPnP for a network device connected to the RG IP network of the RG 30.

The RG-D1 interface is centralized by the RS-485 devices by a control box connected to the RS-485 device, and connected to the RG 30 through the RS-232 interface. The interface between this C-Box and RG is RG-D1.

The RG-U interface is a user interface that allows a user to directly control indoor devices, such as a home web PAD, and provides a general web service.

The RG-O interface and the RG-J interface are internal RG interfaces, and the RG-J interface is an API that enables the Java virtual machine 33 to port on the hardware 31 having the operating system 32. The O interface is an API interface between the OSGi framework 34 and the bundles 36, 37, and 38, and provides an API that satisfies the OSGi R3 standard, and provides an API for creating a service provider or a virtual device.

These interfaces are summarized in Table 1 below.                     

Meanwhile, the RG-HNSN interface is a protocol between the RG 30 and the HNSN 10.

RG-HNSN interface is an UPnP protocol with discovery, description, control, and event functions for devices in an IP-based home network. RG registration, authentication, and keep-alive for RG management It is a protocol applied to wide area network (WAN) by adding function.

The RG-HNSN interface has the following features.

1) RG registration / authentication and keep-alive function

2) Discovery function for the device

3) Description of the device

4) Query and control function for the device

5) Event function for device

6) Remote reboot function of RG device

7) Remote update function for S / W on RG                     

8) Remote control function for network forwarding (Port Forwarding) of RG

The RG-HNSN protocol with this function is summarized in Table 2 below.

Detailed description thereof follows the RG-HNSN interface standard.

The agent on the RG side responsible for the communication between the HNSN 10 and the RG 30 is the RG agent 36. The RG agent 36 is implemented in an OSGi bundle to run on an OSGi framework. In addition, since the HNSN 10 and the RG agent 36 communicate using protocols such as SSDP, HTTP, SOAP, and GENA, the RG agent 36 implements each protocol.

The RG agent 36 performs an RG agent function and a device proxy function.

RG agent function

It is responsible for the link between the RG 30 and the HNSN 10, registers the RG 30 or periodically transmits the RG heart-beat, and notifies the end of the RG upon termination. And, it manages the list of devices currently connected to the RG 30, and delivers the list when requested by the HNSN. In addition, when the device list is updated, update information is transmitted to the HNSN.

1) Registration function (function to register RG to HNSN):

The RG agent 36 sends a registration message when registering with the HNSN. At this time, the RG agent 36 sends the access information and the RG ID / password. The HNSN first authenticates using the RG ID / password. If successful, the HNSN stores the connection information of the RG and responds with an OK.

2) Heart-beat function (to inform HNSN periodically of the current state of RG):

If the RG agent 36 succeeds in registration, it periodically sends a HRT-beat of the RG 30 to the HNSN 10 by sending the current IP information of the RG 30 with an Alive message to the HNSN 10 periodically. And manage the IP information of the RG 30.

3) Graceful bye function (to inform HNSN when RG terminates and exit):                     

By sending a Bye message to the HNSN 10 when the RG agent 36 is normally terminated or rebooted, the HNSN 10 can manage the status information of the RG 30.

4) Maintain connected device list (manage list of devices currently connected to RG and send to HNSN):

When requested by the HNSN 10, it transmits a list of premises devices connected to the RG (30).

5) New Device Notify feature (to detect newly connected devices, update the list of devices, and forward the detection of new devices to HNSN):

If the new home device is connected to the RG 30 and the RG 30 detects it, the RG agent 36 sends information of the newly attached device to the HNSN 10 to update the list of devices.

Device proxy function

It periodically reports the current state of the RG 30 to the HNSN 10 and acts as a proxy for the devices installed in the home and connected to the RG 30.

1) Device control function (to perform device control request of HNSN):

 When the RG agent 36 receives a device control command from the HNSN 10, the RG agent 36 finds the device and performs control. The result is then transmitted back to the HNSN 10.                     

2) Device State Query Function (Performs Device Current State Query Request of HNSN):

The same is true for a query that can check the device status. When the HNSN 10 transmits a query command to the RG agent 36, the RG agent 36 checks the state of the corresponding device and transmits the state value to the HNSN 10.

3) Device Event Subscription / Unsubscription Function (HNSN subscribes and cancels event subscriptions for the device):

The HNSN 10 may subscribe to an event of a specific device. In order to subscribe to an event, an event subscription request is made to the RG agent 36. When the event subscription is no longer needed, the subscription may be canceled.

4) Device Event Notification function (sends an event generated by a device to the HNSN that subscribed to the event for that device):

When a state of a device changes, an event occurs, and the RG agent 36 transmits the event message to the HNSN 10 requesting to subscribe to the event.

4 shows the RG agent structure in relation to HNSN.

Communication with the HNSN 10 uses an UpnP based HNSN-RG protocol.

Based on TCP / IP technology, UPnP uses device information such as HTTP, Simple Service Discovery Protocol (SSDP), General Event Notification Architecture (GENA), and Simple Object Access Protocol (SOAP), which are currently used on the Internet. Collect and control your device.

SSDP Protocol :

The HNSN 10 and the RG agent 36 transmit M-SEARCH, NOTIFY, etc. requests to each other using the SSDP / UDP.

1) M-SEARCH

It is mainly a request that the HNSN 10 sends to the RG agent 36 and is used when the HNSN 10 wants to obtain a list of premises devices connected to the RG 30. Typically requested when the RG Air Agent 36 registers or when the user "refreshes" the list of RG devices' premises devices via the HNSN UI. Upon receiving this request, the RG 30 identifies the devices currently connected to the home and responds to the HNSN 10 with the web URL of the description file describing the device in a location header of HTTP 200 OK for each device.

2) NOTIFY

When the RG agent 36 requests registration with the HNSN 10 and the HNSN 10 responds, the RG agent 36 transmits a list of devices already detected by the HNSN 10 to the HNSN 10 through SSDP / NOTIFY. In this case, like the response of M-SEARCH, the URL of the description file for the device is transmitted together with the location header.

HTTP protocol :

The HNSN 10 is used to download an XML file from the description URL received through the SSDP to the RG agent 36.

SOAP protocol :

When the RG agent 36 becomes a control point and a device proxy, it is used in two cases.

1) When the RG agent is a control point

Sends a request such as Registration / Alive / Bye / SetPreference / GetPreference to the HNSN 10.

(1) Registration SOAP Request

Assuming that the RG 30 basically knows the connection information for the HNSN 10, once the RG 30 is booted and the engine is executed, it first requests registration to the SOAP port of the HNSN 10. The HNSN 10 performs authentication and if successful, responds with an OK to complete the registration. If the authentication fails or there is an error, the HNSN 10 responds with a 500 error. If the RG 30 receives a 500 error, it waits for an appropriate time and attempts to re-register.

(2) Alive SOAP Request

If the RG 30 succeeds in registration, it periodically requests Alive from the HNSN 10 thereafter. The reason for periodically alive is to allow the HNSN 10 to know the abnormality of the RG 30 when the RG 30 operates abnormally or terminates unexpectedly. In addition, when the RG 30 has a floating IP, when the IP of the RG 30 is changed, the HNSN 10 can manage the changed IP.                     

(3) Bye SOAP Request

When the RG 30 is normally terminated by a user or an administrator, a Bye request is made to the HNSN 10. When the HNSN 10 receives Bye, it changes the state information of the RG to power-down and responds with OK. Upon receiving the OK, the RG 30 is completely terminated.

(4) SetPreference SOAP Request

Access to the RG (30), and set the authority to control and monitor the device connected to the RG (30).

(5) GetPreference SOAP Request

Access to the RG 30 set in the HNSN 10 is obtained, and the authority to control and monitor the device connected to the RG 30 is obtained.

2) If the RG agent is a device proxy

When the HNSN 10 wants to control / query one of the devices in the list of devices connected to the RG 30, it transmits a SOAP Request to the RG agent 36 and receives the result / status information.

(1) Control SOAP Request

When the HNSN 10 tries to control a specific device, it sends a Control SOAP Request to the RG agent 36 to control the device, and the RG agent 36 controls the actual device and then sends the result to the Control SOAP Response. To respond to the HNSN (10).

(2) Query SOAP Request                     

If the HNSN 10 wants to know the status information of a specific device, it sends a Query SOAP Request to the RG agent 36 to query the status information of the device, and the RG agent 36 reads the current status information of the actual device. After that, the status information is included in the Query SOAP Response and responded to the HNSN 10.

GENA Protocol :

It is used when HNSN 10 subscribes / cancels an event subscription to notify a specific device connected to one RG 30 and notifies an event that has occurred in the device.

1) Subscribe Request

The HNSN 10 requests when it wants to subscribe to an event of a specific device of one RG 10. The RG agent 36 stores the subscription of the HNSN 10 and processes it when an event occurs in the corresponding device, and transmits the event to the HNSN 10 in a GENA / Notify Request.

2) Unsubscribe Request

Requested when the HNSN 10 wants to unsubscribe from an event of a specific device of an RG 30. The RG agent 36 deletes the subscription of the stored HNSN 10 and does not transmit a Notify Request to the HNSN 10 even if an event occurs in the corresponding device later.

3) Notify Request

When an event occurs in the device when the subscription of the HNSN 10 for one device is stored in the RG 30, the RG 30 transmits a Notify Request by including the content of the event to the HNSN 10.

5 is a diagram illustrating an internal structure of an RG according to the present invention. The relationships between an RG agent, an OSGi framework, an UPnP bundle, and an UPnP device service are as follows.

Relationship to the OSGi Framework

The RG agent 36 is implemented in the form of a bundle that is installed on an OSGi framework (hereafter referred to as a framework) and is a typical bundled application that can be run with a Bundle Activator. You can import and use packages provided by other bundles, and you can get and use services registered by other bundles.

The RG agent 36 constructs a device list by importing UPnP device services registered on the framework 34, and registers and unregisters UPnP device services in real time by registering a service watcher on the framework 34. And monitor changes. In addition, an event of a specific device may be subscribed to by registering a UPnP event listener service that listens for an event occurring in the UPnP device service to the framework.

Relationship to UPnP Bundles

There is no direct relationship between the RG agent 36 and the UPnP bundle, but indirectly through the framework 34. The UPnP event listener service registered by the RG agent 36 on the framework 34 is managed by the UPnP bundle, and events generated from the UPnP event listener service are collected by the UPnP bundle and delivered to the corresponding UPnP event listener.

Relationship to UPnP Device Services

The devices that the RG agent 36 sends to the HNSN 10 are UPnP device services rather than physical devices that are actually connected to the RG 30. Communicating with a physical device with an interface is an implementation of the UPnP device service.

These UPnP device services fall into two categories. One registers UPnP device services directly on the framework 34 in one bundle, and the other detects UPnP devices existing on the local network 20 connected to the RG via the UPnP protocol and then UPnP. The device service is created and registered on the framework 34. In the former, the UPnP bundle instead performs the UPnP protocol on the local network like a real UPnP device, also called a virtual UPnP device.

The RG agent 36 recognizes both as UPnP device services without distinction, and transmits the device list to the HNSN 10 when it is requested to transmit the device list to the HNSN 10. When the registration or deregistration of the UPnP device service is found through the service listener registered on the framework 34, the device list is updated in HNSN in real time through SSDP-Notify-Alive or SSDP-Notify-Byebye.

When the RG agent 36 receives the device control and status query request from the HNSN, it calls the API of the UPnP device service being managed. The returned value is then returned to the HNSN 10. When the API of the UPnP device service is called, if it is a real UPnP device existing on the local network 20, the UPnP bundle instead sends a SOAP message to the real UPnP device, receives a response, and returns it, if it is a virtual UPnP device. In this case, the UPnP device service implementation actually controls the connected physical device, receives a response, and returns it.

According to the present invention, all devices connected to a home network are integratedly managed through OSGi-based residential gateways, and detailed information about these devices can be obtained.

In addition, the present invention proposes a standard of a residential gateway based on OSGi, thereby providing more diverse and high-quality home network services and facilitating device and service scalability.

Claims (21)

In a residential gateway (RG) system that provides various additional services through a home server (HNSN) that provides home network services, RG hardware; An operating system; Java virtual machine; An OSGi framework; A virtual UPnP device; OSGi-based residential gateway system characterized in that it comprises an RG agent which is an agent interworking with the HNSN. The OSGi-based residential gateway system according to claim 1, further comprising an HMS UI supporting a graphical interface and an OAM in charge of network configuration. The OSGi-based residential gateway system according to claim 2, wherein the HMS UI is a bundle supporting a graphical interface, and the OAM is a kind of network management bundle in charge of operation, management, and maintenance of a network. The OSGi based residential gateway system of claim 1, wherein the virtual UPnP device performs a UPnP protocol as a real UPnP device on a local network. The OSGi-based residential gateway system of claim 1, wherein the RG agent is a bundle using an OSGi framework, and implements HNSN, SSDP, HTTP, SOAP, and GENA protocols, respectively. The method of claim 1, wherein the RG agent performs an RG agent function and a device proxy function, wherein the RG agent function includes: RG registration, periodic RG heartbeat transmission, RG end notification, device list management currently connected to RG, OSGi, characterized in that the device list transmission to the HNSN, update information transmission to the HNSN when the device list is updated, the device proxy function includes device control, device status query, device event request / cancellation, device event notification Based residential gateway system. The RG agent of claim 1, 5 or 6, wherein the RG agent comprises an RG-HNSN interface, an RG-UPnP device interface, an RG-RS485 device interface, an RG-user web interface, and a Java virtual machine porting interface. And an OSGi framework application program interface. The method according to claim 7, wherein the RG agent is linked to the HNSN existing in the control IP network using the RG-HNSN interface, registration and authentication of the RG (30), periodic RG keep-alive message delivery and devices connected to the RG OSGi-based residential gateway system that provides control and monitoring, reboot and bundle updates for RG. The method according to claim 7, wherein the RG agent is connected to the indoor devices using the RG-UPnP device interface and the RG-RS485 device interface, the RG-UPnP device interface is a UPnP for the network device connected to the indoor IP network of the RG And the RG-RS485 device interface centralizes RS485 devices by a control box connected to the RS485 device. 8. The OSGi based residential gateway system of claim 7 wherein the RG agent enables a user to directly control premises devices using an RG-user interface. 8. The OSGi based residential gateway system of claim 7, wherein the RG agent enables porting on a hardware on which a Java virtual machine has an operating system using a Java virtual machine porting interface. 9. 8. The OSGi based residential gateway system of claim 7 wherein the RG agent provides interfacing between the OSGi framework and the bundle using an OSGi framework application program interface. The OSGi-based residential gateway system according to claim 7, wherein the RG-HNSN interface is an UpnP-based HNSN-RG protocol in which the HNSN and RG communicate. The RG-HNSN interface of claim 13, wherein the RG-HNSN interface adds RG registration, authentication, and keep-alive functions for RG management to the UPnP protocol having discovery, description, control, and event functions for devices in an IP-based home network. OSGi-based residential gateway system, characterized in that the protocol applied to the network (WAN). An OSGi framework; An RG agent implemented in the form of a bundle installed on the OSGi framework; And a UPnP device service registered on the OSGi framework by the RG agent. The OSGi based residential gateway system of claim 15, wherein the RG agent imports the UPnP device services to form a device list. The OSGi-based residential gateway system according to claim 15, wherein the RG agent registers a service watcher on an OSGi framework to monitor registration, deregistration, and change of UPnP device services in real time. The OSGi-based residential gateway system according to claim 15, wherein the RG agent can subscribe to events of a specific device by registering a UPnP event listener service with the framework that can listen to events occurring in the UPnP device service. The method according to claim 16, wherein the UPnP event listener service registered by the RG agent on the framework is managed by a UPnP bundle, and events generated from the UPnP event listener service are collected by the UPnP bundle and delivered to a corresponding UPnP event listener. OSGi based residential gateway system. The UPnP device service of claim 15, wherein the UPnP device service detects an UPnP device service in which a UPnP device service is directly registered in a bundle on a framework or an actual UPnP device existing on a local network to which the UPnP bundle is connected to an RG through the UPnP protocol. The OSGi-based residential gateway system, characterized in that any one of the UPnP device services registered in the framework by creating a UPnP device service. 21. The OSGi based residential gateway system according to claim 20, wherein the RG agent recognizes both as UPnP device services.

Images