JP2011039819A - Service registration device using httpservice, content registration device, service registration method, content registration method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To control an access to a content registered using a service, for each network interface. <P>SOLUTION: When a service implementing providing function 11 starts an HTTP server corresponding to Http Service, a network interface is bound to start the HTTP server, and thus the HTTP server discloses the content only for the access via the bound network interface. Therefore, a bundle for registering the content using Http Service allows access control for each network interface. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for registering an HTTP Service for registering content to be published in a service registry of an OSGi framework.

  The OSGi (Open Service Gateway Initiative) framework is a framework for managing the dynamic addition, deletion, or execution of software components. A unit of software components operating on the OSGi framework is called a bundle. The bundle is a program written in Java (registered trademark), and is a compressed file in a JAR (Java Archive) format. The bundle is distributed via a network, for example. The bundle is received and executed by a device that implements the OSGi framework.

  In the OSGi specification, an OSGi service specification from Release 1 to HTTP Service is defined. HTTP Service provides an HTTP server and a Java Servlet container running on it. Bundles can dynamically register resources such as HTML files and images, and Java Servlets with the HTTP server using methods defined in HTTP Service. Resources registered by a bundle using a method defined in the HTTP Service and Java Servlet are published according to the HTTP protocol by an HTTP server provided by the HTTP Service.

  FIG. 16 is a block diagram showing the configuration of a conventional service registration apparatus. The service registration apparatus 100 shown in the figure includes a service implementation providing function 110, a service property creation function 120, a service registration function 130, and a service registry 140. Hereinafter, processing for registering an HTTP Service implementation object will be described.

  First, the service implementation providing function 110 creates an object that implements the HTTP Service interface, the service property creation function 120 creates a service property that describes settings such as a port number, and the service implementation provision function 110 creates an HTTP. Start the server. These processes are performed in parallel, but the startup time of the HTTP server may be delayed.

  Subsequently, the service implementation providing function 110 passes a reference to the created HTTP Service implementation object to the service registration function 130, and the service property creation function 120 passes the created service property to the service registration function 130. The service property passed at this time may be null.

  The service registration function 130 adds a service property to the received reference to the HTTP Service implementation object, and registers the service in the service registry by calling a method of the BundleContext interface of the OSGi framework.

  Next, a process in which the bundle 200 registers contents using the HTTP service will be described. As shown in FIG. 16, the bundle 200 has a service acquisition function 210 and a content registration function 220. Here, resources, Java Servlets, and the like are collectively referred to as contents.

  First, the service acquisition function 210 acquires an HTTP Service implementation object registered in the service registry 140 by specifying a service name using a method in accordance with the OSGi specification, that is, a method of the BundleContext interface, and registers the content. Pass to function 220.

  The content registration function 220 registers content by calling a method of the passed HTTP Service implementation object. More specifically, a content registration request is issued by designating a content and an alias indicating the access destination of the content on the HTTP server and calling a method of the HTTP Service interface.

  When the service implementation providing function 110 receives a content registration request via the HTTP Service interface, the service implementation providing function 110 sets the HTTP server so as to return the corresponding content when the designated alias is accessed. Thus, when the HTTP client 300 accesses the HTTP server using the HTTP protocol, the service implementation providing function 110 receives the access and returns the content. If the corresponding content does not exist, an error code according to the HTTP protocol is returned.

OSGi, "OSGi Service Platform: Release 3, March 2003", March 2003

However, when the service registration apparatus 100 has a plurality of network interfaces and the contents are registered using the HTTP Service, the contents are released for access from the plurality of network interfaces. In other words, it is not possible to restrict the disclosure that the content registered using the HTTP Service is made public only for access from a specific network interface, and is not made public for access from other than the network interface. There's a problem. More specifically, for example, a home gateway device having a network interface on the LAN side and the WAN side includes the service registration device 100, and a bundle 200 including content that is desired to be disclosed only to the LAN side is registered as a service. When content is registered using the HTTP service of the device 100, there is a problem that the content registered by the bundle 200 can be accessed from the WAN side. As one solution to this problem, the Servlet registered by the bundle 200 can acquire the IP address and FQDN (Fully Qualified Domain Name) of the HTTP client 300 that sent the request, and individually restrict access. However, there is a problem that a Servlet implementation program becomes complicated.
In addition, regarding resources that are static contents such as HTML files and images, it is impossible to limit the content disclosure destination.

  The present invention has been made in view of the above, and an object of the present invention is to enable access control for each network interface for content registered using a service.

  The service registration device according to the first aspect of the present invention is configured to accept a network interface selection unit that selects a network interface from which a server that publishes content accepts access, and an access addressed to the IP address assigned to the selected network interface. A server activation unit that activates the server, a service generation unit that generates a service that accepts registration of content published by the server, and a property that generates a service property that describes the setting of the service and the information of the network interface And a service registration unit that adds the service property to the service and registers the service property in the service registry.

  In the service registration apparatus, the service registration unit registers the service in a service registry without waiting for the completion of activation of the server.

  In the service registration apparatus, the server activation means activates the server when the service accepts content registration.

  In the service registration apparatus, the service registration apparatus includes information management means for storing correspondence between the service and information of a network interface that the server corresponding to the service accepts access from. The server is activated to read out interface information and accept only access via the network interface.

  In the service registration apparatus, when the server detects a change in an IP address assigned to a network interface that accepts access, and there is a change in the IP address assigned to the network interface, an access addressed to a new IP address The server is restarted so as to accept.

  A content registration device according to a second aspect of the present invention is a content registration device that acquires a service registered in a service registration device and registers content, and a network interface selection unit that selects a network interface that publishes the content. A condition search expression creating means for creating a condition search expression for searching for a desired service from the service registration apparatus based on the selected information of the network interface; and from the service registration apparatus using the condition search expression Service acquisition means for acquiring a service, and content registration means for registering the content using the acquired service.

  A service registration method according to a third aspect of the present invention includes a step of selecting a network interface from which a server that publishes content accepts access, and accepting access to an IP address assigned to the selected network interface. , Generating a service that accepts registration of content published by the server, generating a service property that describes the settings of the service and the network interface, and providing the service with the service Adding a property and registering the property in the service registry.

  The service registration method is characterized in that the service is registered in a service registry without waiting for completion of startup of the server.

  In the service registration method, the server is activated when the service accepts content registration.

  In the service registration method, the network interface information is read from the information management means for storing the correspondence between the service and the network interface information that the server corresponding to the service accepts access, and only access via the network interface is performed. The server is activated so as to accept the server.

  In the service registration method, the server detects a change in an IP address assigned to a network interface that accepts access, and if there is a change in the IP address assigned to the network interface, it is addressed to a new IP address. And restarting the server to accept the access.

  A content registration method according to a fourth aspect of the present invention is a content registration method for registering content by acquiring a service registered in a service registration device, the step of selecting a network interface for publishing the content, Creating a condition search expression for searching for a desired service from the service registration apparatus based on the information of the network interface; acquiring the service from the service registration apparatus using the condition search expression; And registering the content using the acquired service.

  According to a fifth aspect of the present invention, there is provided a program for causing a computer to function as each means constituting the service registration device or the content registration device.

  A recording medium according to a sixth aspect of the present invention records the above program.

  According to the present invention, it is possible to control access to content registered using a service for each network interface.

It is a block diagram which shows the structure of the service registration apparatus in 1st Embodiment. It is a flowchart which shows the flow of the process which registers a service in 1st Embodiment. It is a flowchart which shows the flow of the process in which a bundle registers a content using a service in 1st Embodiment. It is a flowchart which shows the flow of the process which registers a service in 2nd Embodiment. It is a flowchart which shows the flow of the process which registers a service in 3rd Embodiment. It is a flowchart which shows the flow of the process in which a bundle registers content using a service in 3rd Embodiment. It is a block diagram which shows the structure of the service registration apparatus in 4th Embodiment. It is a flowchart which shows the flow of the process which registers a service in 4th Embodiment. It is a figure which shows the example of the management table which an information management function hold | maintains. It is a flowchart which shows the flow of a starting process of the HTTP server in 5th Embodiment. It is a flowchart which shows the flow of a process after detecting the change of an IP address in 5th Embodiment. It is a flowchart which shows the flow of the process in which a bundle registers content using a service in 5th Embodiment. It is a flowchart which shows the flow of the process in which a bundle registers content using a service in 6th Embodiment. It is a block diagram which shows the structure of a bundle. It is a flowchart which shows the flow of a process in which a bundle acquires a service and issues a content registration request. It is a block diagram which shows the structure of the conventional service registration apparatus.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram illustrating a configuration of a service registration apparatus according to the first embodiment. The service registration apparatus 1 shown in FIG. 1 includes a service implementation providing function 11, a service property creation function 12, a service registration function 13, a service registry 14, and a network interface information acquisition function 15. The service registration device 1 may be configured by a computer including an arithmetic processing device, a storage device, a memory, and the like, and processing of each function may be executed by a program. This program is stored in a storage device included in the service registration device 1, and can be recorded on a recording medium such as a magnetic disk, an optical disk, or a semiconductor memory, or provided through a network. Each function will be described below.

  The service implementation providing function 11 starts an HTTP server and generates an object that implements an HTTP Service interface. The HTTP Service is a service whose specifications are defined by OSGi and dynamically registers content published by an HTTP server. Content registration is performed by a bundle calling a method of an HTTP Service implementation object generated by the service implementation providing function 11. Hereinafter, the HTTP Service implementation object may be simply referred to as “Http Service”.

  The service implementation providing function 11 binds the IP address of a predetermined network interface and activates the HTTP server. Information on the network interface to be bound is obtained from the network interface information acquisition function 15.

  When starting the HTTP server, there are two methods for establishing a TCP server socket: one that does not bind to the IP address of any network interface and the other that binds to the IP address of a specific network interface. When the HTTP server is not bound to the IP address of the network interface, that is, in the case of the conventional service registration apparatus 100 shown in FIG. 16, the HTTP server can accept a TCP connection connection request via an arbitrary network interface. For example, if the service registration apparatus 100 has two network interfaces on the LAN side and the WAN side, the connection to the HTTP server accepts access to the IP address of any network interface, and both the LAN side and the WAN side The content will be released.

  On the other hand, when the HTTP server is bound to the IP address of a specific network interface, that is, in the case of the service registration apparatus 1 in the present embodiment, the HTTP server accepts only a TCP connection connection request via the bound network interface. It becomes possible to publish content only for access via the network interface bound by the HTTP server. In the embodiment shown in FIG. 1, one HTTP server is bound to the network interface eth0, and the other HTTP server is bound to the network interface ppp0. The network interface here means not a physical network interface but a logical network interface. For example, the loopback interface represented by 127.0.0.1 is also applicable.

  The service property creation function 12 creates a service property describing the setting of the HTTP Service. The identifier of the network interface to be bound is assigned to the service property as the service property value for the specific key name. Information on the network interface to be bound is obtained from the network interface information acquisition function 15. As a service property key name, for example, “BoundNwIfId” is a character string of a network interface name such as eth0 or ppp0, or a number such as 0, 1, 2, 3 is used as a service property value. It is conceivable that

  The service registration function 13 receives a reference to the HTTP Service implementation object from the service implementation providing function 11 and receives a service property from the service property creation function 12. Then, the service property is added to the reference to the HTTP Service implementation object and registered in the service registry 14. Service registration in the service registry 14 is performed by calling a method of the BundleContext interface of the OSGi framework.

  In the service registry 14, an HTTP service to which a service property is assigned is registered. The bundle 2 acquires the http service from the service registry 14 and registers the content by calling the method of the http service. When the bundle 2 acquires the HTTP Service from the service registry 14, the HTTP service is acquired in which the identifier of the network interface to which the content registered by the bundle 2 is to be disclosed is assigned as the service property value of the specific key name. Acquisition of the HTTP Service by the bundle 2 will be described later.

  The network interface information acquisition function 15 acquires information on a network interface that binds to an HTTP server. As a method of acquiring network interface information, a method of reading from a specific system property or a setting file is conceivable, but the method is not limited to this. The information acquired by the network interface information acquisition function 15 includes an identifier of the network interface to be given as a service property value.

  Next, service registration processing by the service registration apparatus 1 will be described. Registration of the HTTP Service in the service registry 14 is started by the bundle. The bundle is received by, for example, the service registration apparatus 1 via the network, and the service registration process is started by the received bundle. The service registered in the service registry 14 can use another bundle.

  FIG. 2 is a flowchart showing a flow of processing in which the service registration apparatus according to the first embodiment registers the HTTP Service.

  When the registration process of the HTTP Service is started, the service implementation providing function 11 creates an object that implements the HTTP Service interface (Step S11).

  The network interface information acquisition function 15 acquires information on the network interface to be bound and sends it to the service implementation providing function 11 and the service property creation function 12 (step S12).

  The service property creation function 12 creates a service property to which information received from the network interface information acquisition function 15, specifically, a network interface identifier is assigned as a service property value for a specific key name (step S13).

  The service implementation providing function 11 activates an HTTP server corresponding to the created HTTP service (step S14). When starting the HTTP server, the server socket of the HTTP server is bound to the IP address assigned to the predetermined network interface based on the information received from the network interface information acquisition function 15.

  When the creation of the object, creation of the service property, and activation of the HTTP server are completed, the service registration function 13 registers the HTTP Service in the service registry 14 (Step S15). The service registration function 13 receives a reference to the HTTP Service from the service implementation providing function 11, adds the service property received from the service property creation function 12, and registers it in the service registry 14. Service registration in the service registry 14 is performed by calling a method of the BundleContext interface of the OSGi framework.

  In this way, the HTTP service is registered in the service registry 14. The HTTP Service registered in the service registry 14 can be acquired and used by other bundles.

  Next, processing for registering content using the HTTP Service will be described. The bundle 2 acquires the HTTP Service corresponding to the HTTP server bound with the network interface to which the content to be registered is made public from the service registry 14 and registers the content using the HTTP Service. More specifically, an HTTP service in which an identifier of a desired network interface is assigned as a service property value of a specific key name is acquired from the service registry 14, and an alias indicating the content and an access destination of the content on the HTTP server is acquired. The HTTP Service method acquired by specifying is called to issue a content registration request. The content includes resources such as HTML files and images, and Servlet.

  FIG. 3 is a flowchart showing the flow of processing performed by the service implementation providing function 11 when the bundle 2 registers content using the HTTP Service. When content registration is requested by the bundle 2, the service implementation providing function 11 receives a request for content registration through the HTTP Service, and the HTTP client 300 uses the HTTP protocol for the HTTP server corresponding to the HTTP Service for which the method is called. In step S21, the HTTP server is set so that the designated content is returned when the designated alias is accessed.

  In this way, the bundle 2 calls the HTTP Service method to register the content. Since the HTTP server that publishes the registered content is bound to a specific network interface, the registered content is published only for access via the network interface.

[Second Embodiment]
Next, a second embodiment will be described. Since the configuration of the service registration apparatus in the second embodiment is almost the same as the configuration of the service registration apparatus in the first embodiment, detailed description thereof is omitted. The second embodiment is different from the first embodiment in that the HTTP service is registered in the service registry 14 without waiting for completion of the startup of the HTTP server. The service registration process according to the second embodiment will be described below with reference to the drawings.

  FIG. 4 is a flowchart showing a flow of processing in which the service registration apparatus according to the second embodiment registers the HTTP Service.

  When the registration process of the HTTP Service is started, the service implementation providing function 11 creates an object that implements the HTTP Service interface (Step S31).

  The network interface information acquisition function 15 acquires information on the network interface to be bound and transmits it to the service implementation providing function 11 and the service property creation function 12 (step S32).

  The service property creation function 12 creates a service property to which information received from the network interface information acquisition function 15, specifically, a network interface identifier is assigned as a service property value for a specific key name (step S33).

  The service implementation providing function 11 starts an HTTP server corresponding to the created HTTP Service (step S34). When starting the HTTP server, the HTTP server is bound to the IP address of a predetermined network interface based on the information received from the network interface information acquisition function 15.

  Here, the service registration function 13 registers the HTTP Service in the service registry 14 without waiting for completion of activation of the HTTP server (step S35). When the HTTP Service is registered in the service registry 14, the bundle 2 can register the content using the HTTP Service, but if the HTTP server has not been started at that time, the bundle server 2 Access using the HTTP protocol is not possible. The HTTP server may be started after registration of the HTTP Service.

  The process of registering content using the HTTP Service is the same as that in the first embodiment, and a description thereof will be omitted.

[Third Embodiment]
Next, a third embodiment will be described. Since the configuration of the service registration apparatus in the third embodiment is substantially the same as the configuration of the service registration apparatus in the first embodiment, detailed description thereof is omitted. The third embodiment is different from the first embodiment in that the HTTP server is not activated when registering an HTTP service, and the HTTP server is activated when a bundle registers content using the HTTP service. . The service registration process in the third embodiment will be described below with reference to the drawings.

  FIG. 5 is a flowchart showing a flow of processing in which the service registration apparatus according to the third embodiment registers the HTTP Service.

  When the registration process of the HTTP Service is started, the network interface information acquisition function 15 acquires information on the network interface to be bound and transmits it to the service implementation providing function 11 and the service property creation function 12 (step S41).

  The service implementation providing function 11 creates an object that implements the HTTP Service interface (step S42). At this time, the service implementation providing function 11 stores the information of the network interface to be bound in the created HTTP Service implementation object without starting the HTTP server.

  The service property creation function 12 creates a service property to which information received from the network interface information acquisition function 15, specifically, a network interface identifier is assigned as a service property value for a specific key name (step S43).

  When the creation of the object and the creation of the service property are completed, the service registration function 13 assigns the service property to the HTTP service and registers it in the service registry 14 (step S44).

  As described above, the HTTP Service is registered in the service registry 14. At the time when the HTTP service is registered, the HTTP server is not activated. In the third embodiment, the HTTP server is activated when the bundle 2 registers content using the HTTP Service. Hereinafter, processing performed by the service implementation providing function 11 when the bundle 2 registers contents using the HTTP Service will be described.

  FIG. 6 is a flowchart showing a flow of processing in which the bundle 2 registers content using the HTTP Service.

  When the bundle 2 issues a request for content registration by calling an HTTP Service method, the service implementation providing function 11 determines whether the content has already been registered in the HTTP Service (step S51). If the content is not registered, that is, if the number of registered content is 0, the HTTP server has not been activated yet, and the process proceeds to the HTTP server activation process in step S52. If the content has already been registered, that is, if the number of registered content is not 0, the HTTP server is activated, and the process proceeds to the content publishing process in step S54.

  When activating the HTTP server, the service implementation providing function 11 acquires information on the network interface held by the HTTP Service that has requested content registration (step S52). This network interface information is information on the network interface to be bound received from the network interface information acquisition function 15 at the time of http service registration.

  Then, the service implementation providing function 11 activates an HTTP server corresponding to the HTTP Service for which content registration has been requested (step S53). When starting the HTTP server, the HTTP server is bound to the IP address of a predetermined network interface based on the network interface information acquired in step S52. After starting the HTTP server, the process proceeds to the content publishing process.

  When the HTTP server is activated, the HTTP service sets the HTTP server in a state where the designated content is released for access to the alias designated by the bundle 2 (step S54).

  As described above, in the third embodiment, the HTTP server is not activated until the content is actually registered using the HTTP Service. That is, since the HTTP server is activated as necessary, it is possible to reduce the resource consumption of the computer such as the memory consumption. When the registered content is deleted and the registered number of content becomes 0, the HTTP server can be stopped.

[Fourth Embodiment]
Next, a fourth embodiment will be described. In the fourth embodiment, as in the third embodiment, an HTTP server is activated as necessary. As shown in FIG. 7, the configuration of the service registration apparatus according to the fourth embodiment includes an information management function 16 for storing a pair of the HTTP Service and the corresponding network interface information to be bound. Different from the service registration apparatus in the first to third embodiments.

  FIG. 8 is a flowchart illustrating a flow of processing in which the service registration apparatus according to the fourth embodiment registers the HTTP Service.

  When the registration process of the HTTP Service is started, the network interface information acquisition function 15 acquires information on the network interface to be bound and transmits it to the service implementation providing function 11 and the service property creation function 12 (step S61).

  The service implementation providing function 11 creates an object that implements the http service interface (step S62). Then, the created HTTP Service implementation object and the corresponding network interface to be bound are associated with each other and registered in the information management function 16 (step S63). FIG. 9 shows an example of a management table held by the information management function 16. In the management table shown in the figure, an HTTP Service implementation object is placed as a key on the left side, and corresponding network interface information is placed as a value on the right side.

  The service property creation function 12 creates a service property in which information received from the network interface information acquisition function 15, specifically, a network interface identifier is assigned as a service property value for a specific key name (step S64).

  When object creation and service property creation are completed, the service registration function 13 registers the HTTP Service in the service registry 14 (step S65).

  As described above, the HTTP Service is registered in the service registry 14. When the HTTP service is registered, the HTTP server is not activated. In the fourth embodiment, as in the third embodiment, the HTTP server is activated when the bundle 2 registers content using the HTTP Service.

  Since the process of registering content using the HTTP Service is the same as that of the third embodiment except for the method for acquiring the network interface information, detailed description thereof is omitted.

  In the fourth embodiment, the service implementation providing function 11 makes an inquiry to the information management function 16 using the HTTP Service for which content registration has been requested as a key, in order to acquire network interface information when starting the HTTP server. Then, the information of the network interface to be bound is acquired from the information management function 16.

[Fifth Embodiment]
Next, a fifth embodiment will be described. In the fifth embodiment, an HTTP service is created and a service property is created as in the first embodiment. When an HTTP server is started, an IP address is assigned to the network interface to be bound. It is different in that a process for determining whether or not there is is performed. For example, there may be a case where an IP address is not assigned, such as when the network interface acquires an IP address using a DHCP server. If the IP address is not assigned, the IP address of the network interface cannot be bound and the HTTP server cannot be activated. Therefore, in the fifth embodiment, an IP address is assigned to the network interface to be bound when the HTTP server is activated. It is determined whether or not Here, the processes such as the creation of the HTTP service and the creation of the service property are the same as those in the first embodiment, so that the description thereof will be omitted and the HTTP server startup process will be described.

  FIG. 10 is a flowchart illustrating HTTP server activation processing according to the fifth embodiment.

  First, the service implementation providing function 11 determines whether or not an IP address is assigned to the network interface to which the HTTP server to be activated binds (Step S71). If no IP address is assigned to the network interface, the process proceeds to step S73 and waits for an IP address to be assigned.

  If an IP address is assigned to the network interface, an HTTP server in which a server socket is bound to the assigned IP address is activated (step S72).

  When an IP address is not assigned to the network interface, or after the HTTP server is started, a standby process for detecting a change in the IP address of the network interface to be bound is entered (step S73).

  If the IP address assigned to the network interface is changed, the HTTP server bound to the old IP address cannot be accessed. Therefore, in the fifth embodiment, standby processing for detecting the change of the IP address is performed. As an example of changing the IP address of the network interface, the IP address may change when the network interface acquires an IP address from a DHCP server and acquires the IP address again after the expiration date of the acquired IP address. Hereinafter, a standby process for detecting a change in the IP address will be described.

  Whether or not the IP address has been changed in the network interface is, for example, a method of detecting an event when the IP address is changed using an OS-dependent native program, or a method of periodically checking the IP address of the network interface Can be considered. FIG. 11 is a flowchart showing the flow of processing after detecting a change in the IP address of the network interface. The change of the IP address here includes a case where an IP address is assigned to a network interface to which no IP address is assigned, and a case where an IP address assigned to the network interface becomes invalid.

  First, it is determined whether or not the HTTP server bound to the IP address before change is activated (step S81). If the HTTP server bound to the IP address before the change is activated, the HTTP server is stopped (step S82).

  Subsequently, it is determined whether or not a new IP address is assigned to the network interface (step S83). If a new IP address is assigned, the HTTP server bound to the new IP address is activated (step S84). After starting the HTTP server, set the HTTP server so that the specified content is released for access to the specified alias based on the information about the alias and content registered in the HTTP service corresponding to the HTTP server. To do.

  Then, the process again enters a standby process for detecting the change of the IP address (step S85).

  As described above, by detecting the change of the IP address of the bound network interface and restarting the HTTP server, it becomes possible to continuously publish the content even when the IP address of the network interface is changed. .

  Next, processing performed by the service implementation providing function 11 when the bundle 2 registers content using the HTTP Service will be described. FIG. 12 is a flowchart showing the flow of content registration processing in the fifth embodiment.

  When the bundle 2 issues a request for content registration by calling an HTTP Service method, the service implementation providing function 11 holds information on the alias and the content included in the content registration request (step S91).

  Subsequently, it is determined whether or not the HTTP server corresponding to the HTTP service for which content registration is requested has been started (step S92). If the corresponding HTTP server has been activated, the HTTP server is set so that the specified content is released for access to the specified alias (step S93).

  Note that content that is not open at that time and that has not been released at that time is HTTP that corresponds to the HTTP Service that registered the content by the above-described standby processing that detects a change in the IP address of the network interface to be bound. When the server is started in the future, it is set to be made public for access to the specified alias.

[Sixth Embodiment]
Next, a sixth embodiment will be described. In the sixth embodiment, as in the third and fourth embodiments, the HTTP server is not started until a request for content registration is received. As in the fifth embodiment, the network interface This corresponds to the change of the IP address. Since the registration process of HTTP Service is the same as in the third and fourth embodiments, the description thereof is omitted. Hereinafter, a process for starting the HTTP server at the time of content registration will be described.

  FIG. 13 is a flowchart illustrating a flow of content registration processing performed by the service implementation providing function 11 according to the sixth embodiment.

  When the bundle 2 issues a request for content registration by calling an HTTP Service method, the service implementation providing function 11 holds information on the alias and content included in the content registration request (step S101).

  Subsequently, the service implementation providing function 11 determines whether or not the content has already been registered in the HTTP Service that has been requested to register the content. (Step S102). If the content is not registered, that is, if the number of registered content is 0, the HTTP server has not been activated yet, and the process proceeds to the HTTP server activation process in step S105.

  If the content has already been registered, that is, if the number of registered content is not 0, it is determined whether or not the HTTP server has been started (step S103). If the content has already been registered, the HTTP server activation processing has been completed, but the HTTP server has not yet been activated in a situation where an IP address is not assigned to the network interface.

  If the HTTP server has already been started, the HTTP Service sets the HTTP server in a state where the specified content is released for access to the alias specified by the bundle 2 (step S104).

  On the other hand, when the HTTP server activation process is performed, first, the service implementation providing function 11 acquires the information of the network interface to be bound held by the HTTP Service (step S105). Note that, as in the fourth embodiment, the information management function 16 may be provided, and network interface information may be acquired from the information management function 16.

  Subsequently, the service implementation providing function 11 determines whether an IP address is assigned to the network interface to which the HTTP server to be bound binds (Step S106). If an IP address is not assigned to the network interface, the process proceeds to step S108 and waits for an IP address to be assigned.

  If an IP address is assigned to the network interface, an HTTP server that binds a server socket to the assigned IP address is activated (step S107). When the activation of the HTTP server is completed, the HTTP server is set so that the designated content is released for access to the alias designated by the bundle 2 as in step S104.

  When an IP address is not assigned to the network interface, or after the HTTP server is activated, a standby process for detecting a change in the IP address of the network interface to be bound is entered (step S108).

[Acquisition of http service by bundle]
Next, a bundle for registering content using the HTTP Service will be described. Since the service registration apparatus described above binds to the IP address of a predetermined network interface and starts the HTTP server, the bundle 2 can specify whether or not the contents can be disclosed on a network interface basis. Here, the process in which the bundle 2 acquires a desired HTTP Service will be described.

  FIG. 14 is a block diagram showing a configuration of a bundle for registering content using the HTTP Service. The bundle 2 shown in the figure has a service acquisition function 21, a content registration function 22, a network interface determination function 23, and a search condition creation function 24.

  The network interface determination function 23 determines which network interface the user wants to publish content to, and passes it to the search condition creation function 24. As a method for determining the target network interface, for example, a method of hard-coding in the bundle 2 or a method of setting using a configuration file or system property can be considered, but the method is not limited to this.

  The search condition creation function 24 creates a condition search expression based on the received network interface information so that the value of the service property corresponding to the predetermined key value becomes the specified network interface, and passes it to the service acquisition function 21. .

  The service acquisition function 21 specifies a service name of the HTTP Service and the condition search expression received from the search condition creation function 24 by calling a method of the OSGi specification, for example, a method of the BundleContext interface, and the service registry 14 The HTTP service that matches the condition search expression is acquired from the http service registered in the.

  The content registration function 22 registers the content by calling the HTTP Service method acquired by the service acquisition function 21.

  Next, the flow of processing for acquiring an HTTP service will be described.

  FIG. 15 is a flowchart showing a flow of processing in which the bundle 2 designates a network interface and acquires an Http Service.

  First, the network interface determination function 23 acquires information on the network interface to be disclosed (step S111).

  Subsequently, a condition retrieval formula is created based on the network interface information received by the search condition creation function 24 (step S112). The method for creating the conditional search expression follows the OSGi specification. For example, when the key of a predetermined service property is “BoundNwIfId” and the value corresponding to the designated network interface is “1”, the following character string is generated as a search expression.

"(& (objectClass = org.osgi.service.http.HttpService) (BoundNwIfId = 1))"
Subsequently, the service acquisition function 21 acquires an HTTP Service that matches the condition search expression from the service registry 14 (step S113).

  Then, the content registration function 22 registers the content using the acquired http service (step S114).

  As described above, according to the present embodiment, when the service implementation providing function 11 starts the HTTP server corresponding to the HTTP Service, by binding the IP address of the network interface and starting the HTTP server, Since the HTTP server publishes the content only for access through the bound network interface, the bundle for registering the content using the HTTP Service can perform access control for each network interface.

  Further, according to the present embodiment, it is possible to reduce the consumption of computer resources such as memory consumption by not starting the HTTP server until the content is actually registered using the HTTP Service.

  Further, according to the present embodiment, when the change of the IP address of the network interface bound by the HTTP server is detected, and the change of the IP address is detected, the HTTP server is bound to the new IP address and restarted. Thus, even if the IP address of the network interface is changed, the HTTP server can continuously publish the content via the bound network interface.

DESCRIPTION OF SYMBOLS 1 ... Service registration apparatus 11 ... Service implementation provision function 12 ... Service property creation function 13 ... Service registration function 14 ... Service registry 15 ... Network interface information acquisition function 16 ... Information management function 2 ... Bundle 21 ... Service acquisition function 22 ... Content registration Function 23 ... Network interface determination function 24 ... Search condition creation function 100 ... Service registration device 110 ... Service implementation provision function 120 ... Service property creation function 130 ... Service registration function 140 ... Service registry 200 ... Bundle 210 ... Service acquisition function 220 ... Content Registration function 300 ... HTTP client

Claims (14)

A network interface selection means for selecting a network interface from which a server that publishes content accepts access;
Server activation means for activating the server to accept access addressed to the IP address assigned to the selected network interface;
Service generation means for generating a service for accepting registration of content published by the server;
Property generation means for generating a service property describing the setting of the service and the information of the network interface;
Service registration means for adding the service property to the service and registering it in a service registry;
A service registration device comprising:   The service registration apparatus according to claim 1, wherein the service registration unit registers the service in a service registry without waiting for completion of activation of the server.   2. The service registration apparatus according to claim 1, wherein the server activation unit activates the server when the service accepts content registration. Information management means for storing the correspondence between the service and the network interface information that the server corresponding to the service accepts access to;
4. The service registration apparatus according to claim 3, wherein the server activation unit activates the server so as to read out information on the network interface from the information management unit and accept only access via the network interface.   The server detects a change in an IP address assigned to a network interface that accepts access, and if the IP address assigned to the network interface is changed, the server accepts an access addressed to a new IP address. The service registration device according to claim 1, wherein the service registration device is restarted. A content registration device that acquires a service registered in a service registration device and registers content,
Network interface selection means for selecting a network interface for publishing the content;
Condition retrieval expression creating means for creating a condition retrieval expression for retrieving a desired service from the service registration device based on the information of the selected network interface;
Service acquisition means for acquiring the service from the service registration device using the condition search expression;
Content registration means for registering the content using the acquired service;
A content registration apparatus comprising: Selecting a network interface from which a server that publishes content accepts access;
Activating the server to accept access addressed to an IP address assigned to the selected network interface;
Generating a service for accepting registration of content published by the server;
Generating a service property describing the setting of the service and information of the network interface;
Granting the service property to the service and registering it in a service registry;
A service registration method characterized by comprising:   8. The service registration method according to claim 7, wherein the service is registered in a service registry without waiting for completion of startup of the server.   8. The service registration method according to claim 7, wherein the server is activated when the service accepts content registration.   The server is configured to read out information on the network interface from an information management unit that stores a correspondence between the service and information on a network interface that the server corresponding to the service accepts access to accept only access via the network interface. The service registration method according to claim 9, wherein the service registration method is started. Detecting a change in an IP address assigned to a network interface from which the server accepts access;
If the IP address assigned to the network interface has changed, restarting the server to accept access to the new IP address;
The service registration method according to claim 7, further comprising: A content registration method for acquiring a service registered in a service registration device and registering content,
Selecting a network interface to publish the content;
Creating a condition retrieval formula for retrieving a desired service from the service registration device based on the information of the selected network interface;
Obtaining the service from the service registration device using the condition search expression;
Registering the content using the acquired service;
A content registration method characterized by comprising:   The program for functioning a computer as each means which comprises the service registration apparatus or content registration apparatus in any one of Claims 1 thru | or 6.   A recording medium on which the program according to claim 13 is recorded.

Images