JP4784598B2 - Relay server and relay communication system - Google Patents

Description

  The present invention relates to a relay server and a relay communication system that realize resource sharing via a network.

Conventionally, a communication system called a virtual private network (VPN) is known (for example, Patent Document 1). This VPN is used, for example, for applications in which terminals connected to LANs of a plurality of branch offices (bases) provided for each region communicate via the Internet. Using the VPN, each client terminal can share various resources (folders and files) on a device connected to another remote LAN.
JP 2002-217938 A

  In the file sharing method such as VPN, for example, when the operating system adopted by each client terminal is different, the character code used may be different for each client terminal. In this case, if a file or the like is shared between client terminals that use different character codes, the file and folder names will be garbled, and normal display will not be possible, making it difficult to specify and operate the shared file. There was a thing. Therefore, improvement has been demanded from the viewpoint of improving the ease of handling of resources.

  The present invention has been made in view of the above circumstances, and its main purpose is to prevent the shared resource name from being garbled and the like, and to perform the designation and operation of the shared resource easily and reliably Is to provide.

Means and effects for solving the invention

According to an aspect of the present invention, a relay server having the following configuration is provided. That is, the relay server includes a relay group information registration unit, a shared resource information registration unit, and a control unit. The relay group information registration unit stores information on relay groups including other relay servers that can be connected to each other. The shared resource information registration unit stores shared resource information when a resource is shared among a plurality of client terminals in the relay group. The shared resource information includes information on the resource, information on a character code used in a name assigned to the resource, and information on an account of a resource sharing terminal that is a client terminal that shares the resource. The control unit includes a character code information management unit and an instruction relay unit. The character code information management unit records the character code information in the shared resource information by designating a character code of a name given to the resource. The instruction relay unit relays the instruction to a client terminal capable of operating an entity of the specified resource or a relay server having the client terminal under the control of the client terminal by specifying the resource and instructing an operation. To do. When a resource that can operate an entity is shared among a plurality of client terminals, the client terminal accepts a designation of a name to be given to the resource only to those that match the character code.

With this configuration, the shared resource can be indirectly operated by the client terminal via the relay server. Moreover, since the character code of the name given to the shared resource can be managed based on the character code information, the resource name can be prevented from being garbled, and the resource can be specified and operated easily and reliably. Further, it is possible to prevent occurrence of garbled characters or the like by using a character code that cannot be handled by the client terminal for the resource name.

  In the relay server, the character code information in the shared resource information is preferably configured to be described for each group having a different configuration of the resource sharing terminal.

  With this configuration, the character code can be changed according to the configuration of the resource sharing terminal, and the character code of the resource name can be managed appropriately.

According to another aspect of the present invention, a relay communication system having the following configuration is provided. That is, this relay communication system includes a plurality of relay servers and a plurality of client terminals. The relay server includes a relay group information registration unit, a shared resource information registration unit, and a control unit. The relay group information registration unit stores information on relay groups including other relay servers that can be connected to each other. The shared resource information registration unit stores shared resource information when a resource is shared among a plurality of the client terminals in the relay group. The shared resource information includes information on the resource, information on a character code used in a name assigned to the resource, and information on an account of a resource sharing terminal that is a client terminal that shares the resource. The control unit includes a character code information management unit and an instruction relay unit. The character code information management unit records the character code information in the shared resource information by designating a character code of a name given to the resource. The instruction relay unit relays the instruction to a client terminal capable of operating the substance of the specified resource or a relay server under the client terminal by the client terminal specifying a resource and instructing an operation. When a resource that can operate an entity is shared among a plurality of client terminals, the client terminal accepts a designation of a name to be given to the resource only to those that match the character code.

With this configuration, the shared resource can be indirectly operated by the client terminal via the relay server. Moreover, since the character code of the name given to the shared resource can be managed based on the character code information, the resource name can be prevented from being garbled, and the resource can be specified and operated easily and reliably. Further, it is possible to prevent occurrence of garbled characters or the like by using a character code that cannot be handled by the client terminal for the resource name.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is an explanatory diagram showing the overall configuration of a relay communication system according to an embodiment of the present invention.

  As shown in FIG. 1, the relay communication system according to the present embodiment includes a plurality of LANs connected to a WAN. This relay communication system includes a relay server 1, an external server 2, a client terminal 5, a file server 6, and the like.

  A WAN (Wide Area Network) is a network that connects different LANs to each other. In the present embodiment, the Internet is used as the WAN.

  A LAN (Local Area Network) is a relatively small network constructed in a limited place. There are a plurality of LANs, and they are constructed at locations physically separated from each other. In this embodiment, it is assumed that the LAN 91 is constructed in the Tokyo branch and the LANs 92, 93, and 94 are constructed in the Osaka branch, the Nagoya branch, and the Fukuoka branch, respectively. These four LANs 91, 92, 93, 94 are connected to the Internet, which is a global network.

  Next, the external server 2 will be described with reference to FIG. FIG. 2 is a functional block diagram of the external server 2. The external server 2 is a device used for communication between the relay servers 1 arranged in each LAN, and is installed on the Internet.

  The external server 2 shown in FIG. 2 has a function as a SIP (Session Initiation Protocol) server. Specifically, the external server 2 has a function as a SIP proxy server that relays SIP methods and responses, and a function as a SIP registrar server that registers an account of the relay server 1.

  As shown in FIG. 2, the external server 2 includes a WAN interface 201, a control unit 202, and a relay server account information database 203 as main components.

  The WAN interface 201 is an interface that communicates with each device such as the relay server 1 connected to the Internet using a global IP address.

  The relay server account information database 203 is a database that manages the account of the relay server 1 that has requested registration in association with the global IP address.

  The control unit 202 is a processing unit that controls various communications performed via the WAN interface 201, and controls communication processing according to a protocol such as TCP / IP, UDP, or SIP. For example, the control unit 202 receives an account of the relay server 1 from each relay server 1 and registers it in the relay server account information database 203. Also, processing such as relaying communication data such as various SIP methods or responses transmitted from the relay server 1 to other relay servers 1 is performed.

  Next, the client terminal 5 will be described with reference to FIG. FIG. 3 is a functional block diagram of the client terminal 5.

  The client terminal 5 is a terminal that can be directly operated by the user, and corresponds to, for example, a personal computer (PC) used for daily work by the user. Accordingly, there are usually a large number of client terminals 5 in the LAN. In this embodiment, as shown in FIG. 1, client terminals 11 and 12 are connected to a LAN 91, and client terminals 21 and 22 are connected to a LAN 92. In addition, client terminals 31 and 32 are connected to the LAN 93, and client terminals 41 and 42 are connected to the LAN 94. Each client terminal 5 is assigned a private IP address that is uniquely managed in the same LAN.

  As shown in FIG. 3, the client terminal 5 includes a LAN interface 601, a control unit 602, a resource storage unit 603, and a shared resource information database 604 as main components.

  The LAN interface 601 is an interface that communicates with each device such as the relay server 1 and the file server 6 connected to the same LAN using the private IP address.

  The resource storage unit 603 stores resource entities such as files or folders that can be operated by the client terminal 5.

  The shared resource information database 604 stores shared resource information describing information of shared resources held by each client terminal 5.

  The control unit 602 is a processing unit that controls various communications performed via the LAN interface 601. The control unit 602 controls communication processing according to a protocol such as TCP / IP, UDP, or SIP.

  For example, the control unit 602 performs processing for controlling the movement, change, or deletion of resources stored in the resource storage unit 603. When the control unit 602 receives the shared resource information change notification from the relay server 1, the control unit 602 performs a process of updating the shared resource information stored in the shared resource information database 604.

  Next, the relay server 1 will be described with reference to FIG. FIG. 4 is a functional block diagram of each relay server 1.

  As shown in FIG. 1, one relay server 1 is arranged in each LAN. Specifically, the relay server R1 is arranged in the LAN 91, the relay server R2 is arranged in the LAN 92, the relay server R3 is arranged in the LAN 93, and the relay server R4 is arranged in the LAN 94.

  The relay server 1 is connected to a LAN and can communicate with each client terminal 5 connected to the same LAN. The relay server 1 is also connected to the Internet, and can communicate with the relay server 1 connected to another LAN (via the external server 2). For this communication, each relay server 1 is assigned both a private IP address and a global IP address.

  As shown in FIG. 4, the relay server 1 includes a LAN interface 501, a WAN interface 502, a control unit 503, an account information database 504, a relay group information database 505, and a shared resource information database 506. It is provided as a component.

  The LAN interface 501 is an interface that uses a private IP address to communicate with the client terminal 5 connected to the same LAN as its own device. For example, in the LAN 91, the relay server R 1 can communicate with each of the client terminals 11 and 12 using the LAN interface 501.

  The WAN interface 502 is an interface that communicates with each device such as the external server 2 connected to the Internet using a global IP address.

  Each relay server 1 has a function as a SIP registrar server, and communication between each relay server 1 and each client terminal 5 is performed using SIP. For example, in the LAN 92, the relay server R2 functions as a SIP registrar server, receives the accounts of the client terminals 21 and 22 connected to the LAN 92, and registers them in the account information database 504.

  Therefore, as shown in FIG. 5, the relay server 1 functions as a server that receives an account from the client terminal 5 and registers (REGISTER) in relation to the client terminal 5. In relation to the external server 2, the relay server 1 functions as a client that transmits an account to the external server 2 and registers (REGISTER).

  The account information database 504 in FIG. 4 is a database that manages the account of the client terminal 5 that has requested registration in association with the private IP address.

  A relay group information database (relay group information registration unit) 505 is a database that manages relay group information related to the client terminal 5 registered in the account information database 504.

  A shared resource information database (shared resource information registration unit) 506 is a database that manages shared resource information related to the client terminal 5 registered in the account information database 504.

  The control unit 503 is a processing unit that controls various communications performed via the LAN interface 501 and the WAN interface 502, and controls various communication processes according to protocols such as TCP / IP, UDP, and SIP.

  The control unit 503 executes, for example, processing for transmitting an account of the own apparatus to the external server 2 to request registration, and processing for creating relay group information and storing it in the relay group information database 505. Further, the control unit 503 executes processing for creating shared resource information and storing it in the shared resource information database 506.

  The control unit 503 includes a character code information management unit 511 and an instruction relay unit 512.

  The character code information management unit 511 describes the character code information to be followed when the name of the shared resource is described in the shared resource information in the shared resource information according to an instruction from the client terminal 5.

  When the instruction relay unit 512 receives an operation instruction such as opening a shared resource from the client terminal 5 or the like, the instruction relay unit 512 relays the operation instruction to a necessary partner (another relay server 1 or the like).

  Next, the file server 6 will be described. As shown in FIG. 1, this file server 6 is connected to a LAN and is configured to be able to communicate with each client terminal 5 connected to the same LAN.

  The file server 6 is configured to store resources such as files or folders, and functions as a resource storage unit that replaces the resource storage unit 603 (FIG. 3) provided in each client terminal 5. That is, in this embodiment, the resources that can be operated by each client terminal 5 are considered to be stored in the local disk of the client terminal 5 or stored in the file server 6 as a network drive. . This file server 6 is not essential for each LAN, and in the example of FIG.

  Next, relay group information and shared resource information, which are information handled in this relay communication system, will be described.

  First, relay group information will be described with reference to FIG. FIG. 6 is a diagram showing an example of the contents of relay group information.

  FIG. 6 shows an example of the contents stored in the relay group information database 505 in the relay server R3. In this example, the relay group information database 505 stores two pieces of relay group information 100a and 100b.

  Each of the relay group information 100a and 100b includes one group identification information 101, information (relay account information) 102 of the relay server 1 that configures the relay group by permitting mutual connection, and resource sharable terminal information 110. And.

  The group identification information 101 is information for identifying the relay group information 100, and is configured to be uniquely identified with a different identification ID every time the relay group information 100 is created. Thereby, the operator or the like can specify the relay group based on the group identification information 101, and can easily change the group configuration.

  The relay account information 102 includes account information of each relay server 1 that configures a relay group by permitting connection to each other. For example, in the relay group information 100a shown on the upper side of FIG. 6, accounts of three relay servers R1, R2, and R3 constituting the relay group are described. In the relay group information 100b shown on the lower side of FIG. 6, an account of one relay server R3 constituting the relay group is described.

  In the relay account information 102, specific names given to the accounts of the respective relay servers 1 are registered together to facilitate user identification. For example, in the relay account information 102a of the relay server R1 (relay-server1), a name (branch office A) is assigned to the account (relay-server1 @ net) of the relay server R1.

  As described above, the relay group information 100a and 100b are created so as to be uniquely identifiable for each relay group. Further, the relay group information 100a, 100b includes an account (relay account information 102) of each relay server that forms a group (relay group) by allowing connection to each other. Therefore, by referring to the relay group information 100a and 100b, it is possible to know which LAN and which LAN form a group.

  Next, the resource sharable terminal information 110 that can be included in the relay group information 100 will be described.

  As shown in FIG. 6, the resource sharable terminal information 110 is registered corresponding to each relay group information 100. For example, the resource sharable terminal information 110a is registered corresponding to the relay group information 100a, and the resource sharable terminal information 110b is registered corresponding to the relay group information 100b.

  Each of the resource sharable terminal information 110a and 110b includes individual terminal information 111 describing the client terminal 5 that is permitted to share resources in the relay group related to the corresponding relay group information 100a and 100b. The individual terminal information 111 is information describing an account of each client terminal 5 that can share resources.

  For example, the relay group information 100a corresponding to the resource sharable terminal information 110a on the upper side of FIG. 6 defines a relay group including three relay servers R1, R2, and R3. As shown in FIG. 1, there are two client terminals 11 and 12 in the LAN 91 to which the relay server R1 is connected. In the example of the resource sharable terminal information 110 a on the upper side of FIG. 6, both of these two units are selected as terminals that can share resources in the relay group, and the account information is registered as the individual terminal information 111. Similarly, in the LAN 92 to which the relay server R2 is connected, both the client terminals 21 and 22 are selected as resource sharable terminals. Although the client terminals 31 and 32 exist in the LAN 93 to which the relay server R3 is connected, in the example of the resource sharable terminal information 110a, only the client terminal 31 is selected as the resource sharable terminal, and the account information is the individual terminal information 111. It is registered as.

  The relay group information 100b corresponding to the resource sharable terminal information 110b on the lower side of FIG. 6 defines a relay group including only the relay server R3. In the example of the resource sharable terminal information 110b, in the LAN 93 to which the relay server R3 is connected, both of the two client terminals 31 and 32 are selected as resource sharable terminals, and the account information is used as the individual terminal information 111. It is registered.

  In the individual terminal information 111, in addition to the account of each resource sharable terminal, the specific name given to the account is registered, and the user can be easily identified. For example, in the case of the client terminal 11, a name (client 11) given to the account (for example, client11@relay-server1.net) is described. Further, the individual terminal information 111 describes affiliation identification data 112 indicating the affiliation of the resource sharable terminal such as the sales department and the development department.

  In the resource sharable terminal information 110, each individual terminal information 111 is described in association with the relay account information 102 of the relay server connected to the same LAN as the resource sharable terminal. For example, the individual terminal information 111 related to the client terminal 11 is described in a form associated with the relay account information 102a of the relay server R1.

  Further, as illustrated in the example of FIG. 6, the relay group information database 505 can store a plurality of relay group information 100 and resource sharable terminal information 110. The client terminal 31 is a resource sharable terminal in both resource sharable terminal information 110a and 110b in the two relay groups, and the individual terminal information 111 is described. Thus, one client terminal 5 can be selected as a resource sharing terminal in a plurality of relay groups, and the resource sharable terminal information 110 to that effect can be stored in the relay group information database 505.

  Each relay group information 100 is exchanged between the relay servers 1 constituting the relay group. For example, the upper relay group information 100a in FIG. 6 is exchanged by three relay servers R1, R2, and R3, and stored in the relay group information database 505 of the respective relay servers R1, R2, and R3. Also, the lower relay group information 100b in FIG. 6 is held only by the relay server R3 and stored in the relay group information database 505 of the relay server R3.

  Next, the content of the shared resource information will be described with reference to FIGS. FIG. 7 illustrates the shared resource information 120 stored in the shared resource information database 604 of the client terminal 21. Note that the same information is also stored in the shared resource information database 506 of the relay server R2 connected to the same LAN as the client terminal 21.

  The shared resource information 120 includes account identification information 121 indicating that it is shared resource information related to the client terminal 21 and individual shared resource information 122 related to the client terminal 11.

  The account identification information 121 is information for identifying the shared resource information 120 created for each client terminal 5.

  The individual shared resource information 122 includes shared resource identification information 123, family account information 124, family resource information 125, character code information 127, and the like.

  The shared resource identification information 123 is information for identifying the individual shared resource information 122, and is configured to be uniquely identified by being assigned a different ID each time the individual shared resource information 122 is created. Here, the shared resource identification information 123 is composed of an ID associated with the client terminal 5 that has requested creation of the shared resource information 120 and a name for facilitating the identification. The ID can be, for example, 20071001150032client11 @ relay-server1, and the name that facilitates identification can be, for example, workspace1.

  Thereby, since the user etc. can specify the individual shared resource information 122 based on the shared resource identification information 123, the content can be easily edited.

  FIG. 8 shows specific contents of the family resource information 125 described in the individual shared resource information 122a on the upper side of FIG. FIG. 9 shows specific contents of the family resource information 125 described in the individual shared resource information 122b on the lower side of FIG. As shown in FIGS. 8 and 9, the family resource information 125 is a collection of resource information 126 indicating the substance of resources such as files or folders (directories) held by the client terminal 5.

  For example, as shown in FIG. 8, each resource information 126 includes information on the name of a shared resource, account information of a client terminal 5 (owner client terminal) capable of operating the entity of the resource, and information on the resource. It consists of address information indicating the location of the entity and status information about the resource.

  The name of the resource to be shared is a name given to the resource when the resource is shared by a plurality of client terminals 5, and is described as name = “folderA”, for example. In the account information of the owner client terminal, an account for identifying the owner client terminal is described as, for example, owner = “client11@relay-server1.net”. The address indicating the actual location of the resource indicates the location where the shared resource is actually stored in the resource storage unit 603 (or the file server 6). For example, value = “c: / folderA” using a full path. And so on. The status information is information indicating the state of the resource, and is described as, for example, status = “ok”.

  The family account information 124 in FIG. 7 is a collection of information on accounts (for example, client11@relay-server1.net) of the client terminals 5 that share the resource entity indicated by the family resource information 125.

  In the example of the family resource information 125a in FIG. A client terminal (user client terminal) capable of indirectly operating the resource entity via the owner client terminal 11 is the client terminal described in the family account information 124 in the individual shared resource information 122a on the upper side of FIG. Are other than the owner client terminal 11. That is, in this example, the client terminal 21 is a user client terminal.

  As shown in FIGS. 8 and 9, a plurality of family resource information 125 can be described, and the owner client terminals described in each family resource information 125 may be different from each other. Therefore, the relationship between the owner client terminal and the user client terminal is not fixed, and any client terminal described in the family account information 124 can be an owner account terminal. In the following description, the client terminal described in the family account information 124 may be referred to as a shared member terminal.

  The character code information 127 in FIG. 7 indicates the character code that the name of the shared resource described in the resource information 126 should follow. For example, in the individual shared resource information 122a on the upper side of FIG. 7, the character code information 127 is described as charset = “us-ascii”. This means that in the individual shared resource information 122a (that is, when resource sharing between the client terminals 11 and 21 is performed), the name of the shared resource should follow a character code of only single-byte alphanumeric characters.

  On the other hand, in the individual shared resource information 122b on the lower side of FIG. 7, the character code information 127 is described as charset = “Shift_JIS”. This means that in the individual shared resource information 122b (that is, when resource sharing between the client terminals 21 and 31 is performed), the name of the shared resource should follow the so-called shift JIS character code. As described above, the present embodiment is configured such that a character code can be described for each group (for each individual shared resource information 122) having a different configuration of the resource sharing terminal.

  Each of the client terminals 11 and 21 which are shared member terminals in the individual shared resource information 122a on the upper side of FIG. 7 has three relay servers R1 and R2 constituting the relay group described by the relay group information 100a of FIG. , R3 is connected to the same LAN. Each of the client terminals 21 and 31 which are shared member terminals in the individual shared resource information 122b on the lower side of FIG. 7 is also connected to the same LAN as any of the three relay servers R1, R2 and R3. The client terminals 11, 21, 31 are client terminals in which the individual terminal information 111 is described as resource sharable terminals in the resource sharable terminal information 110a in the relay group.

  Each of the shared member terminals stores the shared resource information 120 having the individual shared resource information 122 having the above-described contents in the shared resource information database 604.

  Next, relay group generation and registration steps will be described with reference to sequence numbers 11 to 19 in FIG. The processing of sequence numbers 11 to 19 shown in FIG. 10 is generally performed as a network initial setting by a user and an operator.

  First, in the relay server R1, a method (createGroup method) for newly forming a relay group with the relay server R2 is executed by the operator. In this createGroup method, an account (relay-server2 @ net) of the relay server R2 that forms the relay group is specified.

  Then, the relay group information 100a is newly created in the relay server R1. At this time, an identification ID (0001 @ relay-server1) is assigned to the relay group information and described in the group identification information 101.

  Next, a message transmission command (MESSAGE method) is executed in the relay server R1, and a group-info message for the partner relay server R2 is transmitted to the external server 2 (sequence number 11). This message includes the identification ID of the relay group information created by the createGroup method.

  In this MESSAGE method, an account (sip: relay-server2 @ net) of the relay server R2 that is the message transmission destination is specified. The external server 2 acquires the global IP address of the relay server R2 by referring to the relay server account information database 203, and relays the group-info message from the relay server R1 to the relay server R2. The relay server R2 that has received the message returns an OK response to the relay server R1 via the external server 2.

  As described above, communication between each relay server 1 of the present embodiment is performed via the external server 2, and the same applies to the following. Therefore, in the following description, a specific description of communication processing via the external server 2 is omitted.

  Next, the relay server R1 transmits a server information transmission request message (request-server-info message) to the relay server R2 (sequence number 12). The relay server R2 that has received this message returns information (server-info) about itself together with the OK response to the relay server R1.

  On the contrary, the relay server R2 transmits a request-server-info message to the relay server R1 (sequence number 13), and the relay server R1 returns information (server-info) about itself to the relay server R2.

  As described above, by exchanging information about each other's servers, the information of both relay servers R1, R2 is described in the relay account information 102 included in the relay group information 100, and the relay group information database of each relay server R1, R2 505 is stored.

  Next, in the relay server R2, a method (addGroup method) for newly adding the relay server R3 to the previously created relay group (relay group composed of the relay servers R1 and R2) is executed by the operator. In this addGroup method, the account (relay-server3 @ net) of the relay server R3 to be joined and the identification ID (0001 @ relay-server1) of the relay group to be joined are designated.

  Then, the relay server R2 transmits a group-info message to the relay server R3 that is a partner to join (sequence number 14). This message includes the identification ID of the relay group specified by the addGroup method. Receiving this, the relay server R3 returns an OK response to the relay server R2. Next, server information is exchanged between the relay server R2 and the relay server R3 in exactly the same manner as described for the sequence numbers 12 and 13 (sequence numbers 15 and 16).

  Next, the relay server R2 transmits an update-group-info message notifying that the relay server R3 has joined the relay group to the relay server R1 (sequence number 17). Receiving this, the relay server R1 returns an OK response to the relay server R2. Thereafter, server information is exchanged between the relay server R3 and the relay server R1 (sequence numbers 18, 19).

  As described above, the relay group information 100 (specifically, the information indicated by reference numeral 100a in FIG. 6) that the three relay servers R1, R2, and R3 form a relay group is included in each relay server R1. , R2 and R3 are stored in the relay group information database 505.

  Although not shown in FIG. 10, the createGroup method is further executed in the relay server R3 without designating another relay server that forms the relay group. As a result, the relay group information 100b formed only from the relay server R3 is created, given an identification ID (0002 @ relay-server2), and stored in the relay group information database 505 of R3.

  Next, with reference to sequence numbers 21 to 29 in FIG. 11, the registration stage of the resource sharable terminal for the relay group will be described.

  In the relay server R1, a method for registering the client terminal 11 as a resource sharable terminal (addTerminal method) is executed by the operator in a relay group including three relay servers R1, R2, and R3. In this addTerminal method, an account of the client terminal 11 and an identification ID (0001 @ relay-server1) indicating the relay group of the registration destination are specified.

  When this addTerminal method is executed, the relay server R1 searches its own relay group information database 505. Then, the individual terminal information 111 of the client terminal 11 is added to the resource sharable terminal information 110 corresponding to the relay group information of the specified identification ID.

  Immediately thereafter, the relay server R1 specifies the relay group information 100 from the storage contents of the relay group information database 505 by the identification ID, and checks which relay server 1 is configured with the relay group. Then, it can be seen from the relay group information 100a in FIG. 6 that the target relay group is composed of itself (the relay server R1) and the two relay servers R2 and R3.

  Therefore, the relay server R1 first transmits an add-group-info message for requesting addition of a resource sharable terminal to the relay group to the relay server R2 (sequence number 21). This message includes the account of the target client terminal 11, the identification ID of the registration destination relay group, and the like. The relay server R2 that has received this adds the individual terminal information 111 of the client terminal 11 to the resource sharable terminal information 110 stored in the relay group information database 505, and then returns an OK response.

  Next, the relay server R1 transmits a group-info message to the client terminal 11 (sequence number 22). This message includes resource sharable terminal information 110 to which the individual terminal information 111 of the client terminal 11 is added. Receiving this, the client terminal 11 stores the content of the received resource sharable terminal information 110 in an appropriate storage unit.

  Subsequently, the relay server R1 also transmits an add-group-info message requesting addition of a resource sharable terminal to the relay group to the relay server R3 (sequence number 23). The relay server R3 that has received this adds the individual terminal information 111 of the client terminal 11 to the resource sharable terminal information 110 stored in the relay group information database 505, and then returns an OK response.

  As described above, the individual terminal information of the client terminal 11 as the resource sharable terminal is added to the resource sharable terminal information 110 in the relay group information 100 stored in the relay group information database 505 of the three relay servers R1, R2, and R3. 111 is registered.

  Next, in the relay server R2, a method (addTerminal method) for specifying the above-described relay group identification ID and registering the client terminal 21 as a resource sharable terminal is executed by the operator.

  Then, the relay server R2 searches its own relay group information database 505, and adds the individual terminal information 111 of the client terminal 21 to the resource sharable terminal information 110 corresponding to the relay group information specified by the identification ID.

  Next, the relay server R2 transmits an add-group-info message for requesting addition of a resource sharable terminal to the relay group to the relay server R1 (sequence number 24). This message includes the account of the target client terminal 21, the identification ID of the registration-destination relay group, and the like.

  Receiving this, the relay server R1 adds the individual terminal information 111 of the client terminal 21 to the resource sharable terminal information 110 stored in the relay group information database 505. Further, the relay server R1 is connected to the same LAN as itself, and transmits an add-group-info message to the client terminal 11 already stored as a resource sharable terminal (sequence number 24.1). The client terminal 11 that has received this message stores the individual terminal information 111 of the client terminal 21 in an appropriate storage means. Thereafter, the client terminal 11 returns an OK response to the relay server R1, and the relay server R1 that has received the response returns an OK response to the relay server R2.

  Further, the relay server R2 transmits a group-info message to the client terminal 21 (sequence number 25). This message includes resource sharable terminal information 110 to which the individual terminal information 111 of the client terminals 11 and 21 is added. Receiving this, the client terminal 21 stores the content of the received resource sharable terminal information 110 in an appropriate storage means.

  Subsequently, the relay server R2 also transmits an add-group-info message requesting addition of a resource sharable terminal to the relay group to the relay server R3 (sequence number 26). The relay server R3 that has received this adds the individual terminal information 111 of the client terminal 21 to the resource sharable terminal information 110 stored in the relay group information database 505, and then returns an OK response.

  As described above, the resource sharable terminal information 110 in the relay group information 100 stored in the relay group information database 505 of the three relay servers R1, R2, and R3 has the client terminals 11 and 21 as resource sharable terminals. The individual terminal information 111 is registered.

  Next, in the relay server R3, a method (addTerminal method) for specifying the above-described relay group identification ID and registering the client terminal 31 as a resource sharable terminal is executed by the operator.

  Then, the relay server R3 searches its own relay group information database 505, and adds the individual terminal information 111 of the client terminal 31 to the resource sharable terminal information 110 related to the relay group specified by the identification ID.

  Further, the relay server R3 transmits an add-group-info message for requesting addition of a resource sharable terminal to the relay group to the relay server R1 (sequence number 27). This message includes the account of the target client terminal 31, the identification ID of the registration destination relay group, and the like.

  Receiving this, the relay server R1 adds the individual terminal information 111 of the client terminal 31 to the resource sharable terminal information 110 stored in the relay group information database 505. Further, the relay server R1 is connected to the same LAN as itself, and transmits an add-group-info message to the client terminal 11 already stored as a resource sharable terminal (sequence number 27.1). The client terminal 11 that has received this message stores the individual terminal information 111 of the client terminal 31 in an appropriate storage means. Thereafter, the client terminal 11 returns an OK response to the relay server R1, and the relay server R1 that has received this returns an OK response to the relay server R3.

  Next, the relay server R3 transmits a group-info message to the client terminal 31 (sequence number 28). This message includes resource sharable terminal information 110 to which the individual terminal information 111 of the client terminal 31 is added. Receiving this, the client terminal 31 stores the content of the received resource sharable terminal information 110 in an appropriate storage means.

  Subsequently, the relay server R3 also transmits an add-group-info message requesting addition of a resource sharable terminal to the relay group to the relay server R2 (sequence number 29). Receiving this, the relay server R2 adds the individual terminal information 111 of the client terminal 31 to the resource sharable terminal information 110 stored in the relay group information database 505. Further, the relay server R2 is connected to the same LAN as itself, and transmits an add-group-info message to the client terminal 21 already stored as a resource sharable terminal (sequence number 29.1). The client terminal 21 that has received this message stores the individual terminal information 111 of the client terminal 31 in an appropriate storage means. Thereafter, the client terminal 21 returns an OK response to the relay server R2, and the relay server R2 that has received the response returns an OK response to the relay server R3.

  Thus, the client terminals 11, 21, and 31 as resource sharable terminals are added to the resource sharable terminal information 110 in the relay group information 100 stored in the relay group information database 505 of the three relay servers R1, R2, and R3. The individual terminal information 111 is registered.

  Further, although not shown in FIG. 11, an operation of adding the client terminals 12 and 22 to the relay group information (identification ID is 0001 @ relay-server1) is further performed. As a result, the individual terminal information 111 of the client terminals 11, 12, 21, 22, and 31 is registered as resource sharable terminals in the resource sharable terminal information 110 in the relay group information 100 (reference 110a in FIG. 6). reference). Further, in the relay server R3, an operation of adding the client terminals 31 and 32 to other relay group information (identification ID is 0002 @ relay-server2) is continuously performed.

  In addition, although the process which registers a client terminal as a resource sharable terminal was demonstrated in FIG. 11, the relay server 1 can also perform the process (deleteTerminal method) which removes registration as a resource sharable terminal of the client terminal 5. FIG. In this case, the individual terminal information 111 of the designated client terminal 5 is deleted from the resource sharable terminal information 110.

  Next, the operation when the resources of the client terminal 5 are actually shared will be described with reference to FIG. Here, a case where the file “Japanese.txt” in which the client terminal 21 can manipulate the entity is shared with the client terminal 11 in the relay group whose identification ID is 0001 @ relay-server1 will be described as an example. This file is stored in the folder “c: / document /” (hereinafter referred to as the entity storage folder 21f) created in the resource storage unit 603 of the client terminal 21.

  The user operates the client terminal 11 to designate a relay group whose identification ID is 0001 @ relay-server1, and then instructs the client terminal 11 to display the resource sharable terminals in the relay group. The client terminal 11 acquires information on the resource sharable terminals through communication with the relay server R1, and displays a list of resource sharable terminals in the designated relay group on the screen.

  Here, since the relay group with the identification ID 0001 @ relay-server1 is designated, the four client terminals 12, 21, 22, and 31 share resources based on the resource sharable terminal information 110a shown on the upper side of FIG. Displayed as a possible terminal. The user designates the displayed client terminal 21 as a terminal for sharing resources. In this explanation, only one terminal for sharing resources is specified, but a plurality or all of them may be specified from the list of displayed resource sharable terminals.

  Next, the client terminal 11 inquires the user of the character code of the resource name when sharing the resource. In the example of FIG. 12, the operating system executed on the client terminal 21 supports Shift JIS character codes, and can use Japanese characters in addition to alphanumeric characters including file and folder names. . On the other hand, the client terminal 11 is running an operating system different from that of the client terminal 21 and can use single-byte alphanumeric characters (us-ascii), but cannot use Japanese. It is assumed that the user designates a character code (us-ascii) of only single-byte alphanumeric characters in consideration of the above circumstances for the above inquiry.

  Then, the client terminal 11 transmits a shared resource creation request (createSharedResource command) to the relay server R1 (sequence number 31 in FIG. 12). This command includes the identification ID of the relay group, information on the designated client terminal 21, and information on the character code.

  Receiving this, the relay server R1 creates the shared resource information 120 and stores it in its own shared resource information database 506. The shared resource information 120 created at this time includes one individual shared resource information 122. The individual shared resource information 122 includes appropriately created shared resource identification information 123 and two client terminals 11 and 21. Family account information 124 in which the account is described, and character code information 127 indicating that the name of the shared resource conforms to us-ascii are included.

  Subsequently, the relay server R1 transmits an updateResource message to the other relay server R2 having the designated client terminal 21 under the control, and notifies the created shared resource information 120 (sequence number 31.1). The relay server R2 that has received the message stores the shared resource information 120 in its shared resource information database 506. In addition, the relay server R2 transmits an updateResource command to the designated client terminal 21, and notifies the shared resource information 120 (sequence number 31.1.1).

  The client terminal 21 that has received this updateResource command changes the shared resource information 120 stored in its own shared resource information database 604. Thereafter, an OK response is returned to the transmission source relay server R2. The relay server R2 that has received the OK response returns an OK response to the relay server R1, and the relay server R1 that has received the OK response returns an OK response to the client terminal 11.

  As described above, the shared resource identification information 123, the family account information 124, and the character code information 127 are described in the shared resource information 120 (individual shared resource information 122a) stored in the shared resource information database 506 of the relay servers R1 and R2. Will be. The same content is also described in the shared resource information 120 stored in the shared resource information database 604 of the client terminals 11 and 21.

  Next, when the user operates the client terminal 21 and executes the addResource method, processing for adding resource information (reference numeral 126 in FIG. 8) indicating the substance of the shared resource to the shared resource information 120 is performed. In this explanation, a file “Japanese.txt” is selected from the resource entities stored in the resource storage unit 603 of the client terminal 21 and specified to be shared with other client terminals 11. And

  Upon receiving this designation, the client terminal 21 first executes a ReadFile command to access the entity storage folder 21f and checks whether the designated file exists (sequence number 32). Next, the client terminal 21 refers to the character code information 127 of the shared resource information 120 registered in its own shared resource information database 604, and temporarily sets the name of the shared resource to “Japanese.txt”, which is the same as the name of the entity file. In such a case, it is checked whether the character code specified by the character code information 127 matches.

  In this example, us-ascii (single-byte alphanumeric characters only) is specified as the character code, so the name “Japanese.txt” including characters other than alphanumeric characters cannot be expressed by the character code. . Therefore, the client terminal 21 requests the user to specify a name of only single-byte alphanumeric characters as the name of the shared resource. On the other hand, it is assumed that the user designates the name “asciname.txt”, for example. Then, the client terminal 21 executes the ChangeFileName method, and changes the name of the shared resource to the designated name “asciname.txt”.

  Next, the client terminal 21 adds the resource information 126 to the shared resource information 120 (individual shared resource information 122a) stored in its own shared resource information database 604. The resource information 126 includes information on the name of the shared resource (“asciname.txt”) determined as described above, and information on the location of the shared resource (“c: /document/Japanese.txt”). )).

  Next, the client terminal 21 transmits a shared resource addition request (addResource command) to the relay server R2 (sequence number 33). This shared resource addition request includes information on the name of the shared resource and information on the location of the entity of the shared resource. Receiving this shared resource addition request, the relay server R2 updates the shared resource information 120 stored in its own shared resource information database 506, and adds the resource information 126 relating to “asciname.txt”.

  Then, the relay server R2 transmits an addResource message to the relay server R1 to which the user client terminal 11 is connected (sequence number 33.1). The relay server R1 that has received this message updates the shared resource information 120 stored in its own shared resource information database 506 in the same manner as the relay server R2. Further, the relay server R1 transmits an addResource command to the user client terminal 11 under its control to notify the addition of the shared resource information 120 (sequence number 33.1.1).

  Each user client terminal 11 that has received the addResource command changes the shared resource information 120 stored in its own shared resource information database 604. Thereafter, an OK response is returned to the relay server R1 as the transmission source. The relay server R1 that has received the OK response returns an OK response to the relay server R2, and the relay server R2 that has received the OK response returns an OK response to the client terminal 21. Through the above processing, the resource information 126 (see FIG. 8) related to “asciname.txt” (the actual file name is “Japanese.txt”) is added to the shared resource information 120.

  Next, a process in which the user client terminal 11 opens the registered “asciiname.txt” will be described with reference to sequence numbers 35 to 3.2.1.1.1 in FIG.

  The client terminal 11 transmits a file open request (OpenFile command) to the relay server R1 (sequence number 35). This OpenFile command includes the designation of the owner client terminal (that is, the client terminal 21) and the designation of the shared resource to be opened (“asciname.txt”). As described above, the operating system of the client terminal 11 cannot use Japanese, but since the name of the shared resource is composed of only single-byte alphanumeric characters, there is no display defect such as garbled characters and the shared resource. Can be specified smoothly.

  The relay server R1 that has received the OpenFile command transmits a connection request (INVITE method) to the relay server R2 (sequence number 35.1). The relay server R2 that has received the connection request transmits a file open request (OpenFile) to the client terminal 21 (sequence number 35.1.1). The client terminal 21 that has received the file open request confirms that the target resource can be operated, returns an OK response to the relay server R2, and the relay server R2 returns an OK response to the relay server R1.

  The relay server R1 that has received the OK response transmits a MediaSession command to the relay server R2, thereby establishing a communication path between the relay servers R1 and R2 (sequence number 35.2). The relay server R2 that has received the MediaSession command transmits the MediaSession command to the client terminal 21, thereby establishing a communication path between the relay server R2 and the client terminal 21 (sequence number 35.2.1). Thereafter, the client terminal 21 executes the ReadFile command (sequence number 35.2.1.1.1), reads the target resource from the entity storage folder 21f, and transmits it to the relay server R2. Note that the name of the entity of the read file is “Japanese.txt” as described above. The target resource is transferred from the relay server R2 to the relay server R1, and further transferred to the client terminal 11. As described above, the actual data of the shared resource is transmitted to the client terminal 11, and the client terminal 11 performs a process of opening the data.

  Next, with reference to FIG. 14, a case where the client terminal 21 shares the file “inventory management.xls” that can manipulate the entity with the client terminal 31 will be described as an example. This file is stored in the folder “c: / document /” (entity storage folder 21f) created in the resource storage unit 603 of the client terminal 21 in the same manner as the file “Japanese.txt” described in the above example. ing.

  The user operates the client terminal 31 and gives an instruction to share resources with the client terminal 21. On the other hand, the client terminal 31 inquires the user of the character code of the resource name when sharing the resource, as in the previous description. In this example, similarly to the client terminal 21, the operating system of the client terminal 31 can use the shift JIS character code. It is assumed that the user designates a shift JIS character code (Shift_JIS) in consideration of the above situation for the above inquiry.

  Then, the client terminal 31 transmits a shared resource creation request (createSharedResource command) to the relay server R3 (sequence number 34 in FIG. 14). This message includes information on the designated client terminal 21 and information on the designated character code. Subsequent processing (sequence numbers 34 to 34.1.1) is substantially the same as sequence numbers 31 to 31.1.1 in FIG. As described above, the shared resource identification information 123, the family account information 124, and the character code information 127 are described in the shared resource information 120 (individual shared resource information 122b) stored in the shared resource information database 506 of the relay servers R3 and R2. Will be. The same content is also described in the shared resource information 120 stored in the shared resource information database 604 of the client terminals 31 and 21.

  Next, when the user operates the client terminal 21 and executes the addResource method, processing for adding resource information to the shared resource information 120 is performed. In this explanation, the file “inventory management.xls” is selected from the resource entities stored in the resource storage unit 603 of the client terminal 21 and specified to be shared with other client terminals 31. And Further, it is assumed that the user designates the name “stock management.xls”, which is the same as the actual file name, as the name for sharing the file.

  Upon receiving this designation, the client terminal 21 first executes a ReadFile command to access the entity storage folder 21f and checks whether the designated file exists (sequence number 35). Next, the client terminal 21 refers to the character code information 127 of the shared resource information 120 registered in its own shared resource information database 604, and if the name of the shared resource is “inventory management.xls”, the character It is checked whether the character code specified by the code information 127 matches.

  In this example, since Shift JIS is specified as the character code, the name “inventory management.xls” can be expressed by the character code. Therefore, the client terminal 21 adds the resource information 126 to the shared resource information 120 (individual shared resource information 122a) stored in its own shared resource information database 604. The resource information 126 includes information on the name of the designated shared resource (“stock management.xls”), information on the location of the entity of the shared resource (“c: / document / stock management.xls”), It is included.

  Next, the client terminal 21 transmits a shared resource addition request (addResource command) to the relay server R2 (sequence number 36). This shared resource addition request includes information on the name of the shared resource and information on the location of the entity of the shared resource. The subsequent processing (sequence numbers 36.1 and 36.1.1) is substantially the same as sequence numbers 33.1 and 33.1.1 in FIG.

  As described above, the shared resource information 120 stored in the shared resource information database 604 of the client terminals 31 and 21 describes the resource information 126 related to the shared resource named “inventory management.xls”. Similar resource information 126 is also described in the shared resource information 120 stored in the shared resource information database 506 of the relay servers R3 and R2. The shared resource added in this way can be opened by the user client terminal 31 by designating the resource name (“stock management.xls”) at the time of sharing. The processing at this time is substantially the same as that described with reference to FIG.

  Next, details of the operation of the client terminal 5 will be described with reference to FIG. FIG. 15 is a flowchart showing the operation of the client terminal 5 in the relay communication system of this embodiment. Note that the flowchart shown in FIG. 15 substantially corresponds to the processing after sequence number 32 in the client terminal 21 of FIG. 12 and the processing after sequence number 35 in the client terminal 21 of FIG.

  As shown in FIG. 15, the client terminal 5 waits until an instruction to add a shared resource is issued (S101). When an instruction to add is issued, the client terminal 5 inquires the user about a resource to be added (S102). In response to this query, the user specifies the path of the resource (substance file) that he wants to share. At this time, the client terminal 5 actually accesses the designated path and confirms whether or not the actual file actually exists.

  Next, the client terminal 5 inquires of the user whether or not it is desired to particularly specify a name for sharing the specified resource (S103). In response to this inquiry, when the user selects not to specify a name, the client terminal 5 automatically creates a shared resource name from the path specified in the process of S102 (S104). For example, when the path of the entity file is “c: /document/Japanese.txt”, “Japanese.txt” obtained by removing the description of the folder portion from the path is adopted as the name of the shared resource. If the user specifically specifies a name in response to the query in S103, the process in S104 is skipped and the name specified by the user is used as the shared resource name.

  Next, the client terminal 5 checks whether or not the name of the shared resource determined as described above can be handled with the character code specified by the character code information 127 (S105). If the name of the shared resource does not match the character code, the user is notified that the character code of the name cannot be used and the shared resource name needs to be specified again (S106). Thereafter, the input of the shared resource name is waited (S107), and if it is input, the process returns to the determination of S105 again to check again whether or not the input shared resource name matches the character code of the character code information 127. .

  If it is determined in S105 that the shared resource name matches the character code, the resource selected by the user in S102 is added to the shared resource information 120 with the shared resource name (S108). After that, the shared resource information update command is transmitted to the relay server 1 that is under its control (S109).

  As described above, the relay server 1 of this embodiment includes the relay group information database 505, the shared resource information database 506, and the control unit 503. The relay group information database 505 stores information on relay groups (relay group information 100) including other relay servers that can be connected to each other. The shared resource information database 506 stores shared resource information 120 when resources are shared among a plurality of client terminals 5 in the relay group. The shared resource information 120 includes family resource information 125 that is information of the resource, character code information 127 that is information of a character code used in a name assigned to the resource, and a client terminal that shares the resource. Information of an account of a certain resource sharing terminal (family account information 124). The control unit 503 includes a character code information management unit 511 and an instruction relay unit 512. For example, as shown in FIG. 12, when the character code of the name given to the resource is specified by the client terminal 11, the character code information management unit 511 of the relay server R1 shares the character code information 127 with the shared code. Record in the resource information 120. As shown in FIG. 13, when the client terminal 11 designates a resource and instructs an operation, the instruction relay unit 512 of the relay server R1 sets the client terminal 21 capable of operating the entity of the designated resource. The instruction is relayed to the relay server R2 that is under control.

  As a result, the shared resource can be indirectly operated by the client terminal 5 via the relay server 1. In addition, since the character code of the name assigned to the shared resource can be managed based on the character code information 127, the resource name can be prevented from being garbled, and the resource can be specified and operated easily and reliably.

  In addition, the relay server 1 of the present embodiment is configured such that the character code information 127 in the shared resource information 120 can be described for each group (each individual shared resource information 122) having a different configuration of the resource sharing terminal. Yes.

  Thereby, the character code can be changed according to the configuration of the resource sharing terminal, and the character code of the resource name can be managed appropriately.

  In the present embodiment, when the client terminal 5 shares a resource that can operate the entity among a plurality of client terminals 5, the character code information 127 is used to specify the name to be given to the resource. Only those that match the specified character code are accepted (S105 in FIG. 15).

  As a result, it is possible to prevent a character code that cannot be handled by the client terminal from being used as a resource name and causing garbled characters.

  Although the preferred embodiment of the present invention has been described above, the above configuration can be modified as follows, for example.

  In the above embodiment, communication is performed between the relay servers 1 via the external server 2 that is a SIP server. Instead, the configuration is changed so that communication is performed directly between the relay servers 1 without using the external server 2. can do.

  The designation of the character code is not limited to us-ascii and Shift_JIS, and for example, euc-jp, UTF-8, UTF-16, etc. can be adopted.

The network block diagram of the relay communication system which concerns on one Embodiment of this invention. The functional block diagram of an external server. The functional block diagram of a client terminal. The functional block diagram of a relay server. The figure which shows the relationship between a client terminal, a relay server, and an external server. The figure which shows the content of relay group information. The figure which shows the content of shared resource information. The figure which shows the detail of the content of the family resource information in the separate shared resource information of the upper side of FIG. The figure which shows the detail of the content of the family resource information in the separate shared resource information of the lower side of FIG. The sequence diagram which shows the communication processing which creates a relay group. The sequence diagram which shows the communication processing which registers a client terminal as a resource sharable terminal in a relay group. The sequence diagram which shows the communication process which creates the shared resource information by designating the character code of the name at the time of sharing, and registers shared resource information. The sequence diagram which shows the example of a communication process in the case of opening a shared resource. FIG. 13 is a sequence diagram showing communication processing for creating shared resource information by specifying a character code different from that in FIG. 12 and registering shared resource information. The flowchart which shows the registration process of the shared resource performed in a client terminal.

Explanation of symbols

1 (R1 to R4) Relay server 2 External server 5 (11, 12, 21, 22, 31, 32, 41, 42) Client terminal 120 Shared resource information 124 Family account information 126 Resource information 127 Character code information 503 Control unit 505 Relay group information database (relay group information registration section)
506 Shared resource information database (shared resource information registration unit)
511 Character code information management unit 512 Instruction relay unit

Claims (3)

A relay group information registration unit that stores information on relay groups including other relay servers that can be connected to each other;
When a resource is shared among a plurality of client terminals in the relay group, the resource terminal is a client terminal that shares information on the resource, information on a character code used in a name assigned to the resource, and the resource. A shared resource information registration unit for storing shared resource information including resource sharing terminal account information,
A control unit;
With
The controller is
A character code information management unit that records information of the character code in the shared resource information by designating a character code of a name given to the resource;
An instruction relay unit that relays the instruction to a client terminal capable of operating the entity of the specified resource or a relay server under the client terminal by instructing an operation by specifying the resource by the client terminal;
Equipped with a,
The client terminal accepts designation of a name to be given to the resource only if it matches the character code when the resource that can operate the entity is shared among a plurality of client terminals. Relay server. The relay server according to claim 1,
In the shared resource information, the character code information is configured to be described for each group having a different configuration of the resource shared terminal. Multiple relay servers,
Multiple client devices,
With
The relay server is
A relay group information registration unit that stores information on relay groups including other relay servers that can be connected to each other;
When a resource is shared among a plurality of client terminals in the relay group, information on the resource, information on a character code used in a name assigned to the resource, and a client terminal that shares the resource A shared resource information registration unit for storing shared resource information including information on an account of a certain resource sharing terminal;
A control unit;
With
The controller is
A character code information management unit that records information of the character code in the shared resource information by designating a character code of a name given to the resource;
An instruction relay unit that relays the instruction to a client terminal that can operate the entity of the specified resource or a relay server under the client terminal by instructing an operation by specifying the resource by the client terminal;
Equipped with a,
The client terminal accepts designation of a name to be given to the resource only if it matches the character code when the resource that can operate the entity is shared among a plurality of client terminals. Relay communication system.

Images