JP4453698B2 - Relay server - Google Patents

Description

  The present invention relates to a relay server and a relay communication system that enable communication with a terminal in another local area network (LAN) beyond a wide area network (WAN). In particular, the present invention relates to a technique for operating resources held by a terminal in another LAN from a terminal in a certain LAN.

  There is a communication technology called VPN (Virtual Private Network). If this communication technology is used, other remote LANs can be used as if they were directly connected networks. For example, it is possible to communicate over the Internet between terminals connected to a plurality of branch office LANs provided in each region.

  For this type of technology, various systems have been proposed so far (for example, Patent Document 1).

JP 2002-217938 A

  However, this type of system tends to be a rigid system because of the virtual network construction. For this reason, it is not easy to construct a system with extensibility and flexibility, and the systems proposed so far also have advantages and disadvantages in function and cost.

  For example, within the same LAN, resources are usually managed under the same protocol, and the system configuration is not so complicated, so that resources can be easily shared among a plurality of terminals. However, if the communication system spans multiple LANs across the WAN, you want to share resources such as folders and files among multiple terminals, or delete files held by other terminals from one terminal Even if you think, it can not be easily handled. This is even more true if the protocols used in each LAN are different.

  Further, although resources held by each terminal constantly change due to deletion or movement, it is not easy to dynamically cope with these changes. Furthermore, it is not easy to dynamically respond to changes in the status of each terminal that holds those resources.

  Therefore, in view of the above-described problems, the present invention shares resources with a necessary partner when each terminal is necessary or operates resources even between terminals connected to different LANs and managed by different protocols. An object of the present invention is to provide a relay communication system that can be operated easily and a relay server used in the system. The purpose of the present invention is to provide a dynamic relay communication system that is excellent in expandability and flexibility, and that can cope with resource movement and changes in the status of each terminal.

  In order to solve the above-mentioned problem, the invention described in claim 1 is a relay server that is connected to a LAN and can communicate with a relay server connected to another LAN, and is connected to the same LAN. An account information registration unit for storing account information including information on the client terminals that are present, a relay group information registration unit for storing relay group information including information on a group of relay servers that permit mutual communication, resource information, Stored in the account information registration unit, a shared resource information registration unit that stores shared resource information including information on client terminals that share the resource and information on owner client terminals that can operate the entity of the resource. Client devices connected to other LANs based on the shared resource information. A resource operation relay unit that relays an operation for the resource based on the relay group information when receiving an operation instruction for a resource that can be operated by a second terminal, and the shared resource information registration unit includes one resource When a registration request is received from a plurality of owner client terminals, information on the plurality of owner client terminals is stored in association with the one resource.

  According to a second aspect of the present invention, in the relay server according to the first aspect, the resource operation relay unit operates the one resource with respect to any owner client terminal of the plurality of owner client terminals. Means for relaying.

  According to a third aspect of the present invention, in the relay server according to the second aspect, the resource operation relay unit is an owner client terminal that cannot operate the entity of the one resource among the plurality of owner client terminals. On the other hand, it includes means for not relaying an operation for the one resource.

  According to a fourth aspect of the present invention, in the relay server according to the third aspect, the shared resource information registering unit, when all of the plurality of owner client terminals are deleted from the relay group information, Means for deleting information relating to the one resource from the.

  According to the first aspect of the present invention, resources shared between terminals connected to different LANs may be registered from different terminals. In this case, it is possible to add information on different terminals to the resource information.

  According to the second aspect of the present invention, when an operation instruction for a resource is given from a certain terminal, the relay server to which the terminal is connected gives a resource to any one of a plurality of terminals capable of operating the resource entity. It is possible to relay an operation instruction for.

  In the invention according to claim 3, when any one of a plurality of terminals capable of operating the resource entity is logged off, or excluded from a group of terminals sharing the resource. . In these cases, when an operation instruction for a resource is given from a certain terminal, the relay server to which the terminal is connected can not relay the operation instruction for the resource to any of the terminals described above. is there.

  In the invention according to claim 4, all of the plurality of terminals capable of operating the resource entity may be excluded from the group of terminals sharing the resource. In this case, it is possible to delete the resources possessed by all of the plurality of terminals from the resources shared between the terminals.

<Overall configuration of relay communication system>
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 illustrates an overall configuration of a relay communication system according to the present invention. As shown in FIG. 1, the relay communication system is composed of a plurality of LANs connected to a WAN. The relay communication system includes an external server S, a relay server R, a communication device T, a file server F, and the like. Here, the embodiment using the external server S is illustrated, but a form in which the external server S is not used and the relay server R communicates directly may be used. As a communication protocol, SIP (Session Initiation Protocol) can be suitably used, and this embodiment will be described using this.

  A WAN (Wide Area Network) is a network that connects different LANs. In the present embodiment, the Internet is exemplified as the WAN. However, the present invention is not necessarily limited to this, and other similar networks can be applied.

  A LAN (Local Area Network) is a relatively small network constructed in a limited place. There are a plurality of LANs, and each LAN is constructed in a physically separated place. For example, in this embodiment, LAN 1 is constructed in branch office A in Tokyo, and LANs 2, 3, and 4 are constructed in branch offices B, C, and D in Osaka, Nagoya, and Fukuoka, respectively. . These four LANs 1, 2, 3, 4 are connected to the Internet, which is a global network. Of course, the number of LANs is not limited to four as long as it is plural.

<External server>
The external server S is a facility used for communication between the relay servers R arranged in each LAN, and is installed on the Internet. The external server S here has a function as a SIP server. Specifically, the external server S 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 R. The number of external servers S is not limited to one, and a plurality of external servers S may function in a distributed manner. Note that when a protocol other than SIP is used, it is only necessary to directly control communication between the relay servers R based on the protocol, and the external server S functioning as a SIP server is not necessarily provided.

  FIG. 2 shows a functional block diagram of the external server S. As shown in FIG. 2, the external server S includes a WAN interface 201, a control unit 202, a relay server account information database (DB) 203, and the like.

  The WAN interface 201 is an interface that communicates with each device such as the relay server R connected to the Internet using a global IP address. The relay server account information DB 203 is a database that manages the account of the relay server R 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 protocols such as TCP / IP, UDP, and SIP. For example, the control unit 202 receives an account of each relay server R transmitted from each relay server R and registers it in the relay server account information DB 203, various SIP methods and responses transmitted from the relay server R, and the like. A process of relaying the communication data to the other relay server R is executed.

<Communication device>
The communication device T is a client terminal that can be directly operated by a user (hereinafter simply referred to as a client terminal T). For example, a personal computer (PC) used for daily work by the user corresponds to the client terminal T. In general, there are a large number of client terminals T in the LAN. In this embodiment, client terminals 1A and 1B are connected to LAN 1, client terminals 2A and 2B are connected to LAN 2, and client terminals 3A and 3B are connected to LAN 3. Shows a case where client terminals 4A and 4B are connected to the LAN 4, respectively. Each client terminal T is assigned a private IP address that is uniquely managed only within the same LAN.

  FIG. 3 shows a functional block diagram of the client terminal T. As shown in FIG. 3, the client terminal T includes a LAN interface 601, a control unit 602, a resource storage unit 603, a shared resource information database (DB) 604, a display unit 605, and the like.

  The LAN interface 601 is an interface that communicates with each device such as the relay server R and the file server F connected to the same LAN using a private IP address. The resource storage unit 603 stores resource entities such as files and folders that can be operated by the client terminal T. The shared resource information database (DB) 604 includes shared information held by each client terminal T, including information on resources held by the client terminal T and account information of the client terminals T sharing the resource. The shared resource information 120 describing the resource information is stored. The display unit 605 visually displays the contents of the relay group information 100 and the shared resource information 120. The control unit 602 is a processing unit that controls various communications performed via the LAN interface 601 and controls communication processing according to protocols such as TCP / IP, UDP, and SIP.

  For example, the control unit 602 controls the process of moving, changing, or deleting resources stored in the resource storage unit 603, the process of receiving the shared resource information 120 from the relay server R, and the content of the shared resource information 120. A process of displaying in cooperation with the display unit 605, a process of receiving a resource operation instruction and determining whether or not the resource can be directly operated, a process of registering the shared resource information 120 in the relay server R, and the like are executed. .

<Relay server>
One relay server R is arranged for each LAN. Here, a relay server R1 is arranged in LAN1, a relay server R2 is arranged in LAN2, a relay server R3 is arranged in LAN3, and a relay server R4 is arranged in LAN4.

  The relay server R is connected not only to the LAN but also to the Internet, can communicate with each client terminal T connected to the same LAN, and is connected to another LAN via the external server S. Communication with the server R is possible. Therefore, each relay server R is assigned a global IP address in addition to a private IP address.

  FIG. 4 shows a functional block diagram of each relay server R. As shown in FIG. 4, the relay server R includes a LAN interface 501, a WAN interface 502, a control unit 503, an account information database (DB) 504, a relay group information database (DB) 505, a shared resource information database (DB) 506, and the like. It has.

  The LAN interface 501 is an interface that communicates with a client terminal T or the like connected to the LAN using a private IP address. For example, in the case of LAN1, the relay server R1 communicates with the client terminals 1A and 1B using the LAN interface 501. The WAN interface 502 is an interface that communicates with each device such as an external server S connected to the Internet using a global IP address. In the present embodiment, the relay server R is configured to include the WAN interface 502. However, the router may be connected to the Internet, and the relay server R may be installed under the router.

  The account information DB 504 is a database that manages the account of the client terminal T that has requested registration in association with the private IP address. The relay group information DB 505 is a database that manages the relay group information 100 related to the client terminal T registered in the account information DB. The shared resource information DB 506 is a database that manages the shared resource information 120 related to the client terminal T registered in the account information DB.

  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. For example, the control unit 503 transmits the account of its own device to the external server S, requests registration, and registers the account transmitted from the client terminal T connected to the same LAN in the account information DB 504. A process of creating the relay group information 100 and storing it in the relay group information DB 505, a process of creating the shared resource information 120 and storing it in the shared resource information DB 506, and the like are executed.

  Next, the relay group information 100 and the shared resource information 120 that are information handled in the relay communication system will be described.

<Relay group information>
The relay group information 100 records information of the relay servers R that permit mutual connection, and is stored in the relay group information DB 505 of each relay server.

  The relay group information 100 is normally set at the initial stage of the relay communication system. In the relay group information 100, when any of the relay group information 100 is changed, a change notification setting for automatically updating the contents is performed, and the account of the relay server R or the client terminal T changes. Even so, it can respond dynamically.

  An example of the relay group information 100 is shown in FIG. FIG. 5 shows the relay group information 100 created by exchanging information between the three relay servers R1, R2, and R3 based on the relay server R1 and stored in the respective relay group information DB 505. The relay group information 100 there is composed of one group identification information 101 and information (relay account information) 102 of three relay servers R1, R2, and R3 that permit mutual connection. In FIG. 1, the LAN 4 (relay server R 4) is not connected to the network because the account is not registered here, and cannot participate in the communication service described here.

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

  The relay account information 102 includes an account of the relay server R and information such as an account of the client terminal T connected to the same LAN as the relay server R and registered in the relay server R. Each account of the relay server R is given a specific name, so that the user can be easily identified. Similarly, specific names are assigned to the accounts of the client terminals T, respectively. For example, in the case of the relay account information 102 of the relay server R1 (Relay-server1), the name (branch A) 104 is assigned to the account (relay-server1 @ net) of the relay server R1. Each account (for example, user1A @ account) and its name (for example, terminal1A) 105 of the client terminal T connected to the same LAN is given. Reference numeral 103 denotes identification data indicating the affiliation of the client terminal T, such as “sales department” or “development department”.

  As described above, the relay group information 100 is created for each relay group information so as to be uniquely identifiable, and includes a group of relay account information 102 that permits mutual connection. Since the relay account information 102 includes an account of each relay server R and an account of the client terminal T registered and registered in the same LAN, see the relay group information 100. Then, it is possible to know which LANs and which LANs are grouped, and what relay servers R and client terminals T are registered in those LANs.

<Shared resource information>
The shared resource information 120 is information including information on a plurality of client terminals T that share resources such as files and folders with each other, and information on shared resources, and is shared resource information DB 506 of the relay server or client terminals. This is information stored in the T shared resource information DB 604.

  An example of the shared resource information 120 is shown in FIG. FIG. 6 illustrates the shared resource information 120 stored in the shared resource information DB 604 of the client terminal 1A. The shared resource information 120 includes account identification information 121 indicating that the shared resource information 120 is related to the client terminal 1A, and individual shared resource information 122 related to the client terminal 1A. The individual shared resource information 122 includes shared resource identification information 123, family account information 124, family resource information 125, and the like. In FIG. 6, since a single resource sharing group related to the client terminal 1 </ b> A is formed, the shared resource information 120 includes a single individual shared resource information 122. However, there may be a case where a plurality of different resource sharing groups are formed. In this case, the shared resource information 120 includes a plurality of individual shared resource information 122.

  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. Therefore, the user or the like can specify the individual shared resource information 122 by the shared resource identification information 123, and can easily edit the contents thereof.

  The family resource information 125 is a collection of resource information 126 indicating the substance of resources such as files and folders held by the client terminal T. Each resource information 126 includes information on the name of a shared resource entity (for example, resource name = “file002.pdf”) and account information of a client terminal T (owner client terminal) capable of operating the resource entity. (For example, owner = “user2A @ account”) and address information (for example, value = “c: /file002.pdf”) indicating the location of the entity of the resource.

  The family account information 124 is a collection of accounts (for example, user1A @ account) of the client terminals T that share the resource entity indicated by the family resource information 125. The family account information 124 is composed of an owner client terminal T and a client terminal T (user client terminal) capable of indirectly manipulating resource entities via the owner client terminal. The user client terminal T is a client terminal T that cannot directly operate a resource entity but can indirectly operate a resource via the owner client terminal T.

  By referring to the shared resource information 120 configured as described above, the client terminal T sharing the resource can be specified, and the type and location of the resource can be known.

  The shared resource information 120 is registered by the client terminal T, for example. That is, the client terminal T transmits information on resources (resource information 126) that can be directly or indirectly operated by the client terminal T and information on accounts of other client terminals T that share the resource to the same LAN. Means for registering with the relay server R connected to. Therefore, the operator can easily create and change the shared resource information 120 through the display unit 605 of the client terminal T.

<Operations for the same resource registered from different terminals>
{Initial relay group information and shared resource information}
In the relay communication system shown in FIG. 1, resources shared between client terminals T connected to different LANs may be registered together from different client terminals T. In this case, how the operation instruction of the resource is performed will be described.

  7, 8, and 11 are sequence diagrams of communication processing according to the present embodiment. S shown in FIGS. 7, 8, and 11 represents step S of the sequence, and time has passed in the order of FIGS.

  5 and 6 are diagrams showing the contents of the relay group information 100P1 and the shared resource information 120P1 in the initial state (P1) immediately before the sequence shown in FIG. 7 is started.

  In the relay group information 100P1, state information (status) 106P1 of the relay server R and state information (status) 107P1 of the client terminal T are described. For example, “ok” described in the status information of the relay server R1 indicates that the relay server R1 can be operated. Further, “logon” described in the status information of the client terminals 1A and 1B indicates that the client terminals 1A and 1B are logged on.

  The individual shared resource information 122P1 describes resource status information (status) 127P1. For example, “ok” described in the status information “file002.pdf” indicates that the entity “file002.pdf” is accessible.

  The family resource information 125P1 indicates that the client terminals 1A and 1B have an entity “file001.pdf”. Here, as the account information of the owner client terminal T, the client terminals 1A and 1B are collectively described. However, the entity information of the resources held by the client terminals 1A and 1B can be described separately.

  Further, “netpc: /folder/file001.pdf” is described as address information indicating the location of the resource entity. “netpc” represents a network personal computer. In the present embodiment, “netpc” represents the file server F installed in the LAN 1 shown in FIG. That is, it is shown that both the client terminals 1A and 1B register “file001.pdf” owned by the file server F in the shared resource information 120P1.

  Next, the sequence of the communication process shown in FIG. 7 will be described based on the relay group information 100P1 and the shared resource information 120P1 in the initial state (P1) shown in FIGS.

  When the client terminal 2A receives an instruction to copy “file001.pdf” from the user, the client terminal 2A transmits a copy request (CopyFile command) to the relay server R2 (step S1). The relay server R2 that has received the copy request selects the owner client terminals 1A and 1B that hold “file001.pdf” to be copied based on the shared resource information 120P1. Then, the relay server R1 to which the owner client terminals 1A and 1B are connected is selected based on the relay group information 100P1.

  The relay server R2 transmits a connection request (INVITE method) to the selected relay server R1 via the external server S (step S1.1). The relay server R1 that has received the connection request selects the client terminal 1A from among the client terminals 1A and 1B, and transmits a copy request to the client terminal 1A (step S1.1.1).

  Here, as a method for the relay server R1 to select one of the client terminals 1A and 1B, the following method is conceivable. For example, in the relay server R1, which client terminal T is preferentially selected may be set in advance. Alternatively, any client terminal T may be automatically selected using a random number.

  The client terminal 1A that has received the copy request transmits an OK response to the relay server R1 if the operation of “file001.pdf” to be copied is possible. The relay server R1 that has received the OK response transfers the OK response to the relay server R2.

  The relay server R2 that has received the OK response transmits a Mediasession command to the relay server R1. Here, a communication path is established between the relay servers R1 and R2 (step S1.2). The relay server R1 that has received the Mediation command transmits a file acquisition request (GetFileData command) to the client terminal 1A (step S1.2.1). The client terminal 1A that has received the file acquisition request acquires “file001.pdf” to be acquired from the file server F installed in the LAN 1 shown in FIG. 1 and transmits it to the relay server R1. Then, “file001.pdf” is transmitted to the client terminal 2A via the relay servers R1 and R2 (FileTransfer command).

  When the series of communication processes is completed, the relay server R2 transmits a disconnection request (BYE method) to the relay server R1 in order to disconnect the established communication path (step S2).

<Responding to changes in client terminal status>
{P2 relay group information and shared resource information}
The relay communication system shown in FIG. 1 can flexibly cope with a change in the situation of each client terminal T connected to a different LAN. A response to the situation change of each client terminal T will be described below.

  First, the communication process sequence shown in FIG. 8 will be described. Upon receiving a logoff instruction from the user, the client terminal 1A transmits a logoff registration request (REGISTER method) to the relay server R1 (step S3). The relay server R1 that has received the logoff registration request uses the relay group information 100P1 and the shared resource information 120P1 in the initial state (P1) shown in FIGS. 5 and 6 as the relay group in the state P2 shown in FIGS. Change to information 100P2 and shared resource information 120P2. The contents of this change will be described in detail later.

  The relay server R1 transmits a change information notification (NOTIFY method) to the relay server R2 (step S3.1). The relay server R2 that has received the relay group information 100P2 and the shared resource information 120P2 transmits a status information change request (UpdateResourceStatus command) to the client terminal 2A (step S3.1.1).

  Similarly, the client terminals 3A and 1B receive the status information change request from the relay servers R3 and R1, respectively (step S3.2, step S3.2.1, step S3.3). When Steps S3 to S3.3 are completed, the relay server R1 transmits an OK response to the client terminal 1A. Here, the client terminal 1A is logged off.

  9 and 10 are diagrams showing the contents of the relay group information 100P2 and the shared resource information 120P2 in the P2 state. As a difference between the relay group information 100P2 shown in FIG. 9 and the relay group information 100P1 shown in FIG. 5, in the relay group information 100P2, the state information of the client terminal 1A is changed from “logon” to “logoff”. has been edited. This indicates that the client terminal 1A is logged off in the state of P2.

  However, there is no difference between the shared resource information 120P2 shown in FIG. 10 and the shared resource information 120P1 shown in FIG. In the state of P2, the client terminal 1A is logged off. However, since the client terminal 1A may be logged on again, the client terminal 1A is not deleted from the family account information 124P2 or the family resource information 125P2. In addition, since the client terminal 1B is logged on, it is possible to access the entity “file001.pdf” through the client terminal 1B, and “ok” is described in the status information of “file001.pdf”. Yes.

  Next, the communication processing sequence after step S4 shown in FIG. 8 will be described based on the relay group information 100P2 and the shared resource information 120P2 in the P2 state shown in FIGS.

  Upon receiving an instruction to open a file “file001.pdf” from the user, the client terminal 2A transmits a file open request (OpenFile command) to the relay server R2 (step S4). The relay server R2 selects the owner client terminals 1A and 1B having “file001.pdf” based on the shared resource information 120P2. Then, the relay server R1 to which the owner client terminals 1A and 1B are connected is selected based on the relay group information 100P2.

  The relay server R2 transmits a connection request (INVITE method) to the selected relay server R1 via the external server S (step S4.1). The relay server R1 can only select the client terminal 1B among the client terminals 1A and 1B, and transmits a file open request to the client terminal 1B (step S4.1.1).

  Here, the relay server R1 can only select the client terminal 1B among the client terminals 1A and 1B. In the state of P2, the owner client terminal T of “file001.pdf” is selected by the client terminals 1A and 1B. It is. However, the client terminal 1A is logged off while the client terminal 1B is logged on.

  If the operation of “file001.pdf” is possible, the client terminal 1B transmits an OK response to the relay server R1. The relay server R1 transfers an OK response to the relay server R2.

  The relay server R2 transmits a mediation command to the relay server R1. Here, a communication path is established between the relay servers R1 and R2 (step S4.2). The relay server R1 transmits a file acquisition request (GetFileData command) to the client terminal 1B (step S4.2.1). The client terminal 1B acquires “file001.pdf” from the file server F installed in the LAN 1 shown in FIG. 1 and transmits it to the relay server R1. Then, “file001.pdf” is transmitted to the client terminal 2A via the relay servers R1 and R2 (FileTransfer command).

  When the series of communication processes is completed, the relay server R2 transmits a disconnection request (BYE method) to the relay server R1 in order to disconnect the established communication path (step S5).

{P3 relay group information and shared resource information}
As to how the relay communication system shown in FIG. 1 responds flexibly to such a situation change when the client terminals 1A and 1B are sequentially logged off or excluded from a group sharing resources, This will be described below.

  First, the communication process sequence shown in FIG. 11 will be described. Steps S6 to S8 show a sequence in which the client terminal 1A is excluded from the group sharing the resource by the operator of the relay server R1 or the like. When the relay server R1 receives an instruction from the operator or the like to exclude the client terminal 1A, the relay group information 100P2 and the shared resource information 120P2 in the P2 state shown in FIGS. 9 and 10 are shown in FIGS. The relay group information 100P3 and the shared resource information 120P3 in the P3 state are changed. The contents of this change will be described in detail later.

  The relay server R1 transmits a change information notification (NOTIFY method) to the relay server R3 (step S6). The relay server R3 that has received the relay group information 100P3 and the shared resource information 120P3 transmits a status information change request (UpdateResourceStatus command) to the client terminal 3A (step S6.1). Similarly, the client terminals 2A and 1B receive status information change requests from the relay servers R2 and R1, respectively (step S7, step S7.1, and step S8). Here, the client terminal 1A is excluded from the group sharing the resource.

  12 and 13 are diagrams illustrating the contents of the relay group information 100P3 and the shared resource information 120P3 in the P3 state. As a difference between the relay group information 100P3 shown in FIG. 12 and the relay group information 100P2 shown in FIG. 9, the description of the client terminal 1A is deleted in the relay group information 100P3. This indicates that in the state of P3, the client terminal 1A is excluded from the group sharing the resource.

  Further, as a difference between the shared resource information 120P3 shown in FIG. 13 and the shared resource information 120P2 shown in FIG. 10, in the shared resource information 120P3, the client terminal 1A is deleted from the family account information 124P3 and the family resource information 125P3. Has been. This is because the client terminal 1A is excluded from the group sharing the resource, and in the excluded state, “file001.pdf” cannot be registered in the shared resource information 120P3. However, since the client terminal 1B is logged on, the entity of “file001.pdf” can be accessed through the client terminal 1B, and “ok” is described in the status information of “file001.pdf”. Yes.

{Relay group information and shared resource information in P4 state}
Steps S9 to S9.2.1 show a sequence in which the client terminal 1B is logged off. Upon receiving a logoff instruction from the user, the client terminal 1B transmits a logoff registration request (REGISTER method) to the relay server R1 (step S9). The relay server R1 changes the relay group information 100P3 and the shared resource information 120P3 in the P3 state illustrated in FIGS. 12 and 13 to the relay group information 100P4 and the shared resource information 120P4 in the P4 state illustrated in FIGS. 14 and 15. To do. The contents of this change will be described in detail later.

  The relay server R1 transmits a change information notification (NOTIFY method) to the relay server R2 (step S9.1). The relay server R2 that has received the relay group information 100P4 and the shared resource information 120P4 transmits a status information change request (UpdateResourceStatus command) to the client terminal 2A (step S9.1.1).

  Similarly, the client terminal 3A receives a status information change request from the relay server R3 (step S9.2, step S9.2.1). When Steps S9 to S9.2.1 are completed, the relay server R1 transmits an OK response to the client terminal 1B. Here, the client terminal 1B is logged off.

  14 and 15 are diagrams showing the contents of the relay group information 100P4 and the shared resource information 120P4 in the P4 state. As a difference between the relay group information 100P4 shown in FIG. 14 and the relay group information 100P3 shown in FIG. 12, in the relay group information 100P4, the description of the status information of the client terminal 1B is changed from “logon” to “logoff”. has been edited. This indicates that the client terminal 1B is logged off in the state of P4.

  Further, when the shared resource information 120P4 shown in FIG. 15 is compared with the shared resource information 120P3 shown in FIG. 13, the client terminal 1B is deleted from the family account information 124P4 and the family resource information 125P4 in the shared resource information 120P4. Absent. This is because the client terminal 1B is logged off in the state of P4, but may be logged on again. However, since the client terminal 1B is logged off, it is impossible to access the entity “file001.pdf”, and “error” is described in the status information of “file001.pdf”.

{P5 relay group information and shared resource information}
Steps S10 to S11.1 show a sequence in which the client terminal 1B is excluded from the group sharing the resource by the operator of the relay server R1. When the relay server R1 receives an instruction from the operator or the like to exclude the client terminal 1B, the relay group information 100P4 and the shared resource information 120P4 in the P4 state illustrated in FIGS. 14 and 15 are illustrated in FIGS. 16 and 17. The relay group information 100P5 and the shared resource information 120P5 in the P5 state are changed. The contents of this change will be described in detail later.

  The relay server R1 transmits a change information notification (NOTIFY method) to the relay server R2 (step S10). The relay server R2 that has received the relay group information 100P5 and the shared resource information 120P5 transmits a status information change request (UpdateResourceStatus command) to the client terminal 2A (step S10.1). Similarly, the client terminal 3A receives a status information change request from the relay server R3 (steps S11 and S11.1). Here, the client terminal 1B is excluded from the group sharing the resource.

  16 and 17 are diagrams showing the contents of the relay group information 100P5 and the shared resource information 120P5 in the P5 state. As a difference between the relay group information 100P5 shown in FIG. 16 and the relay group information 100P4 shown in FIG. 14, the description of the client terminal 1B is deleted in the relay group information 100P5. This indicates that in the state of P5, the client terminal 1B is excluded from the group sharing the resource.

  Further, as a difference between the shared resource information 120P5 shown in FIG. 17 and the shared resource information 120P4 shown in FIG. 15, in the shared resource information 120P5, the client terminal 1B is deleted from the family account information 124P5 and the family resource information 125P5. Has been. This is because the client terminal 1B is excluded from the group sharing the resource, and in the excluded state, “file001.pdf” cannot be registered in the shared resource information 120P5. Further, since the client terminal 1B is excluded from the group sharing the resource, the client terminal T having the entity “file001.pdf” no longer exists in the group, and the entity information of “file001.pdf” is stored in the group. , Has been deleted from the family resource information 125P5.

  When the communication processing sequence, relay group information, and shared resource information shown in FIGS. 5 to 17 are summarized, each resource is shared between client terminals T connected to different LANs. The client terminal T can also acquire information on the status change of each other client terminal T. In addition, it is possible to perform operations on resources between different LANs while flexibly responding to changes in the status of each client terminal T.

{Operations of resources registered from client terminals on different LANs}
In the communication processing sequence shown in FIGS. 7, 8, and 11, the client terminals 1 </ b> A and 1 </ b> B having the “file001.pdf” entity are connected to the same LAN 1. However, there may be a case where the client terminal T having the “file001.pdf” entity is connected to a different LAN. Even in this case, the same resource operation as in steps S1 and S2 shown in FIG. 7 is possible.

  For example, consider a case where the client terminals 1A and 3A connected to different LANs have an entity “file001.pdf”. The client terminal 2A transmits a copy request (CopyFile command) to the relay server R2. The relay server R2 selects the owner client terminals 1A and 3A having “file001.pdf” based on the shared resource information 120. Based on the relay group information 100, one of the relay servers R1 and R3 to which the owner client terminals 1A and 3A are connected is selected. Then, a connection request (INVITE method) is transmitted to the selected relay server R via the external server S. Subsequent resource operation contents are the same as steps S1.1 to S2 shown in FIG.

  That is, if the relay server R can relay the resource operation to a plurality of relay servers R or a plurality of client terminals T, any one relay server R or any one client terminal T And the resource operation can be relayed to the relay server R or the client terminal T.

It is a network block diagram of the relay communication system which concerns on this Embodiment. It is a functional block diagram of an external server. It is a functional block diagram of a communication apparatus. It is a functional block diagram of a relay server. It is a figure which shows the content of the relay group information of an initial state (P1). It is a figure which shows the content of the shared resource information of an initial state (P1). It is a sequence diagram of the communication process which concerns on this Embodiment. It is a sequence diagram of the communication process which concerns on this Embodiment. It is a figure which shows the content of the relay group information of the state of P2. It is a figure which shows the content of the shared resource information of the state of P2. It is a sequence diagram of the communication process which concerns on this Embodiment. It is a figure which shows the content of the relay group information of the state of P3. It is a figure which shows the content of the shared resource information of the state of P3. It is a figure which shows the content of the relay group information of the state of P4. It is a figure which shows the content of the shared resource information of the state of P4. It is a figure which shows the content of the relay group information of the state of P5. It is a figure which shows the content of the shared resource information of the state of P5.

Explanation of symbols

S External server T Communication device (client terminal)
R relay server 100 relay group information 120 shared resource information

Claims (4)

A relay server connected to the LAN and capable of communicating with a relay server connected to another LAN;
An account information registration unit for storing account information including information of client terminals connected to the same LAN;
A relay group information registration unit that stores relay group information including information on a group of relay servers that allow mutual communication;
A shared resource information registration unit that stores shared resource information including resource information, information on client terminals that share the resource, and information on owner client terminals that are capable of operating the resource entity;
When receiving an operation instruction on a resource that can be operated by a client terminal connected to another LAN based on the shared resource information from the client terminal stored in the account information registration unit, the relay group information Based on the resource operation relay unit that relays the operation for the resource,
With
The shared resource information registration unit
Means for associating and storing information of the plurality of owner client terminals for the one resource when receiving registration requests from the plurality of owner client terminals for one resource;
Including a relay server. The relay server according to claim 1,
The resource operation relay unit
Means for relaying an operation on the one resource to any one of the plurality of owner client terminals;
Including a relay server. In the relay server according to claim 2,
The resource operation relay unit
Means for not relaying an operation on the one resource to an owner client terminal that cannot operate the entity of the one resource among the plurality of owner client terminals;
Including a relay server. In the relay server according to claim 3,
The shared resource information registration unit
Means for deleting information related to the one resource from the shared resource information when all of the plurality of owner client terminals are deleted from the relay group information;
Including a relay server.

Images