O-ran near-RT RIC system and / or data structure

Abstract

To provide a radio access network (RAN) control device comprising a near-real time RAN intelligent controller (Near-RT RIC) with a defined structure.SOLUTION: In the RAN control device, a class related to a registration configuration of application software called an xApp is associated with at least one of a class related to an xApp policy, a class related to an xApp messaging configuration, a class related to xApp extension information, and a class related to an xApp API enablement configuration. In the RAN control device, in the Near-RT RIC defined by O-RAN Alliance, the class related to the xApp registration configuration is associated with a class related to an xApp RAN function.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present disclosure relates to the system and / or data structure of an O-RAN Near-RT RIC. [Background technology]

[0002] With the aim of opening up radio access networks (RANs) in mobile communication systems, studies are underway on concepts such as "Open RAN," "O-RAN," and "vRAN." In this specification, "O-RAN" is used as a comprehensive term to refer to these various "open radio access networks." Therefore, "O-RAN" in this specification should not be interpreted as being limited to the standards and specifications of the same name established by the O-RAN Alliance. O-RAN provides a virtualization platform known as O-Cloud (hereinafter referred to as O-Cloud for convenience) that virtually manages a collection of multiple radio access network nodes (RAN nodes). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-83058 Summary of the Invention [Problem to be solved by the invention]

[0004] The O-RAN control unit comprises a Non-RT RIC (Non-Real Time RAN Intelligent Controller) with a relatively long control cycle (e.g., one second or more) that executes application software called rApp, and a Near-RT RIC (Near-Real Time RAN Intelligent Controller) with a relatively short control cycle (e.g., less than one second) that executes application software called xApp. The Near-RT RIC collects large amounts of data from each RAN node (O-CU / O-DU) connected via the E2 interface, the radio units (O-RU) connected to each RAN node, and / or the Non-RT RIC connected via the A1 interface, and is required to process this data within a short control cycle. Despite this, the system and / or data structure of the Near-RT RIC have not been adequately defined.

[0005] The present disclosure has been made in light of these circumstances, and aims to provide a radio access network control device and the like that includes a Near-RT RIC with a defined structure. [Means for solving the problem]

[0006] In order to solve the above problem, in a radio access network control device according to an embodiment of the present disclosure, in an O-RAN Near-RT RIC (Near-Real Time RAN Intelligent Controller), a class related to an E2 node is associated with a class related to an E2 node component configuration.

[0007] Another aspect of the present disclosure is a radio access network control device, which is a Near-Real Time RAN Intelligent Controller (Near-RT RIC) of an O-RAN, in which classes related to E2 nodes are associated with classes related to E2 node RAN functions.

[0008] Yet another aspect of the present disclosure is also a radio access network control device, in which, in an O-RAN Near-RT RIC (Near-Real Time RAN Intelligent Controller), a class related to a registration configuration of an xApp is associated with at least one of a class related to a policy of the xApp, a class related to a messaging configuration of the xApp, a class related to enrichment information of the xApp, and a class related to an API enablement configuration of the xApp.

[0009] Yet another aspect of the present disclosure is a radio access network control device, which is a Near-Real Time RAN Intelligent Controller (Near-RT RIC) of an O-RAN, and in which a class related to an xApp registration configuration is associated with a class related to an xApp RAN function.

[0010] Yet another aspect of the present disclosure is also a radio access network control device, in which, in an O-RAN Near-RT RIC (Near-Real Time RAN Intelligent Controller), a class related to an xApp registration configuration is associated with at least one of a class related to mapping of A1 enrichment information during xApp execution, a class related to mapping of A1 policies during xApp execution, and a class related to mapping of E2 node RAN functions during xApp execution.

[0011] Yet another aspect of the present disclosure is a radio access network control device, which, in a Near-Real Time RAN Intelligent Controller (Near-RT RIC) of an O-RAN, associates a class related to subscriptions with a class related to mapping of E2 node RAN functions during xApp execution.

[0012] Any combination of the above components, or any conversion of these expressions into methods, devices, systems, recording media, computer programs, etc., are also encompassed within the present disclosure. [Effects of the Invention]

[0013] According to the present disclosure, it is possible to provide a radio access network control device and the like that includes a Near-RT RIC with a defined structure. [Brief explanation of the drawings]

[0014] [Figure 1] 1 shows a schematic overview of a radio access network control device. [Figure 2] Schematic diagram of various functions realized by SMO and / or Non-RT RIC and O-Cloud. [Figure 3] Schematically illustrates the system and / or data structure of a Near-RT RIC. [Figure 4] 1 illustrates an example of a class included in xApp runtime data in the platform database. [Figure 5] 10 illustrates an example of a class included in data received from a Non-RT RIC via the A1 interface in the platform database. [Figure 6] 1 illustrates the classes contained in the subscription / routing data in the platform database. [Figure 7] 10 illustrates an example of a class included in the RAN function / RAN parameter of an xApp in the xApp deployment data of the platform database. [Figure 8] Illustrates other classes contained in the xApp deployment data in the platform database. [Figure 9] This shows examples of classes included in the E2 node RAN function / E2 node RAN parameter configuration of the R-NIB. [Figure 10] The following shows examples of classes included in the main configuration of the E2 node of the R-NIB. [Figure 11] Schematic showing examples of relationships between classes in R-NIB. [Figure 12]10 is a schematic diagram illustrating an example of relationships between classes in xApp deployment data in a platform database. [Figure 13] 10A and 10B illustrate schematic examples of relationships between classes in xApp deployment data and xApp runtime data of a platform database. [Figure 14] 10 illustrates a schematic diagram of an example of relationships between classes in the platform database's subscription / routing data and xApp runtime data. [Figure 15] 10 shows a variation of class relationships. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, this embodiment will be described in accordance with "O-RAN," which is a standard and specification established by the O-RAN Alliance. Therefore, this embodiment will use well-known terms defined by "O-RAN" for convenience, but the technology disclosed herein can also be applied to other existing radio access networks such as "Open RAN" and "vRAN," as well as similar radio access networks that may be developed in the future.

[0016] FIG. 1 shows a schematic overview of a radio access network control device according to this embodiment. This radio access network control device is a RAN control device that controls a radio access network compliant with O-RAN. The SMO (Service Management and Orchestration) controls the entire RAN control device or the entire O-RAN, causing each unit to operate in a coordinated manner. The SMO includes a Non-RT RIC (Non-Real Time RAN Intelligent Controller), which functions as an overall control processor responsible for overall control. The Non-RT RIC, which has a relatively long control period (e.g., one second or longer), issues guidelines, policies, guidance, etc. regarding the operation of each RAN node (O-CU and / or O-DU, described below). Specifically, the Non-RT RIC runs application software called rApp and issues operation guidelines for each RAN node to the Near-RT RIC (Near-Real Time RAN Intelligent Controller) via the A1 interface. The Near-RT RIC, which has a relatively short control period (for example, less than one second), runs application software called xApp to control each RAN node (O-CU / O-DU) itself and general-purpose hardware in the radio unit (O-RU) connected to each RAN node through the E2 interface.

[0017] The illustrated RAN node includes an O-CU, which is an O-RAN-compliant central unit (CU), and / or an O-DU, which is an O-RAN-compliant distributed unit (DU). Both the O-CU and O-DU are responsible for baseband processing in O-RAN, but the O-CU is located on the core network side (not shown), and the O-DU is located on the O-RU side, which is an O-RAN-compliant radio unit (RU). The O-CU may be divided into an O-CU-CP that constitutes the control plane (CP) and an O-CU-UP that constitutes the user plane (UP). The O-CU and O-DU may be integrated into a single baseband processing unit. Alternatively, the RAN node may include an O-eNB, which is a base station compliant with O-RAN and the fourth-generation mobile communication system (4G). One or more O-RUs are connected to each RAN node (O-CU / O-DU), and are controlled by a Near-RT RIC via the RAN node. A communication device (UE: User Equipment) within a communication cell provided by each O-RU can be connected to each O-RU and can perform mobile communication with a core network (not shown) via each RAN node (O-CU / O-DU).

[0018] Each RAN node (O-CU / O-DU) and Near-RT RIC provides operation data of each RAN node, each O-RU, and each UE to the SMO via the O1 interface for so-called FCAPS (Fault, Configuration, Accounting, Performance, Security). Based on the operation data obtained via the O1 interface, the SMO updates the operation guidelines of each RAN node issued by the Non-RT RIC to the Near-RT RIC via the A1 interface as needed. Note that the O-RU may be connected to the SMO for FCAPS via the O1 interface or another interface (such as Open Fronthaul M-Plane).

[0019] O-Cloud, a virtualization platform that virtually manages a collection of multiple RAN nodes (O-CU / O-DU), is connected to SMO via the O2 interface. Based on the operational status of multiple RAN nodes (O-CU / O-DU) obtained from O-Cloud via the O2 interface, SMO generates resource allocation guidelines for resource allocation of the multiple RAN nodes and load management guidelines for workload management, and issues them to O-Cloud via the O2 interface.

[0020] Figure 2 shows a schematic diagram of the various functions realized by SMO and / or Non-RT RIC and O-Cloud. SMO mainly realizes three functions: FOCOM (Federated O-Cloud Orchestration and Management), NFO (Network Function Orchestrator), and OAM Function. O-Cloud mainly realizes two functions: IMS (Infrastructure Management Services) and DMS (Deployment Management Services).

[0021] FOCOM manages resources in the O-Cloud while receiving services from the IMS of the O-Cloud through the O2 interface (O2ims). NFO realizes the coordinated operation of a collection of Network Functions (NFs) through multiple NF deployments in the O-Cloud while receiving services from the DMS of the O-Cloud through the O2 interface (O2dms). The NFO may use an OAM function to access deployed NFs through the O1 interface. The OAM function is responsible for FCAPS management of O-RAN managed entities such as RAN nodes. In this embodiment, the OAM function can be a function block that provides callbacks to receive data on faults and operational status of multiple RAN nodes virtually managed by the O-Cloud by monitoring the procedures or procedures of O2ims and / or O2dms. The IMS is responsible for managing O-Cloud resources (hardware) and the software used to manage them, and provides services mainly to FOCOM in the SMO. The DMS is responsible for managing multiple NF deployments in the O-Cloud, specifically starting, monitoring, and terminating them, and provides services primarily to the SMO's NFO.

[0022] Figure 3 shows a schematic diagram of the system and / or data structure of a Near-RT RIC. In the illustrated example, the Near-RT RIC includes a database or platform database and an R-NIB (Radio-Network Information Base). The platform database handles xApp runtime data, xApp deployment data, data received from non-RT RICs via the A1 interface, and subscriptions and routing data. The R-NIB handles E2 Node RAN Function and E2 Node RAN Parameter Configuration, and E2 Node Main Configuration.

[0023] The configuration and / or processing of each part of the Near-RT RIC in Figure 3 will be described in detail below using the concept of a class diagram in Unified Modeling Language (UML). However, the technical ideas of this disclosure are also applicable to systems and / or data represented in modeling languages ​​other than UML or any other notation. As is well known in UML, each rectangular class shown in a class diagram has up to three rows: a class name, attributes (fields), and class operations (methods). In the following example, "generated" shown in the attributes and / or class operations indicates that the data is generated by the class, "PK" stands for primary key constraint, and "FK" stands for foreign key constraint.

[0024] Figure 4 shows examples of classes included in the xApp runtime data in the platform database. The class related to xApp runtime context data has the class name "xAppContextData", the attribute "·xAppContextDataID:<<generated>", and the class operations "·xAppID:<<FK>", "·xAppContextData". The class related to the mapping of A1 enrichment information (A1-EI) during xApp runtime has the class name "xAppA1EIMapping", the attribute "·xAppA1EIMapping:<<generated>", and the class operations "·xAppEIJobID:<<FK>", "·xAppID:<<FK>", and "·eiJobID:<<FK>". The class related to A1 policy mapping during xApp execution has the class name "xAppA1PolicyMapping", the attribute "·xAppA1PolicyMapping:≪generated≫", and the class operations "·xAppPolicyID:≪FK≫", "·xAppID:≪FK≫", and "·policyID:≪FK≫". The class related to Shared Data Layer (SDL) notifications during xApp execution has the class name "SDLNotification", the attribute "·SDLNotificationID:≪generated≫", and the class operations "·xAppID:≪FK≫", "·E2NodeId:≪FK≫". The class related to the mapping of E2 node RAN functions when xApp is executed has the class name "xAppE2NodeRANFunctionMapping", the attributes "·xAppE2NodeRANFunctionMappingID:≪generated≫" and "·xAppRANFunctioninstanceID:≪generated≫", and the class operations "·xAppID:≪FK≫", "·E2NodeID:≪FK≫", "·xAppRANFunctionName:≪FK≫", and "·E2NodeRANFunctionName:≪FK≫".Each class included in these xApp runtime data is described in UML as follows:

[0025] xAppE2NodeRANFunctionMapping:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$xAppID xAppE2NodeRANFunctionMapping:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$E2NodeID xAppE2NodeRANFunctionMapping:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$xAppRANFunctionName xAppE2NodeRANFunctionMapping:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$E2NodeRANFunctionName

[0026] xAppA1PolicyMapping:$xAppA1PolicyMappinID:$xAppPolicyID:$xAppID xAppA1PolicyMapping:$xAppA1PolicyMappinID:$xAppPolicyID:$policyID

[0027] xAppA1EIMapping:$xAppA1EIMappingID:$xAppEIJobID:$xAppID xAppA1EIMapping:$xAppA1EIMappingID:$xAppEIJobID:$eiJobID

[0028] xAppContextData:$xAppContextDataID:$xAppID xAppContextData:$xAppContextDataID:$xAppContextData

[0029] SDLNotification:$SDLNotificationID:$xAppID SDLNotification:$SDLNotificationID:$E2NodeId

[0030] Figure 5 shows an example of classes included in data received from Non-RT RIC via the A1 interface in the platform database (Data Received from Non-RT RIC via A1). The class related to A1 Enrichment Information (A1-EI) received from Non-RT RIC has the class name "nonRTA1EI", the attribute "eiJobID:<<generated>>", and the class operations "eiTypeID", "eiTypeObject", "eiJobObject", and "eiJobStatusObject". The class related to A1 policy received from Non-RT RIC has the class name "nonRTA1Policy", the attribute "policyID:<<generated>>", and the class operations "policyTypeID", "policyObject", "policyTypeObject", and "policyStatusObject". Each class included in the data received from Non-RT RIC via the A1 interface is described in UML as follows:

[0031] nonRTA1Policy:$policyID:$policyTypeID nonRTA1Policy:$policyID:$policyObject nonRTA1Policy:$policyID:$policyTypeObject nonRTA1Policy:$policyID:$policyStatusObject

[0032] nonRTA1EI:$eiJobID:$eiTypeID nonRTA1EI:$eiJobID:$eiTypeObject nonRTA1EI:$eiJobID:$eiJobObject nonRTA1EI:$eiJobID:$eiJobStatusObject

[0033] Figure 6 shows an example of classes included in the subscriptions and routing data in the platform database. The class related to messaging routes has the class name "MessagingRoute", attributes "·messagingRouteID:<<generated>>", "·requestID:<<FK>>", "·distributionID:<<FK>>", and "messageType", and class operations "senderEndPoint(hostname / IP.port - InstanceID)" and "receiverEndPoint(hostname / IP.port ? InstanceID="). The class related to distribution has the class name "Distribution", attributes "·distributionID:<<generated>>", "·requestID:<<FK>>", and class operations "xAppInstanceID", "E2TerminationInstanceID", "eventTrigger:(from RANSubFunction)", and "actionID:(from The subscription-related classes have "Subscription" as the class name, "·requestID:[requestorID(xAppID),xAppInstanceID]≪generated≫" and "·subscriptionManagerInstanceID:≪generated≫" as attributes, and "·distributionList:distributionID[]≪FK≫" and "·xAppE2NodeRANFunctionMappingID:≪FK≫" as class operations. Each class included in this subscription / routing data is described in UML as follows:

[0034] Subscription:$requestID:[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$distributionList:$distributionID[] Subscription:$requestID:[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$xAppE2NodeRANFunctionMappingID

[0035] Distribution:$distributionID:$requestID:$xAppInstanceID Distribution:$distributionID:$requestID:$E2TerminationInstanceID Distribution:$distributionID:$requestID:$eventTrigger(from RANSubFunction) Distribution:$distributionID:$requestID:$actionID(from RANSubFunction)

[0036] MessagingRoute:$messagingRouteID:$messageType:$requestID:$distributionID:$senderEndPoint(hostname / IP.port - InstanceID) MessagingRoute:$messagingRouteID:$messageType:$requestID:$distributionID:$receiverEndPoint(hostname / IP.port - InstanceID)

[0037] 7 illustrates classes included in xApp RAN Functions and xApp RAN Parameters in the xApp Deployment Data of the platform database. The class related to xApp RAN parameters has a class name of "xAppRANParameter", attributes of "·xAppRANParameterID:<<generated>>" and "·xAppRANFunctionName:<<FK>>", and class operations of "xAppRANParameterName" and "xAppRANParameterType". The class related to xApp RAN functions has a class name of "xAppRANFunction", attributes of "·xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]<<PK>", and class operations of "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" and "version". The class for the RAN sub-function of xApp has the class name "xAppRANSubFunction", the attributes "·xAppSubFunctionTypeID:[]≪PK≫generated", "·xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]:≪FK≫", and the class operations "RICEventTriggerStyleList:[ricStyleType,ricStyleName,ricFormatType]", "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType], "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType], "RICControlStyleList:[ricControlStyleType,ricControlStyleName,ricControlFormatType,ricControlHeaderFormatType,ricControlMessageFormatType,ricCallProcessIDFormatType,ricControlOutcomeFormatType,RANparameterIDList:xAppRANparameterID[],]", "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:xAppRANparameterID[],]". Each class included in these xApp RAN functions / xApp RAN parameters is described in UML as follows:

[0038] xAppRANFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]: $xAppSubFunctionTypeList:$xAppSubFunctionTypeID xAppRANFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$version

[0039] xAppRANSubFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeID:$RICEventTriggerStyleList:[$ricStyleType,$ricStyleName, ricFormatType] xAppRANSubFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeID:$RICReportStyleList :[$ricReportStyleType,$ricReportStyleName, $ricReportActionFormatType,$RANparameterIDList :$xAppRANparameterID[], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType] xAppRANSubFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$xAppSubFunctionTypeID:$RICInsertStyleList : [$ricInsertStyleType, $ricInsertStyleName, $ricInsertActionFormatType,$RANparameterIDList : $xAppRANparameterID []], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType, $ricCallProcessIDFormatType] xAppRANSubFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$xAppSubFunctionTypeID:$RICControlStyleList : [$ricControlStyleType,$ricControlStyleName,$ricControlFormatType, $ricControlHeaderFormatType, $ricControlMessageFormatType,$ricCallProcessIDFormatType, $ricControlOutcomeFormatType,$RANparameterIDList : $xAppRANparameterID [], ] xAppRANSubFunction:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$xAppSubFunctionTypeID:$RICPolicyStyleList : [$ricPolicyStyleType, $ricPolicyStyleName, $ricPolicyActionFormatType, $RANparameterIDList : $xAppRANparameterID [],]

[0040] xAppRANParameter:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$xAppRANParameterID:$xAppRANParameterName xAppRANParameter:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$xAppRANParameterID:$xAppRANParameterType

[0041] Figure 8 shows examples of other classes included in the xApp Deployment Data of the platform database. The class related to xApp policy has the class name "xAppPolicy", the attributes "·xAppPolicyID:<<generated>>" and "·xAppID:<<FK>>", and the class operations "·xAppRANFunctionList:xAppRANFunctionName[]<<FK>>", "policyObject", "policyTypeObject", and "policyStatusObject". The class related to xApp registration configuration has the class name "xAppRegistrationConfig", the attribute "·xAppID:≪generated≫", and the class operations "·authorizedAPIList:APIType[]≪FK≫", "·xAppRANFunctionList:xAppRANFunctionName[]≪FK≫", "·xAppPolicyIDList:xAppPolicyID[]≪FK≫", "·xAppEIJobIDList:xAppEIJobID[]≪FK≫", "·SDLNotificationIDList:SDLNotificationID[]≪FK≫", "xAppMessagingConfigID≪FK≫", "probeList[]", "metricList[]", "containerList[]", "name", "vendor", and "version". The class related to the messaging configuration of xApp has the class name "xAppMessagingConfig", the attributes "·xAppMessagingConfigID≪generated≫" and "·xAppID:≪FK≫", and the class operations "hostname / IP", "port", "rxMessageList:messageType[]", and "txMessageList:messageType[]".The class related to the xApp Enrichment Information (EI) has the class name "xAppEI", the attributes "·xAppEIJpbID:≪generated≫" and "·xAppID:≪FK≫", and the class operations "eiTypeObject", "eiJobObject", and "eiJobStatusObject". The class related to the xApp API enablement configuration has the class name "xAppAPIEnablementConfig", the attributes "·APIType≪generated≫" and "·xAppID:≪FK≫", and the class operations "authorizationStatus", "servingAreaInfo", "protocols", and "Interfaces". Each class included in these xApp deployment data is described in UML as follows:

[0042] xAppRegistrationConfig:$xAppID:$authorizedAPIList:$APIType[] xAppRegistrationConfig:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName[] xAppRegistrationConfig:$xAppID:$xAppPolicyIDList:$xAppPolicyID[] xAppRegistrationConfig:$xAppID:$xAppEIJobIDList:$xAppEIJobID[] xAppRegistrationConfig:$xAppID:$SDLNotificationIDList:$SDLNotificationID[] xAppRegistrationConfig:$xAppID:$xAppMessagingConfigID xAppRegistrationConfig:$xAppID:$probeList[] xAppRegistrationConfig:$xAppID:$metricList[] xAppRegistrationConfig:$xAppID:$containerList[] xAppRegistrationConfig:$xAppID:$name xAppRegistrationConfig:$xAppID:$vendor xAppRegistrationConfig:$xAppID:$version

[0043] xAppAPIEnablementConfig:$APIType:$xAppID:$authorizationStatus xAppAPIEnablementConfig:$APIType:$xAppID:$servingAreaInfo xAppAPIEnablementConfig:$APIType:$xAppID:$protocols xAppAPIEnablementConfig:$APIType:$xAppID:$interfaces

[0044] xAppMessagingConfig:$xAppMessagingConfigID:$xAppID:$hostname / IP xAppMessagingConfig:$xAppMessagingConfigID:$xAppID:$port xAppMessagingConfig:$xAppMessagingConfigID:$xAppID:$rxMessageList:messageType[] xAppMessagingConfig:$xAppMessagingConfigID:$xAppID:$txMessageList:messageType[]

[0045] xAppPolicy:$xAppPolicyID:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName[] xAppPolicy:$xAppPolicyID:$xAppID:$policyObject xAppPolicy:$xAppPolicyID:$xAppID:$policyTypeObject xAppPolicy:$xAppPolicyID:$xAppID:$policyStatusObject

[0046] xAppEI:$xAppEIJobID:$xAppID:$eiTypeObject xAppEI:$xAppEIJobID:$xAppID:$eiJobObject xAppEI:$xAppEIJobID:$xAppID:$eiJobStatusObject

[0047] Figure 9 illustrates classes included in the E2 Node RAN Function and E2 Node RAN Parameter Configuration of the R-NIB. The class related to the E2 node RAN parameter has a class name of "E2NodeRANParameter", attributes of "·E2NodeRANParameterID:<<generated>>" and "·E2NodeRANFunctionName:<<FK>>", and class operations of "E2NodeRANParameterName" and "E2NodeRANParameterType". The class related to the E2 node RAN function has a class name of "E2NodeRANFunction", attributes of "·E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]<<PK>", and class operations of "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" and "version". The class for the E2 node RAN subfunction has the class name "E2NodeRANSubFunction", the attributes "·E2NodeSubFunctionTypeID:[]≪PK≫generated", "·E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]:≪FK≫", and the class operations "RICEventTriggerStyleList:[ricStyleType,ricStyleName,ricFormatType]", "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:E2NodeRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType]", "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:E2NodeRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType]", "RICControlStyleList:[ricControlStyleType,ricControlStyleName,ricControlFormatType,ricControlHeaderFormatType,ricControlMessageFormatType,ricCallProcessIDFormatType,ricControlOutcomeFormatType,RANparameterIDList:E2NodeRANparameterID[],]", "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:E2NodeRANparameterID[],]". Each class included in these E2Node RAN function / E2Node RAN parameter configurations is described in UML as follows:

[0048] E2NodeRANFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]: $E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID E2NodeRANFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$version

[0049] E2NodeRANSubFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeID:$RICEventTriggerStyleList:[$ricStyleType,$ricStyleName, ricFormatType] E2NodeRANSubFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeID:$RICReportStyleList :[$ricReportStyleType,$ricReportStyleName, $ricReportActionFormatType,$RANparameterIDList :$E2NodeRANparameterID[], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType] E2NodeRANSubFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$E2NodeSubFunctionTypeID:$RICInsertStyleList : [$ricInsertStyleType, $ricInsertStyleName, $ricInsertActionFormatType,$RANparameterIDList : $E2NodeRANparameterID []], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType, $ricCallProcessIDFormatType] E2NodeRANSubFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$E2NodeSubFunctionTypeID:$RICControlStyleList : [$ricControlStyleType,$ricControlStyleName,$ricControlFormatType, $ricControlHeaderFormatType, $ricControlMessageFormatType,$ricCallProcessIDFormatType, $ricControlOutcomeFormatType,$RANparameterIDList : $E2NodeRANparameterID [], ] E2NodeRANSubFunction:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$E2NodeSubFunctionTypeID:$RICPolicyStyleList : [$ricPolicyStyleType, $ricPolicyStyleName, $ricPolicyActionFormatType, $RANparameterIDList : $E2NodeRANparameterID [],]

[0050] E2NodeRANParameter:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$E2NodeRANParameterID:$E2NodeRANParameterName E2NodeRANParameter:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance]:$E2NodeRANParameterID:$E2NodeRANParameterType

[0051] Figure 10 shows an example of classes included in the E2 Node Main Configuration of R-NIB. The class related to the E2 node component configuration has the class name "E2NodeComponentConfig", the attributes "·E2NodeComponentID:<<generated>>" and "·E2NodeID:<<FK>>", and the class operations "E2NodeComponentConfiguration" and "version". The class related to the E2 node has the class name "E2Node", the attribute "·E2NodeID:<<generated>>", and the class operations "E2NodeComponentConfigList:E2NodeComponentID[]<<FK>>", "E2NodeRANFunctionList:E2NodeRANFunctionName[]<<FK>>", and "E2NodeInfoVersion". Each class included in these E2 node main configurations is described in UML as follows:

[0052] E2Node:$E2NodeID:$E2NodeComponentConfigList:$E2NodeComponentID[] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName[] E2Node:$E2NodeID:$E2NodeInfoVersion

[0053] E2NodeComponentConfig:$E2NodeComponentID:$E2NodeComponentConfiguration E2NodeComponentConfig:$E2NodeComponentID:$Version

[0054] Next, the relationships between the classes included in the above platform database (xApp runtime data, xApp deployment data, data received from Non-RT RIC via the A1 interface, subscription / routing data, etc.) and R-NIB (E2 node RAN function / E2 node RAN parameter configuration, E2 node main configuration) will be explained in detail using the concept of a UML class diagram. Note that in a general class diagram, types such as association, aggregation, composition, dependency, generalization, specialization, realization, and implementation are defined as relationships between classes, and in this embodiment, appropriate types of relationships are set between classes according to the context, UML example, and notation example of each diagram.

[0055] FIG. 11 shows a schematic example of the relationships between classes in R-NIB.

[0056] The following statement relates the class "E2Node" in the E2 node main configuration (Figure 10) to the class "E2NodeComponentConfig". Specifically, the attribute "E2NodeID" in the class "E2Node" is related to the attribute "E2NodeComponentID" and the class operations "E2NodeComponentConfiguration" and "version" in the class "E2NodeComponentConfig" via the class operation "E2NodeComponentConfigList:E2NodeComponentID[]".

[0057] E2Node:$E2NodeID:$E2NodeComponentConfigList:$E2NodeComponentID:$E2NodeComponentConfiguration E2Node:$E2NodeID:$E2NodeComponentConfigList:$E2NodeComponentID:$version

[0058] The following description relates the class "E2Node" in the E2 node main configuration (Figure 10) to the classes "E2NodeRANFunction", "E2NodeRANSubFunction", and "E2NodeRANParameter" in the E2 node RAN function / E2 node RAN parameter configuration (Figure 9). As shown in Figure 11, the class "E2Node" is related to the class "E2NodeRANFunction", the class "E2NodeRANFunction" is related to the class "E2NodeRANSubFunction", and the class "E2NodeRANSubFunction" is related to the class "E2NodeRANParameter".

[0059] The following description associates the attribute "E2NodeID" in the class "E2Node" with the attribute "E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "E2NodeRANFunction" and the class operations "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" and "version" via the class operation "E2NodeRANFunctionList:E2NodeRANFunctionName[]".

[0060] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID[] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$version

[0061] The following description associates the attribute "E2NodeID" in the class "E2Node" with the attribute "E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "E2NodeRANFunction" and the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" via the class operation "E2NodeRANFunctionList:E2NodeRANFunctionName[]".Furthermore, the class operation "E2NodeSubFunctionTypeList: E2NodeSubFunctionTypeID[]" is associated with the attribute "E2NodeSubFunctionTypeID" in the class "E2NodeRANSubFunction" and the class operations "RICEventTriggerStyleList: [ricStyleType, ricStyleName, ricFormatType]", "RICReportStyleList: [ricReportStyleType, ricReportStyleName, ricReportActionFormatType, RANparameterIDList: E2NodeRANparameterID[], ricIndicationHeaderFormatType, ricIndicationMessageFormatType]", "RICInsertStyleList: [ricInsertStyleType, ricInsertStyleName, ricInsertActionFormatType, RANparameterIDList: E2NodeRANparameterID[], ricIndicationHeaderFormatType, ricIndicationMessageFormatType, ricCallProcessIDFormatType]", "RICControlStyleList: [ricControlStyleType, ricControlStyleName, ricControlFormatType, ricControlHeaderFormatType, ricControlMessageFormatType, ricCallProcessIDFormatType, ricControlOutcomeFormatType, RANparameterIDList: E2NodeRANparameterID[],]", "RICPolicyStyleList: [ricPolicyStyleType, ricPolicyStyleName, ricPolicyActionFormatType, RANparameterIDList: E2NodeRANparameterID[],]".

[0062] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICEventTriggerStyleList:[$ricStyleType,$ricStyleName, ricFormatType] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICReportStyleList :[$ricReportStyleType,$ricReportStyleName, $ricReportActionFormatType,$RANparameterIDList :$E2NodeRANparameterID[], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICInsertStyleList : [$ricInsertStyleType, $ricInsertStyleName, $ricInsertActionFormatType,$RANparameterIDList : $E2NodeRANparameterID []], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType, $ricCallProcessIDFormatType] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICControlStyleList : [$ricControlStyleType,$ricControlStyleName,$ricControlFormatType, $ricControlHeaderFormatType, $ricControlMessageFormatType,$ricCallProcessIDFormatType, $ricControlOutcomeFormatType,$RANparameterIDList : $E2NodeRANparameterID [], ] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICPolicyStyleList : [$ricPolicyStyleType, $ricPolicyStyleName, $ricPolicyActionFormatType, $RANparameterIDList : $E2NodeRANparameterID [],]

[0063] The following description associates the attribute "E2NodeID" in the class "E2Node" with the attribute "E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "E2NodeRANFunction" and the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" via the class operation "E2NodeRANFunctionList:E2NodeRANFunctionName[]". Furthermore, the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" is associated with the attribute "E2NodeSubFunctionTypeID" in the class "E2NodeRANSubFunction" and the class operation "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:E2NodeRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType]". Furthermore, the class operation "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:E2NodeRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType]" is associated with the attribute "E2NodeRANparameterID" in the class "E2NodeRANParameter" and the class operations "E2NodeRANParameterName" and "E2NodeRANParameterType".

[0064] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICReportStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterName E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICReportStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterType

[0065] The following description associates the attribute "E2NodeID" in the class "E2Node" with the attribute "E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "E2NodeRANFunction" and the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" via the class operation "E2NodeRANFunctionList:E2NodeRANFunctionName[]". Furthermore, the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" is related to the attribute "E2NodeSubFunctionTypeID" in the class "E2NodeRANSubFunction" and the class operation "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:E2NodeRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType]". Furthermore, the class operation "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:E2NodeRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType]" is related to the attribute "E2NodeRANparameterID" in the class "E2NodeRANParameter" and the class operations "E2NodeRANParameterName" and "E2NodeRANParameterType".

[0066] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICInsertStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterName E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICInsertStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterType

[0067] The following description associates the attribute "E2NodeID" in the class "E2Node" with the attribute "E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "E2NodeRANFunction" and the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" via the class operation "E2NodeRANFunctionList:E2NodeRANFunctionName[]". Furthermore, the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" is related to the attribute "E2NodeSubFunctionTypeID" in the class "E2NodeRANSubFunction" and the class operation "RICControlStyleList:[ricControlStyleType,ricControlStyleName,ricControlFormatType,ricControlHeaderFormatType,ricControlMessageFormatType,ricCallProcessIDFormatType,ricControlOutcomeFormatType,RANparameterIDList:E2NodeRANparameterID[],]".Furthermore, the class operation "RICControlStyleList: [ricControlStyleType, ricControlStyleName, ricControlFormatType, ricControlHeaderFormatType, ricControlMessageFormatType, ricCallProcessIDFormatType, ricControlOutcomeFormatType, RANparameterIDList: E2NodeRANparameterID[],]" is associated with the attribute "E2NodeRANparameterID" in the class "E2NodeRANParameter" and the class operations "E2NodeRANParameterName" and "E2NodeRANParameterType".

[0068] E2Node: $E2NodeID: $E2NodeRANFunctionList: $E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance : $E2NodeSubFunctionTypeList: $E2NodeSubFunctionTypeID: $RICControlStyleList: $RANparameterIDList : $E2NodeRANparameterID: $E2NodeRANParameterName E2Node: $E2NodeID: $E2NodeRANFunctionList: $E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICControlStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterType

[0069] As shown below, the attribute "E2NodeID" in the class "E2Node" is related to the attribute "E2NodeRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" and the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" in the class "E2NodeRANFunction" via the class operation "E2NodeRANFunctionList:E2NodeRANFunctionName[]". Furthermore, the class operation "E2NodeSubFunctionTypeList:E2NodeSubFunctionTypeID[]" is related to the attribute "E2NodeSubFunctionTypeID" in the class "E2NodeRANSubFunction" and the class operation "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:E2NodeRANparameterID[],]". Furthermore, the class operation "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:E2NodeRANparameterID[],]" is associated with the attribute "E2NodeRANparameterID" in the class "E2NodeRANParameter" and the class operations "E2NodeRANParameterName" and "E2NodeRANParameterType".

[0070] E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICPolicyStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterName E2Node:$E2NodeID:$E2NodeRANFunctionList:$E2NodeRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$E2NodeSubFunctionTypeList:$E2NodeSubFunctionTypeID:$RICPolicyStyleList:$RANparameterIDList :$E2NodeRANparameterID:$E2NodeRANParameterType

[0071] FIG. 12 shows a schematic example of the relationships between classes in the xApp deployment data of the platform database.

[0072] The following statement relates the class "xAppRegistrationConfig" in the xApp deployment data (Figure 8) to the class "xAppAPIEnablementConfig." Specifically, the attribute "xAppID" in the class "xAppRegistrationConfig" is related to the attribute "APIType" and the class operations "authorizationStatus," "servingAreaInfo," "protocols," and "Interfaces" in the class "xAppAPIEnablementConfig" via the class operation "authorizedAPIList:APIType[]."

[0073] xAppRegistrationConfig:$xAppID:$authorizedAPIList:$APIType:$authorizationStatus xAppRegistrationConfig:$xAppID:$authorizedAPIList:$APIType:$servingAreaInfo xAppRegistrationConfig:$xAppID:$authorizedAPIList:$APIType:$protocols xAppRegistrationConfig:$xAppID:$authorizedAPIList:$APIType:$interfaces

[0074] The following statement relates the class "xAppRegistrationConfig" in the xApp deployment data (Figure 8) to the class "xAppMessagingConfig." Specifically, the attribute "xAppID" in the class "xAppRegistrationConfig" is related to the attributes "xAppMessagingConfigID" and "xAppID" in the class "xAppMessagingConfig" and the class operations "hostname / IP," "port," "rxMessageList:messageType[]," and "txMessageList:messageType[]" via the class operation "xAppMessagingConfigID."

[0075] xAppRegistrationConfig:$xAppID:$xAppMessagingConfigID:$xAppID:$hostname / IP xAppRegistrationConfig:$xAppID:$xAppMessagingConfigID:$xAppID:$port xAppRegistrationConfig:$xAppID:$xAppMessagingConfigID:$xAppID:$rxMessageList:messageType[] xAppRegistrationConfig:$xAppID:$xAppMessagingConfigID:$xAppID:$txMessageList:messageType[]

[0076] The following statement relates the class "xAppRegistrationConfig" in the xApp deployment data (Figure 8) to the class "xAppPolicy." Specifically, the attribute "xAppID" in the class "xAppRegistrationConfig" is related to the attribute "xAppPolicyID" in the class "xAppPolicy" and the class operations "xAppRANFunctionList:xAppRANFunctionName[]," "policyObject," "policyTypeObject," and "policyStatusObject" via the class operation "xAppPolicyIDList:xAppPolicyID[]."

[0077] xAppRegistrationConfig:$xAppID:$xAppPolicyID:$xAppRANFunctionList:$xAppRANFunctionName[] xAppRegistrationConfig:$xAppID:$xAppPolicyID:$policyObject xAppRegistrationConfig:$xAppID:$xAppPolicyID:$policyTypeObject xAppRegistrationConfig:$xAppID:$xAppPolicyID:$policyStatusObject

[0078] The following statement relates the class "xAppRegistrationConfig" in the xApp deployment data (Figure 8) to the class "xAppEI." Specifically, the attribute "xAppID" in the class "xAppRegistrationConfig" is related to the attribute "xAppEIJobID" and the class operations "eiTypeObject," "eiJobObject," and "eiJobStatusObject" in the class "xAppEI" via the class operation "xAppEIJobIDList:xAppEIJobID[]."

[0079] xAppRegistrationConfig:$xAppID:$xAppEIJobID:$eiTypeObject xAppRegistrationConfig:$xAppID:$xAppEIJobID:$eiJobObject xAppRegistrationConfig:$xAppID:$xAppEIJobID:$eiJobStatusObject

[0080] The following description relates an xApp configured by the class "xAppRegistrationConfig" in the xApp Deployment Data (Figure 8) to the classes "xAppRANFunction", "xAppRANSubFunction", and "xAppRANParameter" in the xApp RAN Function / xApp RAN Parameter (Figure 7). As shown in Figure 12, the class "xAppRegistrationConfig" and / or xApp is related to the class "xAppRANFunction", the class "xAppRANFunction" is related to the class "xAppRANSubFunction", and the class "xAppRANSubFunction" is related to the class "xAppRANParameter".

[0081] The following description relates the attribute "xAppID" in the class "xAppRegistrationConfig" and / or xApp to the attribute "xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "xAppRANFunction" and the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" "version" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]".

[0082] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID[] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$version

[0083] The following description relates the attribute "xAppID" in the class "xAppRegistrationConfig" and / or xApp to the attribute "xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "xAppRANFunction" and the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]".Furthermore, the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" is associated with the attribute "xAppSubFunctionTypeID" in the class "xAppRANSubFunction" and the class operations "RICEventTriggerStyleList:[ricStyleType,ricStyleName,ricFormatType]", "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType]", "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType]", "RICControlStyleList:[ricControlStyleType,ricControlStyleName,ricControlFormatType,ricControlHeaderFormatType,ricControlMessageFormatType,ricCallProcessIDFormatType,ricControlOutcomeFormatType,RANparameterIDList:xAppRANparameterID[],]", "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:xAppRANparameterID[],]".

[0084] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICEventTriggerStyleList:[$ricStyleType,$ricStyleName, ricFormatType] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICReportStyleList :[$ricReportStyleType,$ricReportStyleName, $ricReportActionFormatType,$RANparameterIDList :$xAppRANparameterID[], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICInsertStyleList : [$ricInsertStyleType, $ricInsertStyleName, $ricInsertActionFormatType,$RANparameterIDList : $xAppRANparameterID []], $ricIndicationHeaderFormatType, $ricIndicationMessageFormatType, $ricCallProcessIDFormatType] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICControlStyleList : [$ricControlStyleType,$ricControlStyleName,$ricControlFormatType, $ricControlHeaderFormatType, $ricControlMessageFormatType,$ricCallProcessIDFormatType, $ricControlOutcomeFormatType,$RANparameterIDList : $xAppRANparameterID [], ] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICPolicyStyleList : [$ricPolicyStyleType, $ricPolicyStyleName, $ricPolicyActionFormatType, $RANparameterIDList : $xAppRANparameterID [],]

[0085] The following description relates the attribute "xAppID" in the class "xAppRegistrationConfig" and / or xApp to the attribute "xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "xAppRANFunction" and the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]". Furthermore, the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" is related to the attribute "xAppSubFunctionTypeID" in the class "xAppRANSubFunction" and the class operation "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType]". Furthermore, the class operation "RICReportStyleList:[ricReportStyleType,ricReportStyleName,ricReportActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType]" is related to the attribute "xAppRANparameterID" in the class "xAppRANParameter" and the class operations "xAppRANParameterName" and "xAppRANParameterType".

[0086] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICReportStyleList:$RANparameterIDList :$xAppRANparameterID:$xAppRANParameterName xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICReportStyleList:$RANparameterIDList :$xAppRANparameterID:$xAppRANParameterType

[0087] The following description relates the attribute "xAppID" in the class "xAppRegistrationConfig" and / or xApp to the attribute "xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "xAppRANFunction" and the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]". Furthermore, the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" is related to the attribute "xAppSubFunctionTypeID" in the class "xAppRANSubFunction" and the class operation "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType]". Furthermore, the class operation "RICInsertStyleList:[ricInsertStyleType,ricInsertStyleName,ricInsertActionFormatType,RANparameterIDList:xAppRANparameterID[],ricIndicationHeaderFormatType,ricIndicationMessageFormatType,ricCallProcessIDFormatType]" is related to the attribute "xAppRANparameterID" in the class "xAppRANParameter" and the class operations "xAppRANParameterName" and "xAppRANParameterType".

[0088] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICInsertStyleList:$RANparameterIDList :$xAppRANparameterID:$xAppRANParameterName xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICInsertStyleList:$RANparameterIDList :$xAppRANparameterID:$xAppRANParameterType

[0089] The following description relates the attribute "xAppID" in the class "xAppRegistrationConfig" and / or xApp to the attribute "xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "xAppRANFunction" and the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]". Furthermore, the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" is related to the attribute "xAppSubFunctionTypeID" in the class "xAppRANSubFunction" and the class operation "RICControlStyleList:[ricControlStyleType,ricControlStyleName,ricControlFormatType,ricControlHeaderFormatType,ricControlMessageFormatType,ricCallProcessIDFormatType,ricControlOutcomeFormatType,RANparameterIDList:xAppRANparameterID[],]".Furthermore, the class operation "RICControlStyleList: [ricControlStyleType, ricControlStyleName, ricControlFormatType, ricControlHeaderFormatType, ricControlMessageFormatType, ricCallProcessIDFormatType, ricControlOutcomeFormatType, RANparameterIDList: xAppRANparameterID[],]" is associated with the attribute "xAppRANparameterID" in the class "xAppRANParameter" and the class operations "xAppRANParameterName" and "xAppRANParameterType".

[0090] xApp: $xAppID: $xAppRANFunctionList: $xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance : $xAppSubFunctionTypeList: $xAppSubFunctionTypeID: $RICControlStyleList: $RANparameterIDList : $xAppRANparameterID: $xAppRANParameterName xApp: $xAppID: $xAppRANFunctionList: $xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID,<0**********0526>$ranFunctionDescription, $ranFunctionInstance : $xAppSubFunctionTypeList: $xAppSubFunctionTypeID: $RICControlStyleList: $RANparameterIDList :$xAppRANparameterID:$xAppRANParameterType

[0091] As shown below, the attribute "xAppID" in the class "xAppRegistrationConfig" and / or xApp is related to the attribute "xAppRANFunctionName:[ranFunctionShortName,ranFunctionE2SMOID,ranFunctionDescription,ranFunctionInstance]" in the class "xAppRANFunction" and the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]". Furthermore, the class operation "xAppSubFunctionTypeList:xAppSubFunctionTypeID[]" is related to the attribute "xAppSubFunctionTypeID" in the class "xAppRANSubFunction" and the class operation "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:xAppRANparameterID[],]". Furthermore, the class operation "RICPolicyStyleList:[ricPolicyStyleType,ricPolicyStyleName,ricPolicyActionFormatType,RANparameterIDList:xAppRANparameterID[],]" is associated with the attribute "xAppRANparameterID" in the class "xAppRANParameter" and the class operations "xAppRANParameterName" and "xAppRANParameterType".

[0092] xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICPolicyStyleList:$RANparameterIDList :$xAppRANparameterID:$xAppRANParameterName xApp:$xAppID:$xAppRANFunctionList:$xAppRANFunctionName: [$ranFunctionShortName, $ranFunctionE2SMOID, $ranFunctionDescription, $ranFunctionInstance ]:$xAppSubFunctionTypeList:$xAppSubFunctionTypeID:$RICPolicyStyleList:$RANparameterIDList :$xAppRANparameterID:$xAppRANParameterType

[0093] FIG. 13 illustrates a schematic example of relationships between classes in the xApp deployment data and the xApp runtime data of the platform database.

[0094] The following description relates the class "xAppRegistrationConfig" in the xApp deployment data (Figure 8) to the classes "xAppA1EIMapping", "xAppA1PolicyMapping", and "xAppE2NodeRANFunctionMapping" in the xApp runtime data (Figure 4). Specifically, the attribute "xAppID" in the class "xAppRegistrationConfig" is related to the attribute "xAppA1EIMapping" and the class operation "eiJobID" in the class "xAppA1EIMapping" via the class operation "xAppEIJobIDList:xAppEIJobID[]", to the attribute "xAppA1PolicyMapping" and the class operation "policyID" in the class "xAppA1PolicyMapping" via the class operation "xAppPolicyIDList:xAppPolicyID", and to the attributes "xAppE2NodeRANFunctionMappingID" and "xAppRANFunctioninstanceID" and the class operations "xAppRANFunctionName" and "E2NodeRANFunctionName" in the class "xAppE2NodeRANFunctionMapping" via the class operation "xAppRANFunctionList:xAppRANFunctionName[]".

[0095] xAppRegistrationConfig:$xAppID:$xAppEIJobID::$xAppA1EIMappingID:eiJobID xAppRegistrationConfig:$xAppID:$xAppA1PolicyMappinID:$policyID xAppRegistrationConfig:$xAppID:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$xAppRANFunctionName xAppRegistrationConfig:$xAppID:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$E2NodeRANFunctionName

[0096] FIG. 14 illustrates a schematic example of relationships between classes in the subscription / routing data and xApp runtime data of the platform database.

[0097] The following description relates the class "Subscription" in the subscription / routing data (Figure 6) to the classes "Distribution" and "MessagingRoute" in the same figure and the class "xAppE2NodeRANFunctionMapping" in the xApp runtime data (Figure 4). Specifically, the attributes "requestID:[requestorID(xAppID),xAppInstanceID]" and "subscriptionManagerInstanceID" in the class "Subscription" are related to the attributes "xAppE2NodeRANFunctionMappingID" and "xAppRANFunctioninstanceID" in the class "xAppE2NodeRANFunctionMapping" and the class operations "xAppRANFunctionName", "E2NodeID", and "E2NodeRANFunctionName" in the class "xAppE2NodeRANFunctionMapping" via the class operation "xAppE2NodeRANFunctionMappingID". The attribute "distributionID" in the class "Distribution" and the class operations "E2TerminationInstanceID", "eventTrigger:(from RANSubFunction)", and "actionID:(from RANSubFunction), and via the class operation "distributionList:distributionID[]", it is related to the attributes "distributionID", "messagingRouteID", and "messageType" in the class "MessagingRoute", and the class operations "senderEndPoint(hostname / IP.port - InstanceID)" and "receiverEndPoint(hostname / IP.port - InstanceID=".

[0098] Subscription:$requestID:[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID::$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID: $xAppRANFunctionName Subscription:$requestID[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$xAppE2NodeRANFunctionMappingID:$xAppRANFunctionInstanceID:$ E2NodeID:$2NodeRANFunctionName Subscription:$requestID[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$E2TerminationInstanceID Subscription:$requestID[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$eventTrigger(from RANSubFunction) Subscription:$requestID[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$actionID(from RANSubFunction) Subscription:$requestID:[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$distributionID:$messagingRouteID:$messageType:$senderEndPoint(hostname / IP.port - InstanceID) Subscription:$requestID:[requestorID(xAppID), xAppInstanceID]:$subscriptionManagerInstanceID:$distributionID:$messagingRouteID:$messageType:$receiverEndPoint(hostname / IP.port - InstanceID)

[0099] In addition to or instead of the class relationships exemplified in Fig. 11 to Fig. 14, some or all of the class relationships exemplified in Fig. 15 may be adopted. In Fig. 15, the class "xAppContextData" and the class "xAppRegistrationConfig" are related to each other, the class "xAppA1EIMapping" and the classes "nonRTA1EI" and "xAppEI" are related to each other, the class "xAppA1PolicyMapping" and the classes "nonRTA1Policy" and "xAppPolicy" are related to each other, the class "SDLNotification" and the classes "xAppRegistrationConfig" and "E2Node" are related to each other, the class "xAppE2NodeRANFunctionMapping" and the classes "Subscription", "xAppRANFunction", and "E2NodeRANFunction" are related to each other, the class "MessagingRoute" and the classes "Distribution" and "xAppMessagingConfig" are related to each other, and the class "Distribution" and the class "Subscription" are related to each other. The classes "xAppRANParameter" and "xAppRANSubFunction" are related, the classes "xAppRANSubFunction" and "xAppRANFunction" are related, the classes "xAppRANFunction" and "xAppRegistrationConfig" and "xAppPolicy" are related, the classes "E2NodeRANParameter" and "E2NodeRANSubFunction" are related, the classes "E2NodeRANSubFunction" and "E2NodeRANFunction" are related, the classes "E2NodeRANFunction" and "E2Node" are related, the classes "xAppMessagingConfig" and "xAppRegistrationConfig" are related, the classes "xAppEI" and "xAppRegistrationConfig" are related,The class "xAppAPIEnablementConfig" and the class "xAppRegistrationConfig" are related to each other, the class "xAppPolicy" and the class "xAppRegistrationConfig" are related to each other, and the class "E2NodeComponentConfig" and the class "E2Node" are related to each other. Note that the UML representing these relationships can be written in the same way as in Figures 11 to 14, so it will be omitted here.

[0100] The present disclosure has been described above based on the embodiments. Various modifications are possible to the combinations of the components and processes in the exemplary embodiments, and it will be obvious to those skilled in the art that such modifications are included within the scope of the present disclosure.

[0101] In the embodiments of Figure 3 and the like, the system and / or data structure of the Near-RT RIC has been described, focusing on data that can be communicated via the E2 interface and / or the A1 interface, but the system and / or data structure of the Near-RT RIC may also be defined in the same manner as in the embodiments, taking into account data that can be communicated via the O1 interface.

[0102] The configuration, operation, and function of each device and method described in the embodiments can be realized by hardware resources, software resources, or a combination of hardware and software resources. Examples of hardware resources include processors, ROMs, RAMs, and various integrated circuits. Examples of software resources include operating systems, applications, and other programs.

[0103] This disclosure may be expressed in the following terms:

[0104] Item 1: In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), Classes related to E2 nodes are related to classes related to E2 node component configurations. Radio Access Network Controller. Item 2: In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), A class relating to an E2 node is related to a class relating to an E2 node RAN function; Radio Access Network Controller. Item 3: In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), The class relating to the registration configuration of the xApp is related to at least one of the class relating to the policy of the xApp, the class relating to the messaging configuration of the xApp, the class relating to the enrichment information of the xApp, and the class relating to the API enablement configuration of the xApp; Radio Access Network Controller. Item 4: In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), xApp registration configuration classes are related to xApp RAN function classes; Radio Access Network Controller. Item 5: In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), A class relating to the registration configuration of an xApp is related to at least one of a class relating to mapping of A1 enrichment information when the xApp is executed, a class relating to mapping of A1 policies when the xApp is executed, and a class relating to mapping of E2 node RAN functions when the xApp is executed; Radio Access Network Controller. Item 6: In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), The subscription class is related to the E2 node RAN function mapping class when xApp is executed. Radio Access Network Controller.

[0105] This application claims priority based on Japanese Patent Application No. 2022-005950, filed on January 18, 2022, the entire contents of which are incorporated by reference.

Claims

[Claim 1] In O-RAN's Near-RT RIC (Near-Real Time RAN Intelligent Controller), The class related to the E2 node is associated with the class related to the E2 node component configuration. The attribute relating to the ID of the class for the E2 node is associated with the class operation relating to the E2 node component configuration of the class relating to the E2 node component configuration. Wireless access network control device.

Images