+

WO2006013511A1 - Detection de plusieurs interfaces reseau sur la meme liaison reseau - Google Patents

Detection de plusieurs interfaces reseau sur la meme liaison reseau Download PDF

Info

Publication number
WO2006013511A1
WO2006013511A1 PCT/IB2005/052432 IB2005052432W WO2006013511A1 WO 2006013511 A1 WO2006013511 A1 WO 2006013511A1 IB 2005052432 W IB2005052432 W IB 2005052432W WO 2006013511 A1 WO2006013511 A1 WO 2006013511A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
message
network
network interface
interface
Prior art date
Application number
PCT/IB2005/052432
Other languages
English (en)
Inventor
Jarno Guidi
Maarten P. Bodlaender
Alexander W. Heerink
Original Assignee
Koninklijke Philips Electronics N.V.
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 Koninklijke Philips Electronics N.V. filed Critical Koninklijke Philips Electronics N.V.
Publication of WO2006013511A1 publication Critical patent/WO2006013511A1/fr

Links

Classifications

    • 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/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/14—Multichannel or multilink protocols

Definitions

  • the present invention relates to a method for detecting if multiple network interfaces are present on the same network link.
  • the present invention also relates to a networked device for performing the method.
  • the present invention further relates to a computer program for performing the method.
  • networked devices are getting multiple network interfaces, for example a notebook with both a wireless and a wired network interface.
  • Many existing protocol stacks are optimized for or expect a single interface.
  • portable devices such as laptop computers, Personal Digital Assistants (PDA's), notebooks, etc.
  • PDA's Personal Digital Assistants
  • a network connection may change regularly.
  • Protocol stacks fail to operate correctly if the multiple interfaces are connected to the same network.
  • IP Link Local Addressing (LLA, or AutoIP in UPnP) and Link Local Multicast Name Resolution (LLMNR).
  • LPA IP Link Local Addressing
  • LLMNR Link Local Multicast Name Resolution
  • Another group includes protocols which employ broadcasts, for example UPnP discovery and Rendezvous (Apple). These protocols will in many cases send a particular message on all network interfaces of a device. If these are connected to the same network, this will cause duplication of messages, which may cause protocol failure and wastes bandwidth.
  • protocols will often use the first available network interface, even if more suitable ones are present and connected to the same network later.
  • the choice of an interface might not be optimal or even correct if the network topology changes, for example when two interfaces are no longer on the same network. It is therefore desirable to be able to manage multiple network interfaces of a device.
  • the article Mobile IP 2 12th IEEE International Symposium on Personal, Indoor and Mobile Radio Communication, PIMRC 2001, Proceedings, vol. 1, pp. A-88-92, describes a method for switching network traffic between various connection possibilities between a mobile device and a home agent.
  • the connection may be established using various network interfaces, such as Ethernet, Wireless LAN, or cellular.
  • the device detects when an option becomes available or stops being available, and switches the traffic to another, possibly to a more preferable, connection if this is advantageous or necessary.
  • the method described in the article requires modifications to existing protocols in order to work.
  • the above and other objects are fulfilled by providing a method for detecting whether two or more network interfaces of a device are on the same network link, the method comprising the steps of: - sending a message, M, from a first network interface, A, of the device on a link LA to a second network interface, B, of the device on a link LB, receiving a message, M 1 , at least on the second network interface, B, correlating the received message, M', and the previously sent message, M, determining whether the second network interface, B, is on link LA, based on said correlating step.
  • a networked device comprising: two or more network interfaces, means for sending a message, M, from a first network interface, A, of the device on a link LA to a second network interface, B, of the device on a link LB, means for receiving a message, M', at least on the second network interface, B, means for correlating the received message, M 1 , and the previously sent message, M, and for producing a corresponding output, and means for determining whether the second network interface, B, is on link LA, based on the produced output.
  • the present invention relates to a network comprising at least one device as defined above and at least one network link.
  • the network interfaces may, e.g., be 802.3, 802.11 , BT, UMTS, GPRS, etc.
  • the message, M may, e.g., be sent by means of multicasting or unicasting. Furthermore, the message, M', may be received by listening to multicasts or unicasts, by listening in promiscuous mode, etc. Preferably, messages, M, are sent periodically in order to , monitor the situation with respect to which network interfaces are on which link and whether or not one or more of them are on the same link.
  • the present invention makes it possible to determine whether or not two or more network interfaces of a device are on the same network link. Once it is established that this is the case, one of the links can be chosen for network traffic, and the traffic may optionally be switched to that network interface. This will be further described below. It is an advantage that it is positively established that the network interfaces are actually on the same network link before a specific network interface is chosen and network traffic is switched to that interface, because in case two network interfaces are not on the same network link they may not have access to the same set of network nodes, and it may therefore be problematic to switch the network traffic between the interfaces. It is therefore a significant advantage that the present invention provides a method for determining whether or not two or more network interfaces of a device are on the same network link.
  • the correlating step comprises determining whether message, M', has crossed a level-3 router. In this embodiment it is determined that the second network interface, B, is on link LA if message, M', has not crossed a level-3 router.
  • the second network interface, B is on link LA if message, M', has not crossed a level-3 router.
  • TTL time-to-live
  • the correlating step comprises comparing the received message, M', with the previously sent message, M.
  • network interface, B must be on the same network link as network interface, A, i.e. link LA. This is a very simple way of determining whether or not two network interfaces are on the same link, and it requires no modification to the protocol used for sending the message, M.
  • the method can easily be extended to determine whether or not more network interfaces are on said link by simply comparing the message received by each network interface of the device to the previously sent message, M.
  • the correlating step may comprise checking for specific differences between the messages M and M'.
  • the received message, M 1 may comprise the Media Access Control (MAC) address of the gateway.
  • MAC Media Access Control
  • the correlating step may comprise any other suitable kind of correlation between the received message, M', and the previously sent message, M, such as checking if the payload and/or the TTL of M' and M is the same. This may, e.g., be useful in case the sent message, M, is a routed message, such as an User Datagram Protocol (UDP) packet.
  • UDP User Datagram Protocol
  • the sent message, M may be an Address Resolution Protocol (ARP) message.
  • ARP Address Resolution Protocol
  • the correlation step comprises determining whether message, M', has crossed a level-3 router, because ARP messages are not forwarded by level- 3 routers. Therefore, in this case, if a message, M', is actually received on the second network interface, B, it cannot possibly have crossed a level-3 router, and it can therefore easily be determined that network interface, B, is on link LA.
  • ARP Address Resolution Protocol
  • the method may further comprise the steps of: in case it is determined that two or more network interfaces are on the same link, LA, selecting one of said network interfaces based on one or more predetermined criteria, and adapting protocol behavior, so as to
  • the method may comprise the steps of: in case it is determined that two or more network interfaces which were previously on the same link are no longer on the same link, adapting protocol behavior, so as to
  • the protocol normally recommends to have the same IP address on all network interfaces of a device. In case two or more interfaces are on the same link, the IP addresses will always conflict, and the protocol fails. According to the present invention, the protocol behavior will in this case be adapted in such a way that, either one of the interfaces is not configured with an IP address or the recommendation of having the same IP address is not followed.
  • the protocol In case of LLMNR and Rendezvous the protocol normally resolves host names to IP addresses and checks for host name uniqueness. As it is the case for LLA, the unique requirement fails if two or more network interfaces are on the same link. According to the present invention, the protocol behavior will in this case be adapted in such a way that the device is aware that its name announcement will be received by itself on an interface which is different from the one that sent it, but that this does not constitute a name conflict. Hence, LLMNR conflict resolution will be improved. 3. In case of a protocol employing broadcasts, e.g. UPnP discovery, the protocol will in many cases send the same message on all interfaces. This will cause duplication of messages which in turn can cause protocol failure and wastes bandwidth. According to the present invention, the protocol behavior will in this case be adapted in such a way that multicast queries are sent on only one interface per link, and in such a way that responses to multicast queries are only sent from one interface per link.
  • protocol behavior is in this case adapted in such a way that the protocol reconsiders the choice of interface when changes in the link topology are detected.
  • the one or more criteria may be selected from the group consisting of: network speed, operational costs, signal stability, signal strength, static priority configured by user, static priority configured by manufacturer. It may, alternatively, be any other suitable criteria.
  • One way of managing this is to simply prioritize the network interfaces and at any time select the highest ranking network interface which is available. For example, when a wired and a wireless interface are available, the wired interface is normally faster, more reliable and uses less power. It will therefore normally have a higher priority than the wireless interface. Whenever it is detected that both interfaces are on the same link, the wired interface would therefore be selected.
  • the ranking may, of course, involve more than two interfaces.
  • the method of the present invention may advantageously be performed by a computer program.
  • the computer program may, e.g., be running in a general purpose computer, be stored on a carrier, and/or be transferred over a network, etc.
  • Fig. 1 is a flow chart illustrating an embodiment of the method according to the present invention
  • Fig. 2 is a flow chart describing an embodiment of the present invention using ARP messages
  • Fig. 3 shows a networked device according to an embodiment of the present invention.
  • Fig. 1 is a flow chart which illustrates an embodiment of the method according to the present invention.
  • the method starts at 1.
  • a message Ml is sent from interface IFl on link Ll to interface IF2 on link L2.
  • Interfaces IFl and IF2 are both on the same device.
  • message M2 is received at interface IF2.
  • next step 4 it is checked in next step 4 whether or not M2 correlates with Ml. If this is not the case, the process is returned to the previous step 3 to receive and check a new message, possibly sent by another interface. If it is found at step 4 that M2 correlates with Ml then the next step 5 is to check whether or not M2 has crossed one or more level-3 routers.
  • next step 6 it is determined that link Ll is different from link L2, and that interface IFl and interface IF2 are consequently not on the same network link. If, on the other hand, it is found at step 5 that M2 has not crossed one or more level-3 routers, then the next step 7 is to determine that link Ll and link L2 are identical, and that interface IFl and interface IF2 are consequently on the same link. After the final steps 6 or 7 the method reaches an end 8.
  • Fig. 2 is a flow chart describing an embodiment of the method according to the present invention in which ARP messages are employed.
  • the method starts at 11.
  • an ARP message Ml is broadcast from interface IFl on link Ll.
  • the ARP message Ml may, e.g., be an ARP request containing the IP address of a second interface IF2, the second interface IF2 being on link L2.
  • a timeout Tl for the message Ml is set in order to allow the process to be ended within a finite time.
  • Tl timeout
  • the next step 15 is to determine that link Ll is different from link L2, and that interface IFl and interface IF2 are consequently not on the same network link. Thereby the process reaches an end 19 after the expiry of Tl, even if the message for some reason does not reach the second interface IF2.
  • step 14 Tl has not yet expired, in the next step 16 message M2 is received at the second interface IF2.
  • the subsequent step 17 is to compare message M2 into the previously sent message Ml. In particular, it is checked if the payload contains the IP address of IF2 and if the MAC address is that of IFl. In case this comparison 17 reveals that M2 is equal to Ml, then it is determined at the next step 18 that link Ll is equal to link L2, and that interface IFl and interface IF2 are consequently on the same network link. After this step 18, the method reaches the end 19. On the other hand, in case the comparison step 17 reveals that M2 is different from Ml, then the process returns to the step 14 in which it is investigated whether or not the timeout Tl has expired.
  • FIG. 3 shows a networked device 20 according to an embodiment of the present invention.
  • the networked device 20 comprises two network interfaces, an interface A 21, connected to a network link LA 22, and an interface B 23, connected to a network link LB 24.
  • the networked device 20 furthermore comprises a processor unit 25, for controlling the network interfaces 21 and 23, and thereto connected to these interfaces via connections 26 and 27.
  • the processor unit 25 is furthermore coupled via a connection 28 to a memory 29.
  • the connections 26, 27 and 28 are implemented as one or more data and/or control busses.
  • the memory 29 comprises a RAM memory 30 and a program memory 31.
  • the program memory 31 stores a computer program 32 being adapted for performing the steps of a method according to an embodiment of the present invention when being executed under the control of the processor unit 25.
  • the networked device 20 under the control of processor unit 25 executing computer program 32 is capable of sending a message M from network interface A 21 on link LA 22 to network interface B 23 on link LB 24, receiving a message M' at network interface B 23, correlating the received message M' and the previously sent message M for producing a corresponding output, and determining whether the network interface B 23 is on link LA 22, based on the produced output.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé permettant de déterminer si au moins deux interfaces réseau d'un dispositif se trouvent sur la même liaison réseau. Ce procédé consiste : à envoyer un message M depuis une interface ; à recevoir un message M' sur une autre interface ; et à corréler les messages envoyé et reçu. De manière avantageuse, des messages de protocole de résolution d'adresse (ARP) sont utilisés. Ledit procédé consiste de préférence à vérifier si des routeurs de niveau 3 ont été traversés par le message M'. Si deux interfaces se trouvent sur la même liaison, le comportement de protocole est adapté de manière appropriée pour sélectionner une interface préférée.
PCT/IB2005/052432 2004-07-30 2005-07-20 Detection de plusieurs interfaces reseau sur la meme liaison reseau WO2006013511A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP04103686.4 2004-07-30
EP04103686 2004-07-30

Publications (1)

Publication Number Publication Date
WO2006013511A1 true WO2006013511A1 (fr) 2006-02-09

Family

ID=35207796

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2005/052432 WO2006013511A1 (fr) 2004-07-30 2005-07-20 Detection de plusieurs interfaces reseau sur la meme liaison reseau

Country Status (1)

Country Link
WO (1) WO2006013511A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007033059A2 (fr) * 2005-09-12 2007-03-22 Cassatt Corporation Détection d'interfaces réseau capable de lier les canaux

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"LOAD BALANCING FOR MULTIPLE INTERFACES FOR TRANSMISSION CONTROL PROTOCOL/INTERNET PROTOCOL FOR VM/MVS", IBM TECHNICAL DISCLOSURE BULLETIN, IBM CORP. NEW YORK, US, vol. 38, no. 9, 1 September 1995 (1995-09-01), pages 7 - 9, XP000540166, ISSN: 0018-8689 *
ANONYMOUS: "Zero Message Overhead Local Link Detection Mechanism", IP.COM JOURNAL, IP.COM INC., WEST HENRIETTA, NY, US, 18 March 2004 (2004-03-18), XP013014728, ISSN: 1533-0001 *
COLTUN SIARA SYSTEMS D FERGUSON JUNIPER NETWORKS J MOY SYCAMORE NETWORKS R: "OSPF for IPv6", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, vol. ospf, no. 7, October 1999 (1999-10-01), XP015024757, ISSN: 0000-0004 *
ERNST WIDE AT KEIO UNIVERSITY N MONTAVONT LSIIT-ULP R WAKIKAWA KEIO UNIVERSITY E PAIK SEOUL NATIONAL UNIVERSITY C NG PANASONIC SIN: "Goals and Benefits of Multihoming", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 9 February 2004 (2004-02-09), XP015032830, ISSN: 0000-0004 *
STUART CHESHIRE APPLE COMPUTER BERNARD ABOBA MICROSOFT CORPORATION ERIK GUTTMAN SUN MICROSYSTEMS: "Dynamic Configuration of IPv4 Link-Local Addresses", IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, vol. zeroconf, no. 17, 8 July 2004 (2004-07-08), XP015030114, ISSN: 0000-0004 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007033059A2 (fr) * 2005-09-12 2007-03-22 Cassatt Corporation Détection d'interfaces réseau capable de lier les canaux
WO2007033059A3 (fr) * 2005-09-12 2007-06-07 Cassatt Corp Détection d'interfaces réseau capable de lier les canaux
US7609642B2 (en) 2005-09-12 2009-10-27 Computer Associates Think, Inc, Detecting network interfaces capable of channel bonding

Similar Documents

Publication Publication Date Title
US8103784B2 (en) Communication device and communication control method using efficient echonet address determination scheme
US7181503B2 (en) Apparatus and method of searching for DNS server in outernet
US7069312B2 (en) Network location signature for disambiguating multicast messages in dual-IP stack and/or multi-homed network environments
US20040071148A1 (en) Information device, gateway device and control method
EP1107508A1 (fr) Système, méthode et produit logiciel pour la transmission de messages de diffusion
US20050220137A1 (en) Method for the discovery of devices connected to an IP network and device to carry out said method
JPH11355322A (ja) 無線端末装置をデ―タ伝送ネットワ―クと結合する方法及び無線端末装置
US7739375B2 (en) System and method for UPnP discovery advertisement byebye by proxy
CN102025799A (zh) 一种发现及自动配置设备的ip地址的方法
WO2007107624A2 (fr) Procede de resolution d'adresses dans un systeme de communication
WO2001041378A1 (fr) Diffusion comme mecanisme de declenchement pour determiner un routage
WO2007033059A2 (fr) Détection d'interfaces réseau capable de lier les canaux
AU2005209827A1 (en) Method and system for optimization of data transfer between networked devices
WO2013186969A1 (fr) Dispositif de détection d'informations de communication et procédé de détection d'informations de communication
WO2003055180A1 (fr) Detection d'adresse dupliquee dans un reseau de communications
CN100493073C (zh) 不同链路层隔离域的邻居发现实现方法
US7480250B2 (en) Apparatus and method for establishing network
US20050198219A1 (en) Unicast messaging for waking up sleeping devices
EP3866421B1 (fr) Procédé d'accès basé sur le protocole profinet dans un réseau sdn industriel
KR101548959B1 (ko) 패킷 통신 시스템에서 네트워크 주소 설정을 위한 장치 및방법
WO2006013511A1 (fr) Detection de plusieurs interfaces reseau sur la meme liaison reseau
JP4527523B2 (ja) サーバ選択方法およびサーバ選択方式およびサーバおよびクライアント端末
US20050102369A1 (en) Network connection device, network system and method for avoiding duplication of proxy function
KR101415978B1 (ko) 가상랜을 이용한 데이터전송장치에서의 서브넷 디에이치씨피 서버 설정 및 운영 시스템 및 방법
CN101223736A (zh) 网络中发现的方法和设备

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载