Method and system of collecting topology and inventory data in open radio access network

Patent metadata

Field	Value
Publication number	US-12598108-B2
Application number	US-202318291221-A
Country	US
Kind code	B2
Filing date	Dec 12, 2023
Priority date	Jun 19, 2023
Publication date	Apr 7, 2026
Grant date	Apr 7, 2026

Abstract

A method of collecting, creating or updating topology and inventory data for a network includes receiving a request through an interface of a service management and orchestrator (SMO), wherein the request contains instructions for topology and inventory information to be collected, created or updated. The method further includes transferring the request to a topology and inventory (TE&IV) management module. The method further includes collecting, creating or updating topology and inventory data for at least a first component of the network based on the request. The topology and inventory data includes a relationship information between the first component and at least a second component of the network, and capability information for the first component.

First claim

What is claimed is:

1 . A method of collecting, creating or updating topology and inventory data for a network, the method comprising:
receiving a request through an interface of a service management and orchestrator (SMO), wherein the request contains instructions for topology and inventory information to be collected, created or updated; transferring the request to a topology and inventory (TE&IV) management module; collecting, creating or updating topology and inventory data for at least a first component of the network based on the request, wherein the topology and inventory data includes:
a relationship information between the first component and at least a second component of the network, and
capability information for the first component; and
outputting the collected topology and inventory data through the interface.

2 . The method of claim 1 , wherein the interface is an R1 service application programming interface (API), or a SMO TE&IV service API.

3 . The method of claim 1 , further comprising collecting topology and inventory data based on an information model of the network for a third component of the network, wherein the first component is part of a radio network within the network, and the third component is part of a cloud computing network within the network.

4 . The method of claim 1 , further comprising limiting a depth of collecting of the topology and inventory data within the network topology based on at least one of an identity of a source in the query or a searching depth parameter.

5 . The method of claim 1 , wherein the request includes identifying information for the first component.

6 . The method of claim 5 , wherein the request specifies a relationship type to be searched in the layers below the first component within the network topology.

7 . The method of claim 1 , wherein
collecting, creating or updating the topology and inventory data comprises using a TE&IV model and an application program interface (API), and outputting the collected topology and inventory data comprises transmitting the collected topology and inventory data externally to the TE&IV management module.

8 . A non-transitory computer readable medium configured to store instructions thereon for causing a system to execute a method comprising:
receiving a request through an interface of a service management and orchestrator (SMO), wherein the request contains instructions for topology and inventory information to be collected, created or updated; transferring the request to a topology and inventory (TE&IV) management module; collecting, creating or updating topology and inventory data for at least a first component of the network based on the request, wherein the topology and inventory data includes:
a relationship information between the first component and at least a second component of the network, and
capability information for the first component.

9 . The non-transitory computer readable medium of claim 8 , wherein the interface is an R1 service application programming interface (API), or a SMO TE&IV service API.

10 . The non-transitory computer readable medium of claim 8 , wherein the instructions are further configured to cause the system to collect topology and inventory data based on an information model of the network for a third component of the network, wherein the first component is part of a radio network within the network, and the third component is part of a cloud computing network within the network.

11 . The non-transitory computer readable medium of claim 8 , wherein the instructions are further configured to cause the system to limit a depth of collecting of the topology and inventory data within the network topology based on at least one of an identity of a source in the query or a searching depth parameter.

12 . The non-transitory computer readable medium of claim 8 , wherein the request includes identifying information for the first component.

13 . The non-transitory computer readable medium of claim 12 , wherein the request specifies a relationship type to be searched in the layers below the first component within the network topology.

14 . The non-transitory computer readable medium of claim 8 , wherein
collecting, creating or updating the topology and inventory data comprises using a TE&IV model and an application program interface (API), and outputting the collected topology and inventory data, wherein the outputting comprises transmitting the collected topology and inventory data externally to the TE&IV management module.

15 . A system for collecting, creating, or updating topology and inventory data for a network, the system comprising:
a service management and orchestrator (SMO) configured to:
receive a request through an interface, wherein the request contains a topology and inventory information to be collected, created or updated;
transfer the request to a topology and inventory (TE&IV) management module;
collect, create or update topology and inventory data for at least a first component of the network based on the query, wherein the topology and inventory data includes:
a relationship information between the first component and at least a second component of the network, and
capability information for the first components; and

output the collected topology and inventory data through the interface.

16 . The system of claim 15 , wherein the interface is an R1 service application programming interface (API), or a SMO TE&IV service API.

17 . The system of claim 15 , wherein the SMO is further configured to collect, create or update topology and inventory data for a third component of the network, wherein the first component is part of a radio network within the network, and the third component is part of a cloud computing network within the network.

18 . The system of claim 15 , wherein the SMO is further configured to limit a depth of collecting of the topology and inventory data within the network topology based on at least one of an identity of a source of the query or a depth parameter.

19 . The system of claim 15 , wherein the request includes identifying information for the first component.

20 . The system of claim 19 , wherein the request specifies a relationship type to be searched in layers below the first component.

Assignees

• Rakuten Symphony Inc

Inventors

• Sun Kexuan
• Chamarty Ravi

Classifications

• G06Q10/087

  Inventory or stock management, e.g. order filling, procurement or balancing against orders · CPC title

• H04L67/50

  Network services · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L41/50

  Network service management, e.g. ensuring proper service fulfilment according to agreements · CPC title

• H04L41/0853

  by actively collecting configuration information or by backing up configuration information · CPC title