WO2011103840A2 - 虚拟私云的连接方法及隧道代理服务器 - Google Patents

虚拟私云的连接方法及隧道代理服务器 Download PDF

Info

Publication number
WO2011103840A2
WO2011103840A2 PCT/CN2011/072990 CN2011072990W WO2011103840A2 WO 2011103840 A2 WO2011103840 A2 WO 2011103840A2 CN 2011072990 W CN2011072990 W CN 2011072990W WO 2011103840 A2 WO2011103840 A2 WO 2011103840A2
Authority
WO
WIPO (PCT)
Prior art keywords
gateway
tunnel
proxy server
virtual private
private cloud
Prior art date
Application number
PCT/CN2011/072990
Other languages
English (en)
French (fr)
Other versions
WO2011103840A3 (zh
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 PCT/CN2011/072990 priority Critical patent/WO2011103840A2/zh
Priority to CN201180000248.2A priority patent/CN102845123B/zh
Publication of WO2011103840A2 publication Critical patent/WO2011103840A2/zh
Publication of WO2011103840A3 publication Critical patent/WO2011103840A3/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2514Translation of Internet protocol [IP] addresses between local and global IP addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • H04L61/2503Translation of Internet protocol [IP] addresses
    • H04L61/2592Translation of Internet protocol [IP] addresses using tunnelling or encapsulation

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a method for connecting a virtual private cloud and a tunnel proxy server. Background technique
  • the cloud service provider can provide a virtual private cloud service, which allows the user to apply for a series of virtual hosts by logging in to the cloud service provider's website, and the virtual hosts are connected to each other as a Virtual Private Cloud (referred to as:
  • VPC VPC Site (Site).
  • the cloud service provider also allows users to connect their own private sites to the aforementioned VPC sites via the Internet for communication with each other.
  • the user's private site and the VPC site use a private Internet protocol (Internet).
  • Internet private Internet protocol
  • IP Internet Protocol
  • the Internet uses a public IP address. Any two IP addresses in the site that use the private IP address can communicate with each other, but the private IP address cannot be addressed in the public network.
  • the private site of the user cannot communicate with the VPC site through the Internet. .
  • a gateway can be set up on the private site and the VPC site.
  • the two gateways have public IP addresses, which can communicate with each other through the public network, establish a tunnel between the two gateways, and set up a private network.
  • IP packets are encapsulated into public IP packets to implement communication between the two sites.
  • the public IP address is very valuable. If you want to establish a gateway and apply for a public IP address in order to establish communication between the private site and the VPC site, it is expensive and is a kind of public IP address. waste. Summary of the invention
  • the embodiment of the present invention provides a method for connecting a virtual private cloud and a tunnel proxy server, which is used to solve the problem that each user site in the prior art needs to independently set a gateway and apply for a public network IP address, and the system is complicated, and This caused unnecessary waste of the public network IP address.
  • An embodiment of the present invention provides a method for connecting a virtual private cloud, including:
  • the tunnel proxy server receives the virtual private cloud connection request sent by the user station, where the virtual private cloud connection request includes the identity ID of the user site, and the public network protocol IP address of the peer gateway to be connected;
  • the public network IP address of the end gateway establishes a tunnel to the peer gateway, and the tunnel is used by the user station to connect to the virtual private cloud through the tunnel.
  • An embodiment of the present invention provides a tunnel proxy server, including:
  • a receiver configured to receive a virtual private cloud connection request sent by the user station, where the virtual private cloud connection request includes an identity identifier of the user site, and a public network protocol IP address of the peer gateway to be connected;
  • a transmitter configured to send, by the local gateway corresponding to the ID of the user station, a tunnel establishment request that carries the public network IP address of the peer gateway to be connected, so that the local gateway is configured according to the pair
  • the public network IP address of the end gateway establishes a tunnel to the peer gateway, and the tunnel is used by the user station to connect to the virtual private cloud through the tunnel.
  • the tunnel proxy server management user site set at the network operator applies to establish a gateway of the corresponding network operator and a gateway of the virtual private cloud service provider.
  • the tunnel between the user and the virtual private cloud service provider is not required to set up the gateway and apply for the public IP address. Instead, use the gateway of the corresponding network operator and its public IP address to establish a tunnel connection with the gateway of the virtual private cloud service provider. , so that it can communicate with the virtual private cloud. Simplifies the system and saves the public network IP address.
  • FIG. 1 is a flowchart of a method for connecting a virtual private cloud according to an embodiment of the present invention
  • FIG. 2 is a flow chart of a method for connecting a virtual private cloud according to another embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a tunnel proxy server according to an embodiment of the present invention. detailed description
  • connection method of the virtual private cloud may be applicable to, but not limited to, the following scenarios:
  • the user site accesses the Internet through a gateway provided by the network operator, and the gateway of the virtual private cloud service provider
  • the gateways provided by the network operator can be addressed to each other through the public network IP address.
  • FIG. 1 is a flowchart of a method for connecting a virtual private cloud according to an embodiment of the present invention. As shown in FIG. 1, the method includes:
  • Step 101 The tunnel proxy server receives the virtual private cloud connection request sent by the user station.
  • the virtual private cloud connection request includes the identity of the user site (Identity, referred to as ID) and the public IP address of the peer gateway to be connected.
  • ID is used to identify the user site that sends the virtual private cloud connection request, and may be the name, number, serial number, and the like of the user site.
  • the public IP address of the peer gateway to be connected is used to uniquely identify the peer gateway to be connected.
  • the public network IP address of the local gateway can be obtained from the tunnel proxy server of the user site at the opposite end.
  • the user station Before the step 101, the user station sends a request for obtaining the public IP address of the gateway to the tunnel proxy server of the peer end, where the obtaining request carries the ID of the user station, and the tunnel proxy server of the opposite end sends the user site to the user site according to the ID of the user station. Returns the public IP address of the peer gateway corresponding to the ID of the user site.
  • the user station sends a virtual private cloud connection request to the tunnel proxy server of the peer end, where the virtual private cloud connection request carries the ID of the user site, and the tunnel proxy server of the opposite end according to the ID of the user site The user site returns the public IP address of the peer gateway corresponding to the ID of the user site.
  • the tunnel proxy server can be either a network proxy (Network Service Provider, NSP) tunnel proxy server or a virtual private cloud service provider tunnel proxy server.
  • NSP Network Service Provider
  • the tunnel proxy server is the tunnel proxy server of the network operator
  • the local gateway is the gateway of the network operator
  • the peer gateway is the gateway of the virtual private cloud service provider.
  • the tunnel proxy server is the tunnel proxy server of the virtual private cloud service provider
  • the local gateway is the gateway of the virtual private cloud service provider
  • the peer gateway is the gateway of the network operator.
  • the network operator's gateway may have one or more
  • the virtual private cloud service provider's gateway may have one or more.
  • There may be a one-to-one, one-to-many or many-to-one relationship between a user site and a gateway.
  • multiple user sites correspond to one gateway, which can save the public network IP address.
  • Step 102 The tunnel proxy server sends a tunnel establishment request carrying the public network IP address of the peer gateway to be connected to the local gateway corresponding to the ID of the user site according to the virtual private cloud connection request, so that the local gateway is configured according to the peer gateway.
  • the public network IP address establishes a tunnel to the peer gateway, and the tunnel is used for the user site to connect to the virtual private cloud through the tunnel.
  • the tunnel proxy server When the tunnel proxy server is the tunnel proxy server of the network operator, the tunnel proxy server sends a tunnel establishment request to the local gateway corresponding to the ID of the user station. In other words, there is a corresponding relationship between the ID of the user site and the gateway of the network operator.
  • the tunnel proxy server obtains the corresponding local gateway in the corresponding relationship according to the ID of the user site, and carries the public IP address of the peer gateway.
  • the tunnel establishment request is sent to the corresponding local gateway.
  • the correspondence between the ID of the user site and the gateway of the network operator may be stored in the tunnel proxy server of the network operator, or may be operated by the network.
  • the merchant's tunnel proxy server is obtained from other network devices.
  • the tunnel proxy server When the tunnel proxy server is the tunnel proxy server of the virtual private cloud service provider, the tunnel proxy server sends a tunnel establishment request to the local gateway corresponding to the ID of the user site. In other words, there is a correspondence between the ID of the user site and the gateway of the virtual private cloud service provider.
  • the tunnel proxy server obtains the corresponding local gateway in the corresponding relationship according to the ID of the user site, and carries the public gateway of the opposite gateway.
  • a tunnel establishment request of the network IP address is sent to the corresponding local gateway.
  • the correspondence between the ID of the user site and the gateway of the virtual private cloud service provider may be stored on the tunnel proxy server of the virtual private cloud service provider, or may be from the other network by the tunnel proxy server of the virtual private cloud service provider. Obtained at the equipment.
  • the method for connecting a virtual private cloud in the embodiment of the present invention by using a tunnel proxy server at a network operator to manage a user site to apply for establishing a tunnel between a gateway of the corresponding network operator and a gateway of the virtual private cloud service provider.
  • the user site does not need to set the gateway and apply for the public network IP address, but uses the gateway of the network operator to which it belongs and its public network IP address to establish a tunnel connection with the gateway of the virtual private cloud service provider, thereby enabling virtual Private cloud to communicate.
  • FIG. 2 is a flowchart of a method for connecting a virtual private cloud according to another embodiment of the present invention. This embodiment is a specific application scenario of the embodiment shown in FIG. As shown in Figure 2, the method includes:
  • Step 201 The network agent's tunnel proxy server receives the virtual private cloud connection request sent by the user station.
  • the virtual private cloud connection request includes the ID of the user site and the public IP address of the gateway of the virtual private cloud service provider to be connected.
  • the public network IP address of the gateway of the virtual private cloud service provider, the user site can be obtained as follows:
  • the user station sends a request for obtaining the public network IP address of the gateway to the tunnel proxy server of the virtual private cloud service provider, and obtains the ID of the user site in the request, which is provided by the virtual private cloud service provider.
  • the tunnel proxy server returns the public IP address of the corresponding gateway to the user site according to the ID of the user site.
  • step 204 is performed before step 201, after step 204, the virtual private cloud service provider
  • the tunnel proxy server obtains the public network IP address of the gateway of the corresponding virtual private cloud service provider according to the ID of the user site, and feeds back the public network IP address of the gateway of the virtual private cloud service provider corresponding to the user site to the user site.
  • the public network IP address of the gateway of the virtual private cloud service provider may also be obtained by using the method of obtaining the public network IP address of the sending gateway.
  • a user site can be composed of multiple user devices.
  • the virtual private cloud connection request may be automatically sent by the user equipment in the user site, or may be sent by the user equipment in the user site according to the user's operation.
  • Step 202 The tunnel proxy server of the network operator sends a tunnel establishment request to the corresponding local gateway according to the ID of the user station and the correspondence between the ID of the user station and the gateway of the network operator.
  • the tunnel establishment request carries the public network IP address of the gateway of the virtual private cloud service provider.
  • the local gateway is the gateway of the network operator.
  • the network proxy's tunnel proxy server can preset the correspondence between the ID of the user site and the gateway of the network operator. According to the ID of the user site, the public network IP address of the gateway of the corresponding network operator can be directly obtained. As shown in Table 1:
  • the above correspondence may also be obtained from the network operator's tunnel proxy server from other network devices.
  • Step 203 The network operator's gateway receives the tunnel establishment request sent by the network operator's tunnel proxy server, and creates a network operator according to the public network IP address of the gateway of the virtual private cloud service provider carried in the tunnel establishment request. The gateway to the gateway of the virtual private cloud service provider's gateway.
  • the mapping between the ID of the tunnel and the user site may also be saved.
  • the private network IP packet can be sent between the user site and the gateway.
  • the IP address of the private network IP packets of multiple user sites may be the same. of.
  • the gateway receives a private network IP address sent from the user site whose user ID is Sitel, it encapsulates it into a public IP packet.
  • the tunnel ID is tunnel 1.
  • the public network IP packet header is removed, and the private network IP packet is obtained.
  • the tunnel ID is obtained as the tunnel 1 according to the public network IP packet header, and the private network IP packet is sent to the user site whose ID is Sitel. Effectively solve the above possible problems.
  • the correspondence between the ID of the tunnel and the user site can also be saved on the tunnel proxy server.
  • the virtual private cloud connection request sent by the user station to the network agent's tunnel proxy server may further include a QoS parameter, which may be a tunnel traffic limit, a tunnel bandwidth limit, etc., to guarantee the service. quality.
  • a QoS parameter which may be a tunnel traffic limit, a tunnel bandwidth limit, etc., to guarantee the service. quality.
  • the network operator's tunnel proxy server instructs the local gateway to provide the corresponding service for the user site.
  • Step 204 The tunnel proxy server of the virtual private cloud service provider receives the virtual private cloud connection request sent by the user station.
  • the virtual private cloud connection request includes the ID of the user site and the public network IP address of the gateway of the network operator to be connected.
  • the ID of the user site at the virtual private cloud service provider may be different from the ID at the network operator.
  • the ID of the user site to be carried is the ID of the user site identified by the virtual private cloud service provider. If the virtual private cloud connection request is sent to the network operator, the ID of the carried user site is the identifier of the network operator.
  • the public network IP address of the network operator's gateway, the user site can be obtained as follows:
  • the tunnel proxy server of the network operator obtains the public network IP address of the gateway of the corresponding network operator according to the ID of the user station, and the gateway of the network operator corresponding to the user station The network IP address is fed back to the user site.
  • the public network IP address of the gateway of the network operator can also be obtained by using the following method for sending the public IP address of the gateway.
  • the user station sends a request for obtaining the public network IP address of the gateway to the tunnel proxy server of the network operator, and obtains the ID of the user site carried in the request, and the network carries the network.
  • the tunnel proxy server of the business obtains the public IP address of the gateway of the network operator corresponding to the user site in the corresponding relationship between the user site and the gateway according to the received request, and feeds back to the user. Site.
  • Step 205 The tunnel proxy server of the virtual private cloud service provider sends a tunnel establishment request to the corresponding local gateway according to the ID of the user site and the correspondence between the ID of the user site and the gateway of the virtual private cloud service provider.
  • the tunnel establishment request carries the public network IP address of the network operator's gateway.
  • the local gateway is the gateway of the virtual private cloud service provider.
  • the tunnel proxy server of the virtual private cloud service provider may preset the correspondence between the ID of the user site and the gateway of the virtual private cloud service provider, and directly obtain the corresponding virtual private cloud service provider according to the ID of the user site.
  • the public IP address of the gateway as shown in Table 2:
  • the above correspondence may also be obtained from other network devices by the tunnel proxy server of the virtual private cloud service provider.
  • Step 206 The gateway of the virtual private cloud service provider receives the tunnel establishment request of the tunnel proxy server of the virtual private cloud service provider, and creates a virtual private according to the public network IP address of the gateway of the network operator carried in the tunnel establishment request. The tunnel of the cloud service provider's gateway to the network operator's gateway.
  • the method for connecting a virtual private cloud in the embodiment of the present invention by using a tunnel proxy server at a network operator to manage a user site to apply for establishing a tunnel between a gateway of the network operator to which the network operator belongs and a gateway of the virtual private cloud service provider.
  • the user site does not need to set the gateway and apply for the public network IP address, but uses the gateway of the network operator to which it belongs and its public network IP address to establish a tunnel connection with the gateway of the virtual private cloud service provider, thereby enabling virtual Private cloud to communicate.
  • Multiple user sites can be shared A gateway is used to share a public IP address. Each user site does not need to have a public IP address. This avoids the waste of the public IP address.
  • FIG. 3 is a schematic structural diagram of a tunnel proxy server according to an embodiment of the present invention.
  • the tunnel proxy server includes: a receiver 301 and a transmitter 302.
  • the receiver 301 is configured to receive a virtual private cloud connection request sent by the user site, where the virtual private cloud connection request includes an identity identifier of the user site, and a public network protocol IP address of the peer gateway to be connected; where the user site
  • the ID is used to identify the user site that sends the virtual private cloud connection request, and may be the name, number, serial number, etc. of the user site.
  • the public IP address of the peer gateway to be connected is used to uniquely identify the peer gateway to be connected.
  • the transmitter 302 is configured to send a tunnel establishment request that carries the public network IP address of the peer gateway to the local gateway, so that the local gateway establishes a tunnel to the opposite gateway according to the public network IP address of the opposite gateway, and the tunnel is used for the tunnel.
  • the user site is connected to the virtual private cloud through a tunnel.
  • the tunnel proxy server may further include: an IP obtaining module, where the IP obtaining module is configured to send a public network IP address of a gateway that carries the ID of the user station at the receiving user station. After obtaining the request, the public network IP address of the local gateway corresponding to the ID of the user site is returned to the user site.
  • the transmitter 302 of the tunnel proxy server may be further configured to: return, to the user site, a public network IP address of the local gateway corresponding to the ID of the user site.
  • the tunnel proxy server is a tunnel proxy server of the network operator, the local gateway is a gateway of the network operator, and the peer gateway is a gateway of the virtual private cloud service provider.
  • the tunnel proxy server is a tunnel proxy server of the virtual private cloud service provider, the local gateway is a gateway of the virtual private cloud service provider, and the peer gateway is a gateway of the network operator.
  • the network operator's gateway may have one or more, and the virtual private cloud service provider's gateway may have one or more.
  • multiple user sites correspond to one gateway, which can save the public network IP address.
  • the tunnel proxy server can preset the correspondence between the ID of the user site and the gateway, according to the ID of the user site. Obtain the public IP address of the corresponding gateway directly. As shown in Table 3:
  • the above correspondence may also be obtained from other network devices by the virtual private cloud service provider/network operator's tunnel proxy server.
  • the tunnel proxy server is a tunnel proxy server of the network operator
  • the local gateway is a gateway of the network operator
  • the virtual private cloud connection request received by the receiver 301 may further include: a QoS parameter.
  • the tunnel proxy server may further include: an indication module, configured to indicate that the local gateway provides a corresponding service to the user site according to the QoS parameter.
  • the mapping between the ID of the tunnel and the user site may also be saved.
  • the private network IP address can be sent between the user site and the gateway.
  • the IP address of the private network IP packets of multiple user sites may be the same.
  • the gateway receives a private network IP address sent from the user site whose site ID is Sitel, the gateway encapsulates it into a public IP packet.
  • the tunnel ID is tunnel 1.
  • the public network IP packet header is removed, and the private network IP packet is obtained.
  • the tunnel ID is obtained as the tunnel 1 and the private IP address of the 4 bar is sent to the user site whose site ID is Site 1. Effectively solve the above possible problems.
  • the correspondence between the tunnel ID and the user site can also be saved on the tunnel proxy server.
  • the tunnel proxy server in the embodiment of the present invention manages the user site to establish a tunnel between the gateway of the network operator to which the network operator belongs and the gateway of the virtual private cloud service provider through the tunnel proxy server set at the network operator, so that the user site Instead of setting up the gateway and applying for the public IP address, you can use the gateway of the network operator and its public IP address to establish a tunnel connection with the gateway of the virtual private cloud service provider, so that it can be connected with the virtual private cloud. Communication. Multiple user sites can share one The gateways share a public IP address. Each user site does not need to have a public IP address. This avoids the waste of the public IP address.

Landscapes

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

Description

虚拟私云的连接方法及 P遂道代理服务器
技术领域
本发明实施例涉及通信技术领域, 尤其涉及一种虚拟私云的连接方法及 隧道代理服务器。 背景技术
现有技术中, 云服务提供商可以提供一种虚拟私云服务, 这种虚拟私云 服务允许用户通过登陆云服务提供商的网站, 申请一系列虚拟主机, 这些虚 拟主机互相连接起来, 作为一个虚拟私云 ( Virtual Private Cloud, 简称为:
VPC ) 站点 (Site ) 。 云服务提供商还允许用户将自己的私有站点通过互联 网与上述 VPC站点连接起来以进行彼此之间的通信。
其中, 用户的私有站点与 VPC站点使用的是私网互联网协议 ( Internet
Protocol, 简称为: IP ) 地址, 而互联网使用的是公网 IP地址。 使用私网 IP 地址的站点内任意两个 IP地址之间是可以通信的, 但是私网 IP 艮文无法在 公网内寻址 (addressing ) , 用户的私有站点与 VPC站点之间无法通过互联 网通信。这时可以在私有站点和 VPC站点上分别设一个网关,这两个网关具 有公网 IP地址, 可以通过公网彼此通信, 在两个网关之间建立隧道, 将私网
IP报文封装到公网 IP报文中实现两个站点之间的通信。
公网 IP地址是非常宝贵的, 如果为了建立私有站点与 VPC站点之间的 通信,每一个用户都要去设置网关并申请公网 IP地址的话,耗资巨大而且是 对公网 IP地址的一种浪费。 发明内容
本发明实施例提供一种虚拟私云的连接方法及隧道代理服务器, 用以解决 现有技术中每个用户站点均需独立设置网关、 申请公网 IP地址, 系统复杂, 并 造成公网 IP地址的不必要浪费。
本发明实施例提供一种虚拟私云的连接方法, 包括:
隧道代理服务器接收用户站点发送的虚拟私云连接请求, 所述虚拟私云连 接请求包括所述用户站点的身份标识 ID, 以及待连接的对端网关的公网互联网 协议 IP地址;
所述隧道代理服务器向与所述用户站点的 ID相对应的本端网关发送携带所 述待连接的对端网关的公网 IP地址的隧道建立请求, 以使所述本端网关根据所 述对端网关的公网 IP地址建立向所述对端网关的隧道, 所述隧道用于所述用户 站点通过所述隧道与虚拟私云连接。
本发明实施例提供一种隧道代理服务器, 包括:
接收器, 用于接收用户站点发送的虚拟私云连接请求, 所述虚拟私云连接 请求包括所述用户站点的身份标识 ID , 以及待连接的对端网关的公网互联网协 议 IP地址;
发送器, 用于向与所述用户站点的 ID相对应的本端网关发送携带所述待 连接的对端网关的公网 IP地址的隧道建立请求, 以使所述本端网关根据所述 对端网关的公网 IP地址建立向所述对端网关的隧道, 所述隧道用于所述用户 站点通过所述隧道与虚拟私云连接。
本发明实施例的虚拟私云的连接方法及隧道代理服务器, 通过设置在网络 运营商处的隧道代理服务器管理用户站点申请建立其对应的网络运营商的网关 与虚拟私云服务提供商的网关之间的隧道, 使得用户站点不必自行设置网关并 申请公网 IP地址,而是使用其对应的网络运营商的网关及其公网 IP地址建立与 虚拟私云服务提供商的网关之间的隧道连接, 从而可以与虚拟私云进行通信。 简化了系统, 节约了公网 IP地址。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案, 下面将对实施 例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见地, 下面描 述中的附图是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出 创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明一个实施例提供的虚拟私云的连接方法流程图;
图 2为本发明另一个实施例提供的虚拟私云的连接方法交互流程图; 图 3为本发明一个实施例提供的隧道代理服务器的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本发明 实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中 的实施例, 本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其 他实施例, 都属于本发明保护的范围。
需要说明的是, 本发明实施例提供的虚拟私云的连接方法可以但不限于应 用于如下所述的场景: 用户站点通过网络运营商提供的网关接入互联网, 虚拟 私云服务提供商的网关与网络运营商提供的网关之间可以通过公网 IP地址彼此 寻址。
图 1为本发明一个实施例提供的虚拟私云的连接方法流程图, 如图 1所示, 该方法包括:
步骤 101 : 隧道代理服务器接收用户站点发送的虚拟私云连接请求。
其中, 虚拟私云连接请求中包括用户站点的身份标识(Identity, 简称为: ID ) 以及待连接的对端网关的公网 IP地址。 其中的用户站点的 ID用于标识发 送虚拟私云连接请求的用户站点, 可以是用户站点的名称、 编号、 序列号等信 息。待连接的对端网关的公网 IP地址用于唯一标识待连接的对端网关。可选的, 本端网关的公网 IP地址可以是用户站点自对端的隧道代理服务器获取的。例如, 在步骤 101之前, 用户站点向对端的隧道代理服务器发送网关的公网 IP地址的 获得请求, 该获得请求中携带用户站点的 ID, 对端的隧道代理服务器根据用户 站点的 ID, 向所述用户站点返回与用户站点的 ID对应的对端网关的公网 IP地 址。 又如, 在步骤 101 之前, 用户站点向对端的隧道代理服务器发送虚拟私云 连接请求, 该虚拟私云连接请求中携带用户站点的 ID, 对端的隧道代理服务器 根据用户站点的 ID ,向所述用户站点返回与用户站点的 ID对应的对端网关的公 网 IP地址。
这里需要说明的是, 隧道代理服务器既可以为网络运营商( Network Service Provider, 简称为: NSP ) 的隧道代理服务器, 也可以为虚拟私云服务提供商的 隧道代理服务器。 当隧道代理服务器为网络运营商的隧道代理服务器时, 本端 网关为网络运营商的网关, 对端网关为虚拟私云服务提供商的网关。 当隧道代 理服务器为虚拟私云服务提供商的隧道代理服务器时, 本端网关为虚拟私云服 务提供商的网关, 对端网关为网络运营商的网关。 网络运营商的网关可以有一 个或者多个, 虚拟私云服务提供商的网关可以有一个或者多个。 某一个用户站 点与网关之间可以存在一对一、 一对多或者多对一的关系。 优选的, 多个用户 站点对应于一个网关, 可以节约公网 IP地址。
步骤 102: 隧道代理服务器根据虚拟私云连接请求向用户站点的 ID对应的 本端网关发送携带有待连接的对端网关的公网 IP地址的隧道建立请求, 以使本 端网关根据上述对端网关的公网 IP地址建立向对端网关的隧道, 该隧道用于用 户站点通过该隧道与虚拟私云连接。
当隧道代理服务器为网络运营商的隧道代理服务器时, 该隧道代理服务器 向用户站点的 ID对应的本端网关发送隧道建立请求。 换言之, 用户站点的 ID 与网络运营商的网关之间存在对应关系, 隧道代理服务器根据用户站点的 ID, 在对应关系中获得相应的本端网关, 并将携带有对端网关的公网 IP地址的隧道 建立请求发送给该相应的本端网关。 上述用户站点的 ID与网络运营商的网关之 间的对应关系可以保存在网络运营商的隧道代理服务器上, 也可以由网络运营 商的隧道代理服务器从其他网络设备获得。
当隧道代理服务器为虚拟私云服务提供商的隧道代理服务器时, 该隧道代 理服务器向用户站点的 ID对应的本端网关发送隧道建立请求。 换言之, 用户站 点的 ID与虚拟私云服务提供商的网关之间存在对应关系, 隧道代理服务器根据 用户站点的 ID, 在对应关系中获得相应的本端网关, 并将携带有对端网关的公 网 IP地址的隧道建立请求发送给该相应的本端网关。 上述用户站点的 ID与虚 拟私云服务提供商的网关之间的对应关系可以保存在虚拟私云服务提供商的隧 道代理服务器上, 也可以由虚拟私云服务提供商的隧道代理服务器从其他网络 设备处获得。
本发明实施例的虚拟私云的连接方法, 通过设置在网络运营商处的隧道代 理服务器管理用户站点申请建立其对应的网络运营商的网关与虚拟私云服务提 供商的网关之间的隧道, 使得用户站点不必自行设置网关并申请公网 IP地址, 而是使用其所属网络运营商的网关及其公网 IP地址建立与虚拟私云服务提供商 的网关之间的隧道连接, 从而可以与虚拟私云进行通信。
图 2 为本发明另一个实施例提供的虚拟私云的连接方法交互流程图, 该实 施例为图 1所示实施例的一种具体应用场景。 如图 2所示, 该方法包括:
步骤 201: 网络运营商的隧道代理服务器接收用户站点发送的虚拟私云连接 请求。
该虚拟私云连接请求中包括用户站点的 ID , 以及待连接的虚拟私云服务提 供商的网关的公网 IP地址。 其中, 虚拟私云服务提供商的网关的公网 IP地址, 用户站点可以通过如下方式获得:
若步骤 201先于步骤 204执行, 用户站点向虚拟私云服务提供商的隧道代 理服务器发送网关的公网 IP地址的获得请求, 获得请求中携带用户站点的 ID, 由虚拟私云服务提供商的隧道代理服务器根据用户站点的 ID将对应的网关的公 网 IP地址返回给用户站点。
若步骤 204先于步骤 201执行, 则在步骤 204之后, 虚拟私云服务提供商 的隧道代理服务器根据用户站点的 ID获得对应的虚拟私云服务提供商的网关的 公网 IP地址,将该用户站点对应的虚拟私云服务提供商的网关的公网 IP地址反 馈给用户站点。 当然, 这种情况下也可以釆用发送网关的公网 IP地址的获得请 求的方式获取虚拟私云服务提供商的网关的公网 IP地址。
用户站点可以由多个用户设备组成。 虚拟私云连接请求可以是用户站点中 的用户设备自动发送的, 也可以是用户站点中的用户设备根据用户的操作发送 的。
步骤 202: 网络运营商的隧道代理服务器根据用户站点的 ID、 以及用户站 点的 ID与网络运营商的网关的对应关系,向对应的本端网关发送隧道建立请求。
该隧道建立请求中携带虚拟私云服务提供商的网关的公网 IP地址。 本端网 关为网络运营商的网关。 网络运营商的隧道代理服务器中可以预设用户站点的 ID与网络运营商的网关之间的对应关系,根据用户站点的 ID可以直接获得其对 应的网络运营商的网关的公网 IP地址。 如表 1所示的内容:
表 1
Figure imgf000008_0001
上述对应关系也可以由网络运营商的隧道代理服务器从其他网络设备处获 付。
步骤 203: 网络运营商的网关接收到网络运营商的隧道代理服务器发送的隧 道建立请求, 根据隧道建立请求中携带的虚拟私云服务提供商的网关的公网 IP 地址, 创建一个网络运营商的网关向虚拟私云服务提供商的网关的隧道。
一种可选的实施方式下, 网关建立了隧道之后, 还可以保存隧道的 ID与用 户站点之间的对应关系。 用户站点与网关之间可以发送私网 IP报文, 当一个网 关为多个用户站点提供服务时, 多个用户站点的私网 IP报文的地址可能是相同 的。当网关收到一个从用户站点的 ID为 Sitel的用户站点发送的私网 IP 文时, 将其封装到一个公网 IP报文中, 该隧道 ID为隧道 1。 当收到一个公网 IP报文 时, 去掉公网 IP报文头, 得到私网 IP报文。 并根据公网 IP报文头得到隧道 ID 为隧道 1 , 把私网 IP报文发送到用户站点的 ID为 Sitel的用户站点上。 有效解 决了上述可能存在的问题。 当然还可以将隧道的 ID与用户站点之间的对应关系 保存在隧道代理服务器上。
可扩展的实施方式下, 用户站点发送给网络运营商的隧道代理服务器的虚 拟私云连接请求中还可以包括服务质量 QoS参数,该参数可以为隧道流量限制、 隧道带宽限制等等, 以保障服务质量。 当虚拟私云连接请求中携带 QoS参数时, 网络运营商的隧道代理服务器会指示本端网关为用户站点提供相应的服务。
步骤 204:虚拟私云服务提供商的隧道代理服务器接收用户站点发送的虚拟 私云连接请求。
该虚拟私云连接请求中包括用户站点的 ID、 以及待连接的网络运营商的网 关的公网 IP地址。 用户站点在虚拟私云服务提供商处的 ID可能与在网络运营 商处的 ID是彼此不同的, 在发送虚拟私云连接请求时, 如果该虚拟私云连接请 求是发送给虚拟私云服务提供商的, 携带的用户站点的 ID为虚拟私云服务提供 商处标识该用户站点的 ID, 如果该虚拟私云连接请求发送给网络运营商的, 携 带的用户站点的 ID为网络运营商处标识该用户站点的 ID。其中, 网络运营商的 网关的公网 IP地址, 用户站点可以通过如下方式获得:
若步骤 201先于步骤 204执行, 网络运营商的隧道代理服务器在根据用户 站点的 ID获得对应的网络运营商的网关的公网 IP地址后, 将该用户站点对应 的网络运营商的网关的公网 IP地址反馈给用户站点。 当然, 这种情况下也可以 釆用下述的, 发送网关的公网 IP地址的获得请求的方式获取网络运营商的网关 的公网 IP地址。
若步骤 204先于步骤 201执行, 则用户站点发送网关的公网 IP地址的获得 请求给网络运营商的隧道代理服务器, 获得请求中携带用户站点的 ID, 网络运 营商的隧道代理服务器根据接收到的获得请求, 根据用户站点的 ID, 在用户站 点与网关之间的对应关系中获得用户站点对应的网络运营商的网关的公网 IP地 址, 并反馈给用户站点。
步骤 205: 虚拟私云服务提供商的隧道代理服务器根据用户站点的 ID, 以 及用户站点的 ID与虚拟私云月良务提供商的网关的对应关系, 向对应的本端网关 发送隧道建立请求。
该隧道建立请求中携带网络运营商的网关的公网 IP地址。 本端网关为虚拟 私云服务提供商的网关。 虚拟私云服务提供商的隧道代理服务器中可以预设用 户站点的 ID与虚拟私云服务提供商的网关之间的对应关系,根据用户站点的 ID 可以直接获得其对应的虚拟私云服务提供商的网关的公网 IP地址, 如表 2所示 的内容:
表 2
Figure imgf000010_0001
上述对应关系也可以由虚拟私云服务提供商的隧道代理服务器从其他网络 设备处获得。
步骤 206:虚拟私云服务提供商的网关接收到虚拟私云服务提供商的隧道代 理服务器的隧道建立请求, 根据隧道建立请求中携带的网络运营商的网关的公 网 IP地址, 创建一个虚拟私云服务提供商的网关向网络运营商的网关的隧道。
本发明实施例的虚拟私云的连接方法, 通过设置在网络运营商处的隧道代 理服务器管理用户站点申请建立其所属的网络运营商的网关与虚拟私云服务提 供商的网关之间的隧道, 使得用户站点不必自行设置网关并申请公网 IP地址, 而是使用其所属网络运营商的网关及其公网 IP地址建立与虚拟私云服务提供商 的网关之间的隧道连接, 从而可以与虚拟私云进行通信。 多个用户站点可以共 用一个网关,共用一个公网 IP地址,每个用户站点不需要单独拥有公网 IP地址, 避免了公网 IP地址的浪费。
图 3为本发明一个实施例提供的隧道代理服务器的结构示意图, 如图 3所 示, 该隧道代理服务器包括: 接收器 301和发送器 302。 其中, 接收器 301用于 接收用户站点发送的虚拟私云连接请求, 虚拟私云连接请求包括用户站点的身 份标识 ID , 以及待连接的对端网关的公网互联网协议 IP地址; 其中的用户站点 的 ID用于标识发送虚拟私云连接请求的用户站点, 可以是用户站点的名称、 编 号、 序列号等信息。 待连接的对端网关的公网 IP地址用于唯一标识待连接的对 端网关。 发送器 302用于向本端网关发送携带有对端网关的公网 IP地址的隧道 建立请求, 以使本端网关根据对端网关的公网 IP地址建立向对端网关的隧道, 隧道用于用户站点通过隧道与虚拟私云连接。
一种实施方式下, 在上述实施方式的基础上, 该隧道代理服务器还可以包 括: IP获得模块; 该 IP获得模块用于在接收到用户站点发送携带用户站点的 ID 的网关的公网 IP地址的获得请求后, 向用户站点返回用户站点的 ID对应的本 端网关的公网 IP地址。
另一种实施方式下, 在上述实施方式的基础上, 该隧道代理服务器的发送 器 302还可以用于: 向用户站点返回与用户站点的 ID对应的本端网关的公网 IP 地址。
一种实施方式下, 隧道代理服务器为网络运营商的隧道代理服务器, 本端 网关为网络运营商的网关, 对端网关为虚拟私云服务提供商的网关。 另一种实 施方式下, 该隧道代理服务器为虚拟私云服务提供商的隧道代理服务器, 本端 网关为虚拟私云服务提供商的网关, 对端网关为网络运营商的网关。 网络运营 商的网关可以有一个或者多个, 虚拟私云服务提供商的网关可以有一个或者多 个。 某一个用户站点与网关之间可以存在一对一、 一对多或者多对一的关系。 优选的, 多个用户站点对应于一个网关, 可以节约公网 IP地址。 隧道代理月良务 器中可以预设用户站点的 ID与网关之间的对应关系, 根据用户站点的 ID可以 直接获得其对应的网关的公网 IP地址。 如表 3所示的内容:
表 3
Figure imgf000012_0001
上述对应关系也可以由虚拟私云服务提供商 /网络运营商的隧道代理服务器 从其他网络设备处获得。
在上述实施方式的基础上, 隧道代理服务器为网络运营商的隧道代理服务 器, 本端网关为网络运营商的网关, 该接收器 301 接收到的虚拟私云连接请求 中还可以包括: QoS 参数。 相应的, 隧道代理服务器还可以包括: 指示模块, 用于指示本端网关根据该 QoS参数为用户站点提供相应的服务。
一种可选的实施方式下, 网关建立了隧道之后, 还可以保存隧道的 ID与用 户站点之间的对应关系。 用户站点与网关之间可以发送私网 IP 艮文, 当一个网 关为多个用户站点提供服务时, 多个用户站点的私网 IP报文的地址可能是相同 的。当网关收到一个从用户站点的 ID为 Sitel的用户站点发送的私网 IP 文时, 将其封装到一个公网 IP报文中, 该隧道 ID为隧道 1。 当收到一个公网 IP报文 时, 去掉公网 IP报文头, 得到私网 IP报文。 并根据公网 IP报文头得到隧道 ID 为隧道 1 , 4巴私网 IP 艮文发送到用户站点的 ID为 Site 1的用户站点上。 有效解 决了上述可能存在的问题。 当然还可以将隧道的 ID与用户站点之间的对应关系 保存在隧道代理服务器上。
本发明实施例的隧道代理服务器, 通过设置在网络运营商处的隧道代理服 务器管理用户站点申请建立其所属的网络运营商的网关与虚拟私云服务提供商 的网关之间的隧道, 使得用户站点不必自行设置网关并申请公网 IP地址, 而是 使用其所属网络运营商的网关及其公网 IP地址建立与虚拟私云服务提供商的网 关之间的隧道连接, 从而可以与虚拟私云进行通信。 多个用户站点可以共用一 个网关, 共用一个公网 IP地址, 每个用户站点不需要单独拥有公网 IP地址, 避 免了公网 IP地址的浪费。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤可 以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读取存 储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤; 而前述的存储 介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是: 以上实施例仅用以说明本发明的技术方案, 而非对其限 制; 尽管参照前述实施例对本发明进行了详细的说明, 本领域的普通技术人员 应当理解: 其依然可以对前述各实施例所记载的技术方案进行修改, 或者对其 中部分技术特征进行等同替换; 而这些修改或者替换, 并不使相应技术方案的 本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种虚拟私云的连接方法, 其特征在于, 包括:
隧道代理服务器接收用户站点发送的虚拟私云连接请求, 所述虚拟私云连 接请求包括所述用户站点的身份标识 ID, 以及待连接的对端网关的公网互联网 协议 IP地址;
所述隧道代理服务器根据所述虚拟私云连接请求向与所述用户站点的 ID 相对应的本端网关发送携带所述待连接的对端网关的公网 IP 地址的隧道建立 请求,以使所述本端网关根据所述对端网关的公网 IP地址建立向所述对端网关 的隧道, 所述隧道用于所述用户站点通过所述隧道与虚拟私云连接。
2、根据权利要求 1所述的方法, 其特征在于, 所述待连接的对端网关的公 网 IP地址为,对端的隧道代理服务器在接收到用户站点发送的携带用户站点的 ID的网关的公网 IP地址的获得请求后, 向所述用户站点返回的与所述用户站 点的 ID对应的对端网关的公网 IP地址。
3、根据权利要求 1所述的方法, 其特征在于, 所述待连接的对端网关的公 网 IP地址为,对端的隧道代理服务器在接收到用户站点发送的携带用户站点的
ID的虚拟私云连接请求后, 向所述用户站点返回的与所述用户站点的 ID对应 的对端网关的公网 IP地址。
4、根据权利要求 1所述的方法, 其特征在于, 所述隧道代理服务器为网络 运营商的隧道代理服务器, 所述本端网关为网络运营商的网关, 所述虚拟私云 连接请求中还包括: 服务质量 QoS参数;
相应的,所述本端网关根据所述对端网关的公网 IP地址建立向所述对端网 关的隧道之后, 所述方法还包括:
所述隧道代理服务器指示所述本端网关根据所述 QoS参数为所述用户站点 提供相应的服务。
5、根据权利要求 1至 3任一所述的方法, 其特征在于, 所述隧道代理服务 器为网络运营商的隧道代理服务器, 所述本端网关为网络运营商的网关, 所述 对端网关为虚拟私云服务提供商的网关; 或者, 所述隧道代理服务器为虚拟私云服务提供商的隧道代理服务器, 所 述本端网关为虚拟私云服务提供商的网关,所述对端网关为网络运营商的网关。
6、 一种隧道代理服务器, 其特征在于, 包括:
接收器, 用于接收用户站点发送的虚拟私云连接请求, 所述虚拟私云连接 请求包括所述用户站点的身份标识 ID , 以及待连接的对端网关的公网互联网协 议 IP地址;
发送器,用于向与所述用户站点的 ID相对应的本端网关发送携带所述待连 接的对端网关的公网 IP地址的隧道建立请求,以使所述本端网关根据所述对端 网关的公网 IP地址建立向所述对端网关的隧道,所述隧道用于所述用户站点通 过所述隧道与虚拟私云连接。
7、 根据权利要求 6所述的隧道代理服务器, 其特征在于, 还包括: IP地 址获得模块,用于在接收到所述用户站点发送的携带用户站点的 ID的网关的公 网 IP地址的获得请求后, 向所述用户站点返回与所述用户站点的 ID对应的本 端网关的公网 IP地址。
8、根据权利要求 6所述的隧道代理服务器, 其特征在于, 所述发送器还用 于:向所述用户站点返回与所述用户站点的 ID对应的本端网关的公网 IP地址。
9、根据权利要求 6所述的隧道代理服务器, 其特征在于, 所述隧道代理服 务器为网络运营商的隧道代理服务器, 所述本端网关为网络运营商的网关, 所 述接收器接收到的虚拟私云连接请求中还包括: 服务质量 QoS参数;
相应的, 所述隧道代理服务器还包括: 指示模块, 用于指示所述本端网关 根据所述 QoS参数为所述用户站点提供相应的服务。
10、 根据权利要求 6至 8中任一所述的隧道代理服务器, 其特征在于, 所 述隧道代理服务器为网络运营商的隧道代理服务器, 所述本端网关为网络运营 商的网关, 所述对端网关为虚拟私云服务提供商的网关;
或者, 所述隧道代理服务器为虚拟私云服务提供商的隧道代理服务器, 所 述本端网关为虚拟私云服务提供商的网关,所述对端网关为网络运营商的网关。
PCT/CN2011/072990 2011-04-19 2011-04-19 虚拟私云的连接方法及隧道代理服务器 WO2011103840A2 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2011/072990 WO2011103840A2 (zh) 2011-04-19 2011-04-19 虚拟私云的连接方法及隧道代理服务器
CN201180000248.2A CN102845123B (zh) 2011-04-19 2011-04-19 虚拟私云的连接方法及隧道代理服务器

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/072990 WO2011103840A2 (zh) 2011-04-19 2011-04-19 虚拟私云的连接方法及隧道代理服务器

Publications (2)

Publication Number Publication Date
WO2011103840A2 true WO2011103840A2 (zh) 2011-09-01
WO2011103840A3 WO2011103840A3 (zh) 2012-04-19

Family

ID=44507283

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072990 WO2011103840A2 (zh) 2011-04-19 2011-04-19 虚拟私云的连接方法及隧道代理服务器

Country Status (2)

Country Link
CN (1) CN102845123B (zh)
WO (1) WO2011103840A2 (zh)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013052115A1 (en) 2011-10-04 2013-04-11 Amazon Technologies, Inc. Techniques for accessing logical networks via a programmatic service call
WO2013056585A1 (zh) * 2011-10-18 2013-04-25 华为技术有限公司 一种虚拟私云接入认证方法及相关装置
WO2014059787A1 (zh) * 2012-10-19 2014-04-24 华为技术有限公司 通信连接方法、通信装置及通信系统
CN104184727A (zh) * 2014-07-31 2014-12-03 华为数字技术(成都)有限公司 一种消息传输的方法和装置
CN104320258A (zh) * 2014-10-24 2015-01-28 西安未来国际信息股份有限公司 一种云计算服务接入网关的方法
US10339791B2 (en) 2007-06-12 2019-07-02 Icontrol Networks, Inc. Security network integrated with premise security system
CN111464609A (zh) * 2020-03-27 2020-07-28 北京金山云网络技术有限公司 数据通信方法、装置及电子设备
CN114584606A (zh) * 2022-04-29 2022-06-03 阿里云计算有限公司 端云通信方法及设备
CN114679370A (zh) * 2021-05-20 2022-06-28 腾讯云计算(北京)有限责任公司 一种服务器托管方法、装置、系统及存储介质
CN114938318A (zh) * 2022-05-11 2022-08-23 浪潮云信息技术股份公司 基于弹性公网ip的跨区域对等连接实现方法
CN115208884A (zh) * 2022-07-13 2022-10-18 四三九九网络股份有限公司 一种本地和云端网络通信的方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105471596B (zh) * 2014-08-04 2019-05-07 新华三技术有限公司 网络管理的方法和装置
CN111030912B (zh) * 2018-10-09 2021-02-12 华为技术有限公司 虚拟私有云vpc之间互通的方法
CN109889621B (zh) * 2019-01-18 2021-07-16 北京百度网讯科技有限公司 虚拟私有云服务的配置方法和装置
CN112738284B (zh) * 2021-04-01 2021-06-04 腾讯科技(深圳)有限公司 服务集成中的数据传输方法、装置、设备及存储介质
CN115314448B (zh) * 2022-08-11 2023-12-05 北京百度网讯科技有限公司 用于接入云网络的方法和装置、电子设备、计算机介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026547A (zh) * 2006-02-22 2007-08-29 中兴通讯股份有限公司 一种将Intranet中的IPv6主机接入全球IPv6网络的方法及系统
US20100125903A1 (en) * 2008-11-19 2010-05-20 Zscaler, Inc. Traffic redirection in cloud based security services
CN101730074A (zh) * 2009-04-28 2010-06-09 中兴通讯股份有限公司 链式连接建立方法、服务网关及分组数据网网关

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1901539A (zh) * 2005-07-24 2007-01-24 中兴通讯股份有限公司 一种多媒体业务隧道穿越nat的方法
CN101394331A (zh) * 2007-09-21 2009-03-25 华为技术有限公司 非3gpp接入网漫游附着、漫游退网方法与系统及漫游系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101026547A (zh) * 2006-02-22 2007-08-29 中兴通讯股份有限公司 一种将Intranet中的IPv6主机接入全球IPv6网络的方法及系统
US20100125903A1 (en) * 2008-11-19 2010-05-20 Zscaler, Inc. Traffic redirection in cloud based security services
CN101730074A (zh) * 2009-04-28 2010-06-09 中兴通讯股份有限公司 链式连接建立方法、服务网关及分组数据网网关

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10339791B2 (en) 2007-06-12 2019-07-02 Icontrol Networks, Inc. Security network integrated with premise security system
WO2013052115A1 (en) 2011-10-04 2013-04-11 Amazon Technologies, Inc. Techniques for accessing logical networks via a programmatic service call
EP2748715A1 (en) * 2011-10-04 2014-07-02 Amazon Technologies, Inc. Techniques for accessing logical networks via a programmatic service call
CN104011702A (zh) * 2011-10-04 2014-08-27 亚马逊科技公司 用于经编程性服务呼叫访问逻辑网络的技术
EP2748715A4 (en) * 2011-10-04 2015-04-01 Amazon Tech Inc TECHNIQUES FOR ACCESSING LOGIC NETWORKS THROUGH A PROGRAMMATIC SERVICE CALL
WO2013056585A1 (zh) * 2011-10-18 2013-04-25 华为技术有限公司 一种虚拟私云接入认证方法及相关装置
WO2014059787A1 (zh) * 2012-10-19 2014-04-24 华为技术有限公司 通信连接方法、通信装置及通信系统
CN104184727A (zh) * 2014-07-31 2014-12-03 华为数字技术(成都)有限公司 一种消息传输的方法和装置
CN104320258B (zh) * 2014-10-24 2018-02-02 西安未来国际信息股份有限公司 一种云计算服务接入网关的方法
CN104320258A (zh) * 2014-10-24 2015-01-28 西安未来国际信息股份有限公司 一种云计算服务接入网关的方法
CN111464609A (zh) * 2020-03-27 2020-07-28 北京金山云网络技术有限公司 数据通信方法、装置及电子设备
CN114679370A (zh) * 2021-05-20 2022-06-28 腾讯云计算(北京)有限责任公司 一种服务器托管方法、装置、系统及存储介质
CN114679370B (zh) * 2021-05-20 2024-01-12 腾讯云计算(北京)有限责任公司 一种服务器托管方法、装置、系统及存储介质
CN114584606A (zh) * 2022-04-29 2022-06-03 阿里云计算有限公司 端云通信方法及设备
CN114584606B (zh) * 2022-04-29 2022-08-02 阿里云计算有限公司 端云通信方法及设备
CN114938318A (zh) * 2022-05-11 2022-08-23 浪潮云信息技术股份公司 基于弹性公网ip的跨区域对等连接实现方法
CN114938318B (zh) * 2022-05-11 2024-03-26 浪潮云信息技术股份公司 基于弹性公网ip的跨区域对等连接实现方法
CN115208884A (zh) * 2022-07-13 2022-10-18 四三九九网络股份有限公司 一种本地和云端网络通信的方法
CN115208884B (zh) * 2022-07-13 2023-04-25 四三九九网络股份有限公司 一种本地和云端网络通信的方法

Also Published As

Publication number Publication date
CN102845123A (zh) 2012-12-26
WO2011103840A3 (zh) 2012-04-19
CN102845123B (zh) 2015-07-08

Similar Documents

Publication Publication Date Title
WO2011103840A2 (zh) 虚拟私云的连接方法及隧道代理服务器
US10652086B2 (en) Converging IOT data with mobile core networks
EP2579544B1 (en) Methods and apparatus for a scalable network with efficient link utilization
WO2021073565A1 (zh) 业务服务提供方法及系统
US11153207B2 (en) Data link layer-based communication method, device, and system
US10454880B2 (en) IP packet processing method and apparatus, and network system
WO2014075312A1 (zh) 一种网络穿越服务的提供方法、装置及系统
WO2019157968A1 (zh) 一种通信方法、装置及系统
WO2021073555A1 (zh) 业务服务提供方法及系统、远端加速网关
WO2011137842A1 (zh) 一种基于cgn实体的数据传输方法、cgn实体、网关及系统
WO2017166936A1 (zh) 一种实现地址管理的方法、装置、aaa服务器及sdn控制器
WO2014114058A1 (zh) 一种数据报文转发方法、用户驻地设备和系统
WO2012022169A1 (zh) 一种网络地址转换的管理方法及装置
US20180302479A1 (en) Handling at least one communication exchange between a telecommunications network and at least one user equipment
WO2011144083A2 (zh) 策略控制方法及设备
CN104821909A (zh) 端对端的数据传输方法和系统
CN112073244A (zh) 基于tr069协议的消息处理方法及系统
WO2011144138A1 (zh) 实现路由聚合的方法、装置和系统
US10742751B2 (en) User based mDNS service discovery
EP3414969A1 (en) Method for converging iot data with mobile core
CN102075588B (zh) 一种实现网络地址转换nat穿越的方法、系统和设备
EP3073691B1 (en) Method and device for improving qos
WO2015096734A1 (zh) 一种业务数据的下行传输方法及分组数据网关
WO2014169590A1 (zh) 一种数据业务通信方法、设备及系统
WO2011160390A1 (zh) 代理网络设备的管理方法和系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180000248.2

Country of ref document: CN

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

Ref document number: 11746882

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11746882

Country of ref document: EP

Kind code of ref document: A2