WO2009018658A1 - Dispositif, système et procédé pour le provisioning ipv4 automatique dans un réseau local raccordé à un réseau ipv6 - Google Patents

Dispositif, système et procédé pour le provisioning ipv4 automatique dans un réseau local raccordé à un réseau ipv6 Download PDF

Info

Publication number
WO2009018658A1
WO2009018658A1 PCT/CA2008/001417 CA2008001417W WO2009018658A1 WO 2009018658 A1 WO2009018658 A1 WO 2009018658A1 CA 2008001417 W CA2008001417 W CA 2008001417W WO 2009018658 A1 WO2009018658 A1 WO 2009018658A1
Authority
WO
WIPO (PCT)
Prior art keywords
ipv4
ipv6
network
protocol
tunneling
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.)
Ceased
Application number
PCT/CA2008/001417
Other languages
English (en)
Inventor
Eric Melin
Mikael Lind
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.)
Hexago Inc
Original Assignee
Hexago Inc
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 Hexago Inc filed Critical Hexago Inc
Publication of WO2009018658A1 publication Critical patent/WO2009018658A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling

Definitions

  • IPv4 is already deployed in most existing IP based infrastructures, and provides access to both the Internet and to private IP networks (such as a corporate network). Success in the deployment of the IPv4 protocol has lead to rapid exhaustion of the pool of available IPv4 addresses.
  • IPv6 In order to address the above drawbacks, IPv6 was developed. In particular, the IPv6 protocol has been designed to address those problems associated with the exhaustion of the IPv4 address space. With an almost unlimited pool of IPv6 addresses (public by nature), each user (and even each device at home, in a car, etc.), can be allocated a unique IPv6 address. This significantly simplifies the deployment of services based on the peer to peer paradigm which as a result can be deployed at a lower cost than with IPv4.
  • IPv4 enabled clients interact with a central server via an IPv6 only network in order to negotiate the particular properties of the tunnel and will be accorded a tunnel end-point.
  • This tunnel end-point can be the client itself (the client must then be enabled for IPv4-in-IPv6 tunneling), or a dedicated default router implementing IPv4-in-IPv6 tunneling (this router may then serve several clients).
  • This solution is typically deployed by installing dedicated software for tunnel negotiation and setup on each client. However, this solution is not always scalable, and it is necessary to upgrade the software on each client in order to provide them with this IPv4-in- IPv6 tunneling capability.
  • the present invention addresses the above and other drawbacks by providing a protocol tunneling device for supporting communication between a local IPV4 data source comprising a network layer identified by a data source IPv4 address and located on a local network and a remote IPv4 data sink, the data source communicating using IPv4 protocol data packets with the data sink via a communications path comprising an IPv6 router and a tunneling end point.
  • the router and tunneling end point communicate using an IPv6 protocol and the tunneling end point and the data sink communicate using the IPv4 protocol.
  • data communication system comprising a data source identified by a data source IPv4 address and located on a local network, and a data sink located on a remote IPv4 network.
  • the data source communicates with the data sink using an IPv4 protocol via a communications path comprising an IPv6 router located on the local network and an intermediate IPv6 network and a tunneling end point located on the intermediate IPv6 network and a remote IPv4 network.
  • the data communication system also comprises a protocol tunneling device located on the local network.
  • the tunneling device comprises a first network layer compatible with the IPv4 protocol, the first network layer identified by a first address compatible with the IPv4 protocol, a second network layer compatible with the IPv6 protocol, the second network layer identified by a second address compatible with the IPv6 protocol, a tunneling client providing a tunnel to the tunneling end point via the IPv6 router and the intermediate IPv6 network using the IPv6 protocol and an IPv4 routing function.
  • Figure 1 is a block diagram of an interoperability device in accordance with an illustrative embodiment of the present invention
  • Figure 2 is a block diagram of the architecture of the interoperability device and related network devices in accordance with an illustrative embodiment of the present invention
  • Figure 3 is a block diagram of an architecture of an interoperability communication system in accordance with an illustrative embodiment of the present invention
  • Figure 5 is a flow chart detailing the actions performed by the interoperability device in accordance with an illustrative embodiment of the present invention.
  • the interoperability device 10 is illustratively comprised of a CPU 12 under control of program code and configuration information stored in a ROM 14 and/or a RAM 16.
  • the CPU 12 receives, handles and transmits packets (not shown), illustratively packets conforming to IPv6, via a network interface 18.1 , which provides the interoperability device 10 access to a first IPv6 network segment 20.1 and packets conforming to IPv4, via a network interface 18.2, which provides the interoperability device 10 access to a second network segment, such as a Local Area Network (LAN), or "local network" 20.2.
  • LAN Local Area Network
  • a serial interface 22 such as a USB interface
  • a power supply 24 is also provided in order to supply the components with the requisite current to ensure their correct operation.
  • DMA Direct Memory Access
  • RAM 16 is provided between the network interfaces 18.1 and 18.2, and RAM 16 in order to allow for the direct transfer of incoming packets from the network interfaces 18.1 and 18.2 to the RAM 16 and direct transfer of outgoing packets from the RAM 16 to the network interfaces 18.1 and 18.2.
  • the network interfaces as 18.1 and 18.2 are illustrated as comprising a direct physical connection, respectively 26.1 to the IPv6 network segment and 26.2 to the LAN 20.2, for example when the access technology conforms to Ethernet (e.g. IEEE 802.3), Firewire (IEEE 1394) or the like, other wireless technologies such as WiFi (e.g. IEEE 802.11) may also prove suitable in a given application.
  • the RAM 16 may also be used to store routing tables and the like (not shown).
  • the architecture 28 of the interoperability device 10 is comprised of a four (4) layer TCP/IP protocol stack 30, a configuration interface 32 and a tunneling client (such as a TSP client with DSTM support) 34.
  • the tunneling client 34 and the configuration interface 32 both take advantage of the communication services provided by the TCP/IP protocol stack 30 in order to communicate with other network devices (e.g. the peer tunneling server 48 for the tunneling client).
  • the TCP/IP protocol stack 30 is comprised of a transport layer 36 which can establish end-to-end communications with other suitably equipped network devices using either TCP or UDP.
  • a first network layer 38 compliant with a first protocol such as IPv4 is provided in order to communicate with other IPv4 compatible network devices located in the LAN 20.2, as well as with remote IPv4 hosts located in an IPv4 network segment beyond the peer tunneling server 48.
  • a second network layer 40 compliant with a second protocol such as IPv6 is also provided in order to communicate over the IPv6 network segment, mainly with the peer tunneling server 48, via other IPv6 compatible network entities such as a router 42.
  • a data link layer 44 for example an Ethernet (as defined in IEEE 802.3) or WiFi (as defined IEEE 802.11) data link layer is provided.
  • the data link layer 44 is interconnected with other network devices via the physical layer 46, for example a twisted pair cable, fiber optic cable, RF wireless transceiver or the like.
  • the configuration interface 32 allows parameters to be configured, for example when automatic configuration is otherwise unavailable. This would allow the configuration interface 32 to be accessed via the TCP/IP protocol stack 30, for example using a web browser if HTTP support and suitable web based configuration pages are provided by the configuration interface 32.
  • the serial (USB) interface (reference 22 in Figure 1), if available, could be used to provide access to the configuration interface 32.
  • a number of other parameters could also be preconfigured or modifiable via the configuration interface 32.
  • a number of parameters related to the configuration of the tunneling client 34 (the operation of which will be explained in more detail hereinbelow).
  • the fully qualified domain name of the host 48 on which the tunneling end point 50 resides with which the tunneling client 34 wishes to establish a tunnel 52 via the external IPv6 network segment (or "domain") 20.1 could be configured via the configuration interface 32.
  • a Domain Name Server (DNS, not shown) could then be used to look up the actual IPv6 address of the TSP peer 50.
  • Other parameters include those credentials necessary to authenticate the tunneling client 34 with the tunneling end point 50 when establishing the tunnel 52.
  • the interoperability device 10 provides IPv4 connectivity to IPv4 enabled network devices, or "data sources”, as in 54 located in the LAN 20.2, which, without the presence of the interoperability device 10, would not be capable of communicating with remote IPv4 correspondents, or "data sinks" 56, across the IPv6 network segment 20.1.
  • IPv4 enabled network devices do not have the capability to use the native IPv6 protocol for communication: either their IP stack is IPv4 only and cannot be upgraded to support IPv6, or they provide services / applications that only work with the IPv4 protocol and cannot be upgraded.
  • IPv4 network devices will be grouped in the LAN 20.2 and all other hosts using the IPv6 protocol only, will be located in the IPv6 network segment 20.1.
  • IPv6 network segment 20.1 IPv6 network segment 20.1.
  • the LAN 20.2 may be reduced to a single IPv4 enabled network device 54 directly connected to the interoperability device 10, via network interface 18.2.
  • One aspect of the interoperability device 10 is that it automatically provisions IPv4 connectivity in the LAN 20.2 where it is connected.
  • the interoperability device 10 illustratively includes all the necessary networking protocols and functionalities to offer IPv4 connectivity to the IPv4 enabled network devices 54 within the LAN 20.2 (by means of standard IPv4 networking procedures over the LAN 20.2), as well as outside the LAN 20.2 (by means of IPv4-in-IPv6 tunneling).
  • One feature of the interoperability device 10 is that no software upgrade or modification to the IPv4 enabled network devices is required, provided the IPv4 enabled network devices as in 54 are equipped with those minimum set of functionalities required for an IPv4 host to operate on the LAN 20.2.
  • IPv6 enabled network devices located in the IPv6 network segment 20.1 , IPv6 enabled router 42 or other IPv6 enabled networking (such as other routers, gateways, firewalls, etc.) equipment found on the IPv6 network segment 20.1.
  • the LAN 20.2 is connected to a second network segment, for example an external IPv6 network 20.1 (which could be a corporate network or the service infrastructure network of a cellular operator or ISP, like the IMS) via the interoperability device 10.
  • IPv4 enabled network devices 54 may be attached to the LAN 20.2.
  • IPv4 enabled network devices may include legacy IPv4 only application servers, printers, etc.
  • IPv6 IMS deployment such IPv4 enabled network devices, would support IPv4 only services, that a cellular operator or ISP cannot or does not want to transition to IPv6, typically mainly for reasons related to cost.
  • the interoperability device 10 has two network interfaces 18.1 and 18.2, attached respectively to the IPv6 network segment 20.1 and the LAN 20.2.
  • the interoperability device 10 provides those functions necessary to interconnect the data source IPv4 enabled network devices 54 resident on the LAN 20.2 with remote data sinks such as IPv4 enabled network devices as in 56 located on a remote IPv4 network segment 58, but accessible only via the intermediate IPv6 network segment 20.1 (connected to the IPv6 network interface 18.1 of the interoperability device 10).
  • the interoperability device 10 illustratively provides IPv4-in-IPv6 tunneling and acts as one of the tunnel end points.
  • the other tunnel end point is, for example, an IPv6 / IPv4 router (providing a tunnel server functionality) 60 illustratively interconnecting the remote IPv4 network segment 58 with the intermediate IPv6 network segment 20.1.
  • IPv6 / IPv4 router providing a tunnel server functionality
  • a compatible tunneling mechanism must be implemented in both the interoperability device 10 and the tunnel server 60.
  • IPv4 networking is used to support communications between the IPv4 enabled network devices 54 in the LAN 20.2 and the interoperability device 10; and between the tunnel server 60 and the remote IPv4 enabled network devices 56.
  • IPv4-in-IPv6 tunneling is performed between the interoperability device 10 and the tunnel server 60 (which provides the remote tunnel end point) via the IPv6 enabled router 42 and any other IPv6 router in the path.
  • the tunnel server 60 is replaced by a Tunnel Broker Server (TBS).
  • TBS Tunnel Broker Server
  • the IPv4-in-IPv6 tunnel, as well as the interaction between the interoperability device 10 and the TBS, complies with that as described in US Patent Applications entitled “Method and apparatus for connecting IPv4 devices through an IPv6 network using a tunnel setup protocol" and published with the numbers 2004/0088385 A1 and 2006/0248202 A1 , which are incorporated herein by reference in their entirety.
  • FIG. 4 in addition to Figure 1 , in a further illustrative embodiment of the present invention, we consider a corporate network that has been fully transitioned to IPv6 and no longer supports IPv4 networking. However, a few IPv4 network devices as in 54 still need IPv4 networking capabilities, and have been grouped in a "legacy" LAN 20.2.
  • the interoperability device 10 is simply connected to the IPv6 network segment 20.1 via its "IPv6" network interface 18.1.
  • the "IPv4" network interface 18.2 of the interoperability device 10 is connected to the LAN 20.2, which is granted IPv4 connectivity across the IPv6 network segment 20.1.
  • IPv4 network devices 54 for example an IPv4 application server, a legacy IPv4 only network device, an IPv4 SIP phone, etc.
  • All these IPv4 network devices 54, as well as the interoperability device 10, will be inter-connected by means of a standard hub / switch 62. They will constitute the LAN 20.2, the interoperability device 10 providing all standard IPv4 routing functionalities to these IPv4 network devices 54.
  • the first step 100 comprises configuring an IPv6 address on the network interface 18.1 of the interoperability device 10 connected to the IPv6 network segment 20.1. This is typically carried out by sending an IPv6 Router Solicitation, which will be answered by an IPv6 Router Advertisement from an IPv6 router 42 located in the IPv6 network segment 20.1.
  • IPv6 Router Solicitation which will be answered by an IPv6 Router Advertisement from an IPv6 router 42 located in the IPv6 network segment 20.1.
  • IPv6 Router Advertisement from an IPv6 router 42 located in the IPv6 network segment 20.1.
  • one way to obtain the IPv6 address is to perform IPv6 stateless auto-configuration, generating an IPv6 address based on an IPv6 prefix advertised in the Router Advertisement and the MAC address of the network interface.
  • Another alternative is to perform stateful auto-configuration, if made mandatory by a dedicated flag in the Router Advertisement.
  • a DHCPv ⁇ client must be present on the interoperability device 10, to interact with a DHCPv ⁇ server located in the IPv6 network segment 20.1 , to obtain an IPv6 address.
  • a default route to a default IPv6 router 42 (advertised in the Router Advertisement) located in the IPv6 network segment 20.1 must also be configured and associated to the network interface 18.1 connected to the IPv6 network segment 20.1.
  • a DNS accessible via IPv6 transport may be optionally advertised in the Router Advertisement, and should be used as the current DNS. Otherwise, a default DNS accessible via IPv6 transport should be pre-configured on the interoperability device 10 and used as the current DNS.
  • the IPv6 address of the TBS 60 is retrieved. This can be performed dynamically using for example a DNS query (provided the fully qualified domain name of the TBS 60, e.g. tunnel_broker.isp_provider.com, is available for example in a configuration file stored on the interoperability device 10).
  • the IPv6 address of the TBS 60 can also be statically retrieved, for example from a configuration file stored on the interoperability device 10.
  • a third step 120 comprises negotiating the IPv4-in-IPv6 tunnel parameters using TSP, between the TSP client located on the interoperability device 10 and the TBS 60.
  • the negotiation on the TSP client side, is typically based on pre-configured values stored in a configuration file on the interoperability device 10. Pre-configured values would typically include the version of the TSP protocol supported by the TSP client, authentication mode supported by the TSP client and associated credentials, the type of tunnel requested (v4-in-v6 in this case), etc...
  • the interoperability device 10 is allocated an IPv4 address and a delegated IPv4 prefix.
  • IPv6 address of the associated tunnel end-point (this could be for example, the IPv6 address of the TBS 60, or the IPv6 address of an alternate tunnel end-point, such as a dual stack IPv6 / IPv4 router), as well as the IPv4 address allocated to the associated tunnel end point, are also transmitted to the interoperability device 10.
  • a DNS with IPv4 transport should also be allocated by the TBS 60, if this option is supported by the tunneling protocol. Otherwise, a default DNS with IPv4 transport must be pre-configured on the interoperability device 10.
  • a fourth step 130 comprises configuring the local tunnel end-point on the interface 18.1 of the interoperability device 10 connected to the IPv6 network segment 20.1 , using the parameters negotiated during step 120.
  • the allocated IPv4 address is configured as the local tunnel end-point IPv4 address.
  • a fifth step 140 involves auto-configuration of the interoperability device 10 in order to perform IPv4 router functionalities for the IPv4 enabled network devices 54 located in the LAN 20.2.
  • An IPv4 address is configured on the interface 18.2 connected to the LAN 20.2 (it must be consistent with the delegated IPv4 prefix).
  • a DHCP server is configured, to allocate IPv4 addresses based on the delegated IPv4 prefix, to advertise the IPv4 address of the interface connected to the LAN 20.2 as the default IPv4 gateway, to advertise the delegated IPv4 prefix and the address of the DNS server with IPv4 transport.
  • IPv4 enabled network devices 54 located in the LAN 20.2 may not have a DHCP client and may need static IPv4 configuration.
  • the delegated prefix may be split between a range of DHCP allocated IPv4 addresses and a range of IPv4 addresses to be statically configured on the IPv4 enabled network devices 54.
  • An IPv4 route to the delegated IPv4 prefix must be associated with the interface 18.2 connected to the LAN 20.2.
  • the default IPv4 route must be associated with the IPv4-in- IPv6 tunnel end-point.
  • the interoperability device 10 is ready to act as the default IPv4 router for the IPv4 enabled network devices 54 on the LAN 20.2 and performs the following functions:
  • IPv4 prefix DNS IPv4 address
  • DHCPv4 client DNS IPv4 address
  • the interoperability device 10 performing the DHCPv4 server.
  • IPv4 traffic from the IPv4 enabled network devices 54 located in the LAN 20.2 to remote IPv4 enabled network devices 56 located in a remote IPv4 network segment 58. This traffic is transmitted via the IPv4-in-IPv6 tunnel established by the interoperability device 10.
  • Routes at step 154 IPv4 traffic from remote IPv4 enabled network devices 56 located in a remote IPv4 network segment 58 to the IPv4 enabled network devices 54 located in the LAN 20.2. This traffic will be received via the IPv4-in-IPv6 tunnel established by the interoperability device 10.

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

La présente invention concerne un dispositif de tunnellisation de protocole pour soutenir la communication entre une source de données IPV4 locale comprenant une couche réseau identifiée par une adresse IPv4 de source de données et située sur un réseau local et un référentiel de données IPv4 distant, la source de données communiquant à l'aide de paquets de données de protocole IPv4 avec un référentiel de données via un chemin de communications comprenant le dispositif de tunnellisation de protocole, un routeur IPv6 et un point d'extrémité de tunnellisation, le dispositif de tunnellisation de protocole, un routeur et un point d'extrémité de tunnellisation communiquant à l'aide d'un protocole IPv6, le point d'extrémité de tunnellisation et le référentiel de données communiquant à l'aide du protocole IPv4 et le dispositif de tunnellisation de protocole et la source de données communiquant à l'aide du protocole IPv4.
PCT/CA2008/001417 2007-08-03 2008-08-01 Dispositif, système et procédé pour le provisioning ipv4 automatique dans un réseau local raccordé à un réseau ipv6 Ceased WO2009018658A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US95378407P 2007-08-03 2007-08-03
US60/953,784 2007-08-03

Publications (1)

Publication Number Publication Date
WO2009018658A1 true WO2009018658A1 (fr) 2009-02-12

Family

ID=40340910

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2008/001417 Ceased WO2009018658A1 (fr) 2007-08-03 2008-08-01 Dispositif, système et procédé pour le provisioning ipv4 automatique dans un réseau local raccordé à un réseau ipv6

Country Status (1)

Country Link
WO (1) WO2009018658A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012083657A1 (fr) * 2010-12-20 2012-06-28 刘建 Procédé et système de traitement de paquets et équipement des locaux d'abonné
CN102938736A (zh) * 2012-11-20 2013-02-20 杭州迪普科技有限公司 一种实现IPv4报文穿越IPv6网络的方法和设备
TWI483605B (zh) * 2012-11-29 2015-05-01 Compal Broadband Networks Inc 用於網路系統之部署方法及電腦系統
CN105610857A (zh) * 2016-01-26 2016-05-25 杭州德澜科技有限公司 一种自动识别本地与远程网络的方法
CN106060180A (zh) * 2016-08-24 2016-10-26 电子科技大学 一种针对IPv6的基于地理位置和应用信息的寻址方法
CN108322400A (zh) * 2012-06-05 2018-07-24 华为技术有限公司 报文处理方法、系统及路由设备
CN113923110A (zh) * 2020-06-22 2022-01-11 中兴通讯股份有限公司 Map-e隧道的配置管理方法、设备、服务器以及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0840482A1 (fr) * 1996-11-01 1998-05-06 Hitachi, Ltd. Méthode de communication entre un terminal IPv4 et un terminal IPv6 et appareil de conversion IPv4-IPv6
WO2004045183A1 (fr) * 2002-11-13 2004-05-27 Thomson Licensing S.A. Procede et dispositif pour la mise en oeuvre de protocole tunnel 6a4 sur un mecanisme de traduction d'adresse de reseau
US20040133692A1 (en) * 2003-01-07 2004-07-08 Hexago Inc. Method and apparatus for connecting IPV6 devices through an IPv4 network and a network address translator (NAT) using a tunnel setup protocol
US20050094575A1 (en) * 2003-10-31 2005-05-05 Samsung Electronics Co., Ltd. System for providing tunnel service capable of data communication between different types of networks
US20050099976A1 (en) * 2003-09-23 2005-05-12 Shu Yamamoto Enabling mobile IPv6 communication over a network containing IPv4 components using a tunnel broker model

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0840482A1 (fr) * 1996-11-01 1998-05-06 Hitachi, Ltd. Méthode de communication entre un terminal IPv4 et un terminal IPv6 et appareil de conversion IPv4-IPv6
WO2004045183A1 (fr) * 2002-11-13 2004-05-27 Thomson Licensing S.A. Procede et dispositif pour la mise en oeuvre de protocole tunnel 6a4 sur un mecanisme de traduction d'adresse de reseau
US20040133692A1 (en) * 2003-01-07 2004-07-08 Hexago Inc. Method and apparatus for connecting IPV6 devices through an IPv4 network and a network address translator (NAT) using a tunnel setup protocol
US20050099976A1 (en) * 2003-09-23 2005-05-12 Shu Yamamoto Enabling mobile IPv6 communication over a network containing IPv4 components using a tunnel broker model
US20050094575A1 (en) * 2003-10-31 2005-05-05 Samsung Electronics Co., Ltd. System for providing tunnel service capable of data communication between different types of networks

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012083657A1 (fr) * 2010-12-20 2012-06-28 刘建 Procédé et système de traitement de paquets et équipement des locaux d'abonné
CN102546362A (zh) * 2010-12-20 2012-07-04 中兴通讯股份有限公司 报文处理方法、系统和用户前端设备
CN108322400A (zh) * 2012-06-05 2018-07-24 华为技术有限公司 报文处理方法、系统及路由设备
CN108322400B (zh) * 2012-06-05 2021-06-08 华为技术有限公司 报文处理方法、系统及路由设备
CN102938736A (zh) * 2012-11-20 2013-02-20 杭州迪普科技有限公司 一种实现IPv4报文穿越IPv6网络的方法和设备
TWI483605B (zh) * 2012-11-29 2015-05-01 Compal Broadband Networks Inc 用於網路系統之部署方法及電腦系統
CN105610857A (zh) * 2016-01-26 2016-05-25 杭州德澜科技有限公司 一种自动识别本地与远程网络的方法
CN106060180A (zh) * 2016-08-24 2016-10-26 电子科技大学 一种针对IPv6的基于地理位置和应用信息的寻址方法
CN106060180B (zh) * 2016-08-24 2019-06-18 电子科技大学 一种针对IPv6的基于地理位置和应用信息的寻址方法
CN113923110A (zh) * 2020-06-22 2022-01-11 中兴通讯股份有限公司 Map-e隧道的配置管理方法、设备、服务器以及存储介质

Similar Documents

Publication Publication Date Title
Waddington et al. Realizing the transition to IPv6
Durand et al. Dual-stack lite broadband deployments following IPv4 exhaustion
JP4303600B2 (ja) 異なるアドレス領域を有するネットワーク間の接続設定機構
Mawatari et al. 464XLAT: Combination of stateful and stateless translation
JP5475763B2 (ja) ＩＰｖ４ドメインからのデータパケットをＩＰｖ６ドメインで受信する方法、ならびに関連するデバイスおよびアクセス機器
US8751617B2 (en) Method and device for identifying and selecting an interface to access a network
CN102347993B (zh) 一种网络通信的方法和设备
RU2602971C2 (ru) Способ динамического конфигурирования ipv6 для домашнего шлюза
US10659430B2 (en) Systems and methods for dynamic network address modification related applications
US20060248202A1 (en) Method and apparatus for connecting ipv4 devices through an ipv6 network using a tunnel setup protocol
CN101019381B (zh) 在访问广域网期间维持为指定站点中的IPv6节点分配的唯一本地地址的机密性
WO2000079765A1 (fr) Procedes et appareil de transmission tunnel inverse utilises dans des reseaux informatiques prives
EP1997303A2 (fr) Procédé destiné à configurer des téléphones ip éloignés
US8392613B2 (en) Network address assignment
CN101854285A (zh) 运营商级网络地址转换设备发现方法、设备和系统
CN100379219C (zh) 利用nat-pt和客户/服务器模式实现ip网络终端通信方法
Cui et al. Public IPv4-over-IPv6 access network
JP4600394B2 (ja) ネットワークアクセスルータ、ネットワークアクセス方法、プログラム、及び記録媒体
WO2008106773A1 (fr) Dispositif de tunnellisation pour l'établissement automatique de protocoles dans un réseau
CN104935677A (zh) 一种nat64资源获取方法及获取/分配装置
DK1817892T3 (en) PROCEDURE AND SYSTEM TO OPEN A NETWORK LINK
Durand et al. RFC 6333: Dual-stack lite broadband deployments following IPv4 exhaustion
JP3808471B2 (ja) ネットワーク及びルータ装置並びにそれらに用いるアドレス通知方法
Anderson et al. Stateless IP/ICMP Translation for IPv6 Internet Data Center Environments (SIIT-DC): Dual Translation Mode
Radley et al. Evaluation and study of transition techniques addressed on IPv4-IPv6

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08783328

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08783328

Country of ref document: EP

Kind code of ref document: A1