JP4961826B2 - Server apparatus, device association registration method, program, and recording medium - Google Patents

Description

  The present invention relates to a server device that registers and associates each device as a control device and a controlled device in order to allow the first device to access the second device through the network, a device registration method, a program, And a recording medium.

  Examples of a method for accessing a controlled device in the home from a control device on the Internet include a DDNS (Dynamic Domain Name System) method and a mail method.

  In the DDNS system, a controlled device in the home can access this controlled device by registering its own address on the DDNS server and receiving the designation of the domain name and port number from the control device on the Internet side. It is a mechanism.

  There is XMPP (eXtensible Messaging and Presence Protocol) as a protocol for realizing real-time communication (see Non-Patent Document 1). One form of real-time communication using XMPP is instant messaging (IM) (see Non-Patent Document 2). Instant messaging (IM) checks whether an IM client (a friend who can exchange IM) is online on the Internet, and if it is online, chats or exchanges files with that IM client be able to.

Further, as a protocol for calling data and services in other computers, there is SOAP (Simple Object Access Protocol) (see Non-Patent Document 3). In SOAP communication, messages with accompanying information called envelopes are exchanged in XML (eXtensible Markup Language) documents using protocols such as HTTP (Hyper Text Transfer Protocol). Both the client that uses the service and the server that provides the service have SOAP generation / interpretation engines that allow objects to be called between different environments.
"Extensible Messaging and Presence Protocol (XMPP): Core", RFC3920, The Internet Engineering Task Force (IETF), October 2004 "Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence", RFC3921, The Internet Engineering Task Force (IETF), October 2004 "SOAP Version 1.2", W3C Recommendation, World Wide Web Consortium (W3C), June 2003

  In the DDNS method, it is necessary to register a combination of a domain name and a port number in advance in a control device according to an application. In addition, when there are multiple controlled devices in the home, in order to fix the ports that are open to the Internet, the address for the controlled devices in the home and the port forwarding to the ports are controlled, for example It is necessary to set a fixed value for each application corresponding to the device. There is also the problem that this setting takes considerable effort. Furthermore, since the port for which port forwarding is set is always open, it creates a security vulnerability.

  In other words, the DDNS method is effective only in an environment where there is only one device that provides an application such as a Web server that accesses only a single port in the home from a control device.

  In the mail method, the controlled device can easily access the controlled device with the software of the existing mail client, but the controlled device polls the mail server to obtain the mail, so there is a minimum polling interval of several minutes. And real-time property is impaired. In addition, it is necessary to deal with email vulnerabilities such as spam emails.

  In view of such circumstances, the present invention provides a server device, a device registration method, a program, and a recording that can easily register each device in a network system that controls the second device from the first device through the network. The purpose is to provide a medium.

  In order to solve the above-described problem, a server device according to the present invention is a server device that performs a process of registering a first device and a second device connected via a network in association with each other. A first password is generated in response to a password issuance request from the storage device and the first device, and the first password is associated with first identification information related to the first device. The first processing means for storing in the storage means and transmitting the first password to the first device and the second password transmitted from the second device are received, and the received second If the second password is stored in the storage means, the second identification information related to the second device is obtained as the first identification information. Associate with identification information ; And a second processing means for storing in the storage means.

  The server device according to the present invention issues a first password to the first device, and stores the first password in association with the first identification information related to the first device in the storage means. . The first password issued to the first device is held as a second password in the second device transferred from the first device to the second device. The server device receives the second password transmitted from the second device, confirms whether the received second password is stored in the storage means, and stores the second password in the storage means. If there is, the second identification information related to the second device is stored in the storage means in association with the first identification information. Therefore, according to the present invention, the first device gives a password issuance request to the server device, and the second device acquires the first password from the first device and uses this as the second password as the server. By only transmitting to the apparatus, the first device and the second device that is the control target of the first device can be stored in association with each other.

  In the server device of the present invention, the first processing means generates first identification information related to the first device, associates the generated first identification information with the first password, It is good also as memorize | storing in a memory | storage means.

  In the server device of the present invention, the first device is connected to the server device via a service server device that provides a service to the first device, and the first processing means uses the first identification information as the first identification information. You may make it produce | generate the identification information relevant to 1 apparatus and a service server apparatus. In this case, the first processing means generates identification information for the combination of the first device and the service provided by the service server device as the first identification information.

In the server device of the present invention, device authentication processing for authenticating the validity of the second device is executed, and authentication identification information associated with authentication information necessary for authentication of the second device is generated and generated. Means for transmitting authentication identification information to the second device, wherein the second processing means associates the authentication identification information with the first identification information as the second identification information; Store in the storage means.
In the server device of the present invention, the first processing unit sets an expiration date for the generated first password, and the second processing unit checks the expiration date, and the expiration date has expired. If there is, the process of associating the second identification information with the first identification information is not performed.

In the server device of the present invention, the first processing means transmits the generated first password and information on an expiration date set in the first password to the first device.
In the server device according to the present invention, the server device associates a plurality of the second identification information with the first identification information.
In the server device according to the present invention, the server device associates a plurality of the first identification information with the second identification information.

In the server device according to the present invention, the second processing means stores the first password stored in the storage means when storing the second identification information in association with the first identification information. to erase.
In the server device according to the present invention, the second information associated with the first identification information based on the association between the first identification information and the second identification information stored in the storage unit. The information processing apparatus further includes means for generating a list of identification information and transmitting the list to the first device.

  In the server device of the present invention, when a request to the second device is received from the first device, the information related to the first device is the first identification information is the second identification information. Whether the first identification information is stored in association with the second identification information, and an error is transmitted to the first device. .

  In the server device of the present invention, when a request to the second device is received from the first device, the information related to the first device is the first identification information is the second identification information. If the first identification information is stored in association with the second identification information, the first device stores the first identification information in the second device. Send a request from the device.

  According to the present invention, in a network system that controls a second device from a first device through a network, a server device that can easily register each device, a device registration method, a program, and a storage medium are provided. can do.

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

(First embodiment)
FIG. 1 is a diagram showing an overall configuration of a network system according to an embodiment of the present invention.

  This network system includes a mobile phone 10 as a control device, a DVR (Digital Video Recorder) 20 as a controlled device, a service server 30, a direct access management server 40, and a router 50.

  The mobile phone 10 operates as a control device that controls the controlled device. The control device may be anything as long as it controls the controlled device, and may be, for example, a PC (Personal Computer), a PDA (Personal Digital Assistance), or the like.

  In addition to the telephone function unit, the mobile phone 10 includes a main memory that stores programs, a CPU (Central Processing Unit) that executes programs stored in the main memory and performs various arithmetic processes, an interface unit with a network, a DVR 20 Interface unit, a user interface unit such as a key input unit and a display unit, a nonvolatile storage unit 11 and the like. The storage unit 11 stores user identification information registered in the mobile phone 10. In addition to a program for operating the telephone function unit, the main memory stores a program for performing processing related to registration of the device to the service server 30, remote recording reservation of content, content acquisition, and the like.

  In addition to a recording / playback function unit that records and plays back content such as broadcast programs on media, the DVR 20 executes various arithmetic processes by executing a main memory that stores programs and programs stored in the main memory. A CPU, an interface unit with a network, an interface unit with a mobile phone 10, a non-volatile storage unit 21, a remote control receiving unit, an interface unit for connecting a TV and the like are provided. In the storage unit 21, device authentication information fixedly assigned to the controlled device is stored in advance. In the main memory, in addition to a program for controlling the recording / playback function unit of the DVR 20, a program for performing processing related to registration of controlled devices in the direct access management server 40, reservation of remote recording of content, content acquisition, etc. Is remembered. In this embodiment, the DVR 20 is a controlled device, but any device having a network connection function may be used. For example, a television may be used.

  The service server 30 is a server that provides various services for accessing a controlled device via a network to a control device such as the mobile phone 10. The service server 30 includes, for example, an input unit such as a keyboard / mouse, a display unit, a main memory that stores programs, a CPU that executes programs stored in the main memory and performs various arithmetic processes, This is realized using, for example, a typical computer system including a communication unit with a network and a storage unit 31. The main memory stores a basic program necessary for operating the computer system, a program necessary for executing the service, and the like. The storage unit 31 stores a service ID for identifying a service server and a service for each service provided by the service server 30.

  The direct access management server 40 is a server that manages the correspondence between the control device and the service of the service server 30 and the controlled device. The direct access management server 40 includes, for example, an input unit such as a keyboard / mouse, a display unit, a main memory that stores programs, and a CPU that executes various arithmetic processes by executing programs stored in the main memory. For example, a typical computer system including a network interface unit and a storage unit 41 is realized. The main memory stores a basic program necessary for operating the computer system, a program for causing the computer system to function as a direct access management server, and the like.

  The direct access management server 40 includes a SOAP (Simple Object Access Protocol) server 42 and an XMPP (eXtensible Messaging and Presence Protocol) server 43. The SOAP server 42 is a server for performing processing related to registration of a combination of a control device and a service, registration of a controlled device, exchange of information for performing direct access to the service server, and the like. The XMPP server 43 is a server for setting a bidirectional always-on session with the DVR 20 that is a controlled device. Note that the SOAP server and XMPP server are just examples. The SOAP server can be replaced with a server using another API call method, and the XMPP server can be replaced with a server using another IM method. It is.

  Next, the interface of each device will be described. In FIG. 1, [IF-**] indicates an interface number.

  The SOAP server 42 of the direct access management server 40 has an interface [IF-02] accessed from the service server 30 and an interface [IF-00, IF-04] accessed from the DVR 20. The SOAP server 42 also includes a SOAP client function, and accesses the interface [IF-05] on the service server 30 side. The interface of the XMPP server 43 is accessed from an XMPP client when establishing an XMPP session. In this system configuration example, the interface [IF-06] accessed from the DVR 20 corresponds to this, and after the XMPP session is established, messages can be exchanged bidirectionally using this interface [IF-06]. Can also access the interface [IF-07] of DVR20. The direct access management server 40 also has a direct access URI (Uniform Resource Identifier) interface [IF-10] provided to the service server 30 during XMPP tunneling described later.

  The service server 30 has an interface [IF-01] accessed from the mobile phone 10 and an interface [IF-05] accessed from the direct access management server 40.

  In this system configuration example, the service server 30 is not directly interfaced with the XMPP server 43 of the direct access management server 40, but may of course be configured to interface directly.

  The DVR 20 is an interface for transmitting and receiving data between the interface [IF-07] after the XMPP session established accessed from the direct access management server 40 and the mobile phone 10 using, for example, infrared or USB (Universal Serial Bus). [IF-03] and an interface [IF-09] corresponding to the direct access URI accessed from the service server 30 or the mobile phone 10.

  The router 50 has a UPnP (Universal Plug and Play) IGD (Internet Gateway Device) function interface [IF-08] accessed from the DVR 20.

  Next, the operation of the network system of this embodiment will be described. In the following description, <X-XX> indicates a request, and <X-XXR> indicates a response to <X-XX>.

  [1. Registration of controlled devices / services and controlled devices]

  First, a control device / service management ID issued for each combination of the mobile phone 10 (control device) and service, and a unique issuance for each DVR 20 (controlled device) within the direct access management server 40 The operation for associating with the controlled device management ID will be described.

  FIG. 2 is a sequence diagram showing the flow of information when registering the combination of the mobile phone 10 and the service and registering the DVR 20. FIG. 3 is a flowchart of the cellular phone 10 at the time of registration. FIG. 4 is a flowchart of the service server 30 at the time of registration. FIG. 5 is a flowchart of the direct access management server 40 at the time of registration. FIG. 6 is a flowchart of the DVR 20 at the time of registration.

  [1-1. Registration of combination of control device and service]

  First, the mobile phone 10 receives a controlled device registration instruction from the user (FIG. 3: step S301), and issues a controlled device registration request <R-1> including user identification information to the service server 30 (FIG. 3: Step S302).

  When the service server 30 receives the controlled device registration request <R-1> including the user identification information (FIG. 4: step S401), the control device / service management ID corresponding to the user identification information is stored in the storage unit 31. It is determined whether it has been performed (FIG. 4: Step S402).

  When the control device / service management ID corresponding to the user identification information is not stored, the service server 30 stores the user identification information in the storage unit 31 (FIG. 4: step S403), and the Service ID assigned to itself in advance. Is issued to the SOAP server 42 in the direct access management server 40 (FIG. 4: step S404). The control device / service management ID is an ID uniquely assigned to a combination of an individual service provided by a service provider and a control device.

  When the SOAP server 42 receives the control device / service management ID acquisition request <R-2> (FIG. 5: step S501), the Service ID included in this is registered in advance in the storage unit 41 of the direct access management server 40. If it does not match (Figure 5: Step S502), if it does not match, an error code indicating that the ServiceID has not been registered in the service server 30 is sent to the control device / service management ID acquisition response < R-2R> is transmitted (FIG. 5: Step S506). If the Service IDs match, the SOAP server 42 issues a new control device / service management ID (FIG. 5: Step S503), and stores the correspondence between the control device / service management ID and Service ID in the storage unit 41. (FIG. 5: Step S504), and transmits the control device / service management ID to the service server 30 as a control device / service management ID acquisition response <R-2R> (FIG. 5: Step S505). Thereby, the direct access management server 40 can identify the control side as seen from the direct access management server 40 by combining the mobile phone 10 that is the control device and the service of the service server 30 used by the mobile phone 10. It becomes like this.

  Upon receiving the control device / service management ID as the control device / service management ID acquisition response <R-2R> (FIG. 4: step S405), the service server 30 associates the control device / service management ID with the user identification information. To the storage unit 31 (FIG. 4: step S406). By storing the control device / service management ID in association with the user identification information, the service server 30 subsequently controls the device / service corresponding to the user identification information of the mobile phone 10 when accessed from the mobile phone 10. By using the management ID to request processing from the direct access management server 40, the control request source is sent to the direct access management server 40 as the control side of the combination of the mobile phone 10 that is the control device and the service of the service server 30. It is possible to uniquely identify them.

  The service server 30 associates the control device / service management ID with the user identification information in the storage unit 31, or the user identification included in the controlled device registration request <R-1> received from the mobile phone 10 If the control device / service management ID corresponding to the information is registered in the storage unit 31, the controlled device registration password acquisition request <R-3> including the control device / service management ID and Service ID is sent to the direct access management server. It is issued to the SOAP server 42 within 40 (FIG. 4: Step S407).

  When the SOAP server 42 in the direct access management server 40 receives the controlled device registration password acquisition request <R-3> (FIG. 5: Step S507), the control device / service management ID and ServiceID included in this request are received. It is determined whether or not the combination is registered in the storage unit 41 (FIG. 5: step S508). If not registered, the SOAP server 42 sets an error code indicating that the combination of the control device / service management ID and ServiceID is not registered in the service server 30 as the controlled device registration password acquisition response <R-3R>. Transmit (FIG. 5: Step S512). If the combination of the control device / service management ID and Service ID included in the controlled device registration password acquisition request <R-3> is already registered in the storage unit 41, the SOAP server 42 A new registration password is generated (Fig. 5: Step S509), and the controlled device registration password acquisition request is issued for the controlled device registration password and information regarding the expiration date determined for the controlled device registration password. The control device / service management ID and Service ID included in <R-3> are associated with each other and registered in the storage unit 41 (FIG. 5: step S510). Thereafter, the SOAP server 42 transmits the controlled device registration password and the expiration date information of the controlled device registration password to the service server 30 as a controlled device registration password acquisition response <R-3R> ( FIG. 5: Step S511).

  Upon receiving the controlled device registration password acquisition response <R-3R> (FIG. 4: step S408), the service server 30 receives the controlled device registration password acquisition response <R-3R>. The device registration password and its expiration date information are transmitted to the mobile phone 10 as a controlled device registration response <R-4> (FIG. 4: step S409).

  When receiving the controlled device registration response <R-4> (FIG. 3: step S303), the mobile phone 10 stores the controlled device registration password and the expiration date information included in the response to the storage unit 11. Save (FIG. 3: Step S304).

  Thus, the control device / service management ID registration process for the combination of the mobile phone 10 and the service and the controlled device registration password issuance process used to associate the controlled device with the controlled device are completed.

   [1-2. Registration of controlled device]

  Next, the operation at the time of registration of the controlled device DVR 20 will be described.

  The DVR 20 performs its own device authentication in the direct access management server 40 before use by the user as follows.

  First, the DVR 20 checks the value of the automatic connection flag (FIG. 6: step S601). Before the controlled device is registered in the direct access management server 40, the value of the automatic connection flag is off. In this case, the DVR 20 transmits a device authentication request <R-0> including the authentication method information set in advance and device authentication information to the SOAP server 42 in the direct access management server 40 (FIG. 6: Step S602). .

  When the SOAP server 42 in the direct access management server 40 receives the device authentication request <R-0> from the DVR 20 (FIG. 5: Step S513), it determines whether or not this DVR 20 is a valid device < Determination is made based on the authentication method information and device authentication information included in R-0> (FIG. 5: step S514). When it is determined as an unauthorized device, that is, when the authentication method is different from a predetermined authentication method or when the device authentication information is different from the predetermined authentication method format, the SOAP server 42 An error code indicating that the device authentication has failed is transmitted to the DVR 20 as a device authentication response <R-0R> (FIG. 5: Step S515). If it is determined that the device is a legitimate device, that is, if the authentication method matches the predetermined authentication method and the device authentication information is in the predetermined authentication method format, the SOAP server 42 generates a device authentication continuation ID to be assigned to the DVR 20 (FIG. 5: step S516), and associates this device authentication continuation ID with the device authentication information included in the device authentication request <R-0>. To the storage unit 41 (FIG. 5: step S517). Thereafter, the SOAP server 42 transmits a device authentication response <R-0R> including the generated device authentication continuation ID and information on its expiration date to the DVR 20 (FIG. 5: step S518). The device authentication continuation ID is identification information assigned to a device for which device authentication has been completed by the direct access management server 40. By this identification information, the direct access management server 40 uses the device of the DVR 20 that is the controlled device. It is possible to confirm the authentication status of

  When the DVR 20 receives a device authentication response <R-0R> including the device authentication continuation ID and information on its expiration date from the SOAP server 42 in the direct access management server 40 (FIG. 6: Step S603), this device authentication The device authentication continuation ID and the expiration date information included in the response <R-0R> are stored in the storage unit 21 in association with the device authentication information (FIG. 6: step S604).

  Thereafter, the DVR 20 determines whether the controlled device registration password is stored in the storage unit 21 (FIG. 6: step S605). If the controlled device registration password is not stored, the operation is terminated, and if the controlled device registration password is stored, the process proceeds to step S609. Immediately after acquiring the device authentication continuation ID, the controlled device registration password is not saved, and in this case, the operation is terminated. Up to this point, the DVR 20 that is the controlled device stores the device authentication continuation ID, the expiration date information of the device authentication continuation ID, and the combination of the device authentication information in the storage unit 21, and the direct access management server 40 has the device authentication continuation ID and A combination with the device authentication information is stored in the storage unit 41.

  [1-3. Linking Control Device / Service Management ID and Controlled Device Management ID]

  Next, the control device / service management ID and the controlled device management ID are associated with each other and registered in the direct access management server 40. In the mobile phone 10, a one-time password transmission request from the user is input (FIG. 3: step S305). When the mobile phone 10 receives a one-time password transmission request from the user, the controlled device registration password stored in the storage unit 11, for example, using an interface [IF-03] such as infrared or USB, A one-time password <R-5> is passed to the DVR 20 that is the controlled device (FIG. 3: step S306). There are various other ways to pass the password for registering the controlled device, such as passing through a non-contact IC card, wireless transmission using Bluetooth (trademark), wireless LAN, etc. As long as the controlled device registration password can be passed from the telephone 10 to the DVR 20 that is the controlled device, any method may be used. Thereafter, the mobile phone 10 deletes the controlled device registration password from the storage unit 11 (FIG. 3: step S307).

  Upon receiving the controlled device registration password <R-5> from the mobile phone 10 (FIG. 6: Step S607), the DVR 20 stores the controlled device registration password in the storage unit 21 (FIG. 6: Step S608). . Subsequently, the DVR 20 sends the controlled device registration request <R-6> including the device authentication continuation ID stored in the storage unit 21 and the controlled device registration password received from the mobile phone 10 to the direct access management server 40. To the SOAP server 42 (FIG. 6: step S609). As a result, the DVR 20 requests the direct access management server 40 to register in association with the mobile phone 10 that has transmitted the controlled device registration password.

  When the SOAP server 42 in the direct access management server 40 receives the controlled device registration request <R-6> from the DVR 20 (FIG. 5: step S519), the devices included in the controlled device registration request <R-6> A check is made to see if the authentication continuation ID matches that stored in the storage unit 41 and the validity period of the device authentication continuation ID is checked (FIG. 5: step S520). If NG is determined by these checks, that is, if the device authentication continuation ID does not match or the device authentication continuation ID has expired, an error code indicating that device authentication is required is included A controlled device registration response <R-6R> is transmitted to the DVR 20 (FIG. 5: step S528). Upon receiving the controlled device registration response <R-6R> including this error code (FIG. 6: step S622), the DVR 20 returns to step S602 and repeats the device authentication process.

  Further, if the check result in step S520 is OK, that is, the SOAP server 42 matches the device authentication continuation ID stored in the storage unit 41, and the device authentication continuation ID has not expired, Check whether the controlled device registration password included in the controlled device registration request <R-6> received from the DVR 20 matches the one stored in the storage unit 41 and the validity of the controlled device registration password The deadline is checked (FIG. 5: step S521). If NG is determined by these checks, that is, the controlled device registration password does not match or the controlled device registration password has expired, the SOAP server 42 sends a controlled device registration request < An error code indicating that the controlled device registration password included in R-6> is invalid is transmitted to the DVR 20 as a controlled device registration response <R-6R> (FIG. 5: step S527). When the DVR 20 receives this error code as a controlled device registration response <R-6R> (FIG. 6: step S620), the DVR 20 re-acquires the controlled device registration password through the TV screen connected to the DVR 20 or the like. As described above, an error message is displayed to the user (FIG. 6: step S621), and the process is terminated.

  In addition, the SOAP server 42 determines that the check result in step S521 is OK, that is, the controlled device registration password matches that stored in the storage unit 41, and the controlled device registration password has expired. If not, whether the controlled device management ID is assigned to the device authentication continuation ID included in the controlled device registration request <R-6> with reference to the information stored in the storage unit 41 Judgment is made (FIG. 5: step S521-1). If the controlled device management ID corresponding to the device authentication continuation ID is not yet allocated, the SOAP server 42 allocates the controlled device management ID to the DVR 20 (FIG. 5: step S522), and this allocated controlled device The device management ID is stored in the storage unit 41 in association with the device authentication information and device authentication continuation ID of the DVR 20 (FIG. 5: step S523). If the controlled device management ID is already assigned to the device authentication continuation ID included in the controlled device registration request <R-6>, the SOAP server 42 stores the controlled device management ID in the storage unit 41. The control device / service management ID stored in association with the controlled device registration password is stored in the storage unit 41 (FIG. 5: step S523-1). Here, the controlled device management ID is identification information uniquely assigned to the controlled device in the direct access management server 40. As a result, the control device / service management ID assigned to the combination of the control device and the service is associated with the controlled device management ID assigned to the controlled device. In this connection, even if multiple controlled device management IDs are linked to one controlled device / service management ID, multiple controlled devices / service management IDs are linked to one controlled device management ID. It may be attached.

  Next, the SOAP server 42 transmits the number of services that are currently associated to the DVR 20 as a controlled device registration response <R-6R> (FIG. 5: step S524). Next, the SOAP server 42 sends a controlled device registration completion notification <R-7> including the ServiceID, control device / service management ID, and controlled device registration password stored in the storage unit 41 to the service server 30. (FIG. 5: Step S525). Thereafter, the SOAP server 42 deletes the controlled device registration password in the storage unit 41 (FIG. 5: step S526), and ends the process. When the service server 30 receives the controlled device registration completion notification <R-7> from the SOAP server 42 (FIG. 4: step S410), the service server 30 notifies the mobile phone 10 that the controlled device registration is completed ( FIG. 4: Step S411). Examples of a method for notifying the cellular phone 10 from the service server 30 that registration of the controlled device has been completed include, for example, e-mail and applications prepared for communicating with the cellular phone 10 by other methods. Etc.

  When the DVR 20 receives from the SOAP server 42 the number of services that are currently associated as a controlled device registration response <R-6R> (Fig. 6: step S610), it sets the automatic connection flag to on (Fig. 6: Step S611), a message indicating that registration of the controlled device is completed is displayed (FIG. 6: Step S612). Subsequently, the DVR 20 deletes the controlled device registration password stored in the storage unit 21 (FIG. 6: step S613). After that, the DVR 20 sends an XMPP login information acquisition request <D-0-1> including the device authentication continuation ID to the direct access management server 40 in order to establish a constant connection session with the XMPP server 43 of the direct access management server 40. The information is transmitted to the SOAP server 42 within 40 (FIG. 6: step S614).

  [2.XMPP login of controlled device]

  In this network system, the direct access management server 40 is provided with an XMPP server 43 for setting a bidirectional always-connected session with a controlled device. In order to access the DVR 20 that is the controlled device through the network from the mobile phone 10 that is the controlling device, the DVR 20 logs into the XMPP server 43 and establishes a constant connection session between the XMPP servers 43 before that. Thereby, the service server 30 and the mobile phone 10 can acquire necessary information from the DVR 20 when necessary. In order to simplify the design of the service server 30 at this time, the XMPP server that conceals the XMPP protocol in the direct access management server 40 and sets a bidirectional always-on session with the DVR 20 using only the SOAP interface. It is possible to exchange information with 43.

  7 is a sequence diagram showing a flow of information related to the XMPP login of the controlled device, and FIG. 10 is a flowchart showing an operation of the direct access management server 40 related to the XMPP login of the controlled device.

  As shown in these figures, when the direct access management server 40 receives the XMPP login information acquisition request <D-0-1> including the device authentication continuation ID from the DVR 20 (FIG. 10: step S1001), this XMPP login The device authentication continuation ID included in the information acquisition request <D-0-1> and the expiration date of the device authentication continuation ID are checked (FIG. 10: Step S1002). If this check does not match the device authentication continuation ID included in the XMPP login information acquisition request <D-0-1> with that stored in the storage unit 41 of the direct access management server 40, or the expiration date If it is expired, it means that the DVR 20 is not properly registered in the direct access management server 40, or it has been registered in the past, but the device authentication continuation ID at the time of registration has expired Therefore, an error code indicating that device authentication is required is transmitted to the DVR 20 as an XMPP login information acquisition response <D-0-1R> (FIG. 10: step S1003). When the device authentication continuation ID is stored in the storage unit 41 and the device authentication continuation ID has not expired, the direct access management server 40 is associated with the device authentication continuation ID from the storage unit 41. Is the XMPP login ID required for the DVR 20 to log in to the XMPP server 43 based on the controlled device management ID and device authentication information (see FIG. 10: Step S1004). Full JID (D), XMPP login password, and expiration date information of the XMPP login password are generated (FIG. 10: step S1005) and stored in the storage unit 41 (FIG. 10: step S1006). The direct access management server 40 adds the XMPP address and port number, authentication method information, and SSL (Secure Socket Layer) option to the generated Full JID (D), XMPP login password, and expiration date information. Is transmitted to the DVR 20 as an XMPP login information acquisition response <D-0-1R> (FIG. 10: step S1007).

  When the DVR 20 receives the XMPP login information acquisition response <D-0-1R> including the Full JID (D), the XMPP login password, etc. from the SOAP server 42 in the direct access management server 40 (FIG. 6: Step S615), the Full An XMPP login authentication request <D-0-2> including JID (D) and XMPP login password is transmitted to the XMPP server 43 in the direct access management server 40 (FIG. 6: step S616).

  When the XMPP server 43 in the direct access management server 40 receives the XMPP login authentication request <D-0-2> from the DVR 20 (FIG. 10: Step S1008), it is included in this XMPP login authentication request <D-0-2>. The full JID (D), XMPP login password and XMPP login password expiration date are checked (Fig. 10: Step S1009), and the Full JID (D) does not match the one stored in the storage unit 41. Or, if the XMPP login password does not match that stored in the storage unit 41, or if the XMPP login password has expired, an error code indicating XMPP login failure is displayed as the XMPP login authentication response <D- 0-1R> is transmitted to the DVR 20 (FIG. 10: Step S1010). Full JID (D). If the XMPP login password and the expiration date check are all OK, the XMPP server 43 in the direct access management server 40 transmits a code indicating XMPP login permission to the DVR 20 as an XMPP login authentication response <D-0-2R> ( FIG. 10: Step S1011).

  When the DVR 20 receives an error code indicating failure of XMPP login from the direct access management server 40 as the XMPP login authentication response <D-0-2R> (FIG. 6: step S619), the DVR 20 returns to step S614 and again returns the XMPP login information. Make an acquisition request. That is, since the XMPP login password may expire, XMPP login information acquisition request processing is performed again. Further, when the code indicating XMPP login permission is received from the direct access management server 40 as the XMPP login authentication response <D-0-2R> (FIG. 6: step S618), the DVR 20 completes the XMPP login process.

  The DVR 20 receives an error code indicating that device authentication is required from the SOAP server 42 in the direct access management server 40 as an XMPP login information acquisition response <D-0-1R> (FIG. 6). : Step S617) Since the device itself is not normally registered in the direct access management server 40 or the device authentication continuation ID may have expired, it is set in advance again. The device authentication request <R-0> including the authentication method information and device authentication information is transmitted to the SOAP server 42 in the direct access management server 40, and the device authentication is performed again (FIG. 6: step S602).

  As described above, in this network system, the direct access management server 40 generates an XMPP login ID (Full JID (D)) and an XMPP login password necessary for the DVR 20 to log in to the XMPP server 43, and the DVR 20 It is distributed to. This Full JID (D) is composed of a Bare JID part and a Resource part, for example, as shown in FIG. A controlled device management ID assigned to the controlled device is used for the Bare JID portion, and a product code and a serial number obtained from the device authentication information are used for the Resource portion. Further, as shown in FIG. 25, a control device / service management ID for identifying a combination of a control device and a service may be used in the Resource portion.

  By the way, when the automatic connection flag is set to ON in step S611, the DVR 20 is connected at the next connection, for example, when the power of the DVR 20 is once turned off and then turned on again, or after the session with the XMPP server 43 is disconnected. When the session is re-established, after the automatic connection flag is checked in step S601, the process starts from transmission of the XMPP login information acquisition request <D-0-1> in step S614. That is, the DVR 20 skips processing for device authentication, acquisition of a controlled device registration password from the mobile phone 10 and processing for controlled device registration when reconnecting, and enters processing for XMPP login. As a result, the DVR 20 can establish a connection session between the XMPP servers 43 simply by performing processing for XMPP login at the time of reconnection.

  This completes the process for associating the DVR 20 that is the controlled device as the control target of the mobile phone 10 that is the controlling device. Hereinafter, specific processing when the mobile phone 10 controls the DVR 20 between two associated devices will be described.

  [3. Remote recording reservation]

  The operation of remote recording reservation to the DVR 20 will be described.

  7 is a sequence diagram showing the flow of information at the time of remote recording reservation, FIG. 8 is a flowchart showing the operation of the mobile phone 10 related to remote recording reservation, and FIG. 9 is a flowchart showing the operation of the service server 30 related to remote recording reservation. FIGS. 10 and 11 are flowcharts showing the operation of the direct access management server 40 related to remote recording reservation and content acquisition, and FIG. 12 is a flowchart showing the operation of the DVR 20 related to remote recording reservation and content acquisition.

  When an instruction to start using direct access is given to the mobile phone 10 in order to receive the remote recording reservation service from the user of the mobile phone 10 (FIG. 8: Step S801), the mobile phone 10 is preset in itself. A controlled device list acquisition request <D-1> including user identification information is transmitted to the service server 30 (FIG. 8: step S802).

  When the service server 30 receives the controlled device list acquisition request <D-1> from the mobile phone 10 (FIG. 9: Step S901), the service server 30 includes the user identification information included in the controlled device list acquisition request <D-1>. It is determined whether or not the corresponding control device / service management ID is stored in the storage unit 31 (FIG. 9: Step S902). If the control device / service management ID corresponding to the user identification information is not stored in the storage unit 31, the service server 30 sends an error code indicating that the controlled device needs to be registered to the controlled device list acquisition response < D-3> is transmitted to the mobile phone 10 (FIG. 9: Step S903). When the control device / service management ID corresponding to the user identification information is stored in the storage unit 31, a list of controlled devices associated with the control device / service management ID managed by the direct access management server 40 The service server 30 transmits a controlled device list acquisition request <D-2> including a Service ID that is information for identifying a service and a control device / service management ID to the direct access management server 40 (see FIG. 9: Step S904).

  When the direct access management server 40 receives the controlled device list acquisition request <D-2> from the service server 30 (FIG. 10: step S1012), the ServiceID included in the controlled device list acquisition request <D-2> Then, it is determined whether or not the combination of the control device / service management ID is stored in the storage unit 41 (FIG. 10: Step S1013), and if it is not stored, an error code indicating that it has not been registered is received. A control device list acquisition response <D-2R> is transmitted to the service server 30 (FIG. 10: step S1014). If the service server 30 receives an unregistered error code from the direct access management server 40 as a controlled device list acquisition response <D-2R> (FIG. 9: Step S905), the controlled device registration Is transmitted to the mobile phone 10 as a controlled device list acquisition response <D-3> (FIG. 9: step S906). When the mobile phone 10 receives the error code from the service server 30 as a controlled device list acquisition response <D-3> (FIG. 8: step S803), it indicates that registration of the controlled device to be serviced is necessary. An error message is displayed to the user through the display unit (FIG. 8: Step S804).

  If it is determined in step S1013 that the combination of ServiceID and control device / service management ID included in the controlled device list acquisition request <D-2> is stored in the storage unit 41, direct access is performed. The management server 40 controls the controlled device management ID of the controlled device that can be controlled from the mobile phone 10 according to the contents of the control device / service management ID stored in the storage unit 41 and the controlled device management ID. A list composed of the re-assigned number and the device name included in the device authentication information of the controlled device is generated as a controlled device list, and this controlled device list is associated with the control device / service management ID to store At the same time, the controlled device list acquisition response <D-2R> including this controlled device list is transmitted to the service server 30 (FIG. 10: step S1015). When the service server 30 receives the controlled device list acquisition response <D-2R> including the controlled device list from the direct access management server 40 (FIG. 9: step S907), the controlled device including this controlled device list Device list acquisition response <D-3> is transmitted to mobile phone 10 (FIG. 9: step S908).

  When the mobile phone 10 receives the controlled device list acquisition response <D-3> including the controlled device list (FIG. 8: step S805), there are multiple controlled device numbers in the controlled device list. It is determined whether or not to perform (FIG. 8: step S806). When there are a plurality of controlled device numbers, the mobile phone 10 displays the contents of the controlled device list on the display unit (FIG. 8: step S807), and the user controls one controlled device from the list. The device number is selected (FIG. 8: step S808), and the selected controlled device number is stored in the storage unit 11 (FIG. 8: steps S809 and S811). If a plurality of controlled devices do not exist, the number of the one controlled device is stored in the storage unit 11 (FIG. 8: steps S810 and S811).

  Next, the mobile phone 10 branches the process depending on whether the service to be used (remote recording reservation) is a service that allows direct access from the mobile phone 10 to the controlled device (FIG. 8: step S812). When using a service that can be directly accessed from the mobile phone 10, the mobile phone 10 uses the new remote recording reservation including the user identification information stored in the storage unit 11, the number of the controlled device, and the mobile direct flag (ON). The request <D-4> is transmitted to the service server 30 (FIG. 8: Step S813). Here, the value of the mobile direct flag is set to ON when using a service that can be directly accessed from the mobile phone 10, and set to OFF when using a service that cannot be directly accessed from the mobile phone 10. The Therefore, when using a service that cannot be directly accessed from the mobile phone 10, the mobile phone 10 uses the new remote recording reservation request including the user identification information, the recording reservation program information, the number of the controlled device, and the mobile direct flag (off). <D-4> is transmitted to the service server 30 (FIG. 8: step S814). The scheduled recording program information includes, for example, information such as a recording start time, a program length, a broadcast type, a channel, and a forced reservation flag.

  When the service server 30 receives the new remote recording reservation request <D-4> from the mobile phone 10 (FIG. 9: Step S909), it is included in the available XMPP session ID, that is, the new remote recording reservation request <D-4> Whether or not an ID for identifying a connection session established with the XMPP server 43 associated with the user identification information of the mobile phone 10 is stored in the storage unit 31 (FIG. 9: step S910). If an available XMPP session ID is not stored, the service server 30 establishes an XMPP session with the XMPP server 43, and includes an XMPP login that includes the ServiceID, control device / service management ID, and controlled device number. The request <D-5> is transmitted to the direct access management server 40 (FIG. 9: Step S912).

  When the direct access management server 40 receives the XMPP login request <D-5> from the service server 30 (FIG. 10: Step S1016), the Service ID, control device / service management included in the XMPP login request <D-5> It is determined whether the combination of the ID and the number of the controlled device is stored in the storage unit 41 (FIG. 10: Step S1017). If not stored, the direct access management server 40 sends an error code indicating that the corresponding controlled device to be serviced does not exist as an XMPP login response <D-5R> to the service server 30 (FIG. 10: Step S1018). Thereafter, the operation of the direct access management server 40 ends. When the corresponding controlled device to be serviced is stored in the storage unit 41, the direct access management server 40 generates an XMPP session ID, and this XMPP session ID is ServiceID, control device / service management ID, controlled device. The XMPP login response <D-5R> including this XMPP session ID is transmitted to the service server 30 (FIG. 10: step S1020).

  When the service server 30 receives the XMPP login response <D-5R> including the XMPP session ID from the direct access management server 40 (FIG. 9: Step S913), the XMPP session ID included in the XMPP login response <D-5R> Then, the value of the portable direct flag included in the new remote recording reservation request <D-4> in step S909 is stored in the storage unit 31 in association with the Service ID, the control device / service management ID, and the controlled device list number (FIG. 9: Step S914).

  On the other hand, as a result of the determination in step S910 by the service server 30, if an available XMPP session ID has already been stored in the storage unit 31, the service server 30 includes the mobile phone included in the new remote recording reservation request <D-4>. The value of the direct flag is stored in the storage unit 31 in association with the Service ID, the control device / service management ID, and the controlled device number (FIG. 9: Step S911).

  After storing the mobile direct flag in step S911 or step S914, the service server 30 sends a direct access start request <D-6> including ServiceID, control device / service management ID, service URN (Uniform Resource Name), and XMPP session ID. The data is transmitted to the direct access management server 40 (FIG. 9: Step S915). Here, the service URN is information specifying one of services (applications) that can be provided by the controlled device. Here, since the mobile phone 10 is going to make a remote recording reservation for the DVR 20, the service URN is information for designating the remote recording reservation service.

  Upon receiving the direct access start request <D-6> from the service server 30 (FIG. 11: Step S1101), the direct access management server 40 controls the ServiceID included in this direct access start request <D-6>. It is determined whether the combination of device / service management ID is stored in the storage unit 41 (FIG. 11: Step S1102), and if it is not stored, an error code indicating that registration of the controlled device is required is directly performed. The access start response <D-10> is transmitted to the service server 30 (FIG. 11: Step S1103). When the combination of ServiceID and control device / service management ID included in the direct access start request <D-6> is stored in the storage unit 41, the direct access management server 40 sends the direct access start request <D XMPP session ID included in -6> is stored in the storage unit 41 in association with the combination of Service ID and control device / service management ID included in the direct access start request <D-6>. It is determined whether or not (FIG. 11: step S1104). If not stored, the direct access management server 40 transmits an error code indicating an unauthorized XMPP session ID as a direct access start response <D-10> to the service server 30 (FIG. 11: step S1105). When the service server 30 receives an error code indicating an illegal XMPP session ID from the direct access management server 40 as a direct access start response <D-10> (FIG. 9: step S916), the service server 30 returns to step S912 and returns to XMPP. The login request <D-5> is transmitted to the direct access management server 40, and the XMPP session is established again.

  In step S1104, the XMPP session ID included in the direct access start request <D-6> is combined with the Service ID and control device / service management ID included in the direct access start request <D-6>. When stored in the storage unit 41 in association with each other, the direct access management server 40 includes designation information of the service URN that is information for identifying the service designated by the direct access start request <D-6>. The direct access URI acquisition request <D-7> is transmitted to the controlled device DVR 20 through the always-on session established between the XMPP server 43 and the DVR 20 (FIG. 11: step S1106).

  Upon receiving the direct access URI acquisition request <D-7> including the service URN designation information from the direct access management server 40 (FIG. 12: step S1201), the DVR 20 assigns a local port for direct access ( FIG. 12: Step S1202). Next, the DVR 20 sends a direct access port NAT (Network Address Translation) setting request <D-8> to the router 50, including the local IP address pre-assigned to the DVR 20 and the port number of the local port for direct access. The router 50 is requested to map the global IP address and port number accessible from the Internet to the local IP address and port number (FIG. 12: step S1203). For example, in order to assign a direct access URI, the DVR 20 accesses the router 50 by UPnP IGD DCP (Device Control Protocol) or the like, and reserves a global IP address and a port number accessible from the Internet in advance.

  In response to the NAT setting request <D-8> for the direct access port in step S1203, the DVR 20 sends a NAT setting response from the router 50 with the global IP address and port number associated with the local IP address and port number of the DVR 20. If it is received as <D-8R> (Figure 12: Step S1208), a direct access URI list is created using these global IP addresses and port numbers, and this direct access URI list is used as the direct access URI. An acquisition response <D-9> is transmitted to the direct access management server 40 (FIG. 12: step S1209). The direct access URI list is a list of URIs for directly accessing the device from the service server 30 or the mobile phone 10 through the network.

  When the XMPP server 43 of the direct access management server 40 receives the direct access URI list as a direct access URI acquisition response <D-9> (FIG. 11: step S1107), the direct access URI list is sent as a direct access start response. It is transmitted to the service server 30 as <D-10> (FIG. 11: Step S1111).

  The DVR 20 receives the global IP address and port number acquisition error from the router 50 as a direct access port NAT setting response <D-8R> (FIG. 12: step S1204), and acquires it in step S1201. Based on the designated information of the service URN, it is determined whether or not the service URN can be tunneled (FIG. 12: step S1205). Here, a specific service among the provided services is determined in advance as a tunnelable service. For example, a service with a relatively small amount of data to be communicated such as remote recording is determined as a tunnelable service, and a service with a relatively large amount of data to be communicated such as a content acquisition service is a service that cannot be tunneled. It has been decided. Therefore, if the DVR 20 determines that the specified service URN information included in the direct access URI acquisition request <D-7> is a new remote recording reservation, the DVR 20 directly accesses the error code instructing tunneling. A URI acquisition response <D-9> is transmitted to the direct access management server 40 (FIG. 12: step S1206). The tunneling instruction is performed by, for example, filling all address parts of the direct access URI with “0”.

  When the XMPP server 43 of the direct access management server 40 receives an error code instructing tunneling as a direct access URI acquisition response <D-9> (FIG. 11: step S1109), the XMPP server 43 in the direct access management server 40 Assign a tunneling port (Figure 11: Step S1110), and create a direct access URI list using the assigned port number of the tunneling port in the direct access management server 40 and the global IP address of the direct access management server 40. Then, a direct access start response <D-10> including this direct access URI list is transmitted to the service server 30 (FIG. 11: step S1111). As a result, the service server 30 and the mobile phone 10 can access the DVR 20 without being conscious of being tunneled.

  If it is determined in step S1205 that the service URN specified information included in the direct access URI acquisition request <D-7> is a non-tunable service URN, the DVR 20 acquires a free port. An error code indicating failure is transmitted to the direct access management server 40 as a direct access URI acquisition response <D-9> (FIG. 12: step S1207).

  When receiving the direct access start response <D-10> including the direct access URI list from the direct access management server 40 (FIG. 9: Step S917), the service server 30 determines whether the mobile direct flag is on or off ( FIG. 9: Step S918). When the mobile direct flag is on, in order to access the device specified by the direct access URI directly from the mobile phone 10, the service server 30 sends a new remote recording reservation response including the direct access URI <D- 13> is transmitted to the mobile phone 10 (FIG. 9: step S919). When the mobile direct flag is off, the service server 30 compares the direct access URI and the scheduled recording program information acquired from the mobile phone 10 by the new remote recording reservation request <D-4> with respect to the direct access URI. A new remote recording reservation request including is transmitted (FIG. 9: step S920).

  Hereinafter, some specific examples when the mobile phone 10 makes a recording reservation request to the DVR 20 will be described.

  [3-1. Remote recording reservation by proxy access in service server 30: Fig. 7]

  An operation when the service server 30 receives an instruction from the mobile phone 10 and makes a remote recording reservation for the DVR 20 on behalf of the service server 30 will be described. A part of FIG. 7 is a sequence diagram showing a flow of information when the service server 30 receiving an instruction from the mobile phone 10 makes a remote recording reservation for the DVR 20 on behalf of the user.

  The processing in each device up to the direct access start response <D-10> in the information flow among the mobile phone 10, the DVR 20, the service server 30, the direct access management server 40, and the router 50 is as described above.

  When the service server 30 that has received an instruction from the mobile phone 10 makes a remote recording reservation for the DVR 20 on behalf of the mobile phone 10, it is determined in step S918 that the mobile direct flag is off, and in step S917, the service server 30 Is included in the direct access start response <D-10> received by the DVR 20 as the direct access URI acquisition response <D-9> in step S1209. As already described, since the service server 30 only accesses the direct access URI received as the direct access start response <D-10>, whether the direct access URI corresponds to the DVR 20 or not. It is not particularly necessary to determine whether the management server 40 corresponds to tunneling.

  The service server 30 accesses the address of the DVR 20 included in the direct access URI received as the direct access start response <D-10> in step S917, and makes a new remote recording reservation request <D-4> from the mobile phone 10. A new remote recording reservation request <D-11> including the acquired recording reservation program information is transmitted (FIG. 9: step S920).

  When the DVR 20 receives the new remote recording reservation request <D-11> from the service server 30 (FIG. 12: Step S1210), the validity of the direct access URI included in the new remote recording reservation request <D-11> A check is performed (FIG. 12: Step S1211). If the URI is invalid, an error code indicating that is transmitted to the service server 30 as a new remote recording reservation response <D-11R> (FIG. 12: Step S1212). Here, for the validity check of the direct access URI, for example, a random number that cannot be easily imitated is added when the direct access URI is issued, and this random number is the direct access URI of the new remote recording reservation request <D-11>. There is a method to check whether or not it is included. If the URI is valid, the DVR 20 determines whether or not the recording reservation requested by the service server 30 and the recording reservation date and time are overlapped based on the recording reservation program information. When there is no overlapping recording reservation, the DVR 20 makes a recording reservation based on the recording reservation program information, and creates a reservation overlapping program list indicating no reservation overlapping. If a duplicate recording reservation is found, the DVR 20 creates a reservation duplicate program list including the recording date / time, channel, program title, etc. of the duplicate recording reservation. Thereafter, the DVR 20 transmits a new remote recording reservation response <D-11R> including the reserved duplicate program list to the service server 30 (FIG. 12: step S1213).

  When the service server 30 receives the new remote recording reservation response <D-11R> (FIG. 9: Step S921), the service server 30 displays the reserved duplicate program list of the new remote recording reservation response <D-11R> as a new remote recording reservation response <D -12> is transmitted to the mobile phone 10 (FIG. 9: Step S922). In addition, when the service server 30 receives the error code of the illegal URI as a new remote recording reservation response <D-11R> (FIG. 9: Step S923), the service server 30 receives the error code as a new remote recording reservation response <D-12 > Is transmitted to the mobile phone 10 (FIG. 9: Step S924).

  When the mobile phone 10 receives a new remote recording reservation response <D-12> including the reserved duplicate program list from the service server 30 (FIG. 8: step S823), the mobile phone 10 determines whether there is a reserved duplicate program from the reserved duplicate program list. If it is determined (FIG. 8: step S824) and there is a reserved duplicate program, information of the reserved duplicate program is displayed to the user through the display unit (FIG. 8: step S825). If there is no reserved duplicate program, the mobile phone 10 displays a message indicating the success of the remote recording reservation to the user through the display unit (FIG. 8: step S826).

  In addition, when the mobile phone 10 receives an error code of an illegal URI from the service server 30 as a new remote recording reservation response <D-12> (FIG. 8: Step S827), an error message indicating a direct access failure through the display unit Is displayed to the user (FIG. 8: step S828).

  [3-2. Remote recording reservation directly from mobile phone 10: Fig. 13]

  Next, an operation when the mobile phone 10 directly makes a remote recording reservation to the DVR 20 without going through the service server 30 will be described. FIG. 13 is a sequence diagram showing the flow of information when a remote recording reservation is made directly to the DVR 20 from the mobile phone 10.

  In the flow of information between the mobile phone 10, DVR 20, service server 30, direct access management server 40 and router 50 shown in FIG. 13, the processing in each device up to the direct access start response <D-10> is as shown in FIG. Since the flow is the same as that described with reference to FIG.

  In the case where the remote recording reservation is made directly to the DVR 20 from the mobile phone 10, it is determined in step S918 that the mobile direct flag is ON, and further, a new message transmitted from the service server 30 to the mobile phone 10 in step S919 This is a case where the remote recording reservation response <D-13> includes the URI transmitted by the DVR 20 as the direct access URI acquisition response <D-9> in step S1209. As already explained, since the mobile phone 10 only accesses the direct access URI received as the new remote recording reservation response <D-13>, whether the direct access URI corresponds to the DVR 20 or not. It is not particularly necessary to determine whether the access management server 40 corresponds to tunneling.

  When the mobile phone 10 receives a new remote recording reservation response <D-13> including the direct access URI from the service server 30 (FIG. 8: step S815), the address of the DVR 20 included in the direct access URI To transmit a new remote recording reservation request <D-14> including the URI for direct access and the recording reservation program information to the DVR 20 (FIG. 8: step S816).

  When the DVR 20 receives the new remote recording reservation request <D-14> from the mobile phone 10 (FIG. 12: Step S1210), the validity of the direct access URI included in the new remote recording reservation request <D-14> A check is performed (FIG. 12: Step S1211), and if the URI is invalid, an error code indicating that fact is transmitted to the mobile phone 10 as a new remote recording reservation response <D-14R> (FIG. 12: Step S1212). Here, for the validity check of the direct access URI, for example, a random number that cannot be easily imitated is added when the direct access URI is issued, and this random number is the direct access URI of the new remote recording reservation request <D-14>. There is a method to check whether or not it is included. If the URI is a valid URI, the DVR 20 determines whether or not the recording reservation requested by the mobile phone 10 and the recording reservation date and time are overlapped based on the recording reservation program information. When there is no overlapping recording reservation, the DVR 20 makes a recording reservation based on the recording reservation program information, and creates a reservation overlapping program list indicating no reservation overlapping. If a duplicate recording reservation is found, the DVR 20 creates a reservation duplicate program list including the recording date / time, channel, program title, etc. of the duplicate recording reservation. Thereafter, the DVR 20 transmits a new remote recording reservation response <D-14R> including the reserved duplicate program list to the mobile phone 10 (FIG. 12: Step S1213).

  When the mobile phone 10 receives the new remote recording reservation response <D-14R> (FIG. 8: Step S817), it determines the presence or absence of the reservation duplicate program from the reservation duplicate program list (FIG. 8: Step S818). Is present, the information of the reserved duplicate program is displayed to the user through the display unit (FIG. 8: step S819). If there is no reserved duplicate program, the mobile phone 10 displays a message indicating the success of the remote recording reservation to the user through the display unit (FIG. 8: step S820).

  In addition, when the mobile phone 10 receives the error code of the illegal URI as a new remote recording reservation response <D-14R> (FIG. 8: Step S821), an error message indicating a direct access failure is displayed to the user through the display unit. This is displayed (FIG. 8: Step S822).

  [3-3. Remote recording reservation using tunneling from service server 30: Fig. 14]

  Next, an operation when the service server 30 receives an instruction from the mobile phone 10 and makes a remote recording reservation for the DVR 20 using tunneling by the XMPP server 43 of the direct access management server 40 will be described. FIG. 14 is a sequence diagram showing a flow of information when the service server 30 receiving an instruction from the mobile phone 10 makes a remote recording reservation for the DVR 20 using tunneling by the XMPP server 43.

  In the flow of information between the mobile phone 10, DVR 20, service server 30, direct access management server 40 and router 50 shown in FIG. 14, the processing in each device up to the direct access start response <D-10> is as shown in FIG. Since the flow is the same as that described with reference to FIG.

  When the service server 30 receiving the instruction from the mobile phone 10 performs remote recording reservation for the DVR 20 using tunneling by the XMPP server 43, it is determined that the mobile direct flag is OFF in step S918, and This is a case where the direct access start response <D-10> received by the service server 30 in step S917 includes the tunneling URI assigned by the direct access management server 40 in step S1110. As already described, since the service server 30 only accesses the direct access URI received as the direct access start response <D-10>, whether the direct access URI corresponds to the DVR 20 or not. It is not particularly necessary to determine whether the management server 40 corresponds to tunneling.

  The service server 30 accesses the address of the direct access management server 40 included in the direct access URI received as the direct access start response <D-10> in step S917. A new remote recording reservation request <D-15> including the recording reservation program information acquired by the remote recording reservation request <D-4> is transmitted (FIG. 9: Step S920).

  When the direct access management server 40 receives the new remote recording reservation request <D-15> including the URI for direct access and the recording reservation program information (FIG. 11: Step S1112), the new remote recording reservation request <D-15 > Is checked (Figure 11: Step S1113), and if it is an illegal direct access URI, an error code indicating that it is an illegal URI will be sent to the new remote recording reservation response <D-17> To the service server 30 (FIG. 11: step S1114). If it is a valid direct access URI, the direct access management server 40 transmits a new remote recording reservation request <D-16> including recording reservation program information to the DVR 20 through the XMPP server 43 (FIG. 11: step S1115). . At this time, for example, the address portion of the direct access URI is filled with “0” so that the DVR 20 can recognize that the access is by tunneling via the XMPP server 43 in the direct access management server 40.

  When the DVR 20 receives the new remote recording reservation request <D-16> from the direct access management server 40 (FIG. 12: step S1210), the DVR 20 includes the URI for direct access included in the new remote recording reservation request <D-16>. A validity check is performed (FIG. 12: Step S1211), and if the URI is invalid, an error code indicating that is sent to the direct access management server 40 as a new remote recording reservation response <D-16R> (FIG. 12: Step S1212). If the URI is valid, the DVR 20 transmits information including the reserved duplicate program list to the direct access management server 40 as a new remote recording reservation response <D-16R> (FIG. 12: step S1213).

  When the direct access management server 40 receives the new remote recording reservation response <D-16R> including the reserved duplicate program list from the DVR 20 (FIG. 11: Step S1116), the new remote recording reservation response including the reserved duplicate program list < D-17> is transmitted to the service server 30 (FIG. 11: Step S1117).

  When the service server 30 receives the new remote recording reservation response <D-17> including the reserved duplicate program list (FIG. 9: Step S921), the new remote recording reservation response including the reserved duplicate program list <D-18> Is transmitted to the mobile phone 10 (FIG. 9: step S922). In addition, when the service server 30 receives the error code from the direct access management server 40 as a new remote recording reservation response <D-17> (FIG. 9: Step S923), the service server 30 receives this error code as a new remote recording reservation response <D-17. -18> is transmitted to the mobile phone 10 (FIG. 9: Step S924). The subsequent processing in the service server 30 and the mobile phone 10 is as described above.

  [3-4. Remote recording reservation using tunneling from mobile phone: Fig. 32]

  Next, an operation when the mobile phone 10 makes a remote recording reservation to the DVR 20 using tunneling by the XMPP server 43 of the direct access management server 40 without using the service server 30 will be described. FIG. 32 is a sequence diagram showing the flow of information when making a remote recording reservation for the DVR 20 from the mobile phone 10 using the tunneling by the XMPP server 43 without using the service server 30.

  In the flow of information between the mobile phone 10, DVR 20, service server 30, direct access management server 40 and router 50 shown in FIG. 32, the processing in each device up to the direct access start response <D-10> is as shown in FIG. Since the flow is the same as that described with reference to FIG.

  When the mobile phone 10 performs remote recording reservation for the DVR 20 using tunneling by the XMPP server 43 without going through the service server 30, it is determined in step S918 that the mobile direct flag is on, and This is a case where the new remote recording reservation response <D-13> transmitted from the service server 30 to the mobile phone 10 in step S919 includes the URI for tunneling assigned by the direct access management server 40 in step S1110. . As already explained, since the mobile phone 10 only accesses the direct access URI received as the new remote recording reservation response <D-13>, whether the direct access URI corresponds to the DVR 20 or not. It is not particularly necessary to determine whether the access management server 40 corresponds to tunneling.

  First, when the mobile phone 10 receives a new remote recording reservation response <D-13> including the direct access URI from the service server 30 (FIG. 8: step S815), the direct access included in the direct access URI The address of the access management server 40 is accessed, and a new remote recording reservation request <D-55> including the URI for direct access and the recording reservation program information is transmitted to the direct access management server 40 (FIG. 8: Step S816).

  When the direct access management server 40 receives the new remote recording reservation request <D-55> from the mobile phone 10 (FIG. 11: step S1112), the direct access URI included in the new remote recording reservation request <D-55> (FIG. 11: Step S1113), if it is an illegal direct access URI, an error code indicating that it is an illegal URI is sent to the mobile phone 10 as a new remote recording reservation response <D-57R> ( FIG. 11: Step S1114). If it is a valid direct access URI, the direct access management server 40 transmits a new remote recording reservation request <D-16> including recording reservation program information to the DVR 20 through the XMPP server 43 (FIG. 11: step S1115). . At this time, for example, the address portion of the direct access URI is filled with “0” so that the DVR 20 can recognize that the access is by tunneling via the XMPP server 43 in the direct access management server 40.

  When the DVR 20 receives the new remote recording reservation request <D-16> from the direct access management server 40 (FIG. 12: step S1210), the DVR 20 includes the URI for direct access included in the new remote recording reservation request <D-16>. A validity check is performed (FIG. 12: Step S1211), and if the URI is invalid, an error code indicating that is sent to the direct access management server 40 as a new remote recording reservation response <D-16R> (FIG. 12: Step S1212). If the URI is valid, the DVR 20 transmits information including the reserved duplicate program list to the direct access management server 40 as a new remote recording reservation response <D-16R> (FIG. 12: step S1213).

  When the direct access management server 40 receives the new remote recording reservation response <D-16R> including the reserved duplicate program list from the DVR 20 (FIG. 11: step S1116), the new remote recording reservation response including the reserved duplicate program list <D -57R> is transmitted to the mobile phone 10 (FIG. 11: step S1117). In addition, when the direct access management server 40 receives an error code from the DVR 20 as a new remote recording reservation response <D-16R>, the error code is sent to the mobile phone 10 as a new remote recording reservation response <D-57R>. Send. The subsequent processing in the mobile phone 10 is as described above.

  As described above, the mobile phone 10 uses not only direct access to the DVR 20 but also proxy access by the service server 30 and tunneling using XMPP by the direct access management server 40 to record to the DVR 20. It is possible to execute a reservation process.

  [4. Content acquisition]

  Next, an operation when the mobile phone 10 acquires content from the DVR 20 will be described. FIG. 15 is a sequence diagram showing a flow of information at the time of content acquisition by direct access from the mobile phone 10 to the DVR 20. FIG. 17 is a flowchart showing the operation of the mobile phone 10 at the time of content acquisition, and FIGS. 18 and 19 are flowcharts showing the operation of the service server 30 at the time of content acquisition.

  When an instruction to start using direct access is given to the mobile phone 10 in order to receive the content acquisition service from the user of the mobile phone 10 (FIG. 17: Step S1701), the mobile phone 10 is a user preset in itself A controlled device list acquisition request <D-1> including identification information is transmitted to the service server 30 (FIG. 17: step S1702).

  When the service server 30 receives the controlled device list acquisition request <D-1> from the mobile phone 10 (FIG. 9: Step S901), the service server 30 includes the user identification information included in the controlled device list acquisition request <D-1>. It is determined whether or not the corresponding control device / service management ID is stored in the storage unit 31 (FIG. 9: Step S902). If the control device / service management ID corresponding to the user identification information is not stored in the storage unit 31, the service server 30 displays an error code indicating that registration of the controlled device to be serviced is required. An acquisition response <D-3> is transmitted to the mobile phone 10 (FIG. 9: Step S903). When the control device / service management ID corresponding to the user identification information is stored in the storage unit 31, a list of controlled devices associated with the control device / service management ID managed by the direct access management server 40 The service server 30 transmits a controlled device list acquisition request <D-2> including a Service ID that is information for identifying a service and a control device / service management ID to the direct access management server 40 (see FIG. 9: Step S904).

  When the direct access management server 40 receives the controlled device list acquisition request <D-2> from the service server 30 (FIG. 10: step S1012), the ServiceID included in the controlled device list acquisition request <D-2> And whether the combination of the control device / service management ID matches the one stored in the storage unit 41 (FIG. 10: step S1013). The error code shown is transmitted to the service server 30 as a controlled device list acquisition response <D-2R> (FIG. 10: step S1014). If it is determined that the combination of ServiceID and control device / service management ID included in the controlled device list acquisition request <D-2> is stored in the storage unit 41, the direct access management server 40 stores Number re-assigned to the controlled device management ID of the controlled device that can be controlled from the mobile phone 10 according to the content of the control device / service management ID stored in the unit 41 and the controlled device management ID And a list of device names included in the device authentication information of the controlled device is generated as a controlled device list, and this controlled device list is stored in the storage unit 41 in association with the control device / service management ID, A controlled device list acquisition response <D-2R> including this controlled device list is transmitted to the service server 30 (FIG. 10: step S1015).

  If the service server 30 receives an unregistered error code from the direct access management server 40 as a controlled device list acquisition response <D-2R> (FIG. 9: Step S905), the controlled device registration Is transmitted to the mobile phone 10 as a controlled device list acquisition response <D-3> (FIG. 9: step S906). When the service server 30 receives the controlled device list acquisition response <D-2R> including the controlled device list from the direct access management server 40 (FIG. 9: step S907), the controlled device list is included. A controlled device list acquisition response <D-3> is transmitted to the mobile phone 10 (FIG. 9: Step S908).

  When the mobile phone 10 receives the error code from the service server 30 as the controlled device list acquisition response <D-3> (FIG. 17: step S1703), the mobile phone 10 displays an error message indicating that the controlled device needs to be registered. Then, it is displayed to the user through the display unit (FIG. 17: step S1704). In addition, when the mobile phone 10 receives the controlled device list acquisition response <D-3> including the controlled device list (FIG. 17: Step S1705), the number of the controlled devices in the controlled device list Is determined (FIG. 17: step S1706). When there are a plurality of controlled device numbers, the mobile phone 10 displays the contents of the controlled device list on the display unit (FIG. 17: step S1707), and the user controls one controlled device from among them. The number of the device is selected (FIG. 17: step S1708), and the selected number of the controlled device is stored in the storage unit 11 (FIG. 17: steps S1709 and 1710). If a plurality of controlled devices do not exist, the number of the one controlled device is stored in the storage unit 11 (FIG. 17: steps S1711, S1710).

  Next, the mobile phone 10 determines whether to access the content acquisition service of the DVR 20 directly from the mobile phone 10 or via the service server 30 based on the mobile direct flag preset in itself. The process branches (FIG. 17: step S1712).

  When accessing the content acquisition service of the DVR 20 directly from the mobile phone 10, the mobile phone 10 sends a content search request including user identification information, search conditions, controlled device number, mobile direct flag (on) <D-44> Is transmitted to the service server 30 (FIG. 17: step S1713). Further, when the mobile phone 10 acquires content via the service server 30, the mobile phone 10 sends a content search request including user identification information, search conditions, controlled device number, mobile direct flag (off) <D- 44> is transmitted to the service server 30 (FIG. 17: step S1724). Here, the search condition is a condition for searching for content. For example, the search condition is information that specifies that the content is still image data or that the content is recorded video data. More detailed search conditions may be set by adding items such as date and data size as search conditions.

  Upon receiving the content search request <D-44> from the mobile phone 10 (FIG. 18: step S1801), the service server 30 checks whether an available XMPP session ID is stored in the storage unit 31 (FIG. 18: Step S1802). If an available XMPP session ID is already stored in the storage unit 31, the service server 30 sets the value of the mobile direct flag included in the content search request <D-44> to ServiceID, control device / service management ID, controlled The information is stored in the storage unit 31 in association with the device number (FIG. 18: step S1803). If an available XMPP session ID is not stored, the service server 30 establishes an XMPP session with the XMPP server 43, and includes an XMPP login that includes the ServiceID, control device / service management ID, and controlled device number. The request <D-5> is transmitted to the direct access management server 40 (FIG. 18: Step S1804).

  When the direct access management server 40 receives the XMPP login request <D-5> from the service server 30 (FIG. 10: Step S1016), the Service ID, control device / service management included in the XMPP login request <D-5> It is determined whether the combination of the ID and the number of the controlled device is stored in the storage unit 41 (FIG. 10: Step S1017). If not stored, the direct access management server 40 sends an error code indicating that the corresponding controlled device to be serviced does not exist as an XMPP login response <D-5R> to the service server 30 (FIG. 10: Step S1018). If the corresponding controlled device to be serviced is stored in the storage unit 41, the direct access management server 40 generates and stores an XMPP session ID (FIG. 10: step S1019), and this XMPP session ID An XMPP login response <D-5R> including is transmitted to the service server 30 (FIG. 10: step S1020).

  When the service server 30 receives the XMPP login response <D-5R> including the XMPP session ID from the direct access management server 40 (FIG. 18: step S1805), the XMPP session ID included therein and the content search in step S1801 The value of the portable direct flag included in the request <D-44> is stored in the storage unit 31 in association with the Service ID, the control device / service management ID, and the controlled device list number (FIG. 18: Step S1806).

  After storing the portable direct flag in step S1803 or step S1806, the service server 30 sends a direct access start request <D-6> including the Service ID, control device / service management ID, service URN, and XMPP session ID to the direct access management server 40. Transmit (FIG. 18: Step S1807). Here, since the mobile phone 10 is about to acquire content from the DVR 20, the service URN is information for designating the content acquisition service.

  Upon receiving the direct access start request <D-6> from the service server 30 (FIG. 11: Step S1101), the direct access management server 40 controls the ServiceID included in this direct access start request <D-6>. It is determined whether the combination of device / service management ID is stored in the storage unit 41 (FIG. 11: Step S1102), and if it is not stored, an error code indicating that registration of the controlled device is required is directly performed. The access start response <D-10> is transmitted to the service server 30 (FIG. 11: Step S1103). When the combination of ServiceID and control device / service management ID included in the direct access start request <D-6> is stored in the storage unit 41, the direct access management server 40 sends the direct access start request <D XMPP session ID included in -6> is stored in the storage unit 41 in association with the combination of Service ID and control device / service management ID included in the direct access start request <D-6>. It is determined whether or not (FIG. 11: step S1104). If it is not stored, the direct access management server 40 transmits an error code indicating an unauthorized XMPP session ID to the service server 30 as a direct access start response <D-10> (FIG. 11: step S1105). . The XMPP session ID included in the direct access start request <D-6> is stored in association with the combination of the Service ID and control device / service management ID included in the direct access start request <D-6>. If it is stored in the unit 41, the direct access management server 40 sends a direct access URI acquisition request <D-7> including the specification information of the service URN specified in the direct access start request <D-6>. Then, the data is transmitted to the DVR 20 via the XMPP server 43 in the direct access management server 40 (FIG. 11: Step S1106).

  When the service server 30 receives an error code indicating an illegal XMPP session ID from the direct access management server 40 as a direct access start response <D-10> (FIG. 18: step S1808), the service server 30 returns to step S1804, The XMPP login request <D-5> is transmitted again to the direct access management server 40, and the XMPP session is established again.

  When the DVR 20 receives a direct access URI acquisition request <D-7> including the service URN specification information from the direct access management server 40 (FIG. 12: step S1201), the DVR 20 allocates a local port for direct access. (FIG. 12: Step S1202). Next, the DVR 20 sends a direct access port NAT setting request <D-8> including the local IP address assigned in advance to the DVR 20 and the port number of the local port for direct access to the router 50 to The router 50 is requested to map the global IP address and port number accessible from the Internet to the IP address and port number (FIG. 12: step S1203).

  In response to the direct access port NAT setting request <D-8> in step S1203, the DVR 20 sends a global IP address and port number acquisition error from the router 50 to the direct access port NAT setting response <D-8R>. (FIG. 12: step S1204), based on the service URN designation information acquired in step S1201, it is determined whether or not the service URN can be tunneled (FIG. 12: step S1205). If the DVR 20 determines that the service URN included in the direct access URI acquisition request <D-7> is a tunnelable service URN, the DVR 20 sends an error code indicating tunneling to the direct access URI acquisition response. It is transmitted to the direct access management server 40 as <D-9> (FIG. 12: Step S1206). If the specified service URN information included in the direct access URI acquisition request <D-7> is not a tunnelable service URN, the DVR 20 sends an error code indicating failure to acquire a free port as a direct access URI acquisition response. It is transmitted to the direct access management server 40 as <D-9> (FIG. 12: Step S1207). Here, since the amount of data transferred in the content acquisition service is larger than that in the remote recording reservation service, the service URN cannot be tunneled. However, the content acquisition service is not limited to this. Whether or not tunneling is possible can be appropriately set by the service provider according to the capability of the direct access management server 40.

  In response to the NAT setting request <D-8> for the direct access port, the DVR 20 sends the global IP address and port number associated with the local IP address and port number of the DVR 20 from the router 50 to the NAT setting response < If it is received as D-8R> (Figure 12: Step S1208), a direct access URI list is created using these global IP addresses and port numbers, and this direct access URI list is obtained. The response <D-9> is transmitted to the direct access management server 40 (FIG. 12: step S1209).

  When the XMPP server 43 of the direct access management server 40 receives the direct access URI list as a direct access URI acquisition response <D-9> (FIG. 11: step S1107), the direct access URI list is sent as a direct access start response. It is transmitted to the service server 30 as <D-10> (FIG. 11: Step S1111).

  When the direct access management server 40 receives an error code instructing content acquisition by tunneling as a direct access URI acquisition response <D-9> (FIG. 11: step S1109), the direct access management server 40 Assign a tunneling port (Figure 11: Step S1110), and create a direct access URI list using the assigned port number of the tunneling port in the direct access management server 40 and the global IP address of the direct access management server 40. Then, a direct access start response <D-10> including this direct access URI list is transmitted to the service server 30 (FIG. 11: step S1111).

  Upon receiving the direct access start response <D-10> from the direct access management server 40 (FIG. 18: Step S1809), the service server 30 determines whether the mobile direct flag is on or off (FIG. 18: Step S1810). . When the mobile direct flag is on, the service server 30 directly accesses the device specified by the direct access URI from the mobile phone 10 to search the content search response including the direct access URI <D-20> Is transmitted to the mobile phone 10 (FIG. 18: step S1811). When the mobile direct flag is off, the service server 30 includes the direct access URI and the search condition acquired by the content search request <D-44> from the mobile phone 10 with respect to the direct access URI. The content search request <D-19> is transmitted to the DVR 20 (FIG. 18: Step S1812).

  Hereinafter, some specific examples when the mobile phone 10 makes a content acquisition request to the DVR 20 will be described.

  [4-1. Direct access from mobile phone 10: Fig. 15]

  The operation when the mobile phone 10 directly acquires content from the DVR 20 without going through the service server 30 will be described. FIG. 15 is a sequence diagram showing the flow of information when content is acquired directly from the DVR 20 from the mobile phone 10.

  In the flow of information between the mobile phone 10, DVR 20, service server 30, direct access management server 40 and router 50 shown in FIG. 15, the processing in each device up to the direct access start response <D-10> has been described above. Street.

  The case where content is directly acquired from the mobile phone 10 to the DVR 20 is a case where it is determined in step S1810 that the mobile direct flag is on, and further, tunneling in the direct access management server 40 is not performed.

  First, a flow of requesting content search directly from the mobile phone 10 to the DVR 20 and acquiring a title list of content that matches the search condition will be described.

  When the mobile phone 10 receives the content search response <D-20> including the direct access URI from the service server 30 (FIG. 17: Step S1714), the mobile phone 10 accesses the address of the DVR 20 included in the direct access URI, A content search request <D-29> including the direct access URI and search conditions is transmitted to the DVR 20 (FIG. 17: step S1715).

  When the DVR 20 receives the content search request <D-29> including the URI for direct access and the search condition from the mobile phone 10 (FIG. 12: Step S1214), the direct access included in the content search request <D-29> The URI is checked for validity (Fig. 12: Step S1215) .If the URI is invalid, an error code indicating that it is invalid is sent to the mobile phone 10 as a content search response <D-29R> ( FIG. 12: Step S1216). If the URI is valid, the DVR 20 searches the storage unit 21 for content that matches the search condition according to the search condition in the content search request <D-29>, and searches the title list of the search result content and Local Generate a URI list. Thereafter, the DVR 20 transmits the generated title list and Local URI list to the mobile phone 10 as a content search response <D-29R> (FIG. 12: step S1217). Here, the Lacal URI is information (URI) indicating a local storage location of content. For example, information indicating a storage location in the storage unit 21 specified by a local designation method in the DVR 20, or in a home network specified by a local address in a home network to which the DVR 20 is connected Information indicating the storage location in

  When the mobile phone 10 receives an error code indicating that it is an invalid URI from the DVR 20 as a content search response <D-29R> (FIG. 17: step S1722), a message indicating a direct access failure is sent to the user through the display unit. It is displayed (FIG. 17: Step S1723).

  Further, when the mobile phone 10 receives a content search response <D-29R> including a content title list and a Local URI list from the DVR 20 (FIG. 17: step S1716), the mobile phone 10 proceeds to processing for content acquisition. .

  Next, a process flow for the mobile phone 10 to directly acquire content from the DVR 20 will be described.

  When receiving a content search response <D-29R> including a content title list and a Local URI list from the DVR 20 (FIG. 17: Step S1716), the mobile phone 10 displays a list of received content titles on the display unit. Then, a Local URI list for extracting the Local URI corresponding to the content selected by the user from the displayed title and requesting acquisition of the content is created. Thereafter, the mobile phone 10 transmits a URI acquisition request <D-30> including the user identification information, the Local URI list of the selected content, and the number of the controlled device to the service server 30 (FIG. 17: Step S1717). Here, the reason why the mobile phone 10 acquires the URI for direct access to the DVR 20 again is that the Local URI acquired in step S1716 points to a location that cannot be directly accessed from the Internet.

  Upon receiving the URI acquisition request <D-30> (FIG. 19: Step S1901), the service server 30 checks whether or not an available XMPP session ID is stored in the storage unit 31 (FIG. 19: Step S1902). . If the available XMPP session ID is not stored, the service server 30 transmits an XMPP login request <D-5> to the direct access management server 40 (FIG. 19: step S1903). The service server 30 receives the XMPP login response <D-5R> from the direct access management server 40 (FIG. 19: Step S1904), and stores the XMPP session ID included in the received XMPP login response <D-5R>. The data is stored in the unit 31 (FIG. 19: Step S1905). Thereafter, the service server 30 transmits a direct access start request <D-31> including the Service ID, the control device / service management ID, the service URN, the XMPP session ID, and the content local URI list to the direct access management server 40 (FIG. 19: Step S1906). Even when an available XMPP session ID is already stored, the service server 30 transmits a direct access start request <D-31> to the direct access management server 40 (FIG. 19: step S1906). Here, since the mobile phone 10 is about to acquire content from the DVR 20, the service URN is information for designating the content acquisition service.

  Upon receiving this direct access start request <D-31> (FIG. 11: Step S1101), the direct access management server 40 stores the combination of ServiceID and control device / service management ID included in the storage unit 41. (FIG. 11: Step S1102), and if it is not stored, an error code indicating that the controlled device needs to be registered is sent as a direct access start response <D-35> to the service server 30 (FIG. 11: Step S1103). When the combination of ServiceID and control device / service management ID is stored in the storage unit 41, the direct access management server 40 determines that the XMPP session ID included in the direct access start request <D-31> It is determined whether or not the service ID and the control device / service management ID included in the access start request <D-31> are stored in the storage unit 41 in association with each other (FIG. 11: step S1104). If it is not stored, the direct access management server 40 transmits an error code indicating an unauthorized XMPP session ID to the service server 30 as a direct access start response <D-35> (FIG. 11: Step S1105). . When the XMPP session ID is stored in the storage unit 41 in association with the combination of the Service ID and the control device / service management ID, the direct access management server 40 is designated by the direct access start request <D-31>. A direct access URI acquisition request <D-32> including the service URN and the Local URI list is transmitted to the DVR 20 (FIG. 11: step S1106).

  When the service server 30 receives from the direct access management server 40 an error code indicating an illegal XMPP session ID as a direct access start response <D-35> (FIG. 19: step S1907), the service server 30 returns to step S1903, The XMPP login request <D-5> is made again to the direct access management server 40, and the XMPP login response <D-5R> is received from the direct access management server 40 (FIG. 19: Step S1904). The stored XMPP session ID is stored in the storage unit 41 (FIG. 19: step S1905).

  Upon receiving the direct access URI acquisition request <D-32> from the direct access management server 40 (FIG. 12: step S1201), the DVR 20 assigns a local port for direct access (FIG. 12: step S1202). Next, the DVR 20 transmits a direct access port NAT setting request <D-33> including the local IP address and the port number of the direct access local port to the router 50 (FIG. 12: step S1203).

  When the DVR 20 receives an acquisition error of the global IP address and port number from the router 50 as the NAT setting response <D-33R> from the service server 30 (FIG. 12: step S1204), the service URN acquired in step S1201 Based on the designation information, it is determined whether or not the service URN can be tunneled (FIG. 12: step S1205). If the DVR 20 determines that the service is a tunnelable service URN, the DVR 20 transmits an error code instructing tunneling to the direct access management server 40 as a direct access URI acquisition response <D-34> (FIG. 12: step S1206). ). If the specified service URN information is not a tunnelable service URN, an error code indicating failure to acquire a free port is sent to the direct access management server 40 as a direct access URI acquisition response <D-34> (FIG. 12: Step S1207).

  Also, in response to the NAT setting request <D-33> for the direct access port, the DVR 20 sends the global IP address and port number associated with the local IP address and port number of the DVR 20 from the router 50 as a NAT setting response. If it is received as <D-33R> (Figure 12: Step S1208), a direct access URI list is created using these global IP addresses and port numbers, and this direct access URI list is used as the direct access URI. An acquisition response <D-34> is transmitted to the direct access management server 40 (FIG. 12: step S1209).

  When the XMPP server 43 of the direct access management server 40 receives the direct access URI list as a direct access URI acquisition response <D-34> (FIG. 11: Step S1107), the direct access URI list is sent as a direct access start response. It is transmitted to the service server 30 as <D-35> (FIG. 11: Step S1111).

  Also, when the direct access management server 40 receives an error code instructing content acquisition by tunneling as a direct access URI acquisition response <D-34> (FIG. 11: step S1109), the direct access management server 40 Assign a tunneling port (Figure 11: Step S1110), and create a direct access URI list using the assigned port number of the tunneling port in the direct access management server 40 and the global IP address of the direct access management server 40. Then, a direct access start response <D-35> including this direct access URI list is transmitted to the service server 30 (FIG. 11: step S1111).

  When the service server 30 receives a direct access start response <D-35> including the direct access URI list from the direct access management server 40 (FIG. 19: step S1908), the service server 30 includes the direct access URI list. The URI acquisition response <D-36> is transmitted to the mobile phone 10 (FIG. 19: step S1909).

  As described above, since the mobile phone 10 has acquired the direct access URI for directly acquiring the content from the DVR 20, the process of acquiring the selected content from the DVR 20 is started. Here, in the direct access URI list received by the mobile phone 10 as the URI acquisition response <D-36>, the direct access URI corresponding to each content selected by the user is stored.

  When the mobile phone 10 receives the URI acquisition response <D-36> including the direct access URI list (FIG. 17: step S1718), the direct access URI for the content to be acquired from the direct access URI list. The content acquisition request <D-37> including the direct access URI is directly transmitted to the DVR 20 (FIG. 17: step S1719).

  Upon receiving the content acquisition request <D-37> including the direct access URI from the mobile phone 10 (FIG. 12: Step S1218), the DVR 20 validates the direct access URI included in the content acquisition request <D-37>. (Figure 12: Step S1219), if it is an invalid URI, an error code indicating that the URI is invalid is sent to the mobile phone 10 as a content acquisition response <D-37R> (Figure 12: Step S1220). If the URI is valid, the DVR 20 transmits the content specified by the direct access URI to the mobile phone 10 as a content acquisition response <D-37R> (FIG. 12: step S1221).

  When the mobile phone 10 receives the content from the DVR 20 as the content acquisition response <D-37R> (FIG. 17: Step S1720), until the acquisition of all the content stored in the direct access URI list is completed (FIG. 17). : Step S1721) and the transmission of the content acquisition request <D-37> in step S1719 to the DVR 20 are repeated. In addition, when the mobile phone 10 receives an error code indicating that the URI is invalid from the DVR 20 as the content acquisition response <D-37R>, the mobile phone 10 displays a message indicating a direct access failure to the user through the display unit. .

  [4-2. Content acquisition via service server 30: Fig. 16]

  Next, an operation when the mobile phone 10 acquires content from the DVR 20 via the service server 30 will be described. FIG. 16 is a sequence diagram showing a flow of information at the time of content acquisition by direct access from the service server 30 to the DVR 20.

  In the flow of information between the mobile phone 10, DVR 20, service server 30, direct access management server 40, and router 50 shown in FIG. 16, the processing in each device up to the direct access start response <D-10> is shown in FIG. Since the flow is the same as that described with reference to FIG.

  The case where content is acquired from the DVR 20 from the mobile phone 10 via the service server 30 is a case where it is determined in step S1810 that the mobile direct flag is off, and further, tunneling is not performed in the direct access management server 40. is there.

  First, a flow of requesting content search from the mobile phone 10 directly to the DVR 20 via the service server 30 and acquiring a title list of content that matches the search conditions will be described.

  When the DVR 20 receives the content search request <D-19> including the direct access URI and the search condition transmitted from the service server 30 in step S1812, (FIG. 12: step S1214), the content search request <D-19> Check the validity of the URI for direct access included in the service server (Figure 12: Step S1215). If it is an invalid URI, the service server uses an error code indicating that it is an invalid URI as a content search response <D-19R>. 30 (FIG. 12: Step S1216). If the URI is valid, the DVR 20 searches the storage unit 21 for content that matches the search condition according to the search condition in the content search request <D-19> Generate a URI list. Thereafter, the DVR 20 transmits the generated title list and Local URI list to the service server 30 as a content search response <D-19R> (FIG. 12: Step S1217).

  When the service server 30 receives the content title list and the local URI list from the DVR 20 as the content search response <D-19R> (FIG. 18: step S1813), the service server 30 temporarily stores the local URI list of the content (FIG. 18: Step S1814), a content search response <D-20> including the content title list is transmitted to the mobile phone 10 (FIG. 18: Step S1815).

  Further, when the service server 30 receives an error code indicating an invalid URI as the content search response <D-19R> from the DVR 20 (FIG. 18: Step S1816), the service server 30 sends the error code to the mobile phone. 10 is transmitted as a content search response <D-20> (FIG. 18: step S1817).

  When the mobile phone 10 receives the content search response <D-20> with an error code indicating that the URI is invalid from the service server 30 (FIG. 17: step S1728), the mobile phone 10 displays a message indicating a direct access failure. It is displayed to the user through the display unit (FIG. 17: step S1729). Further, when the mobile phone 10 receives the content title list from the service server 30 as the content search response <D-20> (FIG. 17: step S1725), the mobile phone 10 proceeds to processing for content acquisition.

  Next, a processing flow for the mobile phone 10 to acquire content from the DVR 20 via the service server 30 will be described.

  When the mobile phone 10 receives the content search response <D-20> including the content title list from the service server 30 (FIG. 17: step S1725), the mobile phone 10 displays the received content title list on the display unit, A title corresponding to the content selected by the user is extracted from the displayed titles, and an acquisition title list for requesting acquisition of the content is created.

  Thereafter, the mobile phone 10 transmits a content acquisition request <D-21> including the user identification information, the selected content title list (acquired title list), and the number of the controlled device to the service server 30 (FIG. 17: Step S1726). ). When the service server 30 receives the content acquisition request <D-21> (FIG. 18: step S1818), the storage unit 31 stores a local URI list of content corresponding to the title list included in the content acquisition request <D-21>. (FIG. 18: step S1819), the local URI corresponding to the title of the content selected by the user is extracted, and a local URI list for requesting acquisition of the content is created.

  Next, the service server 30 checks whether an available XMPP session ID is stored in the storage unit 31 (FIG. 18: step S1820). If no available XMPP session ID is stored, the service server 30 transmits an XMPP login request <D-5> to the direct access management server (FIG. 18: step S1821). When the service server 30 receives the XMPP login response <D-5R> from the direct access management server (FIG. 18: step S1822), the storage server 31 stores the XMPP session ID included in the received XMPP login response <D-5R>. (FIG. 18: step S1823). Thereafter, the service server 30 sends a direct access start request <D-22> including the Service ID, the control device / service management ID, the service URN, the XMPP session ID, and the content local URI list to the direct access management server 40 (FIG. 18: Step S1824). Also, even when an available XMPP session ID is already stored, the service server 30 transmits a direct access start request <D-22> to the direct access management server 40 (FIG. 18: step S1824). Here, since content acquisition is to be performed for the DVR 20, the service URN is information for designating the content acquisition service.

  Upon receiving this direct access start request <D-22> (FIG. 11: Step S1101), the direct access management server 40 stores the combination of the Service ID and the control device / service management ID included in the request in the storage unit 41. (FIG. 11: Step S1102), and if it is not stored, an error code indicating that the controlled device needs to be registered is given a direct access start response <D-26> as a service server 30 (FIG. 11: Step S1103). When the combination of ServiceID and control device / service management ID is stored in the storage unit 41, the direct access management server 40 determines that the XMPP session ID included in the direct access start request <D-22> It is determined whether or not the service ID included in the access start request <D-22> is associated with the combination of the control device / service management ID and stored in the storage unit 41 (FIG. 11: step S1104). If it is not stored, the direct access management server 40 transmits an error code indicating an unauthorized XMPP session ID to the service server 30 as a direct access start response <D-26> (FIG. 11: Step S1105). . When the XMPP session ID is stored in the storage unit 41 in association with the combination of the Service ID and the control device / service management ID, the direct access management server 40 is designated by the direct access start request <D-31>. A direct access URI acquisition request <D-23> including the service URN and the Local URI list is transmitted to the DVR 20 (FIG. 11: step S1106).

  When the service server 30 receives an error code indicating an invalid XMPP session ID from the direct access management server 40 as a direct access start response <D-26> (FIG. 18: step S1825), the service server 30 returns to step S1820 for use. Whether or not a possible XMPP session ID is stored in the storage unit 31 is checked again.

  When the DVR 20 receives the direct access URI acquisition request <D-23> from the direct access management server 40 (FIG. 12: step S1201), the DVR 20 allocates a local port for direct access (FIG. 12: step S1202). Next, the DVR 20 transmits a direct access port NAT setting request <D-24> including the local IP address and the port number of the direct access local port to the router 50 (FIG. 12: step S1203).

  When the DVR 20 receives an acquisition error of the global IP address and port number from the router 50 as the NAT setting response <D-24R> from the service server 30 (FIG. 12: step S1204), the service URN acquired in step S1201 Based on the designation information, it is determined whether or not the service URN can be tunneled (FIG. 12: step S1205). If the DVR 20 determines that the service is a tunnelable service URN, it sends an error code instructing tunneling to the direct access management server 40 as a direct access URI acquisition response <D-25> (FIG. 12: Step S1206). If the specified service URN information is not a tunnelable service URN, an error code indicating failure to acquire a free port is sent to the direct access management server 40 as a direct access URI acquisition response <D-25> (FIG. 12: Step S1207).

  In response to the NAT setting request <D-24> for the direct access port, the DVR 20 sends the global IP address and port number associated with the local IP address and port number of the DVR 20 from the router 50 to the NAT setting response. If received as <D-24R> (Figure 12: Step S1208), create a direct access URI list using these global IP addresses and port numbers, and use this direct access URI list as the direct access URI. An acquisition response <D-25> is transmitted to the direct access management server 40 (FIG. 12: step S1209).

  When the XMPP server 43 of the direct access management server 40 receives the direct access URI list as a direct access URI acquisition response <D-25> (FIG. 11: step S1107), the direct access start response is sent to the direct access URI list. <D-26> is transmitted to the service server 30 (FIG. 11: Step S1111).

  Further, when the direct access management server 40 receives an error code instructing content acquisition by tunneling as a direct access URI acquisition response <D-25> (FIG. 11: step S1109), the direct access management server 40 Assign a tunneling port (Figure 11: Step S1110), and create a direct access URI list using the assigned port number of the tunneling port in the direct access management server 40 and the global IP address of the direct access management server 40. Then, a direct access start response <D-26> including this direct access URI list is transmitted to the service server 30 (FIG. 11: step S1111).

  As described above, since the service server 30 has acquired the direct access URI for directly acquiring the content from the DVR 20, the service server 30 starts the process of acquiring the selected content from the DVR 20. Here, the direct access URI list received by the service server 30 as the direct access start response <D-26> stores a direct access URI corresponding to each content selected by the user.

  When the service server 30 receives the direct access start response <D-26> including the direct access URI list (FIG. 18: step S1826), the service server 30 performs direct processing corresponding to the content to be acquired from the direct access URI list. The access URI is selected, and a content acquisition request <D-27> including the direct access URI is transmitted to the DVR 20 (FIG. 18: step S1827). When the DVR 20 receives the content acquisition request <D-27> from the service server 30 (FIG. 12: step S1218), the DVR 20 checks the validity of the direct access URI included in the content acquisition request <D-27> ( FIG. 12: Step S1219) If it is an illegal URI, an error code indicating that it is an illegal URI is transmitted to the service server 30 as a content acquisition response <D-27R> (FIG. 12: Step S1220). If the URI is valid, the DVR 20 transmits the content specified by the direct access URI to the service server 30 as a content acquisition response <D-27R> (FIG. 12: step S1221).

  When the service server 30 receives the content from the DVR 20 as a content acquisition response <D-27R> (FIG. 18: Step S1828), the service server 30 transmits the content as a content acquisition response <D-28> to the mobile phone 10 (FIG. 18: Step S1829), until the transmission of all the contents stored in the direct access URI list to the mobile phone 10 is completed, repeatedly sending the content acquisition request <D-27> of Step S1827 to the DVR 20 (FIG. 18: Step S1830). When the mobile phone 10 receives the content acquisition response <D-28> including the content (FIG. 17: Step S1727), the received content is displayed to the user through the display unit.

  In addition, when the service server 30 receives an error code indicating that the URI is invalid from the DVR 20 as the content acquisition response <D-27R> (FIG. 18: step S1831), the service server 30 sends this error code to the content acquisition response < D-28> is transmitted to the mobile phone 10 (FIG. 18: step S1832).

  As described above, the mobile phone 10 can acquire content from the DVR 20 by using direct access to the DVR 20 or proxy access by the service server 30. In the above description, the content acquisition service has been described as a service that cannot be tunneled. However, by applying the tunneling process described in the remote recording reservation service to the content acquisition service, the direct access management server can also be used in the content acquisition service. It is possible to acquire content from the DVR 20 using the tunneling process via the 40 XMPP servers 43.

  [5. End of direct access]

  Next, a description will be given of a process in which the above-described various processes are completed and the direct access is terminated by the service server 30, the direct access management server 40, and the DVR 20. 20 is a sequence diagram showing the flow of information at the end of direct access, FIG. 21 is a flowchart showing the operation of the service server 30 at the end of direct access, and FIG. 22 shows the operation of the direct access management server 40 at the end of direct access. FIG. 23 is a flowchart showing the operation of the DVR 20 at the end of direct access.

  When the service server 30 receives the direct access end notification <C-1> including the user identification information from the mobile phone 10 (FIG. 21: step S2101), the service server 30, the control device / service management ID, the XMPP session ID, the service URN Then, the direct access end notification <C-2> including the direct access URI is transmitted to the direct access management server 40 (FIG. 21: step S2102).

  When receiving the direct access end notification <C-2> (FIG. 22: Step S2201), the direct access management server 40 transmits a direct access end notification <C-3> including the service URN and the direct access URI to the DVR 20. (FIG. 22: Step S2202). At this time, if no direct access URI is specified in the direct access end notification <C-2> (FIG. 22: step S2206), a direct access end notification <C-3> including only the service URN is transmitted to the DVR 20 (FIG. 22). 22: Step S2207).

  When the DVR 20 receives the direct access end notification <C-3> including the service URN and direct access URI (FIG. 23: step S2301), the direct access including the global IP address and port number related to the specified direct access URI The communication port is closed <C-4> (FIG. 23: Step S2302).

  On the other hand, after transmitting the direct access end notification <C-2>, the service server 30 initializes the portable direct flag (FIG. 21: step S2103). Next, an XMPP logout notification <C-5> including ServiceID, control device / service management ID, and XMPP session ID is transmitted to the direct access management server 40 (FIG. 21: step S2104). Finally, the service server 30 deletes the XMPP session ID entry (FIG. 21: step S2105).

  When the direct access management server 40 receives the XMPP logout notification <C-5> including the Service ID, the control device / service management ID, and the XMPP session ID (FIG. 22: step S2203), all the service URNs related to the XMPP session ID are received. It is determined whether a direct access end notification has been issued to the DVR 20 (FIG. 22: Step S2204). If there is still a service URN that should be notified of the end of direct access, specify only the service URN and send a direct access end notification <C-3> to which the URI for direct access is not specified to the DVR 20 ( FIG. 22: Step S2205) When all the end notifications are issued, the process waits for the direct access end notification <C-2> from the service server 30.

  When the DVR 20 receives a direct access end notification <C-3> without a direct access URI specified from the direct access management server 40 (FIG. 23: Step S2303), the DVR 20 is specified by the direct access end notification <C-3>. All the ports related to the service URN being closed are closed (FIG. 23: steps S2304 and S2305).

  By executing the above processing, the direct access is terminated by the service server 30, the direct access management server 40, and the DVR 20.

  In the above embodiment, the method in which the service server 30 acquires the controlled device registration password that is a one-time password from the direct access management server 40 in response to a request from the mobile phone 10 has been described. The DVR 20 (controlled device) may acquire the controlled device registration password, which is a one-time password, from the direct access management server 40.

(Second Embodiment of the Invention)

  Next, a second embodiment of the present invention will be described.

  In the above embodiment, the method in which the service server 30 acquires the controlled device registration password that is a one-time password from the direct access management server 40 in response to a request from the mobile phone 10 has been described. The DVR 20 (controlled device) acquires the controlled device registration password, which is a one-time password, from the direct access management server 40.

  FIG. 26 is a sequence diagram showing the flow of information when registering the combination of the mobile phone 10 and the service and registering the DVR 20 in the second embodiment. FIG. 27 is a flowchart of processing executed by the mobile phone 10 at the time of registration. FIG. 28 is a flowchart of processing executed by the service server 30 at the time of registration. 29 and 30 are flowcharts of processing executed by the direct access management server 40 during registration. FIG. 31 is a flowchart of processing executed by the DVR 20 at the time of registration.

  First, in the DVR 20, an instruction for preparing for device registration of the DVR 20 is given from the user by selecting from a menu displayed on the screen of the TV connected to the DVR 20 (FIG. 31: step S3101). At this time, since the DVR 20 is not registered in the direct access management server 40, the value of the automatic connection flag held in the DVR 20 is off (FIG. 31: step S3102). Therefore, the DVR 20 starts processing for registering itself in the direct access management server 40.

  In order to register itself with the direct access management server 40, the DVR 20 sends a device authentication request <R-20> including the authentication method information and device authentication information set in advance to the direct access management server 40. The data is transmitted to the SOAP server 42 (FIG. 31: Step S3103).

  When the SOAP server 42 in the direct access management server 40 receives the device authentication request <R-20> from the DVR 20 (FIG. 29: Step S2901), it determines whether or not this DVR 20 is a valid device < It is determined based on the authentication method information and device authentication information included in R-20> (FIG. 29: step S2902). If it is determined as an unauthorized device, the SOAP server 42 transmits a code indicating an error to the DVR 20 as a device authentication response <R-20R> (FIG. 29: step S2906). If it is determined as a valid device, the SOAP server 42 generates a device authentication continuation ID to be assigned to the DVR 20 (FIG. 29: step S2903), and this device authentication continuation ID and this device authentication continuation ID Are associated with the device authentication information of the DVR 20 and stored in the storage unit 41 (FIG. 29: step S2904). Thereafter, the SOAP server 42 transmits information including the generated device authentication continuation ID and the information on the expiration date to the DVR 20 as a device authentication response <R-20R> (FIG. 29: step S2905).

  When the DVR 20 receives a code indicating an error as the device authentication response <R-20R> from the SOAP server 42 in the direct access management server 40, the DVR 20 displays an error message indicating that the DVR 20 is not a valid device. When the DVR 20 receives information including the device authentication continuation ID and information on its expiration date as the device authentication response <R-20R> (FIG. 31: step S3104), it is included in this device authentication response R-20R> The device authentication continuation ID and its expiration date information are stored in the storage unit 21 in association with the device authentication information (FIG. 31: step S3105). Thereafter, the DVR 20 proceeds to a controlled device registration password acquisition process for registering itself as a control target of the mobile phone 10.

  On the other hand, when an instruction for device registration of the DVR 20 is given from the user to the DVR 20, if the value of the automatic connection flag is ON in step S3102, at least once before the direct access management server 40 The device authentication procedure (steps S3103 to S3105), the controlled device registration password acquisition procedure (steps S3106 to S3109), and the registration procedure (steps S3110 to S3114) are executed. Therefore, the DVR 20 has already completed device authentication and device registration with the direct access management server 40, and has already received a device authentication continuation ID from the direct access management server 40. For this reason, the DVR 20 omits the procedure for device authentication from step S3103 to step S3105, and associates a new control device with the DVR 20 using the device authentication continuation ID acquired from the direct access management server 40. The process proceeds to the controlled device registration password acquisition process.

  Next, a process for registering the mobile phone 10 as a control device and associating the mobile phone 10 as a control device of the DVR 20 will be described.

  First, the DVR 20 executes a process for acquiring a password for registering the DVR 20 as the controlled device in the direct access management server 40 as a control target of the mobile phone 10 as the control device.

  The DVR 20 transmits a controlled device registration password acquisition request <R-21> including the device authentication continuation ID acquired from the direct access management server 40 and information on its expiration date to the direct access management server 40 (FIG. 31: Step S3106).

  Upon receiving the controlled device registration password acquisition request <R-21> from the DVR 20 (FIG. 29: Step S2907), the direct access management server 40 is included in the controlled device registration password acquisition request <R-21>. The device authentication continuation ID and its expiration date are checked (FIG. 29: step S2908). If NG is determined in this check, that is, the device authentication continuation ID included in the controlled device registration password acquisition request <R-21> is associated with the device authentication information in the storage unit 41 of the direct access management server 40. If the device authentication continuation ID does not match or the device authentication continuation ID has expired, the controlled device registration password including an error code indicating that device authentication is required is obtained. A response <R-21R> is transmitted to the DVR 20 (FIG. 29: step S2909).

  When the DVR 20 receives the controlled device registration password acquisition response <R-21R> including the error code (FIG. 31: step S3107), the process returns to step S3103, and the authentication method information and device set in advance in itself The device authentication request <R-20> including the authentication information is transmitted again to the SOAP server 42 in the direct access management server 40 (FIG. 31: step S3103). As a result, the DVR 20 again performs device authentication with the direct access management server 40 and performs a procedure for updating to a device authentication continuation ID having a new expiration date.

  In addition, when the result of the device authentication continuation ID and its expiration date check by the direct access management server 40 (FIG. 29: step S2908) is OK, that is, included in the controlled device registration password acquisition request <R-21>. If the device authentication continuation ID matches the device authentication continuation ID stored in the storage unit 41 of the direct access management server 40 in association with the device authentication information, and the device authentication continuation ID has not expired, The access management server 40 generates a controlled device registration password (FIG. 29: Step S2910), and stores the generated controlled device registration password in the storage unit 41 in association with the device authentication continuation ID (FIG. 29). : Step S2911). Thereafter, the direct access management server 40 transmits the generated controlled device registration password and information on its expiration date to the DVR 20 as a controlled device registration password acquisition response <R-21R> (FIG. 29: step S2912). .

  When the DVR 20 receives the controlled device registration password acquisition response <R-21R> including the controlled device registration password and the expiration date information from the direct access management server 40 (FIG. 31: step S3108), the mobile phone 10 In order to pass this controlled device registration password and its expiration date information <R-22>, for example, a two-dimensional barcode such as QR code (trademark) is generated internally and the TV screen connected to the DVR 20 (FIG. 31: Step S3109).

  On the other hand, upon receiving a controlled device registration instruction from the user (FIG. 27: Step S2701), the mobile phone 10 acquires a controlled device registration password and its expiration date information <R-22> from the DVR 20 Execute. For example, the mobile phone 10 captures a two-dimensional barcode such as a QR code (trademark) displayed on a TV screen connected to the DVR 20 with a camera equipped in the mobile phone 10 and images the captured barcode. By recognizing, the controlled device registration password and expiration date information <R-22> are acquired (FIG. 27: step S2702).

  Next, the mobile phone 10 executes processing for causing the direct access management server 40 to associate the mobile phone 10 that is the control device and the DVR 20 that is the controlled device.

  The mobile phone 10 transmits a controlled device registration request <R-23> including the acquired controlled device registration password and user identification information registered in advance to the mobile phone 10 to the service server 30 (FIG. 27). : Step S2703).

  When the service server 30 receives the controlled device registration request <R-23> including the controlled device registration password and user identification information from the mobile phone 10 (FIG. 28: Step S2801), the controlled device registration request It is determined whether the control device / service management ID corresponding to the user identification information included in <R-23> is stored in the storage unit 31 of the service server 30 (FIG. 28: Step S2802).

  If the control device / service management ID corresponding to the user identification information is not stored in the storage unit 31 of the service server 30, the service server 30 determines the user identification included in the controlled device registration request <R-23>. The information is stored in the storage unit 31 (FIG. 28: Step S2803), and the control device / service management ID acquisition request <R-34> including the Service ID assigned to itself is sent to the SOAP server 42 in the direct access management server 40. (FIG. 28: Step S2804). That is, since the mobile phone 10 is in a state of using the service provided by the service server 30 for the first time, the service server 30 is used for processing with the direct access management server 40 when a service request from the mobile phone 10 is made thereafter. The direct access management server 40 is requested to issue a control device / service management ID for uniquely identifying a combination of the mobile phone 10 that is the control device and the service provided by the service server 30. Here, the control device / service management ID is an ID uniquely assigned to a combination of an individual service provided by a service provider and a control device.

  When the SOAP server 42 in the direct access management server 40 receives the control device / service management ID acquisition request <R-34> (FIG. 30: step S3001), this control device / service management ID acquisition request <R-34> It is checked whether the ServiceID included in is stored in the storage unit 41 of the direct access management server 40 (FIG. 30: step S3002). If the ServiceID included in the control device / service management ID acquisition request <R-34> is not stored in the storage unit 41, the service provider's service authorized by the direct access management server 40 by the service server 30 Since it is not a server, an error code indicating that ServiceID is not registered is transmitted as a control device / service management ID acquisition response <R-34R> (FIG. 30: step S3006). When the ServiceID is stored in the storage unit 41, the SOAP server 42 issues a new control device / service management ID (FIG. 30: Step S3003), and the control device / service management ID and ServiceID The correspondence relationship is registered in the storage unit 41 (FIG. 30: step S3004), and the control device / service management ID is transmitted to the service server 30 as a control device / service management ID acquisition response <R-34R> (FIG. 30: step). S3005). By storing the control device / service management ID and the Service ID in association with each other in this way, the direct access management server 40 uniquely identifies the combination of the mobile phone 10 that requested the service provision and the service server 30 in the subsequent service provision. Can be identified.

  When the service server 30 receives the control device / service management ID acquisition response <R-34R> including the control device / service management ID from the direct access management server 40 (FIG. 28: Step S2805), the control device / service management The ID is registered in the storage unit 31 in association with the user identification information of the mobile phone 10 (FIG. 28: Step S2806).

  The service server 30 associates the control device / service management ID with the user identification information in the storage unit 31, or the user identification included in the controlled device registration request <R-23> received from the mobile phone 10 If the control device / service management ID corresponding to the information has already been registered in the storage unit 31, the control device / service management ID and ServiceID, and the controlled device registration password acquired from the mobile phone 10 in step S2801 are included. The controlled device registration request <R-25> is transmitted to the SOAP server 42 in the direct access management server 40 (FIG. 28: step S2807). Accordingly, the service server 30 is a combination of the DVR 20 that is the controlled device specified by the controlled device registration password transmitted from the mobile phone 10 and the service of the mobile phone 10 that is the control device and the service server 30. The direct access management server 40 is requested to associate with the control device / service management ID that identifies the ID.

  When the SOAP server 42 in the direct access management server 40 receives the controlled device registration request <R-25> from the service server 30 (FIG. 30: step S3007), the control device / service management ID and It is determined whether or not a combination of ServiceIDs is registered in the storage unit 41 (FIG. 30: Step S3008). If the combination is not registered in the storage unit 41, the SOAP server 42 sets an error code indicating that the combination of the control device / service management ID and Service ID is unregistered as a controlled device registration response <R-25R>. The data is transmitted to the service server 30 (FIG. 30: Step S3013).

  If the combination of the control device / service management ID and ServiceID included in the controlled device registration request <R-25> has already been registered in the storage unit 41, the SOAP server 42 validates the controlled device registration password and valid The time limit is checked (FIG. 30: Step S3009). As a result of this check, if the password that matches the controlled device registration password acquired from the service server 30 is not stored in the storage unit 41 or if the expiration date has expired, the SOAP server 42 registers the controlled device. An error code indicating that the controlled device registration password included in the request <R-25> is invalid is transmitted to the service server 30 as a controlled device registration response <R-25R> (FIG. 30: Step S3013). ).

  When the service server 30 receives a controlled device registration response <R-25R> containing an error code indicating that it is not registered or an error code indicating that the controlled device registration password is invalid from the SOAP server 42 (FIG. 28: Step S2808), an error code indicating that an error has occurred in the controlled device registration process is transmitted to the mobile phone 10 as a controlled device registration response <R-26> (FIG. 28: Step S2809). ).

  If the controlled device registration password acquired from the service server 30 is stored in the storage unit 41 as a result of the check in step S3009 and the expiration date has not expired, the SOAP server 42 stores the storage unit in step S2911. 41, the device authentication continuation ID corresponding to the controlled device registration password acquired from the service server 30 is searched from the association between the controlled device registration password and the device authentication continuation ID stored in 41, and the device authentication continuation ID of the search result is retrieved. It is determined whether or not the controlled device management ID associated with is already assigned (FIG. 30: step S3010-1). When the controlled device management ID is not assigned, the SOAP server 42 issues a new controlled device management ID (FIG. 30: step S3010-2). Thereafter, the Service ID, the control device / service management ID corresponding to the device authentication continuation ID, and the newly assigned controlled device management ID are stored in the storage unit 41 in association with each other (FIG. 30: Step S3011). In step S3010-1, if the controlled device management ID associated with the device authentication continuation ID has already been assigned, the SOAP server 42 continues the controlled device management ID already assigned and the device authentication continuation. The Service ID corresponding to the ID and the control device / service management ID are stored in the storage unit 41 in association with each other.

  The controlled device management ID is identification information uniquely assigned to the controlled device in the direct access management server 40. As a result, the control device / service management ID assigned to the combination of the control device and the service is associated with the controlled device management ID assigned to the controlled device. In this connection, even if multiple controlled device management IDs are linked to one controlled device / service management ID, multiple controlled devices / service management IDs are linked to one controlled device management ID. It may be attached.

  Thereafter, the SOAP server 42 transmits a controlled device registration response <R-25R> indicating that registration of the controlled device is completed to the service server 30 (FIG. 30: step S3012). Furthermore, if the service server 30 receives a controlled device registration response <R-25R> indicating that the registration is completed from the SOAP server 42 (FIG. 28: step S2808), the registration of the controlled device is completed. A controlled device registration response <R-26> indicating this is transmitted to the mobile phone 10 (FIG. 28: step S2809).

  When the mobile phone 10 receives the controlled device registration response <R-26> from the service server 30 (FIG. 27: step S2704), the registration processing of the controlled device is terminated.

  After the above processing is completed, the user is connected to the DVR 20 with an instruction to check whether the association between the controlled device management ID assigned to the DVR 20 and the control device / service management ID is completed. This is given to the DVR 20 by selecting a menu displayed on the TV screen (FIG. 31: Step S3110).

  Upon receiving this confirmation instruction, the DVR 20 sends a controlled device registration confirmation request <R-27> including its own device authentication continuation ID and the controlled device registration password stored in the storage unit 21 to the direct access management server. The information is transmitted to the SOAP server 42 within 40 (FIG. 31: step S3111).

  When the SOAP server 42 receives the controlled device registration confirmation request <R-27> from the DVR 20 (FIG. 29: step S2913), the SOAP server 42 includes the DVR 20 included in the controlled device registration confirmation request <R-27>. The device authentication continuation ID and the expiration date of this device authentication continuation ID are checked (FIG. 29: step S2914).

  If the check in step S2914 is OK, that is, if the device authentication continuation ID of the DVR 20 is stored in the storage unit 41 and the expiration date has not expired, the SOAP server 42 registers the controlled device. The password expiration date is checked (FIG. 29: Step S2915). If the controlled device registration password acquired from the DVR 20 as a result of this check has expired, the SOAP server 42 uses the controlled device registration password included in the controlled device registration confirmation request <R-27>. Is sent to the DVR 20 as a controlled device registration confirmation response <R-27R> (FIG. 29: step S2920). If the controlled device registration password has not expired, the SOAP server 42 refers to the information stored in the storage unit 41 and is included in the controlled device registration confirmation request <R-27>. The controlled device management ID stored in the storage unit 41 in association with the controlled device registration password is searched, and the number of controlled device / service management IDs associated with the controlled device management ID is determined. Investigate as the number of services currently associated with DVR20.

  After checking the number of services currently associated with the DVR 20, the SOAP server 42 transmits information on the number of services to the DVR 20 as a controlled device registration confirmation response <R-27R> (FIG. 29: Step S2916). ). Next, in order to notify the service server 30 that the device registration of the controlled device DVR 20 is completed, the SOAP server 42 stores the Service ID of the service server 30 stored in the storage unit 41, and this Service ID. The controlled device registration completion notification <R-28> including the controlled device / service management ID and the controlled device registration password associated with is transmitted to the service server 30 (FIG. 29: step S2917). Then, the SOAP server 42 deletes the controlled device registration password of the DVR 20 stored in the storage unit 41 (FIG. 29: step S2918).

  Upon receiving the controlled device registration completion notification <R-28> from the SOAP server 42 (FIG. 28: Step S2810), the service server 30 notifies the mobile phone 10 that registration of the controlled device has been completed (FIG. 28). : Step S2811). Examples of a method for notifying the cellular phone 10 from the service server 30 that registration of the controlled device has been completed include, for example, e-mail and applications prepared for communicating with the cellular phone 10 by other methods. Etc.

  When the DVR 20 receives a controlled device registration confirmation response <R-27R> including information on the number of services from the SOAP server 42 (FIG. 31: Step S3112), it sets the automatic connection flag to ON (FIG. 31: Step S3113), a message indicating that the registration of the own device is completed is displayed on the screen of the TV connected to the own device (FIG. 31: Step S3114).

  Further, the SOAP server 42 determines that NG is determined in the check in step S2814, that is, the device authentication continuation ID of the DVR 20 is not stored in the storage unit 41, or the device authentication continuation ID has expired. If there is, an error code indicating an error in checking the device authentication continuation ID and the controlled device registration password is transmitted to the DVR 20 as a controlled device registration confirmation response <R-27R> (FIG. 30: step S3013). When the DVR 20 receives the error code indicating this check error as the controlled device registration confirmation response <R-27R> (Fig. 31: Step S3125), it connects a message indicating that device re-registration is required to its own device. The information is displayed on the screen of the TV that has been displayed and notified to the user (FIG. 31: step S3126). Thereafter, the operation of the DVR 20 ends.

  After the automatic connection flag is set to ON in the DVR 20 (FIG. 31: Step S3113), a message indicating that the registration of the own device is completed is displayed on the screen of the TV connected to the own device (FIG. 31: In step S3114), the DVR 20 directly sends an XMPP login information acquisition request <D-0-1> including its own device authentication continuation ID to establish a bidirectional always-on session with the XMPP server of the direct access management server 40. The data is transmitted to the SOAP server 42 in the access management server 40 (FIG. 31: Step S3115).

  In the network system of this embodiment, as in the network system of the first embodiment, the direct access management server 40 is provided with an XMPP server 43 for setting a bidirectional always-on session with the controlled device. ing. In order to access the DVR 20 that is the controlled device from the mobile phone 10 that is the controlling device, the DVR 20 logs into the XMPP server 43 and establishes a constant connection session between the DVR 20 and the XMPP server 43 before that. Thus, the service server 30 or the mobile phone 10 can acquire necessary information from the DVR 20 when necessary. In order to simplify the design of the service server 30 at this time, the network system of this embodiment also conceals the XMPP protocol in the direct access management server 40, as in the network system of the first embodiment. Information can be exchanged between the DVR 20 and the XMPP server 43 that has established a bi-directional always-on session using only the SOAP interface.

  Since the operation of the direct access management server 40 when the DVR 20 logs in to the XMPP server 43 is the same as that of the first embodiment, the following description of the second embodiment also describes the first embodiment. It is assumed that FIG. 10 used is used.

  When receiving the XMPP login information acquisition request <D-0-1> including the device authentication continuation ID from the DVR 20 (FIG. 10: Step S1001), the direct access management server 40 receives this XMPP login information acquisition request <D-0-1 The device authentication continuation ID included in> and the expiration date of the device authentication continuation ID are checked (FIG. 10: step S1002). If this check does not match the device authentication continuation ID included in the XMPP login information acquisition request <D-0-1> with that stored in the storage unit 41 of the direct access management server 40, or the expiration date If it is expired, it means that the DVR 20 is not properly registered in the direct access management server 40, or it has been registered in the past, but the device authentication continuation ID at the time of registration has expired Therefore, an error code indicating that device authentication is required is transmitted to the DVR 20 as an XMPP login information acquisition response <D-0-1R> (FIG. 10: step S1003). If the device authentication continuation ID is stored in the storage unit 41, the expiration date has not expired, and the check result in step S1002 is OK, the direct access management server 40 changes the storage unit 41 from the storage unit 41 to the device authentication continuation ID. The controlled device management ID and device authentication information associated with each other are searched (FIG. 10: Step S1004). From the controlled device management ID and device authentication information, the direct access management server 40 uses the Full JID (D), which is the XMPP login ID required for the DVR 20 to log in to the XMPP server 43, the XMPP login password, and the XMPP login password. An expiration date is generated (FIG. 10: Step S1005), and these are associated with the device authentication continuation ID and stored in the storage unit 41 (FIG. 10: Step S1006). The direct access management server 40 obtains the XMPP login information by adding the XMPP address and port number, authentication method information and SSL options to the generated Full JID (D), XMPP login password and expiration date information. A response <D-0-1R> is transmitted to the DVR 20 (FIG. 10: Step S1007).

  When the DVR 20 receives the XMPP login information acquisition response <D-0-1R> including the Full JID (D), the XMPP login password, etc. from the SOAP server 42 in the direct access management server 40 (FIG. 31: Step S3116), the XMPP In order to log in to the server 43, an XMPP login authentication request <D-0-2> including the full JID (D) and XMPP login password is transmitted to the XMPP server 43 in the direct access management server 40 (FIG. 31: step). S3117).

  When the XMPP server 43 in the direct access management server 40 receives the XMPP login authentication request <D-0-2> from the DVR 20 (FIG. 10: Step S1008), it is included in this XMPP login authentication request <D-0-2>. The full JID (D), XMPP login password, and expiration date of the XMPP login password are checked (FIG. 10: step S1009). The XMPP server 43 does not match the full JID (D) stored in the storage unit 41, or does not match the XMPP login password stored in the storage unit 41, or the XMPP login password is valid. If the time limit has expired, an error code indicating XMPP login failure is transmitted to the DVR 20 as an XMPP login authentication response <D-0-2R> (FIG. 10: step S1010). If the full JID (D), XMPP login password, and expiration date check are all OK, the XMPP server 43 in the direct access management server 40 sends a code indicating XMPP login permission to the XMPP login authentication response <D-0- 2R> is transmitted to the DVR 20 (FIG. 10: Step S1011).

  When the DVR 20 receives the error code indicating the XMPP login failure from the direct access management server 40 as the XMPP login authentication response <D-0-2R> (FIG. 31: Step S3118), the DVR 20 returns to Step S3115 to request to obtain the XMPP login information. I do. That is, since the XMPP login password may expire, XMPP login information acquisition request processing is performed again.

  In addition, when the DVR 20 receives a code indicating XMPP login permission from the direct access management server 40 as an XMPP login authentication response <D-0-2R> (FIG. 31: step S3119), the XMPP login process is completed.

  The DVR 20 receives an error code indicating that device authentication is required from the SOAP server 42 in the direct access management server 40 as an XMPP login information acquisition response <D-0-1R> (FIG. 31). : Step S3120) The device itself has not been registered in the direct access management server 40 normally, or the device authentication continuation ID may have expired. A device authentication request <R-20> including authentication method information and device authentication information is transmitted to the SOAP server 42 in the direct access management server 40 to perform device authentication again (FIG. 31: step S3121).

  When the DVR 20 receives the device authentication response <R-20R> from the SOAP server 42 in the direct access management server 40 (FIG. 31: Step S3122), the device authentication continuation ID included in this device authentication response <R-20R> Then, the expiration date information is stored in the storage unit 21 in association with the device authentication information (FIG. 31: step S3123). Thereafter, the DVR 20 moves to step S3115 and transmits again the XMPP login information acquisition request <D-0-1> including its own device authentication continuation ID to the SOAP server 42 in the direct access management server 40.

  In step S2914, the SOAP server 42 continues the device authentication in which the device authentication continuation ID of the DVR 20 included in the controlled device registration confirmation request <R-27> received in step S2913 is stored in the storage unit 41. If the ID does not match or the device authentication continuation ID has expired, an error code indicating that device authentication is required is sent to the DVR 20 as a controlled device registration confirmation response <R-27R> (FIG. 29: Step S2919).

  When the DVR 20 receives an error code indicating that device authentication is required as a controlled device registration confirmation response <R-27R> (FIG. 31: step S3124), the DVR 20 is normally registered in the direct access management server 40. Device authentication request ID including device authentication information and authentication method information set in advance again <R-20> Is transmitted to the SOAP server 42 in the direct access management server 40 to perform device authentication again (FIG. 31: step S3121).

  When the DVR 20 receives the device authentication response <R-20R> from the SOAP server 42 in the direct access management server 40 (FIG. 31: Step S3122), the device authentication continuation ID included in this device authentication response <R-20R> Then, the expiration date information is stored in the storage unit 21 in association with the device authentication information (FIG. 31: step S3123). Thereafter, the DVR 20 moves to step S3115 and transmits again the XMPP login information acquisition request <D-0-1> including its own device authentication continuation ID to the SOAP server 42 in the direct access management server 40.

  As described above, the DVR 20 (controlled device) may acquire the controlled device registration password, which is a one-time password, from the direct access management server 40.

  In addition, in order to pass the controlled device registration password and its expiration date information from the DVR 20 to the mobile phone 10, the method of capturing a two-dimensional barcode with the camera provided in the mobile phone 10 has been described. As long as the controlled device registration password and the expiration date information can be passed from the mobile phone 10 to the mobile phone 10, any method may be used. For example, the DVR20 is equipped with a contactless IC card writing device, the mobile phone 10 is equipped with an IC card reading device, and the DVR20 writes the controlled device registration password and its expiration date information to the IC card. It is also possible to configure the mobile phone 10 to read information from the IC card and transmit it via the IC card. It is also possible to configure the same configuration as devices such as antennas and IC chips provided in the IC card in the mobile phone 10 and write directly to the mobile phone 10 with the DVR20 writing device. is there. Furthermore, the mobile phone 10 and the DVR 20 are equipped with wireless communication devices such as wireless LAN, Bluetooth, and infrared communication so that the controlled device registration password and the expiration date information are transmitted via the wireless communication. It may be configured, or the mobile phone 10 and the DVR 20 may be equipped with a wired communication device such as USB and transmitted via wired communication.

  The configuration and operation of the network system according to the embodiment of the present invention have been described above. However, part of the functions of the service server 30 can be transferred to a control device. For example, by changing the access function to the SOAP interface that the service server 30 had so that the control device (cell phone 10) has, the direct access usage sequence starting from the XMPP login request is changed to the control device (cell phone 10). ) And the direct access management server 40.

  Further, the function of the control device and the function of the controlled device can be integrated. In this case, when accessing the XMPP session of the controlled device (DVR 20) from the control device (mobile phone 10), information necessary for direct access is exchanged between the XMPP sessions without going through the SOAP server 42. .

  Furthermore, direct access between controlled devices is also possible. In this case, the controlled devices are associated with each other using the control device.

  In the embodiment described above, since the service server 30 is arranged between the mobile phone 10 that is a control device and the direct access management server 40, the direct access management server 40 is connected between the mobile phone 10 and the service server 30. Although the control device / service management ID generated for the combination is stored in association with the controlled device management ID, the present invention is not limited to this. That is, the present invention can be used in an environment where direct communication is performed between the control device and the direct access management server 40 without using the service server 30. In this case, the direct access management server 40 generates a control device management ID for identifying the control device instead of the control device / service management ID in the above embodiment, and stores this in association with the controlled device management ID. To do. The control device management ID may be generated by the direct access management server 40. If the control device can publish an ID that can identify itself, the ID given by the control device May be used as the control device management ID associated with the controlled device management ID. The same applies to the controlled device management ID, and if the controlled device can disclose an ID that can identify itself, the ID given from the controlled device is controlled by the controlled device management ID. It may be used as a controlled device management ID associated with the ID. In addition, the devices connected to the direct access management server 40 as control devices and controlled devices may each have both a portion that controls other devices and a portion that is controlled by other devices. .

(Concept of the present invention)
FIG. 33 conceptually illustrates the features of the present invention. The server device 140 according to the present invention is connected to the first device 110 and the second device 120 through a network. The server device 140 includes a storage unit 141 that stores information. The storage unit 141 corresponds to the storage unit 41 of the above embodiment. The server device 140 generates a first password in response to a password issuance request including the first identification information related to the first device 110 from the first device 110, and relates to the first device 110. The first password is stored in the storage unit 141 in association with the first identification information, and the generated first password is transmitted to the first device 110. Here, each of the first device 110 and the second device 120 is a device having both a part that controls other devices and a part that is controlled by other devices.

  The first device 110 transfers the first password acquired from the server device 140 to the second device 120, and the second device 120 holds this as the second password. When the second device 120 requests the server device 140 to register its own device, the second device 120 transmits a second password and second identification information related to the second device 120 to the server device 140. The server device 140 verifies whether or not the second password received from the second device 120 is stored in the storage unit 141, and when the second password is stored in the storage unit 141, the second password is stored. The second identification information related to the device 120 is registered in the storage unit 141 in association with the first identification information associated with the same first password as the second password. Thereby, in the server device 140, the association between the first identification information of the first device 110 and the second identification information of the second device 120, that is, between the controlling device and the controlled device. Association is achieved.

  The first identification information related to the first device 110 stored in the storage unit 141 of the server device 140 may be generated by the server device 140 or may be provided from the first device 110. It may be device identification information. The second identification information related to the second device 120 stored in the storage unit 141 of the server device 140 may also be generated by the server device 140, or the own device provided from the second device 120 May be the identification information.

  FIG. 34 shows a modification of the server device according to the present invention shown in FIG. In this modification, the server device 240 is connected to the control device 210 and the controlled device 220 through a network. The server device 240 generates a first password in response to a password issuance request including the first identification information related to the control device 210 from the control device 210, and the first identification information related to the control device 210 The first password is stored in the storage unit 241 in association with it, and the generated first password is transmitted to the control device 210.

  The control device 210 transfers the first password acquired from the server device 240 to the second device 220, and the controlled device 220 holds this as the second password. When the controlled device 220 requests the server device 240 to register its own device, the controlled device 220 transmits a second password and second identification information related to the controlled device 220 to the server device 240. The server device 240 verifies whether or not the second password received from the controlled device 220 is stored in the storage unit 241, and when the second password is stored in the storage unit 241, the controlled device The second identification information related to 220 is registered in the storage unit 241 in association with the first identification information associated with the same first password as the second password. Thereby, in the server apparatus 240, the association between the first identification information of the control device 210 and the second identification information of the controlled device 220 is achieved.

  The first identification information related to the control device 210 stored in the storage unit 241 of the server device 240 may be generated by the server device 240, or the identification information of the own device provided from the control device 210 It may be. The second identification information related to the controlled device 220 stored in the storage unit 241 of the server device 240 may also be generated by the server device 240, or the identification of the own device provided from the controlled device 220 It may be information.

  FIG. 35 shows another modification of the server device according to the present invention shown in FIG. In this modification, the server device 340 is connected to the control device 310 and the controlled device 320 through the network in the same manner as the server device 240 shown in FIG. However, in this example, the server device 340 generates a first password in response to a password issuance request including the first identification information related to the controlled device 320 from the controlled device 320, and the controlled device 320 The first password is stored in the storage unit 341 in association with the first identification information related to, and the first password is transmitted to the controlled device 320.

  The controlled device 320 transfers the first password acquired from the server device 340 to the control device 310, and the control device 310 holds this as the second password. When the control device 310 requests the server device 340 to register its own device, the control device 310 transmits a second password and second identification information related to the control device 310 to the server device 340. The server device 340 verifies whether or not the second password received from the control device 310 is stored in the storage unit 341. When the second password is stored in the storage unit 341, the server device 340 The related second identification information is registered in the storage unit 341 in association with the first identification information associated with the same first password as the second password. Thereby, in the server device 340, the association between the first identification information of the controlled device 320 and the second identification information of the control device 310 is achieved.

  Note that the first identification information related to the controlled device 320 stored in the storage unit 341 of the server device 340 may be generated by the server device 340 or the own device provided from the controlled device 320. It may be identification information. The second identification information related to the control device 310 stored in the storage unit 341 of the server device 340 may also be generated by the server device 340, or the identification information of the own device provided from the control device 310. It may be.

  FIG. 36 shows still another modification of the present invention shown in FIG. In this modification, the control device 410 is connected to the server device 440 via the service server 430. Server device 440 is connected to service server 430 and controlled device 420 via a network. The service server 430 is a server that provides various services for accessing the controlled device 420 via the network to the control device 410 such as a mobile phone. Therefore, this modification corresponds to the first and second embodiments described above.

  The server device 440 generates a first password in response to a password issuance request sent from the control device 410 through the service server 430, and associates the service server 430 with the first identification information related to the control device 410. The first password is stored in the storage unit 441, and the first password is transmitted to the control device 410 through the service server 430. The control device 410 transfers the first password acquired from the server device 440 through the service server 430 to the controlled device 420, and the controlled device 420 holds this as the second password.

  When the controlled device 420 requests the server device 440 to register its own device, the controlled device 420 transmits a second password and second identification information related to the controlled device 420 to the server device 440. The server device 440 verifies whether or not the second password received from the controlled device 420 is stored in the storage unit 441, and when the second password is stored in the storage unit 441, the controlled device The second identification information related to 420 is registered in the storage unit 441 in association with the first identification information associated with the same first password as the second password. Thereby, in the server device 440, the association between the first identification information of the control device 410 and the second identification information of the controlled device 420 is achieved.

  It should be noted that the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the present invention.

1 is a diagram showing an overall configuration of a network system according to an embodiment of the present invention. FIG. 2 is a sequence diagram showing a flow of information when registering a combination of a control device and a service and registering a controlled device in the network system of FIG. 3 is a flowchart showing the operation of a control device at the time of registration in FIG. 3 is a flowchart showing the operation of the service server at the time of registration in FIG. 3 is a flowchart showing the operation of the direct access management server at the time of registration in FIG. 3 is a flowchart showing an operation of the DVR at the time of registration in FIG. FIG. 2 is a sequence diagram showing a flow of information at the time of XMPP login and remote recording reservation of a controlled device in the network system of FIG. It is a flowchart which shows operation | movement of the mobile telephone regarding a remote recording reservation. It is a flowchart which shows operation | movement of the service server regarding a remote recording reservation. It is a flowchart which shows operation | movement of the direct access management server regarding XMPP login of a controlled apparatus, remote recording reservation, and content acquisition. It is a flowchart which shows operation | movement of the direct access management server regarding remote recording reservation and content acquisition. It is a flowchart which shows operation | movement of DVR regarding a remote recording reservation and content acquisition. FIG. 2 is a sequence diagram showing a flow of information when performing remote recording reservation directly from a mobile phone in the network system of FIG. FIG. 2 is a sequence diagram showing a flow of information when performing remote recording reservation for tunneling from a mobile phone in the network system of FIG. FIG. 2 is a sequence diagram showing a flow of information at the time of content acquisition by direct access from a mobile phone in the network system of FIG. It is a sequence diagram which shows the flow of the information at the time of the content acquisition by the direct access from a service server. It is a flowchart which shows operation | movement of the mobile telephone at the time of content acquisition. It is a flowchart which shows operation | movement of the service server at the time of content acquisition. It is a flowchart which shows operation | movement of the service server at the time of content acquisition. FIG. 2 is a sequence diagram showing a flow of information at the end of direct access in the network system of FIG. It is a flowchart which shows operation | movement of the service server at the time of completion | finish of direct access. It is a flowchart which shows operation | movement of the direct access management server at the time of completion | finish of direct access. It is a flowchart which shows operation | movement of DVR at the time of completion | finish of direct access. It is a figure which shows the structure of Full JID. It is a figure which shows another structure of Full JID. It is a sequence diagram which shows the flow of the information at the time of performing registration of the combination of a mobile telephone and a service in the network system of 2nd Embodiment, and registration of DVR. 27 is a flowchart showing an operation of the mobile phone at the time of registration in FIG. 27 is a flowchart showing the operation of the service server at the time of registration in FIG. 27 is a flowchart of the direct access management server at the time of registration in FIG. 27 is a flowchart showing the operation of the direct access management server at the time of registration in FIG. 27 is a flowchart showing an operation of the DVR at the time of registration in FIG. It is a sequence diagram which shows the flow of information in the case of performing remote recording reservation of tunneling from a mobile phone without going through a service server. It is a figure which shows the characteristic of this invention notionally. It is a figure which shows the modification of the server apparatus concerning this invention. It is a figure which shows another modification of the server apparatus concerning this invention. It is a figure which shows another modification of the server apparatus concerning this invention.

Explanation of symbols

10 Mobile phone (control device)
11 Memory
20 DVR (controlled device)
21 Memory
30 Service server
31 Memory
40 Direct access management server
41 Memory
42 SOAP server
43 XMPP server
50 routers

Claims (16)

A server device that performs processing of registering a first device and a second device connected via a network in association with each other,
Storage means for storing information;
A first password is generated in response to a password issuance request from the first device, and the first password is stored in the storage unit in association with first identification information related to the first device. First processing means for transmitting the first password to the first device;
The second receiving a second password transmitted from the device, checks whether the second password this received is stored in the storage means, said second password stored in said storage means And second processing means for storing second identification information related to the second device in the storage means in association with the first identification information. The server device according to claim 1,
The first processing unit generates the first identification information related to the first device, associates the generated first identification information with the first password, and stores the first identification information in the storage unit. Remember. The server device according to claim 2,
The first device is connected to the server device via a service server device that provides a service to the first device;
The first processing means generates identification information related to the first device and the service server device as the first identification information. The server device according to claim 3,
The first processing means generates identification information for a combination of the first device and a service provided by the service server device as the first identification information. The server device according to claim 1,
Device authentication processing for authenticating the validity of the second device is executed, authentication identification information associated with authentication information necessary for authentication of the second device is generated, and the generated authentication identification information is used as the second authentication information. Further comprising means for transmitting to
The second processing means stores the authentication identification information in the storage means in association with the first identification information as the second identification information. The server device according to claim 1,
The first processing means sets an expiration date for the generated first password,
The second processing means checks the expiration date, and if the expiration date has expired, does not perform a process of associating the second identification information with the first identification information. The server device according to claim 6, wherein
The first processing means transmits the generated first password and information on an expiration date set in the first password to the first device. The server device according to claim 1,
The server device associates a plurality of the second identification information with the first identification information. The server device according to claim 1,
The server device associates the second identification information with a plurality of the first identification information. The server apparatus according to claim 1,
The second processing means erases the first password stored in the storage means when storing the second identification information in association with the first identification information. The server apparatus according to claim 1,
Based on the association between the first identification information and the second identification information stored in the storage means, a list of the second identification information associated with the first identification information is generated. And a means for transmitting to the first device. The server apparatus according to claim 1,
When a request to the second device is received from the first device, information related to the first device is associated with the first identification information and the second identification information is stored in the storage unit. It is determined whether the first identification information is stored, and if the first identification information is not stored in association with the second identification information, an error is transmitted to the first device. The server apparatus according to claim 1,
When a request to the second device is received from the first device, information related to the first device is associated with the first identification information and the second identification information is stored in the storage unit. It is determined whether the first identification information is stored, and if the first identification information is stored in association with the second identification information, a request from the first device is transmitted to the second device. . A method for registering a first device connected to a network and a second device in association with a server device,
The server device
The first processing means generates a first password in response to a password issuance request from the first device, and associates the first password with the first identification information related to the first device. Storing in a storage means, and transmitting the first password to the first device;
The second processing means receives the second password transmitted from the second device, confirms whether or not the received second password is stored in the storage means, and the second password is Storing the second identification information related to the second device in association with the first identification information when stored in the storage means. A program that causes a computer having a storage unit to function as a server device that performs processing of associating and storing a first device and a second device connected via a network,
The program is
The computer generates a first password in response to a password issuance request from the first device, and stores the first password in association with first identification information related to the first device. A first processing unit for storing the first password and transmitting the first password to the first device;
Causing the computer to receive a second password transmitted from the second device, to verify whether the received second password is stored in the storage unit, and to store the second password in the storage unit. And a second processing unit that stores second identification information related to the second device in the storage unit in association with the first identification information. A recording medium recorded with a program that causes a computer having a storage unit to function as a server device that performs processing of associating and storing a first device and a second device connected via a network,
The program is
The computer generates a first password in response to a password issuance request from the first device, and stores the first password in association with first identification information related to the first device. A first processing unit for storing the first password and transmitting the first password to the first device;
Causing the computer to receive a second password transmitted from the second device, to verify whether the received second password is stored in the storage unit, and to store the second password in the storage unit. And a second processing unit that stores second identification information related to the second device in the storage unit in association with the first identification information.

Images