JP2006252214A - Client or controller with automatic network connecting function and network connecting program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a client and controller with automatic network connecting function, which can be automatically reconnected to the same server in such a case that the client is disconnected from a network by any cause in a client server system. <P>SOLUTION: The client with automatic network connecting function searches a first server, when disconnected from the first server and connected to a second server different from the first server, and executes reconnection with the first server if the first server can be found. The controller with automatic network connecting function monitors and/or controls the client, searches the second server the client is connected with when the client is disconnected from the first server and connected to the second server different from the first server, and connects the client to the same server if the second server can be found. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a client and a controller with an automatic network connection function, and more particularly, in a client-server system, when a connection between a client and a server is disconnected for some reason, the client and the controller may connect to the same server again. The present invention relates to a client and a controller with an automatic network connection function.

  Currently, content distribution using a client server system on a network is performed. If the connection between the client and the server is disconnected due to a server malfunction or the like during content distribution, the client cannot receive the interrupted content distribution unless the connection with the server is restored. Therefore, even if the client is provided with an automatic connection recovery function and the connection with the server is disconnected, the connection to another server on the network is connected, so that a quick connection recovery to the network is achieved. If the highest priority is to be played back by the client, it is very advantageous to have the automatic connection recovery function. However, as shown in FIG. 1, a plurality of servers SV storing a plurality of music data, a plurality of audio clients CL, and a plurality of controllers CN are provided, which are mutually connected by a LAN (local area network) 101. In a client server system such as the connected network audio system 100, in order to control (monitor and / or control) the client CL1 from the controller CN1, each needs to be connected to the same server SV1. This is because the controller CN1 controls the client CL1 via the server SV1. Therefore, the client CL1 is disconnected from the server SV1 for some reason, the client CL1 is connected to another server SV2 by the automatic connection recovery function, and the network NW1 is outside the monitoring / control range of the controller CN1. When moved, the controller CN1 cannot control the client CL1 connected to the server SV2.

WO 03/102919

  The present invention has been made in order to solve the above-described conventional problems. The object of the present invention is to automatically connect a client and a controller in a client-server system when the client is disconnected from the network for some reason. It is another object to provide a client and a controller with an automatic network connection function that can connect to the same server again.

  The client with an automatic network connection function according to a preferred embodiment of the present invention disconnects the connection means connected to at least one of the plurality of servers and the first server, and the connection means is the first server. Search means for searching for the first server when connected to a different second server, and when the search means finds the first server, the connection means is connected to the first server. Reconnect.

  Even if the connection between the client and the server is lost due to some reason and the client is connected to the second server (that is, when the client moves to a network outside the monitoring / control range from the controller), the automatic network connection function The client searches for the first server connected before disconnection and reconnects. As a result, even when the client moves to a network outside the monitoring / control range from the controller, the client can quickly restore the connection state with the server by itself, and the monitoring / control from the same controller again. It becomes possible.

  In a further preferred embodiment, the client further comprises server connection history means for registering server specifying information of the first server, and server list registration means for registering server specifying information of the currently operating server in the server list. The searching means determines whether or not the server specifying information of the first server exists in the server list.

  The client registers the server identification information of the first server before the connection is cut off as the server connection history, searches for the server by broadcast, and registers the server identification information of the currently operating server in the server list. To do. Then, it is possible to determine whether or not the first server has been restored by searching for server specifying information that matches the server connection history in the server list. Therefore, even when the client is connected to another server, the first server can be quickly reconnected to the first server after recovery.

  A controller with an automatic network connection function according to another preferred embodiment of the present invention comprises a connection means for connecting to at least one of a plurality of servers, a monitoring / control means for monitoring and / or controlling a client, Search means for searching for the second server to which the client is connected when the connection to the server is disconnected and the second server is connected to a second server different from the first server. Finds the second server, the connection means connects to the same server as the client.

  Even if the connection between the client and the server is broken for some reason and the client is connected to another server, the controller and the client are the same when searching for and finding the server to which the client is connected. Connect to the server. As a result, even if the client moves to a network outside the monitoring / control range from the controller, the client and the controller can quickly connect to the same server, and monitor and / or control the client from the same controller again. Can do.

  In a further preferred embodiment, the controller includes a client monitoring / control history means for registering client specifying information of the client that has been monitored and / or controlled, and a client list including client specifying information of the client connected to the server. Client list receiving means for receiving from the server, and the search means determines whether or not the client specifying information of the client exists in the client list.

  The controller registers the client specific information of the client to be monitored and / or controlled as a client monitoring / control history. Further, the server is searched by broadcasting to search for an operating server, and the servers that are found are sequentially connected to obtain a client list from the server. Then, by searching for client identification information that matches the client monitoring / control history in the client list, it is possible to search for a server to which a client to be monitored and / or controlled is connected. Therefore, even when the client is connected to another server, it is possible to quickly find another server to which the client is connected.

  In a further preferred embodiment, the controller further comprises means for reconnecting the client to the first server when the search means discovers the second server to which the client is connected.

  When the controller returns the client connected to the second server to the first server, the controller and the client can connect to the same server. Accordingly, it becomes possible to monitor and / or control the client again from the same controller as before disconnection. It is possible to avoid a situation in which content reproduction cannot be continued by connecting to the second server, such as when the second server does not have the same music data and video data as the first server.

  In a further preferred embodiment, the controller further comprises means for connecting to the second server when the searching means discovers the second server to which the client is connected.

  Since the controller connects to the server to which the client is connected, the controller and the client can connect to the same server. When there is content to be reproduced on the second server, it is not necessary to connect the client to the first server, and the controller only connects to the server to which the client to be monitored and / or controlled is connected. You can return to the original connection state.

  In another aspect of the present invention, a client program is provided. This program is a client program for executing a client that can be connected to at least one of a plurality of servers, and when the connection to one of the plurality of servers is disconnected from the first server. And connecting to a second server different from the first server, searching for the first server, and when the first server is found in the searching step, Re-connecting to the first server.

  By installing the client program of the present invention in the computer, even if the connection between the client and the first server is cut off due to some cause and the client is connected to the second server, the client is connected before disconnection by the search step. The first server that has been searched is searched. If the first server can be found in the searching step, the client reconnects to the first server by reconnecting to the first server. As a result, even if the client moves to a network outside the monitoring / control range from the controller, the client can quickly restore the connection state with the server, and the same controller as before the connection is disconnected. The client can be monitored and / or controlled again.

  In yet another aspect, a controller program is provided. A client program for executing a controller connectable to at least one of a plurality of servers, the step of connecting to any of the plurality of servers, a monitoring / controlling step of monitoring and / or controlling the client, A search step for searching for a second server to which the client is connected when the connection with the first server is disconnected and a second server different from the first server is connected; When the second server is found in the step, the computer is caused to execute the step of connecting to the same server as the client.

  By installing the controller program of the present invention in the computer, even if the connection between the client and the server is cut for some reason and the client is connected to another server, the controller is connected to the client by the search step. Search for existing servers. If the client can be found in the search step, the controller and the client connect to the same server in the connection step. As a result, even if the client moves to a network outside the control range from the controller, the client and the controller can quickly connect to the same server, and monitor and re-monitor the client from the same controller before the connection is disconnected. And / or can be controlled.

  According to the present invention, even when the client is disconnected from the network for some reason and the client is connected to another server, the client and the controller can be quickly connected without giving the user a sense of incongruity in terms of operation. It is possible to provide a client server system that can automatically connect to the same server again.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings, taking a network content reproduction system as an example. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof is incorporated.

[Overall configuration of networked content playback system]
FIG. 1 is a block diagram illustrating a network type content playback system 100 according to a preferred embodiment of the present invention. The network type content reproduction system 100 includes a plurality of servers SV (in this example, two servers SV1, SV2) that store a plurality of contents (for example, music data) and one or a plurality of audio clients CL (in this example, Three audio clients CL1 to CL3) and one or a plurality of controllers CN (two controllers CN1 and CN2 in this example). The server SV, audio client CL, and controller CN are connected to each other via a network such as a LAN (local area network) 101.

  In this example, the network NW1 includes a server SV1, an audio client CL1 and an audio client CL2 connected to the server SV1, and a controller CN1. The controller CN1 issues a playback instruction to the audio clients (CL1 and CL2) via the server SV1 (this is called control). The audio clients (CL1 and CL2) acquire the content stored in the server SV1 from the server SV1 and reproduce it according to an instruction from the controller CN1 (or spontaneously). The audio clients (CL1 and CL2) transmit their own information (status, etc.) to the server SV1, and the controller CN1 acquires the information of the audio clients (CL1 and CL2) from the server SV1 and displays it on the display device (this). Is called monitoring). In this way, the network NW1 is configured around the server SV1.

  The network NW2 includes a server SV2, an audio client CL3 connected to the server SV2, and a controller CN2. Also in the network NW2, the server SV2, the audio client CL3, and the controller CN2 can operate in the same manner as the network NW1.

  Next, the hardware structure of the server SV will be described in detail with reference to the drawings. FIG. 2 is a block diagram showing a hardware configuration of the server SV according to a preferred embodiment of the present invention. The server SV includes a storage device (for example, a hard disk drive) 205 for accumulating contents (for example, compressed digital music data), a CPU processing unit 201 including a database management unit 202 and a network protocol processing unit 203, and the server SV. And a LAN controller 204 that transmits and receives signals between the LAN 101 and the LAN 101. The storage device 205 stores content data.

Table 1 below is a client list stored in the storage device 205.

  In the client list, information (client specific information) related to clients connected to the server SV is registered. The controller CN can know the audio client CL currently connected to the server SV by acquiring the client list from the server SV. Here, the client specifying information includes a client name and a solid identifier assigned to each client. The client name is an identifier including a character string that can be freely changed by the user. Further, an IP address and a port number may be used for the client specifying information.

  Next, the hardware structure of the audio client CL will be described in detail with reference to the drawings. FIG. 3 is a block diagram showing a hardware configuration of the audio client CL according to the preferred embodiment of the present invention. The audio client CL temporarily stores a microcomputer processing unit 301 including a network protocol processing unit 303 and a system operation unit 302, a flash memory 306, and sequentially input content data (compressed digital music data in this example). A memory 305 that sequentially outputs, an audio processing unit 308 that decodes the compressed digital song data to generate an uncompressed digital song, a D / A converter (DAC) 307 that converts the digital song data into analog song data, A LAN controller 304 that transmits and receives signals between the audio client CL and the LAN 101.

In the audio client CL, the server list shown in Table 2 below is registered in the memory 305.

  In the server list, server identification information of the currently operating server is registered. The server specifying information includes a server name and an individual identifier assigned to each server. Here, the server name is an identifier made up of a character string that can be freely changed by the user, and the solid identifier is an identifier unique to the server such as a MAC address. Further, the IP address and port number of each server SV may be used for the server specifying information. From this server list, the audio client CL can grasp the server SV currently operating.

The audio client CL has a server connection history shown in Table 3 below in the memory 305. In the server connection history, server identification information of the server SV to which the audio client CL was connected before being disconnected is registered.

  The audio client CL reproduces music based on the music data from the server SV. The audio client CL includes an active client having not only such a music playback function but also a control function such as music selection, playback, and stop according to a user operation, and a passive client having only a music playback function. There is a client. The audio client CL having only the music playback function is embedded in, for example, a wall or a ceiling, and plays back music according to an instruction from the controller CN.

  Next, the hardware structure of the controller CN will be described in detail with reference to the drawings. FIG. 4 is a block diagram showing a hardware configuration of the controller CN according to a preferred embodiment of the present invention. The controller CN functions as a client for the server SV. The controller CN includes a LAN controller 404, a microcomputer processing unit 401 including a system operation unit 402 and a network protocol processing unit 403, a flash memory 406, a memory 405, a display device 410 such as a CRT and an LCD, and an input device such as a keyboard and a mouse. 409. The controller CN is different from the audio client CL in that the audio client CL has a reproduction function, whereas the controller CN may not have the reproduction function, and mainly has a function of monitoring and / or controlling the audio client CL. Is a point.

  A server list having the same configuration as in Table 2 is registered in the memory 405 of the controller CN. In the server list, server identification information including a server name and an individual identifier assigned to each server is registered. The server list is used by the controller to broadcast and discover active servers.

  Furthermore, the client list shown in Table 1 is acquired from the server SV and stored in the memory 405 of the controller CN. As described above, the client list is used to determine whether a client to be monitored / controlled is connected to the server.

The controller CN has a client monitoring / control history shown in Table 4 below in the memory 405. In the client monitoring / control history, client specific information of the audio client CL monitored / controlled by the controller CN before being disconnected is registered. The client monitoring / control history is used to search for a server to which a client to be monitored / controlled is connected by comparing with the client list.

[Initial connection processing]
FIG. 5 is a flowchart showing an initial connection process of the audio client to the server. When the audio client CL is powered on, the audio client CL first searches for the server SV (S501). Specifically, the audio client CL acquires server specifying information of a plurality of servers SV by broadcasting and registers it in the server list.

  Next, the audio client CL selects one server from the plurality of servers that have acquired the server specifying information, and connects to the selected server (S502). After the connection is established, the audio client CL transmits client information as its own information to the connected server SV (S503). Here, client information includes statuses such as [Play], [Stop], [Pause], volume information, playback song information that is information of the song being played, and a list construction key for creating a list. Including.

  Through the above operation, the audio client CL is connected to one selected server SV. Thereafter, the audio client CL reproduces the music data transmitted from the server SV in accordance with an instruction from the controller CN connected to the server SV. The initial connection process with the server SV by the controller CN is also the same as in FIG.

[Connection monitoring and connection recovery]
FIG. 6 is a flowchart showing audio client monitoring processing and connection recovery processing. The audio client CL (for example, the audio client CL1) determines whether or not a predetermined period has elapsed since the connection with the server SV (for example, the server SV1) (S601). After a predetermined period, the audio client CL1 determines whether or not the connection with the server SV1 is maintained (S602, S603). Specifically, the audio client CL1 transmits a connection confirmation command to the server SV1 (S602). If there is a response to the connection confirmation command from the server SV1 to the audio client CL1 (S603: YES), it is determined that the connection is maintained. On the other hand, when there is no response or when a transmission error occurs (S603: NO), it is determined that the connection is disconnected. As a response method, for example, there is a method of returning the same command as the connection confirmation command transmitted by the server SV1.

  If there is a response in step S603, the audio client CL returns to S601 again and determines whether or not the connection is maintained after a predetermined period of time (S601 to S603). Accordingly, the audio client CL1 checks the connection state with the server SV every predetermined period. If the connection is disconnected, the audio client CL1 tries to reconnect to the same server SV1 (S502).

  If the connection with the server SV1 fails as a result of the reconnection attempt (S604: NO), the audio client CL1 abandons the connection with the same server SV1 and executes a connection recovery process with another server SV2 (S501). ~ S503). Specifically, the audio client CL1 searches for a server SV2 that can be connected by broadcasting (S501), and connects to the searched server SV2 (S502). Then, the audio client CL1 transmits client information to the server SV1 (S503).

[Automatic network connection processing (1)]
When the audio client CL1 is connected to another server SV2 by the above connection recovery process, the network configuration is as shown in FIG. 7, and the audio client connected to another server (second server, eg, server SV2). CL1 cannot be controlled by the controller CN1. Next, an automatic network connection process for enabling the controller CN1 to control the audio client CL1 again will be described.

  FIG. 8 is a flowchart showing network connection processing of the audio client. After the connection recovery process, the audio client CL1 determines whether a predetermined period has elapsed (S801). After a predetermined period, the audio client CL1 first searches for a server SV currently operating on the network. Specifically, the audio client CL1 acquires server specifying information of a plurality of servers SV from the server SV by broadcasting and registers them in the server list as shown in Table 2 (S802, S803).

  Next, the audio client CL1 determines whether or not the server SV1 (first server) connected before disconnection exists among the servers currently operating on the network (S804). Specifically, it is determined whether or not the server identification information registered in the server connection history of Table 3 exists in the server identification information registered in the server list in S803.

  If the server SV1 is found (the server identification information of the server SV1 exists in the server list) (S804: YES), the audio client CL1 disconnects from the server SV2 and reconnects to the server SV1 (S805). After the reconnection, the audio client CL1 transmits its client information to the server SV1 (S806).

  After the audio client CL1 is reconnected to the server SV1, the controller CN1 can control the client CL1 via the server SV1. For example, the controller CN1 receives the client information of the audio client CL1 from the server SV1, and monitors the client status (displays it on the display device). Alternatively, the controller CN1 transmits a playback instruction command to the audio client CL1 via the server SV1.

  On the other hand, if the server SV1 cannot be found in S804, the process returns to S801 again, and broadcasts after a predetermined period to search for the server SV1.

  With the above operation, even when the audio client CL is disconnected from the server SV1 for some reason and the audio client CL is connected to another server SV2 by the automatic connection recovery function, the audio client CL itself is SV1 can be searched and reconnected. Thereafter, the audio client CL1 reproduces and stops the music data transmitted from the server SV1 in accordance with an instruction from the controller CN1 connected to the server SV1. As a result, the audio client can be controlled again by the same controller as before the disconnection, and the user can use the client without being aware that the client and the server are reconnected.

[Automatic network connection processing (2)]
Next, another preferred embodiment of the present invention will be described with reference to FIGS. The description of the same parts as in the previous embodiment is omitted.

  FIG. 9 is a block diagram illustrating an automatic network connection process according to a preferred embodiment of the present invention. In the automatic network connection function in this example, the audio client CL (for example, the audio client CL1) is disconnected from the server SV (first server, for example, the server SV1) for some reason. When CL1 is connected to another server (second server, eg, server SV2) (arrow A in FIG. 9), the controller CN (eg, controller CN1) searched for the server by broadcasting and found Each server is sequentially connected to search for the audio client CL1 (arrow B in FIG. 9). When the controller CN1 finds that the audio client CL1 is connected to the server SV2, the controller CN1 calls back the audio client CL1 to the original network (arrow C in FIG. 9) and returns to the original network (arrow in FIG. 9). D).

  FIG. 10 is a flowchart showing an automatic network connection process in the controller according to a preferred embodiment of the present invention. After the connection recovery process, the controller CN1 determines whether or not a predetermined period has elapsed (S1001). After a predetermined period, the controller CN1 first searches for a server SV operating on the network. Specifically, the controller CN1 acquires the server specifying information of the server SV by broadcasting (S1002), and registers the acquired server specifying information in the server list of Table 2 (S1003). Next, the controller CN1 selects one server (for example, the server SV2) from the plurality of servers that have acquired the server specifying information (that is, from the server list), and connects to the selected server SV2 (S1004).

  After the connection with the server SV2 is established, the controller CN1 searches for the audio client CL1 via the server SV2. Specifically, the controller CN1 requests the client list from the server SV2 (S1005), the server SV2 returns the client list to the controller CN1 in response to the request, and the controller CN1 receives the client list and stores it in the memory 305. Registration is performed (S1006).

  The controller CN1 determines whether the client CL1 to be monitored and / or controlled is connected to the server SV2. That is, it is determined whether or not the client specifying information of the audio client CL1 registered in the client monitoring / control history of Table 4 exists in the client list registered in S1006 (S1007).

  When the client identification information of the audio client CL1 does not exist in the client list (S1007: NO), the controller CN1 sequentially connects to other servers registered in the server list, acquires the client list for each server, and the audio client CL1 It is determined whether or not they are connected (S1004 to S1007).

  In this example, since the audio client CL1 is connected to the server SV2 (that is, the client specifying information of the client CL1 exists in the client list) (S1007: YES), the controller CN1 connects to the audio client CL1 to the server SV1. A request (that is, a disconnection request to the server SV2) is transmitted (S1008). After transmitting the connection request, upon receiving a notification that the connection request has been received from the audio client CL1, the controller CN1 disconnects from the server SV2 and reconnects to the server SV1 (S1009). On the other hand, the audio client CL1 that has received the connection request disconnects from the server SV2 and connects to the server SV1. The audio client CL1 transmits to the server SV1 with its own client information, and the server SV1 receives this.

  The controller CN1 determines whether or not a predetermined period has elapsed after reconnecting to the server SV1 (S1010). After the predetermined period has elapsed (S1010: YES), the controller CN1 connects the audio client CL1 to the server SV1. Confirm whether or not. Specifically, the controller CN1 requests a client list from the server SV1 (S1011), the server SV1 returns the client list to the controller CN1, and the controller CN1 receives and registers the client list (S1012). Then, it is determined whether or not there is client specifying information of the audio client CL1 in the client list of the server SV1 (S1013). When the client identification information of the audio client CL1 exists in the client list (that is, the audio client CL1 is reconnected to the server SV1) (S1013: YES), the controller CN1 controls and / or monitors the audio client CL1 ( S1014). When the client identification information of the audio client CL1 does not exist in the client list (that is, the audio client CL1 is not yet connected to the server SV1) (S1013: NO), the controller CN1 executes S1011 to S1013 again.

  With the above operation, even when the client is connected to another server by the automatic connection recovery means, the controller quickly searches for another server to which the client is connected, and the controller itself connects to that server. Furthermore, the client and the controller can be connected to the same server by reconnecting the client whose controller is connected to another server to the original server. Thereafter, the audio client CL performs reproduction, stop, and the like of music data transmitted from the server SV in accordance with instructions from the controller CN connected to the server SV. As a result, the audio client can be controlled again by the same controller as before the disconnection, and the user can use the client without being aware that the client and the server are reconnected.

[Automatic network connection processing (3)]
Next, still another preferred embodiment of the present invention will be described with reference to FIGS. The description of the same parts as in the previous embodiment is omitted.

  FIG. 11 is a block diagram illustrating automatic network connection processing according to a preferred embodiment of the present invention. In the automatic network connection function in this example, the audio client CL (for example, the audio client CL1) is disconnected from the server SV (first server, for example, the server SV1) for some reason. When CL1 is connected to another server (second server, eg, server SV2) (arrow A in FIG. 11), the controller CN (eg, controller CN1) searches for the server by broadcasting and is found The audio client CL1 is searched by sequentially connecting to each server. When the controller CN1 finds that the audio client CL1 is connected to the server SV2, the controller CN1 connects to the server SV2 to which the audio client CL1 is connected (arrow B in FIG. 11).

  FIG. 12 is a flowchart showing an automatic network connection process in the controller according to the preferred embodiment of the present invention. The automatic network connection process will be described in more detail. After the connection recovery process, the controller CN1 determines whether or not a predetermined period has elapsed (S1201). After a predetermined period, the controller CN1 first searches for a server SV operating on the network. Specifically, the controller CN1 acquires server identification information of the server SV by broadcasting (S1202), and registers the acquired server identification information in the server list of Table 1 (S1203). Next, the controller CN1 selects one server (for example, the server SV2) from the plurality of servers that have acquired the server specifying information (that is, from the server list), and connects to the selected server SV2 (S1204).

  After the connection with the server SV2 is established, the controller CN1 searches for the audio client CL1 via the server SV2 (S1205). Specifically, the client list is requested to the controller CN1, the server SV2 returns the client list to the controller CN in response to the request, and the controller CN1 receives the client list and registers it (S1206).

  The controller CN1 determines whether the client CL1 to be monitored and / or controlled is connected to the server SV2. That is, it is determined whether or not the client specific information of the audio client CL1 registered in the client specific information in Table 4 exists in the client list registered in S1206 (S1207).

  When the client identification information of the audio client CL1 exists in the client list (that is, the audio client CL1 is reconnected to the server SV1) (S1207: YES), the controller CN1 controls and / or monitors the audio client CL1 ( S1208). When the client identification information of the audio client CL1 does not exist in the client list (S1207: NO), the controller CN1 sequentially connects to other servers registered in the server list, acquires the client list for each server, and the audio client CL1 It is determined whether or not the connection is established (S1204 to S1207).

  With the above operation, even when the client is connected to another server by the automatic connection recovery means, the controller quickly searches for another server to which the client is connected, and the controller itself connects to that server. As a result, even if the client moves from server to server, if there is no effect on reproducible content (music data, video data, etc.) (such as when the content to be played also exists on another server to which it is connected), the controller And the client does not have to be reconnected to the original server, and the controller can return to the original connection state simply by connecting to another server to which the client to be monitored and / or controlled is connected. And / or can be controlled.

  The audio client CL has the automatic connection recovery function described above by installing the connection recovery program shown in FIGS. 5 and 6 in the computer. Further, the audio client CL has the automatic network connection function described above by installing the network connection program shown in FIG. 8 in the computer, and the controller CN installs the network connection program shown in FIG. 10 or FIG. .

  In the present embodiment, the audio client CL has an automatic connection recovery function, but the controller CN may have an automatic connection recovery function.

  In this embodiment, the server SV stores the music data. However, instead of this, the video data (or still image data) may be stored in addition to this, or various other contents are stored. You may do it. The server SV, the audio client CL, and the controller CN are connected to each other via the LAN 101. However, the server SV, the audio client CL, and the controller CN are not limited to this, and any one suitable for constructing a computer network such as USB or IEEE 1394 may be adopted. . When the LAN 101 is adopted, it is preferable to adopt a standard TCP / IP protocol in a PC (personal computer), but a UDP protocol or the like may be adopted, and the protocol is not particularly limited. In the figure, the server SV, the audio client CL, and the controller CN are connected so as to branch from the basic wiring of the LAN 101. For example, in the case of 10BASE-T or 100BASE-TX, the hub is used as a star. Connected.

  Furthermore, although the present invention has been described as a client-server system, it can also be applied to P2P (peer-to-peer) systems. Any terminal provided with a peer corresponding to a server and a peer corresponding to a client with an automatic network connection function and / or a peer corresponding to a controller with an automatic network connection function can function as a terminal of the P2P system. As a result, even in the P2P system, when the terminal is disconnected from the network for some reason, the peer corresponding to the client and the peer corresponding to the controller can automatically connect to the same network again.

  While the embodiments of the present invention have been described above, the above-described embodiments are merely examples for carrying out the present invention. Therefore, the present invention is not limited to the above-described embodiment, and can be implemented by appropriately modifying the above-described embodiment without departing from the spirit thereof.

  The client or controller with an automatic network connection function of the present invention can be used for a client server system of any application and scale, but can be particularly preferably used for a network audio system.

1 is a block diagram showing an overall configuration of a network type content reproduction system according to a preferred embodiment of the present invention. It is a block diagram which shows the hardware constitutions of the server by preferable embodiment of this invention. FIG. 2 is a block diagram showing a hardware configuration of an audio client according to a preferred embodiment of the present invention. It is a block diagram which shows the hardware constitutions of the controller by preferable embodiment of this invention. FIG. 6 is a flowchart showing an initial connection process in an audio client according to a preferred embodiment of the present invention. It is a flowchart which shows the monitoring process and the connection recovery process in the audio client by preferable embodiment of this invention. It is a block diagram which shows the connection recovery process in the audio client by preferable embodiment of this invention. FIG. 6 is a flow diagram illustrating automatic network connection processing in an audio client according to a preferred embodiment of the present invention. It is a block diagram which shows the automatic network connection process in the controller by preferable embodiment of this invention. FIG. 6 is a flowchart showing automatic network connection processing in a controller according to a preferred embodiment of the present invention. It is a block diagram which shows the automatic network connection process in the controller by preferable embodiment of this invention. FIG. 6 is a flowchart showing automatic network connection processing in a controller according to a preferred embodiment of the present invention.

Explanation of symbols

100 Network type content playback system 101 LAN
201 CPU Processing Unit 202 Database Management Unit 203 Network Protocol Processing Unit 204 LAN Controller 205 Storage Device 301 Microcomputer Processing Unit 302 System Operation Unit 305 Memory 306 Flash Memory 307 DAC
308 Audio processing unit 409 Input device 410 Display device CL Audio client CN Controller SV Server NW Network

Claims (8)

Connection means for connecting to at least one of the plurality of servers;
Search means for searching for the first server when the connection with the first server is disconnected and the connection means is connected to a second server different from the first server;
A client that the connection means reconnects to the first server when the search means finds the first server. Server connection history means for registering server specifying information of the first server;
A server list registration means for registering server specific information of a currently operating server in the server list;
The client according to claim 1, wherein the search unit determines whether server specifying information of the first server exists in the server list. Connection means for connecting to at least one of the plurality of servers;
Monitoring / control means for monitoring and / or controlling the client;
Search means for searching for a second server to which the client is connected when the client is disconnected from the first server and connected to a second server different from the first server; With
A controller that connects to the same server as the client when the searching means discovers the second server. Client monitoring / control history means for registering client specific information of the client that has been monitored and / or controlled;
Client list receiving means for receiving from the server a client list including client identification information of a client connected to the server,
The controller according to claim 3, wherein the search unit determines whether or not the client specifying information of the client exists in the client list. The controller according to claim 3 or 4, further comprising means for reconnecting the client to the first server when the searching means discovers the second server to which the client is connected. 5. The controller according to claim 3, wherein when the search unit finds the second server to which the client is connected, the connection unit connects to the second server. 6. A client program for executing a client connectable to at least one of a plurality of servers,
Connecting to any of a plurality of servers;
Connecting to a second server different from the first server when the connection to the first server is disconnected;
A search step for searching for the first server;
A client program for causing a computer to execute a step of reconnecting to the first server when the first server is found in the searching step. A controller program for executing a controller connectable to at least one of a plurality of servers,
Connecting to any of a plurality of servers;
Monitoring / control steps for monitoring and / or controlling the client;
A search step of searching for a second server to which the client is connected when the client is disconnected from the first server and connected to a second server different from the first server; ,
A controller program for causing a computer to execute a step of connecting to the same server as the client when the second server is found in the searching step.

Images