IP Library › Granted Patent US 12,495,104
Granted Patent B2
US 12,495,104 · App. 18/012,034 · Granted Dec 9, 2025

Data node, data node management method, and data node management program

Inventors: Masatoshi Saito (Musashino, JP); Takayoshi Hirasawa (Musashino, JP)
Assignee: NTT, Inc.
H04L69/324H04L45/645
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 12,495,104
App. No.
18/012,034
Granted
Dec 9, 2025
Kind
B2
Abstract

A data node includes: a bridge layer adapted to mediate messages between a hardware layer adapted to transfer data with reference to an FIB indicating a forwarding address and a plurality of NOSs that set contents of the FIB for the hardware layer, wherein the bridge layer includes: a setting storage unit adapted to store setting information that associates the NOSs with those resources of the hardware layer which are available for use by the NOSs, and a message conversion unit adapted to receive messages setting the contents of the FIB from the NOSs, convert the messages according to the setting information in the setting storage unit so as to contain those resources of the hardware layer which are available for use by the NOSs, and update the contents of the FIB based on the converted messages.

Claims (26)

1 . A data node comprising:

a bridge layer adapted to mediate messages between a hardware layer that transfers data with reference to an Forwarding Information Base (FIB) indicating a forwarding address and a plurality of (Network Operating Systems (NOSs) that set contents of the FIB for the hardware layer, wherein

the bridge layer includes:

a setting storage medium adapted to store setting information that associates the plurality of NOSs with resources of the hardware layer which are available for use by the plurality of NOSs, wherein the resources of the hardware layer comprise one or more ports available for each NOS among the plurality of NOSs, and

a message processing unit, including one or more processors, adapted to receive a message setting the contents of the FIB from a particular NOS among the plurality of NOSs, wherein the message comprises first port information indicating one or more ports unavailable for use by the particular NOS, convert the message according to the setting information in the setting storage medium, wherein the converted message comprises second port information indicating one or more ports available for use by the particular NOS, and update the contents of the FIB based on the converted message.

2 . A data node comprising:

a bridge layer adapted to mediate messages between a hardware layer that transfers data with reference to an FIB indicating a forwarding address and a plurality of NOSs that set contents of the FIB for the hardware layer, wherein

the bridge layer includes:

a setting storage medium adapted to store setting information that associates the plurality of NOSs with resources of the hardware layer which are available for use by the NOSs, wherein the resources of the hardware layer comprise one or more ports available for each NOS among the plurality of NOSs, and

a message processing unit, including one or more processors, adapted to receive a message setting the contents of the FIB from a particular NOS among the plurality of NOSs, wherein the message comprises port information indicating one or more ports available for use by the particular NOS, and update the contents of the FIB based on the message, with reference to the setting information in the setting storage medium, while rejecting messages comprising port information indicating one or more ports unavailable for use by the particular NOS.

3 . The data node according to claim 1 , further comprising an API calling unit including one or more processors, wherein

in a process in which the API calling unit transmits the message containing the resources of the hardware layer which are available for use by the plurality of NOSs to the hardware layer, causing the contents of the FIB to be updated, until the message from one of the plurality of NOSs is completed, message transmission from another of the plurality of NOSs is kept waiting.

4 . A method for managing a data node that includes a bridge layer adapted to mediate messages between a hardware layer that transfers data with reference to a Forwarding Information Base (FIB) indicating a forwarding address and a plurality of Network Operating Systems (NOSs) that set contents of the FIB for the hardware layer, wherein:

the bridge layer includes a setting storage medium, and a message processing unit;

the method comprises:

setting information that associates the plurality of NOSs with resources of the hardware layer which are available for use by the plurality of NOSs is stored in the setting storage medium, wherein the resources of the hardware layer comprise one or more ports available for each NOS among the plurality of NOSs; and

receiving, by the message processing unit, a message setting the contents of the FIB from a particular NOS among the plurality of NOSs, wherein the message comprises first port information indicating one or more ports unavailable for use by the particular NOS;

converting the message according to the setting information in the setting storage medium, wherein the converted message comprises second port information indicating one or more ports available for use by the plurality of NOSs; and

updating the contents of the FIB based on the converted message.

5 . The method for managing the data node according to claim 4 , further comprising:

updating the contents of the FIB based on the converted message comprising the second port information indicating one or more ports available for use by the particular NOS, with reference to the setting information in the setting storage medium, while rejecting messages containing port information indicating one or more ports unavailable for use by the particular NOS.

6 . A non-transitory computer readable medium storing one or more instructions that cause a computer to function as the data node according to claim 1 .

7 . The data node according to claim 2 , further comprising an API calling unit including one or more processors, wherein

in a process in which the API calling unit transmits the message containing the resources of the hardware layer which are available for use by the plurality of NOSs to the hardware layer, causing the contents of the FIB to be updated, until the message from one of the plurality of NOSs is completed, message transmission from another of the plurality of NOSs is kept waiting.

8 . The method for managing the data node according to claim 4 , further comprising:

in a process in which an API calling unit including one or more processors transmits the message containing the resources of the hardware layer which are available for use by the plurality of NOSs to the hardware layer, causing the contents of the FIB to be updated, until the message from one of the plurality of NOSs is completed, message transmission from another of the plurality of NOSs is kept waiting.

Assignments (2)
CHANGE OF NAME Recorded Aug 14, 2025
From: NIPPON TELEGRAPH AND TELEPHONE CORPORATION
To: NTT, INC.
Reel/Frame 072412/0498 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2022
From: SAITO, MASATOSHI; HIRASAWA, TAKAYOSHI
To: NIPPON TELEGRAPH AND TELEPHONE CORPORATION
Reel/Frame 062170/0970 →
Continuity (1)
Related Publication 20230262149A1 · Aug 17, 2023
References Cited (10)
US 8068442B1 · Kompella · 2011 [cited by examiner]
US 20070291773A1 · Khan · 2007 [cited by examiner]
US 20100061366A1 · DelRegno · 2010 [cited by examiner]
US 20140328343A1 · Kapadia · 2014 [cited by examiner]
US 20160191374A1 · Singh · 2016 [cited by examiner]
US 20190104104A1 · Kapadia · 2019 [cited by examiner]
US 20200065141A1 · Pai · 2020 [cited by examiner]
US 20200068014A1 · Sarkar · 2020 [cited by examiner]
US 20200204492A1 · Sarva · 2020 [cited by examiner]
“What is Node Slicing?,” Jupiter Networks, Inc., May 7, 2020, retrieved from URL <https://www.juniper.net/jp/jp/products-services/what-is/node-slicing>, 7 pages (with Machine translation). [cited by applicant]