FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR DETERMINING BEAM PROFILE CONFIGURATION OF NETWORK NODE IN WIRELESS COMMUNICATION
SYSTEM”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

5 METHOD AND SYSTEM FOR DETERMINING BEAM PROFILE
CONFIGURATION OF NETWORK NODE IN WIRELESS COMMUNICATION
SYSTEM
FIELD OF THE INVENTION
10
[0001] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to methods and systems for determining beam profile configuration of a network node in a radio access network (RAN).
15
BACKGROUND
[0002] The following description of related art is intended to provide background
information pertaining to the field of the disclosure. This section may include certain
20 aspects of the art that may be related to various features of the present disclosure. However,
it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few
25 decades, with each generation bringing significant improvements and advancements. The
first generation of wireless communication technology was based on analog technology
and offered only voice services. However, with the advent of the second generation (2G)
technology, digital communication and data services became possible, and text messaging
was introduced. The third generation (3G) technology marked the introduction of high-
30 speed internet access, mobile video calling, and location-based services. The fourth
generation (4G) technology revolutionized wireless communication with faster data
speeds, better network coverage, and improved security. Currently, the fifth generation
(5G) technology is being deployed, promising even faster data speeds, low latency, and the
ability to connect multiple devices simultaneously. With each generation, wireless
35 communication technology has become more advanced, sophisticated, and capable of
delivering more services to its users.
2

5 [0004] In general, a wireless communication system includes one or more network nodes,
User Equipment (UEs) and an Access Point (AP) which are configured to transmit and receive signals to one another. The network nodes use directive patterns when transmitting and/or receiving data packets and also cover a desired service area for communication using beam profile configurations technology. Beam profile configuration technology in network
10 communications refers to the technique of directing wireless signals toward specific
devices or areas. This is achieved by adjusting the phase and amplitude of signals transmitted by multiple antennas, creating a focused beam of radio frequency energy. Beam profile configuration plays a crucial role in network infrastructure deployment, in scenarios where high-speed, reliable, and efficient wireless communication is required. Beam profile
15 configuration allows for the concentration of signal in specific directions, resulting in
stronger and more reliable connections to network nodes (or devices). The effectiveness of beam profile configuration depends on several factors, including but not limited to Antenna Array Configuration, Channel Condition, Device Mobility, Network Deployment Environment etc. that impact the effectiveness of beam profile configuration technology
20 and may require customized beam profile configuration strategies. In general, determining
beam profile configuration is a type of radio frequency (RF) management in which a wireless signal is directed toward a specific direction. In the context of a Radio Access Network (RAN), beam profile configuration plays a crucial role in optimizing wireless communication between base stations and user equipment (UEs).
25
[0005] Conventionally, in the existing topologies of the communication networks, depending on the deployment scenario like that of a high-rise building, flat terrain, etc., the static beam profile configurations were used for deploying network nodes (primarily millimeter wave radio) which may be suboptimal after a few days with addition of more
30 user equipment (UEs) or network nodes. In the prior known solutions, the beam profile
configuration being static, was used for all the network nodes in the communication network. Due to this the beam utilization was not happening fully. Often manual beam profile configuration is done that requires more manpower. Further, the power and efficiency of the network nodes are being wasted due to unavailability of the users in the
35 beam range since the beam profile configuration is static. Thus, the serving users were
devoid of a better signal quality.
3

5 [0006] Further, as per the conventional approach, the beam profile configuration i.e.,
number of beams and layers is static for all mm Wave radio (or Radio) deployment based
on the user distribution in a sector. There can be multiple combinations of the beam profile
configuration that can be defined for the mm Wave deployment depending on the radio,
UE; height, horizontal and vertical separation of the customer premises equipment (CPEs).
10 Also, one particular beam profile configuration is not suitable for every sector type and for
each radio deployment. A particular type of beam profile configuration is typically manually pushed by a Network Management Server (NMS) to the radio. With the increase of the CPE in the sector, the particular beam profile configuration may not be suitable.
15 [0007] Hence, in view of these and other existing limitations, there arises an imperative
need to provide an efficient solution to overcome the above-mentioned limitations and to provide a method and system to effectively determine beam profile configuration of network nodes(s) in the communication network.
20 OBJECTS OF THE DISCLOSURE
[0008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
25 [0009] It is an object of the present disclosure to provide a system and a method to
determine beam profile configuration of network node(s) in a communication network (e.g., a radio access network (RAN)).
[0010] It is another object of the present disclosure to allow the RAN nodes to select the
30 appropriate beam profile configuration depending on the customer precise equipment
(CPEs) deployments in the network.
[0011] It is yet another object of the present disclosure to effectively utilize the network
capacity by serving users with a better signal quality without the involvement of human
35 resources for setting beam profile configuration.
4

5 [0012] It is yet another object of the present disclosure to provide automatic beam profile
configuration in the RAN that is adopted as per the user distribution (or deployed CPEs) in the network.
[0013] It is yet another object of the present disclosure to maximize resource utilization
10 by providing an automatic approach of beam profile configuration.
[0014] It is yet another object of the present disclosure to increase the user-received throughput by appropriate beam alignment which helps to improve cell effective throughput. 15
[0015] It is yet another object of the present disclosure to update the beam profile configuration in real time or in a defined time period based on the registration of new users.
SUMMARY
20
[0016] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
25 [0017] The present disclosure relates to a method to determine beam profile configuration
of a network node in a Radio Access Network (RAN). The method comprises receiving, a set of data associated with location and height of one or more deployed Customer Premises Equipment (CPEs), by a centralized repository. The method further comprises analyzing, by an analyzer unit, the set of data to determine at least one beam profile configuration
30 suitable for transmission of data to the one or more deployed CPEs. And the method further
comprises automatically configuring, by a configuration unit, via a Network Management Server (NMS), the network node based on the determined at least one beam profile configuration.
35 [0018] In an exemplary aspect of the present disclosure, in the disclosed method, the at
least one beam profile configuration is determined based on at least one of: a distribution of user(s), a distribution of the one or more deployed CPEs, an identification of a category
5

5 of the one or more deployed CPEs, height of the network node, height of the one or more
deployed CPEs, vertical positioning of the one or more deployed CPEs and horizontal positioning of the one or more deployed CPEs.
[0019] In an exemplary aspect of the present disclosure, in the disclosed method, the at
10 least one beam profile configuration is at least one of: a first beam profile configuration, a
second beam profile configuration, and a third beam profile configuration, wherein the first beam profile configuration, the second beam profile configuration and the third beam profile configuration enable services of the RAN within the coverage area of the network node. 15
[0020] In an exemplary aspect of the present disclosure, in the disclosed method, the first beam profile configuration comprises deploying the network node at lesser elevation compared to the height of the one or more deployed CPEs.
20 [0021] In an exemplary aspect of the present disclosure, in the disclosed method, the
second beam profile configuration comprises deploying the network node at higher elevation compared to the height of the one or more deployed CPEs.
[0022] In an exemplary aspect of the present disclosure, in the disclosed method, the third
25 beam profile configuration comprises deploying the network node to cover the one or more
deployed CPEs at a higher elevation, a lower elevation and a parallel elevation, compared to an existing deployment of the network node.
[0023] In an exemplary aspect of the present disclosure, in the disclosed method, the
30 determining the at least one beam profile configuration suitable for transmission of data to
the one or more CPEs facilitates installation of one or more new CPEs within the coverage area of the network node.
[0024] The present disclosure also relates to a system to determine beam profile
35 configuration of a network node in the RAN. The system comprises a centralized
repository, a storage unit, an analyzer unit and a configuration unit. A network management
server (NMS) is connected to the network node and the system. All units of the system are
6

5 connected to each other. The centralized repository is configured to receive a set of data
associated with location and height of one or more deployed customer premise equipment
(CPEs). It is emphasized that each of the one or more deployed CPEs is within a coverage
area of the network node of the RAN. The analyzer unit is configured to analyze the set of
data to determine at least one beam profile configuration suitable for transmission of data
10 to the one or more deployed of CPEs. The configuration unit is configured to automatically
configure the network node based on the at least one determined beam profile configuration via the NMS.
[0025] The present disclosure also relates to a non-transitory computer readable storage
15 medium storing executable instructions to determine beam profile configuration of a
network node in a radio access network (RAN). The instructions, when executed by one or
more units of a system, enables: receiving, by a centralized repository of the system, a set
of data associated with location and height of the one or more deployed customer premise
equipment (CPEs), wherein each of the one or more deployed CPEs is within a coverage
20 area of the network node of the RAN; analyzing, by an analyzer unit of the system, the set
of data to determine at least one beam profile configuration suitable for transmission of
data to the one or more deployed CPEs; and automatically configuring, by a configuration
unit of the system via a Network Management Server (NMS) of the system, the network
node based on the at least one determined beam profile configuration.
25
BRIEF DESCRIPTION OF DRAWINGS
[0026] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems
30 in which like reference numerals refer to the same parts throughout the different drawings.
Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such
35 drawings includes disclosure of electrical components, electronic components or circuitry
commonly used to implement such components.
7

5 [0027] FIG.1A illustrates an exemplary block diagram representation of a 5th generation
core (5GC) network architecture [100a].
[0028] FIG.1B illustrates an exemplary block diagram of a system [100] connected to a
network node [101] to determine beam profile configuration of the network node [101]
10 present in a Radio Access Network (RAN), in accordance with exemplary embodiments of
the present disclosure.
[0029] FIG. 2 illustrates an exemplary method flow diagram indicating the process [200]
to determine beam profile configuration of a network node [101] in the RAN, in accordance
15 with exemplary embodiments of the present disclosure.
[0030] FIG. 3 illustrates an exemplary method flow diagram indicating the process [300]
for determining beam profile configuration of millimetre radio wave in a wireless
communication system, in accordance with the exemplary embodiments of the present
20 disclosure.
[0031] FIG. 4A, 4B and 4C illustrate exemplary deployment scenarios, for customer
precise equipment (CPEs) based on the dynamic beam profile configuration, in accordance
with exemplary embodiments of the present disclosure is shown.
25
[0032] FIG. 5 illustrates another exemplary deployment scenario of the beam profile
configuration having various azimuth angles, in accordance with the present disclosure.
[0033] FIG. 6 illustrates a method flow diagram indicating the process [600] of receiving
30 a set of data associated with location and height of CPEs, for determining beam profile
configuration of network node [101], in accordance with exemplary embodiments of the present disclosure.
[0034] FIG. 7 illustrates a system architecture [700] for dynamic beam profile
35 configuration in a millimetre radio wave as per the user distribution, in accordance with
exemplary embodiments of the present disclosure is shown.
8

5 [0035] FIG. 8 illustrates an exemplary block diagram of a computing device upon which,
an embodiment of the present disclosure may be implemented, in accordance with exemplary embodiments of the present disclosure.
[0036] The foregoing shall be more apparent from the following more detailed description
10 of the disclosure.
DETAILED DESCRIPTION
[0037] In the following description, for the purposes of explanation, various specific
15 details are set forth in order to provide a thorough understanding of embodiments of the
present disclosure. It will be apparent, however, that embodiments of the present disclosure
may be practiced without these specific details. Several features described hereafter can
each be used independently of one another or with any combination of other features. An
individual feature may not address any of the problems discussed above or might address
20 only some of the problems discussed above. Some of the problems discussed above might
not be fully addressed by any of the features described herein. Exemplary embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
25 [0038] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements
30 without departing from the spirit and scope of the disclosure as set forth.
[0039] It should be noted that the terms "mobile device", "user equipment", "user device",
“communication device”, “device” and similar terms are used interchangeably for the
purpose of describing the disclosure. These terms are not intended to limit the scope of the
35 disclosure or imply any specific functionality or limitations on the described embodiments.
The use of these terms is solely for convenience and clarity of description. The disclosure is not limited to any particular type of device or equipment, and it should be understood
9

5 that other equivalent terms or variations thereof may be used interchangeably without
departing from the scope of the disclosure as defined herein.
[0040] It should be noted that the terms “Access Point”, “Base Station”, “gNodeB” is a
wireless network module / device that facilitates or acts as a portal for devices or UEs to
10 connect to a local area network.
[0041] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For
15 example, circuits, systems, networks, processes, and other components may be shown as
components in a block diagram form in order to not obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
20
[0042] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order
25 of the operations may be re-arranged. A process is terminated when its operations are
completed but could have additional steps not included in a figure.
[0043] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter
30 disclosed herein is not limited by such examples. In addition, any aspect or design described
herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar
35 words are used in either the detailed description or the claims, such terms are intended to
be inclusive—in a manner similar to the term “comprising” as an open transition word— without precluding any additional or other elements.
10

5
[0044] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating
10 with other user devices and transmitting data to the other user devices. The user equipment
may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi
15 direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone,
smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
20
[0045] Further, the user device and/or a system as described herein to implement technical features as disclosed in the present disclosure may also comprise a “processor” or “processing unit”, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose
25 processor, a conventional processor, a digital signal processor, a plurality of
microprocessors, one or more microprocessors in association with a Digital Signal Processor (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or
30 any other functionality that enables the working of the system according to the present
disclosure. More specifically, the processor is a hardware processor.
[0046] As portable electronic devices and wireless technologies continue to improve and
grow in popularity, the advancing wireless technologies for data transfer are also expected
35 to evolve and replace the older generations of technologies. In the field of wireless data
communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second
11

5 generation (2G), third generation (3G), fourth generation (4G), and now fifth generation
(5G), and more such generations are expected to continue in the forthcoming time.
[0047] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and
10 standards that govern the way devices communicate with base stations, which are
responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division
15 Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-
Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/devices’ capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available
20 network resources.
[0048] As discussed in the background section about the problem in the network
infrastructure deployment, the static beam profile configuration was used, which led to
improper utilization, frequent manual intervention, inefficient network nodes, wastage of
25 resources like power and bandwidth, which ultimately led to degraded user services due to
poor signal quality.
[0049] The present disclosure aims to overcome the above-mentioned and other existing
problems in this field of technology by providing a method and system for determining
30 beam profile configuration of network node(s) in a communication network (preferably a
Radio Access Network (RAN)). This beam profile configuration is dynamic in nature as it is adopted as per the user distribution (or Customer Premises Equipment (CPEs)) in a deployed sector.
35 [0050] Hereinafter, exemplary embodiments of the present disclosure will be described
with reference to the accompanying drawings.
12

5 [0051] Referring to FIG. 1A, an exemplary block diagram representation of 5th generation
core (5GC) network architecture [100a] is shown. As shown in FIG. 1A, the 5GC network architecture [100a] includes a user equipment (UE) [102a], a radio access network (RAN) [104a], an access and mobility management function (AMF) [106a], a Session Management Function (SMF) [108a], a Service Communication Proxy (SCP) [110a], an
10 Authentication Server Function (AUSF) [112a], a Network Slice Specific Authentication
and Authorization Function (NSSAAF) [114a], a Network Slice Selection Function (NSSF) [116a], a Network Exposure Function (NEF) [118a], a Network Repository Function (NRF) [120a], a Policy Control Function (PCF) [122a], a Unified Data Management (UDM) [124a], an application function (AF) [126a], a User Plane Function (UPF) [128a],
15 a data network (DN) [130a], wherein all the components are assumed to be connected to
each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
[0052] The User Equipment (UE) [102a] interfaces with the network via the Radio
20 Access Network (RAN) [104a]; the Access and Mobility Management Function (AMF)
[106a] manages connectivity and mobility, while the Session Management Function (SMF) [108a] administers session control; the service communication proxy (SCP) [110a] routes and manages communication between network services, enhancing efficiency and security, and the Authentication Server Function (AUSF) [112a] handles user authentication; the
25 Network Slice Specific Authentication and Authorization Function (NSSAAF) [114a] for
integrating the 5G core network with existing 4G LTE networks i.e., to enable Non-Standalone (NSA) 5G deployments, the Network Slice Selection Function (NSSF) [116a], Network Exposure Function (NEF) [118a], and Network Repository Function (NRF) [120a] enable network customization, secure interfacing with external applications, and
30 maintain network function registries respectively; the Policy Control Function (PCF)
[122a] develops operational policies, and the Unified Data Management (UDM) [124a]
manages subscriber data; the Application Function (AF) [126a] enables application
interaction, the User Plane Function (UPF) [128a] processes and forwards user data, and
the Data Network (DN) [130a] connects to external internet resources; collectively, these
35 components are designed to enhance mobile broadband, ensure low-latency
communication, and support massive machine-type communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
13

5
[0053] Radio Access Network (RAN) [104a] is the part of a mobile telecommunications
system that connects the user equipment (UE) [102a] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication. 10
[0054] Access and Mobility Management Function (AMF) [106a] is a 5G core network
function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging. 15
[0055] Session Management Function (SMF) [108a] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement. 20
[0056] Service Communication Proxy (SCP) [110a] is a network function in the 5G core
network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
25 [0057] Authentication Server Function (AUSF) [112a] is a network function in the 5G
core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0058] Network Slice Specific Authentication and Authorization Function (NSSAAF)
30 [114a] is a network function that provides authentication and authorization services
specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
[0059] Network Slice Selection Function (NSSF) [116a] is a network function
35 responsible for selecting the appropriate network slice for a UE based on factors such as
subscription, requested services, and network policies.
14

5 [0060] Network Exposure Function (NEF) [118a] is a network function that exposes
capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0061] Network Repository Function (NRF) [120a] is a network function that acts as a
10 central repository for information about available network functions and services. It
facilitates the discovery and dynamic registration of network functions.
[0062] Policy Control Function (PCF) [122a] is a network function responsible for
policy control decisions, such as QoS, charging, and access control, based on subscriber
15 information and network policies.
[0063] Unified Data Management (UDM) [124a] is a network function that centralizes
the management of subscriber data, including authentication, authorization, and subscription information. 20
[0064] Application Function (AF) [126a] is a network function that represents external
applications interfacing with the 5G core network to access network capabilities and services.
25 [0065] User Plane Function (UPF) [128a] is a network function responsible for handling
user data traffic, including packet routing, forwarding, and QoS enforcement.
[0066] Data Network (DN) [130a] refers to a network that provides data services to user
equipment (UE) in a telecommunications system. The data services may include but are
30 not limited to Internet services, private data network related services.
[0067] Referring to FIG. 1B, an exemplary block diagram of a system [100] connected to
a network node [101] to determine beam profile configuration of the network node [101]
present in a Radio Access Network (RAN), in accordance with the exemplary embodiments
35 of the present disclosure is shown. The system [100] interacts with the network node(s)
[101] in a deployed network infrastructure. The system [100] comprises at least one central repository [106], at least one analyzer unit [108] and at least one configuration unit [110].
15

5 Further, at least one network management server [112] is connected to the network node
[101] and the system [100]. Also, all of the components/ units of the system [100] are
assumed to be connected to each other unless otherwise indicated below. Also, in Fig. 1B
only a few units are shown, however, the system [100] may comprise multiple such units,
or the system [100] may comprise any such numbers of said units, as required to implement
10 the features of the present disclosure. Further, in an implementation, the system [100] may
be present at a network level to implement the features of the present disclosure. In an implementation, the system [100] may reside in a server (local server or cloud server) or a network entity.
15 [0068] The centralized repository [106] of the system [100] is configured to receive a set
of data associated with location and height of one or more deployed Customer Premises Equipment (CPEs). It is important to note that the one or more deployed CPEs are within a coverage area of the network node [101] of the RAN. For instance, in an exemplary scenario, the data associated with the location and height of the CPEs can be collected
20 manually through filled-in customer application forms (CAFs) on the paper. This set of
data can also be captured or received via a digital means such as an application that is responsible for collecting data for installation of the CPEs like a CPE installation app. Suppose a CPE (lets’ say CPE#1) has to be installed at a location (lets’ say L) having an altitude or height (lets’ say H), then the same will be collected through CAFs or the mobile
25 application that collects installation data. It is to be noted that the each of the one or more
deployed CPEs is within the coverage area of the network node [101] of the radio access network (RAN). As used herein, the centralized repository [106] (also referred as “centralized platform” or “centralized server” or “centralized location”) may be used to store data permanently or temporarily (for e.g., set of data associated with location and
30 height of the one or more deployed CPEs) while it is being processed. Furthermore, it is to
be noted that the one or more deployed Customer Premises Equipment (CPEs) may include devices located on the customer's premises of the network operator that enable access to communication services. For instance, the one or more deployed CPEs may include modems, routers, set-top boxes, and telephones etc. that facilitate the connection between
35 the customers and the service provider's network infrastructure.
16

5 [0069] The analyzer unit [108] is connected to the centralized repository [106], and the
analyzer unit [108] is configured to analyze the set of data to determine at least one beam profile configuration suitable for transmission of data to the one or more deployed CPEs. It is to be noted that the analysis of the set of data takes place once the set of data is received. The configuration unit [110] is connected to the analyzer unit [108] and is configured to
10 automatically configure the network node [101] via the NMS [112] based on the at least
one beam profile configuration. As used herein, the network management server (NMS) [112] is an important component in RAN whose task may include configuration management of base stations, antennas, radio frequency (RF) configuration, cell planning, power levels, and network topology to ensure optimal performance and coverage; fault
15 management; performance management; security management, software management like
upgrade and maintenance of software components and firmware in the RAN; resource allocation including but not limited to allocation of radio resources, spectrum, and bandwidth, and interoperability and interworking between RAN technologies. Further, the network node [101] may include, but is not limited to, a radio device/ simply a millimetre
20 (mm) wave radio whose beam profile configuration(s) is projected to offer services of the
network to the one or more CPEs.
[0070] The at least one beam profile configuration is determined based on at least one of: a distribution of user(s), a distribution of the one or more deployed CPEs, an identification
25 of a category of one or more deployed CPEs, height of the network node [101], height of
the one or more deployed CPEs, vertical positioning of the one or more deployed CPEs and horizontal positioning of the one or more deployed CPEs. In an exemplary embodiment of the present disclosure, the identification of a category of the one or more deployed CPEs is done from the analyzed set of the data. For instance, the beam profile configuration in a
30 scenario where a communication network (that utilizes a fixed wireless access (FWA)
connection to connect to the network) requires the one or more CPEs to be deployed, the beam profile configuration can be identified based on the strength and direction of the wireless signal received. In another instance, the coverage area may comprise of servicing the mmWave 5G service in the 120-degree horizontal plane and ±60° in the vertical plane.
35 Therefore, based on the distribution of the user clutter i.e., building height and number of
one or more CPEs in the coverage area, various combinations of the beam profile configurations [exemplary beam profile configurations (BPC)/ beam profile configurations
17

5 (BC) are depicted in FIG. 4A, FIG. 4B and FIG. 4C] can be defined in order to effectively
serve the users and providing the efficient downlink and uplink throughputs.
[0071] In another exemplary embodiment of the present disclosure, the category of the CPE deployment for the one or more deployed CPEs include one of a scattered category
10 and a focused category. The scattered category includes a set of the one or more deployed
CPEs that are placed at a distance from each other, and focused category includes a set of the one or more deployed CPEs that are placed nearer to each other. The identification of the category of the CPE deployment for the one or more deployed CPEs is further based on at least one of an identification of a number of active one or more deployed CPEs, and
15 an identification of a distance between each of at least two deployed CPEs within the
coverage area of the network node [101]. For e.g., the network operator wants to deploy the beam profile configuration to provide services via the one or more deployed CPEs situated in residential areas, then the network operator monitors the number of active one or more deployed CPEs and distance between the deployed CPEs. The former leads to
20 identification of the category of the one or more deployed CPEs based on the level of CPE
utilization that indicates high demand and heavy usage on a plurality of the one or more set of deployed active CPEs, thereby leading to classification as a densely populated deployment. The latter leads to the network operator analyzing the distance between each of two deployed CPEs i.e., measuring the proximity between the two deployed CPEs, and
25 thereafter the network operator can assess the spatial distribution of customers and the
density of CPE deployment like indicating a densely populated urban area with closely spaced residential units based upon the distance between CPEs being relatively shorter.
[0072] Further, the at least one beam profile configuration is at least one of: a first beam
30 profile configuration, a second beam profile configuration, and a third beam profile
configuration, and wherein the first beam profile configuration, the second beam profile configuration and the third beam profile configuration cause the enabling of services of the RAN within the coverage area of the network node [101].
35 [0073] Furthermore, the the first beam profile configuration includes deploying the
network node [101] at lesser elevation compared to the height of one or more deployed CPEs. In another exemplary embodiment of the present disclosure, the network node [101]
18

5 is configured using a first beam profile configuration, upon identifying the category of the
CPE deployment for the plurality of CPE(s) to be scattered, wherein the first beam profile configuration is a beam profile configuration that is identified for the scattered category.
[0074] Additionally, the second configuration includes deploying the network node [101]
10 at higher elevation compared to the height of the one or more deployed CPEs. In another
exemplary embodiment of the present disclosure, the network node [101] is configured
using a second beam profile configuration, upon identifying the category of the CPE
deployment for the plurality of CPE(s) to be focused, wherein the second beam profile
configuration is a beam profile configuration that is identified for the focussed/ nearby
15 category.
[0075] Also, the third beam profile configuration includes deploying the network node
[101] to cover the one or more deployed CPEs at a higher elevation, a lower elevation and
a parallel elevation compared to an existing deployment of the network node [101]. It is to
20 be noted that the existing deployment of the network node [101] here pertains to previous
position of the currently deployed network node [101] which is later changed using the techniques described herein.
[0076] In an exemplary embodiment of the present disclosure, the determination of the at
25 least one beam profile configuration suitable for transmission of data to the one or more
CPEs facilitates installation of one or more new CPEs within the coverage area of the network node [101].
[0077] In yet another implementation of the disclosure, a non-transitory computer
30 readable storage medium storing executable instructions to determine beam profile
configuration of a network node [101] in the RAN is disclosed. The instructions, when
executed by one or more units of a system [100], enable: receiving, by a centralized
repository [106] of said system, a set of data associated with location and height of one or
more deployed customer premise equipment (CPEs), wherein each of the one or more
35 deployed CPEs is within a coverage area of the network node [101] of the RAN; analyzing,
by an analyzer unit [108] of the system, the set of data, to determine at least one beam profile configuration suitable for transmission of data to the one or more deployed CPEs,
19

5 and automatically configuring, by a configuration unit of the system via a Network
Management Server (NMS) [112], the network node [101] based on the at least one determined beam profile configuration.
[0078] Referring to FIG. 2, an exemplary method flow diagram [200], to determine beam
10 profile configuration of a network node [101] in a radio access network (RAN), in
accordance with exemplary embodiments of the present disclosure is shown. The method [200] is performed by the system [100]. As shown in FIG. 2, the method [200] starts at step [202].
15 [0079] At step [204], the method [200] as disclosed by the present disclosure comprises
receiving a set of data associated with location and height of one or more deployed Customer Premises Equipment (CPEs) by a centralized repository [106]. It is important to note that the one or more deployed CPEs are within a coverage area of the network node [101] of the RAN. For instance, in an exemplary scenario, the data associated with the
20 location and height of the CPEs can be collected manually through filled-in customer
application forms (CAFs) on the paper. This set of data can also be captured or received via a digital means such as an application that is responsible for collecting data for installation of the CPEs like a CPE installation app. Suppose a CPE (lets’ say CPE#1) has to be installed at a location (lets’ say L) having an altitude or height (lets’ say H), then the
25 same will be collected through CAFs or the mobile application that collects installation
data. It is emphasized that each of the one or more deployed CPEs is within the coverage area of the network node [101] of the RAN. As used herein, the centralized repository [106] (also referred as “centralized platform” or “centralized server” or “centralized location”) may be used to store data permanently or temporarily (for e.g., set of data associated with
30 location and height of one or more deployed CPEs) while it is being processed.
Furthermore, it is to be noted that the one or more deployed Customer Premises Equipment (CPE) may include devices located on the customer's premises of the network operator that enable access to communication services. For instance, the CPEs may include modems, routers, set-top boxes, and telephones etc. that facilitate connection between the customers
35 and the service provider's network infrastructure.
20

5 [0080] At step [206], the method [200] as disclosed by the present disclosure comprises
analyzing, by an analyzer unit [108], the set of data to determine at least one beam profile
configuration suitable for transmission of data to the one or more deployed CPEs. It is to
be noted that the analysis of the set of data takes place once the set of data is received. For
instance, the set of data associated with the location and height of the two CPEs i.e., CPE#1
10 and CPE#2 is analysed in terms by determining the distance between CPE#1 and CPE#2.
This distance then helps in identifying the type of deployment (whether scattered or nearby) for beam profile configuration (BC)/ beam profile configuration (BPC).
[0081] At step [208], the method [200] as disclosed by the present disclosure comprises
15 automatically configuring, by a configuration unit [110] via a Network Management Server
(NMS) [112], the network node [101] based on the determined at least one beam profile configuration.
[0082] The at least one beam profile configuration is determined based on at least one of:
20 a distribution of user(s), a distribution of the one or more deployed CPEs, an identification
of a category of one or more deployed CPEs, height of the network node [101], height of the one or more deployed CPEs, vertical positioning of the one or more deployed CPEs and horizontal positioning of the one or more deployed CPEs. In an exemplary embodiment of the present disclosure, the identification of a category of the one or more deployed CPEs is
25 done from the analyzed set of the data. For instance, the beam profile configuration in a
scenario where a communication network (that utilizes a fixed wireless access (FWA) connection to connect to the network) requires the one or more CPEs to be deployed, the beam profile configuration can be identified based on the strength and direction of the wireless signal received. In another instance, the coverage area may comprise of servicing
30 the mmWave 5G service in the 120-degree horizontal plane and ±60° in the vertical plane.
Therefore, based on the distribution of the user clutter i.e., building height and number of one or more CPEs in the coverage area, various combinations of the beam profile configurations [exemplary beam profile configurations (BPC)/ beam profile configurations (BC) are depicted in FIG. 4A, FIG. 4B and FIG. 4C] can be defined in order to effectively
35 serve the users and providing the efficient downlink and uplink throughputs.
21

5 [0083] Further, the at least one beam profile configuration is at least one of: a first beam
profile configuration, a second beam profile configuration, and a third beam profile configuration, and wherein the first beam profile configuration, the second beam profile configuration and the third beam profile configuration cause the enabling of services of the RAN within the coverage area of the network node [101].
10
[0084] Furthermore, the first beam profile configuration includes deploying the network node [101] at lesser elevation compared to the height of one or more deployed CPEs. It is to be noted that as per the CPEs deployment scenario (as explained above), the radio will select the first beam profile configuration. For e.g., the first beam profile configuration is
15 not limited to having 4, 8 or 12 numbers of beams. It can have many beams depending upon
the coverage requirement. It is also to be noted that the beam directions and number of beams shown along with the building floors in the Figures 4A, 4B and 4C are for illustration purposes only. There can be multiple combinations of the beam profile configurations depending upon the direction and number of building floors coverage and on the
20 beamwidths of the antenna array of the mmWave Radio.
[0085] Additionally, the second configuration includes deploying the network node [101] at higher elevation compared to the height of the one or more deployed CPEs. It is to be noted that as per the CPEs deployment scenario (as explained above), the radio will select
25 the second beam profile configuration. For e.g., the second beam profile configuration is
not limited to having 4, 8 or 12 numbers of beams. It can have many beams depending upon the coverage requirement. It is also to be noted that the beam directions and number of beams shown along with the building floors in the Figures 4A, 4B and 4C are for illustration purposes only. There can be multiple combinations of the beam profile configurations
30 depending upon the direction and number of building floors coverage and on the
beamwidths of the antenna array of the mmWave Radio.
[0086] Also, the third beam profile configuration includes deploying the network node
[101] to cover the one or more deployed CPEs at a higher elevation, a lower elevation and
35 a parallel elevation compared to an existing deployment of the network node [101]. It is to
be noted that the existing deployment of the network node [101] here pertains to previous position of the currently deployed network node [101] which is later changed using the
22

5 techniques described herein. It is to be noted that as per the CPEs deployment scenario (as
explained above), the radio will select the third beam profile configuration. For e.g., the
third beam profile configuration is not limited to having 4, 8 or 12 numbers of beams. It
can have many beams depending upon the coverage requirement. It is also to be noted that
the beam directions and number of beams shown along with the building floors in the
10 Figures 4A, 4B and 4C are for illustration purposes only. There can be multiple
combinations of the beam profile configurations depending upon the direction and number of building floors coverage depending on the beamwidths of the antenna array of the mmWave Radio.
15 [0087] Thereafter, the method [200] terminates at step [210].
[0088] Referring to FIG. 3, an exemplary method flow diagram indicating the process
[300] for determining beam configuration of millimetre (mm) wave radio in a wireless
communication system is shown, in accordance with the exemplary embodiments of the
20 present disclosure. As depicted in Figure 3, at [step 1], a centralized platform [302] gets
the location of all the customer premises enterprises (CPEs) along with their height in a coverage area of a network node (shown in Fig. 1) and sends it along with the mm wave Radio location as input to the [step 2].
25 [0089] At [step 2], the no. of connected CPEs is identified as per individual mm wave
Radio. At [step 3], the inter distance between the CPEs is estimated. At [step 4], the deployment configuration is identified. It is important to note that deployment configuration may include scattered user distribution or nearby user distribution. It is important to note that scattered user distribution covers a wider area in horizontal and/or
30 vertical plane with less focused signal strength which is suitable for dispersed CPE
deployments or broad coverage scenarios. On the other hand, the nearby user distribution provides highly focused beams directed at nearby or co-located CPEs, offering stronger signal strength and higher performance over shorter distances. At [step 5], the selection of the beam profile configuration takes place. This selection is based on user distribution
35 (scattered or nearby), an identification of a number of active CPEs, gNB height, and an
identification of a distance between each of at least two CPE(s) within the network coverage area. At [step 6], the selected beam profile configuration is sent to a Network
23

5 Management Server (NMS) [312]. At [step 7], the NMS [312] sends the beam
configuration to the mm wave radio. Thus, the beam configuration is automatically configured based on the type of deployment of the CPEs and their distribution.
[0090] Referring to FIG. 4A, FIG. 4B and FIG. 4C, exemplary deployment scenarios, for
10 customer precise equipment (CPEs), based on the dynamic beam profile configuration, in
accordance with exemplary embodiments of the present disclosure is shown. FIG. 4A, FIG. 4B and FIG. 4C illustrate beam profile configuration BPC-1, BPC-2 and BPC-3 respectively. The beam profile configurations are as follows:
- BPC-1: This profile will be selected when the radio/ mm Wave radio is at lesser
15 height and the one or more CPEs are installed in a high-rise building. There are 4
beams at 0-degree elevation angle and 4 beams are at 15 degrees elevation angle.
These beams can cover -60 degrees to +60 degrees area in a horizontal span and
30 degrees span in a vertical plane. There could be a tilt of 0 & +15 degrees in the
BPC which will cover ground and higher floors of a building having deployed
20 CPEs.
- BPC-2: This profile is selected when the radio is at higher height and the CPEs are
deployed/ installed in lower height. There are 4 beams at 0-degree elevation angle
and 4 beams are at -15 degrees elevation angle. These beams are able to cover -60
degrees to + 60 degrees area in horizontal span and 30 degrees span in vertical
25 plane. There will be a tilt of 0 & -15 degrees that will cover parallel and lower
floors of a building having the deployed CPEs.
- BPC-3: This profile is selected when the radio is required to cover the deployed
CPEs that are installed in lower, higher and parallel heights. There are 4 beams at
0-degree elevation angle, 4 beams are at -15 degrees elevation angle and 4 beams
30 are at +15 degrees elevation angle. These beams are able to cover -60 degrees to +
60 degrees area in horizontal span and 40 degrees span in vertical plane. There will be a tilt of 0, +15 & -15 degrees and will cover parallel, higher and lower floors of a building having deployed CPEs.
35 [0091] It is to be noted that as per the CPEs deployment scenario (as explained above),
the radio will select the BPC-1. BPC-2 or BPC-3 profile. Thus, one can generate any number of beam profile configurations depending upon the deployment scenario. Here,
24

5 there are only 3 profiles considered, however, there can be a “n” number of beam profile
configuration that can be defined by an operator. These beam profiles can have 1, 4, 8 or 12 numbers of beams depending upon the coverage requirement.
[0092] It is also to be noted that the beam directions and number of beams shown along
10 with the building floors in FIG. 4A, FIG. 4B and FIG. 4C are for the illustration purpose
only. There can be multiple combinations of the beam profile configurations depending upon the direction and number of building floors coverage depending on the beamwidths of the antenna array of the mmWave Radio.
15 [0093] Referring to FIG. 5, an exemplary deployment scenario of azimuth coverage of the
mmWave Radio is shown, in accordance with the present disclosure. The beam profile configuration has been realised in the horizontal plane. Here, there are 4 beams being shown to have 4 azimuth angles i.e., a -45 degrees azimuth beam, -15 degrees azimuth beam, a 15 degrees azimuth beam and a 45 degrees azimuth. These beams are able to cover
20 -45 degrees to +45 degrees area in the horizontal span. Further, it is important to note that
the azimuth angle in the beam profile configuration is not limited to the above-mentioned degree range. It is to be noted that the azimuth angle can be customised to any particular range to cater to all the CPEs in communication network. It is also important to note that in Fig. 5, only 4 beams have been shown, however, there is no limit to the number of beams
25 that can be deployed in the beam profile configuration shown in Fig. 5.
[0094] Referring to FIG. 6, a method flow diagram indicating the process [600] of receiving a set of data associated with location and height of CPEs, for determining beam profile configuration of network node [101], in accordance with exemplary embodiments
30 of the present disclosure is shown. As shown in Fig. 6, the set of data is indicative of a
geographical location of two CPEs i.e., CPE#1 and CPE#2 and may include, but is not limited to, location of the user, address of the user, geolocation parameters of the user, height of the place of the user from the surface, area of the user, the installation parameters associated with the CPE#1 and CPE#2, floor height and the like. Further, the installation
35 data may include but is not limited to actual coordinates (geo coordinates, height) of the
installation of the CPE. This set of data is then received by the centralized platform [601] (or centralized repository [106] as shown in Fig. 1) with the help of Customer Application
25

5 Form (CAF) or a CPE installation application. This set of data helps in identifying the
CPE’s details like location along with height, etc. The details of CPE are then mapped onto a cell ID in a Radio Access Network (RAN).
[0095] FIG. 7 illustrates a system architecture [700], for dynamic beam profile
10 configuration in a millimetre radio wave as per the user distribution, in accordance with
exemplary embodiments of the present disclosure. A location and floor height of deployed
Customer Precise Enterprise(s) (CPE(s)) are captured in the Customer Application Form
(CAF) [702] or in a CPE deployment application [704]. These details are then made
available at a centralized location called as Centralized Platform (CPF) [706]. After
15 determining the distance between CPEs, the CPF [706] identifies the category of CPE
deployment - whether it is a scattered deployment or a nearby deployment for beam profile
configuration (BC). This BC information is then provided to a Network Management
Server (NMS) [708] by the CPF [706]. Then, the NMS [708] will automatically configure
the beam profile configuration (BC) in a mmWave Radio [710] depending on the type of
20 identified information from the CPF [706]. In an exemplary embodiment of the disclosure,
the CPF [706] may identify a scattered beam profile configuration or a nearby beam profile
configuration based on the analysis of the location and floor height.
[0096] FIG. 8 illustrates an exemplary block diagram of a computing device [1000] upon
25 which an embodiment of the present disclosure may be implemented. In an implementation,
the computing device [1000] implements the method [200] to determine beam profile
configuration of a network node [101] in a radio access network (RAN) in a multi-network
environment, by utilising the system [100]. In another implementation, the computing
device [1000] itself implements the method [200] to determine beam profile configuration
30 of a network node [101] in the RAN in the multi-network environment, using one or more
units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0097] The computing device [1000] may include a bus [1002] or other communication
35 mechanism for communicating information, and a hardware processor [1004] coupled with
bus [1002] for processing information. The hardware processor [1004] may be, for
example, a general-purpose microprocessor. The computing device [1000] may also
26

5 include a main memory [1006], such as a random-access memory (RAM), or other dynamic
storage device, coupled to the bus [1002] for storing information and instructions to be executed by the processor [1004]. The main memory [1006] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [1004]. Such instructions, when stored in non-transitory
10 storage media accessible to the processor [1004], render the computing device [1000] into
a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [1000] further includes a read only memory (ROM) [1008] or other static storage device coupled to the bus [1002] for storing static information and instructions for the processor [1004].
15
[0098] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [1002] for storing information and instructions. The computing device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray tube (CRT), Liquid Crystal Display (LCD), Light Emitting Diode (LED)
20 display, Organic LED (OLED) display, etc. for displaying information to a computer user.
An input device [1014], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information and command selections to the processor [1004]. Another type of user input device may be a cursor controller [1016], such as a mouse, a trackball, or cursor direction keys, for communicating
25 direction information and command selections to the processor [1004], and for controlling
cursor movement on the display [1012]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
30 [0099] The computing device [1000] may implement the techniques described herein
using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [1000] causes or programs the computing device [1000] to be a special-purpose machine. According to one embodiment, the techniques herein are performed by the computing device [1000] in
35 response to the processor [1004] executing one or more sequences of one or more
instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010].
27

5 Execution of the sequences of instructions contained in the main memory [1006] causes
the processor [1004] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.
10 [0100] The computing device [1000] also may include a communication interface [1028]
coupled to the bus [1002]. The communication interface [1028] provides a two-way data communication coupling to a network link [1020] that is connected to a local network [1022]. For example, the communication interface [1028] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data
15 communication connection to a corresponding type of telephone line. As another example,
the communication interface [1028] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [1028] sends and receives electrical, electromagnetic or optical signals that carry digital data streams
20 representing various types of information.
[0101] The computing device [1000] can send messages and receive data, including
program code, through the network(s), the network link [1020] and the communication
interface 1028. In the Internet example, a server [1030] might transmit a requested code for
25 an application program through the Internet [1028], the host [1024], the ISP [1026], the
local network [1022] and the communication interface [1028]. The received code may be executed by the processor [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage for later execution.
30 [0102] As is evident from the above, the present disclosure provides a solution for
automatic dynamic beam profile configuration in communication networks (preferably a millimeter Wave Radio) that helps to effectively utilize the radio capacity by serving users with a better signal quality without the involvement of human resources. This beam profile configuration is determined and thereby adopted as per the user distribution (i.e., Customer
35 Premises Equipment (CPEs)) in a deployed network infrastructure. The present disclosure
also allows the RAN nodes to select the appropriate beam profile configuration depending on the CPEs deployments.
28

5
[0103] Further, the present disclosure provides a technically advanced solution to provide
optimised beam deployment configurations which result in optimised and efficient beam
forming. Thus, the present disclosure provides various technical advantages such as better
efficiency of the antenna, maximum utilization of the resources, increase in the user-
10 perceived throughout, decrease in cost, power efficiency and the like.
[0104] The present disclosure aids in carrying out periodic monitoring of the distribution
of the CPEs and accordingly carry out the re-configuration of the beam profile
configuration for the effective cell user throughput. The present disclosure also allows the
15 radio to automatically select and update the appropriate beam profile from a beam profile
set depending on the CPE deployments and the addition of the new CPEs in the sector.
[0105] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many
20 changes can be made to the embodiments without departing from the principles of the
present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
25 [0106] Further, in accordance with the present disclosure, it is to be acknowledged that
the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the
30 disclosure should not be construed as limiting the scope of the present disclosure.
Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
29

5 We Claim:
1. A method [200] to determine beam profile configuration of a network node [101]
in a radio access network (RAN), the method [200] comprising:
receiving, by a centralized repository [106], a set of data associated with
location and height of one or more deployed customer premise equipment (CPEs),
10 wherein each of the one or more deployed CPEs is within a coverage area of the
network node [101] of the RAN;
analyzing, by an analyzer unit [108], the set of data to determine at least
one beam profile configuration suitable for transmission of data to the one or more
deployed CPEs; and
15 automatically configuring, by a configuration unit [110] via a Network
Management Server (NMS) [112], the network node [101] based on the at least
one determined beam profile configuration.
2. The method [200] as claimed in claim 1, wherein the at least one beam profile
20 configuration is determined based on at least one of: a distribution of user(s), a
distribution of the one or more deployed CPEs, an identification of a category of the one or more deployed CPEs, height of the network node [101], height of the one or more deployed CPEs, vertical positioning of the one or more deployed CPEs and horizontal positioning of the one or more deployed CPEs. 25
3. The method [200] as claimed in claim 1, wherein the at least one beam profile
configuration is at least one of: a first beam profile configuration, a second beam
profile configuration, and a third beam profile configuration, wherein the first
beam profile configuration, the second beam profile configuration and the third
30 beam profile configuration enable services of the RAN within the coverage area of
the network node [101].
4. The method [200] as claimed in claim 3, wherein the first beam profile
configuration comprises deploying the network node [101] at lesser elevation
35 compared to the height of the one or more deployed CPEs.
30

5 5. The method [200] as claimed in claim 3, wherein the second beam profile
configuration comprises deploying the network node [101] at higher elevation compared to the height of the one or more deployed CPEs.
6. The method [200] as claimed in claim 3, wherein the third beam profile
10 configuration comprises deploying the network node [101] to cover the one or
more deployed CPEs at a higher elevation, a lower elevation and a parallel elevation, compared to an existing deployment of the network node [101].
7. The method [200] as claimed in claim 1, wherein the determining the at least one
15 beam profile configuration suitable for transmission of data to the one or more
CPEs facilitates installation of one or more new CPEs within the coverage area of the network node [101].
8. A system [100] to determine beam profile configuration of a network node [101]
20 in a radio access network (RAN), the system [100] comprising:
a centralized repository [106], the centralized repository [106] being configured to receive a set of data associated with location and height of one or more deployed customer premise equipment CPEs, wherein each of the one or more deployed CPEs is within a coverage area
25 of the network node [101] of the RAN;
an analyzer unit [108] connected to the centralized repository [106], the analyzer unit [108] being configured to analyze the set of data to determine at least one beam profile configuration suitable for transmission of data to the one or more deployed CPEs; and
30 a configuration unit [110] connected to the analyzer unit [108], the
configuration unit [110] being configured to automatically configure, via a Network Management Server (NMS) [112], the network node [101] based on the at least one determined beam profile configuration.
35 9. The system [100] as claimed in claim 8, wherein the at least one beam profile
configuration is determined based on at least one of: a distribution of user(s), a distribution of the one or more deployed CPEs, an identification of a category of
31

5 one or more deployed CPEs, height of the network node [101], height of the one
or more deployed CPEs, vertical positioning of the one or more deployed CPEs and horizontal positioning of the one or more deployed CPEs.
10
15
10. The system [100] as claimed in claim 8, wherein the at least one beam profile configuration is at least one of: a first beam profile configuration, a second beam profile configuration, and a third beam profile configuration, and wherein the first beam profile configuration, the second beam profile configuration and the third beam profile configuration enabling services of the RAN within the coverage area of the network node [101].
11. The system [100] as claimed in claim 10, wherein the first beam profile configuration includes deploying the network node [101] at lesser elevation compared to the height of the one or more deployed CPEs.
20 12. The system [100] as claimed in claim 10, wherein the second beam profile
configuration includes deploying the network node [101] at higher elevation compared to height of the one or more deployed CPEs.
13. The system [100] as claimed in claim 10, wherein the third beam profile
25 configuration includes deploying the network node [101] to cover the one or more
deployed CPEs at a higher elevation, a lower elevation and a parallel elevation compared to an existing deployment of the network node [101].
14. The system [100] as claimed in claim 8, wherein the determination of the at least
30 one beam profile configuration suitable for transmission of data to the one or more
deployed CPEs facilitates installation of one or more new CPEs within the coverage area of the network node [101].