JP2008148200A - Relay server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a relay server suitable for a relay communication system that allows different LAN terminals to share resources with a required party as needed and to operate the resources and has improved expandability and flexibility. <P>SOLUTION: There is the relay server R that can communicate with the relay server R of other LANs via an external server S on a WAN. The relay server R stores the account information of a terminal T in the LAN, relay group information 100 of a group of relay servers R, and shared resource information 120 including the resource and the account of the terminal T sharing the resource. The relay group information 100 includes connection information 108 indicating the connection destination of the terminal T. When the terminal T registered at other relay servers R logs in, the relay server R identifies the relay server R to which the terminal T is registered for inquiry based on the relay group information 100, and decides whether connection should be permitted. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a relay server used in a relay communication system that enables communication between terminals in a local area network (LAN) over a wide area network (WAN). In particular, the present invention relates to a communication technique that enables a resource in a terminal in another LAN to be operated 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.

  Various systems have been proposed for this type of technology (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 based on the same protocol, and the system configuration is not so complicated. Therefore, 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.

  A terminal that has already been registered in a certain LAN may move to another LAN. In that case, the connection settings change between the movement source and the movement destination, and in accordance with the change, it is necessary to sequentially correspond to the management settings of the resources related to the terminal.

  Therefore, in view of these problems, the present invention shares resources with the necessary counterparts when each terminal is required, even if the terminals are connected to different LANs and managed by different protocols, and resources are allocated. An object of the present invention is to provide a relay server that can be operated and used in a relay communication system that is easy to operate. Suitable for a dynamic relay communication system that is highly scalable and flexible, and can be used without being conscious of changing the setting conditions even if registered terminals move between LANs. To provide a secure relay server.

  In order to solve the above-described problem, the relay server according to the present invention described in claim 1 is a relay server that is connected to a LAN and can communicate with a relay server of another LAN, and is connected to the same LAN. Account information registration unit that stores information on the client terminals that are connected, and information on a group of relay servers that allow mutual connection, and stores relay group information that includes information on the client terminals registered on each relay server A relay group information registration unit that receives the connection request from the client terminal stored in the account information registration unit of another relay server, and receives the connection request based on the relay group information The relay server that is registered is identified, and the relay server is inquired to determine whether or not to allow the connection. .

  The present invention described in claim 2 is the relay server according to claim 1, wherein the relay group information is recorded for each client terminal, and connection information indicating a relay server to which the client terminal is connected, And when the connection request is received from the client terminal stored in the account information registration unit, the content of the connection information of the client terminal included in the relay group information stored in the own device is updated, and other related relays A relay group information change notification is transmitted to the server.

  The present invention according to claim 3 is the relay server according to claim 2, and the own device stores the connection when the client terminal stored in the account information registration unit of another relay server is permitted. The content of the connection information of the client terminal included in the relay group information to be updated is updated, and a relay group information change notification is transmitted to another related relay server.

  According to the relay communication system to which the relay server according to the present invention is applied, whether or not a client terminal in a different LAN has resources owned by other client terminals beyond the WAN, It can be operated like this.

  Even if a client terminal registered in any one of the LANs moves to another LAN, it is possible to handle resources without being conscious of it as it is without requiring laborious work such as setting change.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. First, the basic configuration of the relay communication system according to the present invention will be described with reference to the first embodiment. In addition, a specific configuration of the present invention will be described in detail according to the second embodiment.

{First embodiment}
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 client terminal 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.

  This embodiment is an example of a system that uses SIP (Session Initiation Protocol) as a communication protocol between an external server S and each relay server R in a WAN and between a relay server R and a client terminal T in a LAN. Explained. However, it is possible to use a protocol other than SIP as a communication protocol between the server and the terminal.

  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 can be applied to other similar networks.

  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, and 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 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. Each function of the external server S centering on the control unit 202 will be described later.

{Client terminal}
The client terminal T is a terminal that can be directly operated by the user. For example, a personal computer (PC) used for daily work by the user corresponds to the client terminal T. Accordingly, a large number of client terminals T exist in the normal LAN, but in this embodiment, client terminals 1A and 1B are connected to the LAN 1, the client terminals 2A and 2B are connected to the LAN 2, and the client terminals 3A are connected to the LAN 3. 3B illustrates a case where the 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, 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 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 protocols such as TCP / IP, UDP, and SIP. For example, the control unit 602 receives a change notification of the shared resource information 120 from the processing for controlling the movement, change, deletion, etc. of the resource stored in the resource storage unit 603 or the relay server R, and stores it in the shared resource information DB 604. A process of updating the stored shared resource information 120 is executed. Each function of the client terminal T centering on the control unit 602 will be described later.

{Relay server}
One relay server R is arranged for each LAN. Specifically, 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 1 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.

  Since communication between each relay server R and each client terminal T is performed using SIP, each relay server R has a function as a SIP registrar server. For example, the relay server R2 connected to the LAN 2 functions as a SIP registrar server that registers the account of each client terminal 2A, 2B connected to the LAN 2 in the account information DB 504 using SIP.

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

  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 relay group information related to the client terminal T registered in the account information DB.

  The shared resource information DB 506 is a database that manages shared resource information 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. Then, processing for creating the relay group information 100 and storing it in the relay group information DB 505, processing for creating the shared resource information 120 and storing it in the shared resource information DB 506, and the like are executed. Each function of the relay server R centering on the control unit 503 will be described later.

{file server}
The file server F is a server that is connected to the LAN and can communicate with each client terminal T connected to the same LAN, and can store the substance of resources such as files and folders. That is, the file server F functions as a resource storage unit that replaces the resource storage unit 603 provided in each client terminal T. In other words, in the present embodiment, the resource that can be operated by each client terminal T is stored in the local disk of the client terminal T or in the file server F as a network drive. is there. Therefore, in FIG. 1, as the file server F is shown in some of the LANs 1 and 3, it is not necessary equipment for each LAN but is installed as needed.

  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 contents of the relay group information 100 are shown in FIG. FIG. 6 shows the relay group information 100 that is exchanged 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 allow connection to each other.

  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 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. Each account (for example, user1A @ account) and each name (for example, terminal1A) of the client terminal T connected to the same LAN are 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}
Next, the contents of the shared resource information 120 are shown in FIG. FIG. 7 illustrates the shared resource information 120 stored in the shared resource information DB 604 of the client terminal 1A. The same information is also stored in the shared resource information DB 506 of the relay server R1 registered in the same LAN as the client terminal 1A. The shared resource information 120 there is composed of account identification information 121 indicating that it is shared resource information 120 related to the client terminal 1A, and individual shared resource information 122 related to the client terminal 1A.

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

  The individual shared resource information 122 includes shared resource identification information 123, family account information 124, family resource information 125, 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, an ID (for example, 20061001150032user1A @ relay-server1) associated with the client terminal T that has requested creation of the shared resource information 120 and a name (for example, user1A-policy01) for facilitating the identification thereof. It is configured.

  Accordingly, since the user or the like can specify the individual shared resource information 122 by the shared resource identification information 123, the contents can be easily edited.

  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 = "folderA") and account information (for example, an owner client terminal) of a client terminal T (owner client terminal) capable of operating the resource entity. , Owner = “user1A @ account”) and address information indicating the location of the resource entity (for example, value = “c: / folderA”).

  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.

  The flow of communication processing in the relay communication system configured as described above will be described with reference to the processing sequence diagrams of FIG. 8, FIG. 9, FIG. 11, FIG. Steps S1 to S9 shown in FIG. 8 indicate the account registration stage of each device.

  The relay server R1 transmits an account registration request (REGISTER) to the external server S (step S1). Here, the relay server R1 makes a registration request for its own account (sip: relay-server1 @ net). The external server S returns an OK response to the relay server R1, and registers the account of the relay server R1 and the global IP address of the relay server R1 in the relay server account information DB 203 in association with each other.

  Subsequently, the relay server R2 transmits an account registration request (REGISTER) to the external server S (step S2). Here, the relay server R2 makes a registration request for its own account (sip: relay-server2 @ net). The external server S returns an OK response to the relay server R2, and registers the account of the relay server R2 and the global IP address of the relay server R2 in association with the relay server account information DB 203.

  Similarly, the relay server R3 makes a registration request (REGISTER) for its own account to the external server S, and registers its own account and the like in the external server S (step S3).

  Next, the client terminal 2A transmits an account registration request (REGISTER) to the relay server R2 (step S4). Here, the client terminal 2A makes a registration request for its own account (sip: user2A @ account). The relay server R2 performs an OK response, and registers the account of the client terminal 2A and the private IP address of the client terminal 2A in association with the account information DB 504.

  Subsequently, the client terminal 1A transmits an account registration request (REGISTER) to the relay server R1 (step S5). Here, the client terminal 1A makes a registration request for its own account (sip: user1A @ account). The relay server R1 performs an OK response and registers the account of the client terminal 1A and the private IP address of the client terminal 1A in association with each other in the account information DB 504.

  Similarly, the client terminal 3A is connected to the relay server R3 (step S6), the client terminal 2B is connected to the relay server R2 (step S7), the client terminal 1B is connected to the relay server R1 (step S8), and the client terminal 3B is connected to the relay server R3. Each relay server R3 is requested to register its own account (step S9), and its own account and the like are registered in each relay server R.

  Through the above steps, the registration of the account with respect to the external server S of each relay server R is completed, and the registration of the account with respect to each relay server R of each client terminal T is completed.

  The order of the above steps is merely an example, and the order of the steps is not limited as long as the account registration of each device is completed. Even if it exists on the network, it does not function as a relay communication system unless these accounts are registered and connected. For example, the LAN 4 in FIG. 1 is not connected to the network because the account is not registered here, and cannot participate in the communication service described here.

  Steps S10 to S16 shown in FIG. 9 indicate the communication stage between the relay servers R. Note that the processing from step S1 to step S16 is generally performed as a network initial setting by a user or an operator.

  The relay server R1 transmits a connection request command (INVITE method) for the relay server R2 to the external server S (step S10). In this INVITE method, an account (sip: relay-server2 @ net) of the relay server R2 that is the connection request destination is designated. The external server S acquires the global IP address of the relay server R2 by referring to the relay server account information DB 203. Then, the external server S relays the INVITE method transmitted from the relay server R1 to the relay server R2. When the connection request command is transmitted from the relay server R1 to the relay server R2, an OK response is transferred from the relay server R2 to the relay server R1 via the external server S.

  As described above, communication between the relay servers R is performed via the external server S. Since the communication process between the relay servers R is similarly performed via the external server S in any communication, a specific description of the communication process via the external server S will be omitted hereinafter.

  Next, the relay server R1 uses the SUBSCRIBE method for the relay server R2 to set change notification using the notification event with the relay server R2 (step S11). As a result, whenever a change occurs in the contents of the relay group information 100 held by the relay server R2, the changed information is notified from the relay server R2 to the relay server R1 by the NOTIFY method.

  Note that the SUBSCRIBE method is one of the processing means defined in SIP. When a notification event is set by this method, the SUBSCRIBE method of the apparatus that has received the SUBSCRIBE method during the period in which the notification event can be executed thereafter. When a change occurs in the predetermined information, new information is notified to the device on the side that transmitted the SUBSCRIBE method by the NOTIFY method each time.

  Similarly, conversely, the relay server R2 sets a change notification with the relay server R1 using the SUBSCRIBE method for the relay server R1 (step S12). As a result, whenever a change occurs in the relay group information 100 of the relay server R1, the changed information is notified from the relay server R1 to the relay server R2 by the NOTIFY method.

  Here, since the change notification setting is performed for the first time, notification is made from the side that received the SUBSCRIBE method, and the relay group information 100a is newly created in the relay server R on the side that sent the SUBSCRIBE method.

  FIG. 10 shows the relay group information 100a. Here, since one group is formed by the relay server R1 and the relay server R2, the relay group information 100a includes both relay account information 102a and 102b. That is, the relay account information 102b of the relay server R2 is notified in the NOTIFY method of step S11, and the relay account information 102a of the relay server R1 is notified in the NOTIFY method of step S12, so that the relay group information 100a having the same contents is created on both sides. It is done. The created relay group information 100a is stored in each relay group information DB 505.

  The next step S13 shows a step in which a relay server R3 is newly added from the relay server R2 to the relay group of the relay server R1 and the relay server R2 formed here. Specifically, an operator or the like specifies a group with reference to the group identification information 101. Then, based on the operation of the operator or the like, the relay server R2 transmits a connection request command (INVITE method) to the relay server R3 (step S13). In response to the transmission, an OK response is transferred from the relay server R3 to the relay server R2. Then, similarly to the previous step S11 and step S12, change notification settings using the SUBSCRIBE method are performed (steps S14 and S15). Then, the changed information is notified by the NOTIFY method, and the relay group information 100b is newly created.

  Here, relay group information having the same contents as the relay group information in FIG. 6 is created. As shown in FIG. 6, since three relay servers R1, R2, and R3 form one group, the relay group information 100b includes the relay account information 102a, 102b, and 102c. That is, in the NOTIFY method of step S14, the relay account information 102c of the relay server R3 is notified, and in the NOTIFY method of step S15, the relay account information 102a and 102b stored in the relay server R2 is notified, and both have the same contents. Relay group information 100b is created. The created new relay group information 100b is stored in each relay group information DB 505.

  By step S14, the relay server R2 changes in the relay group information 100 stored in the relay group information DB 505. As a result, based on the change notification setting set in step S11, the changed information is notified to the relay server R1 (step S16). Specifically, the relay account information 102c of the relay server R3 is notified to the relay server R1, and the group information 100b shown in FIG. 6 is created and stored.

  In this way, when any of the relay group information 100 is changed between the relay server R1 and the relay server R2, or between the relay server R2 and the relay server R3, the contents are automatically updated. Even if the account of the relay server R or the client terminal T fluctuates, it can respond dynamically. Needless to say, the relay group information 100 can be formed between any relay servers R, and a plurality of relay groups can be formed.

  Next, the flow of communication processing related to resource sharing will be described using the processing sequence diagrams of FIGS. 11 and 15.

  In FIG. 11, the client terminal 1A transmits an account information transmission request (GetAccountList command) to the relay server R1 (step S21). In response to this transmission request, the relay server R1 transmits the contents of the stored relay group information, that is, each relay account information 102, to the client terminal 1A and displays it on the client terminal 1A. The user refers to each relay account information 102, selects the user client terminal T sharing the resource from among them, and designates it as the client terminal 1A. Here, user client terminals 2A and 3A are designated.

  The designated client terminal 1A transmits a shared resource creation request (CreateSharedResource command) including the information to the relay server R1 (step S22). Receiving the shared resource creation request, the relay server R1 stores the created shared resource information 120 in its own shared resource information DB 506. Then, the relay server R1 notifies the created shared resource information 120 to each relay server R2 and R3 to which the designated user client terminals 2A and 3A are connected by the NOTIFY method (steps S22.1 and S22). .2). The relay servers R2 and R3 that have received the notification store the shared resource information 120 in their shared resource information DB 506. Then, a shared resource change request (UpdateSharedResource command) is transmitted to each designated user client terminal 2A, 3A (step S22.1.1, step S22.2.1). Receiving this change notification, each user client terminal 2A, 3A changes the shared resource information 120 stored in its own shared resource information DB 604.

  FIG. 12 shows the shared resource information 120a stored in each relay server R1, R2, R3 and each client terminal 1A, 2A, 3A. There are a set of shared resource identification information 121 for uniquely identifying the shared resource information 120a, an account of the client terminal 1A as the owner, and an account of the designated client terminals 2A and 3A as the users. Family account information 124 is included.

  Next, a process of adding resource information 126 indicating the substance of the shared resource to the shared resource information 120 is performed from the client terminal 1A by a user operation. That is, the user selects the resource entity to be shared from the resource entities that can be operated by the client terminal 1A, and designates it as the client terminal 1A. Here, “folderA”, “file001.xls”, “file002.wrd”, and “file003.pdf” are designated.

  The designated client terminal 1A transmits a shared resource change request (UpdateSharedResource command) including the designated information to the relay server R1 (step S23). The relay server R1 that has received the shared resource change request stores the changed shared resource information 120b in its own shared resource information DB 506. Then, the relay server R1 notifies the changed shared resource information 120b to the relay servers R2 and R3 to which the user client terminals 2A and 3A are connected by the NOTIFY method (steps S23.1 and S23.2). . Each relay server R that has received the notification stores the shared resource information 120b in its own shared resource information DB 506. Then, a shared resource change request (UpdateSharedResource command) is transmitted to each user client terminal 2A, 3A (step S23.1.1, step S23.2.1). Receiving this change request, each user client terminal 2A, 3A changes the shared resource information 120 stored in its own shared resource information DB 604.

  FIG. 13 shows the shared resource information 120b stored in each relay server R and each client terminal T here. There, family resource information 125a is added to the shared resource information 120a created in the previous step S22.

  With reference to the shared resource information 120b created by the above communication processing, the client terminal 1A is the owner client terminal T, each client terminal 2A, 3A is the user client terminal T, and the owner client terminal 1A is operated. It is possible to specify the content of a possible resource entity and its location on the network.

  The following shows a step in which the shared resource information 120 is newly created from the client terminal 2B.

  The client terminal 2B transmits an account information transmission request (GetAccountList command) to the relay server R2 (step S24). In response to this transmission request, the relay server R2 transmits the contents of the stored relay group information 100, that is, each relay account information 102, to the client terminal 2B and displays it on the client terminal 2B. The user refers to each relay account information 102, selects the user client terminal T sharing the resource from among them, and designates it as the client terminal 2B. Here, client terminals 1A and 3B are designated as user client terminals.

  The designated client terminal 2B transmits a shared resource creation request (CreateSharedResource command) including the information to the relay server R2 (step S25). Receiving the shared resource creation request, the relay server R2 stores the created shared resource information 120 in its own shared resource information DB 506. Then, the relay server R2 notifies the created shared resource information 120 to each of the relay servers R1 and R3 to which the designated user client terminals 1A and 3B are connected by the NOTIFY method (Steps S25.1 and S25). .2). The relay servers R1 and R3 that have received the notification store the shared resource information 120 created in their shared resource information DB 506. Then, a shared resource change request (UpdateSharedResource command) is transmitted to each designated user client terminal 1A, 3B (step S25.1.1, step S25.2.1). Receiving this change notification, each user client terminal 1A, 3B changes the shared resource information 120 stored in its own shared resource information DB 604.

  FIG. 14 shows shared resource information 120c stored in the client terminal 1A and the relay server R1. There, the newly created individual shared resource information 122a is added to the shared resource information 120b created in the previous step 3. New shared resource identification information 123a is assigned to the newly created individual shared resource information 122a.

  Since the client terminals 2B and 3B are not related to the previously created shared resource information 120b, the newly created individual shared resource information 122a is stored in the client terminals 2B and 3B and the relay servers R2 and R3. Is stored as shared resource information 120.

  Next, FIG. 15 shows a flow of communication processing when processing for adding resource information 126 of resources to be shared from the client terminal 1A to newly created individual shared resource information 122a is performed.

  Based on the shared resource identification information 123a, the user selects the individual shared resource information 122a to which the resource is added from the shared resource information 120c and designates it to the client terminal 1A. Then, the user selects a resource to be shared from the resources that can be operated by the client terminal 1A, and designates it as the client terminal 1A. Incidentally, “file005.ppt” is designated here.

  The designated client terminal 1A transmits a shared resource change request (UpdateSharedResource command) including the designated information to the relay server R1 (step S26). Receiving the shared resource change request, the relay server R1 stores the changed shared resource information 120d in its own shared resource information DB 506. Then, the relay server R1 is changed to each of the relay servers R2 and R3 to which the user client terminals T (2B and 3B) included in the family account information 124 of the targeted individual shared resource information 122a are connected. The individual shared resource information 122a is notified by the NOTIFY method (steps S26.1 and S26.2). The relay servers R2 and R3 that have received the notification change and store the shared resource information 120 of their own shared resource information DB 506. Then, a shared resource change request (UpdateSharedResource command) is transmitted to each user client terminal 2B, 3B (step S26.1.1, step S26.2.1). Receiving this change request, each user client terminal 2B, 3B changes the shared resource information 120 stored in its own shared resource information DB 604.

  FIG. 16 shows shared resource information 120d stored in the client terminal 1A and the relay server R1. There, family resource information 125b is newly added and changed to the individual shared resource information 122a of the shared resource information 120c created in the previous step S25. The changed shared resource information 122a is stored as the shared resource information 120 in the client terminals 2B and 3B and the relay servers R2 and R3.

  The following shows a flow of communication processing when the client terminal 2B performs processing for adding the resource information 126 to the shared resource information 120 for the individual shared resource information 122a.

  Based on the shared resource identification information 123a, the user selects the individual shared resource information 122a to which the resource is added from the shared resource information 120, and designates it to the client terminal 2B. Then, the user selects a resource to be shared from resources that can be operated by the client terminal 2B, and designates it as the client terminal 2B. Incidentally, “folderC”, “file00A.ppt”, and “file00B.ppt” are designated here.

  The designated client terminal 2B transmits a shared resource change request (UpdateSharedResource command) including the designated information to the relay server R2 (step S27). The relay server R2 that has received the shared resource change request stores the changed shared resource information 120 in its own shared resource information DB 506. The relay server R2 notifies the changed individual shared resource information 122 by the NOTIFY method to the relay servers R1 and R3 to which the user client terminals 1A and 3B that share resources are connected (step S27.1). Step S27.2). The relay servers R1 and R3 that have received the notification change and store the shared resource information in their shared resource information DB 506. Then, a shared resource change request (UpdateSharedResource command) is transmitted to each user client terminal 1A, 3B (step S27.1.1, step S27.2.1). Receiving this change request, each user client terminal 1A, 3B changes the shared resource information 120 stored in its own shared resource information DB 604.

  FIG. 17 shows shared resource information 120e stored in the client terminal 1A and the relay server R1. There, family resource information 125c is newly added and changed to the shared resource information 120d created in the previous step S26. The changed individual shared resource information 122a is stored as the shared resource information 120 in the client terminals 2B and 3B and the relay servers R2 and R3.

  Thus, each client terminal T can form an aggregate that individually shares resources. Each client terminal T can change the shared resources as necessary when necessary, and is a relay communication system with excellent versatility and flexibility.

  Next, referring to FIG. 18, a flow of communication processing in which a client terminal T connected to a certain LAN indirectly operates resources held by the client terminal T of another LAN beyond the Internet will be described.

  The first process shows a flow when the client terminal 2A of the LAN 2 indirectly copies resources that the client terminal 1A of the LAN 1 holds and can operate.

  Upon receiving an instruction to copy “file003.pdf” from the user, the client terminal 2A transmits a copy request (Copyfile command) to the relay server R2 (step S31). The relay server R2 that has received the copy request selects the owner client terminal T that holds “file003.pdf” to be copied based on the shared resource information 120, and the owner client terminal T is connected. The selected relay server R is selected based on the relay group information 100 and communicated. Of course, communication is not performed if the resource is not sharable or if the account is not registered.

  Subsequently, the relay server R2 transmits a connection request (INVITE method) to the identified relay server R1 via the external server S (step S31.1). The relay server R1 that has received the connection request transmits a copy request to the client terminal 1A (step S31.1.1). The client terminal 1A that has received the copy request transmits an OK response to the relay server R1 if the target resource (file003.pdf) can be operated, and the relay server R1 transfers it to the relay server R2.

  The relay server R2 that has received the OK response transmits a Mediation command to the relay server R1, and a communication path is established between the relay servers R1 and R2 (step S31.2). The relay server R1 that has received the Mediation command transmits a GetFileData command for copying a file to the client terminal 1A to make a file copy request (step S31.2.1). Upon receiving the file copy request, the client terminal 1A copies the target “file003” from the resource storage unit 603 and transmits it to the relay server R1. Then, “file003” is transmitted to the client terminal 2A via the relay server R1 and the relay server R2 (FileTransfer command). The resource entity may be copied not only from the resource storage unit 603 but also from the file server F.

  When a series of communication processing is completed, in order to disconnect the established communication path, a disconnect request (BYE method) is transmitted from the relay server R2 to the relay server R1, and the communication path between both relay servers is disconnected. Thus, the communication ends (step S32).

  The following shows a flow when the client terminal 3B of the LAN 3 indirectly deletes resources that the client terminal 2B of the LAN 2 holds and can operate.

  When the client terminal 3B receives an instruction to delete “file00A.ppt” from the user, the client terminal 3B transmits a Deletefile command to delete the file to the relay server R3 to request deletion (step S33). The relay server R3 that has received the deletion request transmits the owner client terminal T that has “file00A.ppt” to be deleted and can be operated, and the relay server R to which the owner client terminal T is connected to the shared resource information 120. And the relay group information 100.

  Subsequently, the relay server R3 transmits the deletion request information to the identified relay server R2 through the external server S by the NOTIFY method (step S33.1). Receiving the deletion request information, the relay server R2 sends a Deletefile command to the client terminal 2B to request deletion (step S33.1.1). The client terminal 2B that has received the deletion request deletes the target resource (file00A.ppt) from the resource storage unit 603. Then, an OK response is transmitted to the client terminal 3B via the relay server R2 and the relay server R3.

  FIG. 19 shows the shared resource information 120f after the deletion process is performed. As shown in FIG. 19, the resource information 126 of “file00A.ppt” to be deleted is deleted from the shared resource information 120. This is because the resource entity has been deleted.

  When an operation for changing the content of the shared resource information 120, such as resource deletion, is performed, the shared resource information update process is performed subsequently.

  Specifically, a shared resource change request (UpdateSharedResource command) is transmitted to the relay server R3 from the client terminal 3B instructed to perform an operation involving the change of the shared resource information 120 (step S34). The relay server R3 that has received this change request notifies the changed shared resource information 120 to the relay servers R1 and R2 related to the changed shared resource information 120 by the NOTIFY method (steps S34.1, S34. 2). And each relay server R1 and R2 changes and memorize | stores the shared resource information of own shared resource information DB506.

  Then, a shared resource change request (UpdateSharedResource command) is transmitted to the user client terminals 1A and 2B related to the changed shared resource information 120 (steps S34.1.1 and S34.2.1). Each user client terminal 1A, 2B that has received the change request changes the shared resource information stored in its own shared resource information DB 604.

  That is, when the shared resource information 120 is changed, the related relay server R and client terminal T are notified to that effect and immediately updated to the new shared resource information 120. .

{Second Embodiment}
In this embodiment, even if the client terminal T registered in any one of the LANs moves to another LAN, it does not require time-consuming work such as setting change and logs in without being conscious of resources. It is a more dynamic relay communication system that can be handled.

  Each configuration of the relay communication system such as the relay server R and the client terminal T and the basic configuration of each communication processing flow are the same as those in the first embodiment. Hereinafter, the present embodiment will be described specifically with reference to the sequence diagrams of FIGS.

  FIG. 20 and FIG. 21 show an example of the flow of communication processing when the client terminal T registered in any one of the LANs moves and connects to another LAN. Specifically, the case where the client terminal 1A registered in the relay server R1 of the LAN1 logs off and newly logs in to the relay server R2 of the LAN2 is shown.

  FIG. 22 shows the contents of the relay group information 100 stored in the related relay servers R1, R2, and R3 before the client terminal 1A moves. FIG. 23 shows, before the client terminal 1A moves, each of the client terminals 1A, 2A, and 3A that form a shared group for a predetermined resource, and each of the relay servers R1, R2, and R3 registered by these, respectively. The content of the shared resource information 120 stored is shown.

  In FIG. 23, for example, “value =“ / network / z: folderZ ”” is recorded in the address information indicating the location of the resource entity name “folderNet”. This indicates that the resource entity of the name “folderNet” is in a storage unit on the LAN 1 network different from the client terminal 1A. In the present embodiment, it is assumed that “folderZ” is in the file server F arranged in the LAN 1. On the other hand, “value =“ c: / folderA ”and the like indicate that they are in the storage means inside the client terminal 1A.

  Unlike the first embodiment, the information 100, 120 of this embodiment records status information (status) 107, 127 indicating the connection state of the relay server R, client terminal T, and resources. . For example, “status =“ ok ”” and “status =“ logon ”” indicate that the displayed relay server R, client terminal T, and resource are in a connectable state.

  Further, in the relay group information 100 of this embodiment, connection information (server) 108 indicating the relay server R to which the client terminal T is connected at that time is recorded for each client terminal T. For example, “sever =“ relay-sever1 ”” indicates that the current connection destination is the relay server R1.

  In FIG. 20, the client terminal 1A, which is arranged in the LAN 1 as shown in FIG. 1 and is already registered in the relay server R1 as shown in FIG. 22, sends a logoff request (REGISTER) to the relay server R1. (Step S101). The relay server R1 that has received the request returns a response to the client terminal 1A that has transmitted the request.

  When the client terminal 1A logs off, the content of the relay group information 100 is changed, and the relay server R1 updates the relay group information 100 stored in its own device. Then, the relay server R1 transmits a change notification of the relay group information to the other relay servers R2 and R3 forming the relay group including the client terminal 1A by the NOTIFY method (steps S102 and S103). Each of the relay servers R2 and R3 that has received the change notification updates the relay group information 100 stored in its own device, and returns a response to the transmission source.

  FIG. 24 shows the contents of the relay group information 100h transmitted / received by the change notification. As shown in FIG. 24, “logoff” indicating that connection is not possible is recorded in the status information 107a of the client terminal 1A that has logged off. Similarly, the connection information 108a indicating the relay server R that is the connection destination includes the relay server R1. Since the connection with is disconnected, the record of “relay-sever1” is deleted and is in a blank state.

  Further, when the client terminal 1A logs off, the content of the shared resource information is also changed. For example, a resource for which the client terminal 1A is the owner cannot be operated because the client terminal 1A has logged off. Therefore, based on the updated contents of the relay group information 100, the relay server R1 updates the corresponding data in the shared resource information 120 stored in its own device.

  Then, the relay server R1 transmits a change notification of the shared resource information 120 to the other relay server R in which the client terminal T related to this update is registered. The client terminal T related to the update is the client terminal T included in the family account information 124 of the shared resource information 120 including the resource when there is a resource whose connection state changes due to the update. Since this change notification is the same as the change notification of the previous relay group information 100, the change notification is transmitted together in the previous steps S102 and S103.

  The relay servers R2 and R3 that have received the change notification of the shared resource information 120 update the shared resource information 120 stored in the self-device, and based on the change notification to the related client terminals 2A and 3A, A state change request (UpdateResourceStatus command) is transmitted (step S102.1, step S103.1). Receiving the state change request, the client terminals 2A and 3A update the shared resource information 120 stored in the own device and return a response to the transmission source.

  FIG. 25 shows the contents of the shared resource information 120h transmitted / received at the time of this update. As shown in FIG. 25, “error” indicating that connection is not possible is recorded in the status information 127a of the resource (for example, “folderA”) whose owner is the logged-off client terminal 1A.

  Therefore, the connection state of the client terminal T can be easily determined by referring to the relay group information 100, and the connection state of the resource can be easily determined by referring to the shared resource information 120.

  Next, the client terminal 1A that has logged off moves to the LAN 2 and transmits a connection request (REGISTER) for logging on to the relay server R2 (step S104). The relay server R2 that has received this connection request refers to the information of the client terminal T stored in the account information registration unit 504 of its own device, and determines whether or not the client terminal 1A that has made the connection request is registered. to decide. When it is determined that it is not registered, based on the relay group information 100, the relay server R1 in which the client terminal 1A that requested the connection is registered is specified. The relay server R2 does not accept the login when the information of the client terminal 1A is not obtained and cannot be specified. If it is registered in its own device, the login is accepted as it is.

  Then, the relay server R2 inquires of the identified relay server R1 whether or not the login information such as the ID and password received from the client terminal 1A is correct by sending a confirmation request (NOTIFY) (step S104.1). ). The relay server R1 that has received the confirmation request refers to the relay group information 100 stored in its own device, and transmits whether or not the login information of the client terminal 1A is correct to the relay server R2 inquired by the NOTIFY method. Then, the relay server R2 that has confirmed that the client terminal 1A that has logged in is legitimate transmits an OK response to the client terminal 1A, accepts the login of the client terminal 1A, and permits the connection. .

  When the relay server R2 accepts the login of the client terminal 1A, the relay server R2 updates the relay group information 100 stored in its own device as shown in FIG. 21, and relays the relay group information to the other related relay servers R1 and R3. 100 change notifications are transmitted by the NOTIFY method (step S105, step S106). Then, the relay servers R1 and R3 that have received the change notification update the relay group information 100 stored in their own devices based on the change notification, and return a response to the transmission source.

  FIG. 26 shows the contents of the relay group information 100i transmitted / received at the time of this update. As shown in FIG. 26, “logon” indicating that connection is possible is recorded in the status information 107b of the logged-in client terminal 1A. Similarly, “relay-sever2” indicating the relay server R2 which is a new connection destination is recorded in the connection information 108b. Therefore, referring to this, it can be determined that the client terminal 1A registered in the relay server R1 of the LAN 1 has moved to the LAN 2 and logged into the relay server R2.

  Next, the client terminal 1A transmits a transmission request (GetResourceStatus command) for the shared resource information 120 related to the client terminal 1A to the logged-in relay server R2 (step S107). Receiving this, the relay server R2 transmits the corresponding shared resource information 120 to the client terminal 1A.

  The client terminal 1A that has received the shared resource information 120 automatically confirms whether or not it can operate the resource that it is the owner of, and updates the state information 127 of the shared resource information 120 based on the result. Then, based on the updated shared resource information 120, a status change request (UpdateResourceStatus command) is transmitted to the logged-in relay server R2 (step S108).

  The relay server R2 that has received this status change request updates the target shared resource information 120 stored in its own device. Then, a status change request (UpdateResourceStatus command) is transmitted to the client terminal T registered in the own apparatus and to the client terminal T (2A in this case) included in the family account information 124 of the target shared resource information 120 (Step S108.1). The client terminal 2A that has received the status change request updates the stored shared resource information 120 and returns a response to the transmission source.

  Then, the shared resource information change notification is transmitted to the relay servers R1 and R3 in which the other client terminals T (here, 1A and 3A) included in the family account information 124 are registered (step S108.2, Step S108.3). The relay servers R1 and R2 that have received the change notification update the stored shared resource information 120. Then, the relay server R3 transmits a state change request (UpdateResourceStatus command) to the client terminal 3A (step S108.3.1). The client terminal 3A that has received the state change request updates the stored shared resource information 120 and returns a response to the transmission source. Note that the relay server R1 does not transmit a state change request to the client terminal 1A. This is because the user has already logged in to the relay server R2.

  FIG. 27 shows the contents of the shared resource information 120i transmitted / received at the time of this update. As shown in FIG. 27, the content of the status information 127b in which the client terminal 1A that has moved is the owner has been updated from not connectable (error) to (ok) indicating connectable.

  However, even if the client terminal 1A is the owner, resources stored in the folder Z in the file server F arranged on the LAN 1 network, for example, “folderNet”, are the result of the client terminal 1A moving to the LAN 2. Can no longer operate. For this reason, the state information 127c remains unreachable (error).

  As described above, since the contents of the relay group information 100 and the shared resource information 120 are sequentially updated in the relay communication system, even when moving to another LAN and reconnecting, the user can operate the resource as usual. Can do it.

  As described above, in the relay communication system to which the relay server of the present invention is applied, a client terminal in a different LAN has resources owned by other client terminals beyond the WAN, as if the own apparatus has it. It can be operated as if it were.

  Even if a client terminal already registered in one of the LANs moves to another LAN and logs on, it is possible to respond dynamically, without requiring time-consuming work such as setting changes, and without being aware of it. Can handle resources without.

It is a network block diagram of the relay communication system in 1st Embodiment. It is a functional block diagram of the external server in 1st Embodiment. It is a functional block diagram of the client terminal in 1st Embodiment. It is a functional block diagram of the relay server in 1st Embodiment. It is a figure which shows the relationship between a communication terminal and a relay server in 1st Embodiment, and the relationship between a relay server and an external server. It is a figure which shows the content of the relay group information in 1st Embodiment. It is a figure which shows the content of the shared resource information in 1st Embodiment. It is a sequence diagram of the communication process in 1st Embodiment. FIG. 9 is a sequence diagram of communication processing following FIG. 8. It is a figure which shows the content of the relay group information in a certain process in 1st Embodiment. It is a sequence diagram of the communication process in 1st Embodiment. It is a figure which shows the content of the shared resource information in a certain process in 1st Embodiment. It is a figure which shows the content of the shared resource information in a certain process in 1st Embodiment. It is a figure which shows the content of the shared resource information in a certain process in 1st Embodiment. FIG. 12 is a sequence diagram of communication processing following FIG. 11. It is a figure which shows the content of the shared resource information in a certain process in 1st Embodiment. It is a figure which shows the content of the shared resource information in a certain process in 1st Embodiment. It is a sequence diagram of the communication process in 1st Embodiment. It is a figure which shows the content of the shared resource information in a certain process in 1st Embodiment. It is a sequence diagram of the communication process in 2nd Embodiment. It is a sequence diagram of the communication process in 2nd Embodiment. It is a figure which shows the content of the relay group information of a certain process in 2nd Embodiment. It is a figure which shows the content of the shared resource information of a certain process in 2nd Embodiment. It is a figure which shows the content of the relay group information of a certain process in 2nd Embodiment. It is a figure which shows the content of the shared resource information of a certain process in 2nd Embodiment. It is a figure which shows the content of the relay group information of a certain process in 2nd Embodiment. It is a figure which shows the content of the shared resource information of a certain process in 2nd Embodiment.

Explanation of symbols

S External server T Client terminal R Relay server 100 Relay group information 107 Status information 108 Connection information 120 Shared resource information 127 Status information 504 Account information DB
505 Relay group information DB
506 Shared resource information DB

Claims (3)

A relay server that is connected to a LAN and can communicate with a relay server of another LAN,
An account information registration unit for storing information of client terminals connected to the same LAN;
A group of relay servers that allow mutual connection, a relay group information registration unit that stores relay group information including information of client terminals registered in each relay server;
With
Upon receiving a connection request from a client terminal stored in the account information registration unit of another relay server, based on the relay group information, identify the relay server in which the client terminal that requested the connection is registered, A relay server characterized by inquiring of the relay server and determining whether or not to permit the connection. The relay server according to claim 1,
The relay group information is recorded for each client terminal, and includes connection information indicating a relay server to which the client terminal is connected,
When a connection request is received from the client terminal stored in the account information registration unit, the content of the connection information of the client terminal included in the relay group information stored in the own device is updated, and other related relay servers are updated. A relay server that transmits a change notification of relay group information. The relay server according to claim 2,
When the client terminal stored in the account information registration section of another relay server is allowed,
A relay server that updates the contents of the connection information of the client terminal included in the relay group information stored in its own device, and transmits a change notification of the relay group information to another related relay server .

Images