WO2020052642A1 - 漫游 - Google Patents

漫游 Download PDF

Info

Publication number
WO2020052642A1
WO2020052642A1 PCT/CN2019/105634 CN2019105634W WO2020052642A1 WO 2020052642 A1 WO2020052642 A1 WO 2020052642A1 CN 2019105634 W CN2019105634 W CN 2019105634W WO 2020052642 A1 WO2020052642 A1 WO 2020052642A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
host
network
tcp
peer end
Prior art date
Application number
PCT/CN2019/105634
Other languages
English (en)
French (fr)
Inventor
王玮
Original Assignee
新华三技术有限公司
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 新华三技术有限公司 filed Critical 新华三技术有限公司
Priority to US17/274,626 priority Critical patent/US11665266B2/en
Priority to EP19859679.3A priority patent/EP3852412B1/en
Publication of WO2020052642A1 publication Critical patent/WO2020052642A1/zh

Links

Images

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]
    • H04L69/169—Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • 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
    • 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]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections

Definitions

  • a host also called a client
  • a server establish a Transmission Control Protocol / Internet Protocol (TCP / IP) connection, which is bound to the host's IP address and the server's IP address, etc.
  • TCP / IP Transmission Control Protocol / Internet Protocol
  • the host may roam from the current network to another network. After the host roams to another network, in order to ensure that data can continue to be sent to the host, the IP address of the host needs to be modified.
  • the modified IP address belongs to the IP network segment corresponding to the roamed network.
  • the TCP / IP connection established by the host before roaming (specifically, the TCP / IP connection established between the host and the server) binds the host's IP address before roaming, once the host's IP address is modified after roaming, The TCP / IP connection established by the host before roaming will be interrupted. The host needs to use the modified IP address to re-establish a TCP / IP connection with the server in order to resume communication with the server.
  • FIG. 1 is a flowchart of a method provided by the present application
  • FIG. 2 is a flowchart of obtaining a second IP address of a host on a second network provided by this application;
  • FIG. 3 is a schematic structural diagram of a device provided by this application.
  • FIG. 4 is a schematic diagram of a hardware structure of a host provided by the present application.
  • the "triangular routing" method is often used to ensure that the TCP / IP connection established by the host before roaming is not interrupted due to host roaming, and communication is not interrupted after the host roams, as described below.
  • the host's IP address is not modified, but the router accessed by the host on the destination network (Recorded as the destination router) Notifies the router (recorded as the source router) that the host accesses in the source network of the roaming. If the source router receives a packet addressed to the host (the destination IP address of the packet is the IP address of the host) The packet is forwarded to the destination router, and the destination router forwards the packet to the host. Because the packet passes through the source router and destination router before reaching the host, it is called a triangle route.
  • an overlay method can also be adopted.
  • the gateway publishes the IP address of the destination router accessed by the host's destination network through BGP (Border Gateway Protocol).
  • BGP Border Gateway Protocol
  • other routers receive the packets sent to the host, they do not follow the instructions directly.
  • the destination IP address of the packet (the IP address of the host) is forwarded. Instead, the IP address of the destination router is first found, and then the packet is encapsulated in a VxLAN (Virtual Extensible Local Area Network) packet.
  • VxLAN Virtual Extensible Local Area Network
  • UDP / IP For example, UDP / IP is used. (User Datagram Protocol // Internet Protocol) connection, the destination IP address of this VxLAN message is the IP address of the destination router. After receiving this message, the destination router will take out the load in the VxLAN message and send it to the host.
  • UDP User Datagram Protocol // Internet Protocol
  • the overlay method avoids the problem of "triangular routing", because the gateway needs to publish the IP address of the destination router of the host after roaming, it needs to establish a forwarding entry for each host in the routing table. With the expansion of the host scale, the routing table resources will be consumed tremendously.
  • this application proposes a new method for non-interrupted communication of hosts after roaming to ensure that TCP / IP connections established by hosts before roaming are not interrupted by host roaming. To achieve uninterrupted communication after the host roams. The following is described in conjunction with FIG. 1.
  • a flowchart of a method provided by the present application is provided. This method is applied to the host.
  • the host may be a client or other devices.
  • the host is currently on the first network.
  • the first network is only named for convenience of description, and is not used for limitation.
  • the method includes the following steps.
  • Step 101 Bind the TCP / IP connection established between the host and the opposite end to the host address in the first IP address, so that the TCP / IP connection is roamed from the first network at the first IP address due to the host. It will continue to be maintained until the second network changes.
  • the first IP address is the IP address of the host in the first network, including the network address and the host address
  • the network address indicates the network segment where the host is located
  • the host address refers to the The device identifier of the host is used to uniquely identify the host.
  • the first IP address as an IPv6 address as an example
  • the first 64 bits of the IPv6 address represent the network address
  • the remaining 64 bits represent the host address.
  • a TCP / IP connection established between a host and a peer should be bound to the IP address of the host's current network and other parameters, such as the server IP address.
  • the IP address bound to the TCP / IP connection is different from other parameters.
  • the IP address bound to the TCP / IP connection changes as the host roams to different networks, and other parameters bound to the TCP / IP connection do not occur as the host roams. change.
  • the TCP / IP connection management mechanism is improved. Specifically, the TCP / IP connection established between the host and the server is no longer bound to the first IP address of the first network where the host is currently located.
  • the binding is modified to bind to the host address in the first IP address of the host, and other parameters of the TCP / IP connection binding are unchanged.
  • Step 102 When the host roams from the first network to the second network, continue to maintain the TCP / IP connection, obtain a second IP address of the host on the second network, and change the second IP address. Notify the opposite end or notify the opposite end of a portion where the second IP address is changed compared to the first IP address.
  • the second IP address is an IP address of the host in the second network, including a network address and a host address.
  • the network address indicates a network segment where the host is located.
  • the host address refers to a device identifier of the host. Uniquely identifies the host. Therefore, for the same host, the host address in the second IP address is the same as the host address in the first IP address, and the network address in the second IP address may be different from the network address in the first IP address. For a new network address.
  • the TCP / IP connection established between the host and the peer end is modified from the first IP address that should be currently bound to the host in the first network to the host address in the first IP address, so that All parameters of the TCP / IP connection binding established between the host and the peer will not change because the host roams from the first network to the second network.
  • the host and the peer The TCP / IP connection established between the peers can still be maintained, which ensures that the TCP / IP connection established by the host before roaming is not interrupted by the host roaming, and the communication is not interrupted after the host roams.
  • the TCP / IP connection established between the host and the peer end is originally bound to an IP address that changes due to host roaming to a host that does not change due to host roaming. Address, which allows the TCP / IP connection established between the host and the peer to continue to be maintained even if the host roams from the first network to the second network, which ensures that the TCP / IP connection established by the host before roaming does not occur due to the host Interruption when roaming, so that the host does not interrupt communication after roaming.
  • the network address in the first IP address of the host does not belong to the IP address segment corresponding to the second network.
  • the second IP address In this application, the first IP address and the second IP address are merely named for convenience of description, and are not used for limitation.
  • a second IP address of a host in a second network may be obtained based on a Dynamic Host Configuration Protocol (DHCP: Dynamic Host Configuration Protocol), and FIG. 2 briefly illustrates how to obtain the second IP address.
  • DHCP Dynamic Host Configuration Protocol
  • FIG. 2 a flowchart of obtaining a second IP address of a host on a second network provided by this application is provided. As shown in FIG. 2, the process may include the following steps.
  • Step 201 As a DHCP client, the host sends a DHCP request to a DHCP server to obtain a second IP address of the host on the second network.
  • the DHCP request herein may be a Discover message in DHCP.
  • Step 202 As a DHCP client, the host receives the second IP address of the host on the second network returned by the DHCP server.
  • the host can obtain its second IP address on the second network.
  • the second IP address may be notified to the host.
  • the opposite end so that the opposite end changes the recorded IP address of the host from the first IP address to the second IP address.
  • the second IP address may not be specifically notified to the opposite end by using a specific message, but the second IP address may be notified to the opposite end by using a message that the host should originally send to the opposite end.
  • informing the peer end of the second IP address in the above step 102 includes: sending a data packet or a TCP / IP protocol packet to the peer end through the host, and notifying the peer end of the second IP address.
  • the source IP address of the data message or TCP / IP protocol message is the second IP address.
  • the peer end when the peer end receives the packet and finds that the source IP address of the packet is the second IP address, which is different from the first recorded IP address locally, it directly changes the first recorded local IP address to the first IP address.
  • Two IP addresses Two IP addresses.
  • the part where the second IP address is changed from the first IP address may be notified to the pair. end.
  • a portion where the second IP address is changed from the first IP address refers to a network address in the second IP address.
  • a part in which the second IP address is changed from the first IP address may be notified to the peer end by using a TCP / IP protocol message.
  • notifying the peer end that the second IP address is changed compared to the first IP address may include: notifying the peer end of the changed part through a TCP / IP protocol message.
  • the aforementioned TCP / IP protocol message may be one of a message such as an acknowledgement (ACK) message, a request (REQ) message, or a negative response (NAK) message in TCP / IP.
  • ACK acknowledgement
  • REQ request
  • NAK negative response
  • first IP address and second IP address may both be IPv6 addresses.
  • the method provided in the present application has been described above.
  • the following describes the method provided in this application by using a satellite communication environment: it is applied to a satellite communication environment, and the IP network segment where the satellite responsible for communication in space is located is fixed.
  • the TCP / The IP connection is no longer bound to the satellite's IP address, but to the satellite's device identification. In this way, when the satellite moves fast, the TCP / IP connection between the satellite and the ground terminal will not be interrupted by the satellite movement. This can improve the routing efficiency of satellites in space.
  • FIG. 3 a structural diagram of a device provided by the present application.
  • the device is applied to a host and includes a connection unit 310 and a roaming processing unit 320.
  • the connecting unit 310 is configured to bind a TCP / IP connection established between the host and the opposite end to a host address in a first IP address, so that the TCP / IP connection is in the first IP address due to the host from The first network is maintained while roaming to the second network and changes, wherein the first IP address is an IP address of the host in the first network, and includes a network address and the host address.
  • the network address indicates the network segment where the host is located.
  • the host address refers to a device identifier of the host and is used to uniquely identify the host; and when the host roams from the first network to the second network, Continue to maintain the TCP / IP connection.
  • a roaming processing unit 320 is configured to: when the host roams from the first network to the second network, obtain a second IP address of the host on the second network, and notify the second IP address Notifying the peer end or notifying the peer end of a change in the second IP address compared to the first IP address.
  • the second IP address is an IP address of the host in the second network, and includes a network address and the host address.
  • the notification of the second IP address to the peer by the roaming processing unit 320 includes: a data packet or a TCP / IP protocol packet sent by the host to the peer, Two IP addresses are notified to the peer end, wherein a source IP address of the data packet or the TCP / IP protocol packet is the second IP address.
  • the roaming processing unit 320 notifying the peer end of a portion where the second IP address is changed compared to the first IP address includes: using the TCP / IP protocol message to notify the changed portion. Notify the peer end, wherein the changed part refers to a network address included in the second IP address.
  • the roaming processing unit 320 obtaining the second IP address of the host on the second network includes: the host, as a DHCP client, sends a DHCP request to a DHCP server to obtain the host's presence Receiving the second IP address of the second network; receiving the second IP address of the host on the second network returned by the DHCP server.
  • the first IP address and the second IP address are both IPv6 addresses.
  • the hardware structure may include: a machine-readable storage medium 420 and a processor 410.
  • the machine-readable storage medium 420 is used to store instructions; the processor 410 communicates with the machine-readable storage medium 420, reads and executes the instructions stored in the machine-readable storage medium 420, and implements the roaming disclosed in the above examples of the present disclosure. method.
  • This instruction can implement the functions of the connection unit 310 and the roaming processing unit 320 as shown in FIG. 3.
  • the device shown in FIG. 4 may further include a power source component 430, a network interface 440, and an input / output interface 450.
  • the processor 410, the machine-readable storage medium 420, the power supply component 430, the network interface 440, and the input-output interface 450 may be connected by a bus 460.
  • a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device, and may contain or store information such as executable instructions, data, and so on.
  • the machine-readable storage medium may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard drive), solid state hard disk, any type of storage disk (Such as optical discs, DVDs, etc.), or similar storage media, or a combination thereof.

Landscapes

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

Abstract

本申请提供了漫游方法和主机。本申请中，通过将主机与对端之间建立的TCP/IP连接从原本应绑定主机当前在第一网络的第一IP地址修改为绑定该第一IP地址中不随主机漫游发生变化的主机地址，以实现主机与对端之间建立的TCP/IP连接关联的所有参数不会因为主机从第一网络漫游至第二网络发生变化，如此，即使主机从第一网络漫游至第二网络，主机与对端之间建立的TCP/IP连接仍然可以继续维持。

Description

漫游 背景技术
在网络通信中，主机(也称客户端)与服务器之间建立传输控制协议/因特网互联协议(Transmission Control Protocol/Internet Protocol，TCP/IP)连接，该连接绑定了主机的IP地址、服务器的IP地址等。
在实际应用中，主机可能会从当前一网络漫游至另一网络。当主机漫游至另一网络后，为保证数据可以继续发向主机，则需要修改主机的IP地址，修改后的IP地址属于漫游后的网络对应的IP网段。
但是，因为主机在漫游前建立的TCP/IP连接(具体是主机与服务器之间建立的TCP/IP连接)绑定了主机在漫游前的IP地址，一旦主机的IP地址在漫游后发生修改，则主机在漫游前建立的TCP/IP连接就会中断，主机需利用修改后的IP地址重新与服务器建立TCP/IP连接才能恢复与服务器的通信。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1为本申请提供的方法流程图；
图2为本申请提供的获取主机在第二网络的第二IP地址的流程图；
图3为本申请提供的装置结构示意图；
图4为本申请提供的主机的硬件结构示意图。
具体实施方式
在网络通信中，常采用“三角路由”方法保证主机在漫游前建立的TCP/IP连接不因主机发生漫游而中断，实现主机漫游后通信不中断，下面进行描述。
在“三角路由”方法中，当主机从一个网络(记为源网络)漫游到另一个网络(记为目的网络)时，不修改主机的IP地址，而是由主机在目的网络接入的路由器(记为目的路由器)向主机在源网络接入的路由器(记为源路由器)通知该漫游，如果源路由 器接收到发向主机的报文(报文的目的IP地址为主机的IP地址)，则将该报文转发给目的路由器，由目的路由器再将该报文转发到主机。由于该报文经过了源路由器、目的路由器才最终到达主机，因此称为三角路由。
在“三角路由”方法中，增加了一跳(由源路由器至目的路由器)，这会导致报文转发效率不高。
为了提高“三角路由”方法中报文转发的效率，还可采用覆盖层(Overlay)方式，具体是：当主机从源网络漫游到目的网络时，不修改主机的IP地址，主机需要注册至目的网络中接入的网关，由该网关将主机所在目的网络接入的目的路由器的IP地址通过BGP(Border Gateway Protocol)发布出去，这样其他路由器收到发向该主机的报文时，不是直接按照报文的目的IP地址(主机的IP地址)进行转发，而是先查找目的路由器的IP地址，然后将这个报文封装到一个VxLAN(Virtual extensible Local Area Network)报文中，例如使用UDP/IP(User Datagram Protocol//Internet Protocol)的连接，此VxLAN报文的目的IP地址是目的路由器的IP地址，目的路由器收到此报文后，将取出VxLAN报文中的负载发送到主机。
Overlay方式虽然避免了“三角路由”的问题，但是由于网关需要发布主机在漫游后的目的路由器的IP地址，需要在路由表中为每个主机建立一条转发表项。随着主机规模的扩大，对路由表资源将消耗巨大。
为了避免上述“三角路由”方法、Overlay方式引起的问题，本申请提出了一种新的主机漫游后通信不中断方法，以保证主机在漫游前建立的TCP/IP连接不因主机发生漫游而中断，实现主机漫游后通信不中断。下面结合图1进行描述。
参见图1，为本申请提供的方法流程图。该方法应用于主机。这里，作为一个实施例，所述主机可为客户端，也可为其他设备。
假若主机当前处于第一网络。这里，第一网络只是为便于描述而进行的命名，并非用于限定。
如图1所示，该方法包括以下步骤。
步骤101，将主机与对端之间建立的TCP/IP连接绑定第一IP地址中的主机地址，以使所述TCP/IP连接在所述第一IP地址因本主机从第一网络漫游至第二网络而发生改变时继续维持。
在本申请中，第一IP地址为主机在第一网络中的IP地址，包括网络地址和所述主 机地址，所述网络地址表示所述主机所在的网段，所述主机地址是指所述主机的设备标识，用于唯一标识所述主机。以第一IP地址为IPv6地址为例，IPv6地址的前64个比特表示网络地址，剩下的64个比特表示主机地址。
在现有TCP/IP中，主机与对端(如服务器)之间建立的TCP/IP连接应与主机在当前所处网络的IP地址以及其他参数，比如服务器IP地址，等进行绑定。其中，TCP/IP连接绑定的IP地址与其他参数不同，TCP/IP连接绑定的IP地址随着主机漫游至不同网络会发生变化，而TCP/IP连接绑定的其他参数不随主机漫游发生改变。而本申请中，对TCP/IP连接管理机制进行了改进，具体为：主机与服务器之间建立的TCP/IP连接不再与主机在当前所处的第一网络的第一IP地址进行绑定，而是将绑定修改为与主机的第一IP地址中的主机地址绑定，TCP/IP连接绑定的其他参数不变。通过上述改进，则TCP/IP连接绑定的所有参数都不会因为主机漫游发生变化。如此，本申请中，当主机从第一网络漫游至第二网络时，因为TCP/IP连接绑定的所有参数未发生变化，则TCP/IP连接会继续维持，具体见步骤102。
步骤102，当主机从所述第一网络漫游至第二网络时，继续维持所述TCP/IP连接，并获取本主机在所述第二网络的第二IP地址，将所述第二IP地址通知给对端或者将所述第二IP地址相比所述第一IP地址发生变化的部分通知给对端。
第二IP地址为主机在第二网络中的IP地址，包括网络地址和主机地址，所述网络地址表示所述主机所在的网段，所述主机地址是指所述主机的设备标识，用于唯一标识所述主机。因此，对于同一个主机来讲，其第二IP地址中的主机地址与其第一IP地址中的主机地址相同，其第二IP地址中的网络地址可以与其第一IP地址中的网络地址不同，为一个新的网络地址。
通过上述改进，本申请中，将主机与对端之间建立的TCP/IP连接从原本应绑定本主机当前在第一网络的第一IP地址修改为第一IP地址中的主机地址，使得主机与对端之间建立的TCP/IP连接绑定的所有参数不会因为主机从第一网络漫游至第二网络发生变化，如此，即使主机从第一网络漫游至第二网络，主机与对端之间建立的TCP/IP连接仍然可以继续维持，这保证了主机在漫游前建立的TCP/IP连接不因主机发生漫游而中断，实现主机漫游后通信不中断。
至此，完成图1所示流程的描述。
通过图1可以看出，在本申请中，将主机与对端之间建立的TCP/IP连接原本绑定的 因主机漫游而发生变化的IP地址修改为不会因主机漫游而发生变化的主机地址，这使得即使主机从第一网络漫游至第二网络，主机与对端之间建立的TCP/IP连接仍然可以继续维持，这保证了主机在漫游前建立的TCP/IP连接不因主机发生漫游而中断，实现主机漫游后通信不中断。
在本申请中，当主机从第一网络漫游至第二网络后，主机的第一IP地址中的网络地址因为不属于第二网络对应的IP地址段，需要重新获取主机在第二网络中的第二IP地址。本申请中，第一IP地址、第二IP地址只是为便于描述而进行的命名，并非用于限定。
作为一个实施例，本申请中，可基于动态主机配置协议(DHCP：Dynamic Host Configuration Protocol)获取主机在第二网络中的第二IP地址，图2简单示出如何获取第二IP地址。
参见图2，为本申请提供的获取主机在第二网络的第二IP地址的流程图。如图2所示，该流程可包括以下步骤。
步骤201，主机作为DHCP客户端向DHCP服务器发送DHCP请求，以获取主机在所述第二网络的第二IP地址。
作为一个实施例，这里的DHCP请求可为DHCP中的发现(Discover)报文。
步骤202，主机作为DHCP客户端接收所述DHCP服务器返回的主机在所述第二网络的第二IP地址。
至此，完成图2所示流程的描述。
通过图2所示流程，主机可获取其在第二网络的第二IP地址。
为了保持主机在第二网络正常通信，在一个实施例中，如步骤102所述，当主机的IP地址从第一IP地址修改为第二IP地址后，可将所述第二IP地址通知给对端，以使对端将已记录的主机的IP地址从第一IP地址修改为第二IP地址。
在一个实施例中，可以不使用特定报文专门通知第二IP地址给对端，而是借用主机原本应向对端发送的报文将第二IP地址通知给对端。
具体地，上述步骤102中将第二IP地址通知给对端包括：通过本主机向对端发送数据报文或者TCP/IP协议报文，将所述第二IP地址通知给对端，所述数据报文或者TCP/IP协议报文的源IP地址为所述第二IP地址。
如此，当对端收到该报文时，发现报文的源IP地址为第二IP地址，与本地已记录的第一IP地址不同，则直接将本地已记录的第一IP地址修改为第二IP地址。
在另一个实施例中，当主机的IP地址从第一IP地址修改为第二IP地址后，如步骤102所述，可将第二IP地址相比第一IP地址发生变化的部分通知给对端。这里，第二IP地址相比所述第一IP地址发生变化的部分是指所述第二IP地址中的网络地址。
在一个例子中，可通过TCP/IP协议报文将第二IP地址相比所述第一IP地址发生变化的部分通知给对端。如此，上述步骤102中，将第二IP地址相比所述第一IP地址发生变化的部分通知给对端可包括：通过TCP/IP协议报文将该发生变化的部分通知给对端。
在一个例子中，上述的TCP/IP协议报文可为TCP/IP中的确认(ACK)报文、请求(REQ)报文、否定应答(NAK)报文等报文中的一个。
需要说明的是，作为一个实施例，上述的第一IP地址和第二IP地址可均为IPv6地址。
以上对本申请提供的方法进行了描述。下面以应用卫星通信环境对本申请提供的方法进行描述：应用于卫星通信环境，太空中负责通信的卫星所处的IP网段固定，按照本申请提供的方法，卫星与地面终端之间的TCP/IP连接不再与卫星的IP地址绑定，而是与该卫星的设备标识绑定，如此，当卫星快速移动时，卫星与地面终端之间的TCP/IP连接不会因为卫星移动而中断，这可以提升太空中卫星的路由效率。
同样，对于地面终端，即使地面终端的IP地址发生变化，但由于TCP/IP连接不与地面终端的IP地址改变，也不会导致地面终端通信的中断。
下面对本申请提供的装置进行描述。
参见图3，为本申请提供的装置结构图。该装置应用于主机，包括连接单元310和漫游处理单元320。
连接单元310，用于将主机与对端之间建立的TCP/IP连接绑定第一IP地址中的主机地址，以使所述TCP/IP连接在所述第一IP地址因所述主机从第一网络漫游至第二网络而发生改变时继续维持，其中，所述第一IP地址为所述主机在所述第一网络中的IP地址，且包括网络地址和所述主机地址，所述网络地址表示所述主机所在的网段，所述主机地址是指所述主机的设备标识，用于唯一标识所述主机；以及，当本主机从所述第一网络漫游至第二网络时，继续维持所述TCP/IP连接。
漫游处理单元320，用于当所述主机从所述第一网络漫游至所述第二网络时，获取所述主机在所述第二网络的第二IP地址，将所述第二IP地址通知给所述对端或者将所述第二IP地址相比所述第一IP地址发生变化的部分通知给所述对端。所述第二IP地址为所述主机在所述第二网络中的IP地址，且包括网络地址和所述主机地址。
作为一个实施例，所述漫游处理单元320将第二IP地址通知给所述对端包括：通过所述主机向所述对端发送的数据报文或者TCP/IP协议报文，将所述第二IP地址通知给所述对端，其中，所述数据报文或者所述TCP/IP协议报文的源IP地址为所述第二IP地址。
作为一个实施例，所述漫游处理单元320将第二IP地址相比所述第一IP地址发生变化的部分通知给所述对端包括：通过TCP/IP协议报文将所述发生变化的部分通知给所述对端，其中，所述发生变化的部分是指所述第二IP地址包含的网络地址。
作为一个实施例，所述漫游处理单元320获取所述主机在所述第二网络的所述第二IP地址包括：所述主机作为DHCP客户端向DHCP服务器发送DHCP请求，以获取所述主机在所述第二网络的所述第二IP地址；接收所述DHCP服务器返回的所述主机在所述第二网络的所述第二IP地址。
作为一个实施例，所述第一IP地址和第二IP地址均为IPv6地址。
至此，完成本申请提供的装置结构描述。
参见图4，为本申请提供的主机的硬件结构图。如图4所示，该硬件结构可以包括：机器可读存储介质420和处理器410。其中，机器可读存储介质420用于存储指令；处理器410与机器可读存储介质420通信，读取和执行机器可读存储介质中420存储的所述指令，实现本公开上述示例公开的漫游方法。该指令可以实现如图3所示的连接单元310和漫游处理单元320的功能。
此外，在图4所示的装置中，还可以包括电源组件430、网络接口440和输入输出接口450。处理器410、机器可读存储介质420、电源组件430，网络接口440和输入输出接口450之间可以进行总线460进行连接。
至此，完成图4所示装置的硬件结构图。
在本公开中，机器可读存储介质可以是任何电子、磁性、光学或其它物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，机器可读存储介质可以是：RAM(Radom Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪 存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)，或者类似的存储介质，或者它们的组合。

Claims (10)

  1. 一种漫游方法，其特征在于，该方法应用于主机，包括：
    将所述主机与对端之间建立的传输控制协议/因特网互联协议(TCP/IP)连接绑定第一IP地址中的主机地址，以使所述TCP/IP连接在所述第一IP地址因所述主机从第一网络漫游至第二网络而发生改变时继续维持，其中，所述第一IP地址为所述主机在所述第一网络中的IP地址，且包括网络地址和所述主机地址，所述网络地址表示所述主机所在的网段，所述主机地址是指所述主机的设备标识，用于唯一标识所述主机；
    当所述主机从所述第一网络漫游至所述第二网络时，继续维持所述TCP/IP连接，并获取所述主机在所述第二网络的第二IP地址，所述第二IP地址为所述主机在所述第二网络中的IP地址，且包括网络地址和所述主机地址；
    将所述第二IP地址通知给所述对端或者将所述第二IP地址相比所述第一IP地址发生变化的部分通知给所述对端。
  2. 根据权利要求1所述的方法，其特征在于，将所述第二IP地址通知给所述对端，包括：
    通过所述主机向所述对端发送的数据报文或者TCP/IP协议报文，将所述第二IP地址通知给所述对端，
    其中，所述数据报文或者所述TCP/IP协议报文的源IP地址为所述第二IP地址。
  3. 根据权利要求1所述的方法，其特征在于，将所述发生变化的部分通知给所述对端，包括：
    通过TCP/IP协议报文将所述发生变化的部分通知给所述对端，
    其中，所述发生变化的部分是指所述第二IP地址包含的所述网络地址。
  4. 根据权利要求1所述的方法，其特征在于，获取所述主机在所述第二网络的所述第二IP地址，包括：
    所述主机作为动态主机配置协议(DHCP)客户端向DHCP服务器发送DHCP请求，以获取所述主机在所述第二网络的所述第二IP地址；
    接收所述DHCP服务器返回的所述主机在所述第二网络的所述第二IP地址。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述第一IP地址和所述第二IP地址均为IPv6地址。
  6. 一种主机，其特征在于，包括：
    处理器，以及
    存储有在所述处理器上运行的机器可执行指令的机器可读存储介质，所述处理器执 行所述指令时实现以下操作：
    将所述主机与对端之间建立的TCP/IP连接绑定第一IP地址中的主机地址，以使所述TCP/IP连接在所述第一IP地址因所述主机从第一网络漫游至第二网络而发生改变时继续维持，其中，所述第一IP地址为所述主机在所述第一网络中的IP地址，且包括网络地址和所述主机地址，所述网络地址表示所述主机所在的网段，所述主机地址是指所述主机的设备标识，用于唯一标识所述主机；
    当所述主机从所述第一网络漫游至所述第二网络时，继续维持所述TCP/IP连接，并获取所述主机在所述第二网络的第二IP地址，所述第二IP地址为所述主机在所述第二网络中的IP地址，包括网络地址和所述主机地址；
    将所述第二IP地址通知给所述对端或者将所述第二IP地址相比所述第一IP地址发生变化的部分通知给所述对端。
  7. 根据权利要求6所述的主机，其特征在于，所述处理器通过以下操作实现将所述第二IP地址通知给所述对端，包括：
    通过所述主机向所述对端发送的数据报文或者TCP/IP协议报文，将所述第二IP地址通知给所述对端，
    其中，所述数据报文或者所述TCP/IP协议报文的源IP地址为所述第二IP地址。
  8. 根据权利要求6所述的主机，其特征在于，所述处理器通过以下操作实现将所述发生变化的部分通知给所述对端，包括：
    通过TCP/IP协议报文将所述发生变化的部分通知给所述对端，
    其中，所述发生变化的部分是指所述第二IP地址包含的所述网络地址。
  9. 根据权利要求6所述的主机，其特征在于，所述处理器通过以下操作实现获取所述主机在所述第二网络的所述第二IP地址，包括：
    所述主机作为DHCP客户端向DHCP服务器发送DHCP请求，以获取所述主机在所述第二网络的所述第二IP地址；
    接收所述DHCP服务器返回的所述主机在所述第二网络的所述第二IP地址。
  10. 根据权利要求6至9任一所述的主机，其特征在于，所述第一IP地址和第二IP地址均为IPv6地址。
PCT/CN2019/105634 2018-09-13 2019-09-12 漫游 WO2020052642A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/274,626 US11665266B2 (en) 2018-09-13 2019-09-12 Roaming by binding a host with a device identifier
EP19859679.3A EP3852412B1 (en) 2018-09-13 2019-09-12 Roaming

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811066829.6 2018-09-13
CN201811066829.6A CN110366169B (zh) 2018-09-13 2018-09-13 漫游方法和装置

Publications (1)

Publication Number Publication Date
WO2020052642A1 true WO2020052642A1 (zh) 2020-03-19

Family

ID=68215068

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/105634 WO2020052642A1 (zh) 2018-09-13 2019-09-12 漫游

Country Status (4)

Country Link
US (1) US11665266B2 (zh)
EP (1) EP3852412B1 (zh)
CN (1) CN110366169B (zh)
WO (1) WO2020052642A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070070996A1 (en) * 2005-09-26 2007-03-29 Oran David R Port hopping scheme for peer-to-peer connections
CN101128022A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 终端切换方法及装置、源接入网关地址获取方法及装置
CN101204071A (zh) * 2005-06-23 2008-06-18 Xds有限公司 移动设备网络地址更改的方法及装置
CN101686265A (zh) * 2008-09-26 2010-03-31 凹凸电子（武汉）有限公司 网络设备、网络系统以及建立数据通讯的方法
CN102857985A (zh) * 2012-09-21 2013-01-02 东莞宇龙通信科技有限公司 服务器、终端和网络切换方法
CN103873600A (zh) * 2012-12-10 2014-06-18 中兴通讯股份有限公司 一种网络地址转换穿透方法及设备

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7882247B2 (en) * 1999-06-11 2011-02-01 Netmotion Wireless, Inc. Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments
GB2367980B (en) * 2000-10-09 2004-03-17 Ericsson Telefon Ab L M Mobile hosts
US7644171B2 (en) * 2001-09-12 2010-01-05 Netmotion Wireless, Inc. Mobile networking system and method using IPv4 and IPv6
US8090828B2 (en) * 2002-03-05 2012-01-03 Cisco Technology, Inc. Method and apparatus for reusing DHCP addresses in home addresses of mobile IP clients
US7149225B2 (en) * 2003-03-10 2006-12-12 Cisco Technology, Inc. Arrangement for traversing an IPv4 network by IPv6 mobile nodes via a mobility anchor point
US7649866B2 (en) * 2003-06-24 2010-01-19 Tropos Networks, Inc. Method of subnet roaming within a network
US7453852B2 (en) * 2003-07-14 2008-11-18 Lucent Technologies Inc. Method and system for mobility across heterogeneous address spaces
US7778229B2 (en) * 2005-07-29 2010-08-17 Cisco Technology, Inc. Optimized IP address use in a mobile IP environment
US7680123B2 (en) * 2006-01-17 2010-03-16 Qualcomm Incorporated Mobile terminated packet data call setup without dormancy
US20070189218A1 (en) * 2006-02-11 2007-08-16 Yoshihiro Oba Mpa with mobile ip foreign agent care-of address mode
US8023492B2 (en) * 2007-07-18 2011-09-20 Marvell World Trade Ltd. System and method for allocating an anchoring point for a mobile terminal
US7929557B2 (en) * 2008-11-14 2011-04-19 Juniper Networks, Inc. Summarization and longest-prefix match within MPLS networks
US8380819B2 (en) * 2009-05-14 2013-02-19 Avaya Inc. Method to allow seamless connectivity for wireless devices in DHCP snooping/dynamic ARP inspection/IP source guard enabled unified network
GB201011034D0 (en) * 2010-06-30 2010-08-18 British Telecomm Access network
US8411685B1 (en) * 2010-09-16 2013-04-02 Sprint Communications Company L.P. Managing the allocation of internet protocol addresses in a wireless network
US20120108206A1 (en) * 2010-10-28 2012-05-03 Haggerty David T Methods and apparatus for access control client assisted roaming
CA2773333C (en) * 2011-04-05 2016-11-22 Research In Motion Limited System and method to preserve dialogs in clustered environments in case of node failure
US9264397B2 (en) * 2011-10-18 2016-02-16 Bluecat Networks (Usa) Inc. Method and system for implementing a user network identity address provisioning server
US20130305332A1 (en) * 2012-05-08 2013-11-14 Partha Narasimhan System and Method for Providing Data Link Layer and Network Layer Mobility Using Leveled Security Keys
CN103517264B (zh) * 2012-06-29 2017-04-12 华为终端有限公司 用于切换网络的方法和装置
CN102917339B (zh) * 2012-10-11 2014-06-11 华为技术有限公司 虚拟用户识别模块的实现与通信方法、装置及系统
US10270607B2 (en) * 2013-09-25 2019-04-23 Hewlett Packard Enterprise Development Lp Method and system for roamed client device handling
WO2015164357A1 (en) * 2014-04-21 2015-10-29 Jose Joaquin Garcia-Luna-Aceves Hidden identifiers for demultiplexing and resolution architecture
GB2556745B (en) * 2015-09-23 2019-09-11 Google Llc Systems and methods for mobility management in a distributed software defined network packet core system
CN105897712A (zh) * 2016-04-11 2016-08-24 深圳市信锐网科技术有限公司 基于无线热点的报文转发方法和装置
US10212583B1 (en) * 2017-07-26 2019-02-19 Cisco Technology, Inc. System and method of fast roaming in enterprise fabric networks
KR102326272B1 (ko) * 2017-12-05 2021-11-15 삼성전자주식회사 외부 장치의 네트워크 셋업을 위한 전자 장치 및 그의 동작 방법
US10548052B2 (en) * 2018-01-30 2020-01-28 Comcast Cable Communications, Llc Predictive client mobility session management
US10880895B2 (en) * 2018-05-27 2020-12-29 Brian Gordaychik Variable length downlink control information formats for next generation radio technologies

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101204071A (zh) * 2005-06-23 2008-06-18 Xds有限公司 移动设备网络地址更改的方法及装置
US20070070996A1 (en) * 2005-09-26 2007-03-29 Oran David R Port hopping scheme for peer-to-peer connections
CN101128022A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 终端切换方法及装置、源接入网关地址获取方法及装置
CN101686265A (zh) * 2008-09-26 2010-03-31 凹凸电子（武汉）有限公司 网络设备、网络系统以及建立数据通讯的方法
CN102857985A (zh) * 2012-09-21 2013-01-02 东莞宇龙通信科技有限公司 服务器、终端和网络切换方法
CN103873600A (zh) * 2012-12-10 2014-06-18 中兴通讯股份有限公司 一种网络地址转换穿透方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3852412A4 *

Also Published As

Publication number Publication date
EP3852412A1 (en) 2021-07-21
US11665266B2 (en) 2023-05-30
CN110366169A (zh) 2019-10-22
CN110366169B (zh) 2021-02-26
EP3852412B1 (en) 2024-01-24
EP3852412A4 (en) 2021-12-08
US20220021755A1 (en) 2022-01-20

Similar Documents

Publication Publication Date Title
JP4762581B2 (ja) モバイルコンピューティングデバイスのための仮想私設網構造の再使用
JP4730746B2 (ja) モバイル・インターネット・プロトコルを使用してルーティング・スタックをバイパスするための方法、システム、およびコンピュータ・プログラム
TWI437863B (zh) 異質性ｉｐｖ４網路中之同級間行動能力管理
WO2017000878A1 (zh) 报文处理
JP4722157B2 (ja) ネットワークトラフィックのインテリジェントロードバランシング及びフェイルオーバー
EP2586238B1 (en) Information distribution in a wireless communication system
JP2000183973A (ja) パケットを無線デバイスに送信するステップ
JP2000183972A (ja) 無線アクセス方法
JP2000183975A (ja) デスティネ―ションノ―ドへパケットを分配するル―ティングパスを確立する方法
US9118608B2 (en) Communication apparatus, control method therefor, and computer-readable storage medium
WO2008098439A1 (fr) Procédé et système pour commutation d'acheminement
US11863655B2 (en) Method and system for reliable application layer data transmission through unreliable transport layer connections in a network
JP2018523443A (ja) 要求に基づいてルートを取得する方法およびゲートウェイ
US20190021065A1 (en) Reducing Time Required for Location Lookup When Downlink Packets Arrive By Assisting Preloading of a Location of a Wireless Device Into the IP Advertisement Point (IAP)
Zhang et al. Content delivery in the mobilityfirst future internet architecture
WO2020052642A1 (zh) 漫游
JP5016030B2 (ja) デュアルスタック移動体ノードがＩＰｖ４ネットワーク中でローミングするための方法と装置
US20220345519A1 (en) PFCP Session Load Balancer
TW202249464A (zh) 使用網際網路協定網路於蜂巢式資料封包路由的方法
TW202249465A (zh) 使用網際網路協定網路於蜂巢式資料封包路由的裝置
WO2012019525A1 (zh) 基于hip的通信方法、系统及设备
Davison et al. A split stack approach to mobility-providing performance-enhancing proxies
Kimura et al. Tips: wrapping the sockets api for seamless ip mobility
Sousa et al. Multihoming: a comprehensive review
US12114250B2 (en) Selective importing of UE addresses to VRF in 5G networks

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: 19859679

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019859679

Country of ref document: EP

Effective date: 20210413