JP5493567B2 - Message transmission / reception system, message transmission / reception method, message relay server, and message transmission / reception program - Google Patents

Description

  The present invention relates to a message transmission / reception system, a message transmission / reception method, and a message transmission / reception credit program for transmitting / receiving messages, and more particularly to a message transmission / reception system, a message transmission / reception method, and a message transmission / reception program capable of relaying messages. The present invention also relates to a message relay server provided in a message transmission / reception system.

  With the development of the Internet, a general user generally browses a Web page arranged on the WWW (World Wide Web) using a Web browser that operates on a computer. Web browsers are implemented on various computers. Therefore, a user can easily use a Web browser not only on a general PC (Personal Computer) as a computer but also on a mobile phone, a game terminal, a television receiver, a video device, and the like.

  Also, in general, a remote collaboration system has been proposed for remote users to work together via a network, and users can simultaneously view and draw the same materials and diagrams as a remote conference, Systems have been proposed for sending and receiving files to and from each other. In such a remote conference system, one group is formed in advance or temporarily with a certain period of time. And the operation performed on each terminal is exchanged as an operation message between users belonging to the group, and the remote meeting is realized by reproducing the operation corresponding to the operation message on each terminal. Moreover, the member and period to participate in such a group are managed as a session. Then, while the session continues, control is performed so that members participating in the session can exchange operation messages. In general, a program for controlling the operation of a terminal used by a user in such a remote collaboration system performs control so that an operation performed on the terminal as uplink communication is transmitted to another terminal as an operation message. The above program, on the contrary, receives an operation message transmitted from another program by performing downlink communication, and controls to execute the operation content described in the received message on its own terminal. To do.

  As such a remote collaboration system, a remote collaboration system using a Web browser as a client program has been proposed. For example, in the system described in Patent Document 1, each time the table data arranged on the server is updated, the URL is transmitted as a message to each terminal. Each terminal that receives the message displays the URL using a Web browser, so that the updated table data can be shown to each user.

  In the system described in Patent Document 2, other web browsers (specifically, operations such as scrolling, clicking, and text input performed by the user on the web page displayed on the web browser are used as messages. To a terminal equipped with a Web browser). Then, another Web browser that has received the message reproduces the operation according to the contents described in the message, thereby synchronizing the Web page displayed on the Web browser.

  In such a remote collaboration system using a Web browser, in order to realize operation synchronization, it is necessary to implement message transmission processing (uplink communication) and reception processing (downlink communication) on the Web browser. At this time, since the web browser does not have a function of directly communicating between web browsers, the web browser must always communicate with the web server. By implementing means for relaying messages on this Web server, messages can be exchanged between Web browsers.

  At this time, with respect to the HTTP (Hyper Text Transport Protocol) protocol used for communication between the Web browser and the Web server, the Web browser is the source of the request. Then, after receiving the request from the Web browser, the Web server performs processing according to the request. Therefore, among the upstream and downstream communication of the message described above, in upstream communication, it is possible to deliver to a Web server using a request using an HTTP from a Web browser (hereinafter, HTTP request) as usual. However, since there is no means for actively starting communication from the Web server toward the Web browser, it cannot be realized by ordinary means.

  As a means for making this possible, the system described in Patent Document 2 proposes a technique called permanent polling. This is not completely real-time by sending a request from the Web browser to the message relay server at a certain interval for downlink communication, and receiving a message in response when the message exists in the message relay server. However, it is a technique of acquiring a message at any time after a delay of a certain interval.

  In addition, when a user is newly added as a member to a session that is operating in the remote collaboration system, the Web browser operated by the newly added member is the same as that of other members participating in the session. In order to match the display and internal state with the Web browser, follow-up processing called catch-up is performed. In this session, the messages sent and received via the message relay server in the session are acquired in order from the beginning, and the operation is reproduced according to the messages so that the display and internal state are the same as those of the Web browser operated by other members. Realize with.

JP 2003-259323 A JP-T-2002-514332

  When there is a session that continues for a certain period, and a user who participates in the session repeats the operation of the Web browser, transmission / reception messages in the session are sequentially accumulated in the message relay server. When a new user joins the session, the Web browser acquires messages from the message relay server in order from the beginning by catch-up. At this time, it is necessary to catch up with the other browsers as early as possible. Therefore, messages are obtained continuously as fast as possible. At that time, communication and load are temporarily concentrated on the message relay server, and there is a possibility that the overall performance is deteriorated or the service is temporarily stopped.

  In order to avoid this, a cache is used in the message relay server, or a proxy server is installed in the middle of the communication path between the message relay server and the Web browser, and the cache is used. For example, it is possible to reduce the load on the message relay server by storing the message once transmitted from the message relay server in the cache and transmitting the message stored in the cache at the time of acquisition again by catch-up. .

  In general, the cache stores the URL transmitted from the browser as the request content in association with the response returned from the server, and if the URL transmitted from the browser is the same as the previously stored URL. , It has a mechanism to reply the saved response immediately.

  However, as described above, the message acquisition request by the Web browser is realized by polling. The message acquisition request by normal polling is transmitted with a URL different from the request that transmitted the URL of each request before transmitting the request from the Web browser. If the request is transmitted with the same URL as the request that has already been transmitted, it is determined that the request is equivalent to the previous request in the cache, and the message stored in the cache continues to be returned without reaching the message relay server. It will be. Therefore, even if a new message is accumulated in the message relay server, it cannot be returned to the Web browser.

  Furthermore, if there is no new message to be sent to the message relay server when sending a message acquisition request by polling, the response will be empty and all the requests from the browser are meaningful. Replies are not always returned.

  As a result, it is not easy for one web browser to know the URL of a request sent by another web browser, and even if it can be known, a message is received from the message relay server for that request. I can't know if it was answered. Therefore, even if a message returned to another Web browser remains in the cache, it is generally not easy for the Web browser at the time of catch-up to acquire the message from the cache.

  Therefore, an object of the present invention is to provide a message transmission / reception system, a message transmission / reception method, a message relay server, and a message transmission / reception program that enable a Web browser to acquire a message stored in a cache at the time of catch-up.

A message transmission / reception system according to the present invention includes a user terminal equipped with a browser and a message relay server that relays transmission / reception of messages using a plurality of browsers, and the message relay server is returned in response to a message acquisition request. In addition , response storage means for storing the management information in the message relay server in association with the URL included in the request in association with the message requested in the request, and when a new request is received, the request is requested in the request If the response including the message is already returned, the URL extracting means for extracting the URL stored in the response storage means in association with the management information corresponding to the message, and the URL extracted by the URL extracting means The source of the new request with a response containing And a response reply means for replying. When the user terminal receives a response including the URL from the response reply means, the user terminal uses the URL included in the received response to obtain a message stored in the cache. It includes a request transmission means for generating and transmitting a request.

Message relay server according to the present invention is a message relay server for relaying the transmission and reception of messages with multiple browsers, it sent back to the request for message retrieval, the requested message request, the message relay Response storage means for associating and storing the management information in the server and the URL included in the request, and when a new request is received , if a response including the message requested in the request has already been returned The URL extraction means for extracting the URL stored in the response storage means in association with the management information corresponding to the message, and the URL extracted by the URL extraction means to obtain the message stored in the cache. A response containing the response to the sender of the new request Characterized in that a response returning means for.

The message transmission / reception method according to the present invention includes a response storage step of storing the management information of the message requested in the request returned in response to the message acquisition request and the URL included in the request in the response storage unit. When a new request is received and a response including the message requested in the request has already been returned, the URL stored in the response storage unit is extracted in association with the management information corresponding to the message. A URL extraction step, a response return step of returning a response including the extracted URL to the transmission source of the new request, and a response including the URL, when the URL included in the received response is used, Get saved message Characterized in that it comprises a request transmission step of generating and transmitting a request for.

The message transmission / reception program according to the present invention manages in a computer a message requested by a request that is returned to a message acquisition request to a computer that relays transmission / reception of a message using a plurality of browsers. When a response storage process for storing the information and the URL included in the request in association with the response storage unit and receiving a new request and a response including the message requested in the request have already been returned, A URL extraction process for extracting the URL stored in the response storage unit in association with the management information corresponding to the message, and a response including the extracted URL in order to acquire the message stored in the cache Respond to the sender of the request Characterized in that to execute the return processing.

  According to the present invention, the message stored in the cache can be acquired when the Web browser catches up.

It is a block diagram which shows an example of a structure of the message transmission / reception system by this invention. It is a block diagram which shows an example of a structure of the user terminal carrying a web browser. It is a flowchart which shows the example of a session start process in a message relay server. It is a flowchart which shows the process example in a Web browser at the time of an application process start. It is a flowchart which shows the example of an upstream communication process in a Web browser and a message relay server. It is a flowchart which shows the example of a downlink communication process with a web browser. It is a flowchart which shows the example of a process in a message transmission means. It is a flowchart which shows the process example in a transmission message selection means. It is a flowchart which shows the example of a process in the response management means at the time of returning a message in a message transmission means. It is a flowchart which shows the example of a process in the response management means when returning history URL. It is a block diagram which shows the minimum structural example of a message transmission / reception system.

  Hereinafter, embodiments of the present invention will be described with reference to FIGS. 1 and 2. FIG. 1 is a block diagram showing an example of the configuration of a message transmission / reception system according to the present invention. As shown in FIG. 1, the message transmission / reception system transmits / receives messages between Web browsers using the Web browser 1 used as a user interface for users to collaborate remotely and the HTTP protocol described above. A message relay server 2 mounted on a Web server that relays the message, and a proxy server 3 having a general cache function. If the message relay server 2 has a cache function equivalent to that of the proxy server 3, the proxy server 3 may be omitted.

  Specifically, the Web browser 1 is mounted on an information processing apparatus such as a personal computer that operates according to a program. FIG. 2 is a block diagram illustrating an example of the configuration of a user terminal equipped with a Web browser. As shown in FIG. 2, the terminal on which the web browser 1 is mounted is a communication that is executed by one or a plurality of applications 101 that implement a process for performing a collaborative work, and an application 101 that operates on the web browser 1. Communication management means 102 for controlling the message, uplink communication means 103 for transmitting the message generated by the application 101 to the message relay server 2 as uplink communication, and downlink communication (catch-up processing is performed to the message relay server 2) Link information 104 for acquiring a message by transmitting a request for the message, and associating (corresponding) the position information of the acquired message in the queue on the message relay server 2 with the application 101 that processes the message. Pointer storage means 105 for storing (storing). In the present embodiment, uplink communication is to send a message to another browser, and downlink communication is to receive a message from another browser.

  Each means that operates on the above-mentioned Web browser is defined by a description method generally called HTML (Hyper Text Markup Language), and further operates a program on a Web browser generally called JavaScript, ActiveX, Flash, or the like. Implement by using the mechanism to make it. Java is a registered trademark. In the following, expressions such as the Web browser 1 and the application 101 executing processing and transmission / reception are used. Specifically, an information processing terminal equipped with the Web browser executes processing according to the Web browser and application 101. It is.

  Specifically, the message relay server 2 is realized by an information processing apparatus that operates according to a program. As shown in FIG. 1, the message relay server 2 includes a session management unit 201, a message reception unit 202, a message accumulation control unit 203, a queue storage unit 204, a message transmission unit 205, and a transmission message selection unit 206. Response information storage means 207 and response management means 208.

  Specifically, the session management unit 201 is realized by a CPU of an information processing apparatus that operates according to a program. The session management unit 201 has a function of managing a session of remote collaboration work between users and holding (storing or managing) information indicating a relationship between the session and a queue.

  Specifically, the message receiving unit 202 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The message receiving unit 202 has a function of receiving a message transmitted by performing upstream communication from the Web browser 1 operated by the user.

  Specifically, the message storage control unit 203 is realized by a CPU of an information processing apparatus that operates according to a program. The message accumulation control unit 203 has a function of storing the message received by the message receiving unit 202 in the queue storage unit 204 by a queue method.

  Specifically, the queue storage unit 204 is realized by a storage device such as an optical disk device or a magnetic disk device. The queue storage means 204 actually stores data using a queue prepared for each session.

  Specifically, the message transmitting unit 205 is realized by a CPU and a network interface unit of an information processing apparatus that operates according to a program. The message transmission unit 205 has a function of receiving a request from a Web browser by downlink communication and returning a URL for obtaining a message requested by the request or a message already cached.

  Specifically, the transmission message selection means 206 is realized by a CPU of an information processing apparatus that operates according to a program. The transmission message selection unit 206 searches for a message to be returned to the Web browser 1 from the messages stored in the queue storage unit 204 in response to the request by the downlink communication received from the Web browser 1, and stores the message in the queue. It has a function to acquire (extract) a message together with position information (for example, a sequence number).

  Specifically, the response information storage unit 207 is realized by a storage device such as an optical disk device or a magnetic disk device. The response information storage unit 207 includes position information (for example, sequence number) in the queue of the message transmitted from the message transmission unit 205, the session ID of the queue, and the request URL received by the message transmission unit 205 from the Web browser. Are stored as response information.

  Specifically, the response management means 208 is realized by a CPU of an information processing apparatus that operates according to a program. When the response management unit 208 receives a request for acquiring a message from the Web browser, the response management unit 208 determines whether the corresponding message has already been transmitted. If the request has already been transmitted, the message is transmitted using the request URL at that time as a history URL. A function of transmitting (outputting) to the means 205 is provided.

  In FIG. 1, two Web browsers are connected to the message relay server. However, the number is not limited to two, and for example, three or more may be connected.

  Next, the operation of the message transmission / reception system will be described. FIG. 3 is a flowchart showing an example of session start processing in the message relay server.

  First, a session start process in the message relay server 2 will be described with reference to FIG. For example, when the user performs an operation for starting the system in order to conduct a remote conference, the session management unit 201 creates a session of remote collaboration work between the users according to the user's operation. At this time, the session management means 201 may use any method as a session start method. For example, the session management means 201 and a telephone line switch are connected, the start of a telephone call may be the start of a session, and the callers may be session participants. Alternatively, the Web browser and the session management unit 201 may be separately connected, and the start of the session and the session participants may be defined by the operation of the Web browser.

  Next, the session management unit 201 associates (corresponds) and manages an ID (session ID) indicating a session and an ID (user ID) for identifying a user. The session management unit 201 may store information indicating this association in the session management unit 201 or may store the information on another server such as a database server outside the message relay server 2. Hereinafter, examples of session IDs and user IDs managed by the session management unit 201 will be shown.

  In the example shown in Table 1, “User1” and “User2” participate in the session “000001”, and “A”, “B”, and “C” participate in the session “000002”.

  When the session management unit 201 starts a session (step S101), the session management unit 201 creates a queue corresponding to the session based on the session ID, and stores the created queue in the queue storage unit 204 (step S102). In the present embodiment, a box (for example, a file or the like for storing a message in a queue system for each session created by the session management unit 201 in step S102, such as a file. Is also simply expressed as “queue”. The following is an example of the queue created at this time.

  Table 2 is an example of a queue for a session whose session ID is “000001”. Each row in the queue shown in Table 2 represents a message transmitted from an application operating on the Web browser.

  The sequence number in the first column indicates the order of messages received by the message relay server during the corresponding session. In this embodiment, an integer starting from 0 and increasing by 1 is used for this sequence number.

  The temporary ID in the second column is an ID indicating an application operating on the Web browser that transmitted the message, and details will be described later.

  The message type in the third column represents the type of application that uses the message, and has an arbitrary character string.

  The message content in the fourth column is the main body of the message and has not only characters but also arbitrary data as values. In the example shown in Table 2, the message with the sequence number “0” is transmitted from the application having the temporary ID “A0001”, the message type is “CHAT”, and “HELLO” is specified as the message content. The message with the sequence number “3” is transmitted from the application having the temporary ID “B0001”, the message type is “FILE”, and “FILE = BCD.BIN” is specified as the message content.

  In Table 2, messages are already accumulated in the queue, but the queue is created in an empty state that does not contain any messages at the initial stage when the session management means 201 creates the queue.

  Next, processing in the Web browser 1 at the start of application processing will be described with reference to FIG. FIG. 4 is a flowchart showing an example of processing in the Web browser at the start of application processing.

  When the user performs an operation for starting the Web browser 1 in order to participate in the remote cooperation system or the like, the Web browser 1 performs the application 101, the communication management unit 102, the upstream communication unit 103, the downstream communication unit 104, and the communication according to the user operation. The pointer storage unit 105 is activated (step S201).

  As for these activations, as in a general Web browser, by specifying a URL (Uniform Resource Locator) in the Web browser 1, HTML associated with the specified URL is read and 101 defined in HTML is read. Each means of -105 operates. This mechanism is equivalent to an operation using a normal Web browser, and details thereof are omitted here.

  Next, when each means (101 to 105) operates on the Web browser 1, the communication management means 102 acquires the user ID of the user who uses the Web browser 1 (step S202). As a method for the communication management unit 102 to acquire a user ID, for example, a method of acquiring (extracting) a character string described in HTML or a mechanism called Cookie generally provided in a Web browser is used. Various methods such as an acquisition method and prompting the user to input can be considered, but any method may be used as long as acquisition is possible.

  Next, the communication management unit 102 initializes an application that operates on the Web browser 1. At this time, the communication management unit 102 creates a temporary ID for uniquely identifying the application 101 running on the Web browser 1 (step S203).

  Then, the communication management unit 102 passes (outputs) the created temporary ID to each application (step S204). Any value may be used for the temporary ID as long as each application can be identified.

  Next, each application 101 stores the temporary ID output from the communication management unit 102 in a storage device such as a memory. Each application 101 performs a unique initialization process to notify the communication management unit 102 of the completion of initialization, and notifies the message type used by each application 101 (step S205). This message type may be any character string. However, the same message type is not used between different applications 101.

  Next, when receiving (inputting) the message type, the communication management unit 102 causes the pointer storage unit 105 to store “−1” as an initial point together with the message type and the temporary ID of each application 101 (step S206). . Hereinafter, an example of information stored in the pointer storage unit 105 will be described.

  In the example shown in Table 3, “CHAT” and “DOC” are registered as message types, the temporary ID corresponding to “CHAT” is “A0001”, and the temporary ID corresponding to “DOC” is “A0002”. ", Indicating that each pointer is" -1 ".

(Uplink communication)
Next, uplink communication processing will be described with reference to FIG. FIG. 5 is a flowchart showing an example of upstream communication processing in the Web browser and the message relay server. When the user performs an operation for transmitting a message on the application 101 running on the Web browser 1, the application 101 passes the temporary ID, its message type, and the content of the message to the communication management unit 102 according to the user's operation. (Output). Then, the communication management unit 102 generates a request (hereinafter referred to as an HTTP request) using HTTP describing the user ID, temporary ID, message type, and message content, and uses the upstream communication unit 103 to generate a message relay server. 2 to the message receiving means 202. At this time, the uplink communication means 103 transmits a message. An example of an HTTP request for uplink communication is shown below.

POST / Up
UID = User1 & MT = CHAT & TID = C0001 & MSG = Good evening

  In the above example, for “/ Up” indicating the message receiving means 202 of the message relay server 2, the user ID is “User1”, the message type is “CHAT”, the temporary ID is “C0001”, and the message content is “Good evening” "Is sent.

  The message receiving unit 202 of the message relay server 2 receives the above-described HTTP request for uplink communication (step S301).

  Next, the message receiving unit 202 extracts a user ID, a message type, and a temporary ID from the received HTTP request (step S302), and passes (outputs) the message to the message accumulation control unit 203.

  Next, the message accumulation control unit 203 inquires of the session management unit 201 and acquires the session ID of the session in which the received (received) user ID participates (for example, the session management unit 201 stores the user ID from the storage unit). And the session ID stored in association with the message ID is extracted and output to the message storage control unit 203) (step S303).

  Next, the message accumulation control unit 203 acquires (extracts) the queue associated with the acquired session ID from the queue storage unit 204 (step S304).

  Next, the message accumulation control unit 203 acquires (extracts) the last value (that is, the largest number and the newest in time) among the sequence numbers included in the acquired (extracted) queue ( Step S305).

  Next, the message accumulation control unit 203 adds 1 to the acquired (extracted) sequence number (step S306).

  Next, the message accumulation control unit 203 adds the sequence number added with 1, the temporary ID, the message type, and the message content, and updates the queue stored in the queue storage unit 204 (step S307). An example showing the updated queue is shown in Table 4 below.

(Downlink communication)
Next, downlink communication processing will be described with reference to FIGS. 6, 7, 8, 9, and 10. FIG. FIG. 6 is a flowchart showing an example of downlink communication processing in the Web browser. FIG. 7 is a flowchart showing an example of processing in the message transmission means. FIG. 8 is a flowchart showing an example of processing in the transmission message selection means. FIG. 9 is a flowchart showing an example of processing in the response management unit when a message is returned in the message transmission unit. FIG. 10 is a flowchart showing an example of processing in response management means when a history URL is returned. For example, if the user performs an operation for executing catch-up when participating late in the session, the communication management unit 102 of the Web browser 1 starts downlink communication with the user ID in the downlink communication unit 104. Is output (step S401).

  The downlink communication means 104 first determines whether a history URL (details will be described later) is being transmitted (step S402).

  If it is determined in step S402 that the history URL is being transmitted, the downlink communication unit 104 uses the history URL and further specifies a user ID as additional information of the HTTP request, and uses HTTP for downlink communication. A request is generated and transmitted to the message relay server 2 (step S403). As a method for specifying additional information, a method using an arbitrary HTTP header or a method using Cookie is conceivable. In the example shown below, a method using Cookie is used. The HTTP request at this time is, for example, as shown in the following example (only the main part of the HTTP request is described in the following example)

GET / Down? UID = User1 & MT1 = CHAT & TID1 = C0001 & PT1 = −1 & MT2 = DOC & TID2 = C0002 & PT2 = −1
Cookie: UID = User3

  The HTTP request includes “/ Down” indicating the message transmission unit 205 of the message relay server 2 in the URL, “User1” as the user ID, and further, as the first message type, temporary ID, and pointer, Includes “CHAT”, “C0001” and “−1”. The HTTP request includes “DOC”, “C0002”, and “−1” as the second message type, temporary ID, and pointer. In addition, the user ID is “User3” as Cookie.

  If it is determined in step S402 that the history URL is not being transmitted, after a predetermined period has elapsed (step S404), the downlink communication unit 104 obtains the registered message type and each pointer from the pointer storage unit 105. Obtain (extract) (step S405).

  Then, the downlink communication means 104 adds the additional information as in step S403, generates an HTTP request for downlink communication, and transmits it to the message relay server 2 (step S406).

  Next, the message transmission unit 205 of the message relay server 2 receives the HTTP request for downlink communication described above (step S501).

  Next, the message transmission unit 205 extracts a user ID, a message type, a temporary ID, and a pointer from the received HTTP request for downlink communication (step S502). Hereinafter, the message type, temporary ID, and pointer included in the HTTP request for downlink communication are referred to as request message type, request temporary ID, and request pointer, respectively.

  Next, the message transmission unit 205 first acquires the session ID of the session in which the corresponding user ID participates from the session management unit 201 based on the user ID specified in Cookie (step S503).

  Next, the message transmission unit 205 compares the user ID in the URL with the user ID of the cookie (step S504). If the user IDs are different, the message transmission unit 205 passes (outputs) the session ID, request message type, request temporary ID, and request pointer to the transmission message selection unit 206.

  Next, the transmission message selection unit 206 acquires (extracts) the queue associated with the session ID output from the message transmission unit 205 from the queue storage unit 204 (step S601).

  Next, the transmission message selection unit 206 sets the smallest value among the request pointers output from the message transmission unit 205 as an acquisition pointer (step S602).

  Next, the transmission message selection unit 206 determines whether or not a message having a sequence number larger than the value indicated by the acquisition pointer is in the acquired (extracted) queue (step S603).

  When it is determined that there is a corresponding message, the transmission message selection unit 206 adds 1 to the acquisition pointer (step S604), and acquires (extracts) a message having the same sequence number as the acquisition pointer from the queue (step S605). .

  Next, the transmission message selection unit 206 determines whether or not the message type of the acquired (extracted) message is included in the request message type (step S606).

  If it is determined in step S606 that the message is not included, the transmission message selection unit 206 returns the process to step S603.

  On the other hand, if it is determined in step 606 that the message is included, the transmission message selection unit 206 compares the request temporary ID for the request message type with the temporary ID of the acquired (extracted) message, and whether they are the same. It is determined whether or not (step S607).

  If it is determined in step S607 that they are the same, the transmission message selection unit 206 returns the process to step S603.

  On the other hand, if it is determined in step S607 that they are not the same, the transmission message selection unit 206 compares the request pointer for the request message type with the sequence number of the acquired (extracted) message, and the request pointer is based on the sequence number. It is determined whether it is smaller (step S608).

  When it is determined that the sequence number is smaller than the request pointer, or when it is determined that the request pointer and the sequence number have the same value, the transmission message selection unit 206 returns the process to step S603.

  If it is determined that the sequence number is larger than the request pointer, the transmission message selection unit 206 stores the corresponding sequence number as the selected sequence number (step S609). Thereafter, the transmission message selection unit 206 returns the process to step S603.

  If it is determined in step S603 that there is no message having a sequence number larger than the acquisition pointer in the queue (they have been lost due to the processing in steps S604 to 609), the transmission message selection unit 206 has a stored selection sequence number. It is determined whether or not (step S610).

  If it is determined in step S610 that there is at least one selected sequence number, the transmission message selecting unit 206 acquires (extracts) a message corresponding to the stored selected sequence number from the queue (step S611), The message is sent (output) to the message transmission means 205.

  On the other hand, if it is determined in step S610 that there is no selected sequence number, the transmission message selection unit 206 does not pass (output) nothing to the message transmission unit 205 (step S612).

  Next, the message transmission unit 205 determines whether there is a message output from the transmission message selection unit 206 (step S505).

  If it is determined in step S505 that there is no output message, that is, there is no message for a response using HTTP to the HTTP request for downlink communication (hereinafter referred to as an HTTP response), the message transmission unit 205 Returns (transmits) an empty response to the Web browser 1 (step S506).

  On the other hand, if it is determined in step S505 that there is a corresponding message, the message transmission unit 205 arranges the messages in ascending order of the sequence number, and sends an HTTP response including the sequence number, message type, and message content of each message. It is generated and returned (transmitted) to the Web browser 1 (step S507). At this time, if the user ID in the URL is different from the user ID of the cookie, the message sending unit 205 inserts a cache miss character string indicating a response with a different user ID as additional information to the HTTP response. (Addition) is performed (step S508). This can be realized, for example, by inserting (adding) as an HTTP header.

  For example, when a message as shown in Table 4 is accumulated in the queue storage unit 204 and a request for downlink communication as in the above-described example is received, a selection sequence extracted by the transmission message selection unit 206 The numbers are “0”, “1”, and “2”. At this time, the message returned (transmitted) to the Web browser 1 is as follows.

HTTP / 1.1 200 OK
X-STATUS: IDILLEGAL
<-Separator --->
0
CHAT
HELLO
<-Separator --->
1
DOC
FILE = ABC. DOC
<-Separator --->
2
CHAT
Hello
<-Separator --->

  In the above example, “X-STAUS: IDILLEGAL” is a cache miss character string. <-Delimiter ---> is a character string that represents a delimiter between messages. Note that the present invention is not limited to this character string, and any character string may be used as long as it is known that it is a delimiter.

  Further, the message transmission unit 205 passes (outputs) the information of the message returned (transmitted) to the Web browser 1 to the response management unit 208 together with the URL of the HTTP request for downlink communication transmitted from the Web browser 1. ).

  Next, the response management unit 208 determines whether an item (response information) having the same session ID, temporary ID, message sequence number, and message type is already stored in the response information storage unit 207 (S701). ).

  If it is determined that the same is not stored, the response management unit 208 creates a new item in the response information storage unit 207 and stores it as response information together with the URL of the HTTP request for downlink communication (step S702).

  On the other hand, if it is determined that the same information is stored, the response management unit 208 rewrites only the URL item in the corresponding response information with a new URL (step S703). An example of information stored in the response information storage unit 207 is shown below.

  In the example shown in Table 5, messages with sequence numbers 0, 1, and 2 are returned to the session ID “000001”, and the temporary IDs and message types are as shown in the table. In the example shown in Table 5, the URL when the messages having the sequence numbers 0 and 1 are returned to the Web browser is “/ Down? UID = User2 & MT1 = CHAT & TID1 = B0001 & PT1 = −1 & MT2 = DOC & TID2 = B0002 & PT2 = −1”. It is shown that. The URL when the message of sequence number 2 is returned to the Web browser is “/ Down? UID = User1 & MT1 = CHAT & TID1 = A0001 & PT1 = 1”.

  In the example shown in Table 5, a message with a sequence number 0 is returned to the session ID “000002”, the temporary ID is “C0002”, the message type is “FILE”, and the message is a Web browser. When the URL is returned, the URL is “/ Down? UID = A & MT1 = FILE & TID1 = A01 & PT1 = −1”.

  Note that the response information storage unit 207 may store request information other than the URL as information related to the HTTP request for downlink communication to be stored. Further, the response information storage unit 207 may store, for example, the received date and time as information related to the HTTP request for downlink communication.

  In step S504, when the user ID designations of the cookie and the URL match, the message transmission unit 205 checks with the response management unit 208 whether there is response information regarding the acquired session ID (step S509).

  If it is determined in step S509 that there is no response information, the subsequent processing is the same as step S601.

  On the other hand, if it is determined in step S509 that there is response information, the response management unit 208 acquires (extracts) response information having the acquired session ID as target response information from the response information stored in the response information storage unit 209. (Step S801).

  Next, the response management unit 208 uses the smallest value among the received request pointers as an acquisition pointer (step S802), and whether there is response information having a sequence number larger than the value indicated by the acquisition pointer in the target response information. It is determined whether or not (step S803).

  If it is determined that there is corresponding response information, the response management unit 208 adds 1 to the acquisition pointer (step S804), and acquires (extracts) the same response information as the acquisition pointer from the response information storage unit 209. (Step S805). If the response information cannot be acquired (extracted), the response management unit 208 returns the process to step S803.

  If acquisition (extraction) is possible, the response management unit 208 determines whether the message type of the response information acquired (extraction) is included in the request message type (step S806).

  If it is determined that it is not included, the response management unit 208 returns the process to step S803. On the other hand, if it is determined that the request is included, the response management unit 208 compares the request temporary ID for the request message type with the temporary ID of the acquired (extracted) response information. Then, the response management unit 208 determines whether the request temporary ID and the response information temporary ID are the same (step S807).

  If it is determined in step S807 that they are the same, the response management unit 208 returns the process to step S803. On the other hand, if it is determined that they are not the same, the response management unit 208 compares the request pointer for the request message type with the sequence number of the acquired (extracted) response information (step S808).

  When the sequence number is smaller than the request pointer or when the sequence number is the same, the response management unit 208 returns the process to step S803.

  When the sequence number is larger than the request pointer, the response management unit 208 stores the URL included in the acquired (extracted) response information as a history URL in association with the sequence number (step S809). Thereafter, the response management unit 208 returns the process to step S803.

  If it is determined in step S803 that the response information having the sequence number larger than the acquisition pointer is not the target response information, the response management unit 208 determines whether there is a stored history URL (step S810). . If it is determined that there is, the response management unit 208 passes (outputs) the stored history URL to the message transmission unit 205 (step S811). On the other hand, if it is determined that there is no response, the response management means 208 returns nothing (does not output) (step S812).

  Next, the message transmission unit 205 determines whether or not a history URL is returned (output) from the response management unit 208 (step S510). If it is determined that it has not been returned (outputted), the message transmission unit 205 returns an empty response to the Web browser (step S506).

  If it is determined that it has been returned (output), the message transmission unit 205 collects the duplicate history URLs into one (step S511). Then, the message transmission unit 205 generates a history URL response from the history URL and the sequence number, and returns it to the Web browser. For example, it is assumed that a Web browser having a user ID of User3 transmits the following HTTP request for downlink communication.

/ Down? UID = User3 & MT1 = CHAT & TID1 = A0001 & PT1 = −1 & MT2 = DOC & TID2 = A0002 & PT2 = −1
Cookie: User3

  The history URL response at this time is as follows.

0, 1: / Down? UID = User2 & MT1 = CHAT & TID1 = B0001 & PT1 = −1 & MT2 = DOC & TID2 = B0002 & PT2 = −1
2: / Down? UID = User1 & MT1 = CHAT & TID1 = A0001 & PT1 = 1

  The history URL response includes the sequence number of the message that can be acquired by each history URL and the URL character string.

  Next, the downlink communication means 104 of the Web browser 1 receives the HTTP response (or history URL response) (step S407). Then, the downlink communication unit 104 determines whether or not the received response is empty (that is, neither a message nor a history URL is included) (step S408). If it is determined that it is empty, the downlink communication means 104 returns the process to step S402.

  If it is determined that the HTTP response (or history URL response) is not empty, the downlink communication unit 104 analyzes the HTTP response (or history URL response) and includes a message or includes a history URL. Is determined (step S409).

  If it is determined that a message is included, the downlink communication unit 104 extracts messages one by one from the response (step S410), and passes (outputs) the extracted message to the communication management unit 108.

  Next, the communication management unit 108 acquires (extracts) the sequence number and message type of the message received (output) from the downlink communication unit 104. Then, the communication management unit 108 rewrites the pointer value having the same message type stored in the pointer storage device 105 with the acquisition (extraction) sequence number (step S411). Hereinafter, an example of information stored in the pointer storage unit 105 with the sequence number rewritten will be described.

  Next, the communication management unit 108 acquires (extracts) the temporary ID stored in the same row of the pointer storage device 105, and passes the message content included in the message to the application having the extracted temporary ID ( (Step S412). Each application executes processing according to the content of the message.

  If it is determined in step S409 that the history URL is included (that is, the history URL response has been received), the web browser 1 starts transmitting the history URL (step S413). Thereafter, the Web browser 1 executes Step S403 and the subsequent steps. However, if a message other than the sequence number included in the history URL response is received in step S410, the Web browser 1 excludes it.

  At this time, the URL indicated by the HTTP request for downlink communication has been previously transmitted by another Web browser. If a cache device such as a proxy server exists between the Web browser and the message relay server, there is a high possibility that a response to the request is cached there.

  If it is cached in the cache device, the cache device returns a message included in the cache to the Web browser. If it is not included in the cache, the request is transmitted to the message relay server. In this case, since the user ID included in the URL is different from the user ID of the cookie, the processing after step S601 is executed, and the message is returned to the Web browser.

  Then, when the Web browser 1 acquires (receives) the message, the Web browser 1 executes the processing after Step S410 and passes (outputs) the message to the application.

  Next, at this time, the Web browser 1 determines whether or not a cache miss character string is designated as additional information of the received HTTP response (step S414). If it is determined that the URL is not specified, the Web browser 1 transmits a downlink communication request again based on the next history URL specified. On the other hand, if it is determined that the cache miss character string is designated, the Web browser 1 stops transmitting the history URL (step S415), and returns to normal processing.

  As described above, in the present embodiment, the message relay server stores the HTTP response corresponding to the HTTP request in the response information storage unit 207 as history information in association with the URL included in the HTTP request. When the message relay server receives a new HTTP request from the Web browser, the message relay server extracts the URL stored in association with the HTTP response corresponding to the received request, and returns the URL to the Web browser. For this reason, when the Web browser acquires a message, the returned URL can be used to acquire the message stored in the cache. Further, by effectively using the cache, it is possible to omit the process of extracting a message in response to a request received from the Web browser 1 and returning the extracted message to the Web browser 1 in the message relay server. The load can be reduced.

  Next, the minimum configuration of the message transmission / reception system according to the present invention will be described. FIG. 11 is a block diagram illustrating a minimum configuration example of the message transmission / reception system. As shown in FIG. 11, the message transmission / reception system includes response storage means 10, URL extraction means 20, and request generation means 30 as minimum components.

  The message transmission / reception system with the minimum configuration shown in FIG. 11 includes response storage means 10 that stores a response to a message acquisition request and a URL included in the request in association with each other. When a new request is received, the URL extraction unit 20 extracts a URL associated with the response corresponding to the received request from the response storage unit 10. Then, the request generation unit 30 generates a message acquisition request using the URL extracted by the URL extraction unit 20.

  Therefore, according to the message transmission / reception system having the minimum configuration shown in FIG. 11, since the URL from which the message has been acquired in the past can be used at the time of catch-up, the message stored in the cache can be acquired. This also allows the message relay server to omit the process of extracting a message in response to a request received from the Web browser and returning the extracted message to the Web browser, thus reducing the load. It becomes.

  In the present embodiment, the characteristic configuration of the message transmission / reception system as shown in the following (1) to (8) is shown.

  (1) The message transmission / reception system is realized by a plurality of Web browsers (for example, realized by the Web browser 1) and a message relay server (for example, the message relay server 2) that relays message transmission / reception between the plurality of Web browsers. The message relay server includes a response (for example, a session ID, a sequence number, a temporary ID, a message type) to a message acquisition request (for example, realized by an HTTP request) and a URL included in the request. (For example, realized by the response information storage unit 207) and a response corresponding to the received request when a new request is received. A request for transmitting a message acquisition request using the URL extracted by the URL extraction unit (for example, realized by the response management unit 208). A generation unit (for example, realized by the downlink communication unit 104) is provided.

  (2) In the message transmission / reception system, when the message relay server receives the request, the message relay server determines whether or not a response corresponding to the received request is stored in the response storage unit (for example, realized by the response management unit 208) If the determination means determines that it is not stored, the message that extracts the message based on the received request from the storage unit (for example, realized by the queue storage means 204) that stores the transmitted message When the URL extracting unit determines that the determining unit is stored, the URL extracting unit (for example, realized by the transmission message selecting unit 206) returns a URL associated with the response corresponding to the received request. Configure to extract from storage means It may be.

  (3) A message transmission / reception system includes a user terminal equipped with a browser for allowing users to collaborate remotely, and a message relay server that relays message transmission / reception implemented on a server device communicating with the user terminal; And a proxy server (for example, realized by the proxy server 3) having a cache function, and the user terminal is an application (for example, realized by the application 101) for executing processing for performing a collaborative work. A communication management means (for example, realized by the communication management means 102) for controlling communication executed in accordance with the application, and a message generated by the user terminal as a message transmission request (for example, an HTTP request for uplink communication) Uplink communication sent to relay server Stage (for example, realized by the uplink communication unit 103) and a downlink communication unit (for example, realized by the downlink communication unit 104) that transmits a message acquisition request to the message relay server and receives a message generated by another user terminal. And a piece of positional information (for example, a sequence number) where the received message in the queue on the message relay server exists and information (for example, a temporary ID) for specifying an application that processes the message are stored in association with each other. A message storage server (for example, realized by the pointer storage unit 105), the message relay server manages a session of remote collaboration work between users, and manages a relationship between the session and a queue in the session Management means (for example, in session management means 201 A message receiving means for receiving a message transmitted as a message transmission request from the user terminal (for example, realized by the message receiving means 202), and a message storage control means for storing the message in a queue ( (For example, realized by the message storage control unit 203), a queue storage unit (for example, realized by the queue storage unit 204) for storing a message in a queue prepared for each session according to the message storage control unit, and a user Message transmission means (for example, message transmission means) that receives a message acquisition request from the terminal and returns the message indicated by the message acquisition request or the contents of the message acquisition request (for example, history URL) when the message was returned in the past Realized by 205 In response to a message acquisition request from the user terminal, a message to be returned to the user terminal is searched from the messages stored in the queue storage means, and the management information of the message in the message relay server is retrieved. Transmission message selection means for acquiring a message (for example, realized by the transmission message selection means 206), management information in a message relay server of a message transmitted by the message transmission means, and a user terminal received by the message transmission means And a message indicated by the message acquisition request when receiving the message acquisition request from the user terminal, and a response information storage unit (for example, realized by the response information storage unit 207). Has already been sent Determining whether, when the sent is characterized in that it comprises a response management means for outputting the contents of the message acquisition request to the message transmission means (for example, implemented by the response management unit 208).

  (4) In the message transmission / reception system, when the message transmission means returns a message in response to the message acquisition request from the user terminal, the message management information in the message relay server (for example, session ID, sequence number, temporary ID, The content (for example, URL) of the message acquisition request together with the message type may be stored in the response information storage unit.

  (5) In the message transmission / reception system, when the message transmission unit returns a message to the message acquisition request from the user terminal in the message transmission unit, the response management unit determines whether the message requested for acquisition has already been returned in the past. If it is determined that the message has been replied in the past, the content (for example, history URL) of the downlink communication request received when the message is replied is acquired, and the message transmission means acquires the message acquisition request acquired by the response management means May be configured to be transmitted to the user terminal.

  (6) In the message transmission / reception system, when the content (for example, history URL) of the message acquisition request is returned from the message relay server, the downlink communication means generates the message acquisition request again according to the content of the returned message acquisition request. The user information (for example, user ID) indicating the user operating the user terminal in the message acquisition request may be specified as additional information.

  (7) In the message transmission / reception system, when the message transmission unit receives the message acquisition request from the user terminal, the user information included in the content of the message acquisition request and the user information specified as additional information in the message acquisition request If the user information does not match, additional information (for example, a cache miss character string) indicating a miss in the cache is added to the message when returning the message stored by the message storage control means. It may be configured as follows.

  (8) In the message transmission / reception system, when a message is returned from the message relay server, the downlink communication means confirms whether or not information indicating that the cache has failed is added to the additional information of the reply, and adds If so, the reconfiguration of the message acquisition request according to the content of the message acquisition request acquired from the message relay server may be stopped.

  The present invention can be applied to applications such as a remote conference.

DESCRIPTION OF SYMBOLS 1 Web browser 2 Message relay server 3 Proxy server 10 Response storage means 20 URL extraction means 30 Request generation means 101 Application 102 Communication management means 103 Uplink communication means 104 Downlink communication means 105 Pointer storage means 201 Session management means 202 Message reception means 203 Message Accumulation control means 204 Queue storage means 205 Message transmission means 206 Transmission message selection means 207 Response information storage means 208 Response management means

Claims (14)

A user terminal equipped with a browser;
A message relay server that relays message transmission and reception using a plurality of browsers;
The message relay server
Response storage means for storing the management information in the message relay server and the URL included in the request in association with the message requested by the request, which is returned in response to the message acquisition request;
When a new request is received , if a response including the message requested in the request has already been returned, the URL stored in the response storage means is extracted in association with the management information corresponding to the message. URL extracting means for
Response return means for returning a response including the URL extracted by the URL extraction means to the transmission source of the new request,
The user terminal is
When a response including a URL is received from the response reply unit, a request transmission unit that generates and transmits a request for acquiring a message stored in the cache using the URL included in the received response is included. A message transmission / reception system. The message relay server
Message storage means for storing received messages;
When receiving a new request , a determination unit that determines whether or not management information corresponding to the message requested by the received new request is stored in the response storage unit;
And a message extraction means for extracting a message from the message storage means based on the received new request when it is determined that the determination means is not stored,
If the URL extraction means determines that the determination means is stored, the URL extraction means extracts the URL stored in the response storage means in association with the management information corresponding to the message requested by the received new request. ,
The message transmission / reception system according to claim 1, wherein the response reply unit returns a response including the message extracted by the message extraction unit or a response including the URL extracted by the URL extraction unit to the transmission source of the new request. A user terminal equipped with a browser for users to collaborate remotely,
A message relay server that relays message transmission and reception implemented on a server device that communicates with the user terminal;
A proxy server having a cache function,
The user terminal is
An application for executing a process for performing the collaborative work;
Communication management means for controlling communication executed in accordance with the application;
An uplink communication means for transmitting a message generated by the user terminal as a message transmission request to the message relay server;
A downlink communication means for transmitting a message acquisition request to the message relay server and receiving a message generated by another user terminal;
Pointer storage means for storing the location information of the location where the received message is present in the queue on the message relay server and the information specifying the application that processes the message in association with each other;
The message relay server
Session management means for managing a session of remote collaboration work between users, and managing a relationship between the session and a queue in the session;
Message receiving means for receiving a message transmitted as a message transmission request from the user terminal;
Message accumulation control means for accumulating the message in a queue;
In accordance with the message accumulation control means, queue storage means for storing messages in a queue prepared for each session;
A message transmission means for receiving a message acquisition request from the user terminal and returning the message indicated by the message acquisition request or the content of the message acquisition request when the message is returned in the past;
In response to a message acquisition request from the user terminal, a message to be returned to the user terminal is retrieved from the messages stored in the queue storage means, and the message is sent together with management information in the message relay server of the message. Send message selection means for obtaining
Response information storage means for storing, as response information, management information of the message transmitted by the message transmission means in the message relay server and the content of the message acquisition request received from the user terminal received by the message transmission means;
When receiving a message acquisition request from the user terminal, it is determined whether the message indicated by the message acquisition request has already been transmitted, and if it has been transmitted, from the user terminal stored in the response information storage means A message transmission / reception system, comprising: response management means for outputting the contents of a message acquisition request transmitted in the past to the message transmission means as a message acquisition request for acquiring a message stored in a cache. The message transmission unit stores the content of the message acquisition request in the response information storage unit together with the management information in the message relay server of the message when the message is returned in response to the message acquisition request from the user terminal. Message sending / receiving system. The response management means determines whether or not the message requested for acquisition has already been returned in the past when the message transmission means returns a message in response to the message acquisition request from the user terminal, If it is determined that the message is received, the content of the downlink communication request received when the message is returned,
The message transmission / reception system according to claim 3, wherein the message transmission unit transmits the content of the message acquisition request acquired by the response management unit to a user terminal. When the content of the message acquisition request is returned from the message relay server, the downlink communication means generates the message acquisition request again according to the content of the returned message acquisition request, and operates the user terminal for the message acquisition request The message transmission / reception system according to claim 3, wherein user information indicating a user is designated as additional information. When the message transmission means receives the message acquisition request from the user terminal, the message transmission means compares the user information included in the content of the message acquisition request with the user information specified as additional information in the message acquisition request. The message transmission / reception system according to claim 3, wherein when the two do not match, additional information indicating that the cache has been missed is added to the message when the message stored by the message storage control unit is returned. When the message is returned from the message relay server, the downlink communication means checks whether or not information indicating that the cache has failed is added to the additional information of the reply, and if it is added, the message relay The message transmission / reception system according to claim 3, wherein the regeneration of the message acquisition request according to the content of the message acquisition request acquired from the server is stopped. A message relay server that relays message transmission and reception using multiple browsers,
Response storage means for storing the management information in the message relay server and the URL included in the request in association with the message requested by the request, which is returned in response to the message acquisition request;
When a new request is received , if a response including the message requested in the request has already been returned, the URL stored in the response storage means is extracted in association with the management information corresponding to the message. URL extracting means for
A message relay server comprising: a response reply unit that returns a response including the URL extracted by the URL extraction unit to the transmission source of the new request in order to acquire a message stored in the cache . Message storage means for storing received messages;
When receiving a new request , a determination unit that determines whether or not management information corresponding to the message requested by the received new request is stored in the response storage unit;
When it is determined that the determination unit is not stored, the message extraction unit extracts a message from the message storage unit based on the received new request,
If the URL extraction means determines that the determination means is stored, the URL extraction means extracts the URL stored in the response storage means in association with the management information corresponding to the message requested by the received new request. ,
The message relay server according to claim 9, wherein the response reply unit returns a response including the message extracted by the message extraction unit or a response including the URL extracted by the URL extraction unit to the transmission source of the new request. A response storage step of storing in the response storage unit the management information of the message requested in the request and the URL included in the request, which are returned in response to the message acquisition request;
When a new request is received , if a response including the message requested in the request has already been returned, the URL stored in the response storage unit is extracted in association with the management information corresponding to the message. A URL extracting step,
A response reply step of returning a response including the extracted URL to the transmission source of the new request;
Receiving a response including a URL, and generating a request for acquiring a message stored in the cache using the URL included in the received response, and transmitting a request. To send and receive messages. A message storage step of storing the received message in the message storage unit;
When receiving a new request , a determination step of determining whether or not management information corresponding to the message requested by the received new request is stored in the response storage unit;
Determining that it is not stored, including a message extraction step of extracting a message from the message storage unit based on the received new request;
If it is determined in the URL extraction step that it is stored in the determination step, the URL stored in the response storage unit is extracted in association with the management information corresponding to the received message requested by the new request. ,
The message transmission / reception method according to claim 11, wherein in the response reply step, a response including the extracted message or a response including the extracted URL is returned to the transmission source of the new request. To a computer that relays the sending and receiving of messages using multiple browsers,
A response storage process for storing, in the response storage unit , the management information in the computer and the URL included in the request of the message requested in the request that is returned in response to the message acquisition request; ,
When a new request is received , if a response including the message requested in the request has already been returned, the URL stored in the response storage unit is extracted in association with the management information corresponding to the message. URL extraction processing to
A message transmission / reception program for executing response return processing for returning a response including an extracted URL to the transmission source of the new request in order to acquire a message stored in a cache. On the computer,
Message storage processing for storing the received message in the message storage unit;
When receiving a new request , a determination process for determining whether or not management information corresponding to the message requested by the received new request is stored in the response storage unit;
If it is determined that the message is not stored, a message extraction process for extracting a message from the message storage unit based on the received new request is executed,
If it is determined in the URL extraction process that it is stored in the determination process, the URL stored in the response storage unit is extracted in association with the management information corresponding to the message requested by the received new request. ,
14. The message transmission / reception program according to claim 13, wherein a response reply process executes a process of returning a response including the extracted message or a response including the extracted URL to a transmission source of the new request.

Images