The A1 Consumer / Producer tabs are available when the A1 Interface is enabled on the RIC Node Emulator Configuration test case. The A1 interface is an open logical interface within O-RAN architecture between the Non-RT RIC functionality in the SMO and the Near-RT RIC functionality in the RAN.
About the 5G Application , About O-RAN O-DU Testing
Per 3GPP TS 23.501, 23.502, O-RAN.WG2.A1AP-v03.02 , O-RAN.WG2.A1GAP-v03.00, O-RAN.WG2.A1TD-v04.00, O-RAN.WG2.A1TP_v02.00, O-RAN.WG2.A1TS-v02.00, O-RAN.WG2.A1UCR-v01.00, O-RAN.WG2.Non-RT-RIC-ARCH-TS-v02.01
Non-RT A1 Consumer |
Non-RT A1 Consumer
|
Non-RT A1 Consumer |
Non-RT A1 Consumer |
Non-RT A1 Consumer |
|
Non-RT A1 Producer
|
Near-RT A1 Producer |
Near-RT A1 Consumer |
|
Select the Number of Policy Objects. The Policy Object is the JSON representation of an A1 policy. A Policy Object contains a scope identifier and at least one policy statement (i.e one or more policy objective statements and/or one or more policy resource statements) Range : 1 to 8 Default : 1 Tcl Parameter: NonRtRicA1CsmrPolObjNum
Select to enter the Policy Type ID. Policy Type Identifier. Options : ORAN_QoSTarget_2.0.0 (QoS Target), ORAN_QoETarget_2.0.0 (QoE Target), For same Policy Type ID, multiple Policy Objects can be configured, but must not be duplicated with same Scope setting. Tcl Parameter: NonRtRicA1CsmrPolTypeId_1
Scope - The policy scope in a Policy Object contains a scope identifier that can be e.g. a ueId, a groupId or a cellId. The A1 -P Consumer maps the policyIds to scope identifiers in order to manage e.g. all policies applicable to a specific individual ueId. If there are several policies related to the same scope identifier, then several policy operations are made to manage that specific scope. At least one ID (UE, Group ID, etc) listed should be checked.The valid combination of IDs for a specific Policy Type ID is specified in spec O-RAN.WG2.A1TD-v04.00. Refer to 5.2.1.2.2 for allowed combinations of scope id for policy type ORAN_QoSTarget_2.0.0.
Original Policy / Updated Policy Per spec O-RAN.WG2.A1TD-v04.00.
Scope Per spec O-RAN.WG2.A1TD-v04.00.
QoS (Quality of Service) Objectives At least one option must be selected. Available when Policy Type ID is ORAN_QoSTarget_2.0.0 and ORAN_QoSandTSP_2.0.0
QoE (Quality of Experience) Objectives At least one option must be selected. Available when Policy Type ID is ORAN_QoETarget_2.0.0 and ORAN_QoEandTSP_2.0.0
TSP (Traffic Steering Preference) Resources At least one option must be selected. Available when Policy Type ID is ORAN_TrafficSteeringPreference_2.0.0, ORAN_QoSandTSP_2.0.0 and ORAN_QoEandTSP_2.0.0
At least one option must be selected. Available when Policy Type ID is ORAN_UELevelTarget_1.0.0
At least one option must be selected. Available when Policy Type ID is ORAN_SliceSLATarget_2.0.0
At least one option must be selected. Available when Policy Type ID is ORAN_LoadBalancing_1.0.0
|
Non-RT / A1 Consumer
Apply Test Data File to UE Policy Parameters
|
Select to enter A Test Data File for the UE Policy Parameters. The TDF is editable only when "UE ID" in "Original Policy" is checked. The parameters that are availbale in the TDF are based on the Policy Type ID selection. See also, Applying Test Data FileApplying Test Data File. See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter: Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.
The Test Data File parameters when Policy Type ID = "ORAN_QoSTarget_2.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,GFBR,MFBR,Priority Level,Packet Delay Budget
The Test Data File parameters when Policy Type ID = "ORAN_QoETarget_2.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,QoE Score,Rebuffering Frequency,Initial Buffering,Stall Ratio
The Test Data File parameters when Policy Type ID = "ORAN_TrafficSteeringPreference_2.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,TSP Preference,TSP Primary,TSP Number of Cell IDs,TSP Cell ID MCC_0,TSP Cell ID MNC_0,TSP Cell ID NCI_0,TSP Cell ID ECI_0,TSP Cell ID MCC_1,TSP Cell ID MNC_1,TSP Cell ID NCI_1,TSP Cell ID ECI_1,TSP Cell ID MCC_2,TSP Cell ID MNC_2,TSP Cell ID NCI_2,TSP Cell ID ECI_2,TSP Cell ID MCC_3,TSP Cell ID MNC_3,TSP Cell ID NCI_3,TSP Cell ID ECI_3,TSP Cell ID MCC_4,TSP Cell ID MNC_4,TSP Cell ID NCI_4,TSP Cell ID ECI_4
The Test Data File parameters when Policy Type ID = "ORAN_QoSandTSP_2.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,GFBR,MFBR,Priority Level,Packet Delay Budget,TSP Preference,TSP Primary,TSP Number of Cell IDs,TSP Cell ID MCC_0,TSP Cell ID MNC_0,TSP Cell ID NCI_0,TSP Cell ID ECI_0,TSP Cell ID MCC_1,TSP Cell ID MNC_1,TSP Cell ID NCI_1,TSP Cell ID ECI_1,TSP Cell ID MCC_2,TSP Cell ID MNC_2,TSP Cell ID NCI_2,TSP Cell ID ECI_2,TSP Cell ID MCC_3,TSP Cell ID MNC_3,TSP Cell ID NCI_3,TSP Cell ID ECI_3,TSP Cell ID MCC_4,TSP Cell ID MNC_4,TSP Cell ID NCI_4,TSP Cell ID ECI_4
The Test Data File parameters when Policy Type ID = "ORAN_QoEandTSP_2.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,QoE Score,Rebuffering Frequency,Initial Buffering,Stall Ratio,TSP Preference,TSP Primary,TSP Number of Cell IDs,TSP Cell ID MCC_0,TSP Cell ID MNC_0,TSP Cell ID NCI_0,TSP Cell ID ECI_0,TSP Cell ID MCC_1,TSP Cell ID MNC_1,TSP Cell ID NCI_1,TSP Cell ID ECI_1,TSP Cell ID MCC_2,TSP Cell ID MNC_2,TSP Cell ID NCI_2,TSP Cell ID ECI_2,TSP Cell ID MCC_3,TSP Cell ID MNC_3,TSP Cell ID NCI_3,TSP Cell ID ECI_3,TSP Cell ID MCC_4,TSP Cell ID MNC_4,TSP Cell ID NCI_4,TSP Cell ID ECI_4 The Test Data File parameters when Policy Type ID = "ORAN_UELevelTarget_1.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,DL Packet Delay(ms),DL Reliability User Plane Latency(ms),DL Reliability Packet Size(bytes),DL Reliability Success Probability(%),DL RLC SDU Packet Loss Rate,DL Throughput(kbps),UL PDCP SDU Packet Loss Rate,UL Packet Delay(ms),UL Throughput(kbps),UL Reliability User Plane Latency(ms),UL Reliability Packet Size(bytes),UL Reliability Success Probability(%)
The Test Data File parameters when Policy Type ID = "ORAN_SliceSLATarget_2.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,DL Slice Priority,Guaranteed DL Throughput Per Slice(kbps),Guaranteed UL Throughput Per Slice(kbps),Maximum UL Throughput Per Slice(kbps),Maximum UL Throughput Per UE(kbps),Maximum DL Packet Delay Per UE(kbps),Maximum UL Packet Delay Per UE(kbps),Maximum DL Jitter Per UE(ms),Maximum DL PDCP SDU Packet Loss Rate Per UE,Maximum DL Throughput Per UE(kbps),Maximum DL Throughput Per Slice(kbps),Maximum Number of PDU Sessions,Maximum Number of UEs,Maximum UL Jitter Per UE(ms),Maximum UL RLC SDU Packet Loss Rate Per UE,Minimum DL Reliability User Plane Latency(ms),Minimum DL Reliability Packet Size(bytes),Minimum DL Reliability Success Probability(%),Minimum UL Reliability User Plane Latency(ms),Minimum UL Reliability Packet Size(bytes),Minimum UL Reliability Success Probability(%),SLA Resource Resource Type,UL Slice Priority,SLA Resource Number of TAIs,SLA Resource TAI MCC[0],SLA Resource TAI MNC_0,SLA Resource TAI TAC_0,SLA Resource TAI MCC_1,SLA Resource TAI MNC_1,SLA Resource TAI TAC_1,SLA Resource TAI MCC_2,SLA Resource TAI MNC_2,SLA Resource TAI TAC_2,SLA Resource TAI MCC_3,SLA Resource TAI MNC_3,SLA Resource TAI TAC_3,SLA Resource TAI MCC_4,SLA Resource TAI MNC_4,SLA Resource TAI TAC_4,SLA Resource Number of Cell IDs,SLA Resource Cell ID MCC_0,SLA Resource Cell ID MNC_0,SLA Resource Cell ID NCI_0,SLA Resource Cell ID ECI_0,SLA Resource Cell ID MCC_1,SLA Resource Cell ID MNC_1,SLA Resource Cell ID NCI_1,SLA Resource Cell ID ECI_1,SLA Resource Cell ID MCC_2,SLA Resource Cell ID MNC_2,SLA Resource Cell ID NCI_2,SLA Resource Cell ID ECI_2,SLA Resource Cell ID MCC_3,SLA Resource Cell ID MNC_3,SLA Resource Cell ID NCI_3,SLA Resource Cell ID ECI_3,SLA Resource Cell ID MCC_4,SLA Resource Cell ID MNC_4,SLA Resource Cell ID NCI_4,SLA Resource Cell ID ECI_4
The Test Data File parameters when Policy Type ID = "ORAN_LoadBalancing_1.0.0" for both Original and Updated Policy : RFSP Index,SP ID,Cell ID NCI,Cell ID ECI,Cell ID MCC,Cell ID MNC,Slice ID SST,Slice ID SD,Slice ID MCC, Slice ID MNC,QoS ID 5QI,QoS ID QCI,Load Balancing Target PRB Usage(%),Load Balancing Type,Load Balancing Number of Cell IDs,Load Balancing Cell ID MCC_0,Load Balancing Cell ID MNC_0,Load Balancing Cell ID NCI_0,Load Balancing Cell ID ECI_0,Load Balancing Cell ID MCC_1,Load Balancing Cell ID MNC_1,Load Balancing Cell ID NCI_1,Load Balancing Cell ID ECI_1,Load Balancing Cell ID MCC_2,Load Balancing Cell ID MNC_2,Load Balancing Cell ID NCI_2,Load Balancing Cell ID ECI_2,Load Balancing Cell ID MCC_3,Load Balancing Cell ID MNC_3,Load Balancing Cell ID NCI_3,Load Balancing Cell ID ECI_3,Load Balancing Cell ID MCC_4,Load Balancing Cell ID MNC_4,Load Balancing Cell ID NCI_4,Load Balancing Cell ID ECI_4
Tcl Parameter: NonRtRicA1CsmrCfgFileEn_1 Tcl Parameter: NonRtRicA1CsmrCfgFile_1 Tcl Parameter: NonRtRicA1CsmrUpdCfgFileEn_1 Tcl Parameter: NonRtRicA1CsmrUpdCfgFile_1 |
Non-RT / Near RT A1 Producer
|
Select to enter the API Prefix for Non-RT RIC A1 / Near-RT RIC A1. Default : spirent-NearRtRicA1Pdcr#(N1), spirent-NonRtRicA1Pdcr#(N1) Select the Auto-Increment Format Wizard to Auto increment the API Prefix.
Tcl Parameter: NearRtRicA1PdcrApiPrefixEn Tcl Parameter: NearRtRicA1PdcrApiPrefix Tcl Parameter: NonRtRicA1PdcrApiPrefixEn Tcl Parameter: NonRtRicA1PdcrApiPrefix |
Default Host Format in apiRoot |
Select which default host format to use in apiRoot, IP or FQDN (Fully Qualified Domain Name). Default : IP Spec reference : 3GPP 29.501, RFC #3986 Tcl Parameter: NearRtRicA1PdcrDefaultHostFormat Tcl Parameter: NonRtRicA1PdcrDefaultHostFormat |
Number of Policy Types |
Select the Number of Policy Types. The model on which a Policy Object and a PolicyStatusObject is based. Select the Policy Type ID. Currently the following types that are supported : ORAN_QoSTarget_2.0.0 (QoS Target), ORAN_QoETarget_2.0.0 (QoE Target), Select the Policy Schema - Select the TDF for Policy schema in Text format file with JSON (JavaScript Object Notation) schema. "Select a TDF on TAS" or "Upload a new TDF to TAS" are supported. The following Schema files will be provided in the Basic library on TAS. Select the corresponding schema type that matches the Policy Type : All Schema files start with "TC-RIC_Node-ORAN_"
It is up to the user to ensure the TDF file Policy Schema matches the appropriate Policy Type ID. i.e - Select LoadBalancing_1.0.0_Policy_Schema.json when Polict Type ID = ORAN_LoadBalancing 1.0.0 Attached is a text file of the ORAN_QoSTarget_2.0.0 Policy Schema TDF - ORAN_QoSTarget_2.0.0_Policy_Schema.txt The remaining schema text files can be found in the Basic Library starting with "TC-RIC_Node-ORAN_" Select the Status Schema. TDF for Status schema in Text format file with JSON (JavaScript Object Notation) schema. "Select a TDF on TAS" or "Upload a new TDF to TAS" are supported. The ""[Basic] TC-RIC_Node-Generic_Policy_Status_Schema.json" will be provided in the Basic library on TAS. Attached is a text file of the "[Basic] TC-RIC_Node-Generic_Policy_Status_Schema.json" TDF - Generic_Policy_Status_Schema.txt Tcl Parameter: NearRtRicA1PdcrPolTypesNum Tcl Parameter: NearRtRicA1PdcrPolTypeId_1 Tcl Parameter: NearRtRicA1PdcrPolSchema_1 Tcl Parameter: NearRtRicA1PdcrPolStatusSchema_1 |
Feedback Policy |
If Feedback Policy is enabled, then once the Near RT RIC receives a “create/update policy” request and creates/updates a policy successfully, it will send the feedback notification to Non RT RIC after the Feedback Delay timer. Enter the Feedback Delay in milliseconds. Range : 0 to 65535 Default : 0 Tcl Parameter: NearRtRicA1PdcrFeedbackPolicyEn Tcl Parameter: NearRtRicA1PdcrFeedbackPolicyDelay |
Non-RT A1 Producer
Available when Test A1EI is enabled on RIC Node Emulator Configuration
Number of EI Types |
Select the Number of EI (Enrichment Information Service) Types. Currently 1 is supported. Available when Test A1EI is enabled on RIC Node Emulator Configuration Select the EI Type ID. Currently the following type is supported : ORAN_UEGeoandVel_1.0.0 Enter the UE ID in the Scope Pane. Range : 0 to 18446744073709551615 Default: 0 Enter the Granularity Period (ms) in milliseconds. Range : 1 to 60000 Default : 500 Enter the Reporting Period (ms) in milliseconds. Range : 1 to 60000 Default : 500 Enter the Reporting Amount. Range : 1 to 3600000 Default : 1 Tcl Parameter: NonRtRicA1PdcrEiTypesNum Tcl Parameter: NonRtRicA1PdcrEiTypeId_1 Tcl Parameter: NonRtRicA1PdcrUeId_1
Tcl Parameter: NonRtRicA1PdcrGranPeriod_1 Tcl Parameter: NonRtRicA1PdcrEiRptPeriod_1 Tcl Parameter: NonRtRicA1PdcrEiRptAmount_1 |
||||||||||||||||||||||||||||||||||||||
Job Objectives |
Enter the Number of Geographic Areas for UE Location. Available when Test A1EI is enabled on RIC Node Emulator Configuration. Range : 1 to 7 Default : 1 Tcl Parameter: NearRtRicA1PdcrEiNumGeoAreas_1
Enter the Number of UE Velocity Types for UE Velocity. Range : 0 to 4 Default : 0 Tcl Parameter: NonRtRicA1PdcrEiNumUeVelocity_1
Select the EI Job Schemas from the Basic library. Available when Test A1EI is enabled on RIC Node Emulator Configuration.
|
Near-RT A1 Consumer
Number of EI Types |
Select the Number of EI (Enrichment Information Service) Types. Currently 1 is supported. Available when Test A1EI is enabled on RIC Node Emulator Configuration. Select the EI Type ID. Currently the following type is supported : ORAN_UEGeoandVel_1.0.0 Select Update EI Type to Copy Original to Updated. Two panes become available for input : Original EI Type / Updated EI Type. Enter the UE ID in the Scope Original EI type. UE ID is not available in the Updated EI Type Pane. Range : 0 to 18446744073709551615, Default: 0 Tcl Parameter: NearRtRicA1CsmrEiTypeNum Tcl Parameter: NearRtRicA1CsmrEiTypeId_1 Tcl Parameter: NearRtRicA1CsmrUpdateEiTypeEn_1 Tcl Parameter: NearRtRicA1CsmrUeId_1 |
Job Objectives |
Select Job Objectives - UE Geographic Location Type. Select Job Objectives - UE Velocity Type. Tcl Parameter: NearRtRicA1CsmrUeGeoLocType_1 Tcl Parameter: NearRtRicA1CsmrUeVelocityType_1 Tcl Parameter: NearRtRicA1CsmrUpdUeGeoLocType_1 Tcl Parameter: NearRtRicA1CsmrUpdUeVelocityType_1 |
Apply Test Data File to EI Type Parameters |
Select to enter Test Data File for the EI Type Parameters. See also, Applying Test Data FileApplying Test Data File. The Test Data File parameters when EI Type ID = "ORAN_UEGeoandVel_1.0.0" for both Original and Updated EI Types : UE Geographic Location Type,UE Velocity Type Tcl Parameter: NearRtRicA1CsmrCfgFileEn_1 Tcl Parameter: NearRtRicA1CsmrCfgFile_1 |