JP2010191736A - Network system, server device, and client device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network system, a server device, and a client device for properly notifying a user of the factor of the impossibility of content distribution from a server or the possibility of the interruption of content distribution. <P>SOLUTION: A server device includes: a storage means for storing a plurality of contents; and a transmission means for transmitting stored contents to a client device. The client device includes a reception means for receiving content to be transmitted from a server device. When such an event that content cannot be distributed occurs, the server device transmits information related with the event included in a content list or the equipment information of the server device to the client device. When such an event that content cannot be distributed during the content distribution occurs, the server device transmits content including the information related with the event to the client device according to a function installed in the client device. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a network system having a server device and a client device.

2. Description of the Related Art Conventionally, content is distributed from a device such as a DVD (Digital Versatile Disk) recorder or a PC to other devices via a network.
However, if a device that distributes content is battery-powered, content distribution may be interrupted due to battery exhaustion, so content must be distributed in consideration of the remaining battery level. .

  Further, in Patent Document 1, when the battery voltage becomes a predetermined value or less during the transfer of the image file, the transfer in progress is interrupted, and the thumbnail file of the image file whose transfer is interrupted is transferred. It is disclosed to notify the receiving side that the file transfer has been interrupted due to a shortage of the battery on the transmitting side.

JP 2003-230082 A

  In the method described in Patent Literature 1, since distribution of a content is temporarily started and then a distribution interruption notification due to a shortage of remaining battery power is performed, the receiving side device does not receive the remaining battery on the transmitting side until it starts receiving the content. It is possible to grasp the shortage of volume, and whether to request content distribution after determining whether the battery is in a state where content can be distributed well before distribution, and which server There is no mention of enabling the user to decide whether or not to request distribution. Further, depending on the function of the receiving apparatus, such as whether or not it has a renderer function, the battery information transmission method needs to be changed, but this point is not described.

  On the other hand, in order to appropriately notify the user of the status related to content distribution, a network system capable of appropriately notifying the user of the cause of content distribution and the possibility of content distribution being interrupted regardless of the function of the receiving device. It has been demanded.

  An object of the present invention is to provide a network system, a server device, and a client device capable of appropriately notifying a user of a cause that content distribution cannot be performed from a server and a possibility that content distribution is interrupted.

  A network system according to the present invention includes a server device that can transmit content and a client device that receives the content. The server device includes a storage unit that stores a plurality of contents and a transmission unit that transmits the stored content to the client device. The client device includes a reception unit that receives the content transmitted from the server device. Then, when an event occurs in which the content cannot be distributed, the server device includes information related to the event in the content list or the device information of the server device, and transmits the information to the client device. Alternatively, when an event occurs in which content cannot be distributed during content transmission, the server device transmits content including information about the event to the client device according to the function of the client device.

  According to the present invention, it is possible to provide a network system, a server device, and a client device that can notify a user of a cause that content cannot be distributed from a server and a possibility that content distribution is interrupted.

It is a figure which shows the structural example of the network system which notifies battery information. It is a figure which shows an example of a content list. It is a figure which shows the example of a screen of the client provided with the player function. It is a figure which shows the structural example of a server. It is a flowchart which shows the process example after a server acquires apparatus information from a client until it notifies battery information. It is a figure which shows the example of the screen transition of a client. It is a flowchart which shows the process example until a server receives the request | requirement of apparatus information from a client, and notifies battery information. It is a flowchart which shows the process example which updates apparatus information when a server changes to a battery shortage state during content delivery. It is a figure which shows the example which displayed the list of servers on the screen using the apparatus information which the client acquired from each server. It is a figure which shows an example of the content list containing the battery information produced by the server. It is a flowchart which shows the process example which produces the content list containing battery information in a server. It is a figure which shows an example of the user interface for a search displayed on the screen of a client. It is a flowchart which shows the example of a process which updates a content list | wrist when a battery state changes while a server is delivering content. It is a flowchart which shows the process example which a client displays a apparatus list using the apparatus information received from the server. It is a figure which shows the example which displayed the list of servers on the screen using the apparatus information which the client acquired from each server.

FIG. 1 shows a configuration example of a network system that notifies battery information. This network system includes a server 1 and a client 2 and is installed in a home, for example.

  The server 1 has a function of accumulating content such as moving images, still images, and music, and transmitting a content list, content, and the like to the client 2 via the network. The server 1 operates using a built-in battery or connected to an external power source. When it is not connected to an external power supply, it operates by obtaining power only from the battery. The server 1 is not limited to a dedicated device, and may be configured by, for example, a PC or a mobile terminal.

  The client 2 has a function of receiving content from the server 1 via the network and playing it back. IEEE (Institute of Electrical and Electronic Engineers) 802.11 wireless LAN, Bluetooth (registered trademark), WiMAX (Worldwide Interoperability for Microwave Access) (registered trademark), wireless LAN, wired LAN using LAN cable, dedicated cable A network is formed using the communication line. In the example of FIG. 1, when the server 1 is driven by a battery, the client 2 receives information indicating a battery shortage state of the server 1 and displays the information on the screen. The client 2 is not limited to a dedicated device, and may be configured by a television, a PC, or the like.

  Further, FIG. 1 shows an example in which one server 1 and one client 2 are provided in the network system, but the present invention is not limited to this. For example, FIG. 3, FIG. As shown in FIG. 4, the network system may include a plurality of servers. Also, the number of clients is not limited to one, and a plurality of clients may be provided in the system.

  First, the flow of data processing will be described below, taking as an example the case where UPnP (Universal Plug and Play) (registered trademark) is used as a standard that defines operational regulations in this network system.

  When a device corresponding to UPnP is connected to the network, it transmits connection notification information to all devices on the network by broadcast in order to notify other devices that it has been connected to the network. And each apparatus which received this connection notification transmits connection notification information with respect to the transmission source of notification. Next, when it is confirmed that the devices are connected to each other on the network, device information for identifying the device type, such as UPnP functions supported by the devices, device names and IDs, etc. is transmitted and received between the devices. ,Share. If the device information is updated, the devices are temporarily disconnected and reconnected, and the latest device information is shared.

  Examples of UPnP functions include “server”, “player”, and “renderer”. Note that devices such as players and renderers that have a function of receiving and playing back content from a server are collectively referred to as “clients”.

  The server stores content, and transmits to the client a content list indicating a list of content via the network, and stream delivery of the content. Further, the server may hold an icon for identifying the device, and include the URL of the icon in the device information when transmitting the device information to another device.

  A device having a player function acquires a content list from the server, receives the content selected by the user from the server, and plays it. A device having a renderer function, like a player, plays back and displays received content, but does not have a control function to request distribution of content to other devices, or a server serving as a distribution source, or The player is different from the player in that the content is reproduced and displayed in accordance with an instruction from a device having another control function.

  Next, the configuration of the content list will be described. The content list is hierarchically configured by folders, and includes content attribute information regarding each content and folder attribute information for managing each content hierarchically.

  The attribute information of the folder includes, for example, an identifier for uniquely identifying each folder, a folder name, an identifier of a folder that is hierarchically higher in the folder, and the like. Configured.

  Specific examples of content attribute information include title information, format information, genre information, data size information, storage location attribute information, update date / time information, hierarchical information between content information and folders, and the like. Here, the format information is information indicating types of moving images, still images, music, and the like, for example, MIME-TYPE (Multipurpose Internet Mail Extension-Type). The storage location attribute information is information representing a storage location of content on a network or in a device, such as a URI (Uniform Resource Identifier). The hierarchy information is information serving as an identifier indicating which folder the content belongs to.

  In addition to the attribute information, the content list includes version information. When the content configuration stored in the server changes, a new content list is created and the version information Update. Unlike device information update, content list update does not require disconnection from the network, and the client acquires the content list and checks the version information each time to identify that the list has been updated. To do.

  FIG. 2 is an example of a content list. Below the highest hierarchy (root hierarchy), there is a folder list 21 for each type of content such as moving images, music, and still images. Various contents are distributed directly under each folder. For example, a moving image content list 22 such as baseball content A and soccer content B, which are moving image contents, is distributed in a moving image folder. Content is also distributed.

  FIG. 3 is a screen example of a client having a player function. In this example, a case where a plurality of servers are included in the network system is shown.

  The client acquires from the server a list of a predetermined number of contents in one hierarchy from the hierarchically configured content list. For example, when the user selects server B from the server list, the client acquires a content list (video folder, music folder, still image folder) in the hierarchy immediately below the highest level, and is in the content list screen 31. The content selection screen is displayed. Next, if the user selects, for example, a video folder, the client obtains a content list (baseball content A, soccer content B) in the hierarchy immediately below the video folder from server B, and a selection as shown on the content list screen 32 Display the screen. In this way, in UPnP content search, the user searches for desired content while moving through each layer.

  Further, the client refers to the version information of the content list when the hierarchy in the content list is changed or when the content reproduction is finished, and checks whether the content list is updated. If there is an update, the content list is acquired from the server. When the content list is updated, it is desirable to allow the user to recognize the updated portion, for example, by displaying a message or symbol such as “New” on the screen.

  Next, an outline of the battery information notification process will be described. The server 1 sets in advance the remaining battery level that can sufficiently deliver the content as the spare remaining level. In this example, a state in which the remaining amount of the battery is less than the reserve remaining amount is referred to as a “battery shortage state”, and a state in which the remaining battery amount is greater than the reserve remaining amount is referred to as a “battery normal state”. The server 1 also generates content including battery information (hereinafter referred to as battery status notification content). Note that this content is not limited to moving image information, and may include still image information and audio information.

  When the server 1 is delivering content to the client 2 and the battery runs out, the content delivery is interrupted. When the server 1 receives the content distribution request again from the client 2 after the content distribution is interrupted, the battery state notification content is transmitted to the client 2. The client 2 displays information such as “server battery is insufficient” on the screen using the received content. By processing in this way, the battery state of the server 1 is presented to the user of the client 2, and the user can recognize that the content distribution has been interrupted due to the low remaining battery level of the server 1. When the client 2 has a renderer function, the battery state notification content may be transmitted from the server 1 to the client 2 regardless of whether there is a re-distribution request from the client 2.

  The battery state notification content includes information indicating the remaining amount of battery power and whether charging is in progress. The remaining battery power is calculated by subtracting the consumed power from the fully charged state of the battery. In addition, in addition to or in addition to the remaining power information, information indicating the ratio of the remaining amount with respect to the fully charged state and the time that can be continuously used may be included.

  FIG. 4 is a block diagram illustrating a configuration example of the server 1. The server 1 includes a network management unit 41, a server control unit 42, a content management unit 43, a power supply control unit 44, a battery 45, a display unit 46, an operation unit 47, and a system control unit 48.

  The network management unit 41 includes a communication unit (not shown) that transmits and receives data to and from other devices by wire or wireless, and manages the communication function in the server 1. The server control unit 42 creates device information necessary for realizing a server function compliant with a standard such as UPnP, manages the created device information, and is performed via the communication unit of the network management unit 41. Controls device information sharing processing with other devices. The content management unit 43 includes a storage unit (not shown) that stores content and a content list, and controls transmission of the content list and content to other devices performed via the communication unit of the network management unit 41.

  The power control unit 44 detects the remaining amount of power of the battery 45 and whether or not charging is in progress. The display unit 46 displays a user interface such as information necessary for the user to input an instruction to the server 1 via the operation unit 47. The system control unit 48 controls each component of the server 1 based on a program stored in a memory (not shown). For example, the network management unit 41 and the content management unit 43 control device information sharing processing and content transmission control based on an instruction from the system control unit 48.

  An example of processing in the server 1 will be described below while showing an example of screen transition of the client 2 in the course of processing. FIG. 5 is a flowchart showing an example of processing from when the server 1 acquires device information from the client 2 until notification of battery information. This process is executed by the system control unit 48. FIG. 6 illustrates the screen transition of the client 2.

  When the server 1 is powered on, the server control unit 42 is controlled to acquire device information from other devices via the network management unit 41 (ST501). When the content distribution request is received from the client 2, the content management unit 43 is controlled to start transmitting the content via the network management unit 41 (ST502). A content reproduction screen 61 in FIG. 6 shows a state in which the client 2 receives the content and displays the content on the screen. Although omitted in the example of FIG. 5, it is assumed that the content transmission is continued until the battery runs out or a new request is received from the client 2. When the server 1 becomes in a battery shortage state during distribution of content (ST503), the content management unit 43 is controlled to stop transmission of the content to the client 2 (ST504). At this time, since the client 2 cannot receive the content from the server 1, the screen changes from the content reproduction screen 61 of FIG. 6 to the content stop screen 62.

  It is determined whether or not a content transmission request has been received from the client 2 again. If the transmission request is received (Yes in ST505), the content management unit 43 reads the battery state notification content from the storage unit and transmits it to the client 2. Is controlled (ST506). In this way, when the content transmission request from the client 2 is received, by controlling to transmit the battery state notification content, even if the client 2 does not have a renderer function, for example, FIG. As shown in the content playback screen 63, the user can be informed that the distribution of content has been stopped due to the battery shortage of the server 1.

  On the other hand, if the content transmission request is not received from the client 2 even after a predetermined time has elapsed since the content transmission was stopped in ST504 (No in ST505), it is determined whether or not the client 2 has a renderer function. If it is determined and the renderer function is provided (Yes in ST507), the battery state notification content is transmitted to the client 2 (ST506). Whether or not a renderer function is provided is determined using device information.

  As described above, when the server 1 is in a battery shortage state and the content distribution is stopped, the distribution of the content is stopped due to the battery shortage of the server 1 by transmitting the battery state notification content to the user. Can be informed.

  In the example of FIG. 5, it is determined whether or not the client 2 has a renderer function when the content transmission request is not received from the client 2 in ST505. However, the present invention is not limited to this. For example, after the content distribution is stopped in ST504, the determination of ST507 is performed. When the client 2 has the renderer function, the battery state notification content is transmitted. When the client 2 does not have the renderer function, the determination of ST505 is performed. You may make it do. Further, when the content transmission request is received in ST505 of FIG. 5, it is desirable to determine the battery state of the server 1, and control to shift the processing of ST502 if the battery has changed to a normal state. .

  In addition, when the client 2 has a renderer function, information indicating that the server 1 is in a normal state when the server 1 is in a normal state due to battery charging or operation with an external power source is included. The battery state notification content may be transmitted to the client 2. As a result, the user can be notified that the content can be distributed.

Further, in the example of FIG. 5, it is described that the process is terminated after transmitting the battery state notification content in ST506, but the process of ST505 may be repeated. This
When the server 1 is in a normal battery state, content indicating that the battery is in a normal state can be transmitted to the client 2 to notify the user that the distribution of the content can be resumed.

Further, by transmitting the battery status notification content every time a transmission request from the client 2 is received, even when the client 2 does not store the battery status notification content, an operation for requesting distribution is input from the user. Each time, the display of the battery shortage of the server 1 can be displayed on the screen of the client 2. However, if the battery state notification content has already been distributed, the battery state notification content may not be transmitted if there is no change in the battery state of the server 1. In the case of such control, a flag indicating that the battery state notification content has already been transmitted is recorded together with the identification information of the client 2. In addition, in order to display a battery shortage in response to an operation from the user, it is necessary to store the battery state notification content in the client 2.
The processing when the server 1 is in a battery shortage state during content distribution has been described above. Next, when the server 1 transmits device information including battery information to the client 2, the client 2 A method for displaying server information including battery status will be described. By using this method, the user can check the battery status of each server at the time of selecting a server for reproducing the content. As a result, the user can select a server with a good battery state that is unlikely to stop content distribution. In addition, when a battery shortage occurs during content distribution by the server selected by this method, battery information is notified by the method shown in FIG. 5, for example.

  FIG. 7 shows an example of processing from when the server 1 receives a request for device information from the client 2 to notify the state of the battery. This process is executed by the system control unit 48.

  When the server 1 is turned on and connected to the network via the network management unit 41 and receives a request for device information from the client 2 (ST701), the server 1 is controlled to detect the remaining battery level by the power control unit 44. (ST702). Then, it is determined whether or not the detected remaining battery level is greater than or equal to the reserve remaining level (ST703). If the remaining amount is greater than or equal to the reserve remaining amount (Yes in ST703), device information indicating a normal state is created (ST704), and the created device information is transmitted to the client 2 (ST706). On the other hand, when the remaining battery capacity is less than the reserve remaining capacity (No in ST703), device information indicating that the battery is insufficient is created (ST705) and transmitted to the client 2 (ST706).

  FIG. 8 shows a processing example in which the device information is updated when the battery changes to a shortage state while the server 1 is delivering content.

  While the server 1 is delivering content, it performs the same processing as ST 702 and ST 703 every predetermined period, for example, every minute, and detects that the battery has transitioned to an insufficient state (ST 801). Distribution of the content is stopped (ST802). Next, device information indicating that the battery is insufficient is created (ST803), and the connection with the network is disconnected (ST804). Then, after connecting to the network again, the latest device information is transmitted to the client 2 (ST805). As a result, the device information indicating that the battery is in shortage can be shared with the client 2. If the server's remaining battery level is even lower than the reserve capacity, the device information transmission interval can be increased or the number of transmissions can be reduced even when the remaining battery level has changed to reduce battery power consumption. It is desirable to reduce the amount of data included in the device information.

   FIG. 14 shows a processing example in which the client 2 displays a device list using the device information received from the server 1.

  When the client 2 receives the device information transmitted from the server 1 (ST1401), the device information is included in the battery information or, if included, indicates that the battery information is insufficient. It is determined whether it exists (ST1402). The presence or absence of battery information includes, for example, whether the device name includes a keyword related to the battery such as “battery” or “charge”, or an identifier indicating that the battery information is included. It is determined by checking.

  If the remaining battery level is low (Yes in ST1402), an icon indicating that the battery is insufficient, such as an icon indicating that the battery is insufficient, is displayed on the device list screen (ST1403). By displaying in this way, it is possible to prevent selection of a server with a battery shortage state. In order to prevent the server from being selected, even when the user tries to input a selection instruction by key operation, the key operation corresponding to the server selection instruction is not accepted or the input is not executed. It is desirable to control.

  On the other hand, when the battery information is not included or the battery information indicates that the battery is in a normal state (No in ST1402), icons and device information are displayed on the device list screen as usual (ST1404). . FIG. 9 shows an example in which the server 2 displays a list of servers on the screen using the device information acquired from each server. The icon displayed on the screen may be created using the device information received by the client 2, or the server 1 transmits the device information including the URL indicating the location where the icon image data is stored, The client 2 may download icon image data using a URL.

  In the example of FIG. 9, 91, 93, and 95 are server names, and 92, 94, and 96 are icons. When device information indicating that the battery is insufficient is acquired, an icon 94 indicating the battery shortage state is displayed including the battery state of “low battery” in the server name 93. Similarly, when device information indicating that the server is charging the battery is acquired, a server name 95 and an icon 96 indicating that the battery is being charged are displayed. By performing such display, it is possible to notify the user of an appropriate server for content distribution. In addition, it is not limited to the example of FIG. 9, You may notify a user with another display method. For example, as shown in FIG. 15, servers with insufficient battery power may be displayed in a list in a display area 1501 “Battery shortage”. At this time, the display area 1501 may be displayed at a position that is difficult for the user to select, such as it is difficult to position the cursor. Further, for a server in a battery shortage state, an icon may not be displayed, and only the server name may be displayed in the display area 1501. In addition, server names and icons may be displayed in order of the remaining battery level, or a mark indicating a server having a good battery state may be displayed. As described above, the server 1 transmits the device information including the battery information to the client 2 and the client 2 displays the server information including the battery information. It becomes possible to select a desired server while checking the battery state, and the user-friendliness can be improved.

  Next, a method in which the server 1 transmits a content list including battery status information to the client 2 and the client 2 presents the content list including the battery status to the user will be described. Thus, by presenting the content list including the battery state to the user, the user can check the battery state when selecting desired content from the content list. Unlike updating device information, when updating the content list, it is not necessary to disconnect from other devices, so the latest battery state can be acquired without disconnecting.

  FIG. 10 is an example of a content list including battery information created by the server 1. The various folder list 1001 includes a plurality of folders corresponding to the type of content such as a moving image folder and a music folder, and a battery information file 1003 is installed in the same hierarchy as the various folder lists 1001. For example, a battery information file 1004 is installed together with a moving image content list 1002 in the moving image folder. As described above, by installing the battery information file at each level of the content list, when the content list is displayed on the client 2, the battery status is presented regardless of the level of the content list to be displayed. be able to. The battery status is displayed at a location indicating the file title, for example.

  FIG. 11 shows a processing procedure for creating a content list including battery information in the server 1. When the server 1 transitions to a battery shortage state, the server 1 selects an arbitrary folder from the content list created in advance (ST1101). When a folder is selected, dummy content including battery information is created and added to the content list (ST1102). In the dummy content, for example, information indicating the remaining battery level such as “low battery level” is included in the title name. Further, the identifier of the folder selected in ST1101 is included in the folder information to which the content belongs. These processes are repeated to create dummy content including battery information immediately below all folders in the content list. Then, dummy content is also created below the highest hierarchy that the client 2 will display first (ST1103). However, when creating content immediately below the highest hierarchy, “0” indicating the highest hierarchy is described in the folder information to which it belongs. With these processes, a content list that supports UPnP and includes dummy content in which battery information is placed on any layer can be distributed to the client 2.

  FIG. 12 shows an example of a search user interface displayed on the screen of the client 2.

  First, the client 2 requests the content list from the server 1 (in this example, server B) that stores the content list. When the client 2 receives the content list from the server 1, the presence or absence of battery information is determined by detecting, for example, a keyword or identifier related to the battery. When the battery information is included, as shown in various folder list screens 1201, a battery information file titled “Battery is low” is displayed side by side with the title of the folder corresponding to each content type. For example, when a moving image folder is selected, a moving image content list screen 1202 in the moving image folder is displayed. Similarly, since a battery information file is installed here, the battery information can be confirmed even at this level. FIG. 12 is an example, and the present invention is not limited to this. For example, a battery information file indicating that the battery is in a normal state may be displayed.

  FIG. 13 shows a processing example in which the content list is updated when the battery status changes while the server 1 is delivering the content.

  If the battery changes to a shortage state while the server 1 is delivering content (ST1301), the server 1 stops delivering content to the client 2 (ST1302). Next, the battery information of each layer of the content list and the version information of the content list are updated (ST1303). When a content list request is received from the client 2, control is performed so as to transmit the latest content list including battery information and version information (ST1304).

  Note that the processing is not limited to the processing in FIG. 13. For example, it is determined whether the client 2 has a renderer function using device information. If the client 2 has the renderer function, whether there is a request from the client 2. Regardless, the updated content list may be transmitted. Further, although the example of FIG. 13 shows processing when the battery transitions to an insufficient state during content distribution, the content list may be updated even when the battery state is improved. However, when the battery state is improved during the distribution of the content, the content is transmitted after the end of the distribution or during the stop of the distribution without stopping the content distribution in response to the improvement of the battery state.

  As described above, in the content / device information / content list transmission / reception method between the server and client that support UPnP, the server battery runs out during content distribution, and content transmission / reception is suddenly disconnected. As a result, the client user was worried that the reason for disconnection was unknown. As described above, by transmitting the battery information from the server to the client, it becomes possible to present the disconnection due to the lack of the battery to the user of the client.

  In addition, although the above example demonstrated the case where battery information was notified, it is not limited to this. Not only the battery information but also other events that cause content to be unable to be delivered to the server may be notified to the client. As a result, the user can be notified of the reason why the content cannot be distributed, and the convenience in content distribution can be improved. For example, if a server that distributes content is something that can be taken outdoors, such as a mobile device or a notebook PC, when this server is taken outdoors, it can be connected to an indoor network such as a home network. An event such as turning off will occur. Therefore, a highly portable server such as a portable terminal is provided with a button for notification of going out, for example, and when the user presses this button, the notification of going out is included such as "The specified content cannot be delivered because it goes out" Content, device information, content list, etc. are sent to the client. Thereby, the client can present to the user that the content cannot be distributed from the server. In addition, transmission of contents including out-of-office notification information is not limited to when the out-of-office notification button is pressed down, but is transmitted in advance at a predetermined timing, such as when driving from an external power source is changed to battery-powered. May be.

  Another example of an event is that a server that distributes content notifies the interruption of distribution due to function restrictions. The restriction of the device is, for example, that it is necessary to stop the distribution to other devices in order to view content locally without using the network. Specifically, when viewing content locally using a device operating as a server, it is possible to notify the client viewing the content of the server via the network of the interruption.

DESCRIPTION OF SYMBOLS 1 ... Server, 2 ... Client, 41 ... Network management part, 42 ... Server control part, 43 ... Content management part, 44 ... Power supply control part, 45 ... Battery, 46... Display unit, 47 .. operation unit, 48... System control unit

Claims (6)

A network system comprising: a server device capable of transmitting content by battery drive; and a client device for receiving content transmitted from the server device,
The server device includes a storage unit that stores a plurality of contents, and a transmission unit that transmits the content stored in the storage unit to the client device. The client device receives the content transmitted from the server device. Receiving means for receiving,
When the remaining amount of the battery is less than a predetermined value, the server device displays information regarding the remaining amount of the battery as a content list indicating a list of a plurality of contents stored in the storage unit or the server device. A network system characterized by being included in device information to be identified and transmitted to the client device by the transmission means. A network system comprising: a server device capable of transmitting content by battery drive; and a client device for receiving content transmitted from the server device,
The server device includes a storage unit that stores a plurality of contents, and a transmission unit that transmits the content stored in the storage unit to the client device. The client device receives the content transmitted from the server device. Receiving means for receiving,
When the remaining amount of the battery becomes less than a predetermined value during transmission of content by the transmission means,
A network system, wherein content including information related to the remaining battery level is transmitted to the client device according to a function of the client device. A server device capable of transmitting content to a client device,
Storage means for storing a plurality of contents;
Transmitting means for transmitting the content stored in the storage means to the client device;
When an event occurs that makes it impossible to deliver content to the client, information related to the event is included in a content list indicating a list of a plurality of contents stored in the storage means or device information for identifying the server device Control means for controlling the transmission means to transmit to the client device;
A server device comprising: A server device capable of transmitting content to a client device,
Storage means for storing a plurality of contents;
Transmitting means for transmitting the content stored in the storage means to the client device;
When an event occurs in which content cannot be distributed to the client while the content is being transmitted by the transmission unit, the content including information related to the event is transmitted to the client device according to the function of the client device. The server apparatus characterized by controlling so that it may do. A client device that receives content from a server,
Receiving means capable of receiving content from the server and a content list indicating a plurality of content titles stored in the server;
Display means for displaying the content or content list received by the receiving means;
When the content list includes information indicating that an event has occurred that prevents the server from distributing content, information indicating that the event has occurred is displayed together with the titles of the plurality of content items. Control means for controlling the display means;
A client device comprising: A client device connectable to a plurality of server devices,
Receiving means for receiving device information for identifying each server device from the plurality of server devices;
Display means for displaying a list of connectable server devices using the device information received by the receiving means;
If the device information includes information indicating that an event has occurred that prevents the server from distributing content, the list includes information indicating that the event has occurred in the server that transmitted the device information. Control means for controlling so as to
A client device comprising:

Images