WO2001086908A1 - Procede d'allocation automatique d'adresses ip - Google Patents
Procede d'allocation automatique d'adresses ip Download PDFInfo
- Publication number
- WO2001086908A1 WO2001086908A1 PCT/EP2000/004147 EP0004147W WO0186908A1 WO 2001086908 A1 WO2001086908 A1 WO 2001086908A1 EP 0004147 W EP0004147 W EP 0004147W WO 0186908 A1 WO0186908 A1 WO 0186908A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- server
- network element
- interfaces
- addresses
- Prior art date
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/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/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- 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/5061—Pools of 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/50—Address allocation
- H04L61/5076—Update or notification mechanisms, e.g. DynDNS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/677—Multiple interfaces, e.g. multihomed nodes
Definitions
- the invention relates to a method for an automatic assignment of IP (internet protocol) addresses to the interfaces of network elements," ' especially routers, having at least two interfaces, by one of which they are newly connected, either directly or via other network elements, to a server of an IP based network.
- IP internet protocol
- the invention equally relates to an IP (internet protocol) network comprising at least one server and network elements with more than one interface. It is understood that an IP address may be an IP host address, identifying one dedicated IP host, as well as an IP network address.
- IP internet protocol
- a host constitutes the access for a user and has typically one interface, which connects the host to a logical IP subnetwork (LIS), i.e. the host is a member of the LIS.
- LIS logical IP subnetwork
- a member of a LIS can send IP packets directly to all other members of the same LIS. If a network element wants to communicate with other network element and the two network elements are not members of a same LIS, then there must be one or more routers between the two LISs.
- a router is a network element, which forwards IP packets between different LISs.
- a router has more than one physical interface, because the LISs typically represent also physically separated networks.
- the physical networks connected by the routers represent subnetworks of the whole IP network, and normally each subnetwork has its own network address.
- Every host in an IP based network is assigned an IP address.
- the address format is comprised of a network address and a local or host address.
- the network address identifies the IP subnetwork to which the host is attached.
- the local address is a unique local address within the IP subnetwork.
- two hosts on the same IP subnetwork can send packets directly to each other.
- Two hosts on different IP subnetworks cannot send IP packets directly to each other, instead the packets have to go via the router connecting the two subnetworks.
- there can be provided an IP address for every interface the IP address being composed again of the network address of the subnetwork, to which the interface belongs, and of a local address identifying the interface in the subnetwork.
- All interfaces with a dedicated IP address are numbered interfaces.
- the assignment of a dedicated IP address is possible but not necessary, i.e. these interfaces may be numbered or unnumbered.
- an IP network has a large number of hosts and the number of hosts in each subnetwork can change. Equally, the number of other network elements can vary, for example, the number of routers when new subnetworks are to be added. In addition, the available IP address space is usually limited and should be used efficiently. In order to take such developments into account, the IP network needs human intelligence when it comes to planning.
- DHCP Dynamic Host Configuration Protocol
- hosts with information from DHCP servers, which maintain a database with IP addresses.
- a new host searches a DHCP server and requests an IP address.
- the router In case there is a router between the host and the DHCP server, the router must have DHCP relay functionality. This method reduces the work necessary to administer an IP network. It is not known, however, how to facilitate the assignment of IP addresses and IP network addresses to new network elements with more than one interface.
- IP internet protocol
- the invention proceeds from the idea that, if the IP network has some known restrictions, the automatic assignment of IP addresses to network elements with more than one interface is essentially facilitated.
- the invention is applicable in networks that do not require hierarchical addressing, e.g. because they are rather small. Moreover, the number of network elements has to be limited and known.
- the method and the IP network of the invention decrease the required amount of planning in an IP based network to a minimum, because it enables the server to automatically choose and reserve IP addresses for a newly connected network element upon request by the network element. Since the distribution of the IP addresses can be carried out efficiently by the server, the address space for the addresses can be set to the minimum needed for the defined maximum number of interfaces.
- the new network element can be connected directly to the server.
- the new network element in particular routers, can be connected to the server via other network elements with also at least two interfaces.
- the other network elements comprise a relay function for the address reservation protocol, the relay function knowing the location, especially the IP address, of the server. Therefore, the other network elements are able to forward the configuration request from the new network element and the response from the server correctly.
- the two alternatives provide in combination a method suitable for an expansion at any location of the existing IP based network.
- the new network element with more than one interface, in particular the router may start its relay functionality after one first interface is provided with an IP address.
- the IP address can be dedicated to an interface in case numbered links are used. If numbered links are used, the IP address is not tied to any interface in particular.
- the routers of the network should run a routing protocol, in particular an Open Shortest Path First (OSPF) routing protocol .
- OSPF Open Shortest Path First
- the new network element comprises interfaces for numbered links, in particular for Logical IP Subnetworks (LIS)
- LIS Logical IP Subnetworks
- the new network element requests an IP network address for each of those interfaces from the server. For the interfaces, that are already connected to existing routers, there is no need for such a request.
- each network element with more than one interface comprises a client for checking if its interfaces are connected, directly or via another network element, to the server and for sending a configuration request to the server.
- Those network elements further all comprise a relay for forwarding configuration requests coming in via one of the interfaces via another one of the interfaces.
- the server of the network comprises means for choosing and reserving IP addresses for a network element newly included in the network in response to a received configuration request from this new network element.
- the IP network uses the Dynamic Host Configuration Protocol (DHCP) for assigning IP addresses to the interfaces of new network elements, especially to IP hosts.
- DHCP Dynamic Host Configuration Protocol
- the use of the DHCP may be in addition to the claimed methods. This is in particular applicable, when the interface to the existing router is numbered.
- the server of the IP network of the invention has access to a database, especially a database maintained by the server, indicating which IP addresses are allocated and which IP addresses are available.
- the server immediately knows, which addresses can be chosen and reserved for new network elements. If a network element is removed from the IP network, the IP addresses of the concerned interfaces should be identified as being available again for future allocations.
- the at least one server of the network moreover has access to a database, in particular a DNS (domain name service) database, in which the distributed IP addresses are put into relation with a generic name of the element to which the IP address is assigned. This way, the different interfaces can be addressed easily by a generic name.
- DNS domain name service
- the network is made up of point-to-point links between the network elements.
- the IP network according to the invention is preferably an IP over ATM network. Still, other suitable networks can used as well.
- Fig. 1 shows an ATM network based on IP to which the method of the invention is applicable
- Fig. 2 shows a part of an IP network with newly connected components
- Fig. 3 shows a method according to the invention for one of the newly connected components of Fig. 2;
- Fig. 4 shows a preferred extension of the method of Fig. 3.
- the components of the network are a server S, and, as network elements, a plurality of routers R,A and a plurality of hosts H.
- Each host H has one interface, each router at least two interfaces.
- the server S is located at a central place and connected to one of the routers R. All routers R,A that are not connected directly to the server S are connected to the server S via other routers R. Router A with interfaces I a to Id has been newly connected to the network.
- the network elements are connected either by a point-to- point link or by a Local Area Network (LAN) L, the IP network comprising several of such subnetworks L.
- LAN Local Area Network
- IP network address forms part of each IP address of the interfaces belonging to the respective subnetwork.
- numbered point-to-point links are used between routers and the LANs have several hosts, then the operator may not want to assign as large IP networks for the point-to-point links as for LANs.
- the operator may in that case define two subnetwork pools: small subnetworks for point-to-point links and larger subnetworks for LANs.
- the router requesting a new IP network from the server would then have to know whether it requests a LAN subnet or a point-to-point subnet for an interface. To simplify the server configuration it is therefore preferred to use unnumbered links between routers (i.e. only one pool) . On the other hand, if the LANs have one or two hosts, then the subnet size in a LAN and a numbered point-to-point link could be same and one pool would be enough.
- the server S is configured accordingly with a pool of subnetworks, all being able to hold the desired number of connected network elements. Because the server has to know whether a router requests a new IP network for a LAN subnetwork or a point-to-point subnet it is simpler to use only unnumbered links between routers .
- Every network element R,A,H there is included a client functionality.
- the client of a network element newly connected to the existing network is able to request IP addresses for its interfaces.
- the request is either sent to a router R or a server S connected by a point-to-point link to the requesting network element or broadcast to every node connected to the same subnetwork, depending on the connection of the new network element.
- the request is received by all directly connected network elements.
- Each client of a network has an unique identifier (node ID) , which enables other elements to identify each client individually. With each request, the node ID is send, such that the request can be associated with the requesting client.
- a relay function is integrated in each network element with more than one interface, i.e. especially in routers. Such a functionality is needed, whenever the client of a network element cannot reach the server S directly.
- the task of the relay is to listen to all interfaces of its network element, and to take note if there are incoming requests from a connected network element. A received request is directly addressed and sent to one or more servers. The relay may add additional information to the request in order to enable the server S to send the response to the client.
- the server S receives a request from a client of a new network element, either directly or via the relay functionality of another network element, chooses an address, reserves it and sends it to the requesting client.
- the server also updates a DNS database to which it has access, so that the clients can easily be addressed by name.
- a network element has a point-to-point connection to another network element, an unnumbered link can be used. This means that the link does not have an IP network address and therefore the interfaces do not have to have IP addresses. If the connection between network elements is not a point-to-point connection, but for example a LAN with hosts, a network address is needed for the link and the interfaces of the routers have to have IP addresses.
- the configuration of the new router A depends on the kind of links between the routers.
- the interfaces Ia, lb and Id of the new router A can be configured to be unnumbered and interface Ic is configured as LIS interface. If it is known that the server can be found only behind an unnumbered link, the new router can try to find the server sending "server discovery" messages to the unnumbered links Ia, lb, Id, an answer arriving via interface Ia. The router A can then requests IP host addresses or IP network addresses from the server S, depending on the other interface types. The server S can provide any free address from a pool of available addresses. Alternatively, the server S can be configured to provide dedicated addresses according to a node ID in the request message.
- the new router A will only request a network address for interface Ic. Other addresses are not necessary, because the router A can use the IP address in interface Ic.
- the new router A configures the received IP addresses according to the answer from the server S and starts the relay function, which will serve other network elements below this router A.
- the relay function must add to the relayed requests information, which identifies the unnumbered interface from where the request came.
- the answer from the server S should include the same information so that the relay can forward the answer to the correct client.
- the router uses a conventional method (DHCP) to obtain an IP address for the interface that leads towards the server. To this end, the router tries all interfaces Ia,Ib,Ic,Id and the DHCP server answers via interface Ia. Thereafter, the new router A can start reserving network addresses for the other interfaces Ib,Ic,Id. Preferably, a new router A always requests network addresses for the same size of networks for all of the interfaces Ib,Ic,Id. This way, the server does not have to keep pools of different sizes of network.
- DHCP conventional method
- the router A When the router A has received the network addresses for the remaining interfaces, it configures the addresses to the interfaces and start its relay function.
- the relay function can use the same method to identify the interface of requests and answers as a DHCP relay function, because all links have IP network addresses .
- Figure 2 shows a part of a network like the one in figure 1, comprising a server S, a router R, a new router A and a host H.
- the server S is provided with several configured interfaces, the only one relevant in this example being referred to in Figure 2 as II.
- the server S has moreover access to a DNS database, not shown in the figure, in which reserved IP addresses are assigned to the name of the client belonging to the host for which they are reserved.
- the router R has at least two configured interfaces 12 and 13 and a relay function.
- the router A also comprises at least two interfaces 14, 15.
- the host H is provided with only one interface 16.
- the router A and the host H both have a client C functionality.
- the interfaces 14, 15, 16 of router A and host H are not configured.
- the shown interface II of the server S is connected to interface 12 of the router R.
- the ' router R is connected by its interface 13 to interface 14 of the router A.
- Interface 15 of the router A is connected to the only interface 16 of the host H.
- the router A has just been connected to the router R of the existing IP network and was switched on. Just the same, the host H has newly been connected to the router A.
- FIG 3 schematically illustrates the steps of the method of the invention applied to the situation depicted in Figure 2.
- Each component of Figure 2 is represented by a vertical dotted line. From left to right, the vertical lines are assigned to the host H, the network element A, the router R and the server S. The horizontal arrows between the vertical lines represent the messages exchanged between the different components.
- the client functionality C of the network element A checks, which of its interfaces 14,15 are useable. Since the network is an ATM network, the presence of a cell sync on interface 14 indicates that there is another element at the end of the link. Moreover, the client functionality C checks, whether the elements reachable via interfaces 14 are configured or unconfigured by using an address resolution message (e.g. InATMARP) to evaluate the state.
- An address resolution message e.g. InATMARP
- the signalling between network element A and host H on the one hand and network element A and router R on the other hand necessary for the checking is indicated in Figures 2 and 3 with the numbers 1 and 2 representing a first step 1 and a second step 2 carried out during the described procedure.
- Interface 13 of the router R is recognised by network element A via interface 14 as being configured, interface 16 of the host H is recognised by the network element A via interface 15 as being not configured.
- the client functionality C of the network element A sends a configuration request via interface 14 to interface 13 of the router R (step 3) .
- a relay RR running on the router R receives the request and forwards it to the server S including the IP address of the router's interface 13 (step 4).
- the server S chooses an IP address that can be assigned to the interface 14 of the new network element A.
- One part of the address is necessarily the address of the subnetwork of the router's R interface 13 that was added by the relay RR of router R to the forwarded configuration request.
- the other part is one of a defined number of addresses provided for the particular subnetwork and which is not yet in use.
- the server S maintains for this purpose a database in which is stored for each subnetwork which addresses are allocated and which are still available. The database equally provides information on which subnetworks are allocated and which are still available.
- the server S outputs a response including the chosen IP address via its interface II (step 5) .
- the server may include other configuration parameters for the network element A in the response.
- the server S updates the DNS database so that the new network element A can be addressed by name.
- the relay RR of the router R receives and forwards the response of the server S to the network element A via the interfaces 12 and 13 (step 6) . Also at this point, additional configuration data relevant for the particular subnetwork may be included in the response to the new network element A.
- the new network element A receives the response and applies the IP address included in the response on the used interface 14. In case other parameters had been included in the server's S response, they are also utilised for configuration.
- the new network element A can now start its relay functionality RA, as depicted in Figure 4.
- the network element A checks, if one of its interfaces 15 currently not supplied with an IP address could be in usage. It recognises or knows that interface 15 (steps 7 and 8) is numbered, but the subnet address is not yet allocated.
- a configuration request for interface 15 is therefore sent via the local relay RA of the network element A (step 9) and the connected network N, which may consist of a plurality of routers R (step 10) to the server S, the routers R not being shown in this figure.
- the configuration request indicates that a new subnetwork has to be used.
- the server S first chooses and reserves an address for a new subnetwork that is still available according to a consultation of the proper database.
- the server S chooses and reserves an IP address for interface 15, composed of the address of the new subnetwork and of a part identifying the interface 16 within the new subnetwork and sends it back via the network N and the relay RA of network element A to the interface 15 (step 11) .
- the IP address chosen by the server S is applied to interface 15, this interface 15 being configured as well thereupon.
- interface 16 of the host H still has to be configured.
- the host H recognises by a check with an InATMARP message that interface 15 of the network element A is configured and sends a configuration request to the server S via the relay RA of the network element A.
- the relay RA of the network element A includes the address of the subnetwork of its interface 15 in the request.
- the further proceeding is the same as described for the configuration of the first interface 14 of the network element A.
- a documentation tool In order to enable the operator to watch over the address usage in the network, there is provided a documentation tool.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU44047/00A AU4404700A (en) | 2000-05-10 | 2000-05-10 | Method for an automatic allocation of ip addresses |
PCT/EP2000/004147 WO2001086908A1 (fr) | 2000-05-10 | 2000-05-10 | Procede d'allocation automatique d'adresses ip |
EP00925271A EP1192777A1 (fr) | 2000-05-10 | 2000-05-10 | Procede d'allocation automatique d'adresses ip |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2000/004147 WO2001086908A1 (fr) | 2000-05-10 | 2000-05-10 | Procede d'allocation automatique d'adresses ip |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2001086908A1 true WO2001086908A1 (fr) | 2001-11-15 |
Family
ID=8163934
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2000/004147 WO2001086908A1 (fr) | 2000-05-10 | 2000-05-10 | Procede d'allocation automatique d'adresses ip |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1192777A1 (fr) |
AU (1) | AU4404700A (fr) |
WO (1) | WO2001086908A1 (fr) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002009451A2 (fr) * | 2000-07-21 | 2002-01-31 | Telefonaktiebolaget L M Ericsson (Publ) | Terminal mobile et procede pour assurer une connexion de reseau a reseau |
WO2012139283A1 (fr) * | 2011-04-12 | 2012-10-18 | 华为技术有限公司 | Procédé et appareil pour allocation d'adresse |
WO2015044565A1 (fr) * | 2013-09-30 | 2015-04-02 | Orange | Procédés de configuration et de gestion d'un réseau ip, dispositifs et programmes d'ordinateur correspondants |
WO2015067827A1 (fr) * | 2013-11-06 | 2015-05-14 | Telefonica, S.A. | Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur |
-
2000
- 2000-05-10 AU AU44047/00A patent/AU4404700A/en not_active Abandoned
- 2000-05-10 EP EP00925271A patent/EP1192777A1/fr not_active Withdrawn
- 2000-05-10 WO PCT/EP2000/004147 patent/WO2001086908A1/fr not_active Application Discontinuation
Non-Patent Citations (6)
Title |
---|
CHUL-JIN PARK ET AL: "The improvement for integrity between DHCP and DNS", PROCEEDINGS. HIGH PERFORMANCE COMPUTING ON THE INFORMATION SUPERHIGHWAY,XX,XX, 28 April 1997 (1997-04-28), pages 511 - 516, XP002110636 * |
D.E.COMER: "Internetworking with TCP/IP, Vol I: Principles, Protocols and Architecture, 3rd edition.", 1995, PRENTICE-HALL, US, XP002164348 * |
GUARENE E ET AL: "IP AND ATM INTEGRATION PERSPECTIVES", IEEE COMMUNICATIONS MAGAZINE,IEEE SERVICE CENTER. PISCATAWAY, N.J,US, vol. 36, no. 1, 1988, pages 74 - 80, XP000739155, ISSN: 0163-6804 * |
PERKINS C E ET AL: "USING DHCP WITH COMPUTERS THAT MOVE", WIRELESS NETWORKS,ACM,US, vol. 1, no. 3, 1 October 1995 (1995-10-01), pages 341 - 353, XP000538245, ISSN: 1022-0038 * |
PERLMAN R: "A COMPARISON BETWEEN TWO ROUTING PROTOCOLS: OSPF AND IS-IS", IEEE NETWORK,IEEE INC. NEW YORK,US, vol. 5, no. 5, 1 September 1991 (1991-09-01), pages 18 - 24, XP000248469, ISSN: 0890-8044 * |
R. DROMS: "RFC 1541, Request For Comments, Dynamic Host Configuration Protocol.", RETRIEVED FROM THE INTERNET, AT WWW.IETF.ORG, XP002164347 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002009451A2 (fr) * | 2000-07-21 | 2002-01-31 | Telefonaktiebolaget L M Ericsson (Publ) | Terminal mobile et procede pour assurer une connexion de reseau a reseau |
WO2002009451A3 (fr) * | 2000-07-21 | 2002-10-31 | Ericsson Telefon Ab L M | Terminal mobile et procede pour assurer une connexion de reseau a reseau |
US6763012B1 (en) | 2000-07-21 | 2004-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Mobile terminal and method of providing a network-to-network connection |
WO2012139283A1 (fr) * | 2011-04-12 | 2012-10-18 | 华为技术有限公司 | Procédé et appareil pour allocation d'adresse |
WO2015044565A1 (fr) * | 2013-09-30 | 2015-04-02 | Orange | Procédés de configuration et de gestion d'un réseau ip, dispositifs et programmes d'ordinateur correspondants |
FR3011424A1 (fr) * | 2013-09-30 | 2015-04-03 | Orange | Procedes de configuration et de gestion d'un reseau ip, dispositifs et programmes d'ordinateur correspondants. |
US10686752B2 (en) | 2013-09-30 | 2020-06-16 | Orange | Methods for configuring and managing an IP network, corresponding devices and computer programs |
WO2015067827A1 (fr) * | 2013-11-06 | 2015-05-14 | Telefonica, S.A. | Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur |
Also Published As
Publication number | Publication date |
---|---|
EP1192777A1 (fr) | 2002-04-03 |
AU4404700A (en) | 2001-11-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7046666B1 (en) | Method and apparatus for communicating between divergent networks using media access control communications | |
US6697360B1 (en) | Method and apparatus for auto-configuring layer three intermediate computer network devices | |
US7483396B2 (en) | Method for assigning an IP address to a device | |
US8103784B2 (en) | Communication device and communication control method using efficient echonet address determination scheme | |
US7152099B1 (en) | Friend configuration and method for network devices | |
CN101534329B (zh) | 一种ip地址分配方法及系统 | |
EP1443693B1 (fr) | Procede de configuration d'un canal d'administration fonde sur un canal ipoa | |
US20050190775A1 (en) | System and method for establishing service access relations | |
US20090193103A1 (en) | Method of and System for Support of User Devices Roaming Between Routing Realms by a Single Network Server | |
US20030172170A1 (en) | Providing multiple ISP access to devices behind NAT | |
JP2001257720A (ja) | Dnsサーバ、dhcpサーバ、端末および通信システム | |
CN101141372A (zh) | 接入设备中用于管理路由信息和数据转发的方法及装置 | |
WO1997048210A1 (fr) | Affectation d'une adresse logique ip dans un reseau local mta | |
CN110365557B (zh) | 一种网络互连的方法及装置 | |
US20140317296A1 (en) | Allocating internet protocol (ip) addresses to nodes in communications networks which use integrated is-is | |
CN100525318C (zh) | 通过接口标识符分配网络标识符的改进方法 | |
CN101600001A (zh) | 基于动态主机分配协议的配置信息的获取方法和装置 | |
JP3394727B2 (ja) | ネットワーク間通信方法及びその装置 | |
RU2275756C2 (ru) | Способ автоматического получения ip адреса для устройства | |
US20060193330A1 (en) | Communication apparatus, router apparatus, communication method and computer program product | |
US20040114590A1 (en) | Packet switching networks | |
JP2008502227A (ja) | ドメインに左右されるプレフィックス割当て方法および装置 | |
US7085836B1 (en) | System and method for automatic private IP address selection | |
WO2001086908A1 (fr) | Procede d'allocation automatique d'adresses ip | |
CN108632173B (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 BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2000925271 Country of ref document: EP |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWP | Wipo information: published in national office |
Ref document number: 2000925271 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10030609 Country of ref document: US |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2000925271 Country of ref document: EP |