Service discovery protocol server

FIELD OF THE INVENTION

P-0001[0001] The present invention relates to a SDP (Service Discovery Protocol) server. More particularly, the present invention relates to a server for enabling a discovery of a service provided by an apparatus or appliance using one SDP from another appliance using other SDP.

DESCRIPTION OF THE RELATED ART

P-0002[0002] Recently, in order to communicate home appliances with a computer, various SDPs are proposed from many organizations. The SDP automatically collects and manages service information on the appliances, and controls the appliances according to the request of a user. Even if many appliances are used, therefore the user does not need to setup and to manage the respective service information. The appliances are, for example, a PDA (Personal Digital Assistant), a printer, a TA (Terminal Adapter), a CD (Compact Disc) drive, a cellular telephone and a digital camera.

P-0003[0003] The SDP may be, for example, JINI proposed by SUN Microsystems, UPnP proposed by UPnP forum, Salutation proposed by Salutation consortium, Bluetooth SDP profile proposed by Bluetooth SIG, or SLP proposed by IETF.

P-0004[0004] A typical conventional, method for discovering an appliance by SDP will be described hereinafter. At first, the appliance will broadcast a position information indicating its location via a cable or radio network. The position information will be detected by a SDP control unit provided in a computer or in another appliance. The SDP control unit may be, for example, a look-up service on JINI. Then, the SDP control unit will send a response message to the appliance who broadcasted the position information. Thus, the appliance will send back service information containing service attributes to the SDP control unit. As a result, the SDP control unit will be able to register the received service information. Since the SDP control unit operates as a server for providing the service information on SDP, it is possible to discover existing many appliances and to collect the service information provided by the appliances. The service attributes may be, for example, a service name, a description of the service, a version, a maker, and a location for providing service.

P-0005[0005] In another conventional method, the SDP control unit will send an inquiry message by multicasting to appliances on the network. Thus, the SDP control unit will receive a response message from the appliance and it is possible to discover the service information.

P-0006[0006] In a further conventional method, the SDP control unit will send an inquiry message to a service discovery server using the same SDP. Then, the SDP control unit will be able to receive all service information stored in the server

P-0007[0007] However, these SDPs are incompatible with each other. Therefore, there is a problem that an appliance using one SDP cannot discover a service provided by another appliance using different SDP.

SUMMARY OF THE INVENTION

P-0008[0008] It is therefore an object of the present invention to provide a SDP server, whereby an appliance using one SDP can discover a service provided by another appliance using different SDP.

P-0009[0009] According to the present invention, particularly, a SDP server provided by an apparatus using a SDP, from another apparatus using a different SDP has a common database for storing service information on a plurality of SDPs, written in a common format, and a handler unit for handling one of the plurality of SDPs. The handler unit includes a conversion unit for mutually converting service information between a format used in the one SDP handled in this handler unit and the common format.

P-0010[0010] The SDP server according to the present invention can discover a service provided by one apparatus using a SDP, from another apparatus using a different SDP. Thus, the availability of SDP enhances. Furthermore, it can support easily to new SDP only by modifying the common database and the format conversion unit.

P-0011[0011] It is preferred that the service information is defined for each service attribute, and that the conversion unit converts the service information between one service attribute of the handler means and another service attribute of the common database. The one service attribute has the same semantic description as the another service attribute.

P-0012[0012] It is also preferred that the service attribute includes a service name, a vender name, a location and a service discovery protocol handler name.

P-0013[0013] It is preferred that the handler unit includes a service discovery protocol control unit, a communication protocol control unit and a communication unit.

P-0014[0014] Further objects and advantages of the present invention will be apparent from the following description of the preferred embodiments of the invention as illustrated in the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

P-0015[0015]FIG. 1 shows a system configuration with a server for SDP according to the present invention;

P-0016[0016]FIG. 2 shows a functional block diagram of the server in FIG. 1;

P-0017[0017]FIG. 3 shows a mapping table of a common database in the server in FIG. 1;

P-0018[0018] FIG.<b>4</b> shows a block diagram of a more concrete example of the server according to the present invention; and

P-0019[0019]FIG. 5 shows a mapping table of a common database in FIG. 4.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

P-0020[0020]FIG. 1 illustrates a system with a server for SDP according to the present invention. As shown in the figure, the system has the server <b>10</b> and two or more (three in this figure) appliances using different SDPs A, B and C. The server <b>10</b> has a common database <b>11</b> and three SDP handlers <b>12</b> to <b>14</b>.

P-0021[0021]FIG. 2 functionally illustrates configuration of the server <b>10</b>. As will be noted from this figure, the SDP. handlers <b>12</b> to <b>14</b> employ different SDPs A, B and C, respectively. The common database <b>11</b> stores service information for service attributes provided by the SDP handler <b>12</b> to <b>14</b>. The service information stored in the common database <b>11</b> is written in a common format that can be understood by all SDP handlers.

P-0022[0022] Each of the SDP handlers <b>12</b> to <b>14</b> includes a communication unit <b>123</b> or <b>133</b> for communicating through a cable such as Ethernet or through a radio such as Bluetooth, a communication protocol control unit <b>122</b> or <b>132</b> that is a high order layer of the communication unit, a SDP control unit <b>121</b>, <b>131</b> or <b>141</b> for executing the SDP, and a format conversion unit <b>120</b>, <b>130</b> or <b>140</b> for converting a SDP format of the service information into the common format or the common format into the SDP format.

P-0023[0023] The communication unit <b>133</b> and the communication protocol control unit <b>132</b> may be shared by different SDP handlers.

P-0024[0024]FIG. 3 illustrates contents of the service information actually stored in the common database <b>11</b> and relationship of the contents with respect to that in the SDP handlers <b>12</b> and <b>13</b>. The format conversion unit converts the format of the service information into the common format when service attributes of the SDP handler are similar to that of the common database, in other words semantic description of service attributes of the SDP handler are the same as that of the common database, and also the format of the service information for the service attribute in the SDP handler differs from the format of the service information in the common database. The format conversion unit sends the converted service information to the common database <b>10</b>.

P-0025[0025] In case of FIG. 3, the service attributes <b>1</b> and <b>3</b> of the SDP handler A are similar to the service attributes <b>1</b> and <b>3</b> of the common database. Thus, the service information “AA” of the SDP handler is converted into the service information “aa” written in the common format, and this service information “aa” for the service attribute <b>1</b> is stored in the common database <b>11</b>. Likewise, the service information “AAAA” of the SDP handler A is converted into the service information “aaaa” written in the common format, and this service information “aaaa” for the service attribute <b>3</b> is stored in the common database <b>11</b>.

P-0026[0026] When a format of the service information for the service attribute in the SDP handler is the same as the format of the service information in the common database, the format conversion unit does not convert the service information, and the format conversion unit sends the original service information to the common database <b>11</b>.

P-0027[0027] Also, when the service attributes in the SDP handler are not similar to that in the common database <b>11</b>, the format conversion unit does not convert the service information, and the format conversion unit sends the service information with the service attributes written in the original format.

P-0028[0028] In case of FIG. 3, the service attributes <b>2</b> are included only in SDP A, and thus the common database <b>11</b> stores the service information “AAA” with the service attributes <b>2</b> written in the original format.

P-0029[0029] As will be noted from the above-description, the common database <b>11</b> can store different service information discovered by two or more SDP handlers. The stored service information in the common database <b>11</b> may be modified by generation, alteration and/or erasure of the service provided by the appliances. The common database <b>11</b> also stores a service attribute for recoding an identifier of the SDP handler discovered in conjunction with the service information.

P-0030[0030] Each SDP handler operates in its inherent SDP as a server for providing service information. When a SDP handler using one SDP receives an inquiry message of service information from an appliance using a different SDP, a format conversion unit in this SDP handler will convert a service information written in a common format and stored in the common database into a format of the different SDP, and then will send back as a response message the converted service information. Therefore, the inquired appliance will be able to obtain not only the service information discovered by its SDP, but also the service information discovered by other SDP stored in the common database.

P-0031[0031] The inquiry message may include name of service information requested. The format conversion unit will convert the name of service information into the common format, and retrieve or search the common database. Then, the format conversion unit will convert the searched result from the common database into a format in a SDP used in the inquired appliance, and the server will send the converted searched result to the inquired appliance.

P-0032[0032]FIG. 4 functionally illustrates configuration of a more concrete example of a server according to the present invention.

P-0033[0033] In this example, as shown the figure, a PDA <b>45</b> supporting Bluetooth can use a service of a FAX <b>46</b> supporting JINI through the server <b>40</b>. Namely, the server <b>40</b> can communicate with the Bluetooth capable PDA <b>45</b> and the JINI capable FAX. In order to enabling this function, the server <b>40</b> has a common database <b>41</b>, a SDP handler <b>42</b> supporting Bluetooth and a SDP handler <b>43</b> supporting JINI.

P-0034[0034] The Bluetooth SDP handler <b>42</b> has a format conversion unit <b>420</b> according to the present invention, a SDP control unit <b>421</b>, a RFCOM/L2CAP <b>422</b>, and a physical layer <b>423</b> of Bluetooth radio unit, in this sequential order from a high order layer. Furthermore, the JINI SDP handler <b>43</b> has a format conversion unit <b>430</b> according to the present invention, a look-up service control unit <b>431</b>, a transport layer <b>432</b> of RMI (Remote Method Invocation)/TCP/IP, and a physical layer <b>433</b> of Ethernet, in this sequential order from a high order layer.

P-0035[0035]FIG. 5 illustrates contents of the service information actually stored in the common database <b>41</b> and relationship of the contents with respect to that in the SDP handlers <b>42</b> and <b>43</b>.

P-0036[0036] The name item “FAX” of ServiceInfo entry on JINI is recorded at a service attribute “service name” in a mapping table of the common database <b>41</b>. The vender item “xx electric” of ServiceInfo entry on JINI is recorded at a service attribute “vender” in the mapping table. The floor item “2F” of Location entry on JINI is recorded at a service attribute “location” in the mapping table.

P-0037[0037] The Bluetooth SDP handler <b>42</b> has a function as a SDP server using Bluetooth, and receives the service discovery request from the Bluetooth capable PDA <b>45</b>.

P-0038[0038] Then, the Bluetooth SDP handler <b>42</b> will receive service information of FAX recorded by the JINI SDP handler <b>43</b>, from the common database <b>41</b>. Since a format “FAX” of service information specified in Bluetooth SDP differs from a format “0x1111” of service information used in the common database <b>41</b>, the format conversion unit <b>420</b> will convert the format of service information.

P-0039[0039] This conversion of format will be executed as follows, for example:

P-0040[0040] The service attribute “service name” in the mapping table of the common database <b>41</b> is mapped with service Class Id List Attribute of Bluetooth. However, service Class Id List Attribute is UUID of 16-bit. Therefore, the format conversion unit <b>420</b> will convert the character string “FAX” recorded as a service information at the service attribute “service name” in the common database <b>41</b>, to UUID=0x1111 for indicating FAX profile of Bluetooth.

P-0041[0041] The service attribute “vender” in the common database <b>41</b> corresponds to provider Name Attribute of Bluetooth. Since a string type of the service attribute “vender” in the common database is the same as that of the providerNameAttribute of Bluetooth, “xx electric” is inputted in providerNameAttribute in the Bluetooth SDP handler <b>42</b> without conversion.

P-0042[0042] The service attribute “location” in the common database <b>41</b> is not used because the service attributes corresponding to the service attribute “location” does not exist in Bluetooth SDP.

P-0043[0043] The Bluetooth SDP handler <b>42</b> then transmits to the PDA <b>45</b> the converted service information from the format of the common database <b>10</b> as mentioned above. Thus, the PDA only supporting Bluetooth can discover a service of the JINI capable FAX through the server <b>40</b>.

P-0044[0044] Many widely different embodiments of the present invention may be constructed without departing from the spirit and scope of the present invention. It should be understood that the present invention is not limited to the specific embodiments described in the specification, except as defined in the appended claims.