Remote management of antenna line device in a network

Abstract

Disclosed herein is an apparatus (114) configured to assign an address to each of one or more Antenna Line Devices (ALDs) (202) in a network. Further, the apparatus (114) is configured to obtain a configuration data associated with the one or more ALDs (202). Furthermore, the apparatus (114) is configured to perform one or more operations on the one or more ALDs (202) based on the obtained configuration data and the assigned addresses, wherein the one or more operations corresponds to a remote management of the one or more ALDs (202). Further, the remote management of the one or more ALDs (202) comprises at least one of a software management and hardware reconfiguration of the one or more ALDs (202).

Description

REMOTE MANAGEMENT OF ANTENNA LINE DEVICE IN A NETWORKCROSS REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims priority based on India Patent Application No. 202411065656. filed August 30, 2024 in the Indian Patent Office, the entire disclosure of which is incorporated herein by reference.TECHNICAL FIELD

[0002] The present disclosure relates to the remote management of Antenna Line Devices (ALDs) in a network.BACKGROUND

[0003] The information disclosed in this background section is only for the enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information fonns the prior art already- known to a person skilled in the art.

[0004] In a communication system, there is transmission and reception of signals between one or more User Equipment (UE) and the associated base station. In the communication system, a base station usually includes a transceiver and an antenna connected by a feeder. The signals transmitted by a UE are in the form of electromagnetic waves. The power associated with the signals transmitted by the UE is low. Therefore, the transmitted signals are amplified to ensure reception at the base station. Antenna Line Devices (ALDs) collectively refer to one or more devices connected in a path between the UE and the base station to amplify the signals forreception at the base station. The ALDs may include Remote Electrical Tilt (RET) antennas, signal boosters, and Voltage Standing Wave Ratio (VSWR) measuring units.

[0005] ALD monitoring and management are necessary for providing uninterrupted network services to the end users. The ALD monitoring may require handling faults at an ALD. In the existing techniques, the fault monitoring and management of the ALDs is usually performed manually through site visits. The manual process for fault monitoring and resolution is tedious and expensive.

[0006] Thus, there is a need to provide a methodology to overcome the above-mentioned issues in the conventional techniques.SUMMARY

[0007] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the disclosure nor is it intended to determine the scope of the disclosure.

[0008] According to one embodiment of the present disclosure, an apparatus is disclosed. The apparatus is configured to assign an address to each of one or more Antenna Line Devices (ALDs) in a network. Further, the apparatus is configured to obtain a configuration data associated with the one or more ALDs. Furthermore, the apparatus is configured to perform one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses. The one or more operations correspond to a remote management of the one or more ALDs.

[0009] According to one embodiment of the present disclosure, a method is disclosed. The method includes assigning an address to each of one or more Antenna Line Devices (ALDs) in a network. Further, the method includes obtaining configuration data associated with the one or more ALDs. Furthermore, the method includes performing one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses. The one or more operations correspond to a remote management of the one or more ALDs.

[0010] According to another embodiment of the present disclosure, a non-transitory computer- readable medium is disclosed. The non-transitory computer-readable medium stores instructions. The instructions comprise one or more instructions that are executed by a Distributed Unit (DU). The DU comprises one or more processors. The one or more instructions cause the one or more processors to assign an address to each of one or more Antenna Line Devices (ALDs) in a network. Further, the one or more instructions cause the one or more processors to obtain a configuration data associated with the one or more ALDs. Furthermore, the one or more instructions cause the one or more processors to perform one or more operations on the one or more ALDs based on the obtained data and the assigned addresses. The one or more operations correspond to a remote management of the one or more ALDs.

[0011] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawing. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting its scope. The disclosure will be described and explained with additional specificity7and detail with the accompanying drawings.BRIEF DESCRIPTION OF FIGURES

[0012] Features, aspects, and advantages of certain example embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:Figure 1 illustrates an example block diagram of a communication environment depicting an Open Radio Access Network (O-RAN) architecture, in accordance with an embodiment of the present disclosure;Figures 2A-2B illustrate a signalling flow diagram associated with remote management of the one or more ALDs by the DU, in accordance with an embodiment of the present disclosure;Figures 3A-3B illustrate a signalling flow diagram associated with applying ALD configuration to the one or more ALDs in the network, in accordance with an embodiment of the present disclosure;Figures 4A-4B illustrate a signalling flow associated with software management for the one or more ALDs, in accordance with an embodiment of the present disclosure;Figures 5A-5B illustrate a signalling flow associated with hardw are reconfiguration for the one or more ALDs, in accordance with an embodiment of the present disclosureFigure 6 illustrates a process flow' depicting a method for implementing remote management of one or more ALDs by the DU, in accordance with an embodiment of the present disclosure; andFigure 7 illustrates an example embodiment of a device, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0013] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from the practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, it is understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part), and the order of one or more operations may be switched, as long as these modifications may not affect the resulting scope of the invention.

[0014] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting to the implementations. Thus, the operation and behaviour of the systems and / or methods were described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0015] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possibleimplementations includes each dependent claim in combination with every other claim in the claim set.

[0016] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more / ’ Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B]”, “[A] and / or [B]”, or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0017] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from the practice of the implementations.

[0018] The present disclosure provides a method for connecting one or more ALDs in a network with an ALD controller. The ALD controller sets an initial configuration of the one or more ALDs and stores device data associated with the one or more ALDs. The present disclosure allows remote management of the one or more ALDs. The remote management may be associated with fault monitoring at the one or more ALDs. The remote management may be further associated with software management and hardware reconfiguration of the one or more ALDs. The present disclosure further provides for the initial configuration of ALDs (e.g. a newly provisioned ALD) using a configuration dataset.

[0019] Now example embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings.

[0020] Figure 1 illustrates an example block diagram of a communication environment depicting an Open Radio Access Network (O-RAN) architecture 100. in accordance with an embodiment of the present disclosure. The architecture illustrated is exemplary and nonlimiting. The present disclosure is applicable to communication networks with ALDs. In an embodiment of the present disclosure, the apparatus may correspond to an ALD controller. In an example, the ALD controller may correspond to a Distributed Unit (DU) in a network.

[0021] In Figure 1, a Service Management and Orchestration Framework (SMO) 102 provides data services to the network functions. The SMO 102 allows managed network functions to interoperate and communicate within the O-RAN. The SMO 102 connects to and manages RAN Intelligent Controllers (RICs) 104 and 106, an O-Cloud 118, an O-RAN Central Unit (O-CU), and an O-RAN Distributed Unit (O-DU) 114.

[0022] The RICs may include a non-real-time RIC 104 and near-real-time RIC 106. The RICs are logical functions for controlling and optimizing the elements and resources of an O-RAN. A near-real-time RIC 106 controls and optimizes elements and resources with granular data collection. The interfaces connecting the different components of the O-RAN architecture are not illustrated for the sake of clarity.

[0023] The O-Cloud 118 is a cloud computing platform made up of the physical infrastructure nodes using the O-RAN architecture. The O-Cloud 118 creates and hosts various virtual network functions (VNFs) used by the RICs and other infrastructure elements.

[0024] The O-CU is a logical node that hosts network protocols such as the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol(PDCP). The O-CU may be further disaggregated into an O-CU-CP 110 corresponds to the O- RAN control unit for the control plane, and an O-CU-UP 112 corresponds to the O-RAN control unit for the user plane.

[0025] The 0-DU 114 (also referred to as DU 114) is a logical node that hosts network protocols such as the radio link control (RLC) protocol, medium access control (MAC) protocol, and the physical interface (PHY).

[0026] The O-RAN Radio Unit (0-RU) 116 processes radio frequencies received by the physical layer of the network. The processed radio frequencies are sent to the 0-DU 114 through a front-haul interface.

[0027] The present disclosure in some of the non-limiting embodiments illustrates the SMO 102 as the network entity controlling the DU 114. The functions of the SMO 102 may be performed by another Core Network (CN) entity in some embodiments as obvious to a person skilled in the art.

[0028] The O-RU 116 may be connected to one or more Antenna Tine Devices (ALDs). The AUD is a generic term for an addressable physical device, such as an antenna drive or amplifier. In an example, the ALD may correspond to a Remote Electrical Tilt (RET) antennas, signal boosters, Voltage Standing Wave Ratio (VSWR) measuring units, and the like. In an example, the one or more ALDs in the network may be connected with the RU 116 via an RS485 connection.

[0029] As used in the present disclosure, inventory' refers to the device information of the ALD 202 obtained by query ing the ALDs in the network. Further, inventory management refers to reconnecting the ALD 202 and DU 114 using the stored inventory'.

[0030] As used in the present disclosure, polling refers to a transmission of an AISG elementary procedure request signal to maintain the connection between the DU 114 and the one or more ALDs 202. The detection of a disconnect between the DU 114 and the ALD 202 is based on a failure response to the transmitted AISG elementary procedure request signal.

[0031] As used in the present disclosure, the term '“discovery or scan” is associated with a procedure performed to detect the ALDs in the network by the ALD controller.

[0032] As used in the present disclosure, the term "software management” is associated with identifying and updating software or an application program installed on each of the one or more ALDs.

[0033] As used in the present disclosure, the term "hardware reconfiguration” is associated with reconfiguring the hardware components (e.g. RETs) based on a hardware reconfiguration request from a core network entity (e.g., SMO).

[0034] Figures 2A-2B illustrate a signalling flow diagram 200 associated with remote management of one or more ALDs 202 by the DU 114, in accordance with an embodiment of the present disclosure.

[0035] Figure 2A illustrates a discovery (or scan) procedure to establish an initial connection between the DU and the one or more ALDs 202 in the network. The Figure 2A further illustrates obtaining device data associated with the one or more ALDs 202 after establishing the initial connection.

[0036] At step 210, the SMO 102 transmits a radio configuration message to the DU 114. Further at step 212, the DU 114 transmits the radio configuration message to the RU 116.

[0037] At step 214, the DU 114 transmits an ALD discovery' (or scan) request to the RU 116. The ALD discovery' request is transmitted in response to the received radio configurationmessage. At step 216, the RU 116 transmits the received ALD discovery request message to the ALD 202. In an example, the ALD discovery request message may include a number of messages such as a scan message, the ALD address assignment message, and a connect message. The messages may be a part of the Antenna Interface Standard Group (AISG) protocol.

[0038] At step 218, each of the one or more ALD 202 responds to the ALD discovery request. The response of the ALD 202 is illustrated as the ALD discovery’ response. Further, at step 220. the ALD discovery response is transmitted by the RU 116 to the DU 114.

[0039] Based on the received ALD discovery responses, the DU 114 establishes a connection with the ALD 202 and the same is illustrated in step 222.

[0040] At step 224, after establishing a connection with the ALD 202, a message may be transmitted by the DU 114 to the ALD 202 depicted as ‘“Get inventory request”. In an example, the “Get inventory request” may correspond to AISG elementary procedures such as GET INFO, GET DEVICE DATA, GET TILT, and the like. At step 226, in response to the “Get inventory request” the ALD 202 may provide the requested device details as a “Get inventory response” message.

[0041] At step 228, the DU 114 may transmit a “set device data request” message to set the device data (e.g., tilt of the ALD) based on the requirement. At step 230, based on the received “set device data request”, the ALD 202 may configure device data of the ALD 202 and share a set device data response message. In an example, the set device data request message may correspond to the AISG elementary’ procedure such as SET DEVICE DATA and SET TILT.

[0042] At step 232, the ALD inventory’ information (or the device data) may be stored at a persistent storage. In an example, the persistent storage may be a part of the architecture of theDU 114. Further at step 234, in case the above-mentioned steps are successful, an ALD discovery notification is transmitted to the SMO 102.

[0043] In an example, the stored information may include a type of the ALD 202, a serial number of the ALD 202. an ALD configuration parameter (e.g., tilt), and the like. In an example, the storage associated with the DU 114 may be a persistent storage unit. The persistent storage unit retains data after power to the storage unit is turned OFF. The device information (or device data) may include an ALD identifier, the device type (e.g. single RET, multi-RET. and the like), a device serial number, and device configuration parameters for each of the one or more ALDs 202 in the network. The device configuration parameters may include parameters such as an ALD tilt, a vendor code, hardware and software versions associated with the ALD 202, device calibration status, and the like.

[0044] Figure 2B is associated with fault monitoring and performing one or more AISG elementary procedures for handling the ALD 202. In one embodiment, the DU 114 may also be referred to as an ALD controller 114. The ALD controller 114 performs fault monitoring and remote management of the ALDs 202.

[0045] At step 236, the DU 114 validates the ALD information (or inventory' information) by comparison with the configuration dataset associated with the one or more ALDs 202. In an example, configuration data corresponds to the inventory' information (or device data) stored at the persistent storage of DU 114. In the example, the configuration data stored at the DU is stored as a configuration dataset. The configuration dataset is determined based on the obtained configuration data in a prior scan procedure.

[0046] The configuration dataset may be used to perform initial configuration (or whitelisting) of the one or more ALDs after a successful discovery' (or scan) procedure. The configurationdataset may also be used to perform the initial configuration of a newly provisioned ALD 202.The configuration dataset therefore reduces the requirement of redundant information in the obtained configuration data. In an example, the inventory information required from the ALDs 202 in a subsequent discovery or scan procedure is reduced.

[0047] At step 238. the DU 114 may raise a notification on an identification of an inconsistency between the device data for an ALD 202 and the configuration dataset.

[0048] At loop 240, the DU 114 may continuously perform ALD fault monitoring. In one embodiment, the DU 114 may handle a fault (e.g.. an ALD disconnected from the DU) and performs the AISG elementary’ procedures for remote management and resolution of the fault at the ALD 202, as illustrated by step 242. In an example, the fault may be associated with a mismatch between device information for an ALD 202 and the configuration dataset.

[0049] Figures 3A-3B illustrate a signalling flow diagram 300 associated with applying the ALD configuration data to the one or more ALDs 202 in the network, in accordance with an embodiment of the present disclosure.

[0050] Figure 3A illustrates a discovery' (or scan) procedure to establish the connection between the DU 114 and the one or more ALDs 202 in the network. The initial configuration (or whitelisting) is performed using the configuration dataset. The Figure 3A further illustrates obtaining device data associated with the one or more ALDs 202 after establishing the connection.

[0051] At step 310, the SMO 102 transmits a radio configuration to the DU 114. At step 312, the DU 114 transmits the radio configuration to the RU 116. The radio configuration from the DU 114 includes the configuration dataset as the predefined ALD template configuration.

[0052] At loop 314, the DU 1 14 automatically performs the initial configuration (or whitelisting) of the one or more ALDs discovered using the scan procedure. The initial configuration or whitelisting is performed using the configuration dataset.

[0053] At step 316, the DU 1 14 applies the configuration associated with the configuration dataset to an ALD 202. The ALD 202 may have been discovered in a previous scan procedure. In an example, the ALD 202 may correspond to a newly provisioned ALD. The application of the configuration dataset to perform an initial configuration (whitelisting) of newly provisioned ALD 202 saves signalling and computation for the DU 114.

[0054] The steps 318 to 334 are associated with discovery (or scan procedure) and obtaining device data from the one or more ALDs 202 in the network. The steps 318 to 334 are identical to the corresponding steps 214 to 230 in Figure 2A. Therefore, the explanation for the steps 318 to 334 is not repeated and is omitted for the sake of brevity.

[0055] Figure 3B illustrates fault monitoring by the DU 114. The fault monitoring as illustrated in Figure 3B is associated with a detected disconnect between the DU 114 and ALD 202.

[0056] In loop 338, a periodic poll is performed to detect the status of the connection between the DU 114 and the ALD 202. In an embodiment of the present disclosure, a periodic signal (polling) is transmitted to maintain a connection with the one or more ALDs. The periodic signalling is performed after the discovery' of the one or more ALDs using a predefined scan procedure. Further, periodic signalling helps in monitoring the one or more ALDs continuously for the identification of a fault.

[0057] At step 340, the DU 114 starts periodic ALD connection monitoring to ascertain the status of the connection between the ALD 202 and the DU 114.

[0058] At step 342, the DU 1 14 sends the AISG elementary procedure request to the ALD 202.In an example, the elementary procedure request may correspond to a ‘GET ALARM STATUS Requesf’. At step 344, an AISG elementary procedure success response may be received by the DU 114. The AISG procedure success response indicates a connection between the DU 114 and the ALD 202. Further, the periodic poll process is repeated at regular intervals to ensure continuous connection between the DU 114 and the ALD 202. In an example, the periodic poll may be performed after a duration of 3 minutes. The periodic poll ensures continuous connection and reduces the need for performing the discovery’ procedure.

[0059] In an event, the DU 114 receives a GET ALARM STATUS failure response from an ALD 202, the ALD 202 is identified to be in a disconnected state. The DU performs the ALD fault monitoring and device management as illustrated in step 336.

[0060] In the explanation for Figure 3A-3B, the ALD 202 is illustrated as a single ALD 202. In other embodiments of the present disclosure, the ALD 202 may correspond to one or more ALDs 202 and the steps provided in the explanation may be performed for each of the one or more ALDs 202 in the network.

[0061] Figures 4A-4B illustrate a signalling flow diagram 400 associated with software management for the one or more ALDs 202 in the network, in accordance with an embodiment of the present disclosure.

[0062] Figure 4A illustrates a discovery (or scan) procedure to establish an initial connection between the DU 114 and the one or more ALDs 202 in the network. The figure 4 A further illustrates obtaining device data associated with the one or more ALDs 202 after establishing the initial connection. The steps 410 to 432 are identical to the steps 210 to 232. The explanation for the steps is not repeated and omitted for the sake of brevity'. Further, at step 434, the DU114 may receive a request associated with a software update of an ALD 202. The request may be transmitted by the SMO 102. The illustration is non-limiting, and the request may be from another northbound entity in the network. In an example, the request may be obtained from Operations Support System (OSS), Element Management System (EMS), and the like.

[0063] Figure 4B illustrates a signalling flow associated with software management to identify a requirement for updating the application program installed on the one or more ALDs 202. The application program may be updated to a desired version based on an identified requirement for update.

[0064] At step 436, the DU 114 perfonns a software version check for an application program. The application program is installed on an ALD 202 in the network. The software version is compared with a desired version of the application program. On identification of a mismatch between the installed version and the desired version of the application program, the software update may be performed for the application program. In an example, the software version installed on the ALD 202 is identified based on the obtained device data (or configuration data) for the ALD 202. In another example, the software version installed on the ALD 202 is identified based on the data in the configuration dataset.

[0065] At step 438, the DU 114 triggers the AISG elementary procedure for ALD software download of the application program. In an example, the desired software version is downloaded from a remote server associated with the DU 114. The downloaded desired software version of the application program may be stored at the DU 114. The ALD 202 updates the softw are version of the application program to the desired version.

[0066] At step 440, the ALD 202 transmits an ALD software update success notification to the DU 114. At step 442, the DU 114 resets the ALD 202.

[0067] Further, at step 444, the DU 1 14 identifies the completion of the software update for the ALD 202. At step 446, the DU sends an AUD software update notification to the SMO 102.

[0068] In the explanation for Figure 4A-4B, the ALD 202 is illustrated as a single ALD 202. In other embodiments of the present disclosure, the ALD 202 may correspond to one or more ALDs 202 and the steps provided in the explanation may be performed for each of the one or more ALDs 202 in the network.

[0069] Figures 5A-5B illustrate a signalling flow diagram 500 associated with hardware reconfiguration for the one or more ALDs 202, in accordance with an embodiment of the present disclosure.

[0070] Figure 5A illustrates a discovery (or scan) procedure to establish an initial connection between the DU 114 and the one or more ALDs 202 in the network. The figure 5 A further illustrates obtaining device data associated with the one or more ALDs 202 after establishing the initial connection. The steps 510 to 532 are identical to the steps 210 to 232. Therefore, the explanation for the steps 510 to 532 is not repeated and is omitted for the sake of brevity.

[0071] Further, at step 534, the DU 114 may receive a request associated with the hardware reconfiguration of an ALD 202. The request may be transmitted by the SMO 102. The illustration is non-limiting, and the request may be from another northbound entity in the network. In an example, the request may be obtained from Operations Support System (OSS), Element Management System (EMS), and the like.

[0072] Figure 5B illustrates the signalling flow associated with hardware reconfiguration for one or more ALD 202 in the network.

[0073] At step 536, the DU 114 downloads the requested hardware reconfiguration binary. In an example, the hardware reconfiguration binary details may be downloaded from a remote server associated with the SMO 102.

[0074] At step 538, the DU 114 triggers a send configuration data procedure as per AISG standard elementary procedure. In an example, ’ SEND CONFIG DATA is triggered by the DU 114 to transmit the downloaded hardware reconfiguration details to the ALD 202. The ALD 202 corresponds to an ALD 202 with requested hardware reconfiguration. In an example, the request may initiate from an end user and is further transmitted by SMO 102 to DU 114.

[0075] At step 540, the ALD hardware reconfiguration is successfully completed. The ALD 202 transmits an ALD configuration update success notification to the DU 114.

[0076] Further, at step 542, the DU 114 identifies the completion of the hardware reconfiguration for the ALD 202. At step 544, the DU sends an ALD hardware reconfiguration notification to the SMO 102. In an example, the hardware configuration may include a beam tilt position of an antenna, an operating mode of the Remote Electrical Tilting (RET) device, and a runtime modification in the hardware configuration of the one or more ALDs.

[0077] In the explanation for Figure 5A-5B, the ALD 202 is illustrated as a single ALD 202. In other embodiments of the present disclosure, the ALD 202 may correspond to one or more ALDs 202 and the steps provided in the explanation may be performed for each of the one or more ALDs 202 in the network.

[0078] Figure 6 illustrates a process flow depicting a method 600 for implementing remote management of one or more ALDs 202 by the DU 114, in accordance with an embodiment of the present disclosure.

[0079] At step 602, the method 600 includes assigning an address to each of one or moreAntenna Line Devices (ALDs) in a network. In an example, addresses are assigned to each of the one or more ALDs on successful discovery (or scan) procedures for the ALD. In another example, on successful M-plane connectivity between DU and RU, a High-Level Data Link Control (HDLC) bus scan may be performed. Further. HDLC addresses may be assigned to the discovered ALDs.

[0080] At step 604, the method 600 includes obtaining configuration data associated with the one or more ALDs. In an example, the configuration data may correspond to the ALD device data (or device information). The configuration data from prior scan procedures may be stored as a dataset to provide a configuration dataset. The device infonnation (or device data) may include, but is not limited to, an ALD identifier, the device type (e.g. single RET, multi-RET, and the like), a device serial number, and device configuration parameters for each of the one or more ALDs 202 in the network.

[0081] At step 606, the method 600 includes performing one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses. The one or more operations correspond to the remote management of the one or more ALDs.

[0082] In an embodiment, the remote management of the one or more ALDs comprises at least one of software management and hardware reconfiguration of the one or more ALDs. Further, remote management may include fault monitoring and handling a fault at the one or more ALDs. In the embodiment, the one or more operations on the one or more ALDs are performed using a communication protocol comprising at least one of an Antenna Interface Standard Group (AISG) elementary7protocol and a High-level Data Link Control (HDLC) protocol

[0083] In the embodiment, after obtaining the configuration data associated with the one or more ALDs, the method 600 includes modifying a configuration of the one or more ALDs using a configuration dataset. The configuration dataset is applied uniformly to the one or more ALDs. In the embodiment, the method 600 includes performing an initial configuration of a replacement or newly provisioned ALD using the configuration dataset. In an example, the configuration dataset is determined based on the obtained configuration data in a prior scan procedure to reduce the requirement of redundant information in the obtained configuration data.

[0084] In an embodiment, the method 600 includes determining a version of an application program installed on each of the one or more ALDs based on the obtained configuration data. The method 600 further includes updating the version of the application program of each of the one or more ALDs based on a comparison of the determined version with a desired version of the application program. The method 600 further includes resetting each of the one or more ALDs for which the version of the application program is updated.

[0085] In an embodiment, the method 600 includes receiving a request from a core network entity to reconfigure hardware configuration on the one or more ALDs. The method 600 includes obtaining reconfiguration data corresponding to the received request. The method 600 includes reconfiguring the hardware configuration based on the obtained reconfiguration data. In the embodiment, the hardware reconfiguration includes a beam tilt position of an antenna, an operating mode of the Remote Electrical Tilting (RET) device, and a runtime modification in the hardware configuration of the one or more ALDs.

[0086] In an embodiment, the method 600 includes transmitting a periodic signal to maintain a connection with the one or more ALDs after the discovery of the one or more ALDs using apredefined scan procedure. Further, the method 600 includes monitoring the one or more ALDs continuously for the identification of a fault.

[0087] The steps of the method flow and the embodiments of the disclosure have been explained with the description for Figures 2A-2B. Figures 3A-3B, Figures 4A-4B, and Figures 5A-5B. The description has not been repeated for the sake of brevity.

[0088] While the above-discussed steps in Figure 6 are shown and described in a particular sequence, the steps may occur in variations to the sequence in accordance with various exemplary embodiments.

[0089] Further, the present disclosure also describes non-transitory computer program products (i.e., physically embodied computer program products) or non-transitory computer-readable mediums encoded with executable instructions that store instructions. The executable instructions, when executed by one or more processors cause the one or more processors to perform as the methods as described in the present disclosure, as elaborated in the preceding paragraphs. Examples of computer-readable mediums include non-volatile, hard-coded type mediums such as read-only memories (ROMs) or erasable, electrically programmable readonly memories (EEPROMs), and user-recordable type mediums such as floppy disks, hard disk drives and compact disk read-only memories (CD-ROMs) or digital versatile disks (DVDs).

[0090] Figure 7 illustrates an example embodiment of a device 700 associated with apparatus or the DU 114 and / or the ALD 202. As shown in Figure 7, the device 700 includes a processor 710, a memory 720, a storage component 730, an input component 740, an output component 750, a communication interface 760, and a bus 770.

[0091] The processor 710, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 710 may be embodied as amulti-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 710 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0092] The memory 720 includes a non-transitory computer readable medium. The memory 720 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g.. a flash memory, a magnetic memory, and / or an optical memory ) that stores information and / or instructions for use by the processor 710. The memory 720 comprises machine-readable instructions which are executable by the processor 710. These machine-readable instructions when executed by the processor 710 cause the processor 710 to perform one or more method steps of an example embodiment described in the present disclosure.

[0093] The storage component 730 stores information and / or software related to the operation and use of the device 700. For example, the storage component 730 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another ty pe of non-transitory7computer-readable medium, along with a corresponding drive.

[0094] The input component 740 is configured to receive information, such as user input. For example, the input component 740 may include, but not be limited to, a touchscreen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 740 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gy roscope, and / or an actuator).

[0095] The output component 750 is configured to provide output information from the device700. For example, the output component 750 may be, but not limited to, a display, a speaker, instructions to an external device, and / or one or more light-emitting diodes (LEDs).

[0096] The communication interface 760 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 760 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 700 and other devices. In other words, the standard of the communication interface 760 is not limited.

[0097] The bus 770 acts as an interconnect between the processor 710, the memory’ 720, the storage component 730, the input component 740, the output component 750. and the communication interface 760 of the device 700. The bus 770 may include a wired interconnection or a wireless interconnection.

[0098] The number and arrangement of components shown in Figure 7 are provided as an example. In practice, the device 700 may include additional components, fewer components, different components, or differently arranged components than those shown in Figure 7. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 700 may perform one or more functions described as being performed by another set of components of the device 700. Further, one or more method steps described in any of the exemplary’ embodiments may be performed utilizing a plurality' of devices 700 in communication with one another.

[0099] An apparatus configured to assign an address to each of one or more Antenna Line Devices (ALDs) in a network. The apparatus is further configured to obtain a configuration dataassociated with the one or more ALDs. The apparatus is further configured to perform one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses. The one or more operations correspond to a remote management of the one or more ALDs.

[0100] The apparatus as described in

[0098] , wherein the remote management of the one or more ALDs comprises at least one of a software management and hardware reconfiguration of the one or more ALDs.

[0101] The apparatus as described in any of

[0098] to

[0099] . wherein the apparatus is configured to modify a configuration of the one or more ALDs using a configuration dataset. The configuration of the one or more ALDs is modified after obtaining the configuration data associated with the one or more ALDs. Further, the configuration dataset is applied uniformly to the one or more ALDs.

[0102] The apparatus as described in any of

[0098] to

[0100] , wherein the apparatus is configured to perform an initial configuration of a replacement or newly provisioned ALD using the configuration dataset.

[0103] The apparatus as described in any of

[0098] to

[0101] , wherein the configuration dataset is determined based on the obtained configuration data in a prior scan procedure to reduce the requirement of redundant information in the obtained configuration data.

[0104] The apparatus as described in any of

[0098] to

[0102] , wherein the apparatus is configured to determine a version of an application program installed on each of the one or more ALDs. The version of the application program installed is determined based on the obtained configuration data. Further, the apparatus is configured to update the version of the application program of each of the one or more ALDs. The version of the application programis updated based on a comparison of the determined version with the desired version of the application program. The apparatus is further configured to reset each of the one or more ALDs for which the version of the application program is updated.

[0105] The apparatus as described in any of

[0098] to

[0103] , wherein the apparatus is configured to receive a request from a core network entity to reconfigure hardware configuration on the one or more ALDs. The apparatus is further configured to obtain a reconfiguration data corresponding to the received request. The apparatus is further configured to reconfigure the hardware configuration based on the obtained reconfiguration data.

[0106] The apparatus as described in any of

[0098] to

[0104] , wherein the hardware configuration comprises a beam tilt position of an antenna, an operating mode of the Remote Electrical Tilting (RET) device, a runtime modification in the hardware configuration of the one or more ALDs.

[0107] The apparatus as described in any of

[0098] to

[0105] , wherein the apparatus is configured to transmit a periodic signal to maintain a connection with the one or more ALDs. The periodic signal is transmitted after the discovery of the one or more ALDs using a predefined scan procedure. The apparatus is further configured to monitor the one or more ALDs continuously for the identification of a fault.

[0108] The apparatus as described in any of

[0098] to

[0106] , wherein the one or more operations on the one or more ALDs is performed using a communication protocol. The communication protocol comprises at least one of an Antenna Interface Standard Group (AISG) elementary7protocol and a High-level Data Link Control (HDLC) protocol.

[0109] The apparatus as described in any of

[0098] to

[0107] , wherein the apparatus corresponds to a Distributed Unit (DU) in the network.

[0110] A method comprises assigning an address to each of one or more Antenna Line Devices(ALDs) in a network. The method comprises obtaining configuration data associated with the one or more ALDs. The method further comprises performing one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses. The one or more operations corresponds to a remote management of the one or more ALDs.

[0111] The method as described in

[0109] . wherein the remote management of the one or more ALDs comprises at least one of a software management and hardware reconfiguration of the one or more ALDs.

[0112] The method as described in any of

[0109] to

[0110] , wherein the method comprises modifying a configuration of the one or more ALDs using a configuration dataset. The configuration of the one or more ALDs is modified after obtaining the configuration data associated with the one or more ALDs. Further, the configuration dataset is applied uniformly to the one or more ALDs.

[0113] The method as described in any of

[0109] to

[0111] , wherein the method comprises performing an initial configuration of a replacement or newly provisioned ALD using the configuration dataset.

[0114] The method as described in any of

[0109] to

[0112] , wherein the configuration dataset is determined based on the obtained configuration data in a prior scan procedure to reduce the requirement of redundant information in the obtained configuration data.

[0115] The method as described in any of

[0109] to

[0113] , wherein the method comprises determining a version of an application program installed on each of the one or more ALDs. The version of the application program installed is determined based on the obtained configuration data. The method further comprises updating the version of the applicationprogram of each of the one or more ALDs based on a comparison of the determined version with a desired version of the application program. The method further comprises resetting each of the one or more ALDs for which the version of the application program is updated.

[0116] The method as described in any of

[0109] to

[0114] , wherein the method comprises receiving a request from a core network entity to reconfigure hardware configuration on the one or more ALDs. The method further comprises obtaining a reconfiguration data corresponding to the received request. The method further comprises reconfiguring the hardware configuration based on the obtained reconfiguration data.

[0117] The method as described in any of

[0109] to

[0115] , wherein the hardware configuration comprises a beam tilt position of an antenna, an operating mode of the Remote Electrical Tilting (RET) device, a runtime modification in the hardware configuration of the one or more ALDs.

[0118] The method as described in any of

[0109] to

[0116] , wherein the method comprises transmitting a periodic signal to maintain a connection with the one or more ALDs. The periodic signal is transmitted after the discovery' of the one or more ALDs using a predefined scan procedure. The method further comprises monitoring the one or more ALDs continuously for identification of a fault.

[0119] The method as described in any of

[0109] to

[0117] , wherein the one or more operations on the one or more ALDs are performed using a communication protocol comprising at least one of an Antenna Interface Standard Group (AISG) elementary protocol and a High- level Data Link Control (HDLC) protocol.

[0120] A non-transitory computer-readable medium storing instructions, the instructions comprising one or more instructions that, when executed by a Distributed Unit (DU) in thenetwork comprising one or more processors, cause the one or more processors to assign an address to each of one or more Antenna Line Devices (ALDs) in a network. Further, the instructions when executed cause the processor to obtain a configuration data associated with the one or more ALDs. Further, the instructions when executed cause the processor to perform one or more operations on the one or more ALDs based on the obtained data and the assigned addresses. The one or more operations correspond to a remote management of the one or more ALDs.

[0121] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware devices and software modules.

[0122] It is understood that terms including “unit” or “module” at the end may refer to the unit for processing at least one function or operation and may be implemented in hardware, software, or a combination of hardware and software.

[0123] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0124] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to anotherembodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

[0125] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not. such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

[0126] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

[0127] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments, ft is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that theembodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

We claim:

1. An apparatus configured to: assign an address to each of one or more Antenna Line Devices (ALDs) in a network; obtain a configuration data associated with the one or more ALDs; and perform one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses, wherein the one or more operations corresponds to a remote management of the one or more ALDs.

2. The apparatus of claim 1, wherein the remote management of the one or more ALDs comprises at least one of a software management and hardware reconfiguration of the one or more ALDs.

3. The apparatus of claim 1, wherein after obtaining the configuration data associated with the one or more ALDs, the apparatus is configured to: modify a configuration of the one or more ALDs using a configuration dataset, wherein the configuration dataset is applied uniformly to the one or more ALDs.

4. The apparatus of claim 3, wherein the apparatus is configured to: perform an initial configuration of a replacement or newly provisioned ALD using the configuration dataset, further wherein the configuration dataset is determined based on the obtained configuration data in a prior scan procedure.

5. The apparatus of claim 1, wherein the apparatus is configured to: determine a version of an application program installed on each of the one or more ALDs based on the obtained configuration data; update the version of the application program of each of the one or more ALDs based on a comparison of the determined version with a desired version of the application program; and reset each of the one or more ALDs for which the version of the application program is updated.

6. The apparatus of claim 1, wherein the apparatus is configured to: receive a request from a core network entity to reconfigure hardware configuration on the one or more ALDs; obtain a reconfiguration data corresponding to the received request; and reconfigure the hardware configuration based on the obtained reconfiguration data.

7. The apparatus of claim 6, wherein the hardware configuration comprises a beam tilt position of an antenna, an operating mode of the Remote Electrical Tilting (RET) device, a runtime modification in the hardware configuration of the one or more ALDs.

8. The apparatus of claim 1, wherein the apparatus is configured to: transmit a periodic signal to maintain a connection with the one or more ALDs after the discovery' of the one or more ALDs using a predefined scan procedure; and monitor the one or more ALDs continuously for identification of a fault.

9. The apparatus of claim 1. wherein the one or more operations on the one or more ALDs are performed using a communication protocol comprising at least one of an Antenna Interface Standard Group (AISG) elementary protocol and a High-level Data Link Control (HDLC) protocol.

10. The apparatus of claim 1. wherein the apparatus corresponds to a Distributed Unit (DU) in the network.

11. A method comprising: assigning an address to each of one or more Antenna Line Devices (ALDs) in a network; obtaining configuration data associated with the one or more ALDs; and performing one or more operations on the one or more ALDs based on the obtained configuration data and the assigned addresses, wherein the one or more operations corresponds to a remote management of the one or more ALDs.

12. The method of claim 11, wherein the remote management of the one or more ALDs comprises at least one of a software management and a hardware reconfiguration of the one or more ALDs.

13. The method of claim 11, wherein after obtaining the configuration data associated with the one or more ALDs, the method comprises: modifying a configuration of the one or more ALDs using a configuration dataset, wherein the configuration dataset is applied uniformly to the one or more ALDs.

14. The method of claim 13, wherein the method comprises: performing an initial configuration of a replacement or newly provisioned ALD using the configuration dataset, further wherein the configuration dataset is determined based on the obtained configuration data in a prior scan procedure.

15. The method of claim 11, wherein the method comprises: determining a version of an application program installed on each of the one or more ALDs based on the obtained configuration data; updating the version of the application program of each of the one or more ALDs based on comparison of the determined version with a desired version of the application program; and resetting each of the one or more ALDs for which the version of the application program is updated.

16. The method of claim 11, wherein the method comprises: receiving a request from a core network entity to reconfigure hardware configuration on the one or more ALDs; obtaining a reconfiguration data corresponding to the received request; and reconfiguring the hardw are configuration based on the obtained reconfiguration data.

17. The method of claim 16, wherein the hardware configuration comprises a beam tilt position of an antenna, an operating mode of the Remote Electrical Tilting (RET) device, a runtime modification in the hardw are configuration of the one or more ALDs.

18. The method of claim 11. wherein the method comprises: transmitting a periodic signal to maintain a connection with the one or more ALDs after the discovery of the one or more ALDs using a predefined scan procedure; and monitoring the one or more ALDs continuously for identification of a fault.

19. The method of claim 11, wherein the one or more operations on the one or more ALDs are performed using a communication protocol comprising at least one of an Antenna Interface Standard Group (AISG) elementary protocol and a High-level Data Link Control (HDLC) protocol.

20. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by a Distributed Unit (DU) in the network comprising one or more processors, cause the one or more processors to: assign an address to each of one or more Antenna Line Devices (ALDs) in a network; obtain a configuration data associated with the one or more ALDs; and perform one or more operations on the one or more ALDs based on the obtained data and the assigned addresses, wherein the one or more operations corresponds to a remote management of the one or more ALDs.

Images