# On Deploying the Internet of Energy with 5G Open RAN Technology including Beamforming Mechanism
## 3 Open RAN for Flexible Development of 5G Networks  
In the classical vision of the development of mobile networks, the individual RAN elements are practically always provided by one supplier because the interfaces between them are largely closed proprietary solutions. As a result, the selected supplier carries out orders (from Mobile Network Operator, MNO) for base stations for a given area, which is commonly known as a cluster. This situation is given by the limited standardization offered by 3 GPP, which reduces the interoperability of multi-vendor elements of the network. Thus, operators identify obstacles to the development of new services due to the lack of flexible and agile development of their networks. In Open RAN networks, the flexibility is higher since more providers may develop concrete solutions requested by the customers of the network. Under the presented conditions, maintaining the so-called multi-vendor, although possible in some situations, is extremely difficult to maintain and manage. Another aspect that prompts telecommunications operators to deal with Open RAN is the issue of the costs of building a 5G network. Disaggregation of the network (Open RAN) could reduce costs, since more actors could provide network equipment (especially in the case of software) and more innovation could develop better management [19]. Flexibility and cost-saving are both crucial for the development of the IoE, therefore we think that Open RAN may be a way for developing IoE with 5G technology. Open RAN architecture is based on new open interfaces (standardized mainly by O-RAN Alliance and its predecessors) which are added to the 3 GPP-standardised F1 interface. 3 GPP considers that Radio Access Network may be divided into two main components: Centralized Unit and Distributed Unit. 3 GPP standardize the interface between the two units (F1 interface). The two units perform concrete radio functionalities: the ones that may be carried out far away from the antennas and are common to a number of antennas are performed by the Centralized Unit, whereas the functionalities that must be run close to the antenna are performed by the Distributed Unit. The Centralized Unit runs: (1) the Radio Resource Control (RRC) protocol, which is in charge of broadcasting the system information, establishment and maintenance of the RRC connections (carrier aggregation, Dual Connectivity), managing security keys with the Core Network, configuring Signalling and Data Radio Bearers, managing handover and interRAT mobility, reporting User Equipment (UE) measurements, and transferring to the Core the NAS (Non-Access Stratum) messages; (2) the Service Data Adaptation Protocol (SDAP), which is responsible of handling QoS (Quality of Service) established by the Session Management Function in the Core, including Guaranteed and Non-guaranteed bit rates as well as negotiated or reflective QoS in the Uplink, executing the radio bearers configured by the RRC and the PDU sessions (each session requires one SDAP instance); (3) the Packet Data Convergence Protocol (PDCP), which performs the next functionalities: transfer of data including sequence numbering and handover control, TCP/IP header compression, ciphering/deciphering and data protection, discarding of Signalling Data Units, managing dual connectivity of Packet Data Units and selection of the Transparent, Acknowledged and Unacknowledged modes of the Radio Link Control [20; 21; 22; 23]. The Distributed Unit runs: (1) Radio Link Control (RLC) protocol, which is in charge of handling transparent, acknowledged, or unacknowledged modes of transmission between the radio and the UE, i.e., how the packet transmission in the radio interface should be acknowledged including the transparent mode for synchronization and other system messages that pass directly to the antenna without further processing in the RLC.