hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.1.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2 QoE target | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.1 Policy type identifier | PolicyTypeId: ORAN_QoETarget_4.0.1 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.2.1 Use case | See "Use case 2: QoE use case" in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.2.2 Statements, restrictions and extensions | A QoE statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.2.2.2-1 indicates the combinations that are allowed. Table 7.2.2.2.2-1: Allowed combinations of qoeObjectives statement with ScopeIdentifier ScopeIdentifier Policy ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_qoetarget_4.0.1", "description": "O-RAN standard QoE Target policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "ueId": {"$ref": "/a1td/common_1.0.0#/$def... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.2.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3 Traffic steering preferences | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.1 Policy type identifier | PolicyTypeId: ORAN_TrafficSteeringPreference_4.0.1 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.2.1 Use case | See "Use case 1: Traffic Steering use case" in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.2.2 Statements, restrictions and extensions | A TSP statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.3.2.2-1 indicates combinations that are allowed. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 43 Table 7.2.3.2.2-1: Allowed combinations of tspResources statement with Sco... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_ trafficsteeringpreference_4.0.1", "description": "O-RAN standard Traffic Steering Preference policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "ueId": ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.3.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4 QoS optimization with resource directive | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.1 Policy type identifier | PolicyTypeId: ORAN_QoSandTSP_4.0.1 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.2.1 Use case | Addresses both the QoS based resource optimization and Traffic steering preferences use cases. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.2.2 Statements, restrictions and extensions | The allowed combinations of ScopeIdentifier and statements is the common subset of those defined for the policy type QoS Target and the policy type Traffic Steering Preferences. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_qosandtsp_4.0.1", "description": "O-RAN standard QoS Target and Traffic Steering Preference policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "ueId": {"... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.4.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5 QoE optimization with resource directive | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.1 Policy type identifier | PolicyTypeId: ORAN_QoEandTSP_4.0.1 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.2.1 Use case | Addresses both the QoE and Traffic steering preferences use cases. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 46 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.2.2 Statements, restrictions and extensions | The allowed combinations of ScopeIdentifier and statements is the common subset of those defined for the policy type QoE Target and the policy type Traffic Steering Preferences. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_qoeandtsp_4.0.1", "description": "O-RAN standard QoE Target and Traffic Steering Preference policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "ueId": {"... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.5.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6 UE level target | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.1 Policy type identifier | PolicyTypeId: ORAN_UELevelTarget_3.0.1 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.2.1 Use case | Addresses the QoS based resource optimization use case. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.2.2 Statements, restrictions and extensions | A UE level statement can be applied together with scope identifiers containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.6.2.2-1 indicates the combinations that are allowed. Table 7.2.6.2.2-1: Allowed combinations of ueLevelObjectives statement with ScopeIdentifier Scope identi... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_ueleveltarget_3.0.1", "description": "O-RAN standard UE Level Target policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "ueId": {"$ref": "/a1td/common_1.... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.6.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7 Slice SLA target | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.1 Policy type identifier | PolicyTypeId: ORAN_SliceSLATarget_3.0.0 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.2.1 Use case | See "Use case 5: RAN Slice SLA Assurance" defined in Non-RT RIC and A1/R1 interface: Use Cases and Requirements [1]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.2.2 Statements, restrictions and extensions | The sliceSlaObjectives statement can be applied together with ScopeIdentifier containing sliceId identifier. Table 7.2.7.2.2-1 indicates the combination that is allowed. Table 7.2.7.2.2-1: Allowed combinations of sliceSlaObjectives statement with ScopeIdentifier ScopeIdentifier Policy statement ueId groupId sliceId qos... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_sliceslatarget_3.0.0", "description": "O-RAN standard slice SLA policy", "type": "object", "properties": { "scope": { "type": "object", "properties": { "sliceId": {"$ref": "/a1td/common_1.0.0#/$defs/Slic... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.7.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8 Load balancing | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8.1 Policy type identifier | PolicyTypeId: ORAN_LoadBalancing_1.0.2 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8.2.1 Use case | See "Use case 5: RAN Slice SLA Assurance use case" in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8.2.2 Statements, restrictions and extensions | A lbObjectives statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.8.2.2-1 indicates the combinations that are allowed. ScopeIdentifier is used to designate a cell from which load needs to be transferred to other cells. If... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.8.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_loadbalancing_1.0.2", "description": "O-RAN standard Load Balancing policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "sliceId": {"$ref": "/a1td/common_... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9 Energy Savings | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.1 Policy type identifier | PolicyTypeId: ORAN_EnergySaving_2.0.0 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.2 Rationale | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.2.1 Use case | See "Use case 8: Network Energy saving Use Cases " in Non-RT RIC & A1 interface: Use Cases and Requirements [1]. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.2.2 Statements, restrictions and extensions | An energy saving statement (i.e. esObjectives and/or esResources) can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. The following table indicates combinations that are allowed. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 53 Table 7.2.9.2.2-1: All... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.3 JSON schemas | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.3.1 Policy schema | { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_energysaving_2.0.0", "description": "O-RAN standard Energy saving policy", "type": "object", "properties": { "scope": { "anyOf": [ { "type": "object", "properties": { "cellId": {"$ref": "/a1td/common_1.0... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 7.2.9.3.2 Policy status schema | The generic policy status schema in clause 7.1.2.2 is used. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8 A1-EI data model | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.1 Introduction | This clause specifies the application data model supported by the A1-EI API specified in A1AP [3]. The purpose of the data model is to be the basis for: • definition of EI types; and • the EI representation objects that are transported in the body of the A1-EI procedures. There are two kinds of EI types: those defined ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.2 Simple data types and enumerations | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.2.1 Simple data types | The EI job contains URIs for EI job status notifications and EI job results. The simple data types for callback URIs are defined in table 8.2.1-1. Table 8.2.1-1: General definition of simple data types for callback URIs Type Name Type Definition Description Applicability JobStatusNotificationUri string target URI for E... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.2.2 Enumerations | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.2.2.1 JobStatusType | The enumeration JobStatusType represents if an EI job is confirmed to deliver EI results. It shall comply with the provisions defined in table 8.2.2.1-1. Table 8.2.2.1-1: Enumeration JobStatusType Enumeration value Description Applicability ENABLED the EI Job is enabled the A1-EI producer is able to deliver EI result f... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.2.2.2 GadShapeType | The enumeration GadShapeType represents the different types or shapes of geographic areas. It shall comply with the provisions defined in table 8.2.2.2-1. Table 8.2.2.2-1: Enumeration GadShapeType Enumeration value Description Applicability POINT Ellipsoid point POINT_UNCERTAINTY_CIRCLE Ellipsoid point with uncertainty... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.2.2.3 VelocityDescType | The enumeration VelocityDescType represents the different types of UE velocity descriptions. It shall comply with the provisions defined in table 8.2.2.3-1. Table 8.2.2.3-1: Enumeration VelocityDescType Enumeration value Description Applicability H_VELOCITY Horizontal velocity HV_VELOCITY Horizontal and vertical veloci... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3 Structured data types | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.1 ScopeIdentifier | The ScopeIdentifier is EI type specific. If the ScopeIdentifier contains attributes corresponding to the A1 policy ScopeIdentifier, they are the same as defined for A1-P, see clause 6.3.1. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 57 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.2 Statements for EI job definition | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.2.1 Introduction | This clause defines the structured data type and attributes to be used for EI job definition, which are summarized in table 8.3.2.1-1. Table 8.3.2.1-1: Statements for EI job definition Data type Clause defined Description Applicability UeGeoandVelEIDescription 8.3.2.2 EI job definition for UE geo-location and velocity ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.2.2 UE geo-location and velocity information | The UEGeoandVelEIDescription statement contains the attributes defined in table 8.3.2.2-1: Table 8.3.2.2-1: Definition of UEGeoandVelEIDescription Attribute name Data type P Cardinality Description Applicability gadShape GadShapeType M 1 GAD shapes used for UE geo- location information, see clause 8.2.2.2 velocityDesc ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.3 Statements for EI job result | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.3.1 Introduction | This clause defines the structured data type and attributes to be used for EI job result definition, which are summarized in table 8.3.3.1-1. Table 8.3.3.1-1: Statements for EI job result definition Data type Clause defined Description Applicability UeGeoandVelEIResult 8.3.3.2 EI job result definition for UE geo-locati... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.3.2 UE geo-location and velocity EI | The UEGeoandVelEIResult statement contains the attributes defined in table 8.3.3.2-1: ETSI ETSI TS 103 988 V9.0.0 (2025-05) 58 Table 8.3.3.2-1: Definition of UEGeoandVelEIResult Attribute name Data type P Cardinality Description Applicability timeStamp DateTime M 1 Indicates the UTC time corresponds to the UE geo- loca... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.4 Statements for EI job constraints | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.4.1 Introduction | This clause defines the structured data type and attributes to be used for EI job constraints. Table 8.3.4.1-1 specifies the statements that can be used for EI job constraints. Table 8.3.4.1-1: Statements for EI job constraints Data type Clause defined Description Applicability UEGeoandVelEIConstraints 8.3.4.2 EI job c... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.3.4.2 UE geo-location and velocity information | The UEGeoandVelEIConstraints contains the attributes defined in table 8.3.4.2-1: Table 8.3.4.2-1: Definition of UEGeoandVelEIConstraints Attribute name Data type P Cardinality Description Applicability supportedGadShapes array(GadShapeType) M 1..N Indicates supported GAD shapes to describe UE geo- location, see clause ... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4 EI representations objects | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.1 EI type object | The EI type object can be empty or contain EI type specific information. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 60 An EiTypeObject is based on IETF RFC 8259 [6] and can contain: • one JSON schema for EiJobDefinition; • one JSON schema for EiJobStatusObject; • one JSON schema for EiJobResultObject; or • one JSON schema f... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.2 EI job object | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.2.1 General | An EiJobObject is based on IETF RFC 8259 [6] and contains: • one EI type identifier; • one target URI for EI Job results; and • one EI type specific job definition containing one or more EI job definition statements. and optionally: • one target URI for EI Job status notifications. The type EiJobObject is defined in ta... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.2.2 Allowed combinations | A job definition 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 EI types (see clause 9). |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.3 EI job status object | An EiJobStatus object is based on IETF RFC 8259 [6] and always contains: • one EI job status attribute. Table 8.4.3-1: General definition of EIJobStatusObject Attribute name Data type P Cardinality Description Applicability jobStatus JobStatusType M 1 See clause 8.2.2 statement indicating status of an EI job NOTE: Pres... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.4 EI job result object | An EiJobResult object is based on IETF RFC 8259 [6] and it contains: • one or more EI job result statements. |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.4.5 EI job constraints object | An EiJobConstraintsObject is based on IETF RFC 8259 [6] and it contains: • one or more EI job constraints statements. The content is related to the EI job definition, i.e. it can express capabilities and limitations related to supported attributes and value ranges for EI job result attributes, and EI job production and... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 8.5 Binary data | Binary data is not applicable in this version of the present document. ETSI ETSI TS 103 988 V9.0.0 (2025-05) 62 |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9 A1-EI data types (EI types) | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.1 Introduction | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.1.1 Identification and compatibility of EI types | An EI type is identified by a EiTypeId as defined in A1AP [3]. The EiTypeId is a string that consists of two parts: a typename and a version. When updating an EI type, the version in the EiTypeId is updated according to SemVer [19] to reflect its compatibility with other EI types that has the same typename. Two EI type... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.1.2 Common definitions | |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.1.2.1 EI job status | This is a generic EI job status schema, it may be adjusted and used together with an EI job schema in an EiTypeObject and will then be identified by the same EI type identifier as the EI job schema. { "$schema": "https://json-schema.org/draft/2020-12/schema", "description": "O-RAN standard EI status", "type": "object",... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.1.2.2 Scope identifiers and common data types | The EI job definition schemas defined in clause 9.2 can be base schemas that embed a subschema with common data types definitions in same way as described for policy types in clause 7.1. An EI type definition can link to the common data types schema defined in clause 7.1.2.1 and the compatibility relations are the same... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.1.2.3 Schema identification | The EI type identifier is part of the $id keyword included in the EI job definition schema. The $id keyword for the EI job definition schemas are constructed from the URI base and the EI type identifier in the same was as for policy types as described in clause 7.1.3.2. The base URI for EI types is the same as for poli... |
dd2f747decb51cf171473fa3c4dbb901 | 103 988 | 9.2 EI type definitions |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.