Transport node and method in a wireless communications network

Abstract

A method performed by a transport node is provided. The method is for configuring connections in a local Distributed Radio Access Network, DRAN, site for a wireless communications network. The local DRAN site comprises the transport node and a first set of Radio Access Network, RAN, entities. The first set of RAN entities comprises one or more radio entities and one or more Baseband, BB, entities between which connections has been configured. The transport node notifies (202) the respective RAN entity in the first set of RAN entities, that a further entity is connected to the local DRAN site. The transport node compiles (203) data related to and received from the respective RAN entity in a second set of RAN entities comprising the further entity and the RAN entities in the first set. The transport node streams out (204) the compiled data to the respective BB entity in the second set of RAN entities. The transport node receives (206) a configuration request from a BB entity in the second set of RAN entities based on the streamed out compiled data. The configuration request requests configurations of connections between the respective one or more radio entities and one or more BB entities in the second set. The transport node configures (207) the respective connection according to the received configuration request. The transport node streams out (208) to a computer connected to the transport node and the respective BB entity in the second set of RAN entities configuration information about the requested configured connections.

Description

[0001] TRANSPORT NODE AND METHOD IN A WIRELESS COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a transport node and a methods therein. In some aspects, they relate to configuring connections in a local Distributed Radio Access Network (DRAN) site for a wireless communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5G Core (5GC) is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5GC.

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] In mobile networks, such as wireless communications networks, there is planning work of both RAN and transport network configurations in advance of deployment. At installation and deployment of a RAN network, all planned configurations are deployed in the installed equipment. Installation and configuration of new site equipment are made at different stages during the deployment. Configuration is made on several different sites by different type of installation engineers and at different times. This work takes a lot of time and is cumbersome.

[0010] A DRAN is a setup where Remote Radio Unit (RRU)s, also referred to as radio entities, and Baseband Units BBU (BBU)s, also referred to as Baseband (BB) entities, are co-located at every cell site. They run proprietary applications on specialized hardware, for Baseband there is also an alternative to run the application on general purpose hardware. SUMMARY

[0011] As part of developing embodiments herein, the inventors identified some problems that first will be described.

[0012] As mentioned above, the planning and deployment of all configurations in a RAN network is time consuming and costly. The same problem applies for planning and deployment of all configurations in local DRAN sites. As there are multiple deployment and / or installation teams involved in a complete deployment, there is always a risk of mistakes or misinterpretation of instructions or configuration files. These mistakes often lead to “hard-to-find” problems that are time-consuming and costly to find and resolve, leading to multiple site visits.

[0013] An object of embodiments herein is to improve simplification of configurations of connections in a local DRAN site of a wireless communications network.

[0014] According to an aspect of embodiments herein, the object is achieved by a method performed by a transport node. The method is for configuring connections in a local Distributed Radio Access Network, DRAN, site for a wireless communications network. The local DRAN site comprises the transport node and a first set of Radio Access Network, RAN, entities. The first set of RAN entities comprises one or more radio entities and one or more Baseband, BB, entities between which connections has been configured, The transport node notifies the respective RAN entity in the first set of RAN entities, that a further entity is connected to the local DRAN site. The transport node compiles data related to and received from the respective RAN entity in a second set of RAN entities comprising the further entity and the RAN entities in the first set. The transport node streams out the compiled data to the respective BB entity in the second set of RAN entities. The transport node receives a configuration request from a BB entity in the second set of RAN entities based on the streamed out compiled data. The configuration request requests configurations of connections between the respective one or more radio entities and one or more BB entities in the second set. The transport node configures the respective connection according to the received configuration request. The transport node streams out to a computer connected to the transport node and the respective BB entity in the second set of RAN entities configuration information about the requested configured connections. According to another aspect of embodiments herein, the object is achieved by a transport node. The transport node is configured to configure connections in a local Distributed Radio Access Network, DRAN, site for a wireless communications network. The local DRAN site is adapted to comprise the transport node and a first set of Radio Access Network, RAN, entities. The first set of RAN entities is adapted to comprise one or more radio entities and one or more Baseband, BB, entities between which connections has been configured. The transport node further configured to:

[0015] - Notify the respective RAN entity in the first set of RAN entities, that a further entity is adapted to be connected to the local DRAN site,

[0016] - Compile data related to and received from the respective RAN entity in a second set of RAN entities adapted to comprise the further entity and the RAN entities in the first set,

[0017] - Stream out the compiled data to the respective BB entity in the second set of RAN entities,

[0018] - Receive a configuration request from a BB entity in the second set of RAN entities based on the streamed out compiled data, which configuration request is adapted to request configurations of connections between the respective one or more radio entities and one or more BB entities in the second set,

[0019] - Configure the respective connection according to the received configuration request,

[0020] - Stream out to a computer connected to the transport node and the respective BB entity in the second set of RAN entities configuration information about the requested configured connections.

[0021] Embodiments herein may provide one or more of the following advantages:

[0022] When installing a new DRAN site or new equipment at a DRAN site there is no need for, or at least much less time needed for planning and / or preparation work for configuration of the local DRAN site. All local RAN entities are automatically detected and needed transport configuration of the transport node is performed quick, efficient, and e.g., automated. This saves cost and / or time for planning work and avoids errors both in planning and during installation phase. Any change or adding of RAN entities on site will automatically be detected and transport configuration automatically set-up. In some embodiments, at early stage of installation when radio entities are connected to the transport node, such as a local Switch Router (SWR), a connected computer of an installation engineer, may get a notification that a further RAN entity is identified and successfully connected to the transport node. This enables different installation teams to perform deployment and verification at different times Without dependencies between teams. At a later stage of installation when network connectivity becomes available, configurations such as e.g., backhaul transport configurations, of all RAN entities connected to the transport node in the local DRAN site are set up quick, efficient, and e.g., automatically.

[0023] BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0025] Figure 1a is a schematic block diagram illustrating embodiments of a communications network.

[0026] Figure 1b is a schematic block diagram illustrating embodiments of a DRAN site. Figure 2 is a flowchart depicting an embodiment of a method in a transport node. Figure 3 is a schematic block diagram illustrating embodiments of a DRAN site.

[0027] Figure 4 is a schematic block diagram illustrating embodiments of a DRAN site.

[0028] Figure 5 is a schematic block diagram illustrating embodiments of a DRAN site.

[0029] Figure 6 is a schematic block diagram illustrating embodiments of a DRAN site.

[0030] Figure 7 is a schematic block diagram illustrating embodiments of a DRAN site.

[0031] Figure 8 is a schematic block diagram illustrating embodiments of a transport node.

[0032] DETAILED DESCRIPTION

[0033] Example embodiments herein provide methods for configuring connections in a local DRAN site for a wireless communications network, such as e.g. configuring local transport node equipment, such as e.g., a SWR equipment at installation and / or deployment of a new DRAN site or new equipment at a DRAN site using local packet fronthaul. This procedure provided by example embodiments herein, automates configuration of the local transport node without any backhaul network connectivity available.

[0034] Figure 1a is a schematic overview depicting a wireless communications network 100 wherein embodiments herein may be implemented. The wireless communications network 100 comprises one or more RANs, and one or more CNs. The communications network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0035] RAN nodes, such as a RAN node 110, operate in the RAN of the communications network 100. The RAN node 110 may be a transmission and reception point e.g. a radio access network node such as a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, or any other network unit capable of communicating with UEs, such as a UE 120, within a cell, served by the RAN node 110. The RAN node 110 may be referred to as a serving radio network node and may communicate with the UE 120 with Downlink (DL) transmissions to the UE 120 and Uplink (UL) transmissions from the UE 120.

[0036] One or more UEs operate in the wireless communication network 100, such as e.g. the UE 120. The UE 120 may e.g. be a remote UE, a wireless device, an NR device, a mobile station, a wireless terminal, an NB-loT device, an MTC device, an eMTC device, a CAT-M device, a WiFi device, an LTE device and an a non-access point (non-AP) STA, a STA, that communicates via the RAN node 110, to one or more CN nodes in one or more CNs. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, client, mobile client, IMS client, wireless communication terminal, user equipment, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a car or any small base station communicating within a cell.

[0037] Figure 1b is a schematic overview depicting a local DRAN site 105 of the wireless communications network 100 wherein embodiments herein may be implemented. A DRAN site 105 being local may e.g., mean that the DRAN site 105 comprises antenna and radio entities transmitting the wireless signals, baseband computing entities, site interconnect entities, and transport connectivity entities for connection into the wireless communication network. The local DRAN site 105 comprises the RAN node 110 and a transport node 130. The transport node 130 may e.g., be represented by a SWR.

[0038] The local DRAN site 105 further comprises a first set of RAN entities. The first set of RAN entities comprises one or more radio entities 111, 112, 113 and one or more Baseband (BB) entities 121 122 between which connections have been configured, according to an example scenario herein.

[0039] The transport node 130 and the first set of RAN entities may be comprised in the RAN node 110.

[0040] According to embodiments herein a, e.g. one or more, further entity 114, 123, 150 will be connected to the local DRAN site 105. The further entity may be represented by any one or more out of a further radio entity 114, a further BB entity 123 and / or a further network connection node 150. The network connection node 150 may e.g., be a Cell Site Router (CSR) for the local DRAN site 105.

[0041] When the at least one further entity 114, 123, 150 is connected to the local DRAN site 105, the first set of RAN entities is updated and is, when updated with further entity 114, 123, 150, referred to as a second set of RAN entities. The second set of RAN entities thus comprises the first set of RAN entities, and the further entity 114, 123, 150.

[0042] The respective BB entities 121 ,122 and further BB entity 123 may each be BB entity comprising any of a general BB capability, a purpose-built BB or a Cloud RAN implemented BB. General BB capability may e.g., mean handling, steering, prioritizing data to be transmitted and / or received by the radio over the wireless interface. A purpose- built BB may e.g., mean a BB entity built on dedicated and specialized hardware running BB software applications. A Cloud RAN implemented BB may e.g., mean a BB application running in a cloud-based software execution environment where the hardware may be general purpose entities or purpose-built entities.

[0043] A computer 140 is connectable, e.g., accessible, to the transport node 130. The computer 140 may be used and / or controlled by an installation engineer. In some embodiments the transport node 130 receives signals and / or from the computer 140 to perform actions according to embodiments herein. The computer 140 may e.g., be used to visualize and / or present to an installation engineer, when and how entities get plugged- in to the transport node 130, also present specifically which RAN entities and their respective identifications. The installation engineer may e.g., refer to any person being responsible for or taking part of installing the DRAN site 105. Further the computer 140 may e.g., be used to visualize and / or present a connection configuration between entities such as RAN entities that is automatically requested by BB entities and being deployed in the transport node 130.

[0044] The computer 140 may comprise and / or run an application. The application may e.g. visualize and / or present as described above.

[0045] Methods according to embodiments herein are performed by the transport node 130. This node may be Distributed Nodes (DN)s and functionality, e.g. comprised in a cloud 170 as shown in Figure 1a.

[0046] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0047] Examples of embodiments herein provide an automated configuration of a local DRAN site transport node 130. A method according to embodiments will first be described in a general way as seen from the view of the transport node 130 together with Figure 2. This will be followed by a more detailed description with examples.

[0048] Figure 2 shows examples of embodiments of a method performed by the transport node 130. The method is for configuring connections in the local DRAN site 105 for the wireless communications network 100. The word for in “for” the wireless communications network 100, e.g., means that according to an example scenario, the method is performed locally, i.e., it is not needed to be connected to the wireless communications network 100. After configuration of the DRAN site with CONNECTIONS between the RAN entities and the further added entity according to this method it is possible to access to the wireless communications network 100. As mentioned above, the local DRAN site 105 comprises the transport node 130 and a first set of RAN entities. The first set of RAN entities comprises one or more radio entities 111 , 112, 113 and one or more BB entities 121 , 122 122 between which connections have been configured.

[0049] The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 2. Action 201. In some embodiments, the transport node 130 configures connections between the respective one or more radio entities 111 , 112, 113 and the respective one or more Baseband, BB, entities 121 , 122.

[0050] Action 202. According to an example scenario, the transport node 130 detects or is informed that a further entity 114, 123, 150 has been connected to the local DRAN site 105 and need to inform the RAN entities in the first set of RAN entities about it. In some embodiments, the further entity 114, 123, 150 is represented by any one or more out of the radio entity 114, the BB entity 123, and / or the network connection node 150.

[0051] The transport node 130 notifies the respective RAN entity in the first set of RAN entities, that the further entity 114, 123, 150 is connected to the local DRAN site 105. The transport node 130 may send the notification via a discovery protocol such as e.g., Link Layer Discovery Protocol (LLDP) Type, Length, Value (TLV) or vendor specific TLV.

[0052] An LLDP is an open and extendable part of the Internet protocol suite used in IEEE 802 to advertise a device's identity and abilities, as well as other devices connected within the same network. TLV is a common encoding format used in computer networking and data communication protocols. It is a flexible and extensible method for structuring data elements within a protocol message.

[0053] In some embodiments, the transport node 130 further notifies the network connection node 150 such as e.g. the CSR, that the further entity 114, 123, 150 is connected to the local DRAN site 105.

[0054] Action 203. The transport node 130 compiles data related to and received from the respective RAN entity in a second set of RAN entities. The second set of RAN entities comprises the further entity 114, 123, 150 and the RAN entities in the first set. The data may e.g., be received via LLDP TLV.

[0055] In some embodiments, the transport node 130 further compiles data related to and received from, e.g., via LLDP TLV, a network connection node 150.

[0056] Thus, the transport node 130 may compile data related to and received from the respective RAN entity and network connection node 150. The network connection node 150 may in some embodiments be comprised in the first set of RAN entities and in some embodiments also be comprised in the second set of RAN entities.

[0057] The data to be compiled may each e.g., relate to data such as any one or more out of: type of product, capabilities, serial-number, and installation information etc. Action 204. The transport node 130 streams out the compiled data to the respective BB entity 121 , 122 in the second set of RAN entities and in some embodiments also to the network connection node 150. To “stream out” when used herein e.g., means streaming out compiled data on e.g. Secure Shell (SSH) / Secure Sockets Layer (SSL) logical ports that the RAN entities in the second set of RAN entities can connect to and receive the streamed our data.

[0058] The compiled data may be retrieved by the respective RAN entity in the second set of RAN entities by connecting to the SSH / SSL logical ports on the transport node 130. The compiled data may be retrieved by e.g., the computer 140 or the network connection node (150).

[0059] As hinted above, the compiled data may e.g., be streamed out via a SSH authentication protocol connection, or an SSL connection.

[0060] Action 205. The transport node 130 may periodically announces a temporary Internet Protocol (IP) address. The temporary IP address is announced to the computer 140 connected to the transport node 130, the respective BB entity in the second set of RAN entities, and in some embodiments to the network connection node 150. All the RAN entities connected to the DRAN site 105, such as the entities in the second set of RAN entities may use a temporary IP address that may e.g., be announced using an IPv6 link local address or IPv4 Automatic IP Addressing (APIPA) periodically announced via e.g. LLDP TLV. The announced temporary IP address will be used by said entities when they connect to each other. As the local system, such as the local DRAN site 105, is assumed to not have a dedicated entity or function for assignment of IP addresses to the entities in the Local DRAN site, each entity may need to announce its temporary IP address.

[0061] Action 206. According to an example scenario, a BB entity 121 , 122, 123 in the second set of RAN entities reads the streamed out compiled data and realises that it needs to request configuration for new connections between Radio and BB entities.

[0062] The transport node 130 receives the configuration request from the BB entity in the second set of RAN entities. It is a BB entity 121 , 122, 123 that sends the request since it is the BB entities that manages all data transmitted and received by a radio entity and therefore the BB entities decides what radio entity to connect / relate to. The configuration request from the BB entity is based on the streamed out compiled data. The configuration request requests configurations of connections between the respective one or more radio entities 111 , 112, 113, 123 and one or more BB entities 121 , 122, 123 in the second set. In some embodiments, the configuration request from the BB entity in the second set of RAN entities further requests configurations of connections between the network connection node 150 and the one or more BB entities 121 , 122, 123 in the second set.

[0063] Action 207. The transport node 130 configures the respective connection according to the received configuration request. This may be performed by means of the the BB entity sending the configuration request as an intent, e.g. just as a connectivity request between a BB entity 121 , 122, 123, 124 and a radio entity 111 , 112, 113, 123. The transport node 130 may performs all needed configuration according to its internal syntax template. The configuration intent request may also contain principles such as point-to- point or multipoint-to-multipoint connection.

[0064] Action 208. The transport node 130 streams out configuration information about the requested configured connections. The configuration information is streamed out to the computer 140 connected to the transport node 130 and the respective BB entity in the second set of RAN entities. The configuration information may be streamed out e.g., via any of SSH or SSL. The configuration information may be received by the respective BB entity 121 , 122, 123 in the second set and possibly the network connection node 150 by connection to transport node 130 via SSH / SSL as used in Action 204.

[0065] Action 209. In some embodiments, the further entity 114, 123, 150 is represented by the network connection node 150. In these embodiments, the transport node 130 may initiate a permanent network connectivity and in some embodiments also e.g., manageability. This initiation may be performed when the transport node 130 has identified that a network connection node, such as the network connection node 150, for the local DRAN site 105 is available for connection to the wireless communications network 100. This means that the BB entities 121 , 122, 123 are notified about the availability of connection to network connection entity 150 for further connection the RAN network and CN of the wireless communications network 100. The BB entities 121 , 122, 123 may then request configuration of connectivity between BB entities 121 , 122, 123 and the network connection node 150. The request may be as an intent e.g. just as a connectivity request between a BB entity121 , 122, 123 and the network connection node 150. The transport node 130 performs all needed configuration according to its internal syntax template. The configuration intent request may also contain principles such as point-to-point or multipoint-to-multipoint connection. In this way by using the methods above, when installing a new DRAN site 105 or new equipment at the DRAN site 105 there is no need for planning and / or preparation work for configuration of a local DRAN site transport entity. All local equipment is automatically detected and needed transport configuration of local transport node 130 is automated. This saves cost and / or time for planning work and avoids errors both in planning and during installation phase. Any change or adding of equipment on the local DRAN site 105 will automatically be detected and transport configuration automatically set-up. At early stage of installation when a RAN entity, such as the further entity 114, 123, 150, is connected to the Local SWR, a connected installation engineer computer can get a notification that the Radio equipment is identified and successfully connected to the SWR. This enables different installation teams to perform deployment and verification at different times Without dependencies between teams. At a later stage of installation when network connectivity becomes available, all BB wireless network transport configuration in the transport node 130 is automatically set-up.

[0066] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to and may be combined with any suitable embodiment described above.

[0067] Some embodiments of an example of the method may be divided in to five steps described below. In example A the (one or more) further entity 114, 123, is any of: the radio entity 114 and / or BB entity 123 and the steps are referred to as Step 1 A, Step 2 A etc. In example B the (one or more) further entity 114, 123, is a network connection node 150, e.g. a CSR, and the steps are referred to as Step 1 B, Step 2 B etc.

[0068] Step 1 A: This step is depicted in Figure 3 and is related to Action 201 described above. At the DRAN site 105, the RAN entities such as the radio entities 111 , 112, 113 and the BB entities 121 , 122 in the first set of RAN entities, are started and connected to the local DRAN site 105. When they are started and connected, they automatically share their respective entity information with the transport node 130. The information sharing may be done via in LLDP protocol messages in TLV extensions. The LLDP messages mentioned herein may all be signed with vendor and / or local certificates for security reasons. The information shared over LLDP may e.g., be type of product, capabilities, serial-number and installation information.

[0069] Step 1 B. This step is related to Action 201 described above. The BB entities 121 , 122 in the first set of RAN entities and any CSR entities automatically share their respective entity information with the transport node 130, e.g., via LLDP TLV. Specifically, they may share that it is transport network ports and / or interfaces.

[0070] Step 2 A: This step is depicted in Figure 4 and is related to Action 202 described above. The transport node 130 then sends out a notification, e.g., via an LLDP TLV, to all RAN entities in the first set that a new RAN entity is connected and what transport entity address, such as the address of the transport node 130, to connect to for more information. The transport node 130 may also share, periodically, via Link local IPv6 IP address or IPv4 APIPA via LLDP TLV what IP address to connect to for more information. The procedure is the same at an initial installation of a DRAN site and for an existing DRAN site already in operation.

[0071] Step 2 B Notifying. This step is related to Action 202 described above. The transport node 130 receives information, e.g., via LLDP TLV, that the further entity 150, i.e., the CSR has been connected to the DRAN site 105. The further entity, the network connection node 150, is also referred to as a new connected entity herein. The transport node 130 then sends out a notification, e.g., via an LLDP TLV, to all entities, i.e., the RAN entities in the first set, including any CSR, that a new entity is connected, and what transport entity address, such as the address of the transport node 130, to connect to for more information. The transport node 130 may also share, periodically, via Link local IPv6 IP address or IPv4 APIPA via LLDP TLV what IP address to connect to for more information.

[0072] Step 3 A: This step is depicted in Figure 5 and is related to Action 203 and 204 described above. The transport node 130 may have a mode of operation referred to herein as DRAN local site SWR automated configuration. In this mode the transport node 130 is capable to work without a network connection and / or connection to O&M systems and thus used IP addresses may be temporary until permanent IP addresses are assigned at a later stage. All physically connected entities automatically connect, preferably using IPv6 link local IP addresses, where the link local address is periodically announced. If IPv4 needs to be used, all entities may use Automatic Private IP Addressing (APIPA). The transport node 130 share it’s IP address e.g., via IPv6 link local IP addresses or IPv6 via a periodic LLDP TLV. The transport node 130 assembles the further entity’s 114, 123, respective information received, e.g., via LLDP TLV, from the connected RAN entities now in the second set. The transport node 130 further compiles the information received from radio entities 111 , 112, 113, 114 and BB entities 121 , 122, 123, and streams out that information on the ports connected to BB entities 121 , 122, 123 and possibly the computer 140 of the installation engineer. At an initial DRAN site 105 installation when the transport node 130 is in the mode “DRAN local site automated configuration”, it may preferably only allow LLDP and SSH / SSL connectivity during the first stage. The information of connected radio entities 111 , 112, 113, 114 and BB entities 121 , 122, 123 is streamed out, e.g., in clear text using e.g. SSH or SSL. For an existing DRAN site 105 already in operation, the transport node 130 may already be in full switching and / or routing mode, but the automation function of new connected entities further entity 114, 123, may still be performed with the same principles.

[0073] Step 3 B. This step is related to Action 203 and 204 described above. Similar to example A, the transport node 130 compiles the received information received from the radio entities 111 , 112, 113, and BB entities 121 , 122, the network connection node 150, and stream out that information in clear text, using e.g. SSH or SSL for at least the BB entities 121 , 122 in the first set of RAN entities and the CSR to receive, but possibly also to the computer 140 of the installation engineer.

[0074] Step 4 A: This step is depicted in Figure 6 and is related to Action 206 described above. When one or more or any of the BB entity 121 , 122, 123 in the second set of RAN entities has received information of connected radio entities 111 , 112, 113, 114, it sends a configuration request to the transport node 130, i.e., the local transport node 130 in the DRAN site 105. The configuration request requests configuration of connections between the radio entities 111 , 112, 113, 114 and the BB entities 121 , 122, 123. The configuration request is e.g., sent in an LLDP TLV, where the BB entity 121 , 122, 123 notifies the transport node 130 about different connections needed, what radio entities 111 , 112, 113, 114 to connect and e.g., to what physical and / or logical ports to connect on. One alternative configuration may be an “Ethernet line” type of connection, where the radio entities 111 , 112, 113, 114 and the BB entities 121 , 122, 123 are connected point-to point, physically or logically. Another alternative configuration may be an Ethernet Local Area Network (LAN) type of connection, where radio entities 111 , 112, 113, 114 and BB entities 121 , 122, 123 are connected multipoint-to multipoint. Based on the request, the transport node 130 automatically configures connection(s) between radio entities 111 , 112, 113, 114 and the BB entities 121 , 122, 123. The transport node 130 sets-up the internal configuration, such as transport configuration, according to a syntax template of the transport node 130. Thus, there is no need for the BB entity 121 , 122, 123 to know how to configure the transport node 130, just the connection intent.

[0075] Step 4 B. This step is related to Action 206 described above. BB entities 121 , 122, 123 request configuration of connection such as e.g., transport network connection to the network connection node 150, e.g., the CSR entity. The request may be sent using LLDP TLV. The connection may be an Ethernet LAN” type of connection, where all BB entities 121 , 122, 123 and the network connection node 150, e.g., the CSR entity are multipoint connected.

[0076] Step 5 A: This step is depicted in Figure 7 and is related to Action 207 and 208 described above. When the Local transport node 130 have configured, also referred to as automatically configured all the connection(s) between radio entities 111 , 112, 113, 114 and the BB entities 121 , 122, 123, information about all configured connections between radio entities 111 , 112, 113, 114 and BB entities 121 , 122, 123 is streamed out e.g., on the ports connected to BB entities 121 , 122, 123 and possibly the computer 140 of the installation engineer. The information of configured connections is streamed out, e.g., in clear text using e.g., SSH or SSL. At initial installation and deployment of the DRAN site 105, when this stage is reached, the transport node 130 may change its mode of operation to full switching and / or routing mode but keeping the automation function for any more new connected entities. The DRAN site 105 is now fully connected. For an existing site already in switching / operation, this step is just a set-up confirmation of any requested connection configuration(s).

[0077] Step 5 B Configuration information. This step is related to Action 207 and 208 described above. The transport node 130 compiles the made configuration information related to the connections such as e.g., transport network connections and stream out that information in clear text using e.g. SSH or SSL, for at least the BB entities 121 , 122 and the network connection node 150, e.g., the CSR entity to receive, but possibly also to the computer 140 of the installation engineer. As network connectivity now is available via CSR for the transport node 130, any BB entity may initiate permanent IP network connectivity and manageability by sending out DHCP request to get an IP-address from the RAN. To perform the method actions above, the transport node 130 is configured to configure connections in the local DRAN site 105 for the wireless communications network 100. The local DRAN site 105 is adapted to comprise the transport node 130 and the first set of RAN, entities. The first set of RAN entities is adapted to comprise one or more radio entities 111 , 112, 113 and one or more BB entities 121 , 122 between which connections has been configured.

[0078] The transport node 130,131 ,132 may comprise an arrangement depicted in Figure 8. The transport node 130,131 ,132 may comprise an input and output interface 800 configured to communicate in the communications network 100. The input and output interface 800 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0079] The transport node 130,131 ,132 is further configured to notify the respective RAN entity in the first set of RAN entities, that a further entity 114, 123, 150 is adapted to be connected to the local DRAN site 105.

[0080] The transport node 130,131 ,132 is further configured to compile data related to and received from the respective RAN entity in a second set of RAN entities adapted to comprise the further entity 114, 123, 150 and the RAN entities in the first set.

[0081] The transport node 130,131 ,132 is further configured to stream out the compiled data to the respective BB entity 121 , 122 in the second set of RAN entities.

[0082] The transport node 130,131 ,132 is further configured to periodically announce to a computer 140 connected to the transport node 130 and the respective BB entity in the second set of RAN entities, a temporary Internet Protocol, IP, address.

[0083] The transport node 130,131 ,132 is further configured to receive a configuration request from a BB entity in the second set of RAN entities based on the streamed out compiled data, which configuration request is adapted to request configurations of connections between the respective one or more radio entities 111 , 112, 113, 123 and one or more BB entities 121 , 122, 123 in the second set.

[0084] The transport node 130,131 ,132 is further configured to configure the respective connection according to the received configuration request.

[0085] The transport node 130,131 ,132 is further configured to stream out to a computer 140 connected to the transport node 130 and the respective BB entity in the second set of RAN entities configuration information about the requested configured connections.

[0086] In some embodiments, wherein the further entity 114, 123, 150 is adapted to be represented by a network connection node 150, the transport node 130 is further being configured to: when identified that a network connection node 150, for the local DRAN site 105 is available for connection to the wireless communications network 100, initiate a permanent network connectivity.

[0087] Some embodiments, comprises any one out of:

[0088] - The transport node 130 configured to notify, is further configured to notify a network connection node 150, that a further entity 114, 123, 150 is connected to the local DRAN site 105,

[0089] - The transport node 130 configured to compile the data is further configured to compile data related to and received from a network connection node 150,

[0090] - The transport node 130 configured to stream out the compiled data is further configured to stream out to the network connection node 150,

[0091] - The transport node 130 configured to periodically announce a temporary Internet Protocol, IP, address, is further configured to announce to the network connection node 150

[0092] - The configuration request from the BB entity in the second set of RAN entities is further adapted to request configurations of connections between the network connection node 150, and the one or more BB entities 121 , 122, 123 in the second set, and

[0093] - The configuration information about the requested configured connections, is further adapted to stream out to the network connection node 150.

[0094] In some embodiments, the further entity 114, 123, 150 is adapted to be represented by any one or more out of a radio entity, a BB entity, and a network connection node 150.

[0095] In some embodiments, the transport node 130 is further being configured to configure connections between the respective one or more radio entities 111 , 112, 113 and the respective one or more Baseband, BB, entities 121 , 122.

[0096] Embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processor 810 of a processing circuitry in the transport node 130 depicted in Figure 8 together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the respective transport node 130. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the respective transport node 130. The transport node 130 may further comprise a respective memory 820 comprising one or more memory units. The respective memory 820 comprises instructions executable by the processor in the respective transport node 130. The respective memory 820 is arranged to be used to store e.g., media functions, indications, tags, information, data, configurations, communication data, and applications to perform the methods herein when being executed in the respective transport node 130.

[0097] In some embodiments, a respective computer program 830 comprises instructions, which when executed by the respective at least one processor 810, cause the at least one processor of respective transport node 130 to perform the actions above.

[0098] In some embodiments, a respective carrier 840 comprises the respective computer program 830, wherein the respective carrier 840 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0099] Those skilled in the art will appreciate that units in the respective transport node 130 described above may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the respective transport node 130, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry ASIC, or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC).

[0100] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of'.

[0101] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1 . A method performed by a transport node (130) for configuring connections in a local Distributed Radio Access Network, DRAN, site (105) for a wireless communications network (100), wherein the local DRAN site (105) comprises the transport node (130) and a first set of Radio Access Network, RAN, entities, which first set of RAN entities comprises one or more radio entities (111 , 112, 113) and one or more Baseband, BB, entities (121 , 122) between which connections has been configured, the method comprising: notifying (202) the respective RAN entity in the first set of RAN entities, that a further entity (114, 123, 150) is connected to the local DRAN site (105), compiling (203) data related to and received from the respective RAN entity in a second set of RAN entities comprising the further entity (114, 123, 150) and the RAN entities in the first set, streaming out (204) the compiled data to the respective BB entity (121 , 122, 123) in the second set of RAN entities, receiving (206) a configuration request from a BB entity in the second set of RAN entities based on the streamed out compiled data, which configuration request requests configurations of connections between the respective one or more radio entities (111 , 112, 113, 114) and one or more BB entities (121 , 122, 123) in the second set, configuring (207) the respective connection according to the received configuration request, streaming out (208) to a computer (140) connected to the transport node (130) and the respective BB entity in the second set of RAN entities configuration information about the requested configured connections,2. The method according to claim 1 , wherein the further entity (114, 123, 150) is represented by a network connection node (150), the method further comprising: when identified that a network connection node (150), for the local DRAN site (105) is available for connection to the wireless communications network (100), initiating (209) a permanent network connectivity.

3. The method according to any of the claims 1-2, wherein any one out of:the notifying (202) further comprises notifying a network connection node (150) that a further entity (114, 123, 150) is connected to the local DRAN site (105), the compiling (203) of the data further comprises compiling data related to and received from a network connection node (150), the streaming out (204) of the compiled data further is streamed out to the network connection node (150), the method further comprises periodically announcing (205) to a computer (140) connected to the transport node (130) and the respective BB entity in the second set of RAN entities, a temporary Internet Protocol, IP, address, the periodically announcing (205) a temporary Internet Protocol, IP, address, further is announced to the network connection node (150), the configuration request from the BB entity in the second set of RAN entities further requests configurations of connections between the network connection node (150) and the one or more BB entities (121 , 122, 123) in the second set, and the configuration information about the requested configured connections, further is streaming out (208) to the network connection node (150).

4. The method according to any of the claims 1-3, wherein the further entity (114, 123,150) is represented by any one or more out of a radio entity, a BB entity, and a network connection node (150).

5. The method according to any of the claims 1-4, further comprising: configuring (201) connections between the respective one or more radio entities (111 , 112, 113) and the respective one or more Baseband, BB, entities (121 , 122).

6. A computer program (830) comprising instructions, which when executed by a processor (810), causes the processor (810) to perform actions according to any of the claims 1-5.

7. A carrier (840) comprising the computer program (830) of claim 6, wherein the carrier (840) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

8. A transport node (130) configured to configure connections in a local Distributed Radio Access Network, DRAN, site (105) for a wireless communications network (100), wherein the local DRAN site (105) is adapted to comprise the transport node (130) and a first set of Radio Access Network, RAN, entities, which first set of RAN entities is adapted to comprise one or more radio entities (111 , 112, 113) and one or more Baseband, BB, entities (121 , 122) between which connections has been configured, the transport node (130) further configured to: notify the respective RAN entity in the first set of RAN entities, that a further entity (114, 123, 150) is adapted to be connected to the local DRAN site (105), compile data related to and received from the respective RAN entity in a second set of RAN entities adapted to comprise the further entity (114, 123, 150) and the RAN entities in the first set, stream out the compiled data to the respective BB entity (121 , 122, 123) in the second set of RAN entities, receive a configuration request from a BB entity in the second set of RAN entities based on the streamed out compiled data, which configuration request is adapted to request configurations of connections between the respective one or more radio entities (111 , 112, 113, 114) and one or more BB entities (121 , 122, 123) in the second set, configure the respective connection according to the received configuration request, stream out to a computer (140) connected to the transport node (130) and the respective BB entity in the second set of RAN entities configuration information about the requested configured connections.

9. The transport node (130) according to claim 8, wherein the further entity (114, 123,150) is adapted to be represented by a network connection node (150), the transport node (130) further being configured to: when identified that a network connection node (150), for the local DRAN site (105) is available for connection to the wireless communications network (100), initiate a permanent network connectivity.

10. The transport node (130) according to any of the claims 8-9, wherein any one out of:the transport node (130) configured to notify, is further configured to notify a network connection node (150), that a further entity (114, 123, 150) is connected to the local DRAN site (105), the transport node (130) configured to compile the data is further configured to compile data related to and received from a network connection node (150), the transport node (130) configured to stream out the compiled data is further configured to stream out to the network connection node (150), the transport node (130) further is configured to periodically announce to a computer (140) connected to the transport node (130) and the respective BB entity in the second set of RAN entities, a temporary Internet Protocol, IP, address, the transport node (130) configured to periodically announce a temporary Internet Protocol, IP, address, is further configured to announce to the network connection node (150) the configuration request from the BB entity in the second set of RAN entities is further adapted to request configurations of connections between the network connection node (150), and the one or more BB entities (121 , 122, 123) in the second set, and the configuration information about the requested configured connections, is further adapted to stream out to the network connection node (150).11 . The transport node (130) according to any of the claims 8-10, wherein the further entity (114, 123, 150) is adapted to be represented by any one or more out of a radio entity, a BB entity, and a network connection node (150):

12. The transport node (130) according to any of the claims 8-10, further being configured to: configure connections between the respective one or more radio entities (111 , 112, 113) and the respective one or more Baseband, BB, entities (121 , 122).

Images