JP2009027534A - Device, system and method for performing file transmission/reception utilizing http - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a device for performing protocol conversion so that a hypertext transfer protocol (HTTP) may become available for a next generation network (NGN). <P>SOLUTION: A communication terminal device in an NGN network which establishes a session for a speech and data communication via a connection management server includes: a file transfer module which is connected with an HTTP client for performing conversion of a protocol for NGN and HTTP and transmission/reception of data; a storage device which is connected with the HTTP client and the file transfer module for storing data; and the HTTP client connected with the storage device and the file transfer module. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technology for performing protocol conversion between HTTP and an NGN (Next Generation Network) file protocol by providing an NGN-compatible device with a function of an HTTP (Hypertext Transfer Protocol) server in a next-generation network, so-called NGN.

  In recent years, improvements in convenience and the like have been realized by reconstructing the current telephone network using IP technology. This is called a so-called NGN (New Generation Network). NGN is an IP network, and the protocol used is SIP (Session Initiation Protocol). This is a protocol for realizing call control mainly by IP telephone.

  When sending a file to a specific partner via the Internet, the file is currently sent using a file transfer service using HTTP. However, with this method, there is a limit to the size of a file that can be transmitted, and there is a risk of information leakage because it passes through a third party server.

When a file is transmitted using the NGN network, the file is directly exchanged between terminals. Therefore, the above problem does not occur and high-speed transfer is possible.
When performing file transmission and reception using NGN, the file to be transmitted must be set in the NGN compatible telephone. In order to view the received file, it is necessary to retrieve the file from the NGN compatible telephone after receiving the file. When these operations are performed via the LAN using an information terminal, software used in the information terminal is required.

Patent Document 1 discloses that protocol conversion is performed in communication between an electronic control device mounted on a vehicle and a data reading device.
JP 2006-352201 A

  When developing dedicated software, development costs and maintenance costs are required. Software developers must also publish the specifications of the developed software to third parties. This publication requires complicated procedures.

  In order to solve the above-described problems, the present invention is widely used in the NGN protocol and the Internet in a communication terminal apparatus in an NGN network that establishes a session for a telephone call and data communication via a connection management server. Provided is a communication terminal device equipped with a file transfer module that performs conversion with HTTP.

  Since the NGN-compatible communication terminal is provided with a conversion function between the NGN protocol and HTTP, a file having a large file size can be transferred without being restricted by the server.

  The example of the present embodiment assumes a telephone device compatible with NGN as a communication terminal. In particular, it is possible to convert HTTP, which is a protocol used by the telephone, on the Internet, and SIP, which is a protocol for NGN. In the following, first, NGN will be schematically described, and then an example of the embodiment will be described.

(About NGN)
An outline of NGN will be described using FIG. 1 while comparing with a conventional telephone network. As shown in FIG. 1A, in the conventional subscriber telephone network 81, a fixed line 84 is connected between the caller terminal 82 and the callee terminal 83 when exchanging call voice. Once the line is connected, stable quality calls can be realized.

  On the other hand, in the NGN, as shown in FIG. 1B, the calling terminal 82 and the receiving terminal 83 are connected to the IP telephone adapter 85, respectively. The IP telephone adapter 85 is a device that divides a call voice into IP packets and transmits the voice packets, or converts received IP packets into voice. An NGN-compatible telephone (not shown) may have an IP telephone adapter 85 built therein. In the example of the present embodiment described below, an NGN-compatible telephone is assumed.

  FIG. 2 is a flowchart of session establishment in NGN. In establishing an NGN session, first, the calling telephone transmits a connection request (INVITE request) to the SIP server, which is a connection management server (step S100). The SIP server delivers the received INVITE request to the called telephone (step S101). Thereafter, the SIP server returns “100 Trying” as a status code indicating that the request has arrived at the receiving side and is being called to the calling side telephone (step S102).

The called telephone returns a status code “100Trying” to the SIP server as a provisional response until the telephone response is made (step S103). Further, the receiving side telephone returns a status code “180 Ringing” indicating that the ringing tone is sounding to the SIP server (step S104). The SIP server transmits a status code “180 Ringing” to the caller telephone (step S105) to notify that it is ringing.
When the telephone on the called side answers the telephone, a status code “200ok” indicating the response is returned to the SIP server (step S106). Further, the SIP server transmits a status code “200 ok” to the caller telephone (step S107).

  Upon receiving the response, the calling side telephone transmits an “ACK request” informing the SIP server that the response has been received (step S108). The SIP server transmits the received “ACK request” to the called telephone (step S109). Thereby, both communication is completed and data communication can be performed (step S110).

  When an NGN call is made, an IP packet 86 is first generated by the IP telephone adapter 85. For transmission of the generated IP packet 86, SIP (session initiation protocol) for performing call control is used. The IP packet 86 is transmitted through a SIP server 88 and a router 87 that control a call. The router 87 also has a QoS (quality of service) function that keeps the quality of speech voice carried by the IP packet 86 constant.

  QoS classifies IP packets 86 by type, and the router 87 changes the transfer order according to the type. For example, if the voice packet is delayed, the call quality deteriorates. Therefore, the router 87 preferentially transfers the voice packet. The classification of the IP packet 86 is performed based on information (specifically, ToS “type of service”) written in the IP header.

  In this way, the NGN integrates the IP network for the Internet service and the telephone network for the telephone service, which are currently constructed separately, as an IP communication network in which QoS is improved by using the IP technology, and the current public network Next-generation IP network that replaces In addition, since communication is performed using IP packets, not only voice but also video and other data can be transmitted and received.

(Network outline)
FIG. 3 is an overview diagram of an example of the present embodiment. As shown in the figure, the NGN compatible communication terminals 1 and 1 'are connected to the NGN. The NGN compatible communication terminals ₁ and _{1 ′} are, for example, an NGN compatible telephone 10 and an NGN compatible modem 10 ₁ . The NGN compatible communication terminals 1 and 1 ′ are connected to the personal computer 5 as an information terminal, for example. The connection may be either wired or wireless.
When transmitting the file to the other party, an HTTP request with the file to be transmitted is transmitted to the NGN compatible telephone 10. The NGN-compatible telephone 10 as the NGN-compatible communication terminal 1 ′ that has received this converts the HTTP request into a file transfer protocol, and transmits the file to the partner terminal (NGN-compatible telephone). Receiving it, the NGN-compatible telephone 10 stores the file in its own storage device. The file is acquired by the HTTP client.

  FIG. 4 is a functional block diagram of the NGN compatible telephone 10 and the HTTP client 20 in the present embodiment. The NGN-compatible telephone 10 includes an NGN signaling module 11 for making and receiving calls, an NGN file transfer module 12 for transferring files, an HTTP server 13 for receiving requests from the HTTP client 20, and a storage device for storing received files 14. The HTTP client 20 is connected to the NGN compatible telephone 10.

(Sending flowchart)
Next, the flow at the time of file transmission is shown in FIG.
The HTTP client 20 transmits an HTTP request including the destination telephone number, the reserved bandwidth, the attached file name, and the file contents to the HTTP server 13 of the NGN compatible telephone 10 (step S1). The HTTP server 13 stores the received file in the storage device 14 (step S2).

  Further, the HTTP server 13 transmits a file transmission request to the NGN file transfer module 12 (step S3). When receiving the file transmission request, the NGN file transfer module 12 transmits the file transmission request to the NGN signaling module 11 (step S4).

  The NGN signaling module 11 transmits a signaling start request to the transmission destination terminal (step S5). The NGN signaling module 11 receives a signaling response from the destination terminal (step S6).

  Next, the NGN signaling module 11 transmits a file transmission start request to the NGN file transfer module 12 (step S7). When receiving the file transmission start request, the NGN file transfer module 12 acquires a file to be transmitted from the storage device 14 (step S8).

  The NGN file transfer module 12 transmits the file received from the storage device 14 to the transmission destination terminal (step S9). Finally, the NGN signaling module 11 receives a disconnection request from the transmission destination terminal (step S10).

  In this way, by converting HTTP to a protocol for NGN, a file can be sent to the other party using NGN.

(Flow chart when receiving)
FIG. 6 shows the flow when receiving a file. The NGN signaling module 11 receives the signaling start request (step S21). The NGN signaling module 11 transmits the received file reception start request to the NGN file transfer module 12 (step S22), and transmits a signaling response to the counterpart terminal (step S23).

  Next, the NGN file transfer module 12 receives the file from the transmission source terminal (step S24), and stores the file in the storage device 14 (step S25). After the saving is completed, the NGN file transfer module 12 transmits a disconnection request to the NGN signaling module 11 (step S26).

  The NGN signaling module 11 transmits a disconnection request to the counterpart terminal (step S27). This disconnection request corresponds to step S10 in FIG. A file acquisition request is transmitted from the HTTP client 20 to the HTTP server 13 (step S28). The HTTP server 13 acquires a file from the storage device 14 (step S29). The HTTP server 13 transmits the acquired file to the HTTP client 20 (step S30).

Below, the example of the user interface in the case of using a WEB browser as the HTTP client 20 is shown.
FIG. 7 shows an example of the transmission screen 30. A telephone number is entered in the destination telephone number field 31 in the figure. In the QoS column 32, a reserved bandwidth is input. The QoS column 32 may be a method in which, for example, preset numerical values are displayed as a pop-up menu, and a desired numerical value is input by clicking. In the file name column 33, a file to be transmitted is designated. In order to specify a file name, a reference button 35 is arranged in the vicinity of the input area, and the file is displayed in a so-called tree format, which can be used for input. When the input of the file name is completed, the file transmission is started by clicking the transmission button 34.

Next, FIG. 8 shows an example of a transmission / reception status confirmation screen. The transmission status includes a destination telephone number 41 _{1 being} transmitted, a file name 42 ₁ , transmission progress rates 46 ₁ and 47 ₁ indicating how much of the entire transmission file has been transmitted, and a file size 43 _{1 of the} transmission file. Thus, the transmission bandwidth 44 ₁ and the remaining time 45 ₁ until all the files are transmitted can be confirmed. By clicking the cancel button ₄₈ 1, 49 ₁ to stop the transmission, you can abort the file transmission.

Similarly, the reception status includes the transmission source telephone number 41 ₂ , the file name 42 _{2 of} the received file, the reception progress rate 46 ₂ , 47 ₂ indicating how much of the received file has been received, The file size 43 _{2 of} the received file, the reserved bandwidth for reception 44 ₂ , and the remaining time 45 ₂ until all the files are received can be confirmed. By clicking the cancel button 48 _2, you can abort the file received. For files that have been received, the reception stop button is changed to a download button 49. When you click on the download button 49 _2, you can download the file.

  An example of the black list setting screen 50 is shown in FIG. This is a function of blocking mails unilaterally transmitted to an unspecified number of users, such as spam mails that have become a problem in recent years. With this function, file transmissions from the phone numbers set in the blacklist can be automatically rejected.

  When a telephone number is added to the black list 53, the telephone number to be added is input to a predetermined input field 51 and the add button 52 is clicked. Further, when deleting a telephone number from the black list 53, it is performed by selecting a target telephone number from the list and clicking the delete button 54. Finally, the change of the list is reflected by clicking the change button 55.

  An example of an HTTP request transmitted from a WEB browser when performing file transmission / reception in this way is shown. FIG. 10 shows an example 60 of an actual HTTP message. As shown in the figure, multipart / form-data is specified in Content-Type 61, and the destination telephone number, reserved bandwidth, file name, and file contents are set.

FIG. 11 shows an example 70 using SOAP (Simple Object Access Protocol) as an example of outputting an HTTP request from a CE (Consumer Electronics) device or the like not equipped with a WEB browser. For example, an HDD (Hard disk drive) recorder can be assumed as the CE device.
In the SOAP BODY section 71 of FIG. 11, a destination telephone number, a reserved bandwidth, and a file name are designated, and the contents of the file are set as a MIME attachment.

FIG. 12 shows an example 80 when a WebDAV (Web-based Distributed Authoring and Versioning) protocol is used as another format of the HTTP request.
Using the HTTP PUT method 81, a file type is specified in the Content-Type header 82, and a file name is specified in the Content-Disposition header 83. When the WebDAV protocol is used, the destination telephone number and reserved bandwidth cannot be specified. Therefore, only the file upload to the NGN compatible telephone is performed, and the actual transfer process is performed via a WEB browser or the like.

Next, an example 90 of a message obtained by converting the above HTTP request into the NGN file transfer protocol is shown.
FIG. 13 shows a message corresponding to step S5 in FIG. 5 and step S1 in FIG. 6, and performs signaling for file transfer. The destination telephone number is described in the SIP request line 91 and the To header 92.

  FIG. 14 shows an example 100 of a message corresponding to step S9 in FIG. 5 and step S4 in FIG. 6, and actual file transfer is performed. A file name is described in the Content-Disposition header 101, and a file is described in the body part 102.

  The example of this embodiment can transmit and receive files using NGN. In the Internet, which is now widely spread, for example, when trying to transmit a file of several tens of MB (for example, a moving image has a file size of 10 MB to 100 MB or more), the server may not accept the transmission.

This is because sending a file having a large file size affects other users because a large load is applied to the server, and the server is set so that a file larger than a predetermined file size cannot be sent.
However, in the example of the embodiment as described above, there is no limit on the file size to be transmitted. This is because the telephone is usually used by an individual, and even if a load is applied to the server of the NGN compatible telephone, it does not affect other users.

  As described above, by using an NGN-compatible telephone as an HTTP server, a server that has conventionally been used in consideration of the convenience of other users can be freely used. Therefore, the file size to be transmitted or received is not limited.

Next, examples of other embodiments will be described. Since the mail file transmission and reception methods are the same, the configuration of the apparatus will be described. FIG. 15 is a block diagram showing a state in which the NGN compatible telephone 10 and the device 15 that performs protocol conversion are separated. That is, the NGN compatible telephone 10 in this case does not have a protocol conversion function. The protocol converter 15 is connected to the NGN compatible telephone 10. This connection may be wired or wireless. The protocol conversion device 15 includes an HTTP client 20, and specifically, for example, a personal computer can be assumed.
As illustrated, the protocol conversion device 15 includes a storage device 14, an HTTP client 20, an HTTP server 13, and an NGN file transfer module 12.

FIG. 16 shows an example in which the protocol conversion device 60 is connected to the information terminal 50 having the HTTP client 20. By using a personal computer for the information terminal 50 and connecting to the NGN compatible telephone 10, the example of the present embodiment can be realized.
The file transmission / reception method is the same as described above. The information terminal 50 and the NGN compatible telephone 10 are connected, and information is transferred between the NGN file transfer module 12 and the NGN signaling module 11. The file transmission / reception is the same as described in the transmission flowchart and the reception flowchart.

(A) is the schematic of the conventional telephone network, (b) is the schematic of NGN. It is a flowchart at the time of session establishment. It is the schematic of the example of this Embodiment. It is a functional block diagram of the example of this Embodiment. It is a flowchart of the transmission side at the time of file transfer. It is a flowchart of the receiving side at the time of file transfer. It is an example of a file transmission screen. It is an example of the transmission / reception status confirmation screen of a file. It is an example of a black list setting screen. It is an example of the HTTP message of file transmission. It is an example of SOAP among the HTTP message examples of file transmission. This is an example of WebDAV among HTTP message examples of file transmission. It is an example of the signaling message for file transfer. It is an example of the message at the time of performing file transfer in NGN. It is a block diagram of the state which isolate | separated the apparatus which performs a NGN corresponding telephone set and protocol conversion. This is an example in which the protocol conversion apparatus is connected to an information terminal having an HTTP client.

Explanation of symbols

  10 ... NGN compatible telephone, 11 ... NGN signaling module, 12 ... NGN file transfer module, 13 ... HTTP server, 14 ... storage device, 20 ... HTTP client

Claims (7)

In a communication terminal device in an NGN network that establishes a session for calling and data communication via a connection management server,
A file transfer module that connects to an HTTP client, converts between an NGN protocol and HTTP, and transmits and receives data;
A storage device connected to the HTTP client and the file transfer module to store data;
An HTTP client connected to a storage device and a file transfer module. The communication terminal device according to claim 1, wherein the communication terminal device is a telephone or a modem. The communication terminal device according to claim 1, wherein the communication terminal device is connected to an information terminal. The communication terminal device according to claim 1, further comprising an HTTP server, and making a reservation of a communication band at the time of transmission with respect to the file transfer module via the HTTP server. In a communication system in an NGN network that establishes a session for calling and data communication via a connection management server,
A file transfer module that connects to an HTTP client, converts between an NGN protocol and HTTP, and transmits and receives data;
A storage device connected to the HTTP client and the file transfer module and storing data;
A communication terminal device having an HTTP client connected to the storage device and the file transfer module is connected to the network;
system. In an information transmission method in an NGN network for establishing a session for a call and data communication via a connection management server,
Receiving a file to be transmitted by an HTTP server using HTTP;
Transferring the received file from the HTTP server to the file transfer module;
Transmitting a file received by the file transfer module using a protocol for NGN;
Having
Information transmission method. In an information receiving method in an NGN network for establishing a session for a call and data communication via a connection management server,
Receiving a file with a protocol for NGN;
Storing the received file in a storage device;
An HTTP server receiving a file stored in a storage device;
An HTTP server transferring the received file to an HTTP client using a mail transfer protocol;
An information receiving method.

Images