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 SUPPORTING SELF-ORGANISING
NETWORK”
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.

METHOD AND SYSTEM FOR SUPPORTING SELF-ORGANISING NETWORK
FIELD OF THE DISCLOSURE
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to supporting self-organising network (SON).
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few 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-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 communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In wireless communication systems, there is a need for self-optimization of networks for network management. A self-organizing network (SON) is an automation technology designed to make the planning, configuration, management, and optimization of radio access networks simpler and faster. Various vendors develop their own SON for addressing different

problems or network-related issues. Since each vendor has its own way to address a particular issue related to the nodes in the network, lack of compatibility is an issue that arises and needs to be resolved.
[0005] Further, over the period of time various solutions have been developed to improve the performance of such systems to support multi-vendor self-organising network. However, there are certain challenges with existing solutions. For example, the existing systems do not provide a common database of all vendors to interact with and thus, the systems are not developed using a common pool of data from all vendors. Since all the vendors may have different key issues to be addressed in their systems, compatibility issues may still arise from the same and the systems may not even be easy to implement.
[0006] Thus, there exists an imperative need in the art to provide a solution for supporting self-organising network (SON), which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0007] 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.
[0008] An aspect of the present disclosure may relate to a system for supporting self-organising network (SON). The system comprises a multi-vendor self-organising network (MV-SON) module. The MV-SON module further comprises a transceiver unit configured to receive, via a collation platform, one or more types of data to store the one or more types of data in a storage unit. Further, the MV-SON module comprises an execution unit connected to at least the transceiver unit. The execution unit is configured to execute one or more SON algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data. Further, the execution unit is configured to generate an output based on the execution of the SON algorithms, for supporting self-organizing network (SON). Also, the transceiver unit is further configured to transmit the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.

[0009] In an exemplary aspect of the present disclosure, the one or more types of data comprises a data received from at least one of a configuration management (CM) module, a performance management (PM) module, and a fault management (FM) module, a data received from a site database of each vendor among the one or more vendors, and a data received from a cell database of each vendor among the one or more vendors.
[0010] In an exemplary aspect of the present disclosure, the system further comprises a data collector function (DCF) module wherein the transceiver unit is configured to receive the data from the configuration management (CM) module via the DCF module.
[0011] In an exemplary aspect of the present disclosure, the DCF module is configured to: collect, via the collation platform, one or more of a serving cell data, and a neighbour list parameters data from the CM module; process the collected data to change the format of the collected data to generate a processed data; and provide the processed data to the transceiver unit.
[0012] In an exemplary aspect of the present disclosure, in the open loop mode of operation, the execution unit is configured to: execute the one or more SON algorithms; and provide a detailed report based on the execution of the one or more SON algorithms.
[0013] In an exemplary aspect of the present disclosure, in the closed loop mode of operation, the execution unit is configured to: execute the one or more SON algorithms; make changes automatically, to one or more configuration parameters based on the one or more SON algorithms; and provide a detailed report based on the execution of the one or more SON algorithms.
[0014] In an exemplary aspect of the present disclosure, the execution unit is further configured to: send, to the collation platform, a request for providing a comparison report of one or more pre-configured key performance indicators (KPIs); and receive, from the collation platform, the comparison report of the one or more pre-configured KPIs based on the request.
[0015] Another aspect of the present disclosure may relate to a method for supporting self-organising network (SON). The method comprises receiving, by a transceiver unit at a multi-

vendor self-organising network (MV-SON) module via a collation platform, one or more types of data for storing the one or more types of data in a storage unit. Further, the method comprises executing, by an execution unit at the MV-SON module, one or more SON algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data. Further, the method comprises generating, by the execution unit at the MV-SON module, an output based on the execution of the SON algorithms, for supporting self-organising network (SON). Further, the method comprises transmitting, by the transceiver unit at the MV-SON module, the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.
[0016] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for supporting self-organising network (SON), the instructions include executable code which, when executed by a one or more units of a system, causes: (1) a transceiver unit to receive, via a collation platform, one or more types of data to store the one or more types of data in a storage unit; (2) an execution unit to: (a) execute one or more SON algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data, and (b) generate an output based on the execution of the SON algorithms, for supporting the self-organising network (SON); and (3) the transceiver unit further to transmit the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.
[0017] Yet another aspect of the present disclosure may relate to a user equipment (UE) comprising a user interface (UI). The UI is configured to provide a report on a self-organising network (SON) among a plurality of SONs. The report is generated by a system based on: (1) receiving, by a transceiver unit at a MV-SON module via a collation platform, one or more types of data for storing the one or more types of data in a storage unit; (2) executing, by an execution unit at the MV-SON module, one or more SON algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data; (3) generating, by the execution

unit at the MV-SON module, an output based on the execution of the SON algorithms, for supporting the self-organising network (SON); and (4) transmitting, by the transceiver unit at the MV-SON module, the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.
OBJECTS OF THE INVENTION
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for supporting self-organising network that is able to optimize networks of multiple vendors through a central server.
[0020] It is another object of the present disclosure to provide a solution for supporting self-organising network that overcomes the issue of compatibility among systems of various vendors.
[0021] It is yet another object of the present disclosure to provide a solution for supporting self-organising network that is developed using a common database for all vendors.
[0022] It is yet another object of the present disclosure to provide a solution for supporting self-organising network that is independent of vendor type.
[0023] It is yet another object of the present disclosure to provide a solution for supporting self-organising network in which same algorithms can be used for all vendors uniformly.
[0024] It is yet another object of the present disclosure to provide a solution for supporting self-organising network in which there is no need to be dependent on vendor development.
DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are incorporated herein, and constitute a
part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0026] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0027] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0028] Fig. 3 illustrates an exemplary block diagram of a system for supporting self-organising network (SON), in accordance with exemplary implementations of the present disclosure.
[0029] Fig. 4 illustrates a method flow diagram for supporting self-organising network (SON) in accordance with exemplary implementations of the present disclosure.
[0030] Fig. 5 illustrates a system implementing an exemplary scenario for supporting self-organising network (SON), in accordance with exemplary implementations of the present disclosure.
[0031] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION

[0032] In the following description, for the purposes of explanation, various specific 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 may 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 only some of the problems discussed above.
[0033] 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 without departing from the spirit and scope of the disclosure as set forth.
[0034] 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 example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0035] 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 may be performed in parallel or concurrently. In addition, the order 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.
[0036] 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 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 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. 5
[0037] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more
10 microprocessors in association with a (Digital Signal Processing) 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 any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or
15 processing unit is a hardware processor.
[0038] 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
20 is recognized that various configurations and combinations thereof are within the scope of the
disclosure. The functionality of specific units as disclosed in the 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.
25
[0039] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing
30 the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a
9

processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0040] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
5 readable medium including any mechanism for storing information in a form readable by a
computer or similar machine. For example, a computer-readable medium includes read-only
memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
storage media, flash memory devices or other types of machine-accessible storage media. The
storage unit stores at least the data that may be required by one or more units of the system to
10 perform their respective functions.
[0041] As used herein “interface” or “user interface refers to a shared boundary across which
two or more separate components of a system exchange information or data. The interface may
also be referred to a set of rules or protocols that define communication or interaction of one
15 or more modules or one or more units with each other, which also includes the methods,
functions, or procedures that may be called.
[0042] All modules, units, components used herein, unless explicitly excluded herein, may be
software modules or hardware processors, the processors being a general-purpose processor, a
20 special purpose processor, a conventional processor, a digital signal processor (DSP), a
plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
25 [0043] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
30 [0044] As used herein, the term ‘Vendor’ refers to original equipment manufacturer for base
stations. Each vendor may have its own elementary management system (EMS) to manage its own set of base stations. Also, all different EMSs belonging to different vendors may collect data from their respective base stations and send the data to a collation platform.
10

[0045] As discussed in the background section, the current known solutions have several
shortcomings. The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing method and system of supporting
self-organising network (SON). To achieve this in the present discloses a novel solution that
5 comprises a multi-vendor self-organising network (MV-SON) module that works for multiple
situations and scenarios associated with multiple vendors. Further, the solution as disclosed herein is independent of the use case, i.e., the situation or scenario associated with the multiple vendors.
10 [0046] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
(5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy
15 (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data
20 network (DN) [130], 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.
[0047] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system
25 that connects user equipment (UE) [102] 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.
[0048] Access and Mobility Management Function (AMF) [106] is a 5G core network function
30 responsible for managing access and mobility aspects, such as UE registration, connection, and
reachability. It also handles mobility management procedures like handovers and paging.
[0049] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions.
11

It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0050] Service Communication Proxy (SCP) [110] is a network function in the 5G core
5 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.
[0051] Authentication Server Function (AUSF) [112] is a network function in the 5G core
responsible for authenticating UEs during registration and providing security services. It
10 generates and verifies authentication vectors and tokens.
[0052] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] 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. 15
[0053] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
20 [0054] Network Exposure Function (NEF) [118] is a network function that exposes capabilities
and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0055] Network Repository Function (NRF) [120] is a network function that acts as a central
25 repository for information about available network functions and services. It facilitates the
discovery and dynamic registration of network functions.
[0056] Policy Control Function (PCF) [122] is a network function responsible for policy
control decisions, such as QoS, charging, and access control, based on subscriber information
30 and network policies.
[0057] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
12

[0058] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
5 [0059] User Plane Function (UPF) [128] is a network function responsible for handling user
data traffic, including packet routing, forwarding, and QoS enforcement.
[0060] Data Network (DN) [130] refers to a network that provides data services to user
equipment (UE) in a telecommunications system. The data services may include but are not
10 limited to Internet services, private data network related services.
[0061] Fig. 2 illustrates an exemplary block diagram of a computing device [1000] (or as used herein, computer system [1000]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an
15 implementation, the computing device [1000] may also implement a method for supporting
self-organising network (SON) utilising the system. In another implementation, the computing device [1000] itself implements the method for supporting self-organising network (SON) 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.
20
[0062] The computing device [1000] may include a bus [1002] or other communication 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 include a main
25 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 storage media accessible to
30 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].
13

[0063] 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
5 tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) 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
10 trackball, or cursor direction keys, for communicating direction information and command
selections to the processor [1004], and for controlling cursor movement on the display [1012]. This 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.
15 [0064] 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 implementation, the techniques herein are performed by the computing device [1000] in response to the processor
20 [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]. 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 implementations of the present disclosure, hard-wired circuitry
25 may be used in place of or in combination with software instructions.
[0065] The computing device [1000] also may include a communication interface [1018]
coupled to the bus [1002]. The communication interface [1018] provides a two-way data
communication coupling to a network link [1020] that is connected to a local network [1022].
30 For example, the communication interface [1018] may be an integrated services digital network
(ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [1018] 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
14

implementation, the communication interface [1018] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.
5 [0066] 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 [1018].
In the Internet example, a server [1030] might transmit a requested code for an application
program through the Internet [1028], the ISP [1026], the local network [1022], the host [1024]
and the communication interface [1018]. The received code may be executed by the processor
10 [1004] as it is received, and/or stored in the storage device [1010], or other non-volatile storage
for later execution.
[0067] Referring to Figure 3, an exemplary block diagram of a system [300] for supporting self-organising network (SON), is shown, in accordance with the exemplary implementations
15 of the present disclosure. The system [300] comprises at least one storage unit [302], at least
one transceiver unit [304], at least one execution unit [306], and at least one data collector function (DCF) module [308]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other.
20 Also, in Fig. 3 only a few units are shown, however, the system [300] may comprise multiple
such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a server or a network entity.
25 [0068] The system [300] is configured for supporting self-organising network (SON), with the
help of the interconnection between the components/units of the system [300].
[0069] The system [300] for supporting self-organising network (SON) comprises a MV-SON
module [301]. The MV-SON module [301] further comprises the storage unit [302] and the
30 transceiver unit [304]. The transceiver unit [304] configured to receive, via a collation platform,
one or more types of data to store the one or more types of data in the storage unit [302]. For this purpose, the collation platform may be configured to receive the one or more types of data from one or more elementary management systems. It is to be noted that each of the one or more elementary management systems may belong to a separate vendor. Here, vendor may
15

refer to an original equipment manufacturer (OEM) for base stations. Each vendor may have
its own elementary management system to manage its own base stations. Also, a collation
platform may collect data from all different EMSs belonging to different vendors. Then data is
also in varying format, and the collation platform after collecting the data, creates the data in a
5 unified format. In an implementation, the one or more types of data comprises a data received
from at least one of a configuration management (CM) module, a performance management (PM) module, and a fault management (FM) module, a data received from a site database (for example, status of sites/cells, approved or planned sites, site deployment status (such as On-Air, Planned, or Nominal site), configuration details of the existing sites, traffic of the existing
10 sites) of each vendor among the one or more vendors, and a data received from a cell database
of each vendor among the one or more vendors. Also, in an implementation, the collation platform may have access to the site database, a neighboring cell database, a configuration management database, alarms, and performance counters. In an exemplary implementation, the MV-SON module [301] is integrated with the collation platform. Also here, the FM module
15 may be an entity that captures all fault data (for example, alarm data including raise alarm,
clear alarm) from EMSs where the EMSs collect from RAN nodes, the CM module may be an entity that allows setting configuration change request, getting configuration data (for example, radio frequency (RF) parameters such as power, neighbor cell data, aggressor/victims’ cells, antenna tilt, antenna height and azimuth at each node) from EMSs, and the PM module may be
20 an entity that is used for pulling performance counters.
[0070] Also, in an implementation, the system comprises a data collector function (DCF) module [308]. In this implementation, the transceiver unit [304] may be configured to receive the data from the configuration management (CM) module via the DCF module [308]. Further,
25 the DCF module [308] may be configured to: collect, via the collation platform, one or more
of a serving cell data, and a neighbour list parameters data from the CM module. Here, the DCF module [308] is capable of end to end extraction, transformation and loading (ETL) of received data from the collation platform to the MV-SON module [301] in near to real time. The DCF module [308] has the capability to parallel process the data from multiple upstream
30 nodes and provide the transformed data to multiple downstream nodes. Also, the serving cell
data may comprise physical parameters of base stations, such as base station identifier, physical cell identity, received signal strength indicator, internet protocol (IP) address, etc. Further, the neighbour list parameters data may comprise a data related to neighbouring cells, such as neighbour relation table (NBR), where each node holds a table of detected neighbour cells
16

which are used in connection with handovers), and the neighbour list parameter further
comprise cell identities such as Type allocation code (TAC), absolute radio-frequency channel
number (ARFCN), physical cell indicator (PCI), new radio cell global identity (NRCGI)
(mobile country codes (MCC) and mobile network codes (MNC), gNodeB identity (gnb_id),
5 gnb_len, cell identity (cell_id)). In an exemplary implementation, the DCF module [308]
collects the data from the collation platform at a pre-defined frequency, for example, the DCF module [308] may collect data from the collation platform on a daily basis, a weekly basis, a monthly basis etc. Further, the DCF module [308] may be configured to process the collected data to change the format of the collected data to generate a processed data. Since the data may
10 be collected from many different entities, the data may be present in different formats and it
may be needed for the DCF [308] to provide the data in a unified format that can be used by the desired unit, say, MV-SON module [301]. Further, the DCF module [308] may be configured to provide the processed data to the transceiver unit [304]. The processed data, for example, may be in a unified format, such as JavaScript Object Notation (JSON) format.
15
[0071] In some implementations, the MV-SON module [301] may ask for data from the collation platform collected from the configuration management module, the performance management module, and the fault management module or any such modules and other units, at respective pre-defined frequency such as at an hourly basis or daily basis or for any
20 determined time period, or on-demand as and when needed. Also, in an implementation, only
the use case specific data may be fetched by the MV-SON module [301] from the collation platform.
[0072] Further, the execution unit [306] is connected to at least the transceiver unit [304]. The
25 execution unit [306] may be configured to execute one or more self-organizing network (SON)
algorithms in one of an open loop mode of operation and a closed loop mode of operation,
wherein the one or more SON algorithms are executed based on the one or more types of data.
Also, the one or more SON algorithms may be executed based on the one or more types of
data.
30
[0073] In an implementation, in the open loop mode of operation, the execution unit [306] may
be configured to execute the one or more SON algorithms. After execution, no changes may
be made automatically. Further, in this mode of operation i.e., the open loop mode of operation,
the execution unit [306] may be configured to provide a detailed report based on the execution
17

of the one or more SON algorithms. This detailed report may comprise current findings as well
as recommended changes. Here, the recommended changes are related to configuration of a
cell, and the current finding may be the current physical cell identifier (PCI) for that cell. Also,
in an example, if a SON algorithm is related to PCI optimization, then an optimal PCI is
5 selected for the cell, and that is provided as a recommendation.
[0074] Also, in an implementation, in the closed loop mode of operation, the execution unit [306] may be configured to: execute the one or more SON algorithms. Further, in this mode of operation i.e., the closed loop mode of operation, the execution unit [306] may be configured
10 to make changes automatically, to one or more configuration parameters based on the one or
more SON algorithms. For example, when PCI optimization is executed in closed loop, the optimal PCI for a cell is recommended and automatically transmitted to the collation platform which further transmits the optimal PCI for the cell to respective EMS, which in turn transmits the optimal PCI for the cell further to the node, and the node is configured with that PCI.
15 Further, in this mode of operation, the execution unit [306] may be configured to provide a
detailed report based on the execution of the one or more SON algorithms. This detailed report may comprise current findings as well as recommended changes. Also, in an exemplary implementation, in closed loop mode of operation, the execution unit [306] may ask the collation platform to provide on-demand pre-post comparison of a pre-configured key
20 performance indicators (KPIs). For example, after modification of the PCI, the KPI values of
before the modification and after the modification are captured in the report. For this purpose, in this exemplary implementation, the execution unit [306] may be further configured to send, to the collation platform, a request for providing a comparison report of one or more pre-configured key performance indicators (KPIs). Further, in this exemplary implementation, the
25 execution unit [306] may be further configured to receive, from the collation platform, the
comparison report of the one or more pre-configured KPIs based on the request.
[0075] Further, the execution unit [306] may be configured to generate an output based on the
execution of the SON algorithms, for supporting self-organising network (SON). The output
30 may comprise a summary of current attributes of cells, such as SAP ID, and potential PCI value
for the cell, a score given besides each PCI value based on which the PCI may be selected (for example, the lowest PCI may be selected for the cell).
18

[0076] Further, the transceiver unit [304] may be configured to transmit the output to the
collation platform via the DCF module [308] for further sharing the output with one or more
elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a
separate vendor among one or more vendors. The EMSs may further execute the configuration
5 with their respective nodes.
[0077] Referring to Figure 4, an exemplary method flow diagram [400] for supporting self-
organising network (SON), in accordance with exemplary implementations of the present
disclosure is shown. In an implementation the method [400] is performed by the system [300].
10 Further, in an implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0078] At step 402, the method [400] for supporting self-organising network (SON) comprises
15 receiving, by a transceiver unit [304] at a multi-vendor self-organising network (MV-SON)
module [301] via a collation platform, one or more types of data for storing the one or more types of data in a storage unit [302]. For this purpose, the collation platform may be configured to receive the one or more types of data from one or more elementary management systems. It is to be noted that each of the one or more elementary management systems may belong to a
20 separate vendor. Here, vendor may refer to an original equipment manufacturer (OEM) for
base stations. Each vendor may have its own elementary management system to manage its own base stations. Also, a collation platform may collect data from all different EMSs belonging to different vendors. Then data is also in varying format, and the collation platform after collecting the data, creates the data in a unified format. In an implementation, the one or
25 more types of data comprises a data received from at least one of a configuration management
(CM) module, a performance management (PM) module, and a fault management (FM) module, a data received from a site database of each vendor among the one or more vendors, and a data received from a cell database of each vendor among the one or more vendors. Also, in an implementation, the collation platform may have access to the site database, a neighboring
30 cell database, a configuration management database, alarms, and performance counters. In an
exemplary implementation, the MV-SON module [301] is integrated with the collation platform. Also here, the FM module may be an entity that captures all fault data (for example, alarm data including raise alarm, clear alarm) from EMSs where the EMSs collect from RAN
19

nodes, the CM module may be an entity that allows setting configuration change request,
getting configuration data (for example, radio frequency (RF) parameters such as power,
neighbor cell data, aggressor/victims’ cells, antenna tilt, antenna height and azimuth at each
node) from EMSs, and the PM module may be an entity that is used for pulling performance
5 counters.
[0079] Also, in an implementation, the method comprises receiving, by the transceiver unit [304], the data from the CM module via a data collector function (DCF) module [308]. For this, the method may further comprise collecting by the DCF module [308] via the storage unit
10 [302], one or more of a serving cell data, and a neighbour list parameters data from the CM
module. Here, the DCF module [308] is capable of end to end extraction, transformation and loading (ETL) of received data from the collation platform to the MV-SON module [301] in near to real time. DCF module [308] has the capability to parallel process the data from multiple upstream nodes and provide the transformed data to multiple downstream nodes. Also, the
15 serving cell data may comprise physical parameters of base stations, such as base station
identifier, physical cell identity, received signal strength indicator, internet protocol (IP) address, etc. Further, the neighbour list parameters data may comprise a data related to neighbouring cells, such as NBR (each node holds a table of detected neighbour cells which are used in connection with handovers), and the neighbour list parameter further comprise tac,
20 absolute radio-frequency channel number (ARFCN), physical cell indicator (PCI), new radio
cell global identity (NRCGI) (mobile country codes (MCC) and mobile network codes (MNC), gNodeB identity (gnb_id), gnb_len, cell identity (cell_id)). In an exemplary implementation, the DCF module [308] collects the data from the collation platform at a pre-defined frequency, for example, the DCF module [308] may collect data from the collation platform on a daily
25 basis, a weekly basis, a monthly basis etc. Further, the method may comprise processing, by
the DCF module [308], the collected data to change the format of the collected data to generate a processed data. Since the data may be collected from many different entities, the data may be present in different formats and it may be needed for the DCF [308] to provide the data in a unified format that can be used by the desired unit, say, MV-SON module [301]. Further, the
30 method may comprise providing, by the DCF module [308] to the transceiver unit [304], the
processed data. The processed data, for example, may be in a unified format, such as JavaScript Object Notation (JSON) format.
20

[0080] In some implementations, the MV-SON module [301] may ask for data from the
collation platform collected from the configuration management module, a performance
management module, and a fault management module or any such modules and other units, at
respective pre-defined frequency such as at an hourly basis or daily basis or for any determined
5 time period, or on-demand as and when needed. Also, in an implementation, only the use case
specific data may be fetched by the MV-SON module [301] from the collation platform.
[0081] Further, at step 404, the method comprises executing, by an execution unit [306] at the
MV-SON module [301], one or more self-organizing network (SON) algorithms in one of an
10 open loop mode of operation and a closed loop mode of operation, wherein the one or more
SON algorithms are executed based on the one or more types of data. Also, the one or more SON algorithms may be executed based on the one or more types of data.
[0082] In an implementation, the open loop mode of operation comprises executing, by the
15 execution unit [306], the one or more SON algorithms. After execution, no changes may be
made automatically. Further, in this mode of operation, the execution unit [306] may provide
a detailed report based on the execution of the one or more SON algorithms. This detailed
report may comprise current findings as well as recommended changes. Here, the
recommended changes are related to configuration of a cell, and the current finding may be the
20 current physical cell identifier (PCI) for that cell. Also, in an example, if a SON algorithm is
related to PCI optimization, then an optimal PCI is selected for the cell, and that is provided as a recommendation.
[0083] Also, in an implementation, in the closed loop mode of operation, the method comprises
25 executing, by the execution unit [306], one or more SON algorithms. Further, in this mode of
operation, the method further comprises making changes automatically, by the execution unit
[306], to one or more configuration parameters based on the one or more SON algorithms. For
example, when PCI optimization is executed in closed loop, the optimal PCI for a cell is
recommended and automatically transmitted to the collation platform which further transmits
30 the optimal PCI for the cell to respective EMS, which in turn transmits the optimal PCI for the
cell further to the node, and the node is configured with that PCI. Further, in this mode of
operation, the execution unit [306] may provide a detailed report based on the execution of the
one or more SON algorithms. This detailed report may comprise current findings as well as
recommended changes. Also, in an exemplary implementation, in closed loop mode of
35 operation, the execution unit [306] may ask the collation platform to provide on-demand pre-
21

post comparison of a pre-configured key performance indicators (KPIs). For example, after
modification of the PCI, the KPI values of before the modification and after the modification
are captured in the report. For this purpose, in this exemplary implementation, the execution
unit [306] may send, to the collation platform, a request for providing a comparison report of
5 one or more pre-configured key performance indicators (KPIs). Further, in this exemplary
implementation, the execution unit [306] may be further configured to receive, from the collation platform, the comparison report of the one or more pre-configured KPIs based on the request.
10 [0084] Further, at step 406, the method of the present disclosure comprises generating, by the
execution unit [306] at the MV-SON module [301], an output based on the execution of the SON algorithms, for supporting self-organising network (SON). The output may comprise a summary of current attributes of cells, such as SAP ID, and potential PCI value for the cell, a score given besides each PCI value based on which the PCI may be selected (for example, the
15 lowest PCI may be selected for the cell).
[0085] Further, at step 408, the method of the present disclosure comprises transmitting, by the
transceiver unit [304] at the MV-SON module [301], the output to the collation platform via
the DCF module [308] for further sharing the output with one or more elementary management
20 systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among
one or more vendors. The EMSs may further execute the configuration with their respective nodes.
[0086] Referring to Figure 5, an exemplary scenario schematic diagram of a system [500] for
25 supporting self-organising network (SON), in accordance with exemplary implementations of
the present disclosure is shown. For clarity of explanation, the reference numerals of Figure 3
may be used in conjunction while explaining the features of Figure 5. In an exemplary
implementation of the invention, as shown in Figure 5, while deploying multivendor in a
network, each vendor has its own self-organising network (SON) algorithms for each SON use
30 cases. These are mentioned as A1, A2, A3, A4 and A5 in the Figure 1. All the SON algorithms
(A1, A2, A3, A4 and A5) may be executed by the MV-SON module [301] which is commonly used to implement all the SON algorithms, so that it can be uniform for across vendors. In an exemplary implementation, the algorithms may be executed by the execution unit [306]. In an example, the A1 may be for an initial PCI (physical cell identity) allocation and optimization,
22

the A2 may be for a RACH (random access channel) optimization, the A3 may be for a HO
(handover) parameters optimization, the A4 may be for a mobility robustness optimization, the
A5 may be for an auto tilt optimization, etc. A person skilled in the art would appreciate that
the above set of algorithms (A1, A2, A3, A4, and A5) are only exemplary and the disclosure is
5 not limited thereto. Also, any number of algorithms may be present for implementing the
features of the present disclosure. Also, in some implementations, one or more algorithms may be generic algorithms independent of any vendor. Also, in an implementation, as shown in Figure 5, the MV-SON module [301] may collect data from either of the collation platform, the elementary management system (EMS)/network management system, or the network
10 nodes, for example, the base stations directly or via the collation platform which may be
connected to the EMSs of various vendors. Also, each of the EMSs may belong to a separate vendor and may be connected to one or more base station entities (such as gNodeB, eNodeB, or any other such entity as may be useful for implementing the features of the present disclosure) of that vendor. Also, in an implementation, the MV-SON module [301] may be
15 directly connected to one or more EMSs of one or more vendors via an interface such as a
Representational State Transfer Application Programming Interface (REST API) / Javascript Object Notation (JSON) or Hypertext Transfer Protocol (HTTP) interface.
[0087] The present disclosure further discloses a non-transitory computer readable storage
20 medium storing instructions for supporting self-organising network (SON), the instructions
include executable code which, when executed by one or more units of a system [300], causes:
a transceiver unit [304] of the system [300] to receive, via a collation platform, one or more
types of data to store the one or more types of data in a storage unit [302]; an execution unit
[306] of the system [300] to execute one or more self-organizing network (SON) algorithms in
25 one of an open loop mode of operation and a closed loop mode of operation, wherein the one
or more SON algorithms are executed based on the one or more types of data, and generate an
output based on the execution of the SON algorithms, for supporting self-organising network
(SON); and the transceiver unit [304] to transmit the output to the collation platform for further
sharing the output with one or more elementary management systems (EMSs), wherein each
30 of the one or more EMSs belongs to a separate vendor among one or more vendors.
[0088] The present disclosure further discloses a user equipment (UE) comprising at least a user interface (UI). The UI may provide a report on a self-organising network (SON) among a
23

plurality of SONs, wherein the report is generated by a system [300] based on: (a) receiving,
by a transceiver unit [304] at the MV-SON module [301] via a collation platform, one or more
types of data for storing the one or more types of data in a storage unit [302]; (b) executing, by
an execution unit [306] at the MV-SON module [301], one or more self-organizing network
5 (SON) algorithms in one of an open loop mode of operation and a closed loop mode of
operation, wherein the one or more SON algorithms are executed based on the one or more
types of data; (c) generating, by the execution unit [306] at the MV-SON module [301], an
output based on the execution of the SON algorithms, for supporting the self-organising
network (SON); and (d) transmitting, by the transceiver unit [304] at the MV-SON module
10 [301], the output to the collation platform for further sharing the output with one or more
elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.
[0089] As is evident from the above, the present disclosure provides a technically advanced
15 solution for supporting self-organising network (SON). Implementing the features of the
present disclosure enables one to obtain a solution for supporting self-organising network that
is able to optimize networks of multiple vendors through a central server, i.e., the MV-SON
module. Further, the solution as disclosed in the present disclosure overcomes the issue of
compatibility among systems from various vendors. Further, the solution as disclosed in the
20 present disclosure is developed using a common database for all vendors, and the same
algorithms can be used for all vendors uniformly. Therefore, the need for extra development efforts for different vendors is eliminated.
[0090] While considerable emphasis has been placed herein on the disclosed
25 implementations, it will be appreciated that many implementations can be made and that many
changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations 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. 30
24

We Claim:
1. A system for supporting self-organising network (SON), the system comprises a MV-
SON module [301], the MV-SON module [301] further comprises:
- a transceiver unit [304] configured to receive, via a collation platform, one or more types of data to store the one or more types of data in a storage unit [302]; and
- an execution unit [306] connected to at least the transceiver unit [304], the execution unit [306] configured to:
o execute one or more SON algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data, and o generate an output based on the execution of the SON algorithms, for supporting the self-organising network (SON), and
the transceiver unit [304] further configured to transmit the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.
2. The system as claimed in claim 1, wherein the one or more types of data comprises a data received from at least one of a configuration management (CM) module, a performance management (PM) module, and a fault management (FM) module, a data received from a site database of each vendor among the one or more vendors, and a data received from a cell database of each vendor among the one or more vendors.
3. The system as claimed in claim 2, the system comprising a data collector function (DCF) module [308] wherein the transceiver unit [304] is configured to receive the data from the configuration management (CM) module via the DCF module [308].
4. The system as claimed in claim 3, wherein the DCF module [308] is configured to:

- collect, via the collation platform, one or more of a serving cell data, and a neighbour list parameters data from the CM module;
- process the collected data to change a format of the collected data to generate a processed data; and

- provide the processed data to the transceiver unit [304].
5. The system as claimed in claim 1, wherein in the open loop mode of operation, the
execution unit [306] is configured to:
- execute the one or more SON algorithms; and
- provide a detailed report based on the execution of the one or more SON algorithms.
6. The system as claimed in claim 1, wherein in the closed loop mode of operation, the
execution unit [306] is configured to:
- execute the one or more SON algorithms;
- make changes automatically, to one or more configuration parameters based on the one or more SON algorithms; and
- provide a detailed report based on the execution of the one or more SON algorithms.
7. The system as claimed in claim 6, wherein the execution unit [306] is further configured
to:
- send, to the collation platform, a request for providing a comparison report of one or more pre-configured key performance indicators (KPIs); and
- receive, from the collation platform, the comparison report of the one or more pre-configured KPIs based on the request.
8. A method for supporting self-organising network (SON), the method comprising:
- receiving, by a transceiver unit [304] at a multi-vendor self-organising network (MV-SON) module [301] via a collation platform, one or more types of data for storing the one or more types of data in a storage unit [302];
- executing, by an execution unit [306] at the MV-SON module [301], one or more self-organizing network (SON) algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data;

- generating, by the execution unit [306] at the MV-SON module [301], an output based on the execution of the SON algorithms, for supporting the self-organising network (SON); and
- transmitting, by the transceiver unit [304] at the MV-SON module [301], the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.

9. The method as claimed in claim 8, wherein the one or more types of data comprises a data received from at least one of a configuration management (CM) module, a performance management (PM) module, and a fault management (FM) module, a data received from a site database of each vendor among the one or more vendors, and a data received from a cell database of each vendor among the one or more vendors.
10. The method as claimed in claim 9, wherein the method comprises receiving, by the transceiver unit [304], the data from the CM module via a data collector function (DCF) module [308].
11. The method as claimed in claim 10, the method further comprising:

- collecting by the DCF module [308] via the storage unit [302], one or more of a serving cell data, and a neighbour list parameters data from the CM module;
- processing, by the DCF module [308], the collected data to change a format of the collected data to generate a processed data; and
- providing, by the DCF module [308] to the transceiver unit [304], the processed data.
12. The method as claimed in claim 8, wherein the open loop mode of operation comprises:
- executing, by the execution unit [306], the one or more SON algorithms; and
- providing, by the execution unit [306], a detailed report based on the execution of the one or more SON algorithms.
13. The method as claimed in claim 8, wherein the closed loop mode of operation
comprises:

- executing, by the execution unit [306], one or more SON algorithms;
- making changes automatically, by the execution unit [306], to one or more configuration parameters based on the one or more SON algorithms; and
- providing, by the execution unit [306], a detailed report based on the execution of the one or more SON algorithms.
14. The method as claimed in claim 13, the method further comprising:
- sending, by the execution unit [306] to the collation platform, a request for providing a comparison report of one or more pre-configured key performance indicators (KPIs); and
- receiving, by the execution unit [306] from the collation platform, the comparison report of the one or more pre-configured KPIs based on the request.
15. A user equipment (UE) comprising a user interface (UI), wherein the UE is configured
to provide a report on a self-organising network (SON) among a plurality of SONs,
wherein the report is generated by a system [300] based on:
- receiving, by a transceiver unit [304] at a MV-SON module [301] via a collation platform, one or more types of data for storing the one or more types of data in a storage unit [302];
- executing, by an execution unit [306] at the MV-SON module [301], one or more SON algorithms in one of an open loop mode of operation and a closed loop mode of operation, wherein the one or more SON algorithms are executed based on the one or more types of data;
- generating, by the execution unit [306] at the MV-SON module [301], an output based on the execution of the SON algorithms, for supporting the self-organising network (SON); and
- transmitting, by the transceiver unit [304] at the MV-SON module [301], the output to the collation platform for further sharing the output with one or more elementary management systems (EMSs), wherein each of the one or more EMSs belongs to a separate vendor among one or more vendors.