Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update o-ran-integration.md #159

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update o-ran-integration.md #159

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
17263a9
Update o-ran-integration.md
NMSVishal Aug 6, 2024
3d18518
Update o-ran-integration.md
NMSVishal Nov 14, 2024
65e5b1f
Update content/en/docs/network-architecture/o-ran-integration.md
NMSVishal Nov 21, 2024
f046ef9
Update content/en/docs/network-architecture/o-ran-integration.md
NMSVishal Nov 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 22 additions & 1 deletion content/en/docs/network-architecture/o-ran-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,8 @@ As of this release, the O-RAN Alliance has not specified O2ims provisioning inte
The primary role of the NFO and DMS services is to provide for the lifecycle management of the cloud deployments for O-RAN NFs. These services have identified the following O-Cloud capabilities that are planned to be developed using Nephio capabilities:

- NF Deployment Lifecycle Management

- NF Termination Lifecycle Management
-
NMSVishal marked this conversation as resolved.
Show resolved Hide resolved
#### NF Deployment Lifecycle Management

##### Introduction
Expand All @@ -123,7 +124,27 @@ NF Deployment Lifecycle Management services implemented using Nephio capabilitie
{{% alert title="Note" color="primary" %}}

In R3 Nephio use cases and component architectures have been defined for the Deploy O-RAN NF use case.
In R3 ,NFO supports OAI O-RAN(OCU-CP,OCU-UP,ODU) NF deployments using below REST API's.
NMSVishal marked this conversation as resolved.
Show resolved Hide resolved

## input will be packagevariant of OAI NF.
NMSVishal marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't this should be a level 2 heading and I don't understand what it means.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @liamfallon , these are the API's of NFO to trigger OAI NF deployment. In R3 we don't have FOCOM support so NFO talks directly with Porch over the API.


##### NFO API For OAI DU NF Deployment:

POST: BASE_URL/nfo/api/v1/operator/du/
GET: BASE_URL/nfo/api/v1/operator/du/
DELETE: BASE_URL/nfo/api/v1/operator/du/

##### NFO API For OAI CU_CP NF Deployment:

POST: BASE_URL/nfo/api/v1/operator/cucp/
GET: BASE_URL/nfo/api/v1/operator/cucp/
DELETE: BASE_URL/nfo/api/v1/operator/cucp/

##### NFO API For OAI CU_UP NF Deployment:

POST: BASE_URL/nfo/api/v1/operator/cuup/
GET: BASE_URL/nfo/api/v1/operator/cuup/
DELETE: BASE_URL/nfo/api/v1/operator/cuup/
{{% /alert %}}

##### Deploy O-RAN NF
Expand Down