WO2011113381A2 - 业务实例映射方法、装置和系统 - Google Patents
业务实例映射方法、装置和系统 Download PDFInfo
- Publication number
- WO2011113381A2 WO2011113381A2 PCT/CN2011/073322 CN2011073322W WO2011113381A2 WO 2011113381 A2 WO2011113381 A2 WO 2011113381A2 CN 2011073322 W CN2011073322 W CN 2011073322W WO 2011113381 A2 WO2011113381 A2 WO 2011113381A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- area network
- local area
- virtual local
- service instance
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/17—Interaction among intermediate nodes, e.g. hop by hop
-
- 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/4645—Details on frame tagging
- H04L12/465—Details on frame tagging wherein a single frame includes a plurality of VLAN tags
- H04L12/4662—Details on frame tagging wherein a single frame includes a plurality of VLAN tags wherein a VLAN tag represents a service instance, e.g. I-SID in PBB
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
Definitions
- the embodiments of the present invention relate to the field of communications technologies, and in particular, to a service instance mapping method, apparatus, and system. Background technique
- Cloud computing under the support of virtualization technology can provide flexible resource pools for computing, storage, and application services.
- a major development trend in cloud computing is to build a network architecture with a large-capacity, non-blocking data center, on the basis of which it can support the deployment of various business applications.
- Network devices need support for larger clusters of servers, as well as greater migration in the case of virtual machine applications and business continuity during the migration process. Therefore, cloud computing needs to meet the following three network requirements:
- Data Center (Data Center; DC) traffic characteristics are internal horizontal traffic (inter-server traffic) greater than vertical traffic (intermediate server and external customer traffic), and the internal horizontal traffic bursts Large, cannot be planned in advance.
- the prior art network architecture within the data center tends to construct a non-converged internal interconnect in the form of a fat tree. Under the fat tree network architecture, multiple equal-cost paths between nodes in the network need to be utilized from the control plane to meet the requirements of non-blocking switching, which can solve the increasing lateral traffic conflict problem in the data center.
- large L2 that is, the data link layer, also known as the second layer
- second layer the use of large L2 (that is, the data link layer, also known as the second layer) network supports larger servers (cluster) and virtual machine migration.
- the traditional L2 technology cannot support multiple network paths.
- the network with the spanning-tree protocol (STP) related technology has a low effective path utilization for the entire network.
- STP spanning-tree protocol
- the scope requires a larger L2 network. Big L2 network can Improve the migration scope of virtual machines and achieve a wide range of server sharing.
- the public cloud needs the network to support the multi-tenant identification capabilities in order to control the tenants.
- a large number of service instances are needed for multi-tenant identification.
- How to support more tenant services on network devices is also a problem, such as: A data center with a 500K virtual machine needs support from more than 10K service instances. ability.
- TRILL Internet Engineering Task Force
- IEEE Institute of Electrical and Electronics Engineers
- the basic principle of the two is: Calculate the shortest path forwarding of the Layer 2 link by using the Intermediate System to Intermediate System (ISIS) on the Layer 2 link according to the port link connection (Shortest Path First; : SPF ) , which results in a shortest path across devices.
- ISIS Intermediate System to Intermediate System
- SPF Shortest Path First
- TRILL defines the TRILL header, and encapsulates the user's Layer 2 packet in the TRILL header and forwards it hop by hop. 802.
- laq is the shortest path bridge (Shortest). Path Bridging; Abbreviation: SPB) utilizes the 802.1 ah-defined Mac bearer MAC (MacInMac) encapsulation format, and defines a specific multicast header extension according to the protocol requirements.
- the inner MAC of the MacInMac header is the user's Layer 2 packet.
- the control plane of the TRILL protocol is relatively small compared to the SPB, and the equal cost multi-path (ECMP) of the hop-by-hop can balance the bandwidth of the network;
- the current service instance of the TRILL protocol is the virtual local area network (VLAN) identifier of the 802. lq in the packet.
- the total number of bits is 12 bits.
- the SPB protocol mainly performs multi-path load balancing through service portals, and can globally plan service traffic. It can support 16M bit (bits) service instances, and its control plane calculation is larger than TRILL.
- the TRILL protocol encapsulates the Layer 2 packet of the user through the TRILL header.
- the TRILL header contains the VLAN ID (outer VLAN) of the network transport node, and the ISIS is combined with the interconnected link according to the VLAN ID.
- the intermediate node of the forwarding path performs selective learning according to whether it has the service instance (the inner VLAN of the packet is encapsulated in the corresponding packet), and forwards the packet to the user port at the destination node.
- the TRILL protocol is a forwarding path.
- the SPB uses the MacInMac encapsulation to encapsulate the user's Layer 2 packets, and carries the user packets between the network devices through the external BMAC+BVLAN, and the user's service identifier passes the ISID in a specific I-TAG in the MacInMac header. (24 bits) to identify.
- the SPB performs forwarding learning according to the MAC+ISID.
- the user packet can be in multiple forms, including the UN-TAG, single TAG, and dual TAG. In the forwarding plane of the SPB, multiple BVLANs form a plurality of equivalent forwarding planes.
- the user access side can flexibly specify mapping rules to map user packets to the corresponding forwarding plane.
- mapping rules Once the mapping relationship of the ingress is specified, the user packet arrives at the destination node device along the calculated end-to-end fixed path.
- the biggest difference between the SPB protocol and the TRILL protocol is that the forwarding path of the SPB protocol is end-to-end. As determined by the end, the multi-path load burden needs to be divided in the ingress-to-input traffic and mapped to different forwarding planes to share; and the TRILL protocol is a process of routing the equivalent path hop by hop on the forwarding path.
- the SPB protocol load-sharing traffic model is fixed routing from the portal.
- the SPB protocol is fixed. The way is not to ensure the maximum traffic load balancing, and the data center itself is uncertain of the burst traffic, and there is no clear traffic model to make a good pre-planning mapping. Therefore, the SPB protocol is more prone to congestion. Hot spot.
- the SPB protocol fixed routing is prone to more ECMP, and the effective path utilization in the network is low when the end-to-end planning path is used; and the TRILL protocol is hop-by-hop shortest path distribution.
- the situation can make better use of the effective path in the network.
- the interconnected ECMP of its internal nodes increases with the increase of the network scale (the device capacity is certain), and it is increasingly difficult to fully utilize the network by using the SPB protocol to calculate the fixed end-to-end path of the entry.
- the TRILL protocol has the advantage of ECMP equalization on a hop-by-hop basis.
- the embodiments of the present invention provide a service instance mapping method, device, and system, which are used to solve the defect that the TRILL protocol supports fewer service instances in the prior art, and implements more service instances.
- An embodiment of the present invention provides a service instance mapping method, including:
- the service instance identifier is mapped to the service tag of the >3 ⁇ 4 text.
- the embodiment of the invention further provides a service instance mapping device, including:
- An association module configured to associate a service instance of the second layer with a service access port of the service instance, and determine a correspondence between the service access port and the service instance identifier
- the mapping module is configured to map the service instance identifier into a service tag of the packet.
- the embodiment of the present invention further provides a service instance mapping system, including: at least one data center; and the data center includes the service instance mapping device according to any one of the embodiments of the present invention.
- the service instance mapping method, device, and system of the embodiment of the present invention after associating the service instance of the service layer with the service access port, can map the service instance identifier corresponding to the service access port to the service label of the service.
- the service tag carries the service instance identifier, which can include a larger service tag support capability, and can support multiple service instances, which can meet the needs of multi-tenancy in a large-scale public cloud environment; extended control protocol support, TRILL protocol Expansion can meet greater business development capabilities.
- FIG. 1 is a flowchart of a service instance mapping method according to Embodiment 1 of the present invention
- Figure lb is a TRILL message used in the service instance mapping method provided by the first embodiment of the present invention.
- Figure lc is a schematic diagram of a packet encapsulation format of QinQ in the service instance mapping method according to the first embodiment of the present invention.
- FIG. 1 is another schematic diagram of an 802. lq encapsulation format used by a TRILL packet in a service instance mapping method according to Embodiment 1 of the present invention
- Figure le is a schematic diagram of a state machine for establishing a neighbor of a P2P extended in a service instance mapping method according to Embodiment 1 of the present invention
- FIG. 2a is a schematic diagram of an application scenario of a service instance mapping method according to Embodiment 2 of the present invention.
- FIG. 2b is a schematic diagram of another application scenario of a service instance mapping method according to Embodiment 2 of the present invention.
- FIG. 3 is a schematic structural diagram of a service instance mapping apparatus according to Embodiment 3 of the present invention
- FIG. 4 is a schematic structural diagram of a service instance mapping apparatus according to Embodiment 4 of the present invention. detailed description
- Figure la is a flowchart of a service instance mapping method according to Embodiment 1 of the present invention, as shown in Figure la
- the service instance mapping method may specifically include:
- Step 101 Associate a service instance of the second layer with a service access port of the service instance, and determine a correspondence between the service access port and the service instance identifier.
- the service instance in the embodiment of the present invention is a layer 2 (data link layer) network service, where different service instances are in a layer 2 isolation state in the network, service access ports and service instances of the service instance. Associations can be specified in the form of command configuration. E.g:
- each service instance corresponds to a globally unique service instance identifier, where the service instance identifier is composed of a numeric number, a string alias, and the like.
- the service instance ID can be mapped to the data packet.
- Business tags are passed between devices.
- the tenant ID corresponds to the ID of the tenant in the multi-tenancy scenario.
- a tenant may lease multiple Layer 2 service instances to meet the requirements of their service applications. That is, the multi-tenant tenant ID and service instance ID may be one-to-many relationships.
- Step 102 Map the service instance identifier to a service tag of the text.
- the TRILL control protocol is used as an example to improve the spatial distribution of the traffic in the network.
- the format of the TRILL packet is shown in Table 1.
- the TRILL message in Table 1 includes: 6 bytes (Bytes) of outer destination MAC (OuterDMAC), 6 bytes of outer source MAC (OuterSMAC), 4 bytes of outer VLAN. Tag (OuterVlanTAG), 4-byte TRILL Head, in addition, User Pkt is the user's 802.1q message, and finally 4-byte frame check and frame check sequence (Frame Check Sequence; Abbreviation: FCS).
- the outer MAC address is the bridge MAC address of the device, and is the bridge MAC address of the two adjacent devices in the unicast packet. When the broadcast packet is used, the source MAC address is the ingress node bridge MAC, and the destination MAC address is a specific multicast MAC address.
- the device ID based on the packet forwarding routing is defined in the TRILL header.
- the format of the TRILL header is as follows:
- TRILL Eth - type is the Ethernet type of TRILL
- V is the version of TRILL, which is "0" before expansion. If it is found that the version other than “0” may be directly lost Discard the message and modify it to "1" after expansion.
- M is whether the message is a multicast flag, "0" is unicast, " ⁇ , is multicast.
- Op-Length is the length of the TRILL header extension option, in four-byte units, up to 124
- the option definition for the byte, the first byte of each option for the option area follows the format in Table 3 below:
- the CHbH bit is ' ⁇ , indicating that the option is hop-by-hop, and CItE is ⁇ , indicating that the option is end-to-end.
- the device IDs of the Ingress and Egress are respectively a 16-bit RBridge Nickname.
- the unicast message "M" flag is "0"
- "Ingress Rbridge nickname” and “Egress Rbridge nickname” are respectively aliases for the ingress and egress of the network device; and when the message is broadcast, the "M” flag is "1”
- "Ingress Rbridge nickname” is the entry device alias
- "Egress Rbridge nickname” is the device alias of the broadcast tree root node used.
- FIG. lb is a schematic diagram of an 802.1q encapsulation format used by a TRILL packet in a service instance mapping method according to the first embodiment of the present invention.
- VLAN TAG VLAN TAG
- TPID Tag Protocol Identifier
- TCI 2-byte tag control information
- TPID 8100 (hexadecimal)
- TCI contains 3-bit priority information (Priority Information; referred to as: PRI
- PRI To indicate the priority, 1 bit Congestion Factor Information (CFI) to indicate whether congestion has been experienced, the last VLAN field (ie, the inner VLAN field of TRILL) can hold a 12-bit VLAN ID.
- CFI Congestion Factor Information
- the broadcast packet can be cut according to the service instance (inner VLAN) of the downstream node. Therefore, in TRILL In the network, the VLAN ID saved in the inner VLAN field can be used as the identifier of the service instance of the user and the label of the broadcast packet path. In the TRILL network, the VLAN ID saved in the inner VLAN field is used as the service instance identifier and the label of the broadcast packet forwarding path is 12 bits, which can support no more than 4094 inner VLANs. The label of the service instance and the forwarding path in the TRILL protocol is the VLAN ID saved in the inner VLAN field. Therefore, the space capacity of the larger service instance can be obtained based on the definition of the service label extended by the inner VLAN field. .
- Extended service tags can use 20 bits, and these 20 bits can support 1M service instances.
- the network node size should be controlled within 1K as much as possible, thereby controlling the interface and switching capacity that the network device can actually provide.
- the 1M service instance can meet the service application requirements of the 1K network node, and has Larger support for future network scale expansion potential. The following two examples can be used to extend the resulting business tag:
- Example 1 Combining the 802.1q packet encapsulation format with the extension option of the TRILL header can be extended. Get support for 20-bit service tag support.
- the user packet in the TRILL protocol is encapsulated in the 802. lq packet format, and the VLAN field in the TCI domain of the 802.1q packet (that is, the inner VLAN field of the TRILL) is used to store the lower 12 bits of the service label, and the TRILL header is extended.
- the option is the other upper 8 bits of the service tag.
- 12 bits of the inner VLAN field of TRILL can be used as the upper 12 bits
- the option of the extended TRILL header is used as the lower 8 bits, or other available combinations can be used.
- the extended option can be extended by using the Type Length Value (TLV), which occupies 4 bytes.
- TLV Type Length Value
- the first byte of the extended option of the TRILL header can be defined according to the header format specified by the TRILL protocol.
- CHbH is the hop-by-hop flag
- CItE is the end-to-end flag, which defines the way the option is carried. Since a unique service instance identifier is used within a single TRILL domain,
- CHbH can be "0"
- CItE can be "1”
- the remaining 6 bits of Reserved are "0".
- the second byte can be type information (Type), which can be tentatively set to "1".
- the third byte can be the length of the information field (Length), which is counted in bytes and is used to define the length of the following options. The value can be "1”.
- the fourth byte can be the upper 8 bits of the service tag (Lable High8).
- Table 4 There is only one example of the extended option format in Table 4, which can also be defined by other implementations.
- Example 2 A 20-bit or 24-bit service tag is carried in an encapsulated form of a dual-layer VLAN overlay (802.1 q in 802. lq; referred to as QinQ) in the user packet field.
- QinQ dual-layer VLAN overlay
- FIG. lc is a schematic diagram of a QinQ packet encapsulation format in the service instance mapping method according to the first embodiment of the present invention, as shown in Figure lc.
- the QinQ packet includes two internal and external VLAN tags (TAGs). Each VLAN TAG consists of a 2-byte TPID and a 2-byte TCI.
- the Outer TAG has a TPID of 88A8 (hexadecimal) and the inner label (Inner TAG) has a TPID of 8100 (hexadecimal).
- TCI includes a 3-bit PRI indicating priority, 1 bit
- the CFI indicates whether it is experiencing congestion and finally includes a 12-bit VLAN field.
- the VLAN field of the inner label can store the lower 12 bits of the service label, and the lower 8 bits of the 12 bits of the outer label's VLAN field (which can also be 8 bits higher or 8 bits selected in other ways)
- the upper 8 bits of the service tag can be stored, and the remaining high 4 bits can be reserved.
- the VLAN field of the inner label can store the upper 12 bits of the service label, and the lower 8 bits of the 12 bits of the outer VLAN label (which can also be 8 bits higher or 8 bits selected in other ways) can store the service.
- the lower 8 bits of the tag With QinQ encapsulation format, it can be extended to support 20-bit service tags.
- 12 bits of the VLAN field of the inner label and 12 bits of the VLAN field of the outer label can also be used to store the service label, for example: 12 bits of the VLAN field of the inner label can store the upper 12 bits of the service label.
- the 12 bits of the VLAN field of the outer label can store the lower 12 bits of the service label; or, the 12 bits of the VLAN field of the inner label can store the lower 12 bits of the service label, and the 12 bits of the outer field label VLAN field.
- the extension of the foregoing service tag is only an example.
- the capability of the service tag is not limited to supporting the capability of 20-bit and 24-bit, and may be other than 12-bit capability, and may be extended according to the needs of the application scenario.
- the version number information "V" in the TRILL header can be upgraded from “0" to "1" to prevent the unsupported device from performing erroneous analysis and judgment.
- the corresponding TLV can be obtained through the control plane, and the correct connection relationship can be directly ensured in the process of establishing a neighbor relationship in the intermediate system to the intermediate system handshake (IS-IS HELLO; referred to as: ⁇ ).
- the step 102 may specifically include any one of the following ways:
- the service instance identifier may be mapped to the multi-link through a virtual local area network field of the first virtual local area network label of the open internet packet and an extended option of the multi-link transparent internet packet header, a virtual local area network field and a multi-link of the first virtual local area network label of the multi-link transparent interconnected message
- the extended option of the transparent interconnect header constitutes the service tag
- the local area network field maps the upper 12 bits of the service instance identifier to the virtual local area network field of the first inner label in the double layer virtual local area network superimposed message.
- the service instance mapping method can also retain the original virtual local area network identifier, which will be virtualized.
- the local area network identifier is mapped to the original virtual local area network, and the following examples are also included: Example 1: mapping the virtual local area network identifier of the service instance to the virtual local area network field of the second virtual local area network label of the multi-link transparent interconnection;
- FIG. 1 is another schematic diagram of an 802.1q encapsulation format adopted by a TRILL packet in a service instance mapping method according to Embodiment 1 of the present invention.
- the multi-link transparent interconnection mentioned in the foregoing example TRILL
- the first virtual local area network label of the packet can be VLANTAG (see also Figure lb)
- the TRILL second virtual local area network label can be a new VLANTAG'; of course, if the first virtual local area network label is VLANTAG ', the second virtual local area network tag is also possible for VLANTAG.
- the TRILL packet can carry the service instance identifier in the first virtual local area network label, and can carry the original VLAN identifier of the service instance in the second virtual local area network label, thereby being compatible with the original TRILL protocol.
- Example 2 Mapping the virtual local area network identifier of the service instance to the virtual local area network field of the second outer label of the double layer virtual local area network superimposed message and/or the virtual local area network of the second inner layer label.
- the OuterTAG and the InnerTAG' can be added. If the first outer label of the double-layer virtual local area network (QinQ) packet is OuterTAG, the second outer label is OuterTAG. '; If the first inner label is InnerTAG, the second inner label is InnerTAG', and vice versa.
- the original VLAN identifier of the service instance is carried in the second outer layer label and/or the second inner layer label, and can carry the service label and the VLAN identifier, thereby being compatible with the original TRILL protocol.
- an extended service label is used to identify a Layer 2 service instance.
- a more flexible service mapping mode is required to meet the needs of the user side access of the data center.
- the access port on the user side may include a single VLAN encapsulation form and a QinQ encapsulation form, and both of the encapsulation forms can be flexibly mapped into the extended service tag to be exchanged within the service instance.
- the VLAN of the access side can be a local VLAN of a local node, whether it is a single VLAN or a QinQ encapsulation. Modifications based on the original TRILL protocol can support larger capacity services Labeling scheme.
- the service instance uses the VLAN field of the TCI field in the 802.1q encapsulation format to directly save the VLAN ID.
- the 2 bytes of the original VLAN domain can be expanded to support the extended service label. Bytes, the lower 24 bits of these 4 bytes are used as extended service tags, and 1 byte is reserved.
- an extended TLV can be carried in the addition of the Hello message.
- the service label capability TLV is used to transmit the service label support capability of the node, and the service label selection method of the final system is determined through negotiation. See Table 5 for the modified TRILL protocol related Layer 2 TLV.
- the application scenario can be limited to single VLAN connection.
- QinQ access may not support Roots sub-TLV.
- LSP ServiceLable is independent of VLAN and can be distinguished from sub-TLV
- the business instance mapping method may also include any of the following steps:
- TLV Multi Topology aware Port Capability
- the layered service providing message of the group address TLV is sent, and the group MAC address sub-TLV of the group address carries the extended service tag information field.
- Service Label Capability TLV is a newly extended TLV, the format of which can be seen in Table 6 below:
- Type is the type of TLV, for example: Take “146";”Length” is the length of the TLV information, for example, take “2";”Service label Ability Announcement” is the service target of this node.
- a formal statement of the signature where "", in order to carry a 20-bit label in the form of QinQ, "T2, to support a 20-bit label in the extended TRILL header option, "T3, to carry a 24-bit label in the form of QinQ.
- Service label Negotiation is a way of negotiating between nodes to finally carry labels with each other. The definitions of " ⁇ 1, ⁇ 2, ⁇ 3" are the same as above.
- the service instance mapping method may further include: a step of negotiating the service tag support capability of the neighboring device in the process of establishing the connection by using the handshake, Specifically include:
- the negotiation determines the service tag support capability for establishing the connection
- the service tag support capability of the local node and the service tag support capability of the peer node may be determined by the negotiation to determine the service tag support capability for establishing the connection.
- the state transition state is migrated to the connection establishment state, and the matched service tag support capability is determined as the service tag support capability for establishing the connection. ;
- the service tag support capability of the local node is not the same as the service tag support capability of the peer node.
- the matching, the service tag support capability of the local node and the low service tag support capability of the service tag support capability of the peer node are determined as the service tag support capability used for establishing the connection.
- the state machine established by the neighbor of the point-to-point ( ⁇ 2 ⁇ ) is modified.
- the state machine process established by the neighbors of the original ⁇ 2 ⁇ is as follows:
- Table 7 The state machine established by the neighbors
- Figure la is a schematic diagram of a state machine for establishing a neighbor of a P2P extended in a service instance mapping method according to the first embodiment of the present invention.
- the local node receives the service tag and is not connected through the ⁇ message.
- the device can be moved to the connection establishment (Up) state, and the over-handshake state TLV is set to the UP state and the service tag support capability of the device is advertised to the peer node.
- the P2P neighbor establishment can be seen in Table 8.
- Intialize if it does not match, it remains Down. If the status of the local node is Initializing, if the ⁇ message sent by the peer node carries the service label support capability and the peer status is Down, it determines whether the local and the peer service label support capabilities match, and if they match, the local The status is changed to Up; otherwise it remains Down.
- the node that can identify the service tag and the node that cannot identify the service tag establish a neighbor relationship, or the node with high service tag support capability can reduce the service tag support capability to a lower level when there is no neighbor relationship with other high-capability nodes.
- the service tag support capability is as follows: The old version of the TLV and the low-capability node establish a neighbor relationship, so that after the high-capability node and the low-capability node establish a neighbor relationship, the high-capability node also becomes a low-capability node, thereby ensuring the effective network. Networking.
- the service instance identifier corresponding to the service access port can be mapped to the service tag of the packet. It includes a larger service tag support capability, can support many business instances, and can meet the needs of multi-tenancy in a large-scale public cloud environment. It is a large L2 solution; extended control protocol support, and the TRILL protocol extension can satisfy more Large business development capabilities; and, through flexible service mapping, can support multiple business scenarios.
- the physical architecture of the data network based on the data center includes: an access device 21, a convergence device 23, and a core device. 25 and the egress router 27, these devices construct a network to connect the physical server 20 of the data center to the external network 30.
- the physical devices in the actual network are as follows:
- the access device and the aggregation device can be a box or a box switch.
- the core device can be a frame switch. The aggregation and core devices can be set together to make the network layer simpler.
- FIG. 2b is a schematic diagram of another application scenario of the service instance mapping method according to Embodiment 2 of the present invention.
- the physical server 20 can be configured.
- the virtual machine (Virtual Machine; VM) is virtualized by software, and is connected to the access device 21 through a virtual virtual switch (Virtual Switch; VSW) of the physical server 20 software virtual.
- VSW Virtual Switch
- the service instance mapping method in the embodiment of the present invention can be implemented on the access device 21, the aggregation device 23, and the core device 25.
- the access device performs the service access of the user side, and can only perform VLAN tagging.
- the upper-layer aggregation device associates the service access port with the service instance to complete the mapping between the service instance identifier and the packet. After the VLAN tag is configured, the service access port is associated with the service instance, and the service instance ID is directly mapped to the service tag of the packet.
- the aggregation device 23 and the core device 25 can serve as an access node of the service instance, an intermediate node forwarded by the service instance, or an edge node switched by the service instance.
- the corresponding access node When the aggregation device and the core device are connected to the service instance, the corresponding access node only performs the single VLAN tag or the QinQ tag of the user service, and the aggregation device 23 or the core device 25 associates the service access port with the service instance. , complete the mapping of the service instance ID to the packet. If the aggregation device 23 or the core device 25 functions as an intermediate node, the access device 21 can complete the mapping of the user service access interface to the service instance, and the aggregation device 23 or the core device 25 completes the service instance interconnection between different access nodes.
- the physical server can use the unlabeled (UNTAG) or the service card to access the access device through the network card;
- the VSW can adopt the virtual edge bridge (VEB) and the virtual edge port aggregator (referred to as virtual edge port aggregator; : VEPA ), Multi-Channel models are interconnected with access devices.
- VEB can perform internal port switching to send external traffic to encapsulate user packets in a single VLAN.
- VEPA does not perform local node switching, and sends all traffic to the external access device for exchange.
- the user is encapsulated in a single VLAN.
- Multi-channel corresponds to multiple VEBs and VEPAs, and accesses the access switch through a layer of outer VLAN.
- mapping and deployment of service tags in the data center includes various combinations, as shown in Table 9 below: Table 9 Service Tag Mapping and Deployment Combination
- the service access port in Table 9 corresponds to "user access port + VLAN” or "user access port port + QinQ”, "VSW access port + VLAN”, “VSW access port + QinQ”,
- an extended service tag is used to store a VLAN identifier in the TRILL protocol, which may include a 20/24-bit service tag support capability, which can fully utilize the equivalent path in the network, combine the shortest path application, and can have more
- the service instance can meet the requirements of multi-tenant L2 network isolation in a large-scale public cloud environment. It is a large L2 solution; the control protocol is extended, and the TRILL protocol can be extended to meet greater business development capabilities.
- the service mapping mode can support multiple service scenarios.
- the deployment mode is flexible, and the existing equipment can be fully utilized. For example, the low-end switch device can be used only on the access device, and the service instance mapping device is enhanced on the aggregation device. Therefore, the overall system construction cost is superior.
- the changes to the network device are small, and the compatibility with the existing TRILL protocol is good, and the expansion is easy.
- the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
- FIG. 3 is a schematic structural diagram of a service instance mapping apparatus according to Embodiment 3 of the present invention. As shown in FIG. 3, the service instance mapping apparatus includes:
- the association module 31 is configured to associate a service instance of the layer 2 with a service access port of the service instance, and determine a correspondence between the service access port and the service instance identifier.
- the mapping module 33 is configured to map the service instance identifier into a service label of the packet.
- the service instance in the embodiment of the present invention is a layer 2 (data link layer) network service, where different service instances are in a layer 2 isolation state in the network, service access ports and service instances of the service instance.
- the association can be specified by means of command configuration.
- Each service instance corresponds to a globally unique service instance identifier, where the service instance identifier is composed of a numeric number, a string alias, and the like.
- You can assign a corresponding service instance ID to the service instance when the service instance is connected to the service instance.
- the service instance ID can be mapped to the data packet.
- Business tags are passed between devices. The method for mapping the service instance identifier to the service label of the packet may be improved on the basis of the TRILL protocol. For details, refer to the related description of the first and second embodiments of the present invention.
- the mapping module can map the service instance identifier corresponding to the service access port to the service label of the packet, and the service label carries the service.
- the instance ID can include a larger service tag support capability, can support more service instances, and can meet the needs of multi-tenancy in a large-scale public cloud environment. It is a large L2 solution; extended control protocol support, TRILL protocol The expansion can meet the needs of greater business development; and, through flexible service mapping, can support multiple business scenarios.
- the mapping module 33 of the service instance mapping apparatus may include: a single virtual local area network sub-module 331. And an extended option of mapping the service instance identifier to the virtual local area network field of the first virtual local area network label of the multi-link transparent internet packet and the multi-link transparent interconnection packet header, the multi-link transparent interconnection message
- the virtual LAN field of the first virtual local area network label and the extended option of the multi-link transparent interconnect header constitute the service tag; or
- the dual-layer virtual local area network super-sub-module 333 is configured to map the service instance identifier to a virtual local area network field of the first outer label of the double-layer virtual local area network superimposed message and a virtual local area network field of the first inner layer label, where The virtual local area network field of the first outer label and the virtual local area network field of the first inner layer label in the double-layer virtual local area network overlay form the service label.
- the single virtual local area network sub-module 331 is further configured to map the virtual local area network identifier of the service instance to the virtual local area of the second virtual local area network label of the multi-link transparent interconnection Web field; or
- the dual-layer virtual local area network super-sub-module 333 is further configured to map the virtual local area network identifier of the service instance to a virtual local area network field and/or a second inner label of the second outer layer of the dual-layer virtual local area network superimposed message.
- the virtual LAN field of the layer label is further configured to map the virtual local area network identifier of the service instance to a virtual local area network field and/or a second inner label of the second outer layer of the dual-layer virtual local area network superimposed message.
- the service instance mapping device may further include any one of the following modules or a three-state handshake module 35, configured to receive an initial access message carrying the service tag support capability of the opposite node and the unconnected state of the three-state handshake state. And according to the service tag support capability of the local node and the service tag support capability of the peer node, negotiating and determining the service tag support capability for establishing the connection; sending the service tag support capability for carrying the established connection to the peer node and the third State handshake state transition to notification of connection establishment status;
- the multi-topology sensing module 36 is configured to send an initial access message carrying the multi-topology-aware port capability, where the multi-topology-aware port capability is enabled in the virtual local area network, including an extended service tag information field; the media access control module 37 And a layered service providing message for carrying the medium access control reachability, where the medium access control reachability includes an extended service label information field;
- the group address module 38 is configured to send a layered service providing message carrying a group address, where the group medium access control address of the group address carries an extended service label information field.
- the three-state handshake module 35 can include:
- the first negotiation sub-module 351 is configured to: if the service tag support capability of the local node matches the service tag support capability of the peer node, the state transition state is migrated to a connection establishment state, and the matched service tag support capability is determined. Service tag support capabilities for establishing connections;
- the second negotiation sub-module 353 is configured to: if the service tag support capability of the local node does not match the service tag support capability of the peer node, the service tag support capability of the local node and the service tag support capability of the peer node are low.
- the service tag support capability determines the service tag support capabilities used to establish the connection.
- the device that supports the service instance mapping method in the embodiment of the present invention can also be applied to the MEN network of the telecommunication, for example, the DSLAM is connected to the interconnect through the aggregation switch, and the PTN network is used for mobile backhaul.
- the network is a Layer 2 (L2) access, and has some loops to ensure the switching.
- L2 Layer 2
- the service instance mapping method in the embodiment of the present invention can provide and consider flexible configuration, automatically route these advantages, and have a large-capacity service label. Can meet the needs of business applications.
- the sub-module of the mapping module can map the service instance identifier corresponding to the service access port to the service label of the packet.
- the service tag carries the service instance identifier, which can include a larger service tag support capability, can support many service instances, and can meet the needs of multi-tenancy in a large-scale public cloud environment. It is a large L2 solution; extended control protocol support. The extension of the TRILL protocol can meet the needs of greater business development. Moreover, through flexible service mapping, multiple service scenarios can be supported.
- the fifth embodiment of the present invention provides a service instance mapping system, where the service instance mapping system includes: at least one data center;
- the service instance mapping device of any one of the embodiments of the present invention may be used in the data center.
- the structure of the data center may include: a physical server, an access device, a convergence device, a core device, and an egress router, and the like, as shown in FIG. 2a and related description in the second embodiment; the physical server on the data center may pass the software.
- the virtual machine switching, the access device, the aggregation device, the core device, or the physical device may be configured.
- the exit router In the exit router.
- the service instance identifier corresponding to the service access port may be mapped to the service label of the packet.
- the service tag is carried by the service tag, which can include a larger service tag support capability, and can support many service instances. It can meet the needs of multi-tenancy in a large-scale public cloud environment. It is a large L2 solution; Supported, the extension of the TRILL protocol can meet the needs of greater business development; and, through flexible service mapping, can support multiple business scenarios.
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2011800004064A CN102171998B (zh) | 2011-04-26 | 2011-04-26 | 业务实例映射方法、装置和系统 |
ES11755698.5T ES2588739T3 (es) | 2011-04-26 | 2011-04-26 | Método, equipo y sistema para mapear una instancia de servicio |
EP11755698.5A EP2690820B1 (en) | 2011-04-26 | 2011-04-26 | Method, apparatus and system for mapping service instance |
PCT/CN2011/073322 WO2011113381A2 (zh) | 2011-04-26 | 2011-04-26 | 业务实例映射方法、装置和系统 |
US14/061,535 US9900254B2 (en) | 2011-04-26 | 2013-10-23 | Service instance mapping method, apparatus and system |
US15/822,714 US10218624B2 (en) | 2011-04-26 | 2017-11-27 | Service instance mapping method, apparatus and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2011/073322 WO2011113381A2 (zh) | 2011-04-26 | 2011-04-26 | 业务实例映射方法、装置和系统 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/061,535 Continuation US9900254B2 (en) | 2011-04-26 | 2013-10-23 | Service instance mapping method, apparatus and system |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2011113381A2 true WO2011113381A2 (zh) | 2011-09-22 |
WO2011113381A3 WO2011113381A3 (zh) | 2012-03-22 |
Family
ID=44491713
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/073322 WO2011113381A2 (zh) | 2011-04-26 | 2011-04-26 | 业务实例映射方法、装置和系统 |
Country Status (5)
Country | Link |
---|---|
US (2) | US9900254B2 (zh) |
EP (1) | EP2690820B1 (zh) |
CN (1) | CN102171998B (zh) |
ES (1) | ES2588739T3 (zh) |
WO (1) | WO2011113381A2 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130308648A1 (en) * | 2012-05-15 | 2013-11-21 | Marvell World Trade Ltd. | Extended priority for ethernet packets |
CN104579997A (zh) * | 2013-10-28 | 2015-04-29 | 杭州华三通信技术有限公司 | 最短路径桥接网络中的转发路径确定方法及设备 |
Families Citing this family (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101931548B (zh) * | 2009-06-24 | 2012-09-19 | 华为技术有限公司 | 一种接入网络标签管理方法、装置和系统 |
CN102968593B (zh) * | 2011-08-31 | 2016-08-03 | 国际商业机器公司 | 用于多租户环境下定位应用程序的隔离点的方法和系统 |
CN102420760A (zh) * | 2011-12-02 | 2012-04-18 | 盛科网络(苏州)有限公司 | 通过以太网封装包处理头来实现芯片间转发的方法及装置 |
CN102710510B (zh) * | 2012-05-18 | 2018-03-13 | 中兴通讯股份有限公司 | 信息处理方法、装置及系统 |
CN103516620B (zh) * | 2012-06-21 | 2016-10-05 | 华为技术有限公司 | 一种vm的迁移方法、系统及服务器 |
CN102752183B (zh) * | 2012-07-19 | 2015-01-14 | 杭州华三通信技术有限公司 | 一种接入网的快速收敛方法和装置 |
US8855015B2 (en) * | 2012-08-15 | 2014-10-07 | Cisco Technology, Inc. | Techniques for generic pruning in a trill network |
CN103595551B (zh) | 2012-08-17 | 2016-12-21 | 杭州华三通信技术有限公司 | 基于mqc实现网络虚拟化的网络管理方法和装置 |
CN102868614B (zh) * | 2012-09-13 | 2015-08-12 | 杭州华三通信技术有限公司 | Trill网络中的报文转发方法和路由网桥 |
CN102970240B (zh) * | 2012-11-01 | 2015-07-22 | 杭州华三通信技术有限公司 | 一种spb网络中的流量均衡方法及设备 |
TWI536775B (zh) * | 2013-06-04 | 2016-06-01 | 鈺登科技股份有限公司 | 網路系統、伺服器、交換器以及網路系統的運作方法 |
US10951522B2 (en) | 2013-11-05 | 2021-03-16 | Cisco Technology, Inc. | IP-based forwarding of bridged and routed IP packets and unicast ARP |
US9397946B1 (en) | 2013-11-05 | 2016-07-19 | Cisco Technology, Inc. | Forwarding to clusters of service nodes |
US9825857B2 (en) | 2013-11-05 | 2017-11-21 | Cisco Technology, Inc. | Method for increasing Layer-3 longest prefix match scale |
US9374294B1 (en) | 2013-11-05 | 2016-06-21 | Cisco Technology, Inc. | On-demand learning in overlay networks |
US9674086B2 (en) | 2013-11-05 | 2017-06-06 | Cisco Technology, Inc. | Work conserving schedular based on ranking |
US9876711B2 (en) | 2013-11-05 | 2018-01-23 | Cisco Technology, Inc. | Source address translation in overlay networks |
WO2015069576A1 (en) | 2013-11-05 | 2015-05-14 | Cisco Technology, Inc. | Network fabric overlay |
US9769078B2 (en) | 2013-11-05 | 2017-09-19 | Cisco Technology, Inc. | Dynamic flowlet prioritization |
US9655232B2 (en) | 2013-11-05 | 2017-05-16 | Cisco Technology, Inc. | Spanning tree protocol (STP) optimization techniques |
US9502111B2 (en) | 2013-11-05 | 2016-11-22 | Cisco Technology, Inc. | Weighted equal cost multipath routing |
US10778584B2 (en) | 2013-11-05 | 2020-09-15 | Cisco Technology, Inc. | System and method for multi-path load balancing in network fabrics |
US9888405B2 (en) | 2013-11-05 | 2018-02-06 | Cisco Technology, Inc. | Networking apparatuses and packet statistic determination methods employing atomic counters |
CN105306613A (zh) * | 2014-07-24 | 2016-02-03 | 中兴通讯股份有限公司 | Esadi的mac地址通告方法、装置及获取装置 |
CN105471754B (zh) * | 2014-09-01 | 2019-01-18 | 华为技术有限公司 | 一种数据传输控制方法、设备及系统 |
CN105763512B (zh) | 2014-12-17 | 2019-03-15 | 新华三技术有限公司 | Sdn虚拟化网络的通信方法和装置 |
CN110691034B (zh) * | 2015-07-17 | 2022-10-11 | 华为技术有限公司 | 传输灵活以太网的业务流的方法和装置 |
CN105763439B (zh) * | 2016-01-14 | 2019-02-19 | 新华三技术有限公司 | 一种多链接透明互联网络中数据中心的互联方法及装置 |
US10097419B2 (en) * | 2016-11-14 | 2018-10-09 | Alcatel-Lucent Canada, Inc. | Linear method for detection of multiple service topologies |
CN112671643B (zh) * | 2017-03-30 | 2022-05-13 | 上海层峰网络科技有限公司 | 一种基于mpls的sdn业务隔离及选路的装置 |
CN107135154B (zh) * | 2017-05-26 | 2019-08-06 | 烽火通信科技股份有限公司 | Potn业务转发系统及业务转发、配置下发、保护方法 |
EP4123973A1 (en) | 2019-02-08 | 2023-01-25 | Palantir Technologies Inc. | Isolating applications associated with multiple tenants within a computing platform |
CN111865626B (zh) * | 2019-04-24 | 2023-05-23 | 厦门网宿有限公司 | 一种基于聚合端口的数据收发方法和装置 |
US11627017B2 (en) * | 2020-10-22 | 2023-04-11 | Ciena Corporation | VPWS signaling using segment routing |
CN112269562B (zh) * | 2020-09-27 | 2023-09-12 | 福建天泉教育科技有限公司 | 一种组件化产品中租户隔离的方法及终端 |
CN112653766B (zh) * | 2020-12-25 | 2022-08-16 | 中国电子科技集团公司第三十四研究所 | 一种智能业务感知方法 |
US11956140B2 (en) * | 2021-10-01 | 2024-04-09 | Arista Networks, Inc. | Systems and methods for constructing service-aware virtual topologies in wide area networks |
US20230138323A1 (en) * | 2021-11-02 | 2023-05-04 | Arista Networks, Inc. | Mapping virtual local area network (vlan) tags |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8194656B2 (en) * | 2005-04-28 | 2012-06-05 | Cisco Technology, Inc. | Metro ethernet network with scaled broadcast and service instance domains |
US7835267B2 (en) * | 2005-05-09 | 2010-11-16 | Cisco Technology, Inc. | Dynamic path protection in an optical network |
US20080019385A1 (en) * | 2005-12-30 | 2008-01-24 | Huawei Technologies Co., Inc. (Usa) | System and method of mapping between local and global service instance identifiers in provider networks |
CN100502336C (zh) * | 2006-05-24 | 2009-06-17 | 华为技术有限公司 | 城域以太网网桥、系统及提供服务的方法 |
US7768918B2 (en) * | 2006-06-28 | 2010-08-03 | Via Technologies Inc. | Method for expanding the service VLAN space of a provider network |
CN101257452B (zh) * | 2008-04-16 | 2010-12-08 | 中兴通讯股份有限公司 | 一种以太无源光网络接入设备发送下行数据报文的方法 |
US8315159B2 (en) * | 2008-09-11 | 2012-11-20 | Rockstar Bidco, LP | Utilizing optical bypass links in a communication network |
US7787480B1 (en) * | 2009-03-04 | 2010-08-31 | Juniper Networks, Inc. | Routing frames in a trill network using service VLAN identifiers |
US8213296B2 (en) * | 2009-05-14 | 2012-07-03 | Verizon Patent And Licensing Inc. | Link aggregation protection |
US10033650B2 (en) * | 2010-06-08 | 2018-07-24 | Brocade Communication Systems Llc | Preserving quality of service across trill networks |
US9608833B2 (en) * | 2010-06-08 | 2017-03-28 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
US20110299533A1 (en) * | 2010-06-08 | 2011-12-08 | Brocade Communications Systems, Inc. | Internal virtual network identifier and internal policy identifier |
US8929218B2 (en) * | 2010-09-10 | 2015-01-06 | Brocade Communication Systems, Inc. | Congestion notification across multiple layer-2 domains |
US8755383B2 (en) * | 2011-03-21 | 2014-06-17 | Avaya, Inc. | Usage of masked ethernet addresses between transparent interconnect of lots of links (TRILL) routing bridges |
CN102255819B (zh) * | 2011-08-29 | 2014-12-17 | 神州数码网络(北京)有限公司 | 基于vlan的trill流量优先调度方法 |
-
2011
- 2011-04-26 WO PCT/CN2011/073322 patent/WO2011113381A2/zh active Application Filing
- 2011-04-26 ES ES11755698.5T patent/ES2588739T3/es active Active
- 2011-04-26 EP EP11755698.5A patent/EP2690820B1/en active Active
- 2011-04-26 CN CN2011800004064A patent/CN102171998B/zh active Active
-
2013
- 2013-10-23 US US14/061,535 patent/US9900254B2/en active Active
-
2017
- 2017-11-27 US US15/822,714 patent/US10218624B2/en active Active
Non-Patent Citations (1)
Title |
---|
None |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130308648A1 (en) * | 2012-05-15 | 2013-11-21 | Marvell World Trade Ltd. | Extended priority for ethernet packets |
US20140226488A1 (en) * | 2012-05-15 | 2014-08-14 | Marvell World Trade Ltd. | Extended Priority for Ethernet Packets |
US9491109B2 (en) * | 2012-05-15 | 2016-11-08 | Marvell World Trade Ltd. | Extended priority for Ethernet packets |
US9491108B2 (en) | 2012-05-15 | 2016-11-08 | Marvell World Trade Ltd. | Extended priority for ethernet packets |
CN104579997A (zh) * | 2013-10-28 | 2015-04-29 | 杭州华三通信技术有限公司 | 最短路径桥接网络中的转发路径确定方法及设备 |
Also Published As
Publication number | Publication date |
---|---|
US9900254B2 (en) | 2018-02-20 |
ES2588739T3 (es) | 2016-11-04 |
CN102171998B (zh) | 2013-10-09 |
US20180083881A1 (en) | 2018-03-22 |
US20140043972A1 (en) | 2014-02-13 |
EP2690820B1 (en) | 2016-06-08 |
WO2011113381A3 (zh) | 2012-03-22 |
EP2690820A2 (en) | 2014-01-29 |
EP2690820A4 (en) | 2014-01-29 |
US10218624B2 (en) | 2019-02-26 |
CN102171998A (zh) | 2011-08-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10218624B2 (en) | Service instance mapping method, apparatus and system | |
US8694664B2 (en) | Active-active multi-homing support for overlay transport protocol | |
US10135627B2 (en) | System for avoiding traffic flooding due to asymmetric MAC learning and achieving predictable convergence for PBB-EVPN active-active redundancy | |
US8005081B2 (en) | Evolution of ethernet networks | |
CN104937885B (zh) | 用于结构交换机的全局vlan | |
CN107210961B (zh) | 用于虚拟路由和转发路由泄漏的方法和装置 | |
US8098656B2 (en) | Method and apparatus for implementing L2 VPNs on an IP network | |
CN104471899B (zh) | 通过ietf evpn的802.1aq支持 | |
US8531941B2 (en) | Intra-domain and inter-domain bridging over MPLS using MAC distribution via border gateway protocol | |
CN109218178A (zh) | 一种报文处理方法及网络设备 | |
US20100220739A1 (en) | Carrier Network Connection Device And Carrier Network | |
GB2497202A (en) | Transmitting frames between, possibly different, local VLANs by encapsulating frames for global VLAN tunnel | |
WO2014082467A1 (zh) | 多归接入最短路径桥接网络的方法和装置 | |
US9282006B2 (en) | Method and system of enhancing multiple MAC registration protocol (MMRP) for protocol internetworking | |
WO2006056131A1 (fr) | Procede de realisation d'intercommunication entre les differents reseaux vpn l3 | |
WO2015117413A1 (zh) | Esadi的mac地址通告方法、装置及获取装置 | |
EP3190752B1 (en) | Method, apparatus and medium for avoiding traffic flooding due to asymmetric mac learning and achieving predictable convergence for pbb-evpn active-active redundancy | |
Singh | BGP MPLS based EVPN And its implementation and use cases |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180000406.4 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11755698 Country of ref document: EP Kind code of ref document: A2 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011755698 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11755698 Country of ref document: EP Kind code of ref document: A2 |