Decoupled SMO Architecture Overview

 
Decoupled SMO Flows
 
N. K. Shankar
(nkshankarlfn@gmail.com)
 
Note: 9/19/2023 - This is an early draft version.
Sharing since slides were requested.
Comments welcome.
 
Disaggregated SMO Flows
 
Objective
Develop flows showing interaction between SMO modules, in the
context of end-to-end open-source architecture/implementation
using OSC, ONAP and other open-source code
Motivation
Align open-source work related to SMO with O-RAN trends, esp.
ongoing Decoupled SMO Architecture
Improve synergy, and reduce duplication, among projects
Identify best practices and gaps (note: it is expected that open-source
will not address all gaps)
Provide feedback to O-RAN WG discussions
 
Related work
 
WG1 - Decoupled SMO Architecture (SMOF, SMOS)
See following slides from
WG2 – Non-RT RIC Architecture, R1, A1, DME, SME, AIML
WG6 – O2 DMS, O2 IMS
WG10 – OAM Architecture, O1, OFH-MP
OSC projects: oam, non-rt-ric, smo, aimlfw, sim, inf, etc.
ONAP projects: sdn-c/sdn-r, ves, so, a1, cps, policy, acm, intent etc.
 
Decoupled SMO latest SBA figure (from Annex A)
 
Summary of all the SMOSs defined so far is available in section 6 of the DEC_SMO TR
 
Figure 6.2.2 ‑1: SMOSs in the SMO SBA representation
 
Current 
draft
 view 
of O-RAN 
SMO Architecture (June 2023) 
Active o
ngoing work
 
Ref: 
O-RAN Decoupled SMO Architecture 
Decoupled SMO Architecture TR-R003-v01.00.09
 
O-RU
 
SMO
 
Near-RT RIC
 
OFH-MP
 
O1
 
A1
 
O2
 
O-cloud
 
External Interface
 
O1 Nodes
 
O-DU
 
O-CU
 
Non-RT RIC
 
rApp
Management
 
RAN
NF
FM
 
A1 related
services
 
RAN
NF
CM
 
RAN
NF
PM
 
External Interface
R1 Services
 
SMO Service Communications
 
OSC
 and 
ONAP
 projects related to SMO (draft, expect changes)
 
smo
 
oam
 
non-rt-ric
 
sim
 
sim
 
non-rt-ric
 
ran-sim
 
dmaap
/kafka
 
aimlfw
 
policy ?
 
cps
 
intent
 
dcae
 
inf
 
int
 
acm
 
idam
 
a&ai
 
Relevant projects
 
oof?
Notes:
Figure is meant to
explore alignment to
O-RAN architecture
Each red/blue label is an
osc/onap open source
project/component
We may/do not have or
need 1:1 mapping
between projects and
architecture blocks
 
smo-pkg
 
sdc ?
 
so
 
security-framework
 
5gson
 
e2e-slicing
 
ves
sdn-c
 
Ref: OSC/ONAP SMO Framework: Exploring interactions among SMO-related projects in OSC and ONAP, https://wiki.o-ran-sc.org/download/attachments/3604609/OSC_ONAP_SMO_Framework_v5.pptx?api=v2
 
Proposed SO&A SMOS and ZT loops 
(from Annex A)
 
SMO
Near-RT RIC
 
A1
O1 Nodes
 
O-Cloud
 
O2
 
SMOS Communication
O-RU
R1 Services
Federated O-Cloud
Orchestration and
Management
(FOCOM)
Network
Function
Orchestrator
(NFO)
A1 related
services
RAN
NF PM
RAN
NF CM
RAN
NF FM
 
Non-RT RIC
rApp
Management
TE&IV
Services
DME
Services
SME
Services
 
O1
 
O-FH/
M-Plane
 
ZT Automation
 
Decoupled SMO background – 
SMOSs 
(from Annex A)
 
R
A
N
 
N
F
 
O
A
M
 
r
e
l
a
t
e
d
 
S
M
O
S
s
RAN NF Performance Assurance Management
SMO Service (
NFPM
):
RAN NF Fault Supervision Management SMO
Services (
NFFM
):
RAN NF Provisioning Management SMO Services
(
NFCM
):
N
o
n
-
R
T
 
R
I
C
 
r
e
l
a
t
e
d
 
S
M
O
S
s
rApps Service Management and Exposure
SMOS
S
e
r
v
i
c
e
 
M
a
n
a
g
e
m
e
n
t
 
a
n
d
 
E
x
p
o
s
u
r
e
 
(
S
M
E
)
D
a
t
a
 
M
a
n
a
g
e
m
e
n
t
 
a
n
d
 
E
x
p
o
s
u
r
e
 
(
D
M
E
)
R
A
N
 
a
n
a
l
y
t
i
c
s
 
S
M
O
S
 
T
o
p
o
l
o
g
y
 
E
x
p
o
s
u
r
e
 
a
n
d
 
I
n
v
e
n
t
o
r
y
 
M
a
n
a
g
e
m
e
n
t
(
T
E
&
I
V
)
Visualization and optimization of the network rely
upon knowing and maintaining the relationship
between O-RAN resources (i.e., RAN network view).
Topology Exposure (TE) and Inventory Management
(IV) services provide an up-to-date information of O-
RAN resources and their relationships.
Pending WG10 WIs completion for more details
O
-
C
l
o
u
d
 
r
e
s
o
u
r
c
e
s
 
m
a
n
a
g
e
m
e
n
t
 
a
n
d
o
r
c
h
e
s
t
r
a
t
i
o
n
 
r
e
l
a
t
e
d
Network Function Orchestration SMOS (
NFO
) SMOS
Federated O-Cloud Orchestration and Management
(
FOCOM
) SMOS
N
e
t
w
o
r
k
 
S
l
i
c
e
 
S
u
b
n
e
t
 
M
a
n
a
g
e
m
e
n
t
 
S
M
O
S
 
 
SMO SERVICES (
SMOS
s) IDENTIFIED SO FAR
 
Decoupled SMO background – 
SMOFs 
(from Annex A)
 
SMO FUNCTIONS (
SMOF
s) IDENTIFIED SO FAR
 
RAN NF OAM SMO Function (
RNOAMF
)
Produces 
RAN NF 
OAM SMO Services (NFPM, NFFM, NFCM)
O-Cloud Resources Management and Orchestration SMO Function (
ORMO
 SMOF)
Produces 
NFO and FOCOM services
Non-RT RIC 
SMOF
SMOF interactions
Certain SMOSs are expected to be leveraged by all SMOSs
 
ONGOING PROPOSALS/DISCUSSIONS
Discussion with WG2 rapporteurs and co-chair in Osaka about impacts to make 
SME and DME generic services
,
not limited to rApps consumption and non-RT RIC
TIM.AO-2023.06.19-WG1-Decoupled_SMO_architecture_alignment_F2F.pptx
Outcome: SME is ready to be used as generic SMOS, DME requires some changes in their APIs
Service Orchestration (SO) and Service Assurance (SA) SMOSs
Discussion paper in Osaka (see next slide), ATG decision to follow it with a joint CR:
TES.AO-2023.06.02-WG1-I-DEC_SMO_TR_discussion-paper_SO_Automation-v01.pptx
Policy Management in SMO
Couple of discussion papers in Osaka, to be followed up by a WG1-WG6 joint session
SMO/RAN domain vs Transport management domain 
(details in subsequent slides)
 
Sequence Flows
 
Sequence flows seem to be the best tool to capture interactions
between SMOF/SMOS
Proposed approach
Review existing flows and interactions, and build on existing work
Develop flows using latest terminology from DEC-SMO
Take top-down approach to get the correct high-level structure
Develop detailed flows in places where it makes sense
Following slides show some examples of flows which need to be
harmonized using SMOF/SMOS concepts
DEC-SMO work - example of SMOF/SMOS concepts
O-RAN WGs (WG10, WG2)
OSC work
 
Example 1: WG1 DEC-SMO
 
RNOAMF Fault Supervision Use
Case CR in WG1 DEC-SMO TR
(approved 9/18)
https://oranalliance.atlassian.net/wiki/download/attachments/
2844918001/DCM.AO-2023.06.16-WG1-CR-0003-DEC_SMO-
Fault%20Supervision-v06.docx?api=v2
Sequence diagram in Annex A
Uses new SMOF/SMOS
terminology
RNOAMF
 (RAN NF OAM
SMO Function
) produces ..
NFFM
 (NF Fault Management)
SMO Service
Interaction with
Other SMOS consumer (e.g. rApp)
SME
O-RAN NF (O1 node)
 
Example 2 – WG1 DEC-SMO
 
Topology Management CR in WG1 DEC-SMO (under review)
https://oranalliance.atlassian.net/wiki/download/attachments/2844918001/FJT.AO-2023.06.12-WG1-CR-0001-DEC_SMO-TR_topology_management_service-v04.docx?api=v2
RNOAMF
 (RAN NF OAM SMO Function)
ORMO
 (O-Cloud Resources Management and Orchestration SMO Function)
SO and TE&IV 
(Topology Exposure and Inventory Management ) SMOF
Non-RT RIC 
SMO Function
 
Example 3 – WG10 OAM PM
 
O-RAN.WG10.OAM-Architecture-
R003-v10.00
Figure 4.2.2-2: Measurement Data
File Consumption
https://oranalliance.atlassian.net/wiki/download/attachments/
2211610730/O-RAN.WG10.OAM-Architecture-R003-
v10.00.00.docx?api=v2
Generic reference to:
NFO
OAM Functions
Non-RT RIC
O2 DMS
 
Example 4
 
OSC PM Streaming example
https://wiki.o-ran-sc.org/display/OAM/PM+Streaming
Collaboration between oam and non-rt-ric and sim projects in OSC -
Interactions between rApp and …
.. OSC components in “SMO Common” and “SMO OAM” – Message Router, PM Database, Topology
Service, PM Coordination, PM Collector, VES Collector, OAM Controller
.. OSC sim and RAN Network – need to provide data sources for Topology and RAN Data
 
Example 5
 
O-RAN.WG2.Non-RT-RIC-ARCH-
R003-v04.00 
(July 2023)
https://oranalliance.atlassian.net/wiki/download/attachments/
2340816222/O-RAN.WG2.Non-RT-RIC-ARCH-R003-
v04.00.docx?api=v2
Fig 10.4.2-3 Example workflow
of AI/ML training
Shows rApps interacting with
following:
All shown as “non-anchored functions
in SMO/Non-RT RIC” as per current O-
RAN specs
AI/ML workflow functions 
(details of
SMOF / SMOS status ongoing)
DME
 (SMOS)
Model repo 
(unspecified)
 
 
More work needed!!
Comments/participation welcome
 
Annex A: Backgrund Reference:
WG1 Overview of Decoupled
SMO Architecture
 
https://oranalliance.atlassian.net/wiki/download/attachments/2844918001/ERI-
2023-09-08-WG1_I_1ATG-
Decoupled_SMO_architecture_overview_for_other_WGs_v01.pptx?api=v2
 
Decoupled SMO architecture overview for WG11
 
 
 
 
Cristina Badulescu, Ericsson
 
Septemebr 2023
 
(WG1 DEC_SMO TR rapporteurs: Cristina Badulescu; Li Xiang)
 
Decoupled SMO background – SMO services defined in WGs
 
WG2, WG6 and WG10 have been defining SMO services:
orchestration& cloudification
OAM (FM, PM, CM/provisioning)
Non-RT RIC and exposure to rApps for SMO functionality enhancement
 
[DEC_SMO TR]  Figure 4.1-2: Categories of SMOSs based on documented O-RAN SMO capabilities
 
Decoupled SMO background – External terminations
 
[DEC_SMO TR] 
Figure 4.2‑1: SMO external terminations
 
Existing services of SME and DME enabling service and data exposure both internally and externally
 
Decoupled SMO background – decision for SBA approach
 
ATG decision to approach the SMO architecture in an SBA manner
 
[DEC_SMO TR] Figure 4.1‑3: SBA representation of the documented SMO services in July 2022 specifications
SMO Service (SMOS):
 
Standardized
cohesive set of management,
orchestration and automation
capabilities offered by an SMO
Function.
 
SMO Functions (SMOFs):
 Internal
SMO entities which provide one or
more SMO Services.
Note: An SMO Function exposes
standardized interfaces which enable
interoperability between SMO
Functions
 
Initial SBA depiction
Initial SBA depiction
 
Decoupled SMO latest SBA figure
 
Summary of all the SMOSs defined so far is available in section 6 of the DEC_SMO TR
 
Figure 6.2.2 ‑1: SMOSs in the SMO SBA representation
 
Decoupled SMO background – 
SMOSs
 
R
A
N
 
N
F
 
O
A
M
 
r
e
l
a
t
e
d
 
S
M
O
S
s
RAN NF Performance Assurance Management
SMO Service (
NFPM
):
RAN NF Fault Supervision Management SMO
Services (
NFFM
):
RAN NF Provisioning Management SMO Services
(
NFCM
):
N
o
n
-
R
T
 
R
I
C
 
r
e
l
a
t
e
d
 
S
M
O
S
s
rApps Service Management and Exposure
SMOS
S
e
r
v
i
c
e
 
M
a
n
a
g
e
m
e
n
t
 
a
n
d
 
E
x
p
o
s
u
r
e
 
(
S
M
E
)
D
a
t
a
 
M
a
n
a
g
e
m
e
n
t
 
a
n
d
 
E
x
p
o
s
u
r
e
 
(
D
M
E
)
R
A
N
 
a
n
a
l
y
t
i
c
s
 
S
M
O
S
 
T
o
p
o
l
o
g
y
 
E
x
p
o
s
u
r
e
 
a
n
d
 
I
n
v
e
n
t
o
r
y
 
M
a
n
a
g
e
m
e
n
t
(
T
E
&
I
V
)
Visualization and optimization of the network rely
upon knowing and maintaining the relationship
between O-RAN resources (i.e., RAN network view).
Topology Exposure (TE) and Inventory Management
(IV) services provide an up-to-date information of O-
RAN resources and their relationships.
Pending WG10 WIs completion for more details
O
-
C
l
o
u
d
 
r
e
s
o
u
r
c
e
s
 
m
a
n
a
g
e
m
e
n
t
 
a
n
d
o
r
c
h
e
s
t
r
a
t
i
o
n
 
r
e
l
a
t
e
d
Network Function Orchestration SMOS (NFO) SMOS
Federated O-Cloud Orchestration and Management
(FOCOM) SMOS
N
e
t
w
o
r
k
 
S
l
i
c
e
 
S
u
b
n
e
t
 
M
a
n
a
g
e
m
e
n
t
 
S
M
O
S
 
 
SMO SERVICES (
SMOS
s) IDENTIFIED SO FAR
 
Decoupled SMO background – 
SMOFs
 
SMO FUNCTIONS (
SMOF
s) IDENTIFIED SO FAR
 
RAN NF OAM SMO Function (RNOAMF)
Produces 
RAN NF 
OAM SMO Services (NFPM, NFFM, NFCM)
O-Cloud Resources Management and Orchestration SMO Function (ORMO SMOF)
Produces 
NFO and FOCOM services
Non-RT RIC SMOF
SMOF interactions
Certain SMOSs are expected to be leveraged by all SMOSs
 
ONGOING PROPOSALS/DISCUSSIONS
Discussion with WG2 rapporteurs and co-chair in Osaka about impacts to make 
SME and DME generic services
,
not limited to rApps consumption and non-RT RIC
TIM.AO-2023.06.19-WG1-Decoupled_SMO_architecture_alignment_F2F.pptx
Outcome: SME is ready to be used as generic SMOS, DME requires some changes in their APIs
Service Orchestration (SO) and Service Assurance (SA) SMOSs
Discussion paper in Osaka (see next slide), ATG decision to follow it with a joint CR:
TES.AO-2023.06.02-WG1-I-DEC_SMO_TR_discussion-paper_SO_Automation-v01.pptx
Policy Management in SMO
Couple of discussion papers in Osaka, to be followed up by a WG1-WG6 joint session
SMO/RAN domain vs Transport management domain 
(details in subsequent slides)
 
Proposed SO&A SMOS and ZT loops
 
SMO
Near-RT RIC
 
A1
O1 Nodes
 
O-Cloud
 
O2
 
SMOS Communication
O-RU
R1 Services
Federated O-Cloud
Orchestration and
Management
(FOCOM)
Network
Function
Orchestrator
(NFO)
A1 related
services
RAN
NF PM
RAN
NF CM
RAN
NF FM
 
Non-RT RIC
rApp
Management
TE&IV
Services
DME
Services
SME
Services
 
O1
 
O-FH/
M-Plane
 
ZT Automation
 
WG1-WG9 discussion in Osaka about SMO and TN Management interactions
 
TN Management
 
 
TN Mgmt exposed services
Optics
MW
Packet L2/L3
 
O
u
t
c
o
m
e
:
-  WG9 was asked to define the services that TN Management domain exposes, so SMO can consume them
-
Examples of TN Management services to be exposed to other management domains such as SMO/RAN
management:
 
1.
Expose requests for TN with specific characteristics (e.g., 3GPP NRM containing the characteristics
needed for TN, the attachment circuit definition)
2.
Expose abstracted TN topology that is relevant/consumable by SMO
3.
Expose some FCAPS that are relevant for SMO to understand the SLA fulfilment level for TN (e.g.,
enable monitoring FM, PM for TN by  the SMO)
 
Latest WG1 ATG Architecture related documents
 
O-RAN Architecture Description latest draft:
O-RAN.WG1.OAD-R003-v10.00.docx
 
Decoupled SMO architecture TR latest draft:
O-RAN-WG1.Decoupled-SMO-Architecture-TR-v01.00.09.zip
 
Slide Note
Embed
Share

Develop flows showing interaction between SMO modules in the context of open-source architecture using OSC, ONAP, and other code. The objective is to align open-source work with O-RAN trends, improve synergy, reduce duplication, and provide feedback to O-RAN discussions. Related work includes Decoupled SMO Architecture, Non-RT RIC Architecture, and OAM Architecture among others. Current drafts and figures showcase the latest progress in O-RAN SMO Architecture and OSC/ONAP projects related to SMO.


Uploaded on Mar 27, 2024 | 5 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Decoupled SMO Flows N. K. Shankar (nkshankarlfn@gmail.com) Note: 9/19/2023 - This is an early draft version. Sharing since slides were requested. Comments welcome.

  2. Disaggregated SMO Flows Objective Develop flows showing interaction between SMO modules, in the context of end-to-end open-source architecture/implementation using OSC, ONAP and other open-source code Motivation Align open-source work related to SMO with O-RAN trends, esp. ongoing Decoupled SMO Architecture Improve synergy, and reduce duplication, among projects Identify best practices and gaps (note: it is expected that open-source will not address all gaps) Provide feedback to O-RAN WG discussions

  3. Related work WG1 - Decoupled SMO Architecture (SMOF, SMOS) See following slides from WG2 Non-RT RIC Architecture, R1, A1, DME, SME, AIML WG6 O2 DMS, O2 IMS WG10 OAM Architecture, O1, OFH-MP OSC projects: oam, non-rt-ric, smo, aimlfw, sim, inf, etc. ONAP projects: sdn-c/sdn-r, ves, so, a1, cps, policy, acm, intent etc.

  4. Decoupled SMO latest SBA figure (from Annex A) Summary of all the SMOSs defined so far is available in section 6 of the DEC_SMO TR Figure 6.2.2 -1: SMOSs in the SMO SBA representation 4

  5. Current draft view of O-RAN SMO Architecture (June 2023) Active ongoing work External Interface External Interface SMO rApps Service Mgmnt & Exposure (SME) Data Mgmnt & Exposure (DME) Topology Exposure & Inv. Mgmnt (TE&IV) rApp R1 Services Management SMO Service Communications A1 related services Fed. O-Cloud Orch & Mgmnt (FOCOM) RAN NF FM RAN NF CM RAN NF PM Non-RT RIC NF Orch. (NFO) O1 A1 OFH-MP O2 O1 Nodes Near-RT RIC O-RU O-DU O-CU O-cloud Ref: O-RAN Decoupled SMO Architecture Decoupled SMO Architecture TR-R003-v01.00.09

  6. OSC and ONAP projects related to SMO (draft, expect changes) Relevant projects intent aimlfw int smo-pkg acm dcae sdc ? oof? idam a&ai security-framework 5gson non-rt-ric cps policy ? so smo e2e-slicing dmaap/kafka ves sdn-c non-rt-ric Notes: Figure is meant to explore alignment to O-RAN architecture Each red/blue label is an osc/onap open source project/component We may/do not have or need 1:1 mapping between projects and architecture blocks oam ran-sim sim sim inf Ref: OSC/ONAP SMO Framework: Exploring interactions among SMO-related projects in OSC and ONAP, https://wiki.o-ran-sc.org/download/attachments/3604609/OSC_ONAP_SMO_Framework_v5.pptx?api=v2

  7. Proposed SO&A SMOS and ZT loops (from Annex A) SMO rApp Topology & Inventory (TE&IV) Data Service Service Management and Exposure (SME) Management and Exposure (DME) Orchestration & Assurance (SO&A) R1 Services rApp Management TE&IV Services SME Services DME Services SMOS Communication ZT Automation A1 related services Network Function Orchestrator (NFO) RAN NF PM RAN NF CM RAN NF FM Federated O-Cloud Orchestration and Management (FOCOM) Non-RT RIC A1 O-FH/ M-Plane O2 Near-RT RIC O1 O-Cloud O-RU O1 Nodes SMO Legend: Consumption of services Services specified or under development in O-RAN External interface Synergies between capabilities, typically handled together SMO capabilities (candidate SMOS) O-RAN defined interface Production of services 7

  8. Decoupled SMO background SMOSs (from Annex A) SMO SERVICES (SMOSs) IDENTIFIED SO FAR RAN NF OAM related SMOSs RAN NF Performance Assurance Management SMO Service (NFPM): Topology Exposure and Inventory Management (TE&IV) Visualization and optimization of the network rely upon knowing and maintaining the relationship between O-RAN resources (i.e., RAN network view). RAN NF Fault Supervision Management SMO Services (NFFM): Topology Exposure (TE) and Inventory Management (IV) services provide an up-to-date information of O- RAN resources and their relationships. RAN NF Provisioning Management SMO Services (NFCM): Pending WG10 WIs completion for more details Non-RT RIC related SMOSs rApps Service Management and Exposure SMOS O-Cloud resources management and orchestration related Network Function Orchestration SMOS (NFO) SMOS Federated O-Cloud Orchestration and Management (FOCOM) SMOS Service Management and Exposure (SME) Data Management and Exposure (DME) RAN analytics SMOS Network Slice Subnet Management SMOS 8

  9. Decoupled SMO background SMOFs (from Annex A) SMO FUNCTIONS (SMOFs) IDENTIFIED SO FAR RAN NF OAM SMO Function (RNOAMF) Produces RAN NF OAM SMO Services (NFPM, NFFM, NFCM) O-Cloud Resources Management and Orchestration SMO Function (ORMO SMOF) Produces NFO and FOCOM services Non-RT RIC SMOF SMOF interactions Certain SMOSs are expected to be leveraged by all SMOSs ONGOING PROPOSALS/DISCUSSIONS Discussion with WG2 rapporteurs and co-chair in Osaka about impacts to make SME and DME generic services, not limited to rApps consumption and non-RT RIC TIM.AO-2023.06.19-WG1-Decoupled_SMO_architecture_alignment_F2F.pptx Outcome: SME is ready to be used as generic SMOS, DME requires some changes in their APIs Service Orchestration (SO) and Service Assurance (SA) SMOSs Discussion paper in Osaka (see next slide), ATG decision to follow it with a joint CR: TES.AO-2023.06.02-WG1-I-DEC_SMO_TR_discussion-paper_SO_Automation-v01.pptx Policy Management in SMO Couple of discussion papers in Osaka, to be followed up by a WG1-WG6 joint session SMO/RAN domain vs Transport management domain (details in subsequent slides) 9

  10. Sequence Flows Sequence flows seem to be the best tool to capture interactions between SMOF/SMOS Proposed approach Review existing flows and interactions, and build on existing work Develop flows using latest terminology from DEC-SMO Take top-down approach to get the correct high-level structure Develop detailed flows in places where it makes sense Following slides show some examples of flows which need to be harmonized using SMOF/SMOS concepts DEC-SMO work - example of SMOF/SMOS concepts O-RAN WGs (WG10, WG2) OSC work

  11. Example 1: WG1 DEC-SMO RNOAMF Fault Supervision Use Case CR in WG1 DEC-SMO TR (approved 9/18) https://oranalliance.atlassian.net/wiki/download/attachments/ 2844918001/DCM.AO-2023.06.16-WG1-CR-0003-DEC_SMO- Fault%20Supervision-v06.docx?api=v2 Sequence diagram in Annex A Uses new SMOF/SMOS terminology RNOAMF (RAN NF OAM SMO Function) produces .. NFFM (NF Fault Management) SMO Service Interaction with Other SMOS consumer (e.g. rApp) SME O-RAN NF (O1 node)

  12. Example 2 WG1 DEC-SMO Topology Management CR in WG1 DEC-SMO (under review) RNOAMF (RAN NF OAM SMO Function) ORMO (O-Cloud Resources Management and Orchestration SMO Function) SO and TE&IV (Topology Exposure and Inventory Management ) SMOF Non-RT RIC SMO Function https://oranalliance.atlassian.net/wiki/download/attachments/2844918001/FJT.AO-2023.06.12-WG1-CR-0001-DEC_SMO-TR_topology_management_service-v04.docx?api=v2

  13. Example 3 WG10 OAM PM O-RAN.WG10.OAM-Architecture- R003-v10.00 Figure 4.2.2-2: Measurement Data File Consumption https://oranalliance.atlassian.net/wiki/download/attachments/ 2211610730/O-RAN.WG10.OAM-Architecture-R003- v10.00.00.docx?api=v2 Generic reference to: NFO OAM Functions Non-RT RIC O2 DMS

  14. Example 4 OSC PM Streaming example Collaboration between oam and non-rt-ric and sim projects in OSC - Interactions between rApp and .. OSC components in SMO Common and SMO OAM Message Router, PM Database, Topology Service, PM Coordination, PM Collector, VES Collector, OAM Controller .. OSC sim and RAN Network need to provide data sources for Topology and RAN Data https://wiki.o-ran-sc.org/display/OAM/PM+Streaming

  15. Example 5 O-RAN.WG2.Non-RT-RIC-ARCH- R003-v04.00 (July 2023) https://oranalliance.atlassian.net/wiki/download/attachments/ 2340816222/O-RAN.WG2.Non-RT-RIC-ARCH-R003- v04.00.docx?api=v2 Fig 10.4.2-3 Example workflow of AI/ML training Shows rApps interacting with following: All shown as non-anchored functions in SMO/Non-RT RIC as per current O- RAN specs AI/ML workflow functions (details of SMOF / SMOS status ongoing) DME (SMOS) Model repo (unspecified)

  16. More work needed!! Comments/participation welcome

  17. Annex A: Backgrund Reference: WG1 Overview of Decoupled SMO Architecture https://oranalliance.atlassian.net/wiki/download/attachments/2844918001/ERI- 2023-09-08-WG1_I_1ATG- Decoupled_SMO_architecture_overview_for_other_WGs_v01.pptx?api=v2

  18. Decoupled SMO architecture overview for WG11 Cristina Badulescu, Ericsson Septemebr 2023 (WG1 DEC_SMO TR rapporteurs: Cristina Badulescu; Li Xiang) 18

  19. Decoupled SMO background SMO services defined in WGs WG2, WG6 and WG10 have been defining SMO services: orchestration& cloudification OAM (FM, PM, CM/provisioning) Non-RT RIC and exposure to rApps for SMO functionality enhancement [DEC_SMO TR] Figure 4.1-2: Categories of SMOSs based on documented O-RAN SMO capabilities 19

  20. Decoupled SMO background External terminations Existing services of SME and DME enabling service and data exposure both internally and externally [DEC_SMO TR] Figure 4.2-1: SMO external terminations 20

  21. Decoupled SMO background decision for SBA approach ATG decision to approach the SMO architecture in an SBA manner SMO Service (SMOS): Standardized cohesive set of management, orchestration and automation capabilities offered by an SMO Function. SMO Functions (SMOFs): Internal SMO entities which provide one or more SMO Services. Note: An SMO Function exposes standardized interfaces which enable interoperability between SMO Functions [DEC_SMO TR] Figure 4.1-3: SBA representation of the documented SMO services in July 2022 specifications 21

  22. Decoupled SMO latest SBA figure Summary of all the SMOSs defined so far is available in section 6 of the DEC_SMO TR Figure 6.2.2 -1: SMOSs in the SMO SBA representation 22

  23. Decoupled SMO background SMOSs SMO SERVICES (SMOSs) IDENTIFIED SO FAR RAN NF OAM related SMOSs RAN NF Performance Assurance Management SMO Service (NFPM): Topology Exposure and Inventory Management (TE&IV) Visualization and optimization of the network rely upon knowing and maintaining the relationship between O-RAN resources (i.e., RAN network view). RAN NF Fault Supervision Management SMO Services (NFFM): Topology Exposure (TE) and Inventory Management (IV) services provide an up-to-date information of O- RAN resources and their relationships. RAN NF Provisioning Management SMO Services (NFCM): Pending WG10 WIs completion for more details Non-RT RIC related SMOSs rApps Service Management and Exposure SMOS O-Cloud resources management and orchestration related Network Function Orchestration SMOS (NFO) SMOS Federated O-Cloud Orchestration and Management (FOCOM) SMOS Service Management and Exposure (SME) Data Management and Exposure (DME) RAN analytics SMOS Network Slice Subnet Management SMOS 23

  24. Decoupled SMO background SMOFs SMO FUNCTIONS (SMOFs) IDENTIFIED SO FAR RAN NF OAM SMO Function (RNOAMF) Produces RAN NF OAM SMO Services (NFPM, NFFM, NFCM) O-Cloud Resources Management and Orchestration SMO Function (ORMO SMOF) Produces NFO and FOCOM services Non-RT RIC SMOF SMOF interactions Certain SMOSs are expected to be leveraged by all SMOSs ONGOING PROPOSALS/DISCUSSIONS Discussion with WG2 rapporteurs and co-chair in Osaka about impacts to make SME and DME generic services, not limited to rApps consumption and non-RT RIC TIM.AO-2023.06.19-WG1-Decoupled_SMO_architecture_alignment_F2F.pptx Outcome: SME is ready to be used as generic SMOS, DME requires some changes in their APIs Service Orchestration (SO) and Service Assurance (SA) SMOSs Discussion paper in Osaka (see next slide), ATG decision to follow it with a joint CR: TES.AO-2023.06.02-WG1-I-DEC_SMO_TR_discussion-paper_SO_Automation-v01.pptx Policy Management in SMO Couple of discussion papers in Osaka, to be followed up by a WG1-WG6 joint session SMO/RAN domain vs Transport management domain (details in subsequent slides) 24

  25. Proposed SO&A SMOS and ZT loops SMO rApp Topology & Inventory (TE&IV) Data Service Service Management and Exposure (SME) Management and Exposure (DME) Orchestration & Assurance (SO&A) R1 Services rApp Management TE&IV Services SME Services DME Services SMOS Communication ZT Automation A1 related services Network Function Orchestrator (NFO) RAN NF PM RAN NF CM RAN NF FM Federated O-Cloud Orchestration and Management (FOCOM) Non-RT RIC A1 O-FH/ M-Plane O2 Near-RT RIC O1 O-Cloud O-RU O1 Nodes SMO Legend: Consumption of services Services specified or under development in O-RAN External interface Synergies between capabilities, typically handled together SMO capabilities (candidate SMOS) O-RAN defined interface Production of services 25

  26. WG1-WG9 discussion in Osaka about SMO and TN Management interactions TN Mgmt exposed services TN Management Optics MW Packet L2/L3 Outcome: - WG9 was asked to define the services that TN Management domain exposes, so SMO can consume them - Examples of TN Management services to be exposed to other management domains such as SMO/RAN management: 1. Expose requests for TN with specific characteristics (e.g., 3GPP NRM containing the characteristics needed for TN, the attachment circuit definition) Expose abstracted TN topology that is relevant/consumable by SMO Expose some FCAPS that are relevant for SMO to understand the SLA fulfilment level for TN (e.g., enable monitoring FM, PM for TN by the SMO) 2. 3. 26

  27. Latest WG1 ATG Architecture related documents O-RAN Architecture Description latest draft: O-RAN.WG1.OAD-R003-v10.00.docx Decoupled SMO architecture TR latest draft: O-RAN-WG1.Decoupled-SMO-Architecture-TR-v01.00.09.zip 27

Related


More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#