此為英文文檔 TS-202307-O-RAN-WG2-Non-RT RIC Architecture 3.0

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

TechnicalSpecification

O-RANWorkingGroup2(Non-RTRICandA1interfaceWG)

Non-RTRICArchitecture

Copyright?2023bytheO-RANALLIANCEe.V.

ThecopyingorincorporationintoanyotherworkofpartorallofthematerialavailableinthisspecificationinanyformwithoutthepriorwrittenpermissionofO-RANALLIANCEe.V.isprohibited,savethatyoumayprintordownloadextractsofthematerialofthisspecificationforyourpersonaluse,orcopythematerialofthisspecificationforthepurposeofsendingtoindividualthirdpartiesfortheirinformationprovidedthatyouacknowledgeO-RANALLIANCEasthesourceofthematerialandthatyouinformthethirdpartythattheseconditionsapplytothemandthattheymustcomplywiththem.

O-RANALLIANCEe.V.,BuschkaulerWeg27,53347Alfter,Germany

f

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

Contents

Foreword

4

Modalverbsterminology

4

1Scope

5

2References

5

Normativereferences

5

Informativereferences

6

3Definitionofterms,symbolsandabbreviations

6

Terms

6

Symbols

7

Abbreviations

7

4Overview

7

Non-RTRICinO-RANOverallArchitecture

7

Non-RTRICComposition

8

5Requirements

8

RequirementsfortheNon-RTRICFramework

8

RequirementsforR1

1

1

RequirementsforrApps

1

1

6Non-RTRICArchitecture

1

1

7R1ServiceDefinitions

1

2

GeneralDescription

1

2

Servicemanagementandexposureservices

1

3

Datamanagementandexposureservices

1

3

A1-relatedServices

1

4

7.4.1A1policyrelatedservices

1

4

7.4.2A1enrichmentinformationrelatedservices

1

6

RANOAM-relatedServices

1

6

O2-relatedservices

1

6

AI/MLworkflowservices

1

7

rAppmanagementservices

1

8

8Non-RTRICFunctionDefinitions

1

8

GeneralDescriptions

1

8

R1servicemanagementandexposurefunctions

1

9

8.2.1Serviceregistrationanddiscoveryfunctions

1

9

8.2.2Authenticationandauthorisationfunctions

1

9

Datamanagementandexposurefunctions

1

9

A1-relatedfunctions

2

0

8.4.1A1Policyfunctions

2

0

8.4.2A1enrichmentinformationfunctions

2

1

RANOAM-relatedfunctions

2

1

O2-relatedfunctions

2

2

AI/MLworkflowfunctions

2

2

9ExternalInterfaces

2

2

A1Interface

2

2

OtherInterfaces

2

3

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.2

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

10Procedures

2

3

Datamanagementandexposureprocedures

2

3

10.1.1Subscribedataproceduresindataconsumptionandcollection

2

3

10.1.2Requestdataprocedureindataconsumptionanddatacollection

2

8

10.1.3O1relateddatacollectionproceduresbasedondatasubscription

3

0

10.1.4O2relateddatacollectionproceduresbasedondatasubscription

3

2

10.1.5Dataofferprocedures

3

4

A1-relatedprocedures

3

6

10.2.1EIresultscollectionfromrApps

3

6

O1-relatedprocedures

4

0

10.3.1Alarmqueryprocedure

4

0

10.3.2Changealarmacknowledgementstateprocedure

4

1

RevisionHistory

4

3

History43

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.3

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

Foreword

ThisTechnicalSpecification(TS)hasbeenproducedbyO-RANAlliance.

Modalverbsterminology

Inthepresentdocument"shall","shallnot","should","shouldnot","may","neednot","will","willnot","can"and"cannot"aretobeinterpretedasdescribedinclause3.2oftheO-RANDraftingRules(Verbalformsfortheexpressionofprovisions).

"must"and"mustnot"areNOTallowedinO-RANdeliverablesexceptwhenusedindirectcitation.

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.4

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

1Scope

ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithinO-RANandmaychangefollowingformalO-RANapproval.ShouldtheO-RANAlliancemodifythecontentsofthepresentdocument,itwillbere-releasedbyO-RANwithanidentifyingchangeofversiondateandanincreaseinversionnumberasfollows:

versionxx.yy.zz

where:

xx:thefirstdigit-groupisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.(theinitialapproveddocumentwillhavexx=01).Always2digitswithleadingzeroifneeded.

yy:theseconddigit-groupisincrementedwheneditorialonlychangeshavebeenincorporatedinthedocument.Always2digitswithleadingzeroifneeded.

zz:thethirddigit-groupincludedonlyinworkingversionsofthedocumentindicatingincrementalchangesduringtheeditingprocess.Externalversionsneverincludethethirddigit-group.Always2digitswithleadingzeroifneeded.

ThepresentdocumentspecifiesthetechnicalspecificationfortheNon-RTRIC(RANIntelligentController)architecture.ThisdocumentcollectsrequirementsontheNon-RTRICframework,hostedapplications,andservicesoftheR1interface.ThisdocumentspecifiesNon-RTRICframeworkfunctionalitiesandservicesexposedtotheapplications.

2References

Normativereferences

Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.Forspecificreferences,onlythecitedversionapplies.Fornon-specificreferences,thelatestversionofthereferenceddocument(includinganyamendments)applies.

NOTE:Whileanyhyperlinksincludedinthisclausewerevalidatthetimeofpublication,O-RAN

cannotguaranteetheirlongtermvalidity.

Thefollowingreferenceddocumentsarenecessaryfortheapplicationofthepresentdocument.

[1]3GPPTR21.905:"Vocabularyfor3GPPSpecifications".

[2]O-RAN.WG1.O-RAN-Architecture-Description:“O-RANWorkingGroup1;O-RAN

ArchitectureDescription”.

[3]O-RAN.WG2.Use-Case-Requirements:“O-RANWorkingGroup2;UseCaseand

Requirements”.

[4]O-RAN.WG2.A1GAP:“O-RANWorkingGroup2;A1interface:GeneralAspectsand

Principles”.

[5]O-RAN.WG2.A1AP:“O-RANWorkingGroup2;A1interface:ApplicationProtocol”.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.5

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

[6]

[7]

[8]

[9]

[10]

O-RAN.WG2.A1TP:“O-RANWorkingGroup2;A1interface:TransportProtocol”.O-RAN.WG2.A1TD:“O-RANWorkingGroup2;A1interface:TypeDefinitions”.

O-RAN.WG10.OAM-Architecture:“O-RANWorkingGroup10;O-RANOperationsandMaintenanceArchitecture”.

O-RAN.WG2.R1GAP:“O-RANWorkingGroup2;R1interface:GeneralAspectsandPrinciples”.

O-RAN.WG11.SecReqSpecs:"SecurityRequirementsSpecification".

Informativereferences

Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.Forspecificreferences,onlythecitedversionapplies.Fornon-specificreferences,thelatestversionofthereferenceddocument(includinganyamendments)applies.

NOTE:Whileanyhyperlinksincludedinthisclausewerevalidatthetimeofpublication,O-RAN

cannotguaranteetheirlongtermvalidity.

Thefollowingreferenceddocumentsarenotnecessaryfortheapplicationofthepresentdocumentbuttheyassisttheuserwithregardtoaparticularsubjectarea.

NotApplicable.

3Definitionofterms,symbolsandabbreviations

Terms

Forthepurposesofthepresentdocument,thetermsanddefinitionsgivenin3GPPTR21.905[1]andthefollowingapply.

Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,in3GPPTR21.905[1].

FunctionsanchoredinsidetheNon-RTRICframework:LogicalfunctionsintheSMOframeworkthatarepartoftheNon-RTRICframework.

NOTE:Thedefinitionmakesnoassumptiononthemandatoryoroptionalqualifierofthefunction

beinganchored.

FunctionsanchoredoutsidetheNon-RTRICframework:LogicalfunctionsintheSMOframeworkthatarenotpartoftheNon-RTRICframework.

NOTE:Thedefinitionmakesnoassumptiononthemandatoryoroptionalqualifierofthefunction

beinganchored.

Non-RTRIC(O-RANNon-Real-TimeRANIntelligentController):alogicalfunctionwithinSMOthatenablesnon-real-timecontrolandoptimizationofRANelementsandresources,AI/MLworkflowincludingmodeltrainingandupdates,andpolicy-basedguidanceofapplications/featuresinNear-RTRIC.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.6

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

Near-RTRIC(O-RANNear-Real-TimeRANIntelligentController):alogicalfunctionthatenablesnear-real-timecontrolandoptimizationofRANelementsandresourcesviafine-grained(e.g.UEbasis,Cellbasis)datacollectionandactionsoverE2interface.

Non-anchoredfunctions:LogicalfunctionsintheSMOframeworkthatmayormaynotbepartoftheNon-RTRICframework.

NOTE:Thedefinitionmakesnoassumptiononthemandatoryoroptionalqualifierofthefunction

beingnon-anchored.

R1DataProducer:Anentitycapableofproducingdatawhichcanbeconsumedbyotherentitiesandofregisteringfordiscoveryinformationaboutthetypesofthesedatainthecontextofthedatamanagementandexposureservice.

R1DataConsumer:Anentitycapableofconsumingdataoriginatingfromotherentitiesinthecontextofthedatamanagementandexposureservice.

Symbols

Void.

Abbreviations

Forthepurposesofthepresentdocument,thefollowingabbreviationsapply.

AIArtificialIntelligence

EIEnrichmentInformation

MLMachineLearning

Near-RTRICNear-real-timeRANIntelligentController

Non-RTRICNon-real-timeRANIntelligentController

RANRadioAccessNetwork

SMOServiceManagementandOrchestration

4Overview

Non-RTRICinO-RANOverallArchitecture

Non-RealTimeRANIntelligentController(Non-RTRIC)isthefunctionalityinternaltotheServiceManagementandOrchestration(SMO)frameworkinO-RANoverallarchitecture,asshowninFigure4.1-2ofO-RAN.WG1.O-RAN-Architecture-Description[2].

Non-RTRICrepresentsasubsetoffunctionalityoftheSMOframework.

Non-RTRICsupportsintelligentRANoperationandoptimization.

Non-RTRIClogicallyterminatestheA1interface,anditprovidespolicy-basedguidance,enrichment

information,andAI/MLmodelmanagement[FFS]totheNear-RTRICs.

Non-RTRICcanaccessotherSMOframeworkfunctionalities,forexampleinfluencingwhatis

carriedacrosstheO1,openfronthaulM-planeandO2interface.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.7

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

Non-RTRICComposition

Non-RTRICiscomprisedof:

Non-RTRICFramework–FunctionalityinternaltotheSMOFrameworkthat:

oLogicallyterminatestheA1interfacetotheNear-RTRIC.

oExposessetofR1servicestoNon-RTRICApplications(rApps).

Non-RTRICApplications(rApps)–Applicationsthatleveragethefunctionalitiesavailableinthe

SMO/Non-RTRICframeworktoprovidevalueaddedservicesrelatedtoRANoperationandoptimization.ThescopeofrAppsincludes,butisnotlimitedto,radioresourcemanagement,dataanalytics,andprovidingenrichmentinformation.

5Requirements

RequirementsfortheNon-RTRICFramework

[REQ-NRTFWK-FUN1]

TheNon-RTRICframeworkshallsupportfunctionalitytoregisterservicesalongwiththeirserviceproducersintheNon-RTRICandSMO.

[REQ-NRTFWK-FUN2]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowserviceconsumerstodiscoverservices.

[REQ-NRTFWK-FUN3]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowserviceconsumerstosubscribe/unsubscribenotificationsaboutnewlyregistered/updated/deregisteredservices.

[REQ-NRTFWK-FUN4]

TheNon-RTRICframeworkshallsupportfunctionalitytonotifysubscribedserviceconsumersaboutnewlyregistered/updated/deregisteredservices.

[REQ-NRTFWK-FUN5]

TheNon-RTRICframeworkshallsupportfunctionalitytoauthenticateserviceconsumers.

[REQ-NRTFWK-FUN6]

TheNon-RTRICframeworkshallsupportfunctionalitytoauthorizeserviceconsumerstoaccessservices.

[REQ-NRTFWK-FUN7]

TheNon-RTRICframeworkshallsupportfunctionalitytosendmessagestoandreceivemessagesfromtheNear-RTRICviatheA1interface.

[REQ-NRTFWK-FUN8]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowDataConsumers(includingrApps)toregisterdatatypestheyconsume,ifsuchfunctionalityisnotsupportedintheSMOframework.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.8

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

[REQ-NRTFWK-FUN9]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowDataProducers(includingrApps)toregisterdatatypestheyproduce,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN10]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowDataConsumers(includingrApps)tosubscribe/requestinstancesofregistereddatatypesforconsumption,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN10a]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowDataProducers(includingrApps)toofferinstancesofregistereddatatypesforcollectionandstorage,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN11]

TheNon-RTRICframeworkshallsupportfunctionalitytotrainAI/MLmodels,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN12]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowserviceconsumerstostoreandretrievetrainedAI/MLmodels,ifsuchfunctionalityisnotsupportedintheSMOframework

[REQ-NRTFWK-FUN13]

TheNon-RTRICframeworkshallsupportfunctionalitytomonitortheperformancefordeployedAI/MLmodelsinruntime,ifsuchfunctionalityisnotsupportedintheSMOframework

[REQ-NRTFWK-FUN14]

TheNon-RTRICframeworkmaysupportfunctionalitytocollectexternalenrichmentinformationfromexternalenrichmentinformationsources.

[REQ-NRTFWK-FUN15]

TheNon-RTRICframeworkmaysupportfunctionalitytoretrievetrainedMLmodels(andmetadata)fromexternalAI/MLserviceproviders.

[REQ-NRTFWK-FUN16]

TheNon-RTRICframeworkmaysupportfunctionalitytoallowexternalsourcestoinjectRANintents,suspend/resume/checkrApps,and

configure/check/initiate/suspend/resume/terminateAI/MLtrainingprocesses.

[REQ-NRTFWK-FUN17]

TheNon-RTRICframeworkshallsupportfunctionalitytoconsolidatethealarminformationfrommultiplemanagedentities,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN18]

TheNon-RTRICframeworkshallsupportfunctionalitytostorealarmacknowledgementstateforalarmsoriginatingfrommanagedentitiesthatdonotsupportalarmacknowledgementstatechange,ifsuchfunctionalityisnotsupportedintheSMO

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.9

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

framework.

[REQ-NRTFWK-FUN19]

TheNon-RTRICframeworkshallhavethecapabilitytoidentifythepotentiallyapplicableNear-RTRIC(s)forA1policycreationiftheNear-RTRICidentifierisabsentinthecreateA1policyrequestreceivedfromtherApp.

NOTE:SelectionofpotentiallyapplicableNear-RTRIC(s)maybebased,e.g.,onthecontentofthe

receivedcreateA1policyrequestoronconfiguration.

[REQ-NRTFWK-FUN20]

TheNon-RTRICframeworkshallsupportthefunctionalitytocollecttracedata,frommultiplemanagedentities,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN21]

TheNon-RTRICframeworkshallsupportthefunctionalitytocollectanalyticaldatafromtheNear-RTRIC,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN22]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowDataConsumers(includingrApps)toconsumeDeploymentTelemetrymetricscollectedbytheO2-relatedfunctions.

[REQ-NRTFWK-FUN23]

TheNon-RTRICframeworkshallsupportfunctionalitytoallowDataConsumers(includingrApps)toconsumeInfrastructureTelemetrymetricscollectedbytheO2-relatedfunctions.

[REQ-NRTFWK-FUN24]

TheNon-RTRICframeworkshallsupportfunctionalitythatallowsmanagingtheconfigurationofanrApp,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN25]

TheNon-RTRICframeworkshallsupportfunctionalitythatallowsobtaining,fromanrApp,informationaboutthatrApp'sperformance,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN26]

TheNon-RTRICframeworkshallsupportfunctionalitythatallowsobtaining,fromanrApp,faultinformationrelatedtothatrApp,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN27]

TheNon-RTRICframeworkshallsupportfunctionalitythatallowsobtaining,fromanrApp,logginginformationreportedbytherApp,ifsuchfunctionalityisnotsupportedintheSMOframework.

[REQ-NRTFWK-FUN28]

TheNon-RTRICframeworkshallsupportfunctionalitytostoreloginformationreceivedfromrApps,ifsuchfunctionalityisnotsupportedintheSMOframework.

Inaddition,thesecurityrequirementsfortheNon-RTRICspecifiedinclause5.1.2of[10]apply.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.10

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

RequirementsforR1

O-RAN.WG2.Use-Case-Requirements[3]specifiesR1interfacefunctionalrequirements.

RequirementsforrApps

ThesecurityrequirementsforrAppsspecifiedinclause5.1.2of[10]apply.

6Non-RTRICArchitecture

ThefollowingfiguredepictsthereferencearchitectureoftheNon-RTRICaspartoftheSMOframework.

Figure6-1:Non-RTRICReferenceArchitecture

TherearethreecategoriesoflogicalfunctionsinNon-RTRICframeworkandSMOframework:

FunctionsanchoredinsidetheNon-RTRICframework,whichareindicatedinsolidblueboxin

Figure6-1.

FunctionsanchoredoutsidetheNon-RTRICframework,whichareindicatedinsolidorangeboxin

Figure6-1.

Non-anchoredfunctions,whichareindicatedindashedlineboxinFigure6-1.

ThecategoriesaredefinedinClause3.1.

Thedecompositionoflogicalfunctionsisnotmandatory,anditisuptovendor’simplementation.

NOTE1:TheremightbeotherSMOframeworkfunctionsorotherNon-RTRICframeworkfunctionswhichmayprovideadditionalservicesexposedviatheR1interfaceorprovideEIforA1enrichmentinformationservices.ItisFFS.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.11

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

NOTE2:OtherSMOframeworkfunctionsmaybedefinedbyotherO-RANWGsandthepotentialimpactsonNon-RTRICarchitectureisFFS.

NOTE3:WhethertheA1-relatedfunctionsareanchoredfunctionsornotisFFS.

NOTE4:Amongotherfunctionalities,theOtherSMOframeworkfunctionsalsorealizeOAMfunctionalityrelatedtoRAN-specificnetworkslicing.

TheR1servicesareacollectionofservicesproducedbylogicalfunctionsintheSMO/Non-RTRICframeworkorbyrApps.

R1servicemanagementandexposurefunctionsenable(notlimitedto):ServiceRegistration,ServiceDiscovery,ServiceNotification,Authorization,Authentication,Communicationsupport,andoptionalbootstrapandheartbeatservices.

TherAppmanagementfunctionsenablethemanagementofrAppswithinthecontextoftheSMO/Non-RTRICframework.Suchfunctionsenable(notlimitedto)theconfigurationofrApps,providingaccesstofaultandperformancerelatedinformationfromrApps,andfacilitationofrApploggingfunctionality.ThroughtheuseofR1,rAppmanagementfunctionscanprovideaccesstothesefunctionalitiesinaconsistentmannertoallrApps.SuchconsistencyisparticularlyvaluableasrAppscanbeprovidedindependentlybydifferentrAppvendors.

TheR1terminationenablestheNon-RTRICframeworkandrAppstoexchangemessagestoaccesstheR1servicesviatheR1interface.

Theimplementation-specificinterfaces,whichareindicatedbythedashedlineinFigure6-1,allowthelogicalfunctionsinSMO/Non-RTRICframeworktocommunicatewitheachotherbymeansoutsidethescopeofthepresentdocument.

7R1ServiceDefinitions

GeneralDescription

Aserviceisasetofcapabilitiesrelatedtoeachother,offeredbyaserviceproducertoserviceconsumer(s)forconsumption.Thecapabilitieswithinaservicetypicallyhaveacommonpurposeandcanbeinter-dependent.Inordertoimprovere-usability,themutualcouplingacrossanytwoservicesisusuallyavoidedorminimized.Servicesareproducedbyserviceproducersandconsumedbyserviceconsumersthroughserviceendpoints(typicallyAPIs).Theinteroperabilityofserviceproducersandserviceconsumersisensuredbysupportoftherelatedserviceendpoints,butitdoesnotdependonthedecompositionoflogicalfunctions.Beingaserviceproducerand/oraserviceconsumerisaroleofanrApporofalogicalfunctionintheSMOortheNon-RTRICframework(seeClause6).

ThesetofR1serviceswhichcanbeaccessedviatheR1interfaceincludes(butisnotlimitedto):

Servicemanagementandexposureservices,whichincludeserviceregistrationandservice

discoveryservices,authenticationservices,authorizationservicesandcommunicationsupportservices.TheservicemanagementandexposureservicessupportextensibilityofthesetofR1services.

Datamanagementandexposureservices,whichdeliverdatacreatedorcollectedbyData

ProducerstoDataConsumersaccordingtotheirneeds.

________________________________________________________________________________________________

?2023bytheO-RANALLIANCEe.V.Youruseissubjecttothecopyrightstatementonthecoverpageofthisspecification.12

O-RAN.WG2.Non-RT-RIC-ARCH-R003-v03.00

A1-relatedservices,whichprovideaccesstofunctionalityrelatedtoA1.

AI/MLworkflowservices,whichprovideaccesstoAIandMLworkflow.

RANOAM-relatedservices,whichprovideaccesstoRANOAMfunctionalityrelatedtotheO1and

openfronthaulM-planeinterfaces,andtotheOAMfunctionalityrelatedtoRAN-specificnetworkslicingintheSMOframework.

O2-relatedservices,whichprovideaccesstofunctionalityrelatedtoO2.

rAppmanagementservices,whichprovidefunctionalityformanagingrApps.

NOTE:ApartoftheserviceslistedabovemaybeusedonotherO-RAN-definedinterfacesaswell.

Servicemanagementandexposureservices

Thefollowingservicemanagementandexposureservicesaredefined:

rAppregistration:ItallowsanrApptoregisterwiththeServicemanagementandexposureservices

Producer.

Bootstrapservice(Optional):ItenablesanrApptodiscovertheendpointsoftheservice

managementandexposureservice.

Registrationofservices:Itallowstoregisterserviceswhichincludesstoringandmaintainingprofile

abouteachservice.Itfurtherallowstoderegisterservicesanddeletetheserviceprofile.

Discoveryofservices:Itsupportsservicediscoveryforaserviceconsumertofindservicesbasedon

itsselectioncriteriaifitisprovided.Further,basedonthesubscription,itnotifiesitsserviceconsumersaboutthenewlyregistered/updated/deregisteredservices.

Heartbeatservice(Optional):ItenablesanrApptomaintainitsR1serviceregistrationstatuswith

theServicemanagementandexposureservicesProducer.

Authentication:Itallowstheauthenticationofaserviceproducerand/oraserviceconsumer.

Authorisation:ItsupportstograntServiceConsumersaccesstoregisteredR1servicesandtoallow

serviceproducerstoproduceR1services.

Communicationsupport(Optional):ItsupportsinteractionofR1serviceconsumersandproducers

witheachother.

NOTE:CommunicationsupportisFFS.

Datamanagementandexposureservices

The