IP Library › Granted Patent US 10,742,487
Granted Patent B2
US 10,742,487 · App. 15/945,942 · Granted Aug 11, 2020

Border routers in multicast networks and methods of operating the same

Inventors: Hooman Bidgoli (Ottawa, CA); Georges Chung Kam Chung (Nepean, CA)
Assignee: Nokia Technologies Oy
H04L41/0654H04L12/18H04L45/74
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,742,487
App. No.
15/945,942
Granted
Aug 11, 2020
Kind
B2
Abstract

A border router includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code is configured to, with the at least one processor, cause the border router to: identify, in response to receiving a label mapping message from a network node, a backup border router as a hop in a backup path between a leaf node and a root node in a multicast network including an autonomous system, the label mapping message including a type-length-value; determine whether the backup border router is an originating border router having generated the label mapping message based on the type-length-value; and suppress mapping of the hop in the backup path in response to determining that the backup border router is the originating border router.

Claims (59)

1. A border router comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the border router to

identify, in response to receiving a label mapping message from a network node, a backup border router as a hop in a backup path between a leaf node and a root node in a multicast network including an autonomous system, the label mapping message including a type-length-value,

determine whether the backup border router is an originating border router having generated the label mapping message based on the type-length-value, the backup border router being separate from the border router, and

suppress mapping of the hop in the backup path in response to determining that the backup border router is the originating border router, wherein

the type-length-value includes a system address of the originating border router, and

the at least one memory and the computer program code are further configured to, with the at least one processor, cause the border router to examine the type-length-value to determine the system address of the originating border router.

2. The border router of claim 1 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the border router to

determine whether the backup border router is the originating border router based on a comparison between the system address of the originating border router and a system address of the backup border router.

3. The border router of claim 1 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the border router to

determine that the system address of the originating border router matches a system address of the backup border router; and

determine that the backup border router is the originating border router in response to determining that the system address of the originating border router matches the system address of the backup border router.

4. The border router of claim 1 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the border router to

identify, in response to receiving the label mapping message, a primary border router as a hop in a primary path between the leaf node and the root node in the multicast network; and

send a label mapping message to only the primary border router from among the primary border router and the backup border router.

5. The border router of claim 1 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the border router to map the hop of the backup path in response to determining that the backup border router is not the originating border router.

6. The border router of claim 5 , wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the border router to

identify, in response to receiving the label mapping message, a primary border router as a hop in a primary path between the leaf node and the root node in the multicast network;

send a first label mapping message to the primary border router to map the hop in the primary path; and

send a second label mapping message to the backup border router to map the hop in the backup path.

7. A method performed at a border router, the method comprising:

identifying, in response to receiving a label mapping message from a network node, a backup border router as a hop in a backup path between a leaf node and a root node in a multicast network including an autonomous system, the label mapping message including a type-length-value, the type-length-value including a system address of an originating border router having generated the label mapping message;

examining the type-length-value to determine the system address of the originating border router;

determining whether the backup border router is the originating border router based on the type-length-value; and

suppressing mapping of the hop in the backup path in response to determining that the backup border router is the originating border router, wherein

the backup border router is separate from the border router.

8. The method of claim 7 ,

wherein

the determining determines whether the backup border router is the originating border router based on a comparison between the system address of the originating border router and a system address of the backup border router.

9. The method of claim 7 , wherein the determining comprises:

determining that the system address of the originating border router matches a system address of the backup border router; and

determining that the backup border router is the originating border router in response to determining that the system address of the originating border router matches the system address of the backup border router.

10. The method of claim 7 , further comprising:

identifying, in response to receiving the label mapping message, a primary border router as a hop in a primary path between the leaf node and the root node in the multicast network; and

sending a label mapping message to only the primary border router from among the primary border router and the backup border router.

11. The method of claim 10 , further comprising:

mapping the hop of the backup path in response to determining that the backup border router is not the originating border router.

12. A non-transitory computer-readable storage medium including program instructions for causing a border router to perform at least:

identifying, in response to receiving a label mapping message from a network node, a backup border router as a hop in a backup path between a leaf node and a root node in a multicast network including an autonomous system, the label mapping message including a type-length-value, the type-length-value including a system address of an originating border router having generated the label mapping message;

examining the type-length-value to determine the system address of the originating border router;

determining whether the backup border router is the originating border router based on the type-length-value; and

suppressing mapping of the hop in the backup path in response to determining that the backup border router is the originating border router, wherein

the backup border router is separate from the border router.

13. The non-transitory computer-readable storage medium of claim 12 ,

wherein

the determining determines whether the backup border router is the originating border router based on a comparison between the system address of the originating border router and a system address of the backup border router.

14. The non-transitory computer-readable storage medium of claim 12 , wherein the determining comprises:

determining that the system address of the originating border router matches a system address of the backup border router; and

determining that the backup border router is the originating border router in response to determining that the system address of the originating border router matches the system address of the backup border router.

15. The non-transitory computer-readable storage medium of claim 12 , further including program instructions for causing the border router to perform at least:

identifying, in response to receiving the label mapping message, a primary border router as a hop in a primary path between the leaf node and the root node in the multicast network; and

sending a label mapping message to only the primary border router from among the primary border router and the backup border router.

16. The non-transitory computer-readable storage medium of claim 12 , further including program instructions for causing the border router to perform at least:

mapping the hop of the backup path in response to determining that the backup border router is not the originating border router.

17. The non-transitory computer-readable storage medium of claim 12 , further including program instructions for causing the border router to perform at least:

identifying, in response to receiving the label mapping message, a primary border router as a hop in a primary path between the leaf node and the root node in the multicast network;

sending a first label mapping message to the primary border router to map the hop in the primary path; and

sending a second label mapping message to the backup border router to map the hop in the backup path.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 5, 2018
From: BIDGOLI, HOOMAN; CHUNG KAM CHUNG, GEORGES
To: NOKIA TECHNOLOGIES OY
Reel/Frame 045447/0816 →
Continuity (1)
Related Publication 20190312770A1 · Oct 10, 2019