WO2010150457A1 - 中継装置及びその方法 - Google Patents
中継装置及びその方法 Download PDFInfo
- Publication number
- WO2010150457A1 WO2010150457A1 PCT/JP2010/003402 JP2010003402W WO2010150457A1 WO 2010150457 A1 WO2010150457 A1 WO 2010150457A1 JP 2010003402 W JP2010003402 W JP 2010003402W WO 2010150457 A1 WO2010150457 A1 WO 2010150457A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- domain name
- dns
- response packet
- information providing
- relay
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
- H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
Definitions
- the present invention relates to a relay device that relays data transmitted and received on a communication network and a method that is implemented by the relay device.
- the QoS technology is used for a relay device that relays communication in a communication path between a content providing device that provides content and a content using device that uses the content.
- QoS technology for example, in the IEEE (Institut of Electrical and Electronics Engineers) 802.11e standard, the QoS technology of a relay device used in a wireless LAN (Local Area Network) is standardized.
- PLC Power Line Communications
- a bandwidth necessary for transmitting content on a communication path is reserved so that a packet is not discarded or delayed in real-time communication, and a constant communication speed is guaranteed.
- the relay device on the communication path secures the bandwidth resource to the next relay device in accordance with the bandwidth setting request issued by the content using device, transfers the bandwidth setting request to the content providing device, and the content using device And bandwidth resources between the content providing apparatus and the content providing apparatus.
- services such as real-time delivery of audio and video, videophone calls, etc. that do not allow delay or stop of communication can be transmitted with priority over other services.
- FIG. 18 is a diagram for explaining a conventional band setting method used in Patent Document 1.
- a content using device hereinafter referred to as a terminal device
- a content providing device hereinafter referred to as a server
- the terminal device 601 requests bandwidth setting with a requested bandwidth of 18 Mbps initially, a minimum bandwidth of 12 Mbps, and an incremental bandwidth of 3 Mbps.
- the value in parentheses on the arrow of each flow shown in FIG. 18 represents the value of the bandwidth setting information of the bandwidth setting request (requested bandwidth, minimum bandwidth, incremental bandwidth).
- the unit of each band is Mbps, but the unit is omitted.
- the terminal device 601 transmits a bandwidth setting request to the server 604.
- the relay device 602 receives and analyzes the bandwidth setting request transmitted by the terminal device 601, provisionally secures the 18 Mbps bandwidth indicated by the requested bandwidth, and outputs the bandwidth setting request to the server 604 side.
- the relay device 603 rewrites the value indicated by the requested bandwidth to 15 Mbps, and outputs a bandwidth setting request to the server 604 side.
- the server 604 creates a bandwidth setting response including the value indicated by the requested bandwidth of the bandwidth setting request as an acquired bandwidth, and transmits it to the terminal device 601.
- the relay device 603 secures the temporarily secured bandwidth and outputs the bandwidth setting response to the terminal device 601 side.
- a band is secured at 15 Mbps, and a band setting response is output to the terminal device 601 side.
- the terminal device 601 Upon receiving the bandwidth setting response, the terminal device 601 recognizes that the bandwidth setting has succeeded at 15 Mbps, and issues a content transmission request to the server 604 at the bandwidth of 15 Mbps.
- the server 604 changes the content rate to the value indicated by the requested bandwidth, and transmits the content to the terminal device 601 at the rate.
- the parameters are the source IP address of the server 604 for identifying whether the packet should be quality guaranteed, the destination IP address of the terminal device 601, information on the bandwidth necessary for transmitting the content, and the like. is there.
- the terminal apparatus 601 requests the relay apparatuses 602 and 603 to reserve a band
- the terminal apparatus 601 directly transmits a bandwidth setting request control packet including these parameters to the relay apparatuses 602 and 603 or via another server. Therefore, it is necessary to transmit to the relay devices 602 and 603.
- the relay devices 602 and 603 were able to grasp and set the identification information of the content packet and the bandwidth necessary for content packet transmission.
- the terminal device 601 generates the control packet
- the server 604 returns the control packet transmitted from the terminal device 601 to the terminal device 601, and the relay devices 602 and 603.
- a function for setting various parameters for processing a control packet and reserving a bandwidth had to be provided. That is, on the communication path, there is a usage limitation that all of the server 604, the terminal device 601, and the relay devices 602 and 603 must have a function related to QoS processing. For this reason, if there is even one device that does not have a function related to QoS processing on the communication path, quality assurance regarding content transmission cannot be performed. This may be a major limitation in a home network where various devices such as new products, old products, and products of other manufacturers are expected to be mixed.
- the present invention has been made in view of the above problems, and even in a network including a device that does not have a function related to QoS processing, the communication quality in content distribution is ensured, and the disturbed video is transmitted to the terminal device. It is an object of the present invention to provide a relay device that prevents distribution and a method performed by the relay device.
- a first aspect of the present invention is a relay device that interconnects a first network and a second network to relay packet transmission / reception, the first information providing device having a first domain name
- a terminal device that requests acquisition of content, a first communication unit that communicates via a first network, a first information providing device, and a second communication that communicates via a second network
- a storage unit that stores the service information table in association with the parameter, the first domain name, and the parameter related to content transmission, and the second communication unit are transmitted from the terminal device to the first information providing device.
- a response packet transmitted from the first information providing device to the terminal device is received as a response to the acquired content acquisition request, it is determined whether or not the response packet indicates a transfer request, and a response packet is received. If There it is determined that indicates the transfer request, and a control unit of the second domain name indicating the second information providing apparatus included in the response packet in association with the first domain name is stored in the service information table.
- the control unit detects a response packet in which the IP address of the first information providing device is described as a transmission source from the response packet received by the second communication unit, and analyzes the detected response packet for transfer request analysis.
- a response packet detection unit that outputs to the transmission unit, a transfer packet analysis unit that analyzes the response packet detected by the response packet detection unit and determines whether the response packet indicates a transfer request, and a response packet that indicates a transfer request.
- a second domain name indicating the second information providing apparatus included in the response packet is associated with the first domain name and stored in the service information table.
- the transfer request analysis unit analyzes an HTTP (HyperText Transfer Protocol) message as a response packet, and determines that the response packet indicates a transfer request when the response packet indicates HTTP redirect.
- HTTP HyperText Transfer Protocol
- the relay device may further include a second control unit that determines whether or not QoS processing is necessary.
- the second communication unit communicates with a DNS (Domain Name System) server via the second network.
- the second control unit is configured to detect a DNS response packet that is a response to the DNS request packet transmitted from the terminal device to the DNS server, and from the DNS response packet detected by the DNS detection unit, a predetermined domain name and A DNS analysis unit that extracts an IP address corresponding to a predetermined domain name, and determines whether or not the predetermined domain name extracted by the DNS analysis unit is registered in the service information table.
- a QoS necessity determination unit that determines that the predetermined domain name is a domain name that requires QoS processing.
- the QoS necessity determination unit When it is determined that the predetermined domain name extracted by the DNS analysis unit is registered in the service information table, the QoS necessity determination unit outputs the IP address extracted by the DNS analysis unit to the response packet detection unit.
- the first communication unit refers to the service information table when the QoS necessity determination unit determines that the predetermined domain name included in the DNS response packet matches the first domain name.
- a QoS processing unit is further provided for setting a parameter related to the QoS processing associated with the domain name in a relay packet of content transmitted from the first information providing apparatus to the terminal apparatus.
- the first communication unit refers to the service information table when the QoS necessity determination unit determines that the predetermined domain name included in the DNS response packet matches the second domain name, A QoS processing unit that sets a parameter related to the QoS processing associated with the domain name and associated with the first domain name in a relay packet of content transmitted from the second information providing apparatus to the terminal apparatus; You may prepare.
- the storage unit may further store a QoS management table that stores parameters relating to the QoS processing.
- the QoS necessity determination unit determines a parameter corresponding to the predetermined domain name from the service information table. get.
- the second control unit further includes a QoS registration unit that stores the parameter acquired by the QoS necessity determination unit in the QoS management table.
- the first communication unit refers to the QoS management table and relays a parameter related to the QoS processing associated with the relay packet of the content transmitted from the information providing apparatus corresponding to the predetermined domain name to the terminal apparatus.
- a QoS processing unit to be set in the packet.
- the transfer request is HTTP redirect.
- a relay device that interconnects a first network and a second network to relay packet transmission / reception, the first information providing device having a first domain name.
- a terminal device that requests content transmission, a first communication unit that communicates via a first network, a second communication unit that communicates with a DNS server via a second network, A storage unit that associates a domain name of 1 with a parameter related to content transmission and stores it as a service information table, and a second communication unit corresponds to a predetermined domain name transmitted from the terminal device to the DNS server
- a DNS response packet that is a response to a DNS request packet that requests an IP address and includes a predetermined domain name and a second domain name that represents an alias of the predetermined domain name.
- the second domain name included in the DNS response packet is And a controller that stores the service information table in association with the first domain name.
- the resource record type of the DNS response packet including the second domain name representing the alias of the predetermined domain name in the DNS response packet is CNAME (Canonical NAME for an alias).
- the relay apparatus transmits a transfer request (HTTP) that the information providing apparatus transmits to the terminal apparatus.
- HTTP transfer request
- the relay device can guarantee the communication quality by identifying the content distributed from the information providing device having a different domain name and performing the QoS process.
- the user can view high-quality content without video interruptions or disturbances.
- the relay device designates the IP address of the information providing device that transmits the QoS target content included in the DNS response packet, analyzes the payload portion of the HTTP packet having the designated information providing device IP address, An HTTP packet transmitted from a server other than the information providing apparatus having the designated IP address is not analyzed. This eliminates the need for the relay device to analyze the payload (message) portion of all HTTP packets, thereby suppressing an increase in CPU load and avoiding a decrease in communication throughput.
- the relay device transmits the DNS response packet from the DNS server to the terminal device even when the IP address of the information providing device is not included and the alias domain name is included as CNAME.
- the domain name of the alias of the information providing apparatus which is CNAME is detected, and the service information table in which the domain name is associated with the service parameter corresponding to the domain name is updated.
- the relay device can guarantee the communication quality by identifying the content distributed from the information providing device of the alias domain name and performing the QoS process. As a result, the user can view high-quality video content without video interruptions or disturbances.
- FIG. 1 is a diagram showing an example of a network configuration in the first embodiment of the present invention.
- FIG. 2 is a functional block diagram showing an example of the configuration of the relay device 130 according to the first embodiment of the present invention.
- FIG. 3 is a diagram showing an example of a memory structure of the service information table 312 according to the first embodiment of the present invention.
- FIG. 4 is a diagram showing an example of a memory structure of the service information table 312 according to the first embodiment of the present invention.
- FIG. 5 is a diagram showing an example of the memory structure of the QoS management table 315 according to the first embodiment of the present invention.
- FIG. 6 is a diagram for explaining a packet configuration of a DNS packet used in the first embodiment of the present invention.
- FIG. 1 is a diagram showing an example of a network configuration in the first embodiment of the present invention.
- FIG. 2 is a functional block diagram showing an example of the configuration of the relay device 130 according to the first embodiment of the present invention.
- FIG. 3 is
- FIG. 7 is a diagram for explaining a packet configuration of an HTTP packet used in the first embodiment of the present invention.
- FIG. 8 is a sequence diagram showing the operation of each device in the network according to the first embodiment of the present invention.
- FIG. 9 is a sequence diagram showing the operation of each device in the network according to the first embodiment of the present invention.
- FIG. 10 is a flowchart showing details of the operation in the relay device 130c according to the first embodiment of the present invention.
- FIG. 11 is a functional block diagram showing an example of the configuration of the relay device 130 according to the second embodiment of the present invention.
- FIG. 12 is a diagram showing an example of a memory structure of the service information table 404 according to the second embodiment of the present invention.
- FIG. 13 is a diagram for explaining a packet configuration of a DNS packet used in the second embodiment of the present invention.
- FIG. 14 is a sequence diagram showing the operation of each device in the network according to the second embodiment of the present invention.
- FIG. 15 is a flowchart showing details of the operation in the relay device 130c according to the second embodiment of the present invention.
- FIG. 16A is a functional block diagram showing an example of the configuration of the relay device 130 according to the third embodiment of the present invention.
- FIG. 16B is a functional block diagram illustrating an example of the configuration of the relay device 130 according to the third embodiment of the present invention.
- FIG. 17 is a diagram illustrating the priority control process of the QoS processing unit 304 used in each embodiment of the present invention.
- FIG. 18 is a diagram for explaining a conventional band setting method.
- PLC Power Line Communications
- FIG. 1 is a diagram showing an example of a network configuration in the first embodiment of the present invention.
- the network of this embodiment includes various information providing devices (content servers) 100a to 100b, various terminal devices 110a to 110b, and a DNS server 120.
- the information providing devices 100a to 100b and the terminal devices 110a to 110b are connected via relay devices 130a to 130c.
- the terminal devices 110a to 110b are respectively connected to the relay devices 130a to 130b by Ethernet (registered trademark) cables.
- the relay apparatuses 130a to 130c are connected via a first network (for example, a power line network) 140.
- the information providing apparatuses 100a to 100b and the DNS server 120 are connected to the relay apparatus 130c via the second network (for example, the Internet) 150.
- the relay device 130 when referring to the generic name of the relay devices 130a to 130c, it is simply referred to as the relay device 130, and when referring to the generic name of the terminal devices 110a to 110b, it is simply referred to as the terminal device 110, and the information providing devices 100a to 100b.
- the information providing apparatus 100 When referring to a generic name, it is simply referred to as the information providing apparatus 100.
- FIG. 1 the case where there are three relay devices 130a to 130c, two terminal devices 110a to 110b, and two information providing devices 100a to 100b is shown. However, these numbers are merely examples. Any number of devices can be provided.
- the information providing apparatus 100 holds various contents and transmits the contents to the terminal device 110.
- the information providing device 100 may be, for example, an AV server that provides AV content to the terminal device 110 or a music server that provides music content.
- the information providing apparatus 100a and the information providing apparatus 100b have different domain names and different IP addresses.
- the terminal device 110 has a function of receiving content from the information providing device 100 and reproducing video and audio.
- the terminal device 110 may be a device such as a television or a personal computer.
- the various terminal devices 110 are distinguished as a terminal device 110a and a terminal device 110b.
- the DNS server 120 associates the domain name indicating the host name of the information providing apparatus 100a with the IP address of the information providing apparatus 100a corresponding to the domain name, the domain name indicating the host name of the information providing apparatus 100b, It has a function of associating the IP address of the information providing apparatus 100b corresponding to the domain name.
- the DNS server 120 receives a DNS request packet including the domain name of the information providing apparatus 100 from the terminal device 110, the DNS server 120 refers to the domain name included in the DNS request packet. Then, the DNS server 120 transmits a DNS response packet to reply the terminal device 110 with the IP address of the information providing apparatus 100 corresponding to the domain name.
- the number of information providing apparatuses 100 corresponding to one domain name is not limited to one, and there may be a plurality of information providing apparatuses. In this case, a different IP address is assigned to each of the plurality of information providing apparatuses 100. That is, the DNS server 120 may add a plurality of IP addresses corresponding to one domain name to the DNS response packet and transmit it to the terminal device 110.
- the relay devices 130a to 130c are PLC bridges that bridge data transmitted and received via different types of networks.
- the relay devices 130a to 130c relay content transmitted from the information providing device 100, DNS packets transmitted and received between the terminal device 110 and the DNS server 120, and the like.
- the relay devices 130a to 130c have a QoS processing function. For example, a function for reserving a band (hereinafter referred to as “request band”) necessary for transmitting content in each section of the relay apparatuses 130a to 130c, or a priority is provided for each content, and based on the priority Content transmission function.
- request band a function for reserving a band necessary for transmitting content in each section of the relay apparatuses 130a to 130c, or a priority is provided for each content, and based on the priority Content transmission function.
- the relay apparatus 130 is described as having a function of providing a priority for each content subject to QoS and transmitting the content based on the priority.
- the QoS process for each section of the relay apparatuses 130a to 130c will be described. For this reason, QoS processing such as a section between the relay device 130a and the terminal device 110a is excluded.
- FIG. 2 is a functional block diagram showing an example of the configuration of the relay device 130 according to the present embodiment.
- the relay apparatus 130 includes a communication unit (communication device) 301, a communication unit (communication device) 303, a storage unit 316, and a control unit 323.
- a configuration necessary for relaying communication from the second network 150 to the first network 140 in the relay device 130 is illustrated, and the first network 140 to the second network are illustrated.
- a configuration necessary for relaying communication to 150 is not shown.
- the communication unit 301 transmits / receives data to / from the information providing apparatus 100 and the DNS server 120 via the second network 150.
- the communication unit 301 is an Ethernet (registered trademark) communication unit.
- the communication unit 301 includes a transmission unit (not shown) and a reception unit 302.
- the transmission unit has a function of transmitting data to the information providing apparatus 100 and the DNS server 120.
- the receiving unit 302 has a function of demodulating data received by the communication unit 301.
- the communication unit 303 transmits and receives data to and from the relay apparatuses 130a and 130b via the power line network.
- the communication unit 303 is a PLC communication unit.
- the communication unit 303 includes a QoS processing unit 304, a transmission unit 305, and a reception unit (not shown).
- the transmission unit 305 has a media access control (MAC: Media Access Control) function of the communication unit 303 and a function of modulating data to be transmitted.
- the receiving unit has a function of demodulating data received by the communication unit 303. Details of the QoS processing unit 304 will be described later.
- the storage unit 316 stores a service information table 312 and a QoS management table 315.
- the service information table 312 stores a domain name indicating the type of content, various parameters related to the domain name (hereinafter referred to as service parameters), and the address of the information providing apparatus 100 in association with each other.
- the service parameters include parameters related to the transmission of content such as the name of the service provided from the information providing apparatus 100, the requested bandwidth and priority of the content corresponding to the domain name. Details of the service information table 312 will be described later with reference to FIGS.
- the domain name indicates the host name of the information providing apparatus 100.
- the type of the information providing apparatus 100 can be identified from the domain name.
- the domain name includes a character string such as “stream”, “video”, “movie”, or “music”
- the server of this domain name is an information providing apparatus that distributes music or video content. Can be identified.
- a character string such as “game” is included in the domain name, it is possible to identify that the server of this domain name is a game server.
- the type of content transmitted from the information providing apparatus 100 may be identified by a level domain such as a top level domain, a second level domain, or a third level domain in the domain name. Accordingly, for example, whether the content distributed from the information providing apparatus 100 is music or video can be identified by this level domain.
- the domain name is included in a DNS packet transmitted / received between the terminal device 110 and the DNS server 120. For this reason, the relay device 130 can acquire the domain name by relaying the DNS packet transmitted from the DNS server 120.
- the QoS management table 315 stores various parameters related to QoS processing. Details of the QoS management table 315 will be described later with reference to FIG. Note that when the relay device 130 does not perform QoS processing (that is, the communication unit 303 does not include the QoS processing unit 304), the storage unit 316 does not necessarily need to store the QoS management table 315 (for example, (See FIG. 16B).
- the control unit 323 when the terminal apparatus 110a transmits a content acquisition request to the information providing apparatus 100a, and the relay apparatus 130 receives a response packet indicating that the content acquisition destination has been changed from the information providing apparatus 100a to the information providing apparatus 100b. Is assumed.
- the control unit 323 receives the response packet transmitted from the information providing device 100a to the terminal device 110a as a response to the content acquisition request transmitted from the terminal device 110a to the information providing device 100a. Determine whether or not. Then, the control unit 323 determines whether or not the response packet received by the receiving unit 302 indicates a transfer request. When the response packet indicates a transfer request, the control unit 323 indicates the information providing apparatus 100b after the change included in the response packet.
- the domain name is stored in the service information table 312 in association with the domain name of the information providing apparatus 100a before the change.
- control unit 323 includes a DNS detection unit 310, a DNS analysis unit 311, a QoS necessity determination unit 313, a QoS registration unit 314, a response packet detection unit 320, a transfer request analysis unit 321, and a domain information update. Part 322.
- the configuration of the control unit 323 is merely an example, and a configuration other than the above may be used.
- the DNS detection unit 310 determines the type of data received by the reception unit 302, and transfers the data to the DNS analysis unit 311 if the data is a DNS response packet. Specifically, the DNS detection unit 310 checks the port number of the UDP (User Datagram Protocol) header of the received data and the port number of the TCP (Transmission Control Protocol) header. It can be determined that there is. In addition, since an identifier indicating a DNS request or a DNS response exists in the flag area of the DNS packet, the DNS detection unit 310 can determine whether it is a DNS request packet or a DNS response packet by referring to the identifier. The configuration of the DNS packet will be described later with reference to FIG.
- the DNS analysis unit 311 extracts a DNS inquiry name (domain name) included in the received DNS response packet and a reply IP address corresponding to the DNS inquiry name.
- the DNS analysis unit 311 transfers the extracted domain name and reply IP address to the QoS necessity determination unit 313. If the control unit 323 does not include the QoS necessity determination unit 313, the DNS analysis unit 311 sets the reply IP address to the “information providing apparatus address” in the service information table 312 instead of the QoS necessity determination unit 313.
- the registered IP address may be transferred to the response packet detector 320.
- the QoS necessity determination unit 313 confirms whether or not the domain name transferred from the DNS analysis unit 311 is registered in the service information table 312. If it is not registered, the QoS necessity determination unit 313 determines that the service is a domain name that does not require QoS processing, and does not perform the QoS processing. On the other hand, if registered, the QoS necessity determination unit 313 determines that the service is a domain name that requires QoS processing, and acquires a service parameter corresponding to the domain name from the service information table 312. Further, the QoS necessity determination unit 313 registers the reply IP address transferred from the DNS analysis unit 311 in the “information providing device address” of the service information table 312.
- the QoS necessity determination unit 313 transfers the service parameters such as the transfer rate and priority and the reply IP address transferred from the DNS analysis unit 311 to the QoS registration unit 314. In addition, the QoS necessity determination unit 313 transfers the reply IP address to the response packet detection unit 320 at the same time.
- the QoS registration unit 314 registers the transfer rate (requested bandwidth), priority, and reply IP address transferred from the QoS necessity determination unit 313 in the QoS management table 315.
- the response packet detection unit 320 determines whether the reception unit 302 has received a response packet transmitted from the information providing apparatus 100a to the terminal apparatus 110a as a response to the content acquisition request transmitted from the terminal apparatus 110a to the information providing apparatus 100a. Determine whether. Specifically, the response packet detection unit 320 determines the type of data received by the reception unit 302, and only when the received data is an HTTP packet transmitted from the information providing apparatus 100 to be subjected to QoS processing, Is transferred to the transfer request analysis unit 321 as a response packet.
- the response packet detecting unit 320 has a port number of the TCP header of the received data of 80, and the reply IP address transferred from the QoS necessity determining unit 313 and the source IP address of the IP header of the received data If they match, the received data is transferred to the transfer request analysis unit 321 as a response packet. That is, HTTP packets transmitted from information providing apparatuses other than the reply IP address are not transferred to the transfer request analysis unit 321.
- the configuration of the HTTP packet will be described later with reference to FIG.
- the transfer request analysis unit 321 determines whether the response packet received by the receiving unit 302 is a transfer request from the information providing apparatus 100. As a specific example, the transfer request analysis unit 321 analyzes an HTTP message as a response packet, and when the response (status) code is a code indicating HTTP redirect, the response packet is a transfer request from the information providing apparatus 100. judge. When the response code is a code indicating HTTP redirection, the transfer request analysis unit 321 uses the transfer destination URL (Uniform Resource Locator) of the Location header described in the HTTP message and the source address of the IP header, and the domain information update unit Transfer to 322. Response codes indicating HTTP redirect include “301” and “302”.
- the transfer request analyzing unit 321 is transmitted from the information providing apparatus that distributes the content that is not the QoS target. There is no need to analyze the HTTP packet. As a result, the relay device 130 can reduce the load due to the extra HTTP packet analysis processing, and can avoid a reduction in communication throughput due to an increase in the analysis load.
- the domain information update unit 322 extracts the domain name from the transfer destination URL and registers it in the service information table 312. Specifically, the domain information update unit 322 confirms in which of the registration numbers of the service information table 312 the address of the transferred information providing apparatus 100 exists. Since the domain name corresponding to the confirmed registration number is the transfer destination URL, the domain information update unit 322 associates the domain name with the transfer destination URL, and uses the domain name in the transfer destination URL as a new domain name. It is additionally registered in the service information table 312.
- the QoS processing unit 304 has QoS processing functions such as bandwidth reservation and priority control.
- the QoS processing unit 304 refers to the QoS management table 315 and reserves the bandwidth of each section of the relay apparatuses 130a to 130c according to the requested bandwidth.
- Band reservation means that one specific relay device 130 occupies and uses a time slot obtained by dividing a communication channel (communication frequency) on a time axis.
- An example of bandwidth reservation is TDMA (Time Division Multiple Access).
- HCCA Hybrid Coordination Function Controlled Channel Access
- the QoS processing unit 304 refers to the QoS management table 315 and transmits a packet according to the priority associated with the received data.
- FIG. 17 is a diagram for explaining priority control processing in the QoS processing unit 304.
- the QoS processing unit 304 includes a functional block as shown in FIG. 17, for example.
- data identification unit 701 has a function of determining whether received data is a packet to be preferentially transmitted. Specifically, the data identification unit 701 determines whether or not the received data matches the data identification parameter of the QoS management table 315 and is a packet to be preferentially transmitted.
- the queue 702 is prepared for each priority, and as the priority, for example, no priority (no QoS guarantee) or priorities 1 to 8 are set.
- the priority control unit 703 performs control to extract a packet from the high priority queue 702 and transmit the packet.
- priority control EDCA (Enhanced Distributed Channel Access) is standardized in the IEEE 802.11e standard.
- QoS processing unit 304 has a priority control function will be described.
- FIG. 3 and 4 are diagrams showing in detail the memory structure of the service information table 312 shown in FIG. 3 and 4, the service information table 312 associates the item “registration No.”, the item “DNS inquiry name (domain name)”, the item “service parameter”, and the item “information providing apparatus address”.
- the item “service parameter” includes an item “service name”, an item “transfer rate (bps)”, an item “priority”, and an item “Layer4 Protocol”.
- domain name which is a host name of the information providing apparatus 100 is stored.
- This domain name may be FQDN (Fully Qualified Domain Name) or a part indicating the type of content such as the top level domain of the domain name.
- service name a service name corresponding to the domain name is stored. This service name includes, for example, the provider of the service and the type of the content.
- transfer rate bps
- priority a priority indicating the transmission priority of each domain name is recorded. The larger the priority number, the higher the priority of the domain name.
- Layer4 Protocol for example, a communication protocol such as TCP or UDP is stored. This is used for determination such as performing a QoS process with a bi-directional link for TCP, or performing a QoS process with only a one-way link (downlink or uplink) for UDP.
- the item “information providing apparatus address” stores the address of the information providing apparatus 100 corresponding to the domain name.
- FIG. 3A shows a setting example of the service information table 312 before update.
- the service information table 312 manages two pieces of service information.
- the service information of the first (registration No. 1-1) is “xx.yy.tv” in the item “domain name”, “X company TV program distribution” in the item “service name”, and the item “transfer rate (bps)”. “10M”, “7” in the item “priority”, and “TCP” in the item “Layer4 Protocol”.
- the item “information providing apparatus address” is recorded as undecided since it is in the initial state.
- the first service information is “content held by the information providing apparatus 100 with the host name xx.yy.tv is distributed by the TV program distribution service of company X, and this content is distributed to the terminal apparatus 110. In order to achieve this, a bandwidth of 10M is required on the communication path, and transmission is performed with priority 7. "
- the second (registration No. 2-1) service information includes “abc.xyz.com” in the item “domain name”, “A company video distribution” in the item “service name”, and item “transfer rate (bps)”. “6M”, “4” in the item “priority”, and “UDP” in the item “Layer4 Protocol”.
- the item “information providing apparatus address” is recorded as undecided since it is in the initial state. That is, the second service information is “The content held by the information providing apparatus 100 with the host name abc.xyz.com is distributed by the video distribution service of company A, and this content is distributed to the terminal device 110. Indicates that 6M bandwidth is required on the communication path and is transmitted with a priority of 4 ”.
- FIG. 3B shows a state where the IP address “10.20.30.1” is registered in the item “information providing apparatus address” of the first service information in FIG.
- FIG. 4A and 4B show setting examples of the updated service information table 312.
- FIG. An example of updating the service information table 312 will be described later.
- FIG. 5 is a diagram showing an example of the memory structure of the QoS management table 315 shown in FIG.
- the QoS management table 315 stores various QoS parameters, and stores an item “data identification parameter” and an item “data guarantee parameter” in association with each other.
- the item “data identification parameter” includes an item “source address”, an item “destination address”, and an item “Layer4 Protocol”.
- the item “data guarantee parameter” includes the item “request bandwidth (bps)” and the item “priority”.
- the source address and the destination address may be IP addresses or MAC addresses. In this embodiment, it is described as an IP address.
- the item “source address” is “10.20.30.1”
- the item “destination address” is “192.168.”. .0.8 ”
- “ TCP ” is set in the item“ Layer4 Protocol ”.
- “10M” is set in the item “request bandwidth (bps)”
- “7” is set in the item “priority”. That is, the registration No. 1 indicates that “contents are transmitted from the information providing apparatus 100 having an IP address of 10.20.30.0.1 to the terminal apparatus 110 having an IP address of 192.168.0.8 with a priority of 7 or a communication bandwidth of 10 Mbps. Reserved. " The description about FIG.5 (b) is abbreviate
- FIG. 6 is a diagram for explaining the packet configuration of a DNS packet.
- FIG. 6A shows a DNS packet format.
- 6B and 6C show DNS response packets A and B as examples in which values are set in the Query field and the Answer field of the DNS packet.
- the DNS packet is composed of fields of “Ethernet header”, “IP header”, “UDP (TCP) header”, “DNS message”, and “FCS (Frame Check Sequence)”.
- the “DNS message” includes fields of “DNS inquiry name (domain name)”, “Type (inquiry type)”, and “answer data”.
- DNS inquiry name stores a domain name indicating the host name of the information providing apparatus 100.
- Type (inquiry type) stores the type of IP address to be inquired by DNS. For example, when “1” is stored in the “inquiry type”, it indicates an IPv4 IP address corresponding to the DNS inquiry name. On the other hand, when “28” is stored in the “inquiry type”, it indicates an IPv6 IP address corresponding to the DNS inquiry name.
- “Response data” stores the IP address of the information providing apparatus 100 corresponding to the inquired domain name (hereinafter referred to as “response IP address”).
- the terminal device 110 that has received the DNS response packet sets this reply IP address as the IP address of the connection destination.
- a plurality of reply IP addresses are stored in the DNS response packet. In this case, the terminal device 110 sets one IP address arbitrarily selected from a plurality of reply IP addresses as a connection destination IP address.
- FIG. 7 is a diagram showing a packet configuration of the HTTP packet.
- the HTTP packet is composed of fields of “Ethernet header”, “IP header”, “TCP header”, “HTTP message”, and “FCS”.
- the “HTTP message” stores an acquisition request command such as a GET method, a response (status) code, or content data.
- FIG. 7B shows an example of the HTTP redirect (transfer request) of the HTTP message response.
- the response code is “302” and the transfer request destination URL includes “http://xx.yy.001.tv”.
- FIG. 7C shows an HTTP message response. Referring to FIG. 7C, the response code is “200”, indicating normal success with respect to the request.
- FIG. 8 and 9 are sequence diagrams illustrating the operation of each device in the network according to the present embodiment. First, the operation of each device will be described with reference to FIG. 8 by taking as an example the case where there is a content acquisition request from the terminal device 110a shown in FIG.
- terminal apparatus 110a when content reproduction operation is performed by the user (step S501), terminal apparatus 110a writes domain name “xx.yy.tv” of information providing apparatus 100a in the DNS request packet, and performs DNS. It transmits toward the server 120 (step S502).
- the DNS server 120 When the DNS server 120 receives the DNS request packet via the relay devices 130a and 130c, the DNS server 120 writes the IP address corresponding to the domain name of the information providing device 100a in the DNS response packet and returns it to the relay device 130c (step S503). .
- the DNS response packet at this time is shown as DNS response packet A in FIG.
- the “answer data” of the DNS response packet A is the IP address of the information providing apparatus 100a. “10.20.30.1” is written.
- the relay device 130c determines whether or not QoS processing is necessary for content transmission corresponding to the domain name on the communication path with the relay device 130a (Ste S504).
- the relay device 130c performs the QoS process (step S505). Specifically, the relay device 130 c determines that the QoS process is necessary when the DNS inquiry name “xx.yy.tv” of the DNS response packet A is registered in the service information table 312.
- the relay apparatus 130c acquires the service parameters (transfer rate 10 Mbps, priority 7, TCP) corresponding to the domain name “xx.yy.tv” from the service information table 312.
- the relay device 130 c registers the service parameters (transfer rate 10 Mbps, priority 7, TCP) in the QoS management table 315 via the QoS registration unit 314.
- FIG. 5A shows the set QoS management table 315.
- the source address “10.20.30.1” is the reply IP address of DNS response packet A (the IP address of information providing apparatus 100a).
- the destination address “192.168.0.8” is the destination IP address of the IP header of the DNS response packet A and is the IP address of the terminal device 110a.
- the relay device 130c returns a DNS response packet to the terminal device 110a via the relay device 130a (step S506).
- the terminal device 110a receives the DNS response packet via the relay device 130a, the terminal device 110a refers to the reply IP address included in the DNS response packet. In this case, since the IP address of the information providing apparatus 100a is written in the reply IP address, the terminal apparatus 110a transmits a content acquisition request with the destination as the information providing apparatus 100a (step S507).
- the information providing apparatus 100a When the information providing apparatus 100a receives the content acquisition request via the relay apparatuses 130a and 130c, the information providing apparatus 100a transmits an acquisition response (step S508). Further, the information providing apparatus 100a immediately distributes the content to the terminal apparatus 110a (step S509). The terminal device 110a receives the content from the information providing device 100a and reproduces the content (step S510). During content distribution, when the relay device 130c receives content that matches the data identification parameter of the QoS management table 315, the relay device 130c performs priority control QoS processing based on the data guarantee parameter, and between the relay device 130c and the relay device 130a. To guarantee the communication quality of the section.
- FIG. 9 shows the operation of each apparatus when the information providing apparatus that transmits content is changed from the information providing apparatus 100a to the information providing apparatus 100b in the network according to the present embodiment, that is, when HTTP redirect is used. It is the sequence diagram shown.
- the relay device 130c analyzes the acquisition response (transfer request) from the information providing device 100a and updates the service information table 312.
- the terminal device 110a when a content reproduction operation is performed by the user (step S601), the terminal device 110a writes the domain name “xx.yy.tv” of the information providing device 100a in the DNS request packet. It transmits to the server 120 (step S602).
- the DNS server 120 receives the DNS request packet via the relay devices 130a and 130c, the DNS server 120 writes the IP address of the information providing device 100a corresponding to the domain name in the DNS response packet and returns it to the relay device 130c (step S603).
- the DNS response packet at this time is shown as DNS response packet A in FIG.
- the “answer data” of the DNS response packet A is the IP address of the information providing apparatus 100a. “10.20.30.1” is written.
- step S604 When the relay device 130c receives the DNS response packet A from the DNS server 120, QoS processing is required for content transmission corresponding to the domain name “xx.yy.tv” on the communication path with the relay device 130a. It is determined whether or not (step S604). When the QoS process is necessary, the relay device 130c performs the QoS process (step S605). Specifically, the relay device 130 c determines that the QoS process is necessary when the DNS inquiry name “xx.yy.tv” of the DNS response packet A is registered in the service information table 312.
- the relay device 130c acquires the service parameter (transfer rate 10 Mbps, priority 7, TCP) of the domain name “xx.yy.tv” from the service information table 312.
- the relay device 130 c stores the reply IP address of the DNS response packet A in the service information table 312.
- FIG. 3B shows that the service information table 312 stores the IP address “10.20.30.1” of the information providing apparatus 100a.
- FIG. 5A shows the set QoS management table 315.
- the source address “10.20.30.1” is the reply IP address of DNS response packet A (the IP address of information providing apparatus 100a).
- the destination address “192.168.0.8” is the destination IP address of the IP header of the DNS response packet A and is the IP address of the terminal device 110a.
- the relay device 130c returns a DNS response packet A to the terminal device 110a via the relay device 130a (step S606).
- the terminal device 110a refers to the reply IP address included in the DNS response packet A. In this case, since the IP address of the information providing apparatus 100a is written in the reply IP address, the terminal apparatus 110a transmits a content acquisition request with the destination as the information providing apparatus 100a (step S607).
- the information providing apparatus 100a When receiving the content acquisition request, the information providing apparatus 100a recognizes that the requested content exists in the information providing apparatus 100b, and therefore transmits a transfer request (acquisition response) to the information providing apparatus 100b (Ste S608).
- the transfer request includes the domain name “http://xx.yy.001.tv” of the information providing apparatus 100b.
- the information providing apparatus 100a transmits a transfer request using, for example, an HTTP redirect illustrated in FIG.
- the relay device 130c analyzes whether the transfer request is a transfer request using the transfer request analysis unit 321 (step S609). This is determined by examining the response code of the HTTP message.
- the HTTP message in FIG. 7B has a response code “302”, and is determined to be a transfer request.
- the relay device 130c acquires the transfer destination URL of the Location header included in the HTTP message by the transfer request analysis unit 321. This transfer destination URL is the domain name “xx.yy.001.tv” of the information providing apparatus 100b.
- the relay device 130c registers the domain name of the information providing device 100b in the service information table 312 using the domain information update unit 322, and updates the service information table 312 (step S610). Specifically, the relay device 130c checks in which of the registration numbers of the service information table 312 the IP address “10.20.30.1” of the information providing device 100a is recorded. In the example of the service information table 312 shown in FIG. 3B, the IP address “10.20.30.1” is registered as the registration number. 1-1. For this reason, the domain information update unit 322 can associate the transfer destination of the domain name “xx.yy.tv” of the information providing apparatus 100a with the domain name “xx.yy.001.tv” of the information providing apparatus 100b. .
- the domain information update unit 322 registers the registration number in the service information table 312.
- the domain name of the information providing apparatus 100b is additionally registered.
- the service parameter is registered No. 1-1 to registration No. Copied to 1-2.
- the relay device 130c transmits an acquisition response to the terminal device 110a (step S611).
- the terminal device 110a When the terminal device 110a recognizes the HTTP redirect in the acquisition response, the terminal device 110a transmits a DNS request packet to the DNS server 120 in order to check the IP address of the information providing device 100b (step S612). In the DNS request packet, the domain name “xx.yy.001.tv” of the information providing apparatus 100b is written.
- the DNS server 120 When the DNS server 120 receives the DNS request packet, the DNS server 120 writes the IP address of the information providing apparatus 100b corresponding to the domain name in the DNS response packet and sends it back to the relay apparatus 130c (step S613).
- the DNS response packet at this time is shown as DNS response packet B in FIG.
- the “response data” of the DNS response packet B is provided with information “10.20.30.3”, which is the IP address of the device 100b, is written.
- the relay device 130c When the relay device 130c receives the DNS response packet B from the DNS server 120, the QoS processing is performed for content transmission corresponding to the domain name “xx.yy.001.tv” on the communication path with the relay device 130a. It is determined whether or not is necessary (step S614). When the QoS process is necessary, the relay device 130c performs the QoS process (step S615). Specifically, the relay device 130c determines whether or not the QoS processing is necessary depending on whether or not the DNS inquiry name “xx.yy.001.tv” of the DNS response packet B is registered in the service information table 312. to decide.
- the relay apparatus 130c acquires the service parameter (transfer rate 10 Mbps, priority 7, TCP) of the domain name.
- the relay device 130 c stores the reply IP address of the DNS response packet B in the service information table 312.
- FIG. 4B shows that the address “10.20.30.3” of the information providing apparatus is stored in the service information table 312.
- the relay device 130 c registers the service parameters (transfer rate 10 Mbps, priority 7, TCP) in the QoS management table 315 via the QoS registration unit 314.
- FIG. 5B shows the set QoS management table 315.
- the source address “10.20.30.3” is the reply IP address of the DNS response packet B (the IP address of the information providing apparatus 100b).
- the destination address “192.168.0.8” is the destination IP address of the IP header of the DNS response packet B, and is the IP address of the terminal device 110a.
- the relay device 130c returns a DNS response packet B to the terminal device 110a via the relay device 130a (step S616).
- the terminal device 110a refers to the reply IP address included in the DNS response packet B.
- the terminal apparatus 110a transmits a content acquisition request with the destination as the information providing apparatus 100b (step S617).
- the information providing apparatus 100b When the information providing apparatus 100b receives the content acquisition request, the information providing apparatus 100b transmits an acquisition response (step S618). For example, the information providing apparatus 100b transmits an HTTP packet illustrated in FIG. 7C as an acquisition response.
- the relay apparatus 130c detects an acquisition response from the information providing apparatus 100b via the response packet detection unit 320, the relay apparatus 130c analyzes whether the request is a transfer request (step S619). This is determined by examining the response code of the HTTP message. In the HTTP message of FIG. 7C, the response code is 200, and it is determined that the request is not a transfer request. If it is not a transfer request, the relay apparatus 130c does not update the service information table 312.
- the relay device 130c transmits an acquisition response to the terminal device 110a (step S620).
- the information providing apparatus 100b distributes the content to the terminal apparatus 110a immediately after the acquisition response is transmitted (step S621). In addition, a part of the content may be included in the acquisition response transmitted by the information providing apparatus 100b.
- the terminal device 110a receives the content from the information providing device 100b and reproduces the content (step S622).
- the relay device 130c receives a packet that matches the data identification parameter of the QoS management table 315
- the relay device 130c performs QoS processing for priority control based on the data guarantee parameter, and guarantees communication quality in the section of the relay device 130c and 130a. Is realized.
- FIG. 10 is a flowchart showing details of the operation of the relay device 130c in steps S604, S605, S609, and S610 of FIG.
- the DNS detection unit 310 determines the type of reception data received by the reception unit 302, and determines that the reception data is the DNS response packet A (step S1101).
- the DNS analysis unit 311 analyzes the DNS response packet A (step S1102), and acquires an inquiry name (domain name) and a reply IP address (step S1103).
- the QoS necessity determination unit 313 determines whether or not the acquired domain name exists in the service information table 312 (step S1104). If the acquired domain name does not exist in the service information table 312, the QoS necessity determination unit 313 determines that the content transmission does not require the QoS process. In this case, the relay device 130c transmits a DNS response packet without performing the QoS process (step S1105). On the other hand, when the acquired domain name exists in the service information table 312, the QoS necessity determination unit 313 stores the service parameter and the reply IP address of the service information table 312 in the QoS management table 315 via the QoS registration unit 314. Registration is performed (step S1106). Further, the QoS necessity determination unit 313 records the reply IP address in the “information providing apparatus address” of the corresponding domain name in the service information table 312.
- the relay device 130c transmits a DNS response packet A (step S1107). Thereafter, when the relay apparatus 130c receives an acquisition response from the information providing apparatus 100a that is a reply IP address (step S1108), the relay apparatus 130c analyzes the acquisition response (step S1109, step S609 in FIG. 9). If the acquisition response is not a transfer request (HTTP redirect), the relay device 130c transmits the acquisition response (step S1113).
- the relay device 130c extracts the domain name of the transfer destination information providing device 100b from the transfer destination URL included in the transfer request (step S1111). Thereafter, the relay device 130c updates the service information table 312 by associating the domain name of the information providing device 100a with the domain name of the information providing device 100b (step S1112).
- FIG. 3B shows a service information table before update
- FIG. 4A shows a service information table after update. For association, the “information providing apparatus address” in the service information table 312 is used. Thereafter, the relay device 130c transmits an acquisition response (step S1113, step S611 in FIG. 9).
- the relay apparatus 130c allows the information providing apparatus to communicate with the terminal apparatus even when the information providing apparatus to be connected is changed to an information providing apparatus with a different domain name.
- the transfer request HTTP redirect
- the change of the domain name of the information providing device is detected, and the service information table 312 in which the domain name is associated with the service parameter corresponding to the domain name is updated.
- the relay device can guarantee the communication quality by identifying the content distributed from the information providing device having a different domain name and performing the QoS process.
- the user can view high-quality content without video interruptions or disturbances.
- the relay device 130c is designed to optimize resources such as a CPU (Central Processing Unit) and a memory for the data relay transfer function, if the payload (message) portion of all HTTP packets is analyzed, the CPU There is a risk that the communication throughput (communication rate) may decrease due to an increase in load (CPU usage rate). For this reason, the relay device 130c specifies the IP address of the information providing device that transmits the QoS target content included in the DNS response packet, analyzes the payload portion of the HTTP packet transmitted from the information providing device, and is designated. The HTTP packet transmitted from the server other than the information providing apparatus having the IP address is not analyzed. This eliminates the need for the relay device to analyze the payload (message) portion of all HTTP packets, thereby suppressing an increase in CPU load and avoiding a decrease in communication throughput.
- resources such as a CPU (Central Processing Unit) and a memory for the data relay transfer function
- the relay device 130 determines whether or not the QoS processing is necessary based on the domain name of the DNS response packet.
- the acquisition response transmitted to the device 110a is analyzed, and if it is a transfer request to another information providing device 100b, the transfer destination domain name is additionally registered in the service information table 312.
- the relay apparatus 130 determines whether or not the QoS processing is necessary based on the domain name of the DNS response packet.
- the acquisition response transmitted to the device 110a is analyzed, and if it is a transfer request to another information providing device 100b, the transfer destination domain name is additionally registered in the service information table 312.
- the relay device 130c when an alias domain name is added to the DNS response packet as CNAME (Canonical NAME for an alias), the relay device 130c extracts the alias domain name from the DNS response packet. A mode for updating the service information table 312 will be described. Accordingly, the relay device 130c can prevent the disordered video distribution from being performed without performing the QoS process when the content is distributed from the information providing device of the alias domain name.
- FIG. 11 is a functional block diagram of the relay device 130 in the second embodiment of the present invention.
- the same reference numerals are given to the same configurations as the functional blocks described in FIG. 2, and the description thereof is omitted here.
- service information table 404 stores a domain name indicating the type of content and various parameters related to the domain name (hereinafter referred to as “service parameters”) in association with each other.
- the service parameters include the name of the service provided from the information providing apparatus 100, the requested bandwidth and priority of the content corresponding to the domain name. Details of the service information table 404 will be described later with reference to FIG.
- the service information table 404 differs from the service information table 312 according to the first embodiment in the presence / absence of the item “information providing device address”.
- the “information providing apparatus address” in the service information table 312 is used for associating a domain name to be additionally registered with the current registered domain name.
- the item “information providing apparatus” "Address" was deleted.
- the description of the domain name is the same as in the first embodiment, and is omitted.
- the DNS analysis unit 401 extracts a DNS inquiry name (domain name), Type, and answer data included in the received DNS response packet, and transfers them to the QoS necessity determination unit 402.
- the configuration of the DNS packet will be described later with reference to FIG.
- the type of the DNS response packet is 1 or 28
- the response data is an IP address.
- Type is 5
- the answer data is the alias domain name.
- the QoS necessity determination unit 402 determines that the service requires QoS processing, and sets the domain name of the alias as the answer data and the DNS inquiry name (domain name) as the domain information update unit 403. Forward to.
- the domain information update unit 403 registers the transferred alias domain name in the service information table 404. Specifically, the domain information update unit 403 confirms in which of the registration numbers of the service information table 404 the DNS inquiry name exists. If the domain name alias of the confirmed registration number is the domain name of the alias transferred from the QoS necessity determination unit 402, the domain information update unit 403 associates these with the alias domain name in the service information table. Additional registration is made in 404.
- FIG. 12 is a diagram showing in detail the memory structure of the service information table 404 shown in FIG.
- the service information table 404 stores an item “DNS inquiry name (domain name)” and an item “service parameter” in association with each other.
- the item “service parameter” includes an item “service name”, an item “transfer rate (bps)”, an item “priority”, and an item “Layer4 Protocol”.
- a domain name which is a host name of the information providing apparatus 100 is stored. This domain name may be FQDN (Fully Qualified Domain Name) or a part that can indicate the type of content such as the top level domain of the domain name.
- the service name corresponding to the domain name is stored in the item “service name”.
- the service name includes, for example, a service provider and content type.
- the item “transfer rate (bps)” stores a transfer rate indicating the requested bandwidth of the content corresponding to the domain name.
- bps transfer rate
- a priority indicating the transmission priority of each domain name is recorded. It shows that the priority of the said domain name is so high that the numerical value of this priority is large.
- Layer4 Protocol for example, a communication protocol such as TCP or UDP is stored. If this item is TCP, QoS processing is performed on a bi-directional link, and if UDP is used, the QoS processing is used only on a unidirectional link (downlink or uplink).
- the service information table 404 manages two pieces of service information.
- the service information of the first (registration No. 1-1) is “xx.yy.tv” in the item “domain name”, “X company TV program distribution” in the item “service name”, and the item “transfer rate (bps)”. “10M”, “7” in the item “priority”, and “TCP” in the item “Layer4 Protocol”.
- the first service information is “content held by the information providing apparatus 100 with the host name xx.yy.tv is distributed by the TV program distribution service of company X, and this content is distributed to the terminal apparatus 110. In order to achieve this, a bandwidth of 10M is required on the communication path, and transmission is performed with priority 7.
- the second (registration No. 2-1) service information includes “abc.xyz.com” in the item “domain name”, “A company video distribution” in the item “service name”, and item “transfer rate (bps)”. “6M”, “4” in the item “priority”, and “UDP” in the item “Layer4 Protocol”. That is, the second service information is “The content held by the information providing apparatus 100 with the host name abc.xyz.com is distributed by the video distribution service of company A, and this content is distributed to the terminal device 110. Indicates that 6M bandwidth is required on the communication path and is transmitted with a priority of 4 ”.
- FIG. 13 is a diagram for explaining a packet configuration of a DNS packet.
- FIG. 13A shows a DNS packet format.
- FIGS. 13B and 13C show DNS response packets C and D as examples in which values are set in the Query field and the Answer field of the DNS packet.
- the DNS packet is composed of fields of “Ethernet header”, “IP header”, “UDP (TCP) header”, “DNS message”, and “FCS”.
- the “DNS message” includes fields of “DNS inquiry name (domain name)”, “Type (inquiry type)”, and “answer data”.
- FIG. 13B shows an example of the DNS response packet C.
- the “DNS inquiry name (domain name)” stores a domain name “xx.yy.tv” indicating the host name of the information providing apparatus 100a.
- Type inquiry type
- a type inquired by DNS is stored.
- the “answer data” stores an alias domain name “xx.yy.001.tv” of the information providing apparatus 100a.
- the DNS request packet stored in the “name” is transmitted to the DNS server 120.
- the terminal device 110a receives a DNS response packet D as shown in FIG. 13C from the DNS server 120.
- the IP address “10.20.30.1” corresponding to the alias domain name “xx.yy.001.tv” of the information providing apparatus 100a is written.
- the terminal device 110a sets the IP address of the information providing device 100a included in the reply IP address as the IP address of the connection destination.
- FIG. 14 is a sequence diagram showing the operation of each device in the network according to the second embodiment of the present invention.
- the relay device 130c receives and analyzes the DNS response packet C (FIG. 13B) of CNAME from the DNS server 120, and updates the service information table 404.
- terminal apparatus 110a when a content reproduction operation is performed by the user (step S801), terminal apparatus 110a writes the domain name “xx.yy.tv” of information providing apparatus 100a in the DNS request packet to generate a DNS server. It transmits to 120 (step S802). Upon receiving the DNS request packet, the DNS server 120 writes the alias domain name of the information providing apparatus 100a in the DNS response packet and returns it to the relay apparatus 130c (step S803).
- the DNS response packet at this time is shown as DNS response packet C in FIG.
- the relay device 130c determines whether QoS processing is necessary for content transmission corresponding to the domain name on the communication path with the relay device 130a (Ste S804). Specifically, the relay device 130c determines whether or not QoS processing is necessary based on whether or not the DNS inquiry name “xx.yy.tv” of the DNS response packet C is registered in the service information table 404. . In the service information table 404 in FIG. 12A, “xx.yy.tv” is registered as the registration number. 1-1, it can be determined that QoS processing is necessary.
- Type is 1 or 28
- the relay apparatus 130c acquires the service parameter of the corresponding domain name from the service information table 404, and, via the QoS registration unit 314, as in the first embodiment.
- the acquired service parameter is registered in the QoS management table 315.
- the relay device 130 c updates the service information table 404 by registering the domain name “xx.yy.001.tv” of the alias of the information providing device 100 a in the service information table 404 using the domain information update unit 403. (Step S806).
- the relay device 130 c confirms in which of the registration numbers of the service information table 404 the DNS inquiry name “xx.yy.tv” of the DNS response packet C is recorded.
- “xx.yy.tv” is registered as the registration number. 1-1
- the domain information update unit 403 can associate that the alias of the domain name “xx.yy.tv” of the information providing apparatus 100a is “xx.yy.001.tv”.
- the domain information update unit 403 registers the registration number.
- the domain name of the information providing apparatus 100a is additionally registered.
- the service parameter is registered No. 1-1 to registration No. Copied to 1-2.
- the relay device 130c returns a DNS response packet C to the terminal device 110a via the relay device 130a (step S807).
- the terminal device 110a When the terminal device 110a receives the DNS response packet C, the terminal device 110a refers to the Type and the response data included in the DNS response packet C. In this case, an alias domain name “xx.yy.001.tv” of the information providing apparatus 100a is written in the response data. For this reason, in order to check the IP address corresponding to the alias domain name, the terminal device 110a transmits a DNS request packet with the alias domain name as the DNS query name to the DNS server 120 (step S808).
- the DNS server 120 When the DNS server 120 receives the DNS request packet, the DNS server 120 writes the IP address of the information providing apparatus 100a corresponding to the alias domain name in the DNS response packet and returns it to the relay apparatus 130c (step S809).
- the DNS response packet at this time is shown as a DNS response packet D in FIG.
- the “answer data” of the DNS response packet D includes “10.20.30.1”, which is the IP address of the information providing apparatus 100a, is written.
- the relay device 130c determines whether or not QoS processing is necessary for content transmission corresponding to the domain name on the communication path with the relay device 130a (Ste S810).
- the relay device 130c performs the QoS process (step S811). Specifically, the relay device 130c determines whether or not the QoS processing is necessary depending on whether or not the DNS inquiry name “xx.yy.001.tv” of the DNS response packet D is registered in the service information table 404. to decide.
- the relay device 130c When the relay device 130c performs the process of step S806 in FIG. 14, for example, the registration information “No. In 1-2, the domain name “xx.yy.001.tv” is registered. Therefore, the relay device 130c acquires the service parameters (transfer rate 10 Mbps, priority 7, TCP) of the corresponding domain name from the service information table 404. Next, the relay device 130 c registers the service parameters (transfer rate 10 Mbps, priority 7, TCP) in the QoS management table 315 via the QoS registration unit 314. The registration method in the QoS management table 315 is the same as that in the first embodiment, and a description thereof will be omitted. Thereafter, the relay device 130c returns a DNS response packet D to the terminal device 110a via the relay device 130a (step S812).
- the terminal device 110a When the terminal device 110a receives the DNS response packet D via the relay device 130a, the terminal device 110a refers to the reply IP address included in the DNS response packet D. In this case, since the IP address of the information providing apparatus 100a is written in the reply IP address, the terminal apparatus 110a transmits a content acquisition request with the destination as the information providing apparatus 100a (step S813).
- the information providing apparatus 100a transmits an acquisition response to the content acquisition request to the terminal apparatus 110a (step S814). For example, an HTTP packet shown in FIG. 7C is transmitted as an acquisition response.
- the information providing apparatus 100a distributes the content to the terminal apparatus 110a immediately after the acquisition response is transmitted (step S815). In addition, a part of the content may be included in the acquisition response transmitted by the information providing apparatus 100a.
- the terminal device 110a receives the content from the information providing device 100a and reproduces the content (step S816).
- the relay device 130c when the relay device 130c receives content that matches the data identification parameter of the QoS management table 315, the relay device 130c performs priority control QoS processing based on the data guarantee parameter, and guarantees the communication quality of the relay device 130c and 130a sections. Is realized.
- FIG. 15 is a flowchart showing the operation of the relay device 130c in steps S804, S805, and S806 of FIG.
- DNS detection section 310 determines the type of received data received by receiving section 302, and determines that the received data is DNS response packet C (step S1201).
- the DNS analysis unit 311 analyzes the DNS response packet C (step S1202), and acquires an inquiry name (domain name), Type, and answer data (step S1203).
- the QoS necessity determination unit 402 obtains the IP address of the information providing apparatus 100a that is answer data (step S1206), and stores the service information table 404 for the corresponding domain name via the QoS registration unit 314. The service parameter and the reply IP address are registered in the QoS management table 315 (step S1207). Thereafter, the relay device 130c transmits a DNS response packet (step S1210).
- the QoS necessity determination unit 402 acquires the alias domain name of the information providing apparatus 100a, which is answer data (step S1208). Thereafter, the QoS necessity determination unit 402 updates the service information table 404 by associating the domain name “xx.yy.tv” of the information providing apparatus 100a with the alias domain name “xx.yy.001.tv”. (Step S1209).
- FIG. 12A shows the service information table before update
- FIG. 12B shows the service information table after update.
- the relay device 130c transmits a DNS response packet C (step S1210).
- the relay device 130c can perform the DNS server even when the DNS response packet does not include the IP address of the information providing device and includes an alias domain name as CNAME.
- the domain name of the alias of the information providing device that is CNAME is detected, and the domain name is associated with the service parameter corresponding to the domain name Update the service information table.
- the relay device 130c can guarantee the communication quality by identifying the content distributed from the information providing device with the alias domain name and performing the QoS process. As a result, the user can view high-quality video content without video interruptions or disturbances.
- the relay apparatus 130 has been described as including one control unit 323.
- the first control unit 324 The second control unit 325 may be provided separately.
- the first control unit 324 has a function of updating the service information table 312 based on the response packet received by the receiving unit 302.
- the second control unit 325 has a function of determining whether or not QoS processing is necessary.
- the first control unit 324 includes a response packet detection unit 320, a transfer request analysis unit 321, and a domain information update unit 322.
- the second control unit 325 includes a DNS detection unit 310, a DNS analysis unit 311, a QoS necessity determination unit 313, and a QoS registration unit 314. Since the operation of each functional block is as described above, description thereof is omitted.
- the relay apparatus 130 may be configured to include only the first control unit 324 as illustrated in FIG. 16B. This is because the relay apparatus 130 can update the service information table 312 even if the relay apparatus 130 includes only the first control unit 324.
- the relay apparatus and the table updating method according to each embodiment of the present invention are applicable not only to power line communication but also to communication using a radio, a telephone line, a coaxial cable, an optical cable, and the like. Further, the present invention is applicable to communications such as USB (Universal Serial Bus), HDMI (High-Definition Multimedia Interface) (registered trademark), IEEE 1394, and the like. Accordingly, the relay apparatus and the table update method of the present invention can be used with various transmission media.
- the relay device and the table update method according to each embodiment of the present invention can be applied not only to a bridge such as a relay device but also to a router, a gateway, a layer 2 switch, a layer 3 switch, a layer 7 switch, and a brouter. It is.
- the bridge and the layer 2 switch are data link layer relay devices of an OSI (Open System Interconnection) reference model.
- the router and the layer 3 switch are relay devices in the network layer of the OSI reference model.
- a gateway is a relay device with four or more layers of the OSI reference model.
- the layer 7 switch is a relay device in the application layer of the OSI reference model.
- Bruter is a relay device that combines a router function and a bridge function. Accordingly, the relay device and the table update method of the present invention can be used not only for the bridge but also for various relay devices.
- the DNS response packet transmitted from the DNS server is analyzed by the relay device 130c.
- the present invention is not limited to this, and the DNS cache function is provided. This can also be realized by analyzing the DNS response packet transmitted from the built-in router by the relay device 130c.
- the router is located and connected between the DNS server and the relay device 130c. Accordingly, the relay apparatus and the table update method of the present invention can be used not only in the DNS server but also in a network system using a relay apparatus such as a router having a DNS cache function.
- the relay apparatus and the table update method according to each embodiment of the present invention operate only with the relay apparatus 130c connected to the second network 150
- the relay apparatuses 130a and 130b are not limited to this. It is also possible to operate in the same way. Accordingly, it is possible to realize quality assurance control in uplink communication from the relay device 130a to the relay device 130c by two-way communication such as Internet telephone. Further, whether or not the QoS processing of the uplink communication is necessary can be easily added to the service information table as one item of the service parameter.
- the relay apparatuses 130a and 130b can determine whether or not the QoS processing of the uplink communication is necessary with reference to the service information table when the DNS response packet is received.
- each functional block included in the relay device 130 disclosed in each embodiment of the present invention may be realized by an LSI that is an integrated circuit.
- the control unit 323, the first control unit 324, and the second control unit 325 may be configured by an integrated circuit. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them.
- This LSI is sometimes called an IC, a system LSI, a super LSI, or an ultra LSI depending on the degree of integration.
- the method of circuit integration is not limited to LSI, and a dedicated circuit or a general-purpose processor may be used.
- a dedicated circuit or a general-purpose processor may be used.
- an FPGA Field Programmable Gate Array
- a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used.
- a configuration in which a processor executes a control program stored in a ROM in hardware resources including a processor and a memory may be used.
- the present invention can be applied to various communication devices that require communication bandwidth control, such as PLC bridges, routers, gateways, layer 2 switches, layer 3 switches, layer 7 switches, brouters, and the like.
Abstract
Description
図1は、本発明の第1の実施形態におけるネットワーク構成の一例を示す図である。図1において、本実施形態のネットワークは、各種の情報提供装置(コンテンツサーバ)100a~100b、各種の端末装置110a~110b、及びDNSサーバ120を含んでいる。情報提供装置100a~100bと端末装置110a~110bとは、中継装置130a~130cを介して接続されている。具体的には、端末装置110a~110bは、中継装置130a~130bにそれぞれEthernet(登録商標)ケーブルで接続されている。そして、中継装置130a~130cの各間は、第1のネットワーク(例えば、電力線ネットワーク)140を介して接続されている。また、情報提供装置100a~100b及びDNSサーバ120は、第2のネットワーク(例えば、インターネット)150を介して、中継装置130cに接続されている。
第1の実施形態では、中継装置130は、DNS応答パケットのドメイン名に基づいてQoS処理の要否判定を行い、QoS処理の必要がある場合、QoS処理を行うと共に、情報提供装置100aから端末装置110aに送信される取得応答を解析して、別の情報提供装置100bへの転送要求であると、転送先ドメイン名をサービス情報テーブル312に追加登録していた。その結果、異なるドメイン名の情報提供装置100bからコンテンツが配信された場合に、中継装置130においてQoS処理できずに乱れた映像配信が行われることを防止できた。
第3の実施形態では、第1の実施形態及び第2の実施形態で説明した中継装置130の変形例について説明する。第1の実施形態及び第2の実施形態では、中継装置130が、1つの制御部323を備えるものとして説明したが、図16Aに示すように、機能に応じて、第1の制御部324と、第2の制御部325とを分離して備えてもよいものとする。第1の制御部324は、受信部302が受信した応答パケットに基づいて、サービス情報テーブル312を更新する機能を有する。第2の制御部325は、QoS処理の要否を判定する機能を有する。この場合、第1の制御部324は、応答パケット検出部320と、転送要求解析部321と、ドメイン情報更新部322とを備える。第2の制御部325は、DNS検出部310と、DNS解析部311と、QoS要否判定部313と、QoS登録部314とを備える。各機能ブロックの動作については、上述したとおりであるので、説明を省略する。
(1)本発明の各実施形態に係る中継装置及びテーブル更新方法は、電力線通信だけに限らず、無線、電話線、同軸ケーブル、光ケーブルなどを用いた通信にも適用可能である。また、USB(Universal Serial Bus)、HDMI(High-Definition Multimedia Interface)(登録商標)、IEEE1394などの通信にも適用可能である。これらにより、本発明の中継装置及びテーブル更新方法は、各種伝送メディアで利用可能となる。
110,110a,110b 端末装置
120 DNSサーバ
130,130a,130b,130c 中継装置
301 通信部
302 受信部
303 通信部
304 QoS処理
305 送信部
310 DNS検出部
311 DNS解析部
312 サービス情報テーブル
313 QoS要否判定部
314 QoS登録部
315 QoS管理テーブル
316 記憶部
320 応答パケット検出部
321 転送要求解析部
322 ドメイン情報更新部
323 制御部
401 DNS解析部
402 QoS要否判定部
403 ドメイン情報更新部
404 サービス情報テーブル
601 端末装置
602 中継装置
603 中継装置
604 サーバ
701 データ識別部
702 キュー
703 優先制御部
Claims (17)
- 第1のネットワークと第2のネットワークとを相互接続してパケットの送受信を中継する中継装置であって、
第1のドメイン名を有する第1の情報提供装置に対して、コンテンツの取得を要求する端末装置と、前記第1のネットワークを介して通信する第1の通信部と、
前記第1の情報提供装置と、前記第2のネットワークを介して通信する第2の通信部と、
前記第1のドメイン名と、前記コンテンツの送信に関するパラメータとを対応付けて、サービス情報テーブルとして記憶する記憶部と、
前記第2の通信部が、前記端末装置から前記第1の情報提供装置に送信されたコンテンツの取得要求に対する応答として、前記第1の情報提供装置から前記端末装置に送信された応答パケットを受信すると、前記応答パケットが転送要求を示すか否かを判定し、前記応答パケットが前記転送要求を示すと判定した場合、前記応答パケットに含まれる第2の情報提供装置を示す第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶する制御部とを備える、中継装置。 - 前記制御部は、
前記第2の通信部が受信した前記応答パケットから、前記第1の情報提供装置のIPアドレスが送信元として記載された応答パケットを検出し、当該検出した応答パケットを前記転送要求解析部に出力する応答パケット検出部と、
前記応答パケット検出部が検出した前記応答パケットを解析し、前記応答パケットが転送要求を示すか否かを判定する転送要求解析部と、
前記応答パケットが前記転送要求を示すと判定した場合、前記応答パケットに含まれる前記第2の情報提供装置を示す前記第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶するドメイン情報更新部とを備える、請求項1に記載の中継装置。 - 前記転送要求解析部は、前記応答パケットとしてのHTTPメッセージを解析し、前記応答パケットがHTTPリダイレクトを示す場合、前記応答パケットが転送要求を示すと判定することを特徴とする、請求項2に記載の中継装置。
- 前記中継装置は、QoS処理の要否を判定する第2の制御部をさらに備え、
前記第2の通信部は、前記第2のネットワークを介して、DNSサーバと通信し、
前記第2の制御部は、
前記端末装置から前記DNSサーバに送信されたDNS要求パケットに対する応答であるDNS応答パケットを検出するDNS検出部と、
前記DNS検出部が検出した前記DNS応答パケットから、所定のドメイン名と前記所定のドメイン名に対応するIPアドレスとを抽出するDNS解析部と、
前記DNS解析部が抽出した前記所定のドメイン名が、前記サービス情報テーブルに登録されているか否かを判定し、登録されていると判定した場合に、前記所定のドメイン名がQoS処理が必要なドメイン名であると判定するQoS要否判定部とを備えることを特徴とする、請求項2に記載の中継装置。 - 前記QoS要否判定部は、前記DNS解析部が抽出した前記所定のドメイン名が、前記サービス情報テーブルに登録されていると判定した場合に、前記DNS解析部が抽出した前記IPアドレスを前記応答パケット検出部に出力することを特徴とする、請求項4に記載の中継装置。
- 前記第1の通信部は、前記QoS要否判定部が前記DNS応答パケットに含まれる前記所定のドメイン名が前記第1のドメイン名と一致すると判定した場合に、前記サービス情報テーブルを参照し、前記第1のドメイン名に対応付けられた前記QoS処理に関するパラメータを、前記第1の情報提供装置から前記端末装置に対して送信される前記コンテンツの中継パケットに設定するQoS処理部をさらに備えることを特徴とする、請求項4に記載の中継装置。
- 前記第1の通信部は、前記QoS要否判定部が、前記DNS応答パケットに含まれる前記所定のドメイン名が前記第2のドメイン名と一致すると判定した場合に、前記サービス情報テーブルを参照し、前記第2のドメイン名に関連付けられた、前記第1のドメイン名に対応付けられた前記QoS処理に関するパラメータを、前記第2の情報提供装置から前記端末装置に対して送信される前記コンテンツの中継パケットに設定するQoS処理部をさらに備えることを特徴とする、請求項4に記載の中継装置。
- 前記記憶部は、QoS処理に関するパラメータを記憶するQoS管理テーブルをさらに記憶し、
前記QoS要否判定部は、前記DNS応答パケットに含まれる前記所定のドメイン名が、前記サービス情報テーブルに登録されていると判定した場合に、前記サービス情報テーブルから、前記所定のドメイン名に対応するパラメータを取得し、
前記第2の制御部は、前記QoS要否判定部が取得した前記パラメータを前記QoS管理テーブルに記憶するQoS登録部をさらに備え、
前記第1の通信部は、前記QoS管理テーブルを参照して、前記所定のドメイン名に対応する情報提供装置から前記端末装置に対して送信される前記コンテンツの中継パケットに対応付けられた前記QoS処理に関するパラメータを、前記中継パケットに設定するQoS処理部とをさらに備えることを特徴とする、請求項4に記載の中継装置。 - 前記制御部は、前記応答パケットが前記転送要求でないと判定された場合、前記応答パケットに含まれる情報を、前記サービス情報テーブルに記憶しないことを特徴とする、請求項1に記載の中継装置。
- 前記QoS要否判定部は、前記DNS応答パケットに含まれる前記所定のドメイン名が前記第1のドメイン名と一致しないと判定した場合、前記DNS応答パケットに含まれるIPアドレスを前記応答パケット検出部に出力しないことを特徴とする、請求項5に記載の中継装置。
- 前記転送要求は、HTTPリダイレクトであることを特徴とする、請求項1に記載の中継装置。
- 第1のネットワークと第2のネットワークとを相互接続してパケットの送受信を中継する中継装置であって、
第1のドメイン名を有する第1の情報提供装置に対して、コンテンツの送信を要求する端末装置と、前記第1のネットワークを介して通信する第1の通信部と、
前記第2のネットワークを介して、DNSサーバと通信する第2の通信部と、
前記第1のドメイン名と、前記コンテンツの送信に関するパラメータとを対応付けて、サービス情報テーブルとして記憶する記憶部と、
前記第2の通信部が、前記端末装置から前記DNSサーバに送信された所定のドメイン名に対応するIPアドレスを要求するDNS要求パケットに対する応答であり、前記所定のドメイン名と前記所定のドメイン名の別名を表す第2のドメイン名とを含むDNS応答パケットを受信すると、前記DNS応答パケットに含まれる前記所定のドメイン名が前記第1のドメイン名と一致するか否かを判定し、一致すると判定された場合に、前記DNS応答パケットに含まれる第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶する制御部とを備える、中継装置。 - 前記DNS応答パケットにおいて前記所定のドメイン名の別名を表す第2のドメイン名を含むDNS応答パケットの資源レコードタイプは、CNAMEであることを特徴とする、請求項12に記載の中継装置。
- 第1のネットワークと第2のネットワークとを相互接続してパケットの送受信を行う中継装置が実施する方法であって、
前記中継装置の記憶部は、第1のドメイン名と、コンテンツの送信に関するパラメータとを対応付けて、サービス情報テーブルとして記憶しており、
前記中継装置の第1の通信部を用いて、前記第1のドメイン名を有する第1の情報提供装置に対してコンテンツの送信を要求する端末装置と、前記第1のネットワークを介して通信するステップと、
前記中継装置の第2の通信部を用いて、前記第1の情報提供装置と、前記第2のネットワークを介して通信するステップと、
前記第2の通信部が、前記端末装置から前記第1の情報提供装置に送信されたコンテンツの取得要求に対する応答として、前記第1の情報提供装置から前記端末装置に送信された応答パケットを受信すると、前記応答パケットが転送要求を示すか否かを判定し、前記応答パケットが前記転送要求を示すと判定した場合、前記応答パケットに含まれる第2の情報提供装置を示す第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶するステップとを備える、方法。 - 第1のネットワークと第2のネットワークとを相互接続してパケットの送受信を行う中継装置が実施する方法であって、
前記中継装置の記憶部は、第1のドメイン名と、コンテンツの送信に関するパラメータとを対応付けて、サービス情報テーブルとして記憶しており、
前記中継装置の第1の通信部を用いて、前記第1のドメイン名を有する第1の情報提供装置に対してコンテンツの送信を要求する端末装置と、前記第1のネットワークを介して通信するステップと、
前記中継装置の第2の通信部を用いて、前記第1の情報提供装置のIPアドレスを管理するDNSサーバと、前記第2のネットワークを介して通信するステップと、
前記第2の通信部が、前記端末装置から前記DNSサーバに送信された所定のドメイン名に対応する前記第1の情報提供装置のIPアドレスを要求するDNS要求パケットに対する応答であり、前記所定のドメイン名と前記所定のドメイン名の別名を表す第2のドメイン名とを含むDNS応答パケットを受信すると、前記DNS応答パケットに含まれる前記所定のドメイン名が前記第1のドメイン名と一致するか否かを判定し、一致すると判定された場合に前記DNS応答パケットに含まれる第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶するステップとを備える、方法。 - 第1のネットワークと第2のネットワークとを相互接続してパケットの送受信を中継する中継装置が備える集積回路であって、
前記中継装置は、
第1のドメイン名を有する第1の情報提供装置に対して、コンテンツの取得を要求する端末装置と、前記第1のネットワークを介して通信する第1の通信部と、
前記第1の情報提供装置と、前記第2のネットワークを介して通信する第2の通信部と、
前記第1のドメイン名と、前記コンテンツの送信に関するパラメータとを対応付けて、サービス情報テーブルとして記憶する記憶部とを備え、
前記集積回路は、
前記第2の通信部が、前記端末装置から前記第1の情報提供装置に送信されたコンテンツの取得要求に対する応答として、前記第1の情報提供装置から前記端末装置に送信された応答パケットを受信すると、前記応答パケットが転送要求を示すか否かを判定し、前記応答パケットが前記転送要求を示すと判定した場合、前記応答パケットに含まれる第2の情報提供装置を示す第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶する制御部とを備える、集積回路。 - 第1のネットワークと第2のネットワークとを相互接続してパケットの送受信を中継する中継装置が備える集積回路であって、
前記中継装置は、
第1のドメイン名を有する第1の情報提供装置に対して、コンテンツの送信を要求する端末装置と、前記第1のネットワークを介して通信する第1の通信部と、
前記第2のネットワークを介して、DNSサーバと通信する第2の通信部と、
前記第1のドメイン名と、前記コンテンツの送信に関するパラメータとを対応付けて、サービス情報テーブルとして記憶する記憶部とを備え、
前記集積回路は、
前記第2の通信部が、前記端末装置から前記DNSサーバに送信された所定のドメイン名に対応するIPアドレスを要求するDNS要求パケットに対する応答であり、前記所定のドメイン名と前記所定のドメイン名の別名を表す第2のドメイン名とを含むDNS応答パケットを受信すると、前記DNS応答パケットに含まれる前記所定のドメイン名が前記第1のドメイン名と一致するか否かを判定し、一致すると判定された場合に、前記DNS応答パケットに含まれる第2のドメイン名を前記第1のドメイン名と関連付けて、前記サービス情報テーブルに記憶する制御部とを備える、集積回路。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10791783A EP2448183A1 (en) | 2009-06-26 | 2010-05-20 | Relay device and method thereof |
CN2010800024538A CN102138305A (zh) | 2009-06-26 | 2010-05-20 | 中继装置及其方法 |
US13/060,165 US20120087255A1 (en) | 2009-06-26 | 2010-05-20 | Relay apparatus and method therefor |
JP2011519504A JP5329663B2 (ja) | 2009-06-26 | 2010-05-20 | 中継装置及びその方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2009152696 | 2009-06-26 | ||
JP2009-152696 | 2009-06-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010150457A1 true WO2010150457A1 (ja) | 2010-12-29 |
Family
ID=43386247
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/003402 WO2010150457A1 (ja) | 2009-06-26 | 2010-05-20 | 中継装置及びその方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20120087255A1 (ja) |
EP (1) | EP2448183A1 (ja) |
JP (1) | JP5329663B2 (ja) |
CN (1) | CN102138305A (ja) |
WO (1) | WO2010150457A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014230139A (ja) * | 2013-05-23 | 2014-12-08 | Kddi株式会社 | サービス推定装置及び方法 |
RU2621180C2 (ru) * | 2012-01-27 | 2017-05-31 | Квэлкомм Инкорпорейтед | Системы и способы для основанного на приоритете управления сеансами и мобильностью двухприоритетных устройств мтс |
WO2017098859A1 (ja) * | 2015-12-08 | 2017-06-15 | 株式会社日立国際電気 | 通信装置及び通信方法 |
JP2019169862A (ja) * | 2018-03-23 | 2019-10-03 | 三菱電機インフォメーションネットワーク株式会社 | 仮想ルータ及び中継プログラム |
JP2022097129A (ja) * | 2020-12-18 | 2022-06-30 | Necプラットフォームズ株式会社 | 通信制御装置、通信制御プログラム及び通信制御方法 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5195762B2 (ja) * | 2007-12-03 | 2013-05-15 | 富士通株式会社 | パケット通信装置及びパケット通信方法 |
WO2010105351A1 (en) * | 2009-03-16 | 2010-09-23 | Koslar Technologies, Llc | Apparatus, systems and methods for mass transfer of gases into liquids |
EP2408548A1 (en) | 2009-03-16 | 2012-01-25 | Gabae Technologies, Llc | Apparatus, systems and methods for producing particles using rotating capillaries |
CN103999071B (zh) * | 2011-11-02 | 2018-04-17 | 阿卡麦科技公司 | 在边缘网络服务器中的多域配置处理 |
US9730102B2 (en) * | 2012-02-17 | 2017-08-08 | Intel Corporation | Methods and arrangements for packet flows in wireless networks |
EP2632071A1 (en) * | 2012-02-21 | 2013-08-28 | Thomson Licensing | Method for assessing quality of a radio transmission channel, and residential gateway using the method |
US8862702B2 (en) * | 2012-07-18 | 2014-10-14 | Accedian Networks Inc. | Systems and methods of installing and operating devices without explicit network addresses |
KR101946173B1 (ko) | 2014-08-19 | 2019-02-08 | 닛본 덴끼 가부시끼가이샤 | 통신 장치, 통신 시스템 및 통신 방법 |
JP6347431B2 (ja) * | 2015-02-17 | 2018-06-27 | 日本電信電話株式会社 | 名前特定装置、名前特定方法、及びプログラム |
US20180139229A1 (en) * | 2016-11-11 | 2018-05-17 | Verisign, Inc. | Profiling domain name system (dns) traffic |
TWI758680B (zh) * | 2019-01-31 | 2022-03-21 | 日商日本電氣股份有限公司 | 資料中繼裝置、方法、發送系統及程式 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10145424A (ja) | 1996-11-15 | 1998-05-29 | Chokosoku Network Computer Gijutsu Kenkyusho:Kk | 情報通信方法 |
WO2009072247A1 (ja) * | 2007-12-07 | 2009-06-11 | Panasonic Corporation | 通信装置 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6608830B1 (en) * | 1999-01-12 | 2003-08-19 | Yamaha Corporation | Router |
JP3745616B2 (ja) * | 2000-11-24 | 2006-02-15 | 株式会社エヌ・ティ・ティ・ドコモ | 中継装置 |
US8725843B2 (en) * | 2001-11-28 | 2014-05-13 | Thomson Licensing | Method and apparatus for adaptively configuring a router |
US7574508B1 (en) * | 2002-08-07 | 2009-08-11 | Foundry Networks, Inc. | Canonical name (CNAME) handling for global server load balancing |
JP4165196B2 (ja) * | 2002-11-26 | 2008-10-15 | 株式会社日立製作所 | パケット中継装置 |
EP1980949A4 (en) * | 2006-01-31 | 2010-04-14 | Fujitsu Ltd | METHOD AND DEVICE FOR CONTENT DISTRIBUTION IN CONNECTION WITH A TELECONFERENCE |
US8355413B2 (en) * | 2006-02-17 | 2013-01-15 | Cellco Partnership | Policy based procedure to modify or change granted QoS in real time for CDMA wireless networks |
-
2010
- 2010-05-20 US US13/060,165 patent/US20120087255A1/en not_active Abandoned
- 2010-05-20 JP JP2011519504A patent/JP5329663B2/ja not_active Expired - Fee Related
- 2010-05-20 EP EP10791783A patent/EP2448183A1/en not_active Withdrawn
- 2010-05-20 WO PCT/JP2010/003402 patent/WO2010150457A1/ja active Application Filing
- 2010-05-20 CN CN2010800024538A patent/CN102138305A/zh active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10145424A (ja) | 1996-11-15 | 1998-05-29 | Chokosoku Network Computer Gijutsu Kenkyusho:Kk | 情報通信方法 |
WO2009072247A1 (ja) * | 2007-12-07 | 2009-06-11 | Panasonic Corporation | 通信装置 |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2621180C2 (ru) * | 2012-01-27 | 2017-05-31 | Квэлкомм Инкорпорейтед | Системы и способы для основанного на приоритете управления сеансами и мобильностью двухприоритетных устройств мтс |
JP2014230139A (ja) * | 2013-05-23 | 2014-12-08 | Kddi株式会社 | サービス推定装置及び方法 |
WO2017098859A1 (ja) * | 2015-12-08 | 2017-06-15 | 株式会社日立国際電気 | 通信装置及び通信方法 |
JPWO2017098859A1 (ja) * | 2015-12-08 | 2018-10-18 | 株式会社日立国際電気 | 通信装置及び通信方法 |
US11129045B2 (en) | 2015-12-08 | 2021-09-21 | Hitachi Kokusai Electric Inc. | Communication device and communication method |
JP2019169862A (ja) * | 2018-03-23 | 2019-10-03 | 三菱電機インフォメーションネットワーク株式会社 | 仮想ルータ及び中継プログラム |
JP2022097129A (ja) * | 2020-12-18 | 2022-06-30 | Necプラットフォームズ株式会社 | 通信制御装置、通信制御プログラム及び通信制御方法 |
JP7244106B2 (ja) | 2020-12-18 | 2023-03-22 | Necプラットフォームズ株式会社 | 通信制御装置、通信制御プログラム及び通信制御方法 |
Also Published As
Publication number | Publication date |
---|---|
CN102138305A (zh) | 2011-07-27 |
EP2448183A1 (en) | 2012-05-02 |
JPWO2010150457A1 (ja) | 2012-12-06 |
JP5329663B2 (ja) | 2013-10-30 |
US20120087255A1 (en) | 2012-04-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5329663B2 (ja) | 中継装置及びその方法 | |
US7894364B2 (en) | Method for the transmission of data packets in a tunnel, corresponding computer program product, storage means and tunnel end-point | |
CN109194660B (zh) | 移动终端的入网方法和装置 | |
US9450818B2 (en) | Method and system for utilizing a gateway to enable peer-to-peer communications in service provider networks | |
US7855955B2 (en) | Method for managing frames in a global-area communications network, corresponding computer-readable storage medium and tunnel endpoint | |
US20140226664A1 (en) | Method, apparatus, and system for implementing private network traversal | |
US20080235358A1 (en) | Proxy Device, Network System, and Communication Method | |
EP3335125B1 (en) | CARRIER GRADE ETHERNET LAYER 2 OVER LAYER 3 SATELLITE BACKBONES (L2oL3SB) | |
US8724630B2 (en) | Method and system for implementing network intercommunication | |
JP2008516557A (ja) | ネットワークトラフィックを宛先変更する方法、及びシステム | |
JP2022092005A (ja) | ハイブリッドネットワーク内のルーティング | |
US20050232273A1 (en) | Communications system and a gateway device | |
JP5328899B2 (ja) | 通信帯域制御装置及び通信帯域制御方法 | |
JP5242301B2 (ja) | メッセージを転送する装置、出力方法および出力プログラム | |
CN111788812B (zh) | 用于分组数据转换的技术 | |
CN104168302B (zh) | 设备操控实现方法、系统和代理网关 | |
US20030196118A1 (en) | Service control network and its control method | |
JP3519628B2 (ja) | 中継装置 | |
WO2009131181A1 (ja) | 中継装置、および通信制御装置 | |
WO2016189884A1 (ja) | パケット中継装置およびパケット中継方法 | |
JP3825291B2 (ja) | 中継機、サーバ装置、プログラム及び記録媒体 | |
JP2010288167A (ja) | ネットワーク中継装置 | |
JP2004349854A (ja) | 通信システム | |
WO2000062562A1 (en) | Method and apparatus for interoperation between wireless computer networks and internet protocol-based networks | |
JP2003244213A (ja) | トンネル経路を追加するパケット通信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080002453.8 Country of ref document: CN |
|
ENP | Entry into the national phase |
Ref document number: 2011519504 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13060165 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010791783 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10791783 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |