WO2008031335A1 - Procede et appareil d'implementation de reseau prive virtuel de couche 1 l1 vpn - Google Patents
Procede et appareil d'implementation de reseau prive virtuel de couche 1 l1 vpn Download PDFInfo
- Publication number
- WO2008031335A1 WO2008031335A1 PCT/CN2007/070195 CN2007070195W WO2008031335A1 WO 2008031335 A1 WO2008031335 A1 WO 2008031335A1 CN 2007070195 W CN2007070195 W CN 2007070195W WO 2008031335 A1 WO2008031335 A1 WO 2008031335A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- virtual
- vpn
- service model
- model
- vpn service
- Prior art date
Links
Classifications
-
- 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/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
- H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
- H04L12/4679—Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
Definitions
- the present invention relates to the field of network communication technologies, and in particular, to a method and apparatus for implementing a virtual private network. Background technique
- OVPN Optical Virtual Private Network
- ASON Automatically Switched Optical Network
- OVPN provides users with a virtual private network (VPN) at the transport layer.
- Virtual Private Network also known as a layer of virtual private network (LI VPN, Layerl VPN).
- the OVPN service is the same as the traditional VPN service, enabling users to flexibly set up their own network topology within the public network while reducing communication costs, and allows operators to divide physical network resources and provide them to the terminal users comprehensively and securely.
- the ability to view and manage their own OVPNs is like having each user own their own optical network. At the same time, OVPN enables operators to optimize bandwidth utilization and gain more business opportunities with less investment to increase revenue.
- the various business models for implementing LI VPN are described in the draft-ietf-llvpn-framework of IETF: Basic Mode and Enhanced Model.
- the enhanced model includes: Enhanced Overlay Model, Virtual Node Model (Virtual Node) , Virtual Link model and VPN peering model (Per VPN Peer).
- CE customer network edge device
- PE carrier network edge device
- Provider Edge Provider Edge
- Multi-service Backbone in the carrier's carrier's carrier scenario, 4 ⁇ may allocate dedicated resources to users, and users can perform performance monitoring on dedicated circuits in the carrier network.
- Virtual Link is used at this time. Or Per VPN Peer model; while in video conferencing (VideoConference), Content distribution, etc.
- the Basic Mode model is used. Different users may have different scenarios. One operator needs to be able to support all scenarios required by the user. That is, one operator needs to be able to support multiple service models to support different application scenarios. Summary of the invention
- the embodiment of the present invention provides a method for implementing a layer of a virtual private network (LI VPN), where at least one virtual PE is created on the edge device PE of the carrier, and the virtual PE performs signaling and routing interaction with the client edge device CE, and supports at least A LI VPN business model.
- LI VPN virtual private network
- An embodiment of the present invention provides a method for implementing a layer of a virtual private network, including:
- At least one virtual PE is created on the operator edge device PE, and the virtual PE performs signaling and routing interaction with the client edge device CE, and supports at least one layer of the virtual private network LI VPN service model.
- An embodiment of the present invention provides a carrier edge device PE device that implements a layer of a virtual private network, including a VPN common processing module, at least one virtual PE, a memory, and a central processing unit.
- the VPN common processing module is configured to implement PE. a public function corresponding to at least one LI VPN service model, creating or deleting a virtual PE corresponding to the LI VPN service model;
- the central processor interacts with the VPN public processing module according to the member information stored in the memory to support the LI VPN service model.
- the embodiment of the present invention further provides a CE device for implementing a layer of a virtual private network LI VPN, including a VPN public processing module, at least one virtual CE, a memory, and a central processor;
- the VPN public processing module is configured to implement a common function of at least one VPN service model on the CE, and create or delete a virtual CE corresponding to the LI VPN service model;
- the memory saves member information of the LI VPN service model
- the central processor interacts with the VPN public processing module according to the member information stored in the memory, and supports the LI VPN service model.
- one or more LI VPN service models are established according to the requirements of the user for the LI VPN application scenario, and may be based on the requirements of the LIVPN service required by the user.
- the VPE and VCE are dynamically established on the PEs and CEs to support one or more service models to meet the application requirements of different users in different scenarios. Because the information between VCEs and VPEs of different VPNs is isolated, it can also ensure the security of information and the effectiveness of resource usage when supporting multiple service models.
- FIG. 1 is a schematic diagram of creating multiple VPEs on one physical PE according to an embodiment of the present invention
- FIG. 2 is a schematic diagram of creating multiple VCEs on one physical CE according to an embodiment of the present invention
- FIG. 4 is a schematic diagram of a process of creating a VPE and a VCE according to an embodiment of the present invention
- FIG. 5 is a schematic diagram of a process of deleting a VPN 1 according to an embodiment of the present invention.
- FIG. 7 is a multi-service model for implementing LI VPN according to another embodiment of the present invention
- FIG. 8 is a multi-service model for implementing LI VPN according to still another embodiment of the present invention
- FIG. 9 is a schematic diagram of a PE device supporting a VPE according to an embodiment of the present invention.
- FIG. 10 is a schematic diagram of a CE device supporting a VCE according to an embodiment of the present invention. detailed description
- FIG. 1 shows a schematic diagram of creating multiple virtual PEs (VPEs, Virtual PEs) on a physical PE.
- VPEs virtual PEs
- VPE-BM virtual PE supporting basic model
- VPE VN supported Virtual PE of virtual node model
- VPE-VL virtual PE supporting virtual link model
- FIG. 2 shows a schematic diagram of creating multiple virtual CEs (VCEs, Virtual CEs) on a single physical CE.
- VCEs virtual CEs
- VCE-BM Virtual CE supporting basic model
- VCE-VN Virtual CE supporting virtual node model
- VCE-VL virtual CE supporting virtual link model
- FIG. 3 is a schematic diagram showing support for multiple service models in an embodiment of the present invention.
- CE1 and CE4 form a VPN1, which uses a dedicated link, and the user's SLA (service)
- the rating agreement specifies that the user can view the performance alarms of the dedicated link. Therefore, the Virtual Link model is used to support VPN1.
- a dedicated link is assigned to VPN1.
- These links are only used for VPN1.
- CE1, CE2, and CE3 form VPN2 for content distribution. No dedicated link resources are allocated.
- the communication link is dynamically applied and deleted. For VPN2, it needs to be supported by the Basic Mode. According to the different needs of users, by creating VPE and VCE, two business models are supported at the same time.
- FIG. 4 shows the process of creating a VPE and VCE, including the steps:
- PE1 receives the VPN1 command to create the virtual link model, and creates VPE1-1;
- PE2 receives the VPN1 command to create the virtual link model, and creates VPE2- 1;
- CE2 receives the VPN1 command to create the virtual link model and creates VCE2-1.
- CE4 receives the VPN1 command to create the virtual link model and creates VCE4.
- the command may be from a virtual private network manager (VPN Manager), that is, the VPN Manager sends a command to create a virtual PE and a virtual CE to the PE and the CE respectively; or the VPN Manager sends a command to create a virtual PE to the PE.
- the PE sends a VCE command to the CE through the interface between the PE and the CE.
- the creation of VPE and VCE can also be done through signaling between the PE and the CE.
- Figure 5 shows the process of deleting VPN1, including the steps:
- PE1 receives the command to delete the VPE corresponding to VPN1, and deletes the corresponding VPE1-1.
- PE2 receives the command to delete the VPE corresponding to VPN1, and deletes the corresponding VPE2- 1;
- CE2 receives the command to delete the VCE corresponding to VPN1, and deletes the corresponding VCE2-1.
- CE4 receives the command to delete the VCE corresponding to VPN1 and deletes the corresponding VCE.
- VPN2 can be created and deleted using the basic model.
- LI VPN services After the VPE and VCE are created, you can use the routing and signaling interaction between the two to support the L1 VPN service. Specifically, there are two ways to implement LI VPN services:
- each VPE has its own independent signaling and routing part.
- Each VPE and VCE on each PE or CE device are independent entities, each with independent signaling processing module and routing processing. Module, its signaling and routing processing module has no shared parts, regardless of these Whether VPE and VCE belong to the same type of service model as VPE and VCE.
- routing information interaction depends on the service model. If it is a basic model, there is no routing information interaction; if it is an enhanced model, there is routing information interaction.
- the signaling processing module between the VPE and the VCE performs signaling interaction to establish, maintain, and delete the LI VPN service.
- a unified service model VPE can be established on the CE and PE for the processing of the common part of the signaling and routing in the same service model.
- Each VCE and VPE interact with the service model instance according to the service model. .
- the basic model is taken as an example.
- One PE supports two basic models of L1 VPN, and one CE supports two basic models of LI VPN.
- a VPE of the PE basic model will be established on the PE, including the PE basic model signaling processing module and the PE basic model routing processing module;
- a VCE of the CE basic model will be established on the CE, including the CE basic model letter. Let the processing module and CE basic model route processing module.
- the VPE and VCE corresponding to the LI VPN of each basic model does not include the signaling and routing processing part, but only maintains its member information. The maintenance of this information is completed by interacting with the PE basic model instance and the CE basic model instance.
- the CE basic model signaling processing module and the PE basic model signaling processing module perform signaling interaction to establish, maintain, and delete services in the LI VPN.
- the virtual link model in the enhanced model is used as an example.
- One PE supports two virtual link models for LI VPN, and one CE supports two virtual link models for LI VPN.
- a VPE of the PE virtual link model will be established on the PE, including the PE virtual link model signaling processing module and the PE virtual link model routing processing module; a CE virtual link model will be established on the CE.
- the VCE includes a CE virtual link model signaling processing module and a CE virtual link model routing processing module.
- the VPE and VCE corresponding to the LI VPN of each virtual link model do not include the signaling and routing processing part, but only maintain the member information.
- the maintenance of this information is through the VCE of the virtual link model of the PE and the VCE of the virtual link model of the CE. Interact to complete.
- the CE virtual link model signaling processing module and the PE virtual link model signaling processing module perform signaling interaction to establish services in the L1VPN. Maintenance and deletion; At the same time, the CE virtual link model routing processing module and the PE virtual link model routing processing module exchange routing information to implement route maintenance and management functions.
- the possibility of supporting multiple service models on a physical CE is relatively small. Therefore, only one service model is supported on a CE. That is, in the embodiment of the present invention, supporting the VCE on the CE is not necessary. In most cases, VPE is only supported on the PE.
- FIG. 9 shows a PE device supporting a VPE in an embodiment of the present invention, including a VPN public processing module, at least one VPE, a memory, and a central processing unit (CPU).
- a VPN public processing module including a VPN public processing module, at least one VPE, a memory, and a central processing unit (CPU).
- CPU central processing unit
- the VPN public processing module is configured to implement the public functions of the LI VPN on the PE, such as automatic discovery, policy configuration, creation and deletion of the VPE, receiving commands issued by the VPN Manager, and distributing the commands to the corresponding VPEs;
- the current VPN member information is stored in the form of a member information table.
- the member information can be obtained through automatic query.
- Each VPE is associated with the VPN member information table of the corresponding VPN.
- the CPU interacts with the content stored in the VPN common processing module and Memory.
- the function of the VPN on the PE is completed.
- the structure of the VPE has been described above, and is not described here. Of course, the structure of the VPE has two different situations as shown in FIG. 6 and FIG. 7 and FIG.
- FIG. 10 shows a CE device supporting VCE, including a VPN common processing module, at least one VPE, a memory, and a central processing unit (CPU).
- a VPN common processing module including a VPN common processing module, at least one VPE, a memory, and a central processing unit (CPU).
- CPU central processing unit
- the VPN common processing module is used to implement the public functions of the VPN on the CE, such as policy configuration, VCE creation and deletion, receiving commands issued by the VPN Manager, and distributing commands to the corresponding VCEs.
- the memory stores the current VPN member information. It is stored in the form of a member information table. The member information can be obtained through automatic query.
- Each VCE is associated with the VPN member information table of the corresponding VPN.
- the CPU interacts with the VPN public processing module and the content stored in the memory to complete the VPN on the CE. Function;
- the structure of VCE has been explained above, and will not be described here.
- the structure of VCE has two different situations as shown in Fig. 6 and Fig. 7 and Fig. 8.
- a suitable service model may be selected according to the requirements of the LIVPN service required by the user, and VPEs and VCEs are dynamically established on the PEs and CEs to support multiple service models to meet user requirements;
- the information between the VCE and the VPE is isolated, so it can guarantee the security of information and the effectiveness of resource usage when supporting multiple service models.
- the program can be implemented by instructing related hardware, and the program can be stored in a computer readable storage medium, such as a ROM/RAM, a magnetic disk, a compact disk, or the like. Alternatively, they may be fabricated into individual integrated circuit modules, or a plurality of modules or steps may be fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
一种实现一层虚拟专用网的方法和装置 本申请要求于 2006 年 09 月 13 日提交中国专利局、 申请号为 200610062588.9、 发明名称为 "一种实现一层虚拟专用网 LI VPN的方法和 装置" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及网络通信技术领域, 尤其涉及一种实现虚拟专用网的方法 和装置。 背景技术
光虚拟专用网 ( OVPN, Optical Virtual Private Network )是光网络向自 动交换光网络( ASON , Automatically Switched Optical Network )转型过程 中出现的新业务应用, OVPN 在传输层为用户提供虚拟专用网 (VPN, Virtual Private Network )业务, 也称为一层虚拟专用网 ( LI VPN, Layerl VPN )。 OVPN业务同传统的 VPN业务一样, 使得用户在减少通信费用的 情况下, 能够在公网内部灵活组建自己的网络拓朴, 并允许运营商对物理 网络资源进行划分, 提供给终端用户全面并安全地查看以及管理各自的 OVPN 的能力, 如同每个用户拥有自己的光网络一样。 同时, OVPN 能够 使运营商优化带宽的利用率, 通过较少的投资获得更多的商业机会从而增 力口收入。
在 IETF的 draft-ietf-llvpn-framework中描述了实现 LI VPN的各种业务 模型: 基本模型(Basic Mode )和增强模型, 增强模型中又包括: 增强的重 叠模型, 虚节点模型( Virtual Node ), 虚连接模型( Virtual Link ) 以及 VPN 对等模型(Per VPN Peer )等。不同模型中,客户网络边沿设备(CE, Custom Edge )和运营商网络边沿设备 ( PE, Provider Edge )之间交互的信息以及 其信令路由方式都有所差异。
另外, 不同的模型对应不同的业务场景, 例如在多业务骨干网
( Multi-service Backbone ), 运营商的运营商 ( Carrier's carrier )场景中 , 4艮 可能给用户分配专用的资源, 用户能够对运营商网络中的专用电路进行性 能监控, 此时要用到 Virtual Link或 Per VPN Peer模型; 而在视频会议
( VideoConference ), 内容分发 ( Content distribution )等场景中, 运营商的 链路资源由各 VPN共享, 此时要用到 Basic Mode模型。 不同的用户可能有 不同的场景需求, 一个运营商需要能够支持用户要求的所有场景; 也即, 一个运营商需要能够支持多种业务模型, 从而支持不同应用场景的需求。 发明内容
本发明实施例提供了一种实现一层虚拟专用网 LI VPN的方法,在运营 商边缘设备 PE上创建至少一个虚拟 PE , 所述虚拟 PE与客户边缘设备 CE 进行信令和路由交互, 支持至少一个 LI VPN业务模型。
本发明实施例提供一种实现一层虚拟专用网的方法, 包括:
在运营商边缘设备 PE上创建至少一个虚拟 PE ,所述虚拟 PE与客户边 缘设备 CE进行信令和路由交互, 支持至少一个一层虚拟专用网 LI VPN业 务模型。
本发明实施例提供一种实现一层虚拟专用网的运营商边缘设备 PE 装 置, 包括 VPN公共处理模块、 至少一个虚拟 PE、 存储器和中央处理器, 所述 VPN公共处理模块, 用于实现 PE上至少一个 LI VPN业务模型 的公共功能, 创建或删除所述 LI VPN业务模型对应的虚拟 PE;
所述存储器中保存所述 LI VPN业务模型的成员信息;
所述中央处理器根据所述存储器中保存的成员信息与所述 VPN公共处 理模块进行交互, 以支持所述 LI VPN业务模型。
本发明实施例还提供一种实现一层虚拟专用网 LI VPN的客户边缘设 备 CE装置, 包括 VPN公共处理模块、 至少一个虚拟 CE、 存储器和中央处 理器;
所述 VPN公共处理模块用于实现 CE上至少一个 VPN业务模型的公共 功能, 创建或删除 LI VPN业务模型对应的虚拟 CE;
所述存储器保存所述 LI VPN业务模型的成员信息;
所述中央处理器根据所述存储器中保存的成员信息与所述 VPN公共处 理模块进行交互, 支持所述 LI VPN业务模型。
本发明实施例提供的方案中,根据用户对 LI VPN应用场景的需求, 建 立一个或多个 LI VPN业务模型,可以根据用户所需 LI VPN服务的要求不
同, 选择合适的业务模型, 在 PE、 CE上动态建立 VPE、 VCE来支持一种 或一种以上的业务模型,从而满足不同场景下不同用户对 LI VPN的应用需 求。 因不同 VPN的 VCE、 VPE之间信息是隔离的, 还能够保证支持多种业 务模型时信息的安全性以及资源使用的有效性。 附图说明
图 1为本发明实施例中在一个物理 PE上创建多个 VPE的示意图; 图 2为本发明实施例中在一个物理 CE上创建多个 VCE的示意图; 图 3为本发明实施例中支持多种业务模型的示意图;
图 4为本发明实施例中创建 VPE和 VCE的过程示意图;
图 5为本发明实施例中删除 VPN1的过程示意图;
图 6为本发明的一个实施例中实现 LI VPN的多业务模型;
图 7为本发明的另一个实施例中实现 LI VPN的多业务模型; 图 8为本发明又一个实施例中实现 LI VPN的多业务模型;
图 9为本发明的实施例中支持 VPE的 PE装置示意图;
图 10为本发明的实施例中支持 VCE的 CE装置示意图。 具体实施方式
下面结合附图和具体实施例进行详细的说明。
图 1所示为在一个物理 PE上创建多个虚拟 PE ( VPE, Virtual PE )的 示意图。 本发明的实施例中, 在一个物理 PE上可根据用户 VPN的应用场 景及 VPN的个数动态创建多个不同类型的 VPE, 例如 VPE— BM (支持基本 模型的虚拟 PE ), VPE VN (支持虚节点模型的虚拟 PE ), VPE— VL (支持虚 链路模型的虚拟 PE)或其它模型的虚拟 PE等。
图 2所示为在一个物理 CE上创建多个虚拟 CE ( VCE, Virtual CE )的 示意图。 本发明的实施例中, 在一个物理 CE上可根据用户 VPN的应用场 景及 VPN的个数动态创建多个不同类型的 VCE: 例如, VCE— BM (支持基 本模型的虚拟 CE ), VCE— VN (支持虚节点模型的虚拟 CE )、 VCE— VL (支 持虚链路模型的虚拟 CE)或其它模型的虚拟 CE。
图 3所示为本发明的实施例中支持多种业务模型的示意图。 其中, CE2 和 CE4之间组成了 VPN1 , 其中用到专用的链路, 在与用户的 SLA (服务
等级协定) 中规定了用户可查看其专用链路的性能告警等信息, 因此, 要 用到 Virtual Link模型对 VPNl 进行支持, 创建 VPN时分配专用链路给 VPN1 , 这些链路只供 VPN1专用。 CE1、 CE2、 CE3间组成了 VPN2, 用于 内容分发, 没有分配专用的链路资源, 其间通信链路是动态申请和删除的, 对于 VPN2, 需通过 Basic Mode模型进行支持。 根据用户的不同需求, 通 过创建 VPE和 VCE, 同时支持两个业务模型。
下面结合图 3、 图 4和图 5对 VCE, VPE的动态创建和删除过程作进 一步说明。 如图 4所示为创建 VPE和 VCE的过程示意图, 包括步骤:
PE1接收到创建釆用 Virtual Link模型的 VPNl的命令, 创建 VPE1-1 ; PE2接收到创建釆用 Virtual Link模型的 VPN1的命令, 创建 VPE2- 1;
CE2接收到创建釆用 Virtual Link模型的 VPNl的命令, 创建 VCE2-1 ; CE4接收到创建釆用 Virtual Link模型的 VPNl的命令, 创建 VCE4。 上述步骤之间并不需要确定的先后顺序。 所述命令, 可以来自虚拟专 用网管理器( VPN Manager ), 即 VPN Manager分别向 PE和 CE下发创建 虚拟 PE和虚拟 CE的命令;也可以由 VPN Manager向 PE下发创建虚拟 PE 的命令, 然后通过 PE和 CE之间的接口, PE向 CE下发创建 VCE的命令。 另外, VPE和 VCE的创建也可以通过 PE和 CE之间的信令完成。
如图 5所示为删除 VPN1的过程示意图, 包括步骤:
PE1接收到删除 VPN1对应的 VPE的命令, 删除对应的 VPE1-1 ;
PE2接收到删除 VPN1对应的 VPE的命令 , 删除对应的 VPE2- 1;
CE2接收到删除 VPN1对应的 VCE的命令, 删除对应的 VCE2-1; CE4接收到删除 VPN1对应的 VCE的命令, 删除对应的 VCE。
同理, 可以对釆用基本模型的 VPN2进行创建和删除。
当 VPE、 VCE创建完成后, 则可以利用二者之间的路由和信令交互, 支持 L1 VPN业务。 具体来说, 实现 LI VPN业务有下述两种方式:
方式一:
如图 6所示, 每个 VPE, VCE有自己独立的信令和路由部分, 每个 PE 或 CE设备上的各个 VPE, VCE都是独立的实体, 各自具有独立的信令处 理模块和路由处理模块, 其信令和路由处理模块没有共享部分, 不管这些
VPE, VCE是否属于同一类业务模型的 VPE, VCE。
VCE和 VPE的路由处理模块间根据业务模型的不同决定是否有路由信 息交互。 如果是基本模型, 则无路由信息交互; 如果为增强模型, 则有路 由信息交互。
VPE和 VCE间的信令处理模块间进行信令的交互进行 LI VPN业务的 建立, 维护和删除。
方式二:
对于同类业务模型在 CE, PE上可建立一个统一的业务模型的 VPE, 用于同类业务模型中信令和路由公共部分的处理, 各 VCE, VPE根据所属 的业务模型, 与业务模型实例进行交互。
如图 7所示, 以基本模型为例, 一个 PE上支持了两个基本模型的 L1 VPN, 一个 CE上支持了两个基本模型的 LI VPN。 此时, 在 PE上将建立 一个 PE基本模型的 VPE, 其中包括 PE基本模型信令处理模块和 PE基本 模型路由处理模块; 在 CE上将建立一个 CE基本模型的 VCE, 其中包括 CE基本模型信令处理模块和 CE基本模型路由处理模块。
每个基本模型的 LI VPN对应的 VPE和 VCE中不包括信令和路由处理 部分, 只是维护其成员信息, 这些信息的维护通过与 PE基本模型实例、 CE 基本模型实例进行交互完成。 CE基本模型信令处理模块和 PE基本模型信 令处理模块进行信令交互,从而对 LI VPN中的业务进行建立,维护和删除。
如图 8所示, 以增强模型中的虚链路模型为例, 一个 PE上支持了两个 虚链路模型的 LI VPN, 一个 CE上支持了两个虚链路模型的 LI VPN。 此 时, 在 PE上将建立一个 PE虚链路模型的 VPE, 其中包括 PE虚链路模型 信令处理模块和 PE虚链路模型路由处理模块; 在 CE上将建立一个 CE虚 链路模型的 VCE,其中包括 CE虚链路模型信令处理模块和 CE虚链路模型 路由处理模块。
每个虚链路模型的 LI VPN对应的 VPE和 VCE中不包括信令和路由处 理部分,只是维护其成员信息,这些信息的维护通过与 PE虚链路模型 VPE、 CE虚链路模型的 VCE进行交互来完成。 CE虚链路模型信令处理模块和 PE 虚链路模型信令处理模块进行信令交互从而对 L1VPN中的业务进行建立,
维护和删除; 同时, CE虚链路模型路由处理模块和 PE虚链路模型路由处 理模块进行路由信息的交互, 实现路由维护和管理功能。
一般而言, 一个物理 CE上支持多种业务模型的可能性比较小, 因此, 一个 CE上通常只支持一种业务模型, 也就是说, 在本发明实施例中, CE 上支持 VCE不是必须的, 大多数情况下, 只在 PE上支持 VPE即可。
图 9所示为本发明的实施例中支持 VPE的 PE装置, 包括 VPN公共处 理模块、 至少一个 VPE、 存储器(Memory )和中央处理器(CPU )。
其中, VPN公共处理模块用于实现 PE上 LI VPN的公共功能, 如自动 发现, 策略配置, VPE的创建删除, 接收 VPN Manager下发的命令, 将命 令分发到对应的 VPE等; Memory中保存了当前 VPN的成员信息, 其以成 员信息表的形式存储, 成员信息可通过自动查询得到, 每个 VPE与其对应 VPN的 VPN成员信息表关联; CPU通过和 VPN公共处理模块及 Memory 中保存的内容交互, 完成 PE上 VPN的功能; VPE的结构已经在上文中进 行说明, 此处不再赘述。 当然, 所述 VPE的结构存在图 6与图 7、 图 8所 示的两种不同情形。
图 10所示为支持 VCE的 CE装置, 包括 VPN公共处理模块、 至少一 个 VPE、 存储器 (Memory )和中央处理器( CPU )。
VPN公共处理模块用于实现 CE上 VPN的公共功能,如策略配置, VCE 的创建删除,接收 VPN Manager下发的命令,将命令分发到对应的 VCE等; Memory中保存了当前 VPN的成员信息, 其以成员信息表的形式存储, 成 员信息可通过自动查询得到, 每个 VCE与其对应 VPN的 VPN成员信息表 关联; CPU通过和 VPN公共处理模块及内存中保存的内容交互, 完成 CE 上 VPN的功能; VCE的结构已经在上文中进行说明, 此处不再赘述。 VCE 的结构存在图 6与图 7、 图 8所示的两种不同情形。
本发明的多个实施例,可以根据用户所需 LI VPN服务的要求不同,选 择合适的业务模型, 动态在 PE、 CE上建立 VPE、 VCE来支持多种业务模 型以满足用户需求; 因不同 VPN的 VCE、 VPE之间信息是隔离的, 所以能 够保证支持多种业务模型时信息的安全性以及资源使用的有效性。
本领域技术人员可以理解, 上述实施例中的全部或部分模块或各步骤
是可以通过程序来指令相关硬件来实现, 所述程序可存储于计算机可读取 存储介质中, 所述存储介质, 如 ROM/RAM、 磁盘、 光碟等。 或者将它们 分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制作成单 个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软件结 合。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围并不局 限于此, 任何熟悉该技术的人在本发明所揭露的技术范围内, 可轻易想到 的变化或替换, 都应涵盖在本发明的保护范围之内。
Claims
1、 一种实现一层虚拟专用网的方法, 其特征在于, 包括:
在运营商边缘设备 PE上创建至少一个虚拟 PE,所述虚拟 PE与客户边 缘设备 CE进行信令和路由交互, 支持至少一个一层虚拟专用网 LI VPN业 务模型。
2、 如权利要求 1所述的方法, 其特征在于, 还包括:
在所述 CE上创建至少一个虚拟 CE, 与所述虚拟 PE进行信令和路由 交互, 支持至少一个 LI VPN业务模型。
3、如权利要求 1所述的方法, 其特征在于, 所述在运营商边缘设备 PE 上创建至少一个虚拟 PE包括:
所述 PE接收到创建所述至少一个 LI VPN业务模型的命令, 创建所述 LI VPN业务模型对应的虚拟 PE。
4、 如权利要求 2所述的方法, 其特征在于, 所述在 CE上创建至少一 个虚拟 CE, 包括:
所述 CE接收到创建所述至少一个 LI VPN业务模型的命令, 创建所述
LI VPN业务模型对应的虚拟 CE。
5、 如权利要求 2所述的方法, 其特征在于, 所述至少一个 L1 VPN业 务模型的虚拟 PE和虚拟 CE之间分别独立地进行信令和路由交互, 支持各 自的 LI VPN业务模型。
6、 如权利要求 2所述的方法, 其特征在于, 所述至少一个 L1 VPN业 务模型的虚拟 PE和虚拟 CE利用 PE业务模型实例和 CE业务模型实例统一 进行信令和路由交互, 支持所述 LI VPN业务模型。
7、 如权利要求 1或 2所述的方法, 其特征在于, 还包括:
删除所述 LI VPN业务模型时,删除所述 LI VPN业务模型对应的 VPE 和 /或 VCE。
8、 一种实现一层虚拟专用网的运营商边缘设备 PE装置, 其特征在于, 包括 VPN公共处理模块、 至少一个虚拟 PE、 存储器和中央处理器,
所述 VPN公共处理模块, 用于实现 PE上至少一个 LI VPN业务模型 的公共功能, 创建或删除所述 LI VPN业务模型对应的虚拟 PE;
所述存储器中保存所述 LI VPN业务模型的成员信息;
所述中央处理器根据所述存储器中保存的成员信息与所述 VPN公共处 理模块进行交互, 以支持所述 LI VPN业务模型。
9、 如权利要求 8所述的运营商边缘设备 PE装置, 其特征在于, 所述 虚拟 PE包括信令处理模块和路由处理模块, 分别进行信令和路由交互, 支 持各自的 LI VPN业务模型。
10、 如权利要求 8所述的运营商边缘设备 PE装置, 其特征在于, 所述 虚拟 PE中, 支持相同的 PE业务模型的虚拟 PE统一进行信令和路由交互, 并维护所述 LI VPN业务模型的成员信息。
11、 一种实现一层虚拟专用网 LI VPN的客户边缘设备 CE装置, 其特 征在于, 包括 VPN公共处理模块、 至少一个虚拟 CE、 存储器和中央处理 哭口.?
所述 VPN公共处理模块用于实现 CE上至少一个 VPN业务模型的公共 功能, 创建或删除 LI VPN业务模型对应的虚拟 CE;
所述存储器保存所述 LI VPN业务模型的成员信息;
所述中央处理器根据所述存储器中保存的成员信息与所述 VPN公共处 理模块进行交互, 支持所述 LI VPN业务模型。
12、 如权利要求 11所述的客户边缘设备 CE装置, 其特征在于, 所述 每个虚拟 CE都包括信令处理模块和路由处理模块,各自独立进行信令和路 由交互, 支持各自的 LI VPN业务模型。
13、 如权利要求 11所述的运营商边缘设备 PE装置, 其特征在于, 所 述虚拟 CE中, 支持相同的 CE业务模型的虚拟 CE统一进行信令和路由交 互, 并维护所述 LI VPN业务模型的成员信息。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07721805A EP1924033B1 (en) | 2006-09-13 | 2007-06-27 | Method and apparatus for implementing a layer1 virtual private network l1 vpn |
ES07721805T ES2383151T3 (es) | 2006-09-13 | 2007-06-27 | Método y equipo para implementar una red privada virtual de capa 1VPN L1 |
AT07721805T ATE549825T1 (de) | 2006-09-13 | 2007-06-27 | Verfahren und vorrichtung zur implementierung eines schicht 1 virtuellen privatnetzes l1 vpn |
US12/028,313 US7864763B2 (en) | 2006-09-13 | 2008-02-08 | Method and device for implementing layer 1 virtual private network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2006100625889A CN101146015B (zh) | 2006-09-13 | 2006-09-13 | 一种实现一层虚拟专用网l1 vpn的方法和装置 |
CN200610062588.9 | 2006-09-13 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/028,313 Continuation US7864763B2 (en) | 2006-09-13 | 2008-02-08 | Method and device for implementing layer 1 virtual private network |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008031335A1 true WO2008031335A1 (fr) | 2008-03-20 |
Family
ID=39183384
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/070195 WO2008031335A1 (fr) | 2006-09-13 | 2007-06-27 | Procede et appareil d'implementation de reseau prive virtuel de couche 1 l1 vpn |
Country Status (6)
Country | Link |
---|---|
US (1) | US7864763B2 (zh) |
EP (1) | EP1924033B1 (zh) |
CN (1) | CN101146015B (zh) |
AT (1) | ATE549825T1 (zh) |
ES (1) | ES2383151T3 (zh) |
WO (1) | WO2008031335A1 (zh) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9674045B2 (en) * | 2014-12-12 | 2017-06-06 | Oracle International Corporation | Methods, systems, and computer readable media for modeling packet technology services using a packet virtual network (PVN) |
US9866408B2 (en) | 2014-12-12 | 2018-01-09 | Oracle International Corporation | Methods, systems, and computer readable media for configuring a flow interface on a network routing element |
US10230589B2 (en) | 2014-12-12 | 2019-03-12 | Oracle International Corporation | Methods, systems, and computer readable media for configuring service networks |
CN107147509B (zh) * | 2016-03-01 | 2022-03-11 | 中兴通讯股份有限公司 | 虚拟专用网业务实现方法、装置及通信系统 |
CN107342820B (zh) * | 2017-01-09 | 2019-06-25 | 烽火通信科技股份有限公司 | 基于模板管理实现volt的方法及系统 |
CN112468325B (zh) * | 2020-11-11 | 2023-07-11 | 广州鲁邦通物联网科技股份有限公司 | 一种可复用的vpn架构和vpn调度方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1614968A (zh) * | 2004-10-29 | 2005-05-11 | 港湾网络有限公司 | 虚拟个人网络系统内部服务器和客户端的通信方法 |
US20050195767A1 (en) * | 2004-03-04 | 2005-09-08 | Moshiur Rahman | Method and apparatus for enabling IP mobility with high speed access and network intelligence in communication networks |
EP1580939A1 (en) * | 2004-03-26 | 2005-09-28 | Nortel Networks Limited | Method and apparatus for determining and allocating network resources to layer 1 virtual private networks |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7653050B2 (en) * | 2002-02-05 | 2010-01-26 | Nortel Networks Limited | Technique for implementing a multi-service packet and optical/TDM virtual private cross-connect |
US7379457B2 (en) * | 2002-06-10 | 2008-05-27 | Nortel Networks Limited | Technique for implementing a virtual private optical switched transport network using virtual private optical/TDM cross-connect technology |
CN1214583C (zh) * | 2002-08-23 | 2005-08-10 | 华为技术有限公司 | 一种三层虚拟私有网络及其构建方法 |
US7894368B2 (en) * | 2002-12-06 | 2011-02-22 | Nippon Telegraph And Telephone Corporation | OVPN system, OVPN terminating device, collective controlling device, and optical communication network |
EP1589708B1 (en) * | 2003-01-31 | 2016-03-09 | Nippon Telegraph And Telephone Corporation | Vpn communication control device, communication control method in vpn, and virtual dedicated network management device |
US20040255028A1 (en) * | 2003-05-30 | 2004-12-16 | Lucent Technologies Inc. | Functional decomposition of a router to support virtual private network (VPN) services |
US20050190757A1 (en) * | 2004-02-27 | 2005-09-01 | Cisco Technology Inc. | Interworking between Ethernet and non-Ethernet customer sites for VPLS |
US7715429B2 (en) * | 2004-12-06 | 2010-05-11 | Hewlett-Packard Development Company, L.P. | Interconnect system for supply chain management of virtual private network services |
US7889738B2 (en) * | 2005-12-21 | 2011-02-15 | Solace Systems Inc. | Shared application inter-working with virtual private networks |
-
2006
- 2006-09-13 CN CN2006100625889A patent/CN101146015B/zh not_active Expired - Fee Related
-
2007
- 2007-06-27 WO PCT/CN2007/070195 patent/WO2008031335A1/zh active Application Filing
- 2007-06-27 EP EP07721805A patent/EP1924033B1/en not_active Not-in-force
- 2007-06-27 ES ES07721805T patent/ES2383151T3/es active Active
- 2007-06-27 AT AT07721805T patent/ATE549825T1/de active
-
2008
- 2008-02-08 US US12/028,313 patent/US7864763B2/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050195767A1 (en) * | 2004-03-04 | 2005-09-08 | Moshiur Rahman | Method and apparatus for enabling IP mobility with high speed access and network intelligence in communication networks |
EP1580939A1 (en) * | 2004-03-26 | 2005-09-28 | Nortel Networks Limited | Method and apparatus for determining and allocating network resources to layer 1 virtual private networks |
CN1614968A (zh) * | 2004-10-29 | 2005-05-11 | 港湾网络有限公司 | 虚拟个人网络系统内部服务器和客户端的通信方法 |
Also Published As
Publication number | Publication date |
---|---|
ATE549825T1 (de) | 2012-03-15 |
EP1924033A1 (en) | 2008-05-21 |
EP1924033A4 (en) | 2009-05-27 |
US20080181223A1 (en) | 2008-07-31 |
EP1924033B1 (en) | 2012-03-14 |
ES2383151T3 (es) | 2012-06-18 |
CN101146015A (zh) | 2008-03-19 |
US7864763B2 (en) | 2011-01-04 |
CN101146015B (zh) | 2010-08-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7290732B2 (ja) | データ転送方法及び関連する装置 | |
CN108092893B (zh) | 一种专线开通方法及装置 | |
WO2021007963A1 (zh) | 路由分发方法及控制器、信息路由方法及网络节点设备 | |
US8085791B1 (en) | Using layer two control protocol (L2CP) for data plane MPLS within an L2 network access node | |
US7447166B1 (en) | Method to distribute IEEE 802.1X authenticated users among multiple broadcast domains | |
TW202026896A (zh) | 在網路路由環境中的非同步物件管理機制 | |
EP2945330B1 (en) | Route management method, route method, network controller and router | |
WO2016066072A1 (zh) | 实现nvo3网络与mpls网络之间通信的方法和装置 | |
US20160134591A1 (en) | VPN Implementation Processing Method and Device for Edge Device | |
WO2015149604A1 (zh) | 一种负载均衡方法、装置及系统 | |
WO2017032300A1 (zh) | 一种数据传输方法、虚拟网络管理装置及数据传输系统 | |
WO2007134551A1 (fr) | Procédé et dispositif noeud de réservation de ressources de réseau | |
WO2013155943A1 (zh) | 一种虚拟网络实现方法及系统 | |
WO2018233580A1 (zh) | 一种网络中建立转发路径的方法、控制器及系统 | |
WO2018019299A1 (zh) | 一种虚拟宽带接入方法、控制器和系统 | |
WO2006069527A1 (fr) | Procede, dispositif et reseau permettant de garantir la qualite de service d'un service pour un acces a large bande | |
WO2023056722A1 (zh) | 一种分布式防火墙定义方法及系统 | |
WO2008031335A1 (fr) | Procede et appareil d'implementation de reseau prive virtuel de couche 1 l1 vpn | |
US11140091B2 (en) | Openflow protocol-based resource control method and system, and apparatus | |
WO2018006704A1 (zh) | 公网ip分配方法、装置以及虚拟化数据中心系统 | |
WO2009082905A1 (fr) | Procédé système et dispositif commutateur permettant l'établissement dynamique de réseau local virtuel de multidiffusion | |
WO2014180199A1 (zh) | 网络建立的方法及控制设备 | |
WO2004071009A1 (fr) | Procede pour determiner une relation entre un routeur de bordure client et un reseau prive virtuel | |
EP3086512B1 (en) | Implementation method and apparatus for vlan to access vf network and fcf | |
WO2021218627A1 (zh) | 一种通信方法及相关设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2007721805 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2007721805 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |