hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 1.2 Abbreviations | Abbreviations used in the present document are given clause 6 (Glossary) and in GSM 01.04 [1]. |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 2 Traffic distributions | |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 2.1 Uniform | A uniform traffic distribution can be considered to start with in large cells as an average over the cell area, especially in the country side. ETSI ETSI TR 101 362 V7.1.0 (2000-04) 7 (GSM 03.30 version 7.1.0 Release 1998) |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 2.2 Non-uniform | A non-uniform traffic distribution is the usual case, especially for urban areas. The traffic peak is usually in the city centre with local peaks in the suburban centres and motorway junctions. A bell-shaped area traffic distribution is a good traffic density macro model for cities like London and Stockholm. The expone... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3 Cell coverage | |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.1 Location probability | Location probability is a quality criterion for cell coverage. Due to shadowing and fading a cell edge is defined by adding margins so that the minimum service quality is fulfilled with a certain probability. For car mobile traffic a usual measure is 90 % area coverage per cell, taking into account the minimum signal-t... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.2 Ec/No threshold | The mobile radio channel is characterized by wideband multipath propagation effects such as delay spread and Doppler shift as defined in GSM 05.05 annex C. The reference signal-to-noise ratio in the modulating bit rate bandwidth (271 kHz) is Ec/No = 8 dB including 2 dB implementation margin for the GSM system at the mi... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.3 RF-budgets | The RF-link between a Base Transceiver Station (BTS) and a Mobile Station (MS) including handheld is best described by an RF-budget as in annex A which consists of 4 such budgets; A.1 for GSM 900 MS class 4; A.2 for GSM 900 MS class 2, A.3 for DCS 1800 MS classes 1 and 2, and A.4 for GSM 900 class 4 in small cells. The... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.4 Cell ranges | |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.4.1 Large cells | In large cells the base station antenna is installed above the maximum height of the surrounding roof tops; the path loss is determined mainly by diffraction and scattering at roof tops in the vicinity of the mobile i.e. the main rays propagate above the roof tops; the cell radius is minimally 1 km and normally exceeds... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.4.2 Small cells | For small cell coverage the antenna is sited above the median but below the maximum height of the surrounding roof tops and so therefore the path loss is determined by the same mechanisms as stated in section 3.4.1. However large and small cells differ in terms of maximum range and for small cells the maximum range is ... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 3.4.3 Microcells | COST 231 defines a microcell as being a cell in which the base station antenna is mounted generally below roof top level. Wave propagation is determined by diffraction and scattering around buildings i.e. the main rays propagate in street canyons. COST 231 proposes the following experimental model for microcell propaga... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4 Channel re-use | |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.1 C/Ic threshold | The C/Ic threshold is the minimum co-channel carrier-to-interference ratio in the active part of the timeslot at the minimum service quality when interference limited. The reference threshold C/Ic = 9 dB includes 2 dB implementation margin on the simulated residual BER threshold The threshold quality varies with logica... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.2 Trade-off between Ec/No and C/Ic | For planning large cells the service range can be noise limited as defined by Ec/No plus a degradation margin of 3 dB protected by 3 dB increase of C/Ic, see annex A. ETSI ETSI TR 101 362 V7.1.0 (2000-04) 11 (GSM 03.30 version 7.1.0 Release 1998) For planning small cells it can be more feasible to increase Ec/No by 6 d... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.3 Adjacent channel suppressions | Adjacent channel suppression (ACS) is the gain (Ia/Ic) in C/I when wanted and unwanted GSM RF-signals co-exist on adjacent RF channels whilst maintaining the same quality as in the co-channel case, i.e. ACS = C/Ic - C/Ia. Taking into account frequency errors and fading conditions in the product of spectrum and filter o... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.4 Antenna patterns | Antenna patterns including surrounding masts, buildings, and terrain measured on ca 1 km distance will always look directional, even if the original antenna was non-directional. In order to achieve a front-to-back ratio F/B of greater than 20 dB from an antenna with an ideal F/B > 25 dB, backscattering from the main lo... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.5 Antenna heights | The height gain under Rayleigh fading conditions is approximately 6 dB by doubling the BTS antenna height. The same height gain for MS and handheld from reference height 1.5 m to 10 m is about 9 dB, which is the correction needed for using CCIR Recommendation 370. |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.6 Path loss balance | Path loss balance on uplink and downlink is important for two-way communication near the cell edge. Speech as well as data transmission is dimensioned for equal quality in both directions. Balance is only achieved for a certain power class (section 3.4). Path loss imbalance is taken care of in cell selection in idle mo... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.7 Cell dimensioning | Cell dimensioning for uniform traffic distribution is optimized by at any time using the same number of channels and the same coverage area per cell. ETSI ETSI TR 101 362 V7.1.0 (2000-04) 12 (GSM 03.30 version 7.1.0 Release 1998) Cell dimensioning for non-uniform traffic distribution is optimized by at any time using t... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.8 Channel allocation | Channel allocation is normally made on an FDMA basis. However, in synchronized networks channel allocation can be made on a TDMA basis. Note that a BCCH RF channel must always be fully allocated to one cell. Channel allocation for uniform traffic distribution preferably follows one of the well known re-use clusters dep... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.9 Frequency hopping | Frequency hopping (FH) can easily be implemented if the re-use is based on RF channel groups (CAs). It is also possible to change allocation by demand as described in GSM 05.02. In synchronized networks the synchronization bursts (SB) on the BCCH will occur at the same time on different BTS. This will increase the time... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 4.10 Cells with extra long propagation delay | Cells with anticipated traffic with ranges more than 35 km corresponding to maximum MS timing advance can work properly if the timeslot after the CCCH and the timeslot after the allocated timeslot are not used by the BTS corresponding to a maximum total range of 120 km. |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 5 Propagation models | |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 5.1 Terrain obstacles | Terrain obstacles introduce diffraction loss, which can be estimated from the path profile between transmitter and receiver antennas. The profile can preferably be derived from a digital topographic data bank delivered from the national map survey or from a land resource satellite system, e.g. Spot. The resolution is u... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 5.2 Environment factors | Environment factors for the nearest 200 m radius from the mobile play an important role in both the 900 MHz and 1800 MHz bands. For the Nordic cellular planning for NMT there is taken into account 10 categories for land, urban and wood. Further studies are done within COST 231. Coarse estimations of cell coverage can b... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 5.3 Field strength measurements | Field strength measurements of the local mean of the lognormal distribution are preferably done by digital averaging over the typical Rayleigh fading. It can be shown that the local average power can be estimated over 20 to 40 wavelengths with at least 36 uncorrelated samples within 1 dB error for 90 % confidence (Lee,... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 5.4 Cell adjustments | Cell adjustments from field strength measurements of coverage and re-use are recommended after coarse predictions have been done. Field strength measurements of rms values can be performed with an uncertainty of 3.5 dB due to sampling and different propagation between Rayleigh fading and line-of-sight. Predictions can ... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 6 Glossary | ACS Adjacent Channel Suppression (section 4.3) BCCH Broadcast Control Channel (section 4.8) BTS Base Transceiver Station (section 3.3) BSIC Base Transceiver Station Identity Code (section 4.8) CA Cell Allocation of radio frequency channels (section 4.8) CCCH Common Control Channel (section 4.10) COST European Co-operat... |
f48e0f9fa2d7ccfd80e612b2641fd571 | 101 362 | 7 Bibliography | CEPT Recommendation T/R 20-08 Frequency planning and frequency co-ordination for the GSM service; CEPT Recommendation T/R 25-03 Co-ordination of frequencies for the land mobile service in the 80, 160 and 460 MHz bands and the methods to be used for assessing interference; CEPT Recommendation T/R 25-04 Co-ordination in ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 1 Scope | The present document specifies the RAN optimization and control related use cases that have been approved within O-RAN WG2. The purpose of the use cases is to help identify requirements for O-RAN defined interfaces and functions, specifically Non-RT RIC function and A1 and R1 interfaces, eventually leading to formal dr... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 2 References | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 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... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 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... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 3 Definition of terms, symbols and abbreviations | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [i.1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [i.1]. A1: interface between orchestration/NMS layer containing Non-RT RIC and eNB/gNB contai... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 3.2 Symbols | Void. |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [i.1]. 5QI 5G Quality of Service Identifier ASM Advanced Sleep Mode ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4 Use cases | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1 Use case 1: Traffic steering use case | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.0 Introduction | This use case provides the motivation, description, and requirements for traffic steering use case, allowing operators to specify different objectives for traffic management such as optimizing the network/UE performance, or achieving balanced cell load. ETSI ETSI TS 104 226 V10.1.0 (2025-08) 11 |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.1 Background and goal of the use case | 5G systems will support many different combinations of access technologies namely; LTE (licensed band), NR (licensed band), NR-U (unlicensed band), Wi-Fi® (unlicensed band). Several different multi-access deployment scenarios are possible with 5GC to support wide variety of applications and satisfy the spectrum require... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.2 Entities/resources involved in the use case | 1) SMO (including Non-RT RIC): a) Retrieve necessary performance, configuration, and other data for defining and updating policies to guide the behaviour of traffic management function in Near-RT RIC. For example, the policy could relate to specifying different optimization objectives to guide the carrier/band preferen... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.3 Solutions | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.3.1 Traffic steering - policy part | The context of traffic steering - policy part is captured in table 4.1.3.1-1. ETSI ETSI TS 104 226 V10.1.0 (2025-08) 13 Table 4.1.3.1-1: Traffic steering - policy part Use Case Stage Evolution / Specification <<Uses>> Related use Goal Drive traffic management in RAN in accordance with defined intents, policies, and con... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.3.2 Traffic steering - EI part | The context of traffic steering - EI part is captured in table 4.1.3.2-1. ETSI ETSI TS 104 226 V10.1.0 (2025-08) 15 Table 4.1.3.2-1: Traffic steering - EI part Use Case Stage Evolution / Specification <<Uses>> Related use Goal Assist in traffic optimization in RAN in accordance with produced enrichment information. Act... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.4 Required data | The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) should be appropriately aggregated by cell, QoS type, slice, etc.: 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighbouring cells. In multi-access scenarios this will also include intra-RAT and inte... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.5 A1 usage example | An example scenario is here used to describe the use of A1 for traffic management, implying the Non-RT RIC sending policies for allocation of the control plane (RRC) and the user plane for different services, identified by their 5QI. ETSI ETSI TS 104 226 V10.1.0 (2025-08) 17 In the scenario a UE with UEid=1, belonging ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.6 Enrichment information example | Radio fingerprint is composed of multiple virtual grids. The virtual grids are constructed based on the historical report of intra-frequency and inter-frequency measurement results of UEs from both the serving cell and the neighbour cell. The serving cell is divided into multiple grids according to the signalling measu... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.1.7 A1 usage example in multi-access environment | The Non-RT RIC can send policies for traffic distribution in a multi-access environment based on UE characteristics and traffic patterns for different services that can be identified by their 5QI. The following example scenario illustrates this, in which there are three UEs with the following characteristics. UE Identi... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2 Use case 2: QoE use case | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support real-time QoE optimization. Moreover, some high-level description and requirements over Non-RT RIC, A1 and E2 interfaces are introduced. |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.1 Background and goal of the use case | The highly demanding 5G native applications such as cloud VR are both bandwidth consuming and latency sensitive. However, for such traffic-intensive and highly interactive applications, current semi-static QoS framework cannot efficiently satisfy diversified QoE requirements especially taking into account potentially s... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary QoE related measurement metrics from network level measurement report and SMO (can acquire data from application) for constructing/training relevant AI/ML model that will be deployed in Near-RT RIC to assist in the QoE optimization function. For example, this could be application cl... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.3 Solutions | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.3.1 Model training and distribution | The context of model training and distribution is captured in table 4.2.3.1-1. Table 4.2.3.1-1: Model training and distribution Use Case Stage Evolution / Specification <<Uses>> Related use Goal Model training and distribution. Actors and Roles Non-RT RIC, Near-RT RIC, SMO, application server Assumptions • All relevant... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.3.2 Policy generation and performance evaluation | The context of policy generation and performance evaluation is captured in table 4.2.3.2-1. ETSI ETSI TS 104 226 V10.1.0 (2025-08) 26 Table 4.2.3.2-1: Policy generation and performance evaluation Use Case Stage Evolution / Specification <<Uses>> Related use Goal Policy generation and performance evaluation. Actors and ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.4 Required data | Multi-dimensional data are expected to be retrieved by Non-RT RIC for AI/ML model training and policies/intents generation: 1) Network level measurement report, including: - UE level radio channel information, mobility related metrics - L2 measurement report related to traffic pattern, e.g. throughput, latency, packets... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.2.5 A1 usage example | There are 3 examples to explain how A1 policy woks for QoE optimization. One is for ue_id (100), slice_id (1) and qos_id (5QI =50), the target QoE score (for example video MOS 80) should be satisfied. { ETSI ETSI TS 104 226 V10.1.0 (2025-08) 28 "policy_id": "1", "scope": { "ue_id": "100", "slice_id": "1", "qos_id": "50... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3 Use case 3: QoS based resource optimization | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.0 Introduction | This use case provides the background and motivation for the O-RAN architecture to support RAN QoS based resource optimization. Moreover, some high-level description and requirements over Non-RT RIC and A1 interfaces are introduced. |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.1 Background and goal of the use case | QoS based resource optimization can be used when the network has been configured to provide some kind of preferential QoS for certain users. One such scenario can be related to when the network has been configured to support e2e slices. In this case, the network has functionality that ensures resource isolation between... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Monitor necessary QoS related metrics from network function and other SMO functions. b) Send policies to Near-RT RIC to drive QoS based resource optimization at RAN level in terms of expected behaviour. 2) Near-RT RIC: a) Support interpretation and execution of A1 policies for QoS based resource optim... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.3 Solutions | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.3.1 QoS based resource optimization | The context of QoS based resource optimization is captured in table 4.3.3.1-1. Table 4.3.3.1-1: QoS based resource optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal Drive QoS based resource optimization in RAN in accordance with defined policies and configuration. Actors and Roles Non-RT R... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.4 Required data | For this use case, different kind of observability need to be reported to Non-RT RIC. First Non-RT RIC shall monitor resource consumption in the area. As long as resource consumption is low, the RAN scheduler will be able to give all users in an area the needed resources. When resource consumption in an area increases ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.3.5 A1 usage example | Example scenario • One emergency RAN sub-slice defined (S-NSSAI=1) with a ratio of 50 % configured. 5QI=74 configured for a minimum bitrate of 500 kbps. • 4 UEs (UeId=10, 11, 12, 13) in the area which belongs to S-NSSAI = 1 and with active flows of 5QI = 74. • Resource shortage means that minimum bitrate 500 kbps canno... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.0 Introduction | This use case provides the background, motivation, and requirements for the context-based dynamic HO management for V2X use case, allowing operators to adjust radio resource allocation policies through the O-RAN architecture, reducing latency and improving radio resource utilization. ETSI ETSI TS 104 226 V10.1.0 (2025-... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.1 Background and goal of the use case | V2X communication allows for numerous potential benefits such as increasing the overall road safety, reducing emissions, and saving time. Part of the V2X architecture is the V2X UE (SIM + device attached to vehicle) which communicates with the V2X Application Server (V2X AS). The exchanged information comprises Coopera... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve necessary performance, configuration, and other data for constructing/training relevant AI/ML models that will be deployed in Near-RT RIC to assist in the V2X HO management function. For example, this could be a clustering algorithm that classifies traffic situations and radio conditions that... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.3 Solutions | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.3.1 Context-based dynamic handover management for V2X | The context of the context-based dynamic handover management for V2X is captured in table 4.4.3.1-1. Table 4.4.3.1-1: Context-based dynamic handover management for V2X Use Case Stage Evolution / Specification <<Uses>> Related use Goal Drive V2X UE HOs in RAN according to defined intents, policies, and configuration whi... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.4 Required data | The measurement counters and KPIs (as defined by 3GPP) should be appropriately aggregated by cell, QoS type, slice, etc.: 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighbouring cells. 2) UE connection and mobility/handover statistics with indication of successful and failed handovers and err... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.5 Proposed solution(s) | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.5.1 Workflow overview | The use case workflow consists of these main components: 1) Data collection & maintenance: This is required at Non-RT RIC (over O1 and Enrichment Interface (EI)). Required radio measurements and V2X related metrics are collected over a longer period of time (sufficient to facilitate model training). The O1/EI data coll... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.5.2 Overview of ML models | While many combinations and deployments are possible, this proposal outlines one specific set of models and analytics that can be useful to drive such a use case. NonRT_Model1: The Non-RT RIC ML-assisted solution uses the O1-based and EI-based data collection to monitor the V2X UE HO performance metrics and the navigat... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.6 A1 enrichment interface aspects | 1) As per ETSI EN 302 637-2 [i.2], V2X UE provides CAMs (which include its GPS coordinates) on a 0.1-1s temporal granularity to the V2X application server. The inference part of this use case depends on accurate navigation data from V2X UEs, thus O-RAN expects this data to be provided through the A1-EI without substant... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.4.7 A1 usage example | As of now the A1 aspect of the use case is confined to whether the HO optimization is, within a certain scope, activated or not. Thus, some of the attributes can overlap with the policy scope, but they are proposed in order to allow for more fine-grained control (e.g. optimize for only vehicles that are faster than 100... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5 Use case 5: RAN slice SLA assurance | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.0 Introduction | The 3GPP standards architected a sliceable 5G infrastructure which allows creation and management of customized networks to meet specific service requirements that can be demanded by future applications, services and business verticals. Such a flexible architecture needs different requirements to be specified in terms ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.1 Background and goal of the use case | In the 5G era, network slicing is a prominent feature which provides end-to-end connectivity and data processing tailored to specific business requirements. These requirements include customizable network capabilities such as the support of very high data rates, traffic densities, service availability and very low late... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Retrieve RAN slice SLA target from respective entities such as SMO, NSSMF. b) Long term monitoring of RAN slice performance measurements. c) Training of potential ML models that will be deployed in Non-RT RIC for slow loop optimization and/or Near-RT RIC for fast loop optimization. d) Support deployme... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.3 Solutions | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.3.1 Creation and deployment of RAN slice SLA assurance applications | The context of the creation and deployment of RAN slice SLA assurance applications is captured in table 4.5.3.1-1. Table 4.5.3.1-1: Creation and deployment of RAN slice SLA assurance applications Use Case Stage Evolution / Specification <<Uses>> Related use Goal Training and distribution of the RAN slice SLA assurance ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.3.2 RAN slice SLA assurance | The context of RAN slice SLA assurance is captured in table 4.5.3.2-1. Table 4.5.3.2-1: RAN slice SLA assurance Use Case Stage Evolution / Specification <<Uses>> Related use Goal RAN slice SLA assurance Actors and Roles SMO functions, Non-RT RIC framework, RAN slice SLA assurance rApp, Near-RT RIC, E2 nodes Assumptions... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.4 Required data | The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) should be appropriately aggregated by cell, QoS type, slice, etc. Examples for required data for RAN slice SLA assurance use case are as follows: 1) Per UE and/or per slice performance statistics as specified in 3GPP TS 28.5... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.5 A1 usage example | Example scenario 1 • One mobile leased line network slice for live broadcasting is defined (S-NSSAI=1). • The SLA for the slice is defined with the total UL/DL throughput of 30 Mbps of the users in the slice provided in the coverage area (cellId=1, 2, 3). • Non-RT RIC generates A1 policy for Near-RT RIC slice SLA assur... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.5.6 O1 usage example | Example scenario • One mobile leased line network slice for live broadcasting is defined (S-NSSAI=1). • The SLA for the slice is defined with the average total UL/DL throughput of 30 Mbps of the users in the slice provided in the coverage area (cellId=1, 2, 3). • Note that O1 configuration is used to assure SLAs define... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6 Use case 6: NSSI resource optimization | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.0 Introduction | This use case provides the background, objectives, solution, and requirements for the NSSI resource optimization, an rApp implemented in Non-RT RIC, which leverages AI/ML inference on slice performance measurement data to determine the actions to automatically optimize the resource allocation for network slice instance... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.1 Background and goal of the use case | Network slicing is essential to 5G, as it enables many new services across manufacturing, autonomous driving, gaming, and many more via the provision of ultra-low latency in URLLC and huge data volume in eMBB features that require different or contrasting QoS requirements exploiting a shared RAN node. The goal of this ... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.2 Entities/resources involved in the use case | 1) Non-RT RIC: a) Receive measurements to monitor the usage of RRM resources (e.g. PRB, RRC, DRB) identified by S-NSSAI from E2 nodes via the O1 interface. b) Perform the model training with input measurements data received from E2 nodes to create the model. c) Perform the inference function on the model with the input... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.3 Solutions | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.3.1 NSSI resource optimization | The context of the NSSI resource optimization is captured in table 4.6.3.1-1. Table 4.6.3.1-1: NSSI resource optimization Use Case Stage Evolution / Specification <<Uses>> Related use Goal The goal is to ensure the resources (e.g. PRB, RRC, DRB) are allocated dynamically and efficiently among multiple network slices sh... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.4 Required data | |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.4.0 Introduction | This clause contains the input and output data of model training and inference. |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.4.1 Input data | The measurement input data are used in model training and inference. They include the following measurements to monitor the resource usage for network slices in E2 nodes: 1) Measurements used to monitor the usage of RRC related resources in O-CU-CP include: - Mean number of RRC connections - provides the mean number of... |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.4.2 Output data | The output data, including NRCellCU IOC, NRCellDU IOC, GNBDUFunction IOC, GNBCUCPFunction IOC, GNBCUUPFunction IOC and RRMPolicyRatio IOC with RRMPolicy abstract class (as specified in 3GPP TS 28.541 [4]), are needed to enable NSSI resource optimization rApp to re-configure the resources via O1 and O2 interfaces. |
7e4409c8abd9ce1b6236b46207489f8c | 104 226 | 4.6.5 O1 usage example | An example of two NSSIs, where NSSI#1 groups E2 nodes (i.e. O-DU, O-CU-CP, and O-CU-UP), and NSSI#2 groups 5GC NFs is shown in figure 4.6.5-1. It also shows that two network slices, identified by S-NSSAI#1 supporting URLLC, and S-NSSAI#2 supporting eMBB. The goal of this use case is to optimize the resources associated... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.