hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.1.1 Functionality | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.1.1.1 Data connection | Figure 3 shows the complete functional set for the sensor circuitry. It is recognized that not all lamp-posts will host the same (or any) sensors but the installation of a common circuit board capable of hosting all sensors offers advantages in terms of both cost and operational flexibility. The present document does n... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.1.1.2 Power supply | There are number options, depending on the energy consumption of the sensors and by the communication system, including: • an integrated battery - where sensors have particularly low energy consumption and communicate very limited amounts of data to the urban data platform; • a local energy harvesting solution (e.g. so... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.1.2 Availability | The first element of availability to be addressed is the physical capability of the population of lamp-posts in a given city to support the mass of the sensors and any local power supply solutions. It should be noted that additional mass can change the behaviour of the lamp-post, cause collapse and represent a safety r... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2 Stage 3 | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.1 Functionality | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.1.1 Data connection - front-haul and mid-haul networks | RRUs hosted on lamp-posts act as micro-cells which are suitable for a coverage area radius of 50 to 200 metres, while RRUs hosted on lamp-post acting as mini-macro cells could cover an average area radius of 100 to 500 metres. Data connection to an RRU on a lamp-post from a BBU is, as shown in Figure 4, via: • optical ... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.1.2 Power supply | Independent of the means of delivery of data to the RRU, each RRU requires a power supply. This has to be separate from the power supply to the lamp-post to support the lights and the sensor electronics of clause 5.1. This segregation is critical to ensure that any maintenance or breakdown of a lamp-post will not affec... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.2 Availability | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.2.1 General | The first element of availability to be addressed is the physical capability of the population of lamp-posts in a given city to support the mass of an RRU. It is recognized that not all light fittings are accommodated on street-mounted lamp- posts as shown in Figures 5 and 6 of the present document and some will be att... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.2.2 Data connection | Examples of redundant data pathways are shown in Figure 5 where adjacent RRUs being fed from different BBUs and Figure 6 where each RRU is fed by multiple mmWave antennae (also served by multiple BBUs). Both solutions are enhanced using the applicable ring structure of Figure 7. BBU BBU BBU UPS Existing lamp-post power... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 5.2.2.3 Power supply | The provision of a power supply to the many RRUs in a reliable and cost-effective way is a major challenge. Figure 5 and Figure 6 show the RRUs on each side of the road being fed by separate power supplies from the two BBU networks. It should be noted that centralized power supplies could also be accommodated in other ... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 6 RRU infrastructure | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 6.1 General | As shown schematically in Figure 8, the principal components of the RRU are the power supply converter, the Power Amplifier (PA), Radio Frequency (RF) transceiver and the antenna. Figure 8 shows the implementation for cabled front-haul technology (as discussed in this clause) and includes the opto- electronic convertor... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 6.2 Power supply converter | The power supply converter adapts the input power provision to the needs of its electronic circuitry. It includes any needed AC-DC and DC-DC electronics and incorporate overvoltage protection against induction from lightning strikes in the vicinity. |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 6.3 Power amplifier | The PA amplifies the electrical signals received to/from the opto-electronic converter before passing them from/to the RF transceiver. It also amplifies the signals coming from the RF transceiver before transmitting them to the air interface by the antenna. |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 6.4 RF transceiver | RF transceiver consists of an intermediate frequency and baseband interface and the following functions: • modulation/demodulation of the signals; • Voltage Controlled Oscillators (VCO) and mixers; • digital to analog conversion; • analog to digital signal conversion; • low noise amplifier (gain, clock, etc.). RRU BBU ... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 7 RRU Installation | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 7.1 General | This clause describes an RRU installation mode and lamp-post design requirement, for mounting an RRU. It also defines the mechanical interface and adequate load abilities on the lamp-post migration project. When planning to mount an RRU, the lamp-post should be evaluated on a series of indicators, for example wind load... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 7.2 RRU top-mounted installation | The RRU top-mounted installation can have a mechanical flange interface reserved for connection to the 5G RRUs along with the lamp-post migration project (as in clause C.1). It should guarantee adequate wind load resistance ability, together with other indicators, to ensure the safety of lamp-post when there is extreme... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 7.3 RRU side-mounted installation | The RRU side-mounted installation can directly fit on existing lamp-post(as in clause C.2). It requires evaluating the feasibility of drilling holes (typically the diameter is 20 mm) for power cables and optical fibres, to enable provision of RRU's cables and fibres through the inner of the pole. Otherwise cables and f... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 7.4 Cover and concealing Box | A cover can be designed for mounting multiple RRUs (e.g. 2 RRUs on one lamp-post) and to protect the antenna from external mechanical stresses that could come from branches of trees in some scenarios. Additionally, the cover could provide concealment to the RRU and give mechanical protection. The design of the conceali... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 8 RRU energy consumption | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 8.1 General | The micro-cell concept as implemented by RRUs hosted on lamp-posts, with support of Multiple Input-Multiple Output (MIMO) technologies, can have typical energy consumptionin excess of 100 Watts. The mini-macro cell as implemented by RRUs hosted on lamp-posts, with identical MIMO technologies, can have typical power con... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 8.2 Power supply converter | An AC-DC or DC-DC voltage converter is required to provide the necessary voltage supplies to the RRU components. The power supply converter protects the RRU from any overvoltages due to induction from lightning stroke in the vicinity. As good (low resistance) earthing may not be available at all lamp posts due to cost ... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 8.3 Opto-electronic converter | The opto-electronic converter provides: • opto-electronic conversion: optical signals from the front-haul connection to electrical signals for processing by the PA; • electro-optic conversion: electrical signals from the PA to optical signals for transmission to the BBU. Several factors will influence the optical trans... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 8.4 Power amplifier | Modelling the energy consumption of a PA is based on the following parameters: • output transmitted power of the antenna; • output power of the PA; • the share of maximum bandwidth, that an antenna uses, i.e. the actual number of the physical resource blocks that occupies a certain bandwidth for transmission. The PA is... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 8.5 Antenna | The antenna does not influence directly the energy consumption as it is a purely passive element. It affects it indirectly as, depending from the antenna characteristics (the antenna gain and radiation pattern) more or less transmit power could be required. The antenna can be integrated into the RRU. Further consumptio... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9 Power supply provision | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.1 Power from the grid | Figure 5 and Figure 6 show two separate power supplies feeds on each side of the road in order to reduce the risk of service disruption due to failure of one set of RRUs. With the development of 5G aiming at easy deployment of wireless networks, the mainstream 5G related RRUs typically can support AC or DC power feedin... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2 DC power feeding from centralized sites | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2.1 General | Figure 5 and Figure 7 show the use of data and power supply cabling serving each lamp-post. The data and power are served from centralized locations co-located with the groups of BBUs. It should be noted that centralized power supplies could also be accommodated in other ad-hoc sites where required due to the topology,... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2.2 Remote powering at 38-72 VDC | The equipment of the RRU is designed to work with the most common powering architectures found in Central Offices to supply Network Telecommunications Equipment (NTE) with operating voltages in the range 38-72 VDC. Feeding DC voltages within such range enables the use of common and lower cost equipment. The use of volt... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2.3 Remote powering in accordance with IEEE 802.3 applications | Sometimes referred to as Power over Ethernet (PoE), IEEE 802.3bt [i.5] specifies remote power feeding over 2 and 4 balanced pairs of cables of Category 5 and above (as specified in EN 50173-1 [i.1]). In addition, IEEE 802.3cg [i.6] specifies remote power feeding of a variety of 1 pair balanced cables. Both implementati... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2.4 Higher voltage DC power feeding | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2.4.1 RTF-C and RFT-V | Recommendation ITU-T K.50 [i.9] specifies the operation of remote power feeding of telecommunications equipment using voltage- (RFT-V) and current-limited (RFT-C) solutions capable of supplying up to 100 W per powering circuit in accordance with IEC 62368-3 [i.4]. Both RFT-C and RFT-V can use multiple powering circuits... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.2.4.2 Other solutions | A number of solutions exist where the power supply is implemented using conductors of similar diameters to those of clauses 9.2.2 and 9.2.3 but at voltages of up to and including 400 VDC. The simplest solution is to employ a true DC voltage of approximately 400 VDC. The background to this approach is the forecast growt... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.3 Hybrid data and power supply cabling | All of the solutions of clause 8.2 enable the use of comparatively small conductors and are able to supply a variety of power levels over a range of distances. This offers the opportunity for the provision of both data and power supply elements within a "hybrid" cable construction feeding the RRUs from the BBU sites. T... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 9.4 Earthing | The installation of should not assume the presence of a protective earth at each lamp-post. In addition, the presence of a protective earth may not provide an effective functional earth for any sensor circuitry of RRU equipment installed on the lamp-post. ETSI ETSI TS 110 174-2-2 V1.2.1 (2020-11) 28 |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 10 Accessing the lamp-posts | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 10.1 Existing pathways | |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 10.1.1 General | Civil works represent the majority of the cost of deploying a telecommunications communications network outside buildings. Excavation to install new pathway systems (conduit, etc.) and cables is not only costly but can also be a source of delay due to difficulty in obtaining the necessary permissions and the resulting ... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 10.1.2 Underground services | Underground cable management systems providing the existing power supplies to lamp-posts are typically conduits (ducts) of 80-100 mm diameter and these are frequently under-utilized, containing only one or two power circuits. The use of free space in such conduits (ducts) for the provision of data and power to support ... |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 10.1.3 Overhead services | Existing aerial cabling pathways serving the lamp-posts could accept the addition of data and power supply cables feed the RRU. EN 50174-3 [i.2] specifies requirements of the installation of aerial cables on shared infrastructures. |
732c20c558beb43159ed5fd386ac6bc5 | 110 174-2-2 | 10.2 New underground pathways | EN 50174-3 [i.2] specifies the depths of underground pathways for telecommunications cables in footpaths and roads (including parking areas). In addition, EN 50174-3 [i.2] states that installation of cables at depths less than those specified results in those installations being treated as sacrificial (i.e. subject to ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 1 Scope | The present document specifies the high level O-RAN slicing related use cases, requirements and architecture. While some of the requirements are derived from use cases, some of the relevant SDO requirements are captured as they have impact on O-RAN functions. Along with requirements and reference slicing architecture, ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 2 References | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 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... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 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... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 3 Definition of terms, symbols and abbreviations | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 3.1 Terms | For the purposes of the present document, the terms given in [i.1] and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in [i.1]. A1: interface between non-RT RIC and Near-RT RIC to enable policy-driven guidance of Near-RT RIC applications/... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 3.2 Symbols | Void. |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in [i.1] and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in [i.1]. AEF API Exposing Function AI/ML Artificial Intelligence/Machine Learning AMF API Mana... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 4 Slicing Overview | Network Slicing is expected to play a critical role in 5G networks because of various use cases and services 5G will support. It allows a network operator to provide services tailored to customers' requirements. Network slice is defined as a logical network with a bundle of specified network services over a common netw... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5 High-Level O-RAN Slicing Use Cases | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.1 O-RAN Slicing Use Cases | This clause contains high-level O-RAN slicing use cases that O-RAN is expected to support. Slicing requirements will include the requirements derived from the specified use cases. Additional use cases will be added as prioritized by the O-RAN community in future versions of the present document. It should be noted that... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.0 O-RAN Slice Subnet Management and Provisioning | Network slicing is conceived to be an end-to-end feature that includes the core network, the transport network and the RAN. Although 3GPP has started defining network slicing support with Release 15, slicing in O-RAN needs to be further addressed in line with 3GPP to achieve deployable network slicing in an open RAN en... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.1 O-RAN Slice Subnet Instance Creation | The context of the O-RAN Slice Subnet Instance Creation Use Case is captured in table 5.2.1-1. Table 5.2.1-1: O-RAN Slice Subnet Instance Creation Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Creation of a new O-RAN network slice subnet instance (O-NSSI) or use an existing O-NSSI to satis... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.2 O-RAN Slice Subnet Instance Activation | The context of the O-RAN Slice Subnet Instance Activation Use Case is captured in table 5.2.2-1. Table 5.2.2-1: O-RAN Slice Subnet Instance Activation Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Activation of an O-RAN network slice subnet instance (O-NSSI) (3GPP TS 28.531 [4], clause 5.1... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.3 O-RAN Slice Subnet Instance Modification | The context of the O-RAN Slice Subnet Instance Modification Use Case is captured in table 5.2.3-1. Table 5.2.3-1: O-RAN Slice Subnet Instance Modification Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Modification of an existing O-NSSI to satisfy O-RAN slice subnet related requirements (3G... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.4 O-RAN Slice Subnet Instance Deactivation | The context of the O-RAN Slice Subnet Instance Deactivation Use Case is captured in table 5.2.4-1. Table 5.2.4-1: O-RAN Slice Subnet Instance Deactivation Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Deactivation of an O-RAN network slice subnet instance (O-NSSI) (3GPP TS 28.531 [4], clau... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.5 O-RAN Slice Subnet Instance Termination | The context of the O-RAN Slice Subnet Instance Termination Use Case is captured in table 5.2.5-1. Table 5.2.5-1: O-RAN Slice Subnet Instance Termination Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Termination or disassociation of an existing O-RAN network slice subnet instance (O-NSSI) (... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.6 O-RAN Slice Subnet Instance Configuration | The context of the O-RAN Slice Subnet Instance Configuration Use Case is captured in table 5.2.6-1. Table 5.2.6-1: O-RAN Slice Subnet Instance Configuration Use Case Use Case Stage Evolution / Specification <<Uses>> Related use Goal Configuration of an O-NSSI (3GPP TS 28.531 [4], clause 5.1.13). Actors and Roles NSSMS_... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.2.7 O-RAN Slice Subnet Feasibility Check | The context of the O-RAN Slice Subnet Feasibility Check is captured in table 5.2.7-1. Table 5.2.7-1: O-RAN Slice Subnet Feasibility Check Use Case Stage Evolution / Specification <<Uses>> Related use Goal To check the feasibility of provisioning an O-RAN network slice subnet instance (O-NSSI) to determine whether the O... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.3 O-RAN Slicing Use Cases | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.3.1 Use Case 1: RAN Slice SLA Assurance | 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... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.3.2 Use Case 2: Multi-vendor Slices | This use case enables multiple slices with functions provided by multi-vendors, such as slice #1, composed of DU(s) and CU(s), provided by vendor B and slice #2, composed of DU(s) and CU(s), provided by vendor C (see figure 5.3.2-1). Figure 5.3.2-1: Multi-vendor Slices When providing multiple slices, it is assumed that... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 5.3.3 Use Case 3: NSSI Resource Allocation Optimization | 5G networks are becoming increasingly complex with the densification of millimeter wave small cells, and various new services, such as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low Latency Communications), and mMTC (massive Machine Type Communications) that are characterized by high speed high data volume... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 6 O-RAN Slicing Principles and Requirements | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 6.1 General Principles | This clause contains the general O-RAN slicing architecture principles as described below: • O-RAN slicing architecture and interface specifications shall be consistent with 3GPP architecture and interface specifications to the extent possible. • O-RAN slicing architecture shall provide standardized management service ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 6.2 Slicing Requirements | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 6.2.1 Functional Requirements | Initial set of O-RAN slicing functional requirements based on the use cases defined in the present document are captured in table 6.2.1-1. Table 6.2.1-1: O-RAN Slicing Functional Requirements REQ Description Note [REQ-SL-FUN1] O-RAN slicing architecture and interfaces shall support network slicing, where an instance of... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 6.2.2 Non-Functional Requirements | Initial set of O-RAN slicing non-functional requirements based on the use cases defined in the present document are captured in table 6.2.2-1. Table 6.2.2-1: O-RAN Slicing Non-Functional Requirements REQ Description Note [REQ-SL-NFUN1] O-RAN slicing architecture shall support use of AI/ML to support RAN slicing use cas... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7 O-RAN Reference Slicing Architecture | |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.1 O-RAN Reference Slicing Architecture | This clause provides O-RAN reference slicing architecture (see figure 7.1-1) along with the high level roles and responsibilities of O-RAN network functions. Figure 7.1-1: O-RAN Reference Slicing Architecture O-RAN reference slicing architecture includes slice management functions along with O-RAN architectural compone... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.2 Non-RT RIC | The fundamental role of the Non-RT RIC in O-RAN slicing architecture is to gather long term slice related data through interaction with the SMO framework and apply AI/ML based approaches interworking with the Near-RT RIC to provide innovative RAN slicing use cases. For this purpose, Non-RT RIC shall be aware of RAN sli... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.3 Near-RT RIC | Near-RT RIC is the component which enables near-real-time RAN slice subnet optimization through execution of slicing related xApps and communicating necessary parameters to O-CU and O-DU through E2 interface. Deployed xApps can utilize either AI/ML based models or other control schemes which can further be guided by A1... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.4 O-RAN Central Unit (O-CU) | O-CU, which includes a single O-CU-CP and possibly multiple O-CU-UP(s), which are communicating through E1 interface, needs to support slicing features as defined by 3GPP. Depending on slice requirements, O-CU-UP can be shared across slices or a specific instance of O-CU-UP can be instantiated per slice. On top of 3GPP... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.5 O-RAN Distributed Unit (O-DU) | O-DU, which runs the lower layer protocols of RAN stack, shall support slice specific resource allocation strategies as well. Based on the initial O1 configuration of PRB allocation levels along with O-CU directives over F1 interface and the dynamic guidance received from Near-RT RIC over E2 interface, MAC layer needs ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.6 A1 Interface | A1, which is the interface between the Non-RT RIC and the Near-RT RIC, supports policy management, ML model management and enrichment information services [i.13]. These three services will be utilized for various slicing use cases, such as slice SLA assurance. Policy management will be used by Non-RT RIC to send slice ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.7 E2 Interface | E2, which is the interface between the Near-RT RIC and the E2 nodes, supports E2 primitives (Report, Insert, Control and Policy) to control the services exposed by E2 nodes [i.14]. These primitives will be used by slice specific applications (xApps) to drive E2 nodes' slice configurations and slice specific behaviour, ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.8 O1 Interface | O1, which is the interface between O-RAN managed elements and the management entity shall be used as specified in O-RAN.WG1.O1-Interface.0-v04.00 [13], to configure slice specific parameters of O-RAN nodes based on the service requirements of the slice. Some of the slice specific information models have been specified ... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.9 O2 Interface | O2, which is the interface between the SMO and O-Cloud as introduced in [i.15], will be used for life cycle management of virtual O-RAN network functions. As part of RAN NSSI creation and provisioning, RAN NSSMF, in interaction with SMO, triggers the instantiation of necessary O-RAN functions (such as Near-RT RIC, O-CU... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 7.10 Transport Network Slicing | As RAN Slice Subnet is composed of not only the O-RAN NFs but also the transport network components; Fronthaul interface (FH) between O-RU and O-DU and the Midhaul interface (MH) between the O-DU and O-CU, transport slicing aspects needs to be considered and incorporated into the overall O-RAN Slicing Architecture. ETS... |
25afcd9f8bff1a1f16037e46f0d49896 | 104 041 | 8 O-RAN Slice Subnet Provisioning Procedures | 8.1 O-RAN Slice Subnet Instance (O-NSSI) Allocation Procedure The procedure for allocation of an O-RAN slice subnet instance to satisfy the O-NSSI requirements is given in figure 8.1-1. ETSI ETSI TS 104 041 V11.0.0 (2025-03) 34 Figure 8.1-1: O-NSSI Allocation Procedure ETSI ETSI TS 104 041 V11.0.0 (2025-03) 35 1) Slice... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 1 Scope | The present document details measures which may be taken to improve the energy efficiency within operators sites and data centres for broadband deployment. Clauses 2 and 3 contain references, definitions and abbreviations which relate to this part; similar information will be included in the corresponding clauses of th... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ANSI/TIA-942: "Telecommunications Infrastructure Stan... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 102 489: "Environmental Engineering (EE)... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 3 Definitions and abbreviations | |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: application: single program or a set of several programs executing a function or a service availability: time or period during the application or the service has to be operational NOTE: Availability is one of the criticality criteria. ... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Alternative Curent ADSL Asymetric Digital Suscriber Line AS Application Server ATTM Access Transmission Terminal and Multiplexing B2B Business To Business B2C Business To Customer BTS Base Transceiver Station CPU Central Processing Unit CRA... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4 Overview of data centres | |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.1 Types of data centres | There are a number of different types of data centre: • a network data centre has the primary purpose of the delivery and management of broadband services to the operator's customers. To enable their functionality, all network data centres must be connected to at least one core network operator site. For reasons of net... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.2 Tiering of data centres | |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.2.1 Tiers and criticality | Several levels of data centres have been defined, based on the criticality of the applications or the business processed which determine the global Recovery Time Objective (RTO). The lower the RTO, the more the data centre has to be supported by the use of redundant equipment in both the technical environment and IT in... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.2.2 ANSI/TIA-942 | ANSI/TIA-942 [1] defines requirements for reliability and availability of data centres, including the associated redundant support infrastructures, based on four "tiers". Network data centres are assumed to at least meet the requirements of Tier 3. |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.2.3 Uptime Institute | The Uptime Institute [2] defines an alternative system of "Tiers" based upon business objectives and acceptable downtime as shown in table 1. The Tier determines the redundancy of energy and cooling equipment as indicated in table 1 and shown in figure 2 and has some significant consequences on energy costs. Table 1: U... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.2.4 Criticality levels | These levels as shown in table 2 are proposed by the Siska Hennessey Group and offers 10 levels of criticality, from 98 % estimated availability (175,2 hours of downtime/year) for a C1 level to C10 level (99,99999999 %, which corresponds to 0,0031 s of annual downtime). Levels above C4 are not considered to be achievab... |
a525c3531c3b8f5d14495cfdffcb2180 | 105 174-2-2 | 4.2.5 Tiers and costs | The capital expenditure (Capex) and operational expenditure (Opex) of new data centres increase with the tier level. Figure 3 shows Capex and Opex (normalized to 100 for the Uptime Institute Tier 1) as a function of Uptime Institute tier. ETSI ETSI TS 105 174-2-2 V1.1.1 (2009-10) 15 0 50 100 150 200 250 300 Tier 1 Tier... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.