# US 2004/0057429 A1 · Method and telecommunications node for distribution of terminating traffic within telecommunications node

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0057429 A1
- Document ID: US20040057429A1
- Status: Published application
- Kind: A1
- Application number: 10/432,952
- Filed: 2003-09-22
- Published: 2004-03-25
- Earliest claimed: 2000-11-29
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Lars Marklund
- Web page: https://patentgrep.com/patent/US20040057429A1

## CPC

- H04L 45/60: Router architectures
- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 49/602: {Multilayer or multiprotocol switching, e.g. IP switching}
- H04L 61/00: Network arrangements, protocols or services for addressing or naming
- H04L 61/10: of different types
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04Q 3/0045: {involving hybrid, i.e. a mixture of public and private, or multi-vendor systems}
- H04L 69/12: Protocol engines
- H04L 2101/663: Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04Q: SELECTING (switches, relays, selectors H01H; wireless communication networks H04W)

## Abstract

The present invention relates to a telecommunications node (60) that is able to handle IP-traffic and to terminate telecommunications traffic. The node includes a forwarding functionality with a number of forwarding engines (65). The node includes means for creating internal IP-hosts (61) for terminating IP-traffic within the node (60), each of which IP-host is attached to an IP-port (83) of a forwarding engine (65). The IP-hosts are each assigned an individual IP-address, which makes it possible to forward IP-traffic to the IP-hosts (61) by means of using the IP-address as a destination address for the IP-traffic. Information relating to the IP-addresses of the internal IP-hosts (61) is included in forwarding tables of the forwarding engines (65). It is possible to perform load distribution of terminating IP-traffic based on the IP-addresses of the internal IP-hosts.

## Claims

### Claim 1

A telecommunications node with the ability to handle IP-traffic and to terminate telecommunications traffic, which telecommunications node includes
a forwarding functionality comprising at least one forwarding engine,
a routing table manager,
means for creating an IP-host for terminating IP-traffic in the telecommunications node, which IP-host is assigned an IP-address,
means for attaching a created IP-host to an IP-port of one of the at least one forwarding engine, and
means for sending a message to the routing table manager in response to an IP-host being attached to an IP-port of one of the at least one forwarding engine, which message includes information relating to the identity of the IP-port and to the IP-address of the attached IP-host.

### Claim 2 (depends on 1)

The telecommunications node of claim 1, wherein the means for creating an IP-host are arranged to create a first IP-host, which is assigned a first IP-address and is attached to a first IP-port and to subsequently create a second IP-host attached to a second IP-port and assign the first IP-address to the second IP-host instead of to the first IP-host.

### Claim 3 (depends on 2)

The telecommunications node of claim 2, which telecommunications node further includes means for detecting a failure of one or several of the first forwarding engine, the first IP-host and the first IP-port, and wherein the means for creating an IP-host are arranged to create the second IP-host in response to a detected failure of one or several of the first forwarding engine, the first IP-host and the first IP-port.

### Claim 4 (depends on 2, 3)

The telecommunications node of claim 2 or 3, which telecommunications node further includes means for selecting the second IP-port, to which the second IP-host is to be attached, based on load information regarding the load distribution in the telecommunications node.

### Claim 5 (depends on 2, 3)

The telecommunications node of claim 2 or 3, wherein the means for creating an IP-host are arranged to associate back-up information with the first IP-host upon creation of the first IP-host, which back-up information relates to the identity of the second IP-port and wherein the telecommunications node further includes means for selecting the second IP-port, to which the second IP-host is to be attached, based on the back-up information.

### Claim 6 (depends on 1, 2, 3, 4, 5)

The telecommunications node of any of claims 1-5, wherein the routing table manager is arranged to perform a forwarding table recalculation in response to reception of the message with the information relating to the IP-port identity and to the IP-address and wherein the routing table manager is arranged to send a forwarding table update message based on the recalculation to each forwarding engine of the telecommunications node.

### Claim 7 (depends on 1, 2, 3, 4, 5, 6)

The telecommunications node of any of claims 1-6, wherein the means for attaching a created IP-host to an IP-port are means of the created IP-host for sending an attach message to the forwarding engine of the IP-port, which attach message includes the address assigned to the IP-host.

### Claim 8 (depends on 1, 2, 3, 4, 5, 6, 7)

The telecommunications node of any of claims 1-7, wherein the means for creating an IP-host, the means for attaching a created IP-host to an IP-port and the means for sending a message to the routing table manager are arranged to operate while the telecommunications node is in operation with respect to handling telecommunications traffic.

### Claim 9

A method in a telecommunications node with the ability to handle IP-traffic and to terminate telecommunications traffic, which method includes the steps of
creating a first IP-host for terminating IP-traffic in the telecommunications node and assigning a first IP-address to the first IP-host
attaching the first IP-host to a first IP-port of a first forwarding engine, which first forwarding engine is one of at least one forwarding engine of a forwarding functionality of the telecommunications node, and
sending a first message to a routing table manager of the telecommunications node in response to the attachment of the first IP-host to the first IP-port, which first message includes information relating to the identity of the first IP-port and to the first IP-address.

### Claim 10 (depends on 9)

The method of claim 9, which method further comprises the steps of
creating a second IP-host for terminating IP-traffic in the telecommunications node and assigning the first IP-address to the second IP-host instead of to the first IP-host
attaching the second IP-host to a second IP-port of one of the at least one forwarding engine, and
sending a second message to the routing table manager in response to the attachment of the second IP-host to the second IP-port, which second message includes information relating to the identity of the IP-port and to the first IP-address.

### Claim 11 (depends on 10)

The method of claim 10, which method further includes a step of detecting a failure of one or several of the first forwarding engine, the first IP-host and the first IP-port, and wherein the step of creating the second IP-host is performed in response to detection of the failure of one or several of the first forwarding engine, the first IP-host and the first IP-port.

### Claim 12 (depends on 10, 11)

The method of claim 10 or 11, which method further includes the step of selecting the second IP-port, to which the second IP-host is to be attached, based on load information regarding the load distribution in the telecommunications node.

### Claim 13 (depends on 10, 11)

The method of claim 10 or 11, which method further includes the step of selecting the second IP-port, to which the second IP-host is to be attached, based on back-up information associated with the first IP-host, which back-up information relates to the identity of the second IP-port and which back-up information is associated with the first IP-host upon creation of the first IP-host.

### Claim 14 (depends on 9, 10, 11, 12, 13)

The method of any of claims 9-13, wherein the routing table manager performs a forwarding table recalculation in response to reception of the message with the information relating to the IP-port identity and to the IP-address and wherein the routing table manager sends a forwarding table update message based on the recalculation to each forwarding engine of the telecommunications node.

### Claim 15 (depends on 9, 10, 11, 12, 13, 14)

The method of any of claims 9-14, wherein the steps of attaching an IP-host to an IP-port is performed by means of the IP-host sending an attach message to the forwarding engine of the IP-port, which attach message includes the address assigned to the IP-host.

### Claim 16 (depends on 9, 10, 11, 12, 13, 14, 15)

The method of any of claims 9-15, wherein the step of creating an IP-host, the step of attaching a created IP-host to an IP-port and the step of sending a message to the routing table manager are performed while the telecommunications node is in operation with respect to handling telecommunications traffic.
