EP3203706B1 - Dispositif et procédé pour transmettre et recevoir des données à destination et en provenance d'un terminal dans un système de communication sans fil - Google Patents

Dispositif et procédé pour transmettre et recevoir des données à destination et en provenance d'un terminal dans un système de communication sans fil Download PDF

Info

Publication number
EP3203706B1
EP3203706B1 EP15846781.1A EP15846781A EP3203706B1 EP 3203706 B1 EP3203706 B1 EP 3203706B1 EP 15846781 A EP15846781 A EP 15846781A EP 3203706 B1 EP3203706 B1 EP 3203706B1
Authority
EP
European Patent Office
Prior art keywords
dns
communication interface
information
query
handler
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15846781.1A
Other languages
German (de)
English (en)
Other versions
EP3203706A1 (fr
EP3203706A4 (fr
Inventor
Jiangwei XU
Kyeng-Hun LEE
Jin-Hyoung Kim
Jin-Ho Lee
Krishna Manohar SINGH
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of EP3203706A1 publication Critical patent/EP3203706A1/fr
Publication of EP3203706A4 publication Critical patent/EP3203706A4/fr
Application granted granted Critical
Publication of EP3203706B1 publication Critical patent/EP3203706B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • 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/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • 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/58—Caching of addresses or names
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to a method and apparatus for transmitting and receiving data by a terminal in a wireless communication system.
  • a terminal e.g., a portable terminal that supports multiple radio access technology (e.g., Long Term Evolution (LTE), wireless LAN (Wi-Fi), and the like) may perform an HTTP session through a communication interface that supports a corresponding radio access technology, in order to perform downloading through Wi-Fi and LTE.
  • radio access technology e.g., Long Term Evolution (LTE), wireless LAN (Wi-Fi), and the like
  • LTE Long Term Evolution
  • Wi-Fi wireless LAN
  • a portable terminal Before executing an HTTP session, a portable terminal may need to preferentially obtain a host IP address corresponding to a host name from a domain name service (DNS) server.
  • DNS domain name service
  • the portable terminal transmits a DNS query to a DNS server to obtain an IP address, and receives a DNS response including the IP address in response to the transmission.
  • the DNS query may be transmitted through a communication interface that is determined (automatically selected) by default in the portable terminal.
  • the transmission speed of the communication interface determined by default is slower than the transmission speed of another communication interface.
  • a portable terminal may transmit a DNS query through a communication interface that does not support an IP version of a desired host server, and thus, an erroneous result may occur in association with the DNS resolution.
  • the communication interface determined by default has a relatively slower speed than another communication interface, an amount of time expended for the DNS resolution may become long.
  • a DNS resolution may be obtained through any one of the communication interfaces, but may waste power since another communication interface is continuously activated. Also, although a portable terminal obtains a DNS resolution in association with a DNS query through a first communication interface having a high transmission speed from among communication interfaces, a response to an HTTP request may not be quickly received through a second communication interface when the HTTP request is transmitted through the second communication interface which has a low transmission speed.
  • Document US 2014/0173123 A1 discloses a method where a network connection is established with a remote host using the most prioritized one of the IP addresses and a network protocol associated with the most prioritized IP address, where the most prioritized IP address is routable to reach the remote host over a network via the most preferred network interface.
  • various embodiments of the present disclosure provide an apparatus and method for effectively performing a DNS resolution by minimizing power consumption in a portable terminal that supports a multiple radio access technology (multi-RAT).
  • multi-RAT multiple radio access technology
  • an operation method of a terminal in a wireless communication system including: if a domain name service (DNS) query associated with a host is received from a uniform resource locator (URL) protocol handler, comparing previously stored DNS cache information and DNS query information included in the DNS query; and transmitting Internet Protocol (IP) address information corresponding to the host to the URL protocol handler according to a result of the comparison.
  • DNS domain name service
  • URL uniform resource locator
  • Various embodiments of the present disclosure may minimize an amount of time expended for a current DNS resolution by using IP address information stored by a previous DNS resolution.
  • various embodiments of the present disclosure may perform a DNS resolution through a communication interface having a high transmission speed from among a plurality of communication interfaces, thereby providing a high speed HTTP access.
  • various embodiments of the present disclosure may maintain a communication interface, which is not selected from a plurality of communication interfaces, in a deactivated state, thereby minimizing an amount of power consumption of a portable terminal.
  • FIGs. 1 to 26 which are used for describing the principles of the present disclosure are merely for illustrative purposes, and should not be construed as anything that limits the scope of the disclosure. Those skilled in the art can understand that the principles of the present disclosure can be implemented in any properly arranged wireless communication system.
  • FIG. 1 is a diagram illustrating a DNS resolution operation performed through communication interfaces that support Wi-Fi and 3G/LTE in a portable terminal according to a related art of the present disclosure.
  • a portable terminal 101 may include an application (APP) module 103, a uniform resource locator (URL) protocol handler 105, a DNS handler 107, a Wi-Fi communication interface 109, and a 3G/LTE communication interface 111.
  • APP application
  • URL uniform resource locator
  • the application module 103 may request a host access (HTTP request) from the URL protocol handler 105 (Step 1).
  • the URL protocol handler 105 may perform a DNS resolution corresponding to IPv4 through the previously set Wi-Fi communication interface 109 and the DNS handler 107, together with the DNS server 121, and may access a web server 131 through the Wi-Fi communication interface 109 based on an IP address of a host obtained through the DNS resolution (Steps 2, 3, and 4)).
  • the URL protocol handler 105 may perform a DNS resolution corresponding to IPv4 through the DNS handler 107 and the Wi-Fi communication interface 109, thereby obtaining the IP address of the host of which a IP version is IPv4 (Steps 5 and 6). Subsequently, when the URL protocol handler 105 attempts to transmit an HTTP request to the IPv4 web server 131 through the 3G/LTE communication interface 111 of which an IP version is IPv6, the HTTP request may fail due to a difference in IP versions between the 3G/LTE communication interface 111 and the web server 131 (Step 7).
  • FIG. 2 is a diagram illustrating a DNS resolution operation performed through communication interfaces that support Wi-Fi and 3G/LTE, in a portable terminal according to a related art of the present disclosure.
  • a Wi-Fi communication interface may have a weak signal
  • a 3G/LTE communication interface has a strong signal.
  • the application module 103 may request a host access (HTTP request) from the URL protocol handler 105 (Step 1).
  • the URL protocol handler 105 may perform a DNS resolution corresponding to IPv4 for the HTTP request through the previously set Wi-Fi communication interface 109 and the DNS handler 107 from the DNS server 121, and may access the web server 131 through the Wi-Fi communication interface 109 based on an IP address of a host obtained through the DNS resolution (Steps 2, 3, and 4).
  • the URL protocol handler 105 may perform a DNS resolution corresponding to IPv4 through the Wi-Fi communication interface 109, thereby obtaining the IP address of the host (Steps 5 and 6).
  • the URL protocol handler 105 may transmit an HTTP request to the web server 131 through the 3G/LTE communication interface 111 based on the obtained IP address (Step 7).
  • a DNS resolution (a transmission of a DNS query requesting an IP address of a host and a reception of a DNS response thereto) is performed through the Wi-Fi communication interface 109 having a weak signal, and thus, a large amount of time (e.g., 10 [sec]) may be expended for the DNS resolution.
  • FIG. 3 is a diagram illustrating a DNS resolution operation performed through communication interfaces that support Wi-Fi and 3G/LTE in a portable terminal according to a related art of the present disclosure.
  • the portable terminal 101 may include the application module 103, the URL protocol handler 105, the DNS handler 107, the Wi-Fi communication interface 109, and the 3G/LTE communication interface 111.
  • the DNS handler 107 may include a controller 301, a sub-handler 1 303, and a sub-handler 2 305.
  • the sub-handler 1 303 is connected with the Wi-Fi communication interface 109, and may transmit a DNS query to a Wi-Fi DNS server 121 through the Wi-Fi communication interface 109 when receiving the DNS query.
  • the sub-handler 1 303 may receive a DNS response through the Wi-Fi communication interface 109 from the Wi-Fi DNS server 121, in response to the DNS query.
  • the DNS response may include an IP address of a corresponding host.
  • the sub-handler 2 305 may be connected with the 3G/LTE communication interface 111, and may transmit a DNS query to a 3G/LTE DNS server 311 through the 3G/LTE communication interface 111, when receiving the DNS query.
  • the sub-handler 2 305 may receive a DNS response through the 3G/LTE communication interface 111 from the 3G/LTE DNS server 311, in response to the DNS query.
  • a controller 301 may control the sub-handler 1 303 and the sub-handler 2 305.
  • the controller 301 may transmit a DNS query through at least one of the sub-handler 1 303 and the sub-handler 2 305, when receiving the DNS query from the URL protocol handler 105.
  • the controller 301 may transmit a DNS query to both the Wi-Fi communication interface 109 and the 3G/LTE communication interface 111 through the sub-handler 1 303 and the sub-handler 2 305.
  • the Wi-Fi communication interface 109 and the 3G/LTE communication interface 111 switch an idle state into an active state at point 1 323, as shown in a graph 321, and transmits a DNS query.
  • the Wi-Fi communication interface 109 may receive a DNS response at point 2 325, and may switch an active state to an idle state.
  • the 3G/LTE communication interface 111 may receive a DNS response at point 3 327, and may switch an active state to an idle state.
  • the 3G/LTE communication interface 111 maintains a predetermined period of time 329 (from point 2 325 to point 3 327) after receiving a DNS response through the Wi-Fi communication interface 109, thereby wasting power.
  • FIG. 4 is a diagram illustrating a DNS resolution operation performed by a portable terminal having communication interfaces that support Wi-Fi and 3G/LTE according to a related art of the present disclosure.
  • FIG. 4 assumes that a DNS query is transmitted to one of the Wi-Fi communication interface 109 and the 3G/LTE communication interface 111.
  • the controller 301 transmits a DNS query associated with "A.COM" to the Wi-Fi DNS server 121 through the sub-handler 1 303 and the Wi-Fi communication interface 109, and receives a DNS response from the Wi-Fi DNS server 121 through the Wi-Fi communication interface 109.
  • the 3G/LTE communication interface 111 may be in a deactivated state (idle state). Subsequently, as illustrated in the diagrams (b) and (c) of FIG.
  • the controller 301 may transmit a DNS query associated with "A.COM" to the 3G/LTE DNS server 311 through the sub-handler 2 305 and the 3G/LTE communication interface 111, and may receive a DNS response from the 3G/LTE DNS server 311 through the 3G/LTE communication interface 111. After this, the controller 301 may perform a DNS resolution through the 3G/LTE communication interface 111.
  • the DNS resolution associated with "A.COM” is performed again through the 3G/LTE communication interface 111 after the DNS resolution associated with "A.COM” is performed through the WiFi communication interface 109. Therefore, power may be unnecessarily consumed due to the unnecessary operation of the 3G/LTE communication interface 111. Also, a DNS response is received again through the 3G/LTE communication interface 111, and thus, a time for the DNS resolution may be delayed.
  • FIG. 5 is a graph illustrating DNS resolution times corresponding to communication interfaces that support Wi-Fi and 3G/LTE in a portable terminal according to a related art of the present disclosure.
  • the transmission speed of the 3G/LTE communication interface 111 is faster than that of the Wi-Fi communication interface 109, and thus, an operation time 505 of a DNS resolution through the 3G/LTE communication interface 111 may be shorter than an operation time 503 of a DNS resolution through the Wi-Fi communication interface 109.
  • the URL protocol handler 105 may receive a quick response to the HTTP request.
  • the URL protocol handler 105 may not receive a quick response to the HTTP request when an HTTP request is executed through the Wi-Fi communication interface 109.
  • FIG. 6 is a diagram illustrating a DNS resolution operation performed through communication interfaces that support Wi-Fi and 3G/LTE in a portable terminal according to a related art of the present disclosure.
  • a DNS resolution mechanism using a multi-radio access technology may be applied from a second URL request (HTTP request). Therefore, a DNS resolution by a first URL request may be executed through a previously set communication interface among a plurality of communication interfaces.
  • a portable terminal may not efficiently execute a DNS resolution.
  • FIG. 7 is a block diagram of a portable terminal according to an embodiment of the present disclosure.
  • a portable terminal 701 may include an application module 703, a URL protocol handler 705, a DNS handler 707, a Wi-Fi communication interface 719, and a 3G/LTE communication interface 721.
  • the DNS handler 707 may include a controller 709, a network state manager 711, a sub-handler 1 713, a sub-handler 2 715, and a DNS cache 717.
  • the controller 709 may be referred to as a controller.
  • the network state manager 711 may detect a connection state of the Wi-Fi communication interface 719 and a connection state of the 3G/LTE communication interface 721, and may store history information associated with a DNS resolution time of each communication interface.
  • the DNS cache 717 may match a host name and an IP address to an IP version and an ID of a communication interface that receives the corresponding IP address, and may store the same.
  • host information e.g., host name
  • the DNS cache 717 may search for an IP address corresponding to the received host information from among stored host IP addresses, and transmit the retrieved IP address to the controller 709.
  • the DNS cache 717 may transmit the retrieved IP address and information associated with the corresponding communication interface (e.g., the ID and IP version of a communication interface).
  • the controller 709 may receive a DNS query from the URL protocol handler 705, and may transmit the IP address of a host associated with the DNS query to the URL protocol handler 705 in response to the DNS query.
  • the controller 709 may determine the DNS cache 717 and the network state manager 711, and may determine an operation to perform in association with the DNS query.
  • the controller 709 may transmit the retrieved IP address to the URL protocol handler 705.
  • the controller 709 may transmit the DNS query according to a predetermined condition through a plurality of communication interfaces in parallel, or through a relatively faster communication interface from among the plurality of communication interfaces.
  • the predetermined condition may include information indicating whether the transmission speeds of the plurality of communication interfaces are nearly the same, or information indicating which communication interface has a relatively faster transmission speed from among the plurality of communication interfaces.
  • the predetermined condition may be determined based on history information associated with a DNS resolution time stored in the network state manager 711.
  • the sub-handler 1 713 may be connected with the Wi-Fi communication interface 719, and the sub-handler 2 715 may be connected with the 3G/LTE communication interface 721.
  • the DNS handler 707 may include a plurality of sub-handlers for a DNS resolution mechanism using a multi-RAT.
  • the Wi-Fi communication interface 719 may be wirelessly connected to a Wi-Fi DNS server 713, and the 3G/LTE communication interface 721 may be wirelessly connected to a 3G/LTE DNS server 741.
  • FIG. 8 is a flowchart illustrating DNS handling in a portable terminal according to a first embodiment of the present disclosure.
  • the application module 703 transmits the received HTTP request to the URL protocol handler 705 in operation S801.
  • the URL protocol handler 705 transmits a DNS query to the DNS handler 707.
  • the controller 709 of the DNS handler 707 determines whether the name of a host associated with a DNS query exists in the DNS cache 717. When the determination shows that an IP address exists in the DNS cache 717, the controller 709 proceeds with operation S807. Otherwise, the controller 709 proceeds with operation S809.
  • the DNS cache 717 may store the IP address of a predetermined host, as illustrated in FIG.9 .
  • an IP address may be stored together with the ID of a predetermined communication interface that receives a DNS response including the IP version of the communication interface X, a host name, and an IP address, as shown in the diagrams 901 to 907.
  • the controller 709 may search for an IP address that matches the host name and the IP version of the communication interface X, from among IP addresses stored in the DNS cache 717, and may transmit the retrieved IP address to the URL protocol handler 705.
  • the controller 709 may transmit, to the URL protocol handler 705, an IP address that matches the ID of a previously set communication interface from among the plurality of IP addresses.
  • the controller 709 may transmit another IP address to the URL protocol handler 705.
  • the controller 709 may determine that a cache miss has occurred and may proceed with operation S809.
  • the cache miss indicates that an IP address that has the same host name but has a different IP version exists, or indicates that an IP address having the same host name does not exist in the stored IP addresses stored in the DNS cache 717.
  • the controller 709 may determine all communication interfaces having the same IP version as that of the communication interface X, from among the plurality of communication interfaces.
  • a communication interface having the same IP version as the communication interface X may be called an available communication interface, and the available communication interface indicates a communication interface that is connected to the IP address of a host.
  • the controller 709 determines the number of available communication interfaces. When the determination shows that no available communication interface exists, the controller 709 proceeds with operation S813. When the number of available communication interfaces is 1, the controller 709 proceeds with operation S815. When the number of available communication interfaces is 2 or more, the controller 709 proceeds with operation S823.
  • the controller 709 transmits information indicating that an available communication interface does not exist to the URL protocol handler 705.
  • the controller 709 transmits a DNS query to a sub-handler (e.g., the sub-handler 1 713 and the sub-handler 2 715) connected to a corresponding communication interface (e.g., one of the Wi-Fi communication interface 719 and the 3G/LTE communication interface 721).
  • a sub-handler e.g., the sub-handler 1 713 and the sub-handler 2 715) connected to a corresponding communication interface (e.g., one of the Wi-Fi communication interface 719 and the 3G/LTE communication interface 721).
  • the sub-handler generates a DNS query packet, and transmits the DNS query packet to a DNS server (one of the Wi-Fi DNS server 731 and the 3G/LTE DNS server 741) through the corresponding communication interface.
  • the sub-handler receives a DNS response packet from the DNS server, and transmits the same to the controller 709.
  • the DNS response packet may include the IP address of a host.
  • the controller 709 transmits the IP address according to the DNS response to the URL protocol handler 705, and stores the same in the DNS cache 717.
  • the controller 709 may transmit the IP address and an ID of a communication interface that receives the DNS response.
  • the controller 709 may store the IP address in the format as shown in FIG. 9 .
  • the controller 709 transmits a DNS query to each of sub-handlers (e.g., the sub-handler 1 713 and the sub-handler 2 715) connected to available communication interfaces (e.g., the Wi-Fi communication interface 719 and the 3G/LTE communication interface 721).
  • each sub-handler generates a DNS query packet, and transmits the DNS query packet to a DNS server (one of the Wi-Fi DNS server 731 and the 3G/LTE DNS server 741) through a corresponding communication interface.
  • a DNS query may be transmitted through a plurality of available communication interfaces in parallel.
  • a DNS query may be transmitted sequentially through a plurality of available communication interfaces. For example, when a communication interface through which a DNS query is preferentially transmitted may be set by taking into consideration a DNS resolution time, a low power consumption, and the like.
  • the sub-handler receives DNS response packets sequentially from the DNS servers, and transmits the same to the controller 709.
  • the controller 709 transmits, to the URL protocol handler 705, an IP address according to a DNS response that is received first, and stores the same in the DNS cache 717.
  • the controller 709 may transmit the IP address and an ID of a communication interface that receives the DNS response.
  • the controller 709 stores an IP address according to a subsequently received DNS response in the DNS cache 717.
  • FIG. 11 is a flowchart illustrating DNS handling performed in a portable terminal according to a second embodiment of the present disclosure.
  • the URL protocol handler 705 receives a new HTTP request associated with a host from the application module 703, and transmits a DNS query to the DNS handler 707.
  • the controller 709 of the DNS handler 707 receives the DNS query, and determines a host name and the IP version of communication interface X associated with the HTTP request.
  • the controller 709 determines whether an IP address that corresponding to the determined host name and the IP version exists in the DNS cache. When the determination shows that the IP address exists, the controller 709 may proceed with operation S1107. Otherwise, the controller 709 proceeds with operation S1109.
  • the controller 709 searches for IP address information (e.g., IP address) corresponding to the determined host name and the IP version from among IP addresses stored in the DNS cache 717, and transmits the retrieved information to the URL protocol handler 705.
  • IP address information e.g., IP address
  • the controller 709 transmits the DNS query to a DNS server through all available communication interfaces.
  • the controller 709 receives a DNS response from the DNS server in response to the DNS query, and stores the received DNS response in the DNS cache 717.
  • the controller 709 transmits, to the URL protocol handler 705, an IP address corresponding to a DNS response received first.
  • the controller 709 performs operations by changing the sequence of operations S1111 and S1113. For example, the controller 709 transmits, to the URL protocol handler 705, an IP address corresponding to a DNS response received first, and stores the same in the DNS cache 717. The controller 709 may store an IP address corresponding to a subsequently received DNS response in the DNS cache 717, without transmitting the same.
  • FIGs. 12A and 12B are flowcharts illustrating a process in which a portable terminal maps IP address information stored in a DNS cache according to an embodiment of the present disclosure.
  • FIG. 12A assumes that a communication interface that is to perform a DNS resolution is determined.
  • the URL protocol handler 705 transmits a DNS query associated with a determined communication interface to the DNS handler 707 in operation S1201.
  • the URL protocol handler 705 transmits a DNS mapping request together with a URL query signal, to the DNS handler 707.
  • the DNS mapping request may include identification information (e.g., InfX) of a communication interface and a host name (e.g., Host X).
  • the controller 709 of the DNS handler 707 obtains the IP version (e.g., IPvX) of the communication interface from identification information (e.g., InfX) of the communication interface.
  • the controller 709 searches the DNS cache 717 for IP address information that is mapped to the host name (e.g., Host X) and the IP version (e.g., IPvX).
  • the controller 709 determines the number of pieces of mapped IP address information. When the mapped IP address information does not exist, the controller 709 proceeds with operation S1209. When the number of pieces of mapped IP address information is 1, the controller 709 proceeds with operation S1211. When the number of pieces of mapped IP address information is 2 or more, the controller proceeds with operation S1213.
  • the controller 709 determines that a cache miss occurs.
  • the controller 709 transmits the mapped IP address information to the URL protocol handler 705.
  • the controller 709 determines whether IP address information that matches the identification information (e.g., InfX) of the communication interface, exists among the mapped IP address information. When the determination shows that the matching IP address exists, the controller 709 may proceed with operation S1215. Otherwise, the controller 709 proceeds with operation S1217.
  • the identification information e.g., InfX
  • the controller 709 transmits the IP address information that matches the identification information (e.g., InfX) of the communication interface, to the URL protocol handler 705.
  • the controller 709 may transmit, to the URL protocol handler 705, IP address information having a higher communication priority from among the two or more pieces of mapped IP address information.
  • the communication priority may be set in advance by taking into consideration a degree of power consumption, a transmission speed, or the like.
  • the Wi-Fi communication interface 719 may be set to be a first priority
  • the 3G/LTE communication interface 721 may be set to be a second priority.
  • FIG. 12B assumes that a communication interface that is to perform a DNS resolution is not determined.
  • the URL protocol handler 705 transmits a URL query associated with a communication interface, which has not been determined, to the DNS handler 707 in operation S1221.
  • the URL protocol handler 705 transmits a DNS mapping request together with the URL query, to the DNS handler 707.
  • the DNS mapping request may include only a host name (e.g., Host X).
  • the controller 709 of the DNS handler 707 searches the DNS cache 717 for IP address information that is mapped to a host name (e.g., Host X).
  • the controller 709 determines the number of pieces of mapped IP address information. When the determination shows that the IP address information does not exist, the controller 709 proceeds with operation S1227. When the number of pieces of the IP address information is 1, the process proceeds with operation S1229. When the number of pieces of IP address information is two or more, the process proceeds with operation S1231.
  • the controller 709 determines that a cache miss occurs.
  • the controller 709 transmits the mapped IP address information to the URL protocol handler 705.
  • the controller 709 may transmit, to the URL protocol handler 705, IP address information having a higher communication priority from among the two or more pieces of mapped IP address information.
  • FIG. 13 is a flowchart illustrating a process in which a portable terminal transmits a DNS query according to an embodiment of the present disclosure. It is assumed that communication interface Infl is a communication interface that is set in advance for the reduction of power.
  • the controller 709 determines a previous DNS resolution time (a first DNS resolution time (Infl Time)) of communication interface 1 (e.g., the Wi-Fi communication interface 719) based on history information of a DNS resolution time of each communication interface, which is stored in the network state manager 711.
  • the controller 709 determines whether a first DNS resolution time of the communication interface 1 is less than a first threshold time (e.g., a minimum time value of a DNS resolution). When the determination shows that the first DNS resolution time is less than the first threshold time, the controller 709 proceeds with operation S1309. Otherwise, the controller 709 proceeds with operation S 1305.
  • a first DNS resolution time Infl Time
  • the controller 709 determines whether the first DNS resolution time of the communication interface 1 is within a second threshold time range based on a previous DNS resolution time (a second DNS resolution time (Inf2 Time)) of communication interface 2 (e.g., 3G/LTE communication interface 721).
  • the second threshold time is a predetermined value.
  • the controller 709 proceeds with operation S1307. Otherwise, the controller 709 proceeds with operation S1309.
  • the controller 709 determines that the transmission speeds of the communication interface 1 and the communication interface 2 are nearly the same, and transmits a DNS query to a DNS server through the communication interfaces 1 and 2. For example, as illustrated in the diagram (a) of FIG. 14 , when a first DNS resolution time 1401 of the communication interface 1 is within a second threshold time range based on a second DNS resolution time of communication interface 2, the controller 709 transmits a DNS query to DNS servers through the communication interfaces 1 and 2 (e.g., the Wi-Fi communication interface 719 and the 3G/LTE communication interface 721) in parallel at a point 1501, as shown in the diagram (a) of FIG. 15 .
  • the communication interfaces 1 and 2 e.g., the Wi-Fi communication interface 719 and the 3G/LTE communication interface 721
  • the controller 1309 determines that the transmission speed of the communication interface 1 is faster than that of the communication interface 2, and transmits a DNS query through the communication interface 1. For example, as illustrated in the diagram (b) or the diagram (c) of FIG. 14 , when a first DNS resolution time 1403 is less than a first threshold time or when a first DNS resolution time 1405 is out of a second threshold time range of a second DNS resolution time, the controller 709 may transmit a DNS query to a DNS server through the communication interface 1 (e.g., the Wi-Fi communication interface 719) at a point 1503, as shown in the diagram (c) of FIG. 15 .
  • a DNS server e.g., the Wi-Fi communication interface 719
  • the controller 709 determines whether a DNS response to the transmitted DNS query is received within a third threshold time.
  • the third threshold time may be a predetermined value or an average DNS resolution time of DNS resolution times associated with communication interfaces.
  • the controller 709 terminates a DNS query transmission procedure.
  • the controller 709 may proceed with operation S1313.
  • the controller 709 determines whether the communication interface 2 is activated. When the determination shows that the communication interface 2 is activated, the controller 709 proceeds with operation S1317. Otherwise, the controller 709 proceeds with operation S1315. When the controller 709 proceeds with operation S1315, the controller 709 may activate the communication interface 2. For example, the controller 709 may convert the state of the communication interface 2 from an idle state to an active state.
  • the controller 709 transmits a DNS query to a DNS server through the activated communication interface 2. For example, as illustrated in the diagram (c) of FIG. 15 , when the third threshold time elapses from the point 1503, the controller 709 may transmit a DNS query through the communication interface 2 at a point 1505.
  • FIG. 14 is a graph illustrating a relationship between threshold values and previous DNS resolution times according to an embodiment of the present disclosure.
  • FIG. 15 is a graph illustrating a DNS response in response to a DNS query corresponding to the relationship of FIG. 14 according to an embodiment of the present disclosure.
  • the diagram (a) of FIG. 14 is a graph illustrating the case in which a first DNS resolution time 1401 (Infl Time) of communication interface 1 is greater than a first threshold time (Min Threshold 1), and is within a second threshold time (Threshold 2) range of a second DNS resolution time (Inf2 Time) of communication interface 2.
  • the controller 709 transmits a DNS query to DNS servers through all communication interfaces (Wi-Fi and 3G/LTE), receives DNS responses from the DNS servers, and stores (caches) the same in the DNS cache 717.
  • the controller 709 may transmit, to the URL protocol handler 705, IP address information corresponding to a DNS response received first.
  • the diagram (b) of FIG. 14 is a graph illustrating the case in which a first DNS resolution time 1403 of the communication interface 1 is less than a first threshold time.
  • the diagram (c) of FIG. 14 is a graph illustrating the case in which a first DNS resolution time 1405 of the communication interface 1 is greater than a first threshold time, and is out of a second threshold time range of a second DNS resolution time of the communication interface 2.
  • the controller 709 transmits a DNS query to a DNS server through the communication interface 1 (e.g., the Wi-Fi communication interface 719), receives a DNS response from the DNS server through the communication interface 1, and stores the same.
  • the controller 709 may transmit, to the URL protocol handler 705, IP address information corresponding to the received DNS response.
  • the controller 709 transmits a DNS query to the DNS server through the communication interface 2 (e.g., the 3G/LTE communication interface 721) as opposed to the communication interface 1, receives a DNS response from the DNS response, and stores (caches) the same, as illustrated in the diagram (c) of FIG. 15 .
  • the controller 709 may transmit, to the URL protocol handler 705, IP address information corresponding to the received DNS response.
  • information associated with the DNS response may be stored in the DNS cache 717 or the network state manager 711.
  • the information associated with the DNS response may be used as information for determining a network state associated with a subsequent DNS query transmission.
  • the controller 709 When the controller 709 transmits the IP address information corresponding to the received DNS response to the URL protocol handler 705 through a plurality of communication interfaces (Wi-Fi and 3G/LTE communication interfaces 719 and 721), the controller 709 may transmit, to the URL protocol handler 705, communication interface identification information for identifying each communication interface together with the IP address information.
  • FIG. 16 is a flowchart illustrating a process in which a portable terminal requests HTTP according to a DNS response according to an embodiment of the present disclosure.
  • the DNS handler 707 determines whether a DNS query is transmitted through a single communication interface. For example, the DNS handler 707 determines a communication interface through which a DNS query is to be transmitted, based on a DNS resolution time of each communication interface.
  • the DNS handler 707 proceeds with operation S1603. Otherwise, the DNS handler 707 proceeds with operation S1605.
  • the DNS handler 707 transmits a DNS query through a plurality of communication interfaces in parallel.
  • the DNS handler 707 transmits a DNS query to a DNS server through communication interface 1.
  • the DNS handler 707 determines that a predetermined period of time (e.g., a third threshold time) elapses after the transmission of the DNS query.
  • the DNS handler 707 activates communication interface 2 in operation S1609, and transmits a DNS query to a DNS server through the communication interface 2 in operation S1611. That is, the DNS handler 707 performs operations S1605 to S1611, and thus, may sequentially transmit a DNS query through the plurality of communication interfaces.
  • the DNS handler 707 receives a DNS response through the plurality of communication interfaces.
  • the DNS handler 707 transmits IP address information corresponding to the received DNS response together with identification information of a corresponding communication interface to the URL protocol handler 705.
  • the URL protocol handler 705 determines the received communication interface identification information, and may determine a communication interface through which the received IP address information has been received. According to the determination, the URL protocol handler 705 may transmit an HTTP request through the communication interface corresponding to the received IP address information.
  • FIG. 17 is a flowchart illustrating a process in which a portable terminal performs a DNS resolution according to an embodiment of the present disclosure.
  • the DNS handler 707 receives a DNS query associated with a host from the URL protocol handler 705
  • the DNS handler 707 compares DNS cache information stored in a memory and DNS query information included in the DNS query.
  • the memory may be an element corresponding to the DNS cache 717 of FIG. 7 .
  • the DNS cache information may include host name information, communication interface identification information, IP version information corresponding to a communication interface, and IP address information corresponding to a host name.
  • the host name information, the communication interface identification information, the IP version information corresponding to the communication interface, and the IP address information corresponding to the host name may be mapped to one another.
  • DNS cache information 901 stored in a memory may include IPv6 corresponding to IP version information, ABC corresponding to host name information, InfO corresponding to communication interface identification information, and IP0 corresponding to IP address information.
  • DNS cache information 903 may include IPv4 corresponding IP version information, ABC corresponding to host name information, Infl corresponding to communication interface identification information, and IP1 corresponding to IP address information.
  • DNS cache information 905 may include IPv6 corresponding IP version information, ABC corresponding to host name information, Inf0 and Infl corresponding to communication interface identification information, and IP2 and IP3 corresponding to IP address information.
  • the DNS cache information may include a single piece of IP version information and host name information, and a plurality of pieces of different communication interface identification information and a plurality of pieces of different IP address information.
  • DNS cache information 907 may include IPv6 corresponding IP version information, ABC corresponding to host name information, Inf0 and Infl corresponding to communication interface identification information, and IP4 and NoHost corresponding to IP address information.
  • NoHost indicates that IP address information of a host that is mapped to the IP version information, the host name information, and the communication interface identification information does not exist.
  • the DNS query information may include communication interface identification information, IP version information corresponding to a communication interface, host name information, and the like.
  • the communication interface identification information, the IP version information, and the host name information may be information used for obtaining the IP address information of a host.
  • the DNS handler 707 may proceed with operation S1703. Otherwise, the DNS handler 707 may proceed with operation S1705.
  • the DNS handler 707 may transmit, to the URL protocol handler 705, IP address information of the matching DNS cache information For example, when IP version information and/or host name information included in each of a plurality of DNS cache information is identical to IP version information and/or host name information included in the DNS query information, the DNS handler 707 may transmit IP address information corresponding to the IP version information and/or host name information to the URL protocol handler 705.
  • the DNS handler 707 searches for the DNS cache information 903 of which the IP version is IPv4 and the host name is ABC from among the DNS cache information 901 to 907, and transmits communication interface identification information Infl and IP address information IP1 included in the retrieved DNS cache information to the URL protocol handler 705.
  • the DNS handler 707 may transmit communication interface identification information InfO and IP address information IP2 included in the DNS cache information 905 to the URL protocol handler 705, or may transmit communication interface identification information Infl and IP address information IP3 to the URL protocol handler 705 since the DNS cache information 905 includes InfO and Infl corresponding to communication interface identification information and IP2 and IP3 corresponding to IP address information, together with IPv6 corresponding to IP version information and ABC corresponding to host name information.
  • the DNS handler 707 may select a single piece of IP address information according to a predetermined scheme out of a plurality of IP address information, and may transmit the same to the URL protocol handler 705.
  • the predetermined scheme is selecting IP address information that consumes a relatively small amount of power from among the plurality of pieces of IP address information, or selecting IP address information corresponding to communication information having a quick transmission speed from among the IP address information.
  • the DNS handler 707 transmits IP address information IP2 corresponding to the communication interface identification information InfO to the URL protocol handler 705.
  • the DNS handler 707 may transmit communication interface identification information Infl and IP address information IP4 included in the DNS cache information 907 to the URL protocol handler 705 since the DNS cache information 907 includes InfO and Infl corresponding to communication interface identification information and IP4 and NoHost corresponding to IP address information, together with IPv6 corresponding to IP version information and ABC corresponding to host name information.
  • the IP address information that matches the communication interface identification information InfO does not exist (NoHost), and thus, the DNS handler 707 may not transmit the communication interface identification information InfO and NoHost information corresponding thereto to the URL protocol handler 705.
  • the DNS handler 707 transmits a DNS query to a DNS server through at least one communication interface. Operation S1705 will be described through FIG. 18 .
  • the DNS handler 707 receives a DNS response including IP address information from the DNS server in response to the DNS query.
  • the DNS handler 707 receives the DNS response from the DNS server in response to the DNS query, through a network.
  • the DNS response may be received through a communication interface that transmits the DNS query to the DNS server.
  • the DNS handler 707 may receive a DNS response through the Wi-Fi communication interface 719.
  • the DNS handler 707 receives a DNS response through the 3G/LTE communication interface 721.
  • the DNS handler 707 stores IP address information included in the received DNS response, and transmits the same to the URL protocol handler 705. For example, when a DNS response is received through each of a plurality of communication interfaces, the DNS handler 707 may transmit, to the URL protocol handler 705, IP address information corresponding to a DNS response received first.
  • the DNS handler 707 may transmit, to the URL protocol handler 705, the IP address information and communication interface identification information of a communication interface through which the DNS response is received. For example, when a DNS response is received through the 3G/LTE communication interface 721, the DNS handler 707 may transmit IP address information included in the received DNS response and identification information of the 3G/LTE communication interface 721, to the URL protocol handler 705. Accordingly, the URL protocol handler 705 may determine the IP address information and the communication interface identification information, and may determine a communication interface through which the first received IP address information has been received. Also, the URL protocol handler 705 may transmit an HTTP request through the communication interface corresponding to the IP address information received first.
  • the IP address information included in the received DNS response may be stored in the memory, as DNS cache information.
  • the DNS cache information may include IP version information corresponding to the received DNS response, host name information, communication interface identification information, and IP address information received from the DNS server.
  • the DNS cache information stored in the memory may be used as information for a subsequent DNS resolution.
  • FIG. 18 is a flowchart illustrating a process in which a portable terminal transmits a DNS query signal to a DNS server according to an embodiment of the present disclosure.
  • the DNS handler 707 may determine at least one communication interface from among a plurality of communication interfaces, and may transmit a DNS query to a DNS server through the determined communication interface.
  • the DNS handler 707 may determine one of the plurality of communication interfaces according to a predetermined scheme.
  • the predetermined scheme may be selecting a communication interface that consumes a relatively small amount of power from among the plurality of communication interfaces, or selecting a communication interface having a fast transmission speed.
  • the DNS handler 707 may determine the Wi-Fi communication interface 719 as a communication interface used for transmitting a DNS query to a DNS server.
  • the DNS handler 707 determines whether a first DNS resolution time (Infl Time) through communication interface 1 corresponding to one of two or more communication interfaces is less than or equal to a first threshold time.
  • the first DNS resolution time indicates an amount of time expended for a previous DNS resolution through the communication interface 1. That is, the first DNS resolution time indicates a period of time that elapses while a DNS resolution is achieved through the communication interface 1 in a previous process.
  • the first DNS resolution time may be stored in the network state manager 711, which will be described later.
  • the DNS handler 707 may determine whether a first DNS resolution time 1403 (Infl Time) of the communication interface 1 is less than or equal to a first threshold time (Min Threshold 1).
  • the DNS handler 707 proceeds with operation S1807. Otherwise, the DNS handler 707 proceeds with operation S1803.
  • the DNS handler 707 may determine whether the first DNS resolution time is within a second threshold time range based on a second DNS resolution time through communication interface 2, which corresponds to another one of the two or more communication interfaces.
  • the second DNS resolution time indicates an amount of time expended for a previous DNS resolution through the communication interface 2. That is, the second DNS resolution indicates a period of time that elapses while a DNS resolution is achieved through the communication interface 2 in a previous process.
  • the second DNS resolution time may be stored in the network state manager 711. For example, as illustrated in FIG.
  • the DNS handler 707 may determine whether the first DNS resolution time is within the second threshold time range (Threshold2) of the second DNS resolution time (Inf2 Time) when the first DNS resolution time 1401 of the communication interface 1 is greater than the first threshold time (Min Threshold1).
  • the DNS handler 707 proceeds with operation S1805. Otherwise, the DNS handler 707 proceeds with operation S1807.
  • the DNS handler 707 may transmit a DNS query to DNS server 1 and DNS server 2 through the communication interface 1 and the communication interface 2.
  • the DNS handler 707 may respectively transmit a DNS query to the DNS server 1 and the DNS server 2 through all communication interfaces (Wi-Fi and 3G/LTE), as illustrated in the diagram (a) of FIG. 15 .
  • the DNS handler 707 transmits a DNS query to the DNS server 1 through communication interface 1.
  • the DNS handler 707 may transmit a DNS query to the DNS server 1 through the communication interface 1 (WiFi), as illustrated in the diagram (b) of FIG. 15 .
  • the communication interface 1 WiFi
  • the DNS handler 707 may transmit a DNS query to the DNS server 2 through the communication interface 1 (Wi-Fi), as illustrated in the diagram (b) of FIG. 15 .
  • the DNS handler 707 determines whether a DNS response to the transmitted DNS query is received within a third threshold time.
  • the third threshold time may indicate an average time for a DNS resolution.
  • the average time for a DNS resolution may indicate a value obtained by dividing the sum of DNS resolution times by the number of DNS resolutions.
  • the DNS handler 707 terminates a DNS query transmission procedure. Unlike the above, when the DNS response is not received within the third threshold time, the DNS handler 707 may proceed with operation S1811.
  • the DNS handler 707 transmits a DNS query to the DNS server 2 through the communication interface 2 from among two or more communication interfaces.
  • the DNS response is not received within the third threshold time after the DNS query is transmitted to the DNS server 1 through the communication interface 1, it may indicate that the transmission speed of the communication interface 1 is slow. Therefore, in this instance, as illustrated in the diagram (c) of FIG. 15 , the DNS handler 707 transmits a DNS query to the DNS server 2 through another communication interface, which is different from the communication interface 1 (Wi-Fi), that is, the communication interface 2 (3G/LTE).
  • FIG. 19 is a block diagram of a portable terminal according to an embodiment of the present disclosure.
  • a DNS resolution device 1901 is contained in a portable terminal, and the portable terminal includes a URL protocol handler 1913, communication interface 1 1915, and communication interface 2 1917, in addition to the DNS resolution device 1901. Elements for general operations of the portable terminal are not illustrated. As other elements, for ease of description, the DNS server 1 1921 and the DNS server 2 1931 are illustrated. Although FIG. 19 illustrates two DNS sub-handlers and communication interfaces, respectively, this is merely an example and the number thereof may be increased.
  • the portable terminal may include a smartphone, a tablet personal computer (PC), a mobile phone, a video phone, an e-book reader, a netbook computer, a personal digital assistant (PDA), a portable multimedia player (PMP), an MP3 player, a mobile medical device, a camera, or a wearable device (e.g., a head-mounted-device (HMD), such as electronic glasses, electronic clothes, an electronic bracelet, an electronic necklace, an electronic appcessory, an electronic tattoo, or a smart watch), or the like.
  • a wearable device e.g., a head-mounted-device (HMD), such as electronic glasses, electronic clothes, an electronic bracelet, an electronic necklace, an electronic appcessory, an electronic tattoo, or a smart watch
  • the DNS resolution device 1901 may include a memory 1905, a controller 1903, a network state manager 1907, DNS sub-handler 1 1909, and DNS sub-handler 2 1911.
  • the memory 1905 stores DNS cache information.
  • the memory 1905 may map host name information, communication interface identification information, IP version information corresponding to a communication interface, and IP address information corresponding to a host name to one another, and may store the same.
  • the DNS cache information may include identical IP version information and host name information, communication interface identification information, and IP address information.
  • the memory 1905 may store at least one piece of DNS cache information.
  • the controller 1903 may compare DNS cache information stored in the memory 1905 with DNS query information included in the DNS query, and transmits IP address information corresponding to the host to the URL protocol handler 1913, according to a result of the comparison between the DNS cache information and the DNS query information.
  • the DNS query information may include communication interface identification information, IP version information, and host name information, and the like.
  • the controller 1903 may access the memory 1905, and may transmit IP address information corresponding to IP version information and/or host name information to the URL protocol handler 1913 when the IP version information and/or host name information included in the DNS cache information is identical to IP version information and/or host name information included in the DNS query information.
  • the controller 1903 may transmit, to the URL protocol handler 1913, IP address information according to a predetermined scheme out of the two or more pieces of IP address information. In this instance, the controller 1903 may transmit, to the URL protocol handler 1913, IP address information that consumes a relatively small amount of power or IP address information corresponding to a communication interface having a quick transmission speed, from among the two or more pieces of IP address information.
  • the DNS sub-handler 1 1909 and the DNS sub-handler 2 1911 may transmit a DNS query to the DNS server 1 1921 and the DNS server 2 1931 through the communication interface 1 1915 and the communication interface 2 1917, respectively, according to the control of the controller 1903.
  • the controller 1903 may access the memory 1905, and may perform a control to transmit a DNS query to the DNS server 1 1921 and the DNS server 2 1931 through at least one of the communication interface 1 1915 and the communication interface 2 1917 when the IP version information and host name information included in the DNS cache information are different from the IP version information and host name information included in the DNS query information. Subsequently, when a DNS response including IP address information corresponding to the DNS query is received from the DNS server 1 1921 and/or the DNS server 2 1931 through one or more communication interfaces, the controller 1903 may transmit the IP address information included in the received DNS response to the URL protocol handler 1913.
  • the controller 1903 may determine at least one communication interface out of two or more communication interfaces, and may transmit a DNS query to a DNS server through the determined communication interface.
  • the controller 1903 may determine a communication interface that consumes a relatively smaller amount of power or a communication interface having a high transmission speed from among two or more communication interfaces, as the communication interface through which the DNS query is to be transmitted.
  • the network state manager 1907 may store and manage a DNS resolution time, which indicates an amount of time expended for a previous DNS resolution through at least one communication interface.
  • the network state manager 1907 may store and manage a DNS resolution time by distinguishing a DNS resolution time based on a communication interface through which a corresponding DNS resolution is performed. For example, the network state manager 1907 may store a first DNS resolution time according to a DNS resolution performed through the communication interface 1 1915, and may store a second DNS resolution time according to a DNS resolution performed through the communication interface 2 1917.
  • the controller 1903 may access the network state manager 1907, may determine whether the first DNS resolution time through the communication interface 1 1915, which is one of two or more communication interfaces, is less than or equal to a first threshold time, and may perform a control to transmit a DNS query to the DNS server 1 1921 corresponding to the communication interface 1 1915, through the communication interface 1 1915, when the first DNS resolution time is less than or equal to the first threshold time.
  • the controller 1903 determines whether the first DNS resolution time is within a second threshold time range of the second DNS resolution time through the communication interface 2 1917, which is another communication interface from among the two or more communication interfaces, and performs a control to transmit a DNS query signal to the DNS server 1 1921 through the communication interface 1 1915 when the first DNS resolution time is out of the second threshold time range.
  • the controller 1903 may perform a control to transmit a DNS query signal to the DNS server 1 1921 and the DNS server 2 1931 through the communication interface 1 1915 and the communication interface 2 1917, respectively.
  • the controller 1903 determines whether a DNS response is received within a third threshold time in response to the DNS query, after transmitting the DNS query trough the determined communication interface, and performs a control to transmit a DNS query to a DNS server through one out of two or more communication interfaces when the DNS response is not received within the third threshold time.
  • the third threshold time may indicate an average time for a DNS resolution.
  • the controller 1903 may transmit IP address information corresponding to a DNS response received first to the URL protocol handler 1913. In this instance, the controller 1903 may transmit, to the URL protocol handler 1913, the IP address information together with identification information of a communication interface that receives the DNS response from among two or more communication interfaces.
  • the controller 1903 may perform a control to store the IP address information included in the received DNS response in the memory 1905, as DNS cache information.
  • the controller 1903 may perform a control to map the IP version information, host name information, and communication interface identification information corresponding to the received DNS response to the IP address information, and to store the same.
  • the following operational characteristics in association with a DNS resolution may exist.
  • FIG. 20 is a block diagram of a portable terminal including a plurality of communication interfaces that have IP versions different from each other, according to an embodiment of the present disclosure.
  • communication interface 0 2003 corresponds to IPv4
  • communication interface 1 corresponds to IPv6.
  • a DNS handler 2001 receives a DNS query associated with IPv4
  • the DNS query may be transmitted to DNS server 1 through the communication interface 0 2003 and a DNS response corresponding to the DNS query may be received from the DNS server 1 through the communication interface 0 2003.
  • a DNS handler 2005 receives a DNS query associated with IPv6
  • the DNS query may be transmitted to DNS server 2 through the communication interface 1 2007, and a DNS response corresponding to the DNS query may be received from the DNS server 2 through the communication interface 1 2007.
  • FIG. 21 is a diagram illustrating a DNS resolution performed in a portable terminal according to a first embodiment of the present disclosure.
  • a controller of a DNS handler 2101 when a controller of a DNS handler 2101 receives a DNS query from a URL protocol handler 2103, the controller may determine whether IP address information corresponding to the DNS query exists from among IP address information stored in a DNS cache.
  • the controller may transmit a DNS query to DNS servers 1 and 2 through a plurality of DNS sub-handlers 1 and 2 and communication interfaces 1 and 2, and transmits, to the URL protocol handler 2103, IP address information included in a DNS response received first from the DNS servers 1 and 2.
  • a DNS resolution may be promptly performed according to the transmission speed of each of the communication interfaces 1 and 2.
  • FIG. 22 is a diagram illustrating a DNS resolution performed in a portable terminal according to a second embodiment of the present disclosure.
  • a controller of a DNS handler 2201 when a controller of a DNS handler 2201 receives DNS query 1 associated with a predetermined host from a URL protocol handler 2203, the controller may transmit the DNS query 1 to DNS server 1 through communication interface 1 using sub-handler 1.
  • the controller may receive a DNS response from the DNS server 1 through the communication interface 1 using the sub-handler 1, in response to the DNS query 1, may store IP address information included in the received DNS response in a DNS cache, and may transmit the same to the URL protocol handler 2203.
  • the controller may search for IP address information corresponding to the DNS query from among IP address information stored in the DNS cache. For example, when the DNS queries 1 and 2 are DNS queries associated with the same host, the controller may detect IP address information corresponding to the DNS query 1 from the DNS cache, and may transmit the same to the URL protocol handler 2203.
  • a DNS resolution may be promptly performed without an access to a communication interface and a DNS server corresponding thereto.
  • FIG. 23 is a diagram illustrating a DNS resolution performed in a portable terminal according to a third embodiment of the present disclosure.
  • a controller 2303 of a DNS handler 2301 when a controller 2303 of a DNS handler 2301 receives a DNS query from a URL protocol handler, the controller may determine a communication interface having a high transmission speed from among a plurality of communication interfaces (Wi-Fi and 3G/LTE). For example, the controller 2303 may determine a communication interface based on DNS resolution time information for each communication interface stored in the network state manager 2305.
  • the controller 2303 may transmit a DNS query to a Wi-Fi DNS server 2311 through a Wi-Fi communication interface 2309 using a sub-handler 2307.
  • the controller 2303 may perform a DNS resolution by transmitting a DNS query through only the Wi-Fi communication interface, and a 3G/LTE communication interface may maintain an idle state. Accordingly, power may not be consumed since the 3G/LTE communication interface is deactivated.
  • FIG. 24 is a diagram illustrating a DNS resolution performed in a portable terminal according to a fourth embodiment of the present disclosure.
  • a controller 2403 of a DNS handler 2401 may receive a DNS query associated with a host from a URL protocol handler.
  • the controller 2403 may transmit a DNS query to a Wi-Fi DNS server 2411 through a Wi-Fi communication interface 2409 using a sub-handler 1 2405.
  • the controller 2403 may receive a DNS response from the Wi-Fi DNS server 2411, may generate IP address information (e.g., DNS cache information) based on the received DNS response, and may store the same in a DNS cache 2407.
  • IP address information e.g., DNS cache information
  • the DNS handler 2401 may perform a DNS resolution using IP address information (e.g., DNS cache information) stored in the DNS cache 2407 even though no communication interface is connected to a network.
  • IP address information e.g., DNS cache information
  • FIG. 25 is a graph illustrating a DNS resolution time for each communication interface according to an embodiment of the present disclosure.
  • a URL protocol handler may preferentially transmit a URL query (HTTP request) 2507 through a communication interface (e.g., 3G/LTE communication interface) corresponding to a short DNS resolution time from among DNS resolution times 2503 and 2505 of two or more communication interfaces.
  • a communication interface e.g., 3G/LTE communication interface
  • FIG. 26 is a diagram illustrating a DNS resolution performed in a portable terminal according to a fifth embodiment of the present disclosure.
  • a controller 2603 of a DNS handler 2601 when a controller 2603 of a DNS handler 2601 receives a DNS query from a URL protocol handler, the controller 2603 may determine an available communication interface (e.g., the Wi-Fi communication interface 2611) based on DNS resolution time information for each communication interface included in a network state manager 2605. The controller 2603 may transmit a DNS query to a Wi-Fi DNS server 2621 through the Wi-Fi communication interface 2611 using a sub-handler 1 2607.
  • an available communication interface e.g., the Wi-Fi communication interface 2611
  • the controller 2603 may transmit a DNS query to a Wi-Fi DNS server 2621 through the Wi-Fi communication interface 2611 using a sub-handler 1 2607.
  • the controller 2603 may transmit a DNS query to a 3G/LTE DNS server 2631 through a 3G/LTE communication interface 2613, which is another communication interface, using a sub-handler 2 2609. Accordingly, the DNS handler 2601 may promptly receive a DNS response through the 3G/LTE communication interface 2631.
  • Methods according to embodiments stated in the claims and/or specifications may be implemented by hardware, software, or a combination of hardware and software.
  • a computer-readable storage medium for storing one or more programs may be provided.
  • the one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device.
  • the one or more programs may include instructions for allowing the electronic device to perform methods according to embodiments stated in the claims and/or specifications of the present disclosure.
  • the programs may be stored in non-volatile memories including a random access memory and a flash memory, a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic disc storage device, a Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other type optical storage devices, or a magnetic cassette.
  • ROM Read Only Memory
  • EEPROM Electrically Erasable Programmable Read Only Memory
  • CD-ROM Compact Disc-ROM
  • DVDs Digital Versatile Discs
  • any combination of some or all of the may form a memory in which the program is stored. Further, a plurality of such memories may be included in the electronic device.
  • the programs may be stored in an attachable storage device which may access the electronic device through communication networks such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), and Storage Area Network (SAN) or a combination thereof.
  • the storage device may access the electronic device through an external port.
  • a separate storage device on a communication network may access a portable electronic device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Claims (15)

  1. Procédé de fonctionnement d'un terminal dans un système de communication sans fil, le procédé comprenant :
    comparer des informations d'antémémoire de service de nom de domaine, DNS, stockées dans le terminal avec des informations de requête de DNS incluses dans une requête de DNS associée à un hôte si la requête de DNS est pourvue à partir d'un gestionnaire de protocole de localisateur uniforme de ressource, URL ; et
    fournir des informations d'adresse de protocole Internet, IP, correspondant à l'hôte au gestionnaire de protocole d'URL selon un résultat de la comparaison,
    où les informations d'antémémoire de DNS stockées dans le terminal sont définies sur la base d'au moins l'une d'une vitesse de transmission et d'une quantité de consommation d'énergie.
  2. Procédé selon la revendication 1, où les informations d'antémémoire de DNS comprennent au moins l'une parmi des informations de nom d'hôte, des informations d'identification d'interface de communication, des informations de version IP correspondant à une interface de communication et des informations d'adresse IP correspondant à un nom d'hôte.
  3. Procédé selon la revendication 1, où les informations de requête de DNS comprennent au moins l'une parmi des informations d'identification d'interface de communication, des informations de version IP correspondant à une interface de communication et des informations de nom d'hôte.
  4. Procédé selon la revendication 1, où la fourniture des informations d'adresse IP au gestionnaire de protocole d'URL comprend :
    si les informations de nom d'hôte incluses dans les informations d'antémémoire de DNS sont identiques aux informations de nom d'hôte incluses dans les informations de requête de DNS, fournir les informations d'adresse IP correspondant aux informations de nom d'hôte au gestionnaire de protocole d'URL.
  5. Procédé selon la revendication 1, où la fourniture des informations d'adresse IP au gestionnaire de protocole d'URL comprend :
    si les informations de version IP et les informations de nom d'hôte incluses dans les informations d'antémémoire de DNS sont identiques aux informations de version IP et aux informations de nom d'hôte incluses dans les informations de requête de DNS, fournir les informations d'adresse IP correspondant aux informations de version IP et aux informations de nom d'hôte au gestionnaire de protocole d'URL.
  6. Procédé selon la revendication 5, où la fourniture des informations d'adresse IP au gestionnaire de protocole d'URL comprend :
    s'il existe au moins deux informations d'adresse IP correspondant aux informations de version IP et aux informations de nom d'hôte, sélectionner une information d'adresse IP parmi les au moins deux informations d'adresse IP sur la base d'au moins l'une parmi une vitesse de transmission et une quantité de consommation d'énergie associées à une pluralité d'interfaces de communication pour fournir les informations d'adresse IP sélectionnées au gestionnaire de protocole d'URL.
  7. Procédé selon la revendication 1, où la fourniture des informations d'adresse IP au gestionnaire de protocole d'URL comprend :
    transmettre la requête de DNS à un serveur de DNS par l'intermédiaire d'au moins une interface de communication si des informations de nom d'hôte incluses dans les informations d'antémémoire de DNS sont différentes des informations de nom d'hôte incluses dans les information de requête de DNS ;
    recevoir une réponse de DNS en réponse à la requête de DNS en provenance du serveur de DNS pour stocker la réponse de DNS ; et
    fournir des informations d'adresse IP incluses dans la réponse de DNS stockée au gestionnaire de protocole d'URL.
  8. Procédé selon la revendication 7, où la transmission de la requête de DNS au serveur de DNS par l'intermédiaire de l'au moins une interface de communication comprend :
    déterminer au moins une interface de communication parmi la pluralité d'interfaces de communication sur la base d'au moins l'une d'une quantité de consommation d'énergie et d'une vitesse de transmission associées à la pluralité d'interfaces de communication ; et
    transmettre la requête de DNS au serveur de DNS par l'intermédiaire de l'interface de communication déterminée.
  9. Procédé selon la revendication 8, où la transmission de la requête de DNS au serveur de DNS par l'intermédiaire de l'au moins une interface de communication comprend :
    déterminer si un premier temps de résolution de DNS qui indique un temps de résolution de DNS précédent par l'intermédiaire d'une première interface de communication parmi la pluralité d'interfaces de communication est inférieur ou égal à un premier temps de seuil précédemment désigné ; et
    transmettre la requête de DNS à un premier serveur de DNS correspondant à la première interface de communication par l'intermédiaire de la première interface de communication lorsque le premier temps de résolution de DNS est inférieur ou égal au premier temps de seuil.
  10. Procédé selon la revendication 9, comprenant en outre :
    si le premier temps de résolution de DNS dépasse le premier temps de seuil, déterminer si le premier temps de résolution de DNS existe dans une deuxième plage de temps de seuil d'un deuxième temps de résolution de DNS qui indique un temps de résolution de DNS précédent par l'intermédiaire d'une deuxième interface de communication parmi la pluralité d'interfaces de communication ; et
    transmettre la requête de DNS au premier serveur de DNS par l'intermédiaire de la première interface de communication lorsque le premier temps de résolution de DNS n'existe pas dans la deuxième plage de temps de seuil.
  11. Procédé selon la revendication 10, comprenant en outre :
    si le premier temps de résolution de DNS existe dans la deuxième plage de temps de seuil, transmettre la requête de DNS au premier serveur de DNS et au deuxième serveur de DNS correspondant à la deuxième interface de communication par l'intermédiaire de la première interface de communication et de la deuxième interface de communication, respectivement.
  12. Procédé selon la revendication 8, comprenant en outre :
    déterminer si la réponse de DNS en réponse à la requête de DNS est reçue dans un troisième temps de seuil précédemment désigné ; et
    transmettre la requête de DNS par l'intermédiaire d'une autre interface de communication parmi la pluralité d'interfaces de communication si la réponse de DNS n'est pas reçue dans le troisième temps de seuil.
  13. Procédé selon la revendication 8, où la transmission des informations d'adresse IP correspondant à la requête de DNS au gestionnaire de protocole d'URL comprend :
    si la réponse de DNS correspondant à la requête de DNS est reçue par l'intermédiaire de la pluralité d'interfaces de communication, après avoir stocké des informations d'adresse IP correspondant à une réponse de DNS reçue précédemment, transmettre les informations d'adresse IP stockées au gestionnaire de protocole d'URL.
  14. Procédé selon la revendication 8, où la transmission des informations d'adresse IP correspondant à la requête de DNS au gestionnaire de protocole d'URL comprend :
    fournir, au gestionnaire de protocole d'URL, les informations d'adresse IP et les informations d'identification d'une interface de communication qui reçoit la réponse de DNS.
  15. Terminal dans un système de communication sans fil, comprenant :
    un contrôleur configuré pour mettre en œuvre un procédé de l'une quelconque des revendications 1 à 14.
EP15846781.1A 2014-10-02 2015-10-02 Dispositif et procédé pour transmettre et recevoir des données à destination et en provenance d'un terminal dans un système de communication sans fil Active EP3203706B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020140133161A KR102154788B1 (ko) 2014-10-02 2014-10-02 무선 통신 시스템의 단말에서 DNS(Domain Name Service) 레졸루션 방법 및 장치
PCT/KR2015/010423 WO2016053045A1 (fr) 2014-10-02 2015-10-02 Dispositif et procédé pour transmettre et recevoir des données à destination et en provenance d'un terminal dans un système de communication sans fil

Publications (3)

Publication Number Publication Date
EP3203706A1 EP3203706A1 (fr) 2017-08-09
EP3203706A4 EP3203706A4 (fr) 2017-09-27
EP3203706B1 true EP3203706B1 (fr) 2020-04-15

Family

ID=55630987

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15846781.1A Active EP3203706B1 (fr) 2014-10-02 2015-10-02 Dispositif et procédé pour transmettre et recevoir des données à destination et en provenance d'un terminal dans un système de communication sans fil

Country Status (4)

Country Link
US (1) US10448325B2 (fr)
EP (1) EP3203706B1 (fr)
KR (1) KR102154788B1 (fr)
WO (1) WO2016053045A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10142282B2 (en) * 2012-11-05 2018-11-27 Pismo Labs Technology Limited Methods and gateways for processing DNS request
KR101942158B1 (ko) * 2016-11-04 2019-02-19 주식회사 시큐아이 네트워크 보안 방법 및 그 장치
CN109218050B (zh) * 2017-06-30 2021-07-13 贵州白山云科技股份有限公司 一种域名系统故障处理方法和系统
US10666603B2 (en) * 2017-07-13 2020-05-26 T-Mobile Usa, Inc. Optimizing routing of access to network domains via a wireless communication network
CN112565482B (zh) * 2018-11-21 2022-04-15 Oppo广东移动通信有限公司 电子设备、域名查询方法及相关产品
CN110674098B (zh) * 2019-09-19 2022-04-22 浪潮电子信息产业股份有限公司 一种分布式文件系统中的域名解析方法

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7444371B2 (en) * 2004-03-11 2008-10-28 At&T Intellectual Property Ii, L.P. Method and apparatus for limiting reuse of domain name system response information
KR100765238B1 (ko) 2006-08-24 2007-10-09 엘지전자 주식회사 이동통신단말의 ｄｎｓ 정보 획득방법 및 이를 위한이동통신단말기
CN100502367C (zh) * 2007-04-04 2009-06-17 华为技术有限公司 保存域名系统记录的方法、装置
US7970940B1 (en) * 2009-12-22 2011-06-28 Intel Corporation Domain name system lookup latency reduction
US8671221B2 (en) * 2010-11-17 2014-03-11 Hola Networks Ltd. Method and system for increasing speed of domain name system resolution within a computing device
WO2012094675A2 (fr) * 2011-01-07 2012-07-12 Seven Networks, Inc. Système et procédé de réduction du trafic sur les réseaux de mobiles utilisé pour les requêtes aux systèmes de noms de domaine (dns)
US8738765B2 (en) * 2011-06-14 2014-05-27 Lookout, Inc. Mobile device DNS optimization
KR20130014226A (ko) * 2011-07-29 2013-02-07 한국전자통신연구원 공격 트래픽 형태별 특성에 따른 ｄｎｓ 플러딩 공격 탐지 방법
US9215283B2 (en) 2011-09-30 2015-12-15 Alcatel Lucent System and method for mobility and multi-homing content retrieval applications
US8874790B2 (en) * 2011-12-30 2014-10-28 Verisign, Inc. DNS package in a partitioned network
KR20140036981A (ko) * 2012-09-16 2014-03-26 엘지전자 주식회사 클라이언트 기기 및 그 통신 수행 방법
US9866448B2 (en) * 2012-09-18 2018-01-09 Htc Corporation Electronic device and method for DNS processing
WO2014047452A1 (fr) * 2012-09-21 2014-03-27 Interdigital Patent Holdings, Inc. Dispositif et procédé pour permettre une sélection de serveur dns à l'aide d'andsf dans des hôtes à interfaces multiples
US9407701B2 (en) * 2012-12-14 2016-08-02 Apple Inc. Address family preference in multiple network interface environments
KR101482516B1 (ko) * 2013-03-20 2015-01-16 주식회사에어플러그 무선 통신망에의 추가 접속시의 망 사용을 제어하는 방법과 그 방법을 위한 장치
WO2014188233A1 (fr) * 2013-05-23 2014-11-27 Pismo Labs Technology Ltd. Méthodes et systèmes pour système de nom de domaine dynamique (ddns)
WO2015031356A1 (fr) * 2013-08-26 2015-03-05 Seven Networks, Inc. Mise en antémémoire améliorée d'un système de nom de domaine (dns) et requête dns inverse pour la gestion de trafic permettant une optimisation de la signalisation sur un réseau mobile
US10296925B2 (en) * 2014-02-05 2019-05-21 PushSpring, Inc. Automatic profiling of a mobile device and/or its user
US9131032B1 (en) * 2014-03-10 2015-09-08 Cellco Partnership Methods and improvements in UICC polling mechanism for UICC management

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US10448325B2 (en) 2019-10-15
EP3203706A1 (fr) 2017-08-09
KR20160039882A (ko) 2016-04-12
US20170280386A1 (en) 2017-09-28
WO2016053045A1 (fr) 2016-04-07
KR102154788B1 (ko) 2020-09-11
EP3203706A4 (fr) 2017-09-27

Similar Documents

Publication Publication Date Title
EP3203706B1 (fr) Dispositif et procédé pour transmettre et recevoir des données à destination et en provenance d'un terminal dans un système de communication sans fil
US8509753B2 (en) Transfer of data-intensive content between portable devices
US9736767B2 (en) Identification-assisted wireless network connections
US9052898B2 (en) Remote access and administration of device content, with device power optimization, using HTTP protocol
WO2016023357A1 (fr) Procédé et appareil d'accès à une page web et routeur
US20130318194A1 (en) Micro-Staging Device and Method for Micro-Staging
US20160182639A1 (en) Internet of things network system using fog computing network
US9351174B2 (en) Method and system for acquiring location information
US20160112830A1 (en) Method and Apparatus for Detecting Smartphone Application Users Utilizing Globally Unique Identifiers and Wireless Sensors
US20140173123A1 (en) Address family preference in multiple network interface environments
WO2017152433A1 (fr) Procédé et dispositif permettant d'effectuer le transfert intercellulaire d'un équipement utilisateur entre des points d'accès sans fil
CN111741039B (zh) 会话请求处理方法、装置及电子设备
EP3507712A1 (fr) Systèmes et procédés de fourniture d'un stockage en nuage de périphérie et d'un système de cache fonctionnant sur un réseau local
CN112888042B (zh) 基于移动终端的智能手表控制方法、装置、终端及介质
US10660141B2 (en) Communication link establishments via identifiers
RU2615759C2 (ru) Способ и устройство для видеозаписи
US8977785B2 (en) Machine to machine development environment
CN111163190A (zh) 一种跨网段获取服务端ip的方法及系统
WO2016186628A1 (fr) Redirection de bus matériel
JP6036983B2 (ja) 情報処理装置および起動制御プログラム
WO2019018993A1 (fr) Procédé et appareil de radiomessagerie de dispositif utilisable
KR101331998B1 (ko) 원격 접속을 통한 ｐ2ｐ 시스템
WO2017190513A1 (fr) Procédé et dispositif pour déterminer un point d'accès sans fil auquel un équipement utilisateur a accès
KR101565293B1 (ko) Ｈｔｔｐ 프로토콜을 사용한 디바이스 전력 최적화에 의한 디바이스 컨텐츠의 원격 액세스 및 운영
KR20190093324A (ko) 무선통신 설정 방법 및 디바이스

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170331

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20170830

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 29/12 20060101ALI20170824BHEP

Ipc: H04L 29/08 20060101AFI20170824BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200102

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015050879

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1258646

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200515

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200415

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200715

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200716

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200815

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200817

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20200923

Year of fee payment: 6

Ref country code: GB

Payment date: 20200923

Year of fee payment: 6

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1258646

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200715

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015050879

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20200921

Year of fee payment: 6

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

26N No opposition filed

Effective date: 20210118

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201002

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201002

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602015050879

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029080000

Ipc: H04L0065000000

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602015050879

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20211002

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200415

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211002

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220503

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211031