hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.2.2 Test entrance criteria | 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI job identifiers procedure. 2) The DUTs supports a known set of EI types (two or more) used for this test. 3) The agreed eiTypeIds are known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.2.3 Test methodology | 7.3.3.2.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 2) The Non-RTR-DUT supports the two different test configurations listed below to test complete functionality: a) Non-RTR-DUT has no EI job available for any of the EI types s... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.3 Query EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.3.1 Test description and applicability | The purpose of this test case is to test query EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.5. The expected outcome is successful retrieval of EI job for the given eiJobId. This test case is conditionally mandatory if the DUTs claim to support A1-EI service and the Que... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.3.2 Test entrance criteria | 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI job procedure. 2) An EI job exists in the Non-RTR-DUT and the eiJobId is known to the Near-RTR-DUT. 3) The eiJobId is known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.3.3.3 Test methodology | 7.3.3.3.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 84 7.3.3.3.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface.... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.4.1 Update EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.4.1.1 Test description and applicability | The purpose of this test case is to test update EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.4. The expected outcome is successful update of the EI job. This test case is conditionally mandatory if the DUTs claim to support A1-EI service and Update EI job procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.4.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-EI Update EI job procedure. 2) An EI job exists in the Non-RTR-DUT and the eiTypeID and eiJobID are known to the Near-RTR-DUT. 3) The eiTypeID and the JSON schemas of the EI type used for this test are available and used in Near-RTR-DUT to formulate the Update EI job ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.4.1.3 Test methodology | 7.3.4.1.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 7.3.4.1.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.5.1 Delete EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.5.1.1 Test description and applicability | The purpose of this test case is to test the delete EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.6. The expected outcome is successful validation of the Delete EI job request This test case is conditionally mandatory if the DUTs claim to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.5.1.2 Test entrance criteria | 1) The Non-RTR-DUT has functionality to initiate A1-EI Delete EI job procedure. 2) An EI job exists in the Non-RTR-DUT and the eiJobId is known to the Near-RTR-DUT. 3) The eiJobId is known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.5.1.3 Test methodology | 7.3.5.1.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 7.3.5.1.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.1 Query EI job status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.1.1 Test description and applicability | The purpose of this test case is to test the query EI job status functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.7. The expected outcome is successful retrieval of EI job status object. This test case is conditionally mandatory if the DUTs claim to support A1-EI service and the ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.1.2 Test entrance criteria | 1) The Near-RTR-DUT has functionality to initiate Query EI job status procedure. 2) An EI job exists in the Non-RTR-DUT and the eiJobId is known to the Near-RTR-DUT. 3) The agreed eiTypeId is known to the protocol analyser. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.1.3 Test methodology | 7.3.6.1.3.1 Initial conditions 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. 7.3.6.1.3.2 Procedure Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. Step 1. Initiate appropriate action in t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.2 Notify EI job status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.2.1 Test description and applicability | This purpose of this test case is to test the notify EI job status functionality of A1-EI Producer and AI-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is successful request and delivery of EI job status notification. This test case is optional if the DUTs claim to support A1-EI service and ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.2.2 Test entrance criteria | The test entrance criteria for Create EI job specified in clause 7.3.2.1.2 applies. And in addition: 1) Near-RTR-DUT has the functionality to request and receive EI job status notification. 2) Non-RTR-DUT has the functionality to provide EI job status notification. 3) Non-RTR-DUT and Near-RTR-DUT have agreed on a how t... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.6.2.3 Test methodology | 7.3.6.2.3.1 Initial conditions The initial conditions for Create EI job specified in clause 7.3.2.1.3.1 applies. And in addition: 1) The Near-RTR-DUT supports generation of an EiJobStatusObject based on the EI job status schema of the agreed EI type used for this test. 2) The Near-RTR-DUT has HTTP server ready and avai... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.7.1 Deliver EI job result (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.7.1.1 Test description and applicability | This purpose of this test case is to test the deliver EI job result functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is successful EI job result request and delivery of EI job results. This test case is optional if the DUTs claim to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.7.1.2 Test entrance criteria | The test entrance criteria for Create EI job specified in clause 7.3.2.1.2 applies. And in addition: 1) Non-RTR-DUT and Near-RTR-DUT have agreed on a how to trigger the EI job results delivery based on supported EI types and functionality in the Non-RTR-DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 7.3.7.1.3 Test methodology | 7.3.7.1.3.1 Initial conditions The initial conditions for Create EI job specified in clause 7.3.2.1.3.1 applies. And in addition: 1) The Near-RTR-DUT has HTTP server ready and available to receive HTTP requests from the Non-RTR-DUT for EI job result delivery. NOTE: The Near-RTR-DUT is expected to provide callback URI (... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 1 Scope | The present document specifies the data model and the data types that are used in the body of the procedures in the A1 interface. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 2 References | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 3 Definition of terms, symbols and abbreviations | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 3.1 Terms | For the purposes of the present document, the terms given in A1GAP [2], A1AP [3] and the following apply: ScopeIdentifier: structured data type representing the scope identifier NOTE: See A1AP [3]. Statement: structured data type representing a policy statement that is policy type specific NOTE: See A1AP [3]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 3.2 Symbols | Void. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in A1GAP [2], A1AP [3] and the following apply: AMF Access and Mobility Management Function E1AP E1 Application Protocol ETSI ETSI TS 103 988 V9.0.0 (2025-05) 11 F1AP F1 Application Protocol gNB-CU-CP gNB Central Unit Control Plane GUAMI Globally Unique ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 4 A1 Application data model | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 4.1 Introduction | The present document together with A1AP [3] contains a REST method realization of the A1 interface architecture and the A1 procedures identified in A1GAP [2]. A1AP [3] contains the service description, service operations, resource indicators and the API definition (including the OpenAPI document) for the A1 services. T... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 4.2 Compatibility of A1 type definitions | The version number of the present document indicates that there may be implications for the compatibility between implementations of policy types and/or EI types defined in different versions of the present document. The first two-digit value of the present document is incremented when: • at least one policy type and/o... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 5 Generic aspects and common data types | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 5.1 Encoding of attributes in A1 data types | The encoding of 3GPP attributes into JSON is based on their original definitions, and their value ranges, rather than on encodings used in other protocols or solutions sets. The definitions are referred to in the data type definitions (see clauses 6.2 and 6.3) and the corresponding encodings are seen in the type defini... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 5.2 Current type definitions | The present document defines the policy types, EI types and common data types listed in table 5.2-1. Table 5.2-1: Type definitions in the present document Type Type name Type version Definition Common data types common 1.0.0 See clause 7.1.2.1 Policy types QoS target QoSTarget 4.0.1 See clause 7.2.1 QoE target QoETarge... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6 A1-P data model | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.1 Introduction | This clause specifies the application data model and data types supported by the A1-P API specified in A1AP [3]). The data model is based on policy statements that include attributes and are combined with a scope identifier into policy objects. Simple data types and enumerations can be referenced from structured data t... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2 Simple data types and enumerations | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2.1 Simple data types | The simple data types are defined in table 6.2.1-1. Table 6.2.1-1: Definition of simple data types for scope and statements Type Name Type Definition Description Applicability RanUeId string UE identifier, based on RAN UE Id (see ETSI TS 138 463 [8] and ETSI TS 138 473 [9]). Encoded as 16 hexadecimal characters. 5G RAN... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2.2 Enumerations | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2.2.1 PreferenceType | The enumeration PreferenceType represents the preference of a specific network resource (e.g. cell usage). It shall comply with the provisions defined in table 6.2.2.1-1. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 14 Table 6.2.2.1-1: Definition of PreferenceType Enumeration value Description Applicability SHALL equals to se... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2.2.2 EnforcementStatusType | The enumeration EnforcementStatusType represents if a policy is enforced or not. It shall comply with the provisions defined in table 6.2.2.2-1. Table 6.2.2.2-1: Definition of EnforcementStatusType Enumeration value Description Applicability ENFORCED equals that the policy is enforced NOT_ENFORCED equals that the polic... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2.2.3 EnforcementReasonType | The enumeration EnforcementReasonType represents the reason why notification is sent (e.g. why enforcement status has changed). It also represents the latest reason for change of enforcement status to NON_ENFORCED in case policy status is queried. It shall comply with the provisions defined in table 6.2.2.3-1. Table 6.... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.2.2.4 AvoidanceType | The enumeration AvoidanceType represents the avoidance of a specific network resource (e.g. cell usage). It shall comply with the provisions defined in table 6.2.2.4-1. Table 6.2.2.4-1: Definition of AvoidanceType Enumeration value Description Applicability AVOID equals to avoid selecting the network resource avoid sel... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3 Structured data types | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1 ScopeIdentifier | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.1 Introduction | A1 policies are defined in A1GAP [2] as containing a scope identifier and one or more policy statements where policy statements contain policy objectives and/or policy resources. This clause defines the structured data type ScopeIdentifier. The ScopeIdentifier contains the attributes defined in table 6.3.1.1-1: Table 6... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.2 GroupId | GroupId is defined based on different RF selection priority parameters for 4G and 5G networks. GroupId does not explicitly define a UE group, and does not enable any group management operations, but is a property that several UE can share and thereby enables implicit identification of a dynamic set of UEs for which the... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.3 SliceId | SliceId is based on the definition of S-NSSAI (see ETSI TS 123 003 [10]) and includes a PLMN identifier. The SliceId contains the attributes defined in table 6.3.1.3-1: Table 6.3.1.3-1: Definition of type SliceId Attribute name Data type P Cardinality Description Applicability sst integer M 1 Slice/Service type part of... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.4 QosId | QosId is defined based on different QoS identifiers for 4G and 5G networks. The QosId contains the attributes defined in table 6.3.1.4-1: Table 6.3.1.4-1: Definition of type QosId Attribute name Data type P Cardinality Description Applicability qcI integer C 0..1 QoS Class Identifier (see ETSI TS 123 203 [16]). Value r... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.5 CellId | CellId is based on the definition of the global cell identifiers ECGI and NCGI (see ETSI TS 123 003 [10]) for 4G and 5G RANs. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 17 The CellId contains the attributes defined in tables 6.3.1.5-1 and 6.3.1.5-2: Table 6.3.1.5-1: Definition of type CId Attribute name Data type P Cardinal... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.6 PlmnId | This clause contains the definition of the structured data type PlmnId. PlmnId is based on the definition in ETSI TS 123 003 [10]. The PlmnId contains the attributes defined in table 6.3.1.6-1: Table 6.3.1.6-1: Definition of type PlmnId Attribute name Data type P Cardinality Description Applicability mcc string M 1 Mob... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.7 UeId | This clause contains the definition of the structured data type UeId. Table 6.3.1.7-1: Definition of type GuRanUeId Attribute name Data type P Cardinality Description Applicability globalGnbId GlobalGnbId M 1 Global GNB ID, see clause 6.3.1.8 5G RAN ranUeId RanUeId M 1 RAN UE ID, see clause 6.2.1 5G RAN Table 6.3.1.7-2... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.8 GlobalGnbId | This clause contains the definition of the structured data type GlobalGnbId. This is based on Global gNB ID defined in ETSI TS 138 413 [21], clause 9.3.1.6. The GlobalGnbId contains the attributes defined in tables 6.3.1.8-1 and 6.3.1.8-2: Table 6.3.1.8-1: Definition of type GnbId Attribute name Data type P Cardinality... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.9 GuAmI | This clause contains the definition of the structured data type GuAmI. This is based on GUAMI defined in ETSI TS 138 413 [21], clause 9.3.3.3. The GuAmI contains the attributes defined in table 6.3.1.9-1: Table 6.3.1.9-1: Definition of type GuAmI Attribute name Data type P Cardinality Description Applicability plmnId P... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.1.10 GuMmeI | This clause contains the definition of the structured data type GuMmeI. This is based on GUMMEI defined in ETSI TS 136 413 [22], clause 9.2.3.9. The GuMmeI contains the attributes defined in table 6.3.1.10-1: Table 6.3.1.10-1: Definition of type GuMmeI Attribute name Data type P Cardinality Description Applicability pl... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.2 Structured data types for statements | This clause contains definitions of structured data types that are used in statements for policy objectives and/or statements for policy resources. The CellIdList contains the attributes defined in table 6.3.2-1: Table 6.3.2-1: Definition of type CellIdList Attribute name Data type P Cardinality Description Applicabili... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3 Statements for policy objectives | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.1 Introduction | A1 policies are defined in A1GAP [2] as containing a scope identifier and one or more policy statements where policy statements contain policy objectives and/or policy resources. This clause defines the structured data types and attributes to be used for policy objectives. Table 6.3.3.1-1 specifies the data types defin... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.2 QoS target | The QosObjectives statement contains the attributes defined in table 6.3.3.2-1: Table 6.3.3.2-1: Definition of statement type QosObjectives Attribute name Data type P Cardinality Description Applicability gfbr number C 0..1 Guaranteed Flow Bit Rate, see ETSI TS 123 501 [11] 5G RAN mfbr number C 0..1 Maximum Flow Bit Ra... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.3 QoE target | The QoeObjectives statement contains the attributes defined in table 6.3.3.3-1: Table 6.3.3.3-1: Definition of statement type QoeObjectives Attribute name Data type P Cardinality Description Applicability qoeScore number C 0..1 mean opinion score (MOS) value between 1 and 5, it can be either e.g. video MOS as specified... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.4 UE level targets | The UeLevelObjectives statement contains the attributes defined in table 6.3.3.4-1: Table 6.3.3.4-1: Definition of statement type UeLevelObjectives Attribute name Data type P Cardinality Description Applicability ulThroughput number C 0..1 the average UL RAN UE throughput as the UE performance targets or RAN optimizati... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.5 Slice SLA target | The SliceSlaObjectives statement contains the attributes defined in table 6.3.3.5-1: Table 6.3.3.5-1: Definition of statement type SliceSlaObjectives Attribute name Data type P Cardinality Description Applicability maxNumberOfUes number C 0..1 This attribute describes the partial SLA target for providing maximum number... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.6 Load balancing targets | The LbObjectives statement contains the attributes defined in table 6.3.3.6-1: Table 6.3.3.6-1: Definition of statement type LbObjectives Attribute name Data type P Cardinality Description Applicability targetPrbUsg number M 1 The target PRB usage in percent. The denominator is the total number of PRBs in the cell, and... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.3.7 Energy saving targets | The EsObjectives statement contains the attributes defined in table 6.3.3.7-1: Table 6.3.3.7-1: Definition of statement type EsObjectives Attribute name Data type P Cardinality Description Applicability targetPeeEnergy number C 0..1 Target average value of energy consumption PEE.Energy of PNF such as O-RU in kWh over t... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.4 Statements for policy resources | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.4.1 Introduction | A1 policies are defined in A1GAP [2] as containing a scope identifier and one or more policy statements where policy statements contain policy objectives and/or policy resources. This clause defines the structured data types and attributes to be used for policy resources. Table 6.3.4.1-1 specifies the data types define... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.4.2 Traffic steering preference | The TspResources statement is defined in table 6.3.4.2-2 as an array of the type TspResource defined in table 6.3.4.2-1. Table 6.3.4.2-1: Definition of type TspResource Attribute name Data type P Cardinality Description Applicability cellIdList CellIdList M 1 list of CellIds, see clause 6.3.2 preference PreferenceType ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.4.3 Slice SLA Policy Resources | The SliceSlaResources statement is defined in table 6.3.4.3-1. Table 6.3.4.3-1: Definition of type SliceSlaResources Attribute name Data type P Cardinality Description Applicability cellIdList CellIdList C 0..1 list of CellIds, see clause 6.3.2 taIList TaIList C 0..1 list of TaIs, see clause 6.3.2 NOTE: Presence condit... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.4.4 Load Balancing Policy Resources | The LbResources statement is defined in table 6.3.4.4-1. Table 6.3.4.4-1: Definition of type LbResources Attribute name Data type P Cardinality Description Applicability cellIdList CellIdList M 1 list of CellIds used to designate candidate cells to which cell load is to be transferred |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.3.4.5 Energy Savings resources | The EsResources statement is defined in Table 6.3.4.5-2 as an array of the type EsResource defined in Table 6.3.4.5-1. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 30 Table 6.3.4.5-1: Definition of type EsResource Attribute name Data type P Cardinality Description Applicability operationalCells CellIdList C 0..1 list of Cells... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.4 Policy representations objects | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.4.1 Policy object | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.4.1.1 General | A PolicyObject is based on IETF RFC 8259 [6] and it always contains one set of: • one ScopeIdentifier; and • one or more Statements. The PolicyObject can contain objective and/or resource statements as defined in table 6.4.1.1-1. Table 6.4.1.1-1: General definition of PolicyObject Attribute name Data type P Cardinality... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.4.1.2 Allowed combinations | A Statement can be applied together with a ScopeIdentifier containing different combinations of identifiers attributes. Not all combinations are relevant and different combinations are relevant for different policy types (see clause 7). ETSI ETSI TS 103 988 V9.0.0 (2025-05) 32 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.4.2 Policy status object | A PolicyStatusObject is based on IETF RFC 8259 [6] and contains: • one enforceStatus attribute; and conditionally; • one enforceReason attribute. The PolicyStatusObject contains status related attributes as defined in table 6.4.2-1: Table 6.4.2-1: General definition of PolicyStatusObject Attribute name Data type P Card... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.4.3 Policy type object | A PolicyTypeObject is based on IETF RFC 8259 [6] and contains: • one JSON schema for PolicyObject; and optionally; • one JSON schema for PolicyStatusObject. The type PolicyTypeObject is defined in table 6.4.3-1. Table 6.4.3-1: General definition of PolicyTypeObject Attribute name Data type P Cardinality Description App... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 6.5 Binary data | Binary data is not applicable in the present document. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 33 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7 A1-P data types (A1 policy types) | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1 Introduction | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.1 Identification and compatibility of policy types | A policy type is identified by a PolicyTypeId as defined in A1AP [3]. The PolicyTypeId is a string that consists of two parts: a typename and a version. When updating a policy type, the version in the PolicyTypeId is updated according to SemVer [19] to reflect its compatibility with other policy types that has the same... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.2 Common definitions | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.2.1 Scope and resource identifiers | An A1 policy type always contains a ScopeIdentifier with data types defined in clause 6.3.1. It may also contain attributes for a resource statement that includes identifiers defined in clauses 6.3.2 and 6.3.4. To enable multiple policy types to be created based on the same identifiers, the policy schemas can link to t... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.2.2 Policy status | This is a generic policy status schema, it may be adjusted and used together with a policy schema in a PolicyTypeObject and will then be identified by the same policy type identifier as the policy schema. { "$schema": "https://json-schema.org/draft/2020-12/schema", "description": "O-RAN standard policy status", "type":... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.3 Schema identification | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.3.1 General | The policy schemas defined in clause 7.2 (e.g. policy schema for QoS target in clause 7.2.1.3.1) are base schemas that embed a subschema with common data types definitions. The base schemas can be used for creating or validating A1 policies after embedding the content of the linked common data types schema. A schema re... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.1.3.2 Schema URI structure | The base URI for A1 policy types and embedded schemas is: {uriRoot}/a1td where uriRoot follows an absolute URI syntax, but excludes the "query" component. The URI root contains the "scheme" component and may contain an "authority" component and may also contain a prefix subcomponent. ETSI ETSI TS 103 988 V9.0.0 (2025-0... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2 Policy type definitions | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1 QoS target | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.1 Policy type identifier | PolicyTypeId: ORAN_QoSTarget_4.0.1 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.2.1 Use case | See "Use case 3: QoS based resource optimization" in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.2.2 Statements, restrictions and extensions | A QoS statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.1.2.2-1 indicates the combinations that are allowed. Table 7.2.1.2.2-1: Allowed combinations of qosObjectives statement with ScopeIdentifier ScopeIdentifier Policy ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_qostarget_4.0.1", "description": "O-RAN standard QoS Target policy", "type": "object", "properties": { "scope": { "anyOf": [ { ETSI ETSI TS 103 988 V9.0.0 (2025-05) 40 "type": "object", "properties": { "... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.