EP1629641A2 - Method for routing ip-packets to an external control component of a network node in an ip-packet switching communications network comprising several network nodes - Google Patents
Method for routing ip-packets to an external control component of a network node in an ip-packet switching communications network comprising several network nodesInfo
- Publication number
- EP1629641A2 EP1629641A2 EP04741669A EP04741669A EP1629641A2 EP 1629641 A2 EP1629641 A2 EP 1629641A2 EP 04741669 A EP04741669 A EP 04741669A EP 04741669 A EP04741669 A EP 04741669A EP 1629641 A2 EP1629641 A2 EP 1629641A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- network node
- packet
- control component
- packets
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
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/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/825—Involving tunnels, e.g. MPLS
-
- 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
-
- 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]
-
- 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
-
- 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/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2458—Modification of priorities while in transit
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
- H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]
Definitions
- the invention relates to a method according to the preambles of claims 1, 3, 5 and 7.
- IP networks will transport higher-quality services and allow new applications in addition to the Internet and best-effort services that are common today.
- network nodes and / or network elements such as routers, or
- control components as external servers to the network components, network nodes or routers to be controlled. This can be done directly, i.e. by a connection or line between an external interface of the network component and the control component located nearby, or via a network connection between the network component and control component.
- the first integrated solution has the advantage that the control component is provided with internal information of the network component due to the close coupling to the network component.
- a "provided” solution is manufacturer-independent and more flexible, since it is not so closely interwoven with the internals of the network component.
- “provided” solutions can be based on standardized hardware, short HW, and software, short SW, solutions Network components such as routers are mostly based on proprietary HW / SW solutions. Shorter development cycles and cost savings can be achieved through “provided” control components.
- the disadvantage of "provided” solutions is that internal information of the network component is not available.
- One task of an admission control is to accept incoming resource requests, compare them with the resources still available and, if resources are still available, a network node or router, e.g. to program the router on the edge of the network or edge router to control the data flow. This includes the setting of so-called functions such as marking, filtering and policing.
- RSVP resource reservation protocol
- RSVP-capable network i.e. of a network with RSVP-capable network nodes or routers according to FIG. 1, the sequence is to be described schematically.
- FIG. 1 shows a schematic IP network, consisting of several network nodes or routers A to H, each of which internally has a control component AC.
- the network node A is connected to the network node E on the one hand by a series connection of the network nodes B, C, D and on the other hand by a series connection of the network nodes F, G, H.
- the network nodes B and G, C and H and D and H are also connected to one another.
- connections or connection paths are designed, for example, as electrical or optical lines, such as two-wire lines, coaxial cables or optical fibers.
- a node X is connected to network node A and a node Y is connected to network node E.
- Subscriber X creates a resource request to the network for a data stream to subscriber Y. It must be ensured that the resource reservations in the network nodes are actually made along the later data path. In IP networks, this data path depends on the current routing. Therefore in the resource reservation Protocol RSVP sent the resource request with the IP destination address, i.e. the IP address of subscriber Y, into the network. It thus automatically follows the data path of the later data stream to subscriber Y. Although these RSVP messages are not now addressed to the RSVP control components AC or RSVP instances, the RSVP control components AC or RSVP instances must be on the way lying network nodes each get knowledge of it.
- Protocol type "RSVP" in the IP header ie in the header of an IP packet, specially marked.
- the routers recognize this type of protocol and forward messages marked in this way directly to their RSVP instance, that is to say to the control component AC.
- the RSVP instance on the network edge to subscriber X must configure "its" edge router A (filtering, marking, policing). Specifically, the interface must be configured via which the RSVP message from node X originally arrived and via which the data stream from node X to node Y will arrive later. Since the RSVP instance is implemented in the router, it can query this internal information.
- the solution for the two points A and B lies in the close internal coupling between the network node and the control component.
- the resource requests reach the control component via special filters in the network node or router, which recognize the protocol ID and forward the packets past the routing directly to the internal control component.
- the control component AC receives information on the configuration of the network node or router by accessing router-internal data.
- the problem with external control components is that this internal information is not queried from the network node or made available by the network node.
- the object of the present invention is to provide a method in which received IP packets with interface information of the receiving network node can be passed on to an external control component.
- the advantage of the invention is that IP packets with control information internal to the node are forwarded to an external control component.
- a control component "provided" to a network node can take on more extensive control tasks of the network node.
- the external control component can be arranged at a remote point in the network and is connected via a network connection.
- FIG. 1 shows a schematic IP network with internal control components AC according to the prior art.
- 2 shows an IP network constructed analogously to FIG. 1 with two external control components AC according to the invention.
- FIG. 1 shows an IP network according to the prior art, already explained in the introduction to the description.
- FIG. 2 shows a network according to FIG. 1, with the difference that an external control component AC is connected to network elements D and G in each case.
- IP packets are to be transmitted from subscriber X to subscriber Y.
- the external control components AC require certain IP packets, such as in-band IP signaling packets, for example RSVP packets, and the information at which interface of the network node the IP packet / in-band IP signaling packet / RSVP packet was received , The latter information is only available internally in the network node and cannot be queried.
- the routing tables of the network node or router only contain information about destinations, but not about where a packet came from.
- rules are configured on the interfaces of the network nodes.
- Current network nodes or routers support so-called policy routing. Rules can be configured for how to deal with special packages. So-called tunneling is also used.
- IP tunnels eg GRE tunnels
- the original IP packet at the tunnel entrance is supplemented by a tunnel header including a tunnel ID and a new outer IP header.
- the IP packet is routed through the network.
- the outer header is removed and the original package is processed further.
- Modern network nodes or routers, in particular the edge routers affected here, often support one or more variants of tunneling.
- tunnel start the network node or router
- end point the control component AC or control entity
- a first variant is based on using the tunnel ID for the transmission of internal information.
- a separate tunnel to the control component is set up for each interface of the network node, so that the interface number corresponds explicitly or implicitly to the tunnel ID.
- a tunnel to the control component is set up from each interface of the network node.
- a rule is set up in the network node or on the interface that certain IP packets, such as in-band IP signaling packets, which are identified by an entry in the protocol field of the IP header of the IP packet, are "outer" "IP packet are packed, the IP address of the control component assigned to the network node is entered as the destination IP address in the" outer "IP packet and a unique value assigned to the interface, which differs from the values of the other interfaces of the network node distinguishes and with which the interface can be clearly identified, entered as tunnel ID in the "outer” IP packet.
- This packet is forwarded to the control component through IP routing.
- in-band IP signaling packets of the "RSVP" type are packed and transmitted.
- This tunnel solution has the advantage that the control components or control instances do not have to be connected directly to the network node or router, but can be placed anywhere in the network, as in FIG. 2 exemplified by the control components AC on the network nodes D and G. The control components AC can then be reached via the logical "direct interface" tunnel.
- a solution by so-called DSCP marking is proposed for a similar task.
- a specific received IP packet such as an in-band IP signaling packet of the “RSVP” type
- the value of a specific field such as the DSCP field
- the IP header or header field of the IP packet is changed and one of depending on the receiving interface of the network node in the specific header field / DSCP field.
- This solution can be combined with the tunnel solution.Tunnels can be set up and the DSCP fields of an IP packet can also be modified.
- the rules on the interfaces of the network nodes then contain a corresponding marking, such as DSCP marking, and the corresponding tunnel as a "next-hop" entry.
- the DSCP field is assumed to be the field to be changed, but another field can also be used in the header or header of the IP packet.
- a DSCP field change or a DSCP marking should be carried out on the inner IP header.
- the outer IP header can then really be used for DSCP priority identification.
- tunnel ID no longer has to contain a value assigned to the interface, since this is clearly entered in the DSCP field.
- a tunnel to the assigned control component does not have to be set up from every interface of the network node become.
- at least one tunnel to the control component could be set up from the network node, all IP packets of a certain type, such as in-band IP signaling packets, for example “RSVP” packets, being transmitted to the control component and the distinction at which interface the packet was received through the changed DSCP field.
- IP packets of a certain type such as in-band IP signaling packets, for example “RSVP” packets
- the DSCP field is 6 bits in size, which allows a range of 64 values, a combination of tunneling and DSCP marking increases the available range of values. This means that a large area can be covered with just a few tunnels. By e.g. 2 tunnels and DSCP marking can be used to differentiate between 128 values or interfaces of the network node.
- Tunneling can also be achieved using Multi Protocol Label Switching, MPLS for short.
- MPLS Multi Protocol Label Switching
- the process works analogously to IP tunnels, with the difference that MPLS "tunnels" or MPLS paths are used instead of the IP tunnels.
- Multiprotocol Label Switching maintains network-wide states that define the paths or paths on which packets are routed through the network bypassing "normal" IP routing.
- the network nodes no longer forward packets based on the destination IP addresses, but a bit sequence, a so-called label, is added to each packet at the network input.
- This label which is evaluated in each network node, determines the way in which the packets are forwarded.
- the connection between labels and paths must be established when the network is started up.
- the label is removed at the network outlet.
- local or local mechanisms or rules are required in order to redirect packets to a replacement path if the originally intended path fails or to set up a replacement path after a failure.
- An in-band IP signaling packet received at an interface of the network node or an IP packet of the “RSVP” type, or also of another type, is recognized and the packet is preceded by an MPLS label, the label ID of which is unambiguously the receiving one
- the interface assigned and leads to the control component assigned to the network node The IP packet packed in this way is forwarded to the control component by means of MPLS.
- the MPLS label ID preceding the IP packet is evaluated in the control component and a comparison with stored values is used in the Control component determines the interface or the interface on which the IP packet was received by the network node.
- the rule is implemented on the interface of the network node that a certain value, defined for the interface, is placed in front of the IP packet as an MPLS label and the packet is forwarded by MPLS.
- the MPLS process must ensure that packets with a specific MPLS label ID lead to the corresponding destinations, in the example to the control component.
- MPLS can be combined with DSCP marking, analogous to the previously written procedure. It is sufficient if at least one MPLS label ID is entered in the network node, since the interfaces of the network node are differentiated by DSCP marking.
- an in-band IP signaling packet or a packet of the "RSVP" type received at an interface of the network node is recognized and processed in such a way that the value of a specific field, such as the "DSCP" field, depends on the receiving interface is changed.
- a unique interface ID that differs from the interface ID of the other interfaces of the
- Network node differentiates, entered in the DSCP field, also prepended the IP packet with an MPLS label and ver changed packet forwarded to the engine by the MPLS process. Not every interface has to enter its own MPLS label ID, since the DSCP field differentiates between the interfaces. Large ranges of values can also be achieved by combining the MPLS label ID and DSCP marking. 128 MPLS label ID and DSCP marking can be used to distinguish 128 values or interfaces of a network node.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10324604A DE10324604A1 (en) | 2003-05-30 | 2003-05-30 | Method for forwarding IP packets to an external control component of a network node in a communication network which conveys IP packets which have several network nodes |
PCT/EP2004/050950 WO2004107675A2 (en) | 2003-05-30 | 2004-05-27 | Method for routing ip-packets to an external control component of a network node in an ip-packet switching communications network comprising several network nodes |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1629641A2 true EP1629641A2 (en) | 2006-03-01 |
Family
ID=33482314
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04741669A Withdrawn EP1629641A2 (en) | 2003-05-30 | 2004-05-27 | Method for routing ip-packets to an external control component of a network node in an ip-packet switching communications network comprising several network nodes |
Country Status (4)
Country | Link |
---|---|
US (2) | US20060268911A1 (en) |
EP (1) | EP1629641A2 (en) |
DE (1) | DE10324604A1 (en) |
WO (1) | WO2004107675A2 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010022767A1 (en) * | 2008-08-26 | 2010-03-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Packet forwarding in a network |
CN102273136B (en) * | 2009-09-01 | 2012-12-26 | 华为技术有限公司 | Method and apparatus for detecting multi-service performance in tunnel |
US8891406B1 (en) * | 2010-12-22 | 2014-11-18 | Juniper Networks, Inc. | Methods and apparatus for tunnel management within a data center |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6101549A (en) * | 1996-09-27 | 2000-08-08 | Intel Corporation | Proxy-based reservation of network resources |
US7203740B1 (en) * | 1999-12-22 | 2007-04-10 | Intel Corporation | Method and apparatus for allowing proprietary forwarding elements to interoperate with standard control elements in an open architecture for network devices |
US6865185B1 (en) * | 2000-02-25 | 2005-03-08 | Cisco Technology, Inc. | Method and system for queuing traffic in a wireless communications network |
US7046680B1 (en) * | 2000-11-28 | 2006-05-16 | Mci, Inc. | Network access system including a programmable access device having distributed service control |
US7215638B1 (en) * | 2002-06-19 | 2007-05-08 | Meshnetworks, Inc. | System and method to provide 911 access in voice over internet protocol systems without compromising network security |
WO2004002061A1 (en) * | 2002-06-25 | 2003-12-31 | Siemens Aktiengesellschaft | Communication network and method for operating the same |
US7023843B2 (en) * | 2002-06-26 | 2006-04-04 | Nokia Corporation | Programmable scheduling for IP routers |
US7359984B1 (en) * | 2002-07-15 | 2008-04-15 | Packeteer, Inc. | Management of network quality of service |
-
2003
- 2003-05-30 DE DE10324604A patent/DE10324604A1/en not_active Ceased
-
2004
- 2004-05-27 WO PCT/EP2004/050950 patent/WO2004107675A2/en not_active Application Discontinuation
- 2004-05-27 US US10/558,901 patent/US20060268911A1/en not_active Abandoned
- 2004-05-27 EP EP04741669A patent/EP1629641A2/en not_active Withdrawn
-
2009
- 2009-01-12 US US12/352,013 patent/US20090180485A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of WO2004107675A2 * |
Also Published As
Publication number | Publication date |
---|---|
DE10324604A1 (en) | 2004-12-23 |
WO2004107675A3 (en) | 2005-04-07 |
US20060268911A1 (en) | 2006-11-30 |
US20090180485A1 (en) | 2009-07-16 |
WO2004107675A2 (en) | 2004-12-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE60225892T2 (en) | Firewall for filtering tunneled data packets | |
DE60037368T2 (en) | Method and architecture for supporting multiple services in a label switching network | |
EP1430665A2 (en) | Method and device for adapting label-switched paths in packet networks | |
EP1438829B1 (en) | Method and device for mapping network headers onto mpls headers in bearer architectures | |
WO2003007484A2 (en) | Method for the optimised use of sctp (stream control transmission protocol) in mpls (multi protocol label switching) networks | |
DE60202454T2 (en) | Mechanism to establish a connection for ATM over MPLS | |
WO2003094444A1 (en) | Method for examining the connectivity of links in mpls-networks | |
EP1262084B1 (en) | Equivalent switching method for transmission devices in mpls networks | |
EP3854035A1 (en) | Data transmission method and automation communication network | |
EP1438825A1 (en) | Method and devices for header compression in packet-oriented networks | |
EP1317820B1 (en) | Method for establishment of connections of pre-determined performance for a packet-oriented communication network with a resource manager | |
EP1629641A2 (en) | Method for routing ip-packets to an external control component of a network node in an ip-packet switching communications network comprising several network nodes | |
EP1894363B1 (en) | Method and independent communications subnet for determining label-switched routes in a communications subnet of this type | |
DE69921776T2 (en) | Mobile IP with quality of service for foreign network with foreign agent and several mobile nodes | |
WO2003081850A1 (en) | Method for operation and monitoring of mpls networks | |
EP1629639B1 (en) | Method for relaying ip-packets to an external control component of a network node | |
DE20122358U1 (en) | Telecommunication system has two tiers of distributed broadband remote access servers that aggregate connections from access network and subscribers respectively into two distinct communication pipes | |
EP0998093B1 (en) | Method to transmit reverse channel data on a connection between a terminal and a server in a packet switched network | |
DE60203539T2 (en) | MULTI-DOMAIN ACCESS CONTROL OF DATA FLOWS ASSOCIATED WITH QUALITY OF SERVICE QUALITY | |
DE10055066A1 (en) | System for multidirectional exchange of information between subscribers or users such as automation devices on an Ethernet basis | |
DE10324370A1 (en) | Network node of a packet-switched communication network and method for traffic distribution of data traffic in a packet-switched communication network | |
DE10062375B4 (en) | Method for forwarding data packets, forwarding unit and associated program | |
WO2020169280A1 (en) | Method for data transmission, device, computer program and computer-readable medium | |
DE102005052188B4 (en) | Quality assurance using centrally recorded quality of service parameters | |
WO2004002061A1 (en) | Communication network and method for operating the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20051109 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): DE FR GB |
|
DAX | Request for extension of the european patent (deleted) | ||
RBV | Designated contracting states (corrected) |
Designated state(s): DE FR GB |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: WINKLER, CHRISTIAN Inventor name: SCHMITT, ANTON Inventor name: BERGMANN, JOHANNES |
|
17Q | First examination report despatched |
Effective date: 20070606 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SIEMENS NETWORKS S.P.A. |
|
RAP3 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20071017 |