System and method for optimizing physical cell identity configuration in wireless communication network

Abstract

SYSTEM AND METHOD FOR OPTIMIZING PHYSICAL CELL IDENTITY CONFIGURATION IN WIRELESS COMMUNICATION NETWORK 5 Disclosed is a system (240) and method (400) for optimizing Physical Cell Identity (PCI) configuration in a wireless communication network. The method comprises collecting configuration data and performance metrics from one or more cells within a defined coverage area. The method further comprises processing the collected 10 configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of a PCI collision or a PCI confusion. The method further comprises determining a target PCI value for each identified cell based on a predefined selection criteria and executing a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI 15 configuration in the wireless communication network.

Description

SYSTEM AND METHOD FOR OPTIMIZING PHYSICAL CELL IDENTITY CONFIGURATION IN WIRELESS COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for optimizing Physical Cell Identity (PCI) configuration in a wireless communication network.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] With technological advancements in the field of telecommunications, cellular networks are experiencing an exponential increase in data demand. In cellular network systems, with increase in number of users and their requirements for data intensive applications, there is a strong emphasis on maximizing network throughput and ensuring uninterrupted Quality of Service (QoS) to the users. Thus, achieving efficient utilization of network resources is critical to enhance user experience and address increasing network performance expectations.

[0004] To this end, one of the primary challenges faced by traditional cellular network systems is limited availability of frequencies within a spectrum. To meet the requirements of the users, the frequencies are reused across different cells. This reusing of the frequencies introduces complications, particularly when neighboring or overlapping cells operate on same frequency. Further, reuse of the frequencies leads to interference problems between the cells. For instance, if two adjacent ornearby cells use the same frequency, the signal transmitted in one cell may interfere with the other. The interference disrupts communication and reduces the signal quality experienced by the users, resulting in degraded QoS, increased call drops and reduced data throughput. The interference is particularly problematic during handovers between the cells, where the user device must seamlessly transition from one cell to another cell without losing connectivity.

[0005] In existing cellular networks, mechanisms to mitigate frequency interference rely on Physical Cell Identity (PCI) for ensuring efficient wireless communication. The PCI is a unique identifier assigned to each cell within the cellular network, enabling proper cell identification and facilitating seamless communication between mobile devices and network elements. Efficient PCI allocation ensures reduced interference, enhanced network performance, and better resource management. However, as cellular networks evolve, managing PCIs has become increasingly complex due to rapid expansion of network deployments and integration of advanced technologies.

[0006] Further, rise of heterogeneous networks comprising various macro cells, micro and femtocells has led to densely populated cellular environments. The total number of available PCIs is insufficient to ensure unique assignments across large areas, leading to inevitable reuse of the PCIs across different cells. However, improper reuse of the PCIs results in severe network performance issues, including PCI collisions and PCI confusions.

[0007] A PCI collision (referring to FIG. 1A) occurs when two or more neighboring (Nbr) cells are assigned the same PCI, resulting in signal interference and degraded network performance. The PCI collisions are particularly problematic in high density urban areas, where the cells often overlap due to limited frequency reuse.

[0008] Additionally, a PCI confusion arises (referring to FIG. 1B) when a serving cell detects multiple Nbr cells assigned the same PCI, making it difficult for the user devices to determine which Nbr cell the PCI corresponds to.

[0009] Heretofore, existing PCI assignment techniques have struggled to address these problems effectively in densely deployed heterogeneous networks. Further, with advent of Fifth Generation (5G) technology, the PCI management problem has further increased. Particularly, in Non-Stand Alone (NSA) deployment modes, Evolved Universal Terrestrial Radio Access (E-UTRA) and New Radio (NR) technologies coexist under E-UTRA-NR Dual Connectivity (EN-DC) architecture. This coexistence allows simultaneous connectivity between Long Term Evolution (LTE) based Evolved NodeBs (eNBs) and New Radio based Next Generation Node Bs (gNBs) within a single network, creating a densely populated environment with the overlapping cells, thereby increasing the risk of the PCI collisions and the PCI confusions.

[0010] Furthermore, the existing PCI assignment techniques rely on static or semi static assignment techniques, which are insufficient for handling a dynamic nature of the modern cellular networks. The existing PCI assignment techniques fail to account for changes in network topology, user behavior, and traffic patterns, resulting in suboptimal PCI assignment. Moreover, the existing PCI assignment techniques lack real time adaptability, making it difficult to address the PCI conflicts as they arise.

[0011] Thus, to overcome aforementioned challenges and limitations associated with the existing PCI assignment techniques, there lies a need for a system and a method that can optimize PCI allocation in a wireless communication network.SUMMARY

[0012] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0013] In an embodiment, disclosed herein is a method for optimizing Physical Cell Identity (PCI) configuration in a wireless communication network. The method comprises collecting, by a receiving module, configuration data and performance metrics from one or more cells within a defined coverage area. The method further comprises processing, by a processing module, the collected configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of a PCI collision or a PCI confusion. The method further comprises further determining, by a PCI selection module, a target PCI value for each identified cell based on a predefined selection criteria and executing, by an execution module, a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI configuration in the wireless communication network. In one or more implementations, the method further comprises creating, by a creation module, a PCI candidate list by excluding PCI values currently used by neighboring cells of the plurality of cells.

[0014] In one or more implementations, the configuration data includes at least one of cell identifiers, current PCI value associated with each cell, neighbour relation information, and the performance metrics include at least one of interference measurements, signal quality indicators, handover return statistics or call failure statistics.

[0015] In one or more implementations, executing the PCI update operation comprises transmitting a PCI change command to a network node associated with each identified cell and recording, based on an execution of the PCI change command, an updated PCI configuration status for each identified cell. The recording comprises storing the applied target PCI value, timestamp, and associated network node information in a PCI configuration database.

[0016] In one or more implementations, the method further comprises generating, by a generation module, a PCI candidate list by excluding one or more PCI values currently used by neighboring cells of the one or more cells.

[0017] In one or more implementations, determining the target PCI value comprises selecting a PCI value from a PCI candidate list that satisfies the predefined selection criteria.

[0018] In one or more implementations, the predefined selection criteria comprise at least one of a minimum PCI reuse distance, PCI availability within a predetermined set of PCI values, interference score, or historical PCI usage pattern.

[0019] In one or more implementations, the identifying at least one cell among the one or more cells exhibiting the PCI collision comprises detecting, by the processing module, one or more neighboring cells with same PCI values.

[0020] According to another aspect of the present disclosure, disclosed is a system for optimizing Physical Cell Identity (PCI) configuration in a wireless communication network. The system comprises a receiving module, a processing module, a PCI selection module, an execution module, a generation module. The receiving module is configured to collect configuration data and performance metrics from one or more cells within a defined coverage area. The processing module is configured to process the collected configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of a PCI collision or a PCI confusion. The PCI selection module is configured to determine a target PCI value for each identified cell based on a predefined selection criteria. The execution module configured to execute a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI configuration in the wireless communication network.BRIEF DESCRIPTION OF DRAWINGS

[0021] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead beingplaced upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0022] FIG. 1A and FIG. 1B illustrate schematic representation of a Physical Cell Identity (PCI) collision scenario and a PCI confusion scenario respectively in a multi-vendor communication environment, in accordance with prior arts.

[0023] FIG. 2 illustrates a block diagram depicting the multi-vendor communication environment, in accordance with an embodiment of the present disclosure.

[0017] FIG. 3 illustrates a block diagram depicting an architecture of a MultiVendor Self Organizing Network (MVSON) unit, in accordance with an example embodiment of the present disclosure.

[0024] FIG. 4 illustrates a detailed flowchart depicting a method for optimizing the PCI configuration in a wireless communication network.

[0025] FIG. 5 illustrates a detailed flowchart depicting an exemplary method for identifying PCI collisions and PCI confusions to perform target PCI optimization in the wireless communication network, in accordance with an embodiment of the present disclosure.

[0026] FIG. 6 illustrates a schematic block diagram of a computing system for optimizing the PCI configuration in the wireless communication network, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

[0027] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodimentsdisclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0028] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0029] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” or “some implementations” which may each refer to one or more or all of the same or different embodiments or implementations. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” or “in an implementation” refers to one embodiment or one implementation and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments ”. Further, the term, for example, “in one or more implementations” refers to “at least one implementation, or more than one implementation, or all implementations”.

[0030] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,”“have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0031] 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 can each be used independently of one another or with any combination of other features.

[0032] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0033] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0034] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0035] The present disclosure relates to a system and a method for managing and optimizing Physical Cell Identity (PCI) configuration in a multivendor network environment. An aspect of the present disclosure is to provide a system and a method that aims to minimize PCI conflicts by evaluating and adjusting PCI settings of cells based on their locations, and interaction with neighboring cells. Another aspect of the present disclosure is to provide a system and a method that may ensure optimized network performance and reduced interference between adjacent cells, thus enhancing an overall user experience by mitigating PCI collisions and PCI confusions.

[0036] Several key terms used in the description play pivotal roles in facilitating the system functionality. In order to facilitate an understanding of the description, the key terms are defined below.

[0037] The PCI- The PCI may refer to a unique identifier assigned to each cell in a Long-Term Evolution (LTE), NR (New Radio), or other 3 GPP-compliant wireless communication networks. The PCI is used by User Equipment (UE) for physical layer cell identification, synchronization, and initial access. PCI planning is essential to avoid collision or confusion with the neighboring cells.

[0038] Self-Organizing Network (SON) Parameters - The SON parameters may refer to a set of network configuration and optimization attributes that support dynamic self-configuration, self-optimization functionalities in the wireless communication networks. These parameters include, but are not limited to, PCI values, Neighbor Relations (NR list), handover thresholds, transmission power settings, frequency allocations, and mobility control parameters.

[0039] Key Performance Indicators (KPI) - The Key Performance Indicators (KPI) may refer to quantifiable performance metrics used to evaluate health, efficiency, and Quality of Service (QoS) of the wireless communication network.

[0040] GNodeB (gNB) - The gNB is a base station in 5G New Radio (NR) networks responsible for wireless communication between the UE and 5G core network.

[0041] ENodeB (eNB)- The eNB is a base station used in LTE (4G) networks, providing radio access and management functions between the UE and Evolved Packet Core (EPC).

[0042] PCI Collision - The PCI Collision may refer to a scenario in a wireless network where two or more physically adjacent cells are configured with the same PCI, leading to the UE being unable to distinguish between them. This may result in synchronization failures, access denial, or dropped connections.

[0043] PCI Confusion - The PCI Confusion may occur when two or more nonadjacent but overlapping cells with the same PCI are detected by the UE, causing ambiguity in cell identity during handover or reselection.

[0044] Configuration Management (CM) Data - The CM Data may refer to a set of static and semi-static parameters related to the configuration of network elements such as the gNBs or the eNBs. The static parameters may include, for example, cell identifiers, supported frequency bands, and bandwidth configuration. The semistatic parameters may include, for example, PCI values, neighbor cell relations, tracking area codes, frequency assignments, transmission power settings, and handover-related configuration parameters, which are configurable but do not change frequently during normal network operation.

[0045] Performance Management (PM) Data - The PM Data may refer to timebased statistical data collected from the network elements to measure performance, quality of service, and resource utilization. The PM data may include counters and measurements related to throughput, traffic volume, signal quality, call drops, and handover success / failure.

[0046] Intra-Frequency Adjacent Cells (Intra-FA Adjacent Cells) - The IntraFrequency Adjacent Cells may refer to neighboring cells operating on the same frequency (or frequency carrier) within a mobile network. These cells are typically part of the same frequency layer and are candidates for handover or cell reselection. In the context of the PCI optimization, conflicts and the interference arising fromintra-FA adjacent cells using the same PCI can lead to the collision or the confusion, severely affecting user experience.

[0047] Conflict score - The conflict score is a computed metric that quantifies a severity of a PCI-related conflict (the collision or the confusion) for a particular cell and is calculated based on various factors such as number of the neighboring cells using the same PCI, frequency and tier of conflict occurrences, signal overlap levels, or handover failures. Higher conflict scores indicate a greater likelihood of network degradation, and such scores are used to prioritize victim cells for PCI reallocation.

[0048] A Victim Cell- The victim cell is a gNB or eNB cell that has been identified as being adversely affected by the PCI collision or the confusion and has the conflict score exceeding a predefined threshold.

[0049] Handover Success Rate Performance Metric (HOSR PM) - The HOSR PM is the KPI derived from the PM data and represents a ratio of successful handovers to total handover attempts between the neighboring cells.

[0050] FIG. 1A and FIG. 1B illustrate schematic representation of a PCI collision scenario 100 and a PCI confusion scenario 100’ respectively in a multi-vendor communication environment, in accordance with prior arts.

[0051] Referring to FIG. 1A, a source cell 110 is at a distance X from an adjacent / first tier neighboring cell 120 (hereinafter may also be referred to as “a neighboring cell 120”). The source cell 110 and the neighboring cell 120 are using the same PCI (PCI:1) resulting in the signal interference and the overlapping coverage areas. The vendors typically prevent such PCI collisions by restricting neighbor cell addition when the same PCI and Absolute Radio-Frequency Channel Number (ARFCN) combination exist, but physical tier mapping complexities often bypass such constraints.

[0052] Referring to FIG. 1B, the source cell 110 using the PCI (PCI: 1) has a neighboring relation with an intermediate cell 140 with a different PCI (PC2). Thesource cell 110 has a second-tier neighboring cell 130 with same PCI (PCI: 1). The second-tier neighboring cell 130 is in neighboring relation with the intermediate cell 140. Thus, the PCI confusion scenarios may be detected using neighbour relations where second tier or nth tier neighbour from the source cell has same PCI and potential PCI confusion cases may be detected by increasing detection scope in terms of tier count. This PCI confusion scenario creates ambiguity during the handovers since the user device may get confused about which cell to connect to, based on conflicting PCI signals.

[0053] To solve the above problems, the present disclosure provides a methodology that enables systematic detection of problematic cells and selection of appropriate PCI values. The disclosed approach utilizes network configuration information and performance-related measurements to identify the cells affected by PCI conflicts, evaluate available PCI options, and cany' out controlled PCI updates. By integrating these operations into a coordinated procedure, the methodology ensures that PCI assignments are optimized in response to actual network conditions, thereby minimizing the interference, improving mobility robustness, and enhancing overall network performance.

[0054] Embodiments of the present disclosure will now be described below in detail with reference to the accompanying drawings. FIG. 2 and FIG. 6, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0055] FIG. 2 illustrates a block diagram depicting a multi-vendor communication environment 200 (hereinafter may also be referred to as a communication environment 200 or a communication system 200), in accordance with an embodiment of the present disclosure. The communication environment 200 includes a cognitive platform 210, multiple Element Management Systems (EMSs)220-1 through 220-n (n denotes the number of vendors in the communication environment) corresponding to a plurality of vendors, for example, (EMS)vendor 1 associated with vendor 1 depicted by reference numeral 220-1, (EMS)vendor 2 associated with vendor 2 depicted by reference numeral 220-2, and (EMS)vendornassociated with vendor n depicted by reference numeral 220-n. The multiple EMSs 220-1 through 220-n may also be collectively referred to as “vendor EMSs 220”, “EMSs 220”, and individually as “EMS 220” hereinafter. Each vendor EMS is configured to manage multiple nodes (e.g., base stations).

[0056] The vendor in the multi-vendor communication environment 200 may correspond to service providers who are responsible for fulfilling operational and technological requirements and may host services including but not limited thereto, invoicing, streamlining a company’s wireless services, and providing seamless internet access. The EMSs 220 are designed to monitor performance, configuration, and fault management of network element(s) deployed by the service providers, ensuring optimal network operation.

[0057] The communication environment 200 further includes Next Generation Node Bs (gNodeBs or gNBs) i.e., (gNBs)vendori associated with vendor 1 depicted by reference numeral 230-1, (gNBs)vendor 2 associated with vendor 2 depicted by reference numeral 230-2, and (gNBs)vendorn associated with vendor n depicted by reference numeral 230-n. The gNBs 230-1 through 230-n may also be collectively referred to as “gNBs 230” and individually as “gNB 230” or “base station 230” hereinafter.

[0058] The cognitive platform 210 integrates various modules responsible for overall coordination and management of the PCI allocation. The cognitive platform 210 communicates in real time with different network components to ensure optimized PCI management, especially in complex Fifth Generation (5G) network architectures involving multiple vendors. The cognitive platform 210 includes a site database 212, a Configuration Management (CM) module 214, a Performance Management (PM) module 216, and a Fault Management (FM) module 218.

[0059] The site database 212 stores detailed information about network infrastructure, including data about site locations, the PCI configurations, sector configurations, and network topology. The site database 212 acts as a reference for the entire communication environment 200 to track deployment and status of various network elements across the multiple vendors.

[0060] The CM module 214 is configured to maintain and provide the configuration data, including, but not limited to, existing PCI values associated with each cell, cell identifiers, tracking area codes, bandwidth settings, neighbor relations, and vendorspecific configuration parameters associated with each gNB. The PM module 216 may collect and aggregates performance indicators from the network, such as interference levels, handover return statistics, call failure statistics, signal quality measurements, load metrics, and KPI trends. The FM module 218 may monitor alarms, error notifications, and fault events generated by the gNBs and EMS systems, enabling detection of conditions such as PCI collision alarms, PCI confusion alarms, or abnormal neighbor-relation behaviors. Collectively, all the three modules provide a foundational operational data required by the MVSON unit 240 to accurately detect PCI-related issues and determine optimized PCI values.

[0061] The cognitive platform 210 communicates in two-way interactions with the vendor EMSs 220, which manage the equipment and configurations for various base station types across multiple vendors. Each EMS 220 handles the configuration and status monitoring of the gNBs 230 from specific vendors. The EMSs 220 are responsible for managing configurations of the network elements such as the gNBs 230 and providing operational data to the cognitive platform 210, including performance metrics and fault logs. The EMSs 220 are configured to receive updates from the cognitive platform 210 to adjust the PCI settings dynamically across vendor specific equipment.

[0062] The gNBs 230 and the EMSs 220 may communicate with each other via wireless communication protocols, e.g., Fifth Generation / New Radio Third Generation Partnership Project (5G / NR 3GPP) New Radio interface / access (NR),Long Term Evolution (LTE), LTE Advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.

[0063] The gNBs 230 deployed in the network are responsible for wireless communication with user devices. Each gNB is associated with a specific vendor EMS and operates within different frequency bands. The cognitive platform 210 facilitates communication between the EMSs 220 and the gNBs 230, ensuring optimal PCI assignments, avoiding the PCI collisions, and ensuring efficient communication between the gNBs 230 and the user devices.

[0064] The communication environment 200 further includes a Multi-Vendor Self Organizing Network (MVSON) unit 240 and a User Interface / Command Line Interface (UI / CLI) 250. The MVSON unit 240 may refer to a centralized network management entity configured to collect configuration, performance, and fault data from network elements provided by multiple vendors and to perform self-organizing functions, including analysis, optimization, and configuration updates across the wireless communication network.

[0065] In an embodiment, the MVSON unit 240 may integrate advanced algorithms, data processing capabilities, and optimization strategies to address network performance challenges. The MVSON unit 240 is configured to receive the CM data, the PM data and other network parameters, and further processes the data for the PCI optimization.

[0066] The MVSON unit 240 interacts with the cognitive platform 210 and utilizes the advanced algorithms to optimize the PCI allocation across the network. The MVSON unit 240 provides real time feedback to the cognitive platform 210, adjusting the PCI assignments based on network performance data and dynamically resolving the PCI conflicts.

[0067] The MVSON unit 240 starts with selecting the scope of sites where the PCI optimization process will run in close loop or open loop. A plurality of configurable parameters is then set for instance, data required to take decision and how the PCIissue will be identified. The PCI is then monitored as per logic and the PCIs of the problematic cells are changed and monitored and PCI changes steps are reiterated.

[0068] Thus, the MVSON unit 240 communicates with the cognitive platform 210 to obtain the data from the CM, PM and FM modules and interfaces with the vendorspecific EMS systems to transmit PCI change commands to the corresponding gNBs. In one or more embodiments, the MVSON unit 240 may be implemented on a server. As shown in FIG. 3, the MVSON unit 240 may include a set of communication modules 310, that collectively perform the PCI optimization operations described herein.

[0069] The UI / CLI 250 is communicatively coupled to the cognitive platform 210 and is configured to provide network administrators with real time alerts, network performance reports, and PCI optimization status.

[0070] Although FIG. 2 illustrates one example of the communication environment 200, various changes may be made to FIG. 2. For example, the communication environment 200 may include any number of gNBs and the EMSs in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 2 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0071] FIG. 3 illustrates a block diagram depicting an architecture of the MVSON unit 240, in accordance with an example embodiment of the present disclosure.

[0071] As shown in FIG. 3, the MVSON 240 unit includes a processor 302, a memory 304, a communication interface 306, an Input / Output (I / O) interface 308, and communication modules 310. Components of the MVSON unit 240 are coupled to each other via a first communication bus 300-2.

[0072] The processor 302 may include various processing circuitry and communicate with the memory 304, and the communication interface 306 via the first communication bus 300-2. The processor 302 is configured to executeinstructions or a set of instructions stored in the memory 304 to perform various processes. In an implementation, the processor 302 may also include the communication modules 310. Components of the communication modules 310 are coupled to each other via a second communication bus 300-4.

[0073] The processor 302 may include a general -purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, a Graphics-only Processing Unit such as a Graphics Processing Unit (GPU) or the like, a programmable logic device, or any combination thereof.

[0074] The memory 304 stores the set of instructions required by the processor 302 of for controlling its overall operations. The memory 304 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of Electrically Programmable Memories (EPROM) or Electrically Erasable and Programmable (EEPROM) memories. In addition, the memory 304 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as the memory 304 is nonmovable. In some examples, the memory 304 may be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 304 may be an internal storage unit or an external storage unit, cloud storage, or any other type of external storage.

[0075] The communication interface 306 may include an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface 306 is configured for communicating with external devices via networks.

[0076] The I / O interface 308 may include suitable logic, circuitry, interfaces, and / or codes that may be configured to receive input(s) and present (or display) output(s) on the MVSON unit 240. For example, the I / O interface 308 may have an inputinterface (not shown) and an output interface (not shown). The input interface may be configured to enable a user to provide input(s) to trigger (or configure) the MVSON unit 240 for performing data processing operation(s). Examples of the input interface may include, but are not limited to, a touch interface, a mouse, a keyboard, a motion recognition unit, a gesture recognition unit, a voice recognition unit, or the like. The output interface may be configured to display (or present) output(s) generated (or provided) by the MVSON unit 240. Examples of the output interface may include, but are not limited to, a digital display, an analog display, a touch screen display, an appearance of a desktop, and / or illuminated characters. Aspects of the present disclosure are intended to include or otherwise cover any type of the input interface and output interface in the I / O interface 308, including known, related art, and / or later developed technologies without deviating from the scope of the present disclosure.

[0077] The communication modules 310 comprises a receiving module 320, a processing module 330, a PCI selection module 340, an execution module 350, a generation module 360. The receiving module 320 is configured to collect the configuration data and the performance metrics from one or more cells within the defined coverage area. The processing module 330 is configured to process the collected configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of the PCI collision or the PCI confusion. The PCI selection module 340 is configured to determine the target PCI value for each identified cell based on the predefined selection criteria. The execution module 350 is configured to execute a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI configuration in the wireless communication network. In one or more implementations, the execution module 350 is configured to execute the PCI update operation by transmitting a PCI change command to the network node associated with each identified cell and recording, based on the execution of the PCI change command, an updated PCI configuration status for each identified cell. Therecording comprises storing the applied target PCI value, timestamp, and associated network node information in a PCI configuration database.

[0078] The communication modules 310 further comprises a generation module 360 configured to generate a PCI candidate list by excluding one or more PCI values currently used by neighboring cells of the one or more cells. In one or more embodiments, the PCI candidate list may be stored in the memory 304 associated with the MVSON unit 240 for processing by the PCI selection module 340. Further, the PCI selection module 340 is configured to determine the target PCI value by selecting the PCI value from the PCI candidate list that satisfies the predefined selection criteria.

[0079] Furthermore, to identify at least one cell among the one or more cells exhibiting the PCI collision, the processing module 330 is configured to detect one or more neighboring cells with same PCI values.

[0080] Although FIG. 3 illustrates one example of the MVSON unit 240, various changes may be made to FIG. 3. Further, various components in FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.

[0081] FIG.4 illustrates a detailed flowchart depicting a method 400 for optimizing the PCI configuration in the wireless communication network. FIG. 4 shows the flow chart of the method 400 performed by the communication modules 310 of the MVSON unit 240. The method 400 comprises a series of operation steps indicated by blocks 402 through 408 in the FIG. 4.

[0082] At step 402, the receiving module 320 is configured to collect the configuration data and the performance metrics from the one or more cells within the defined coverage area by interfacing with the EMSs 220. The configuration data may include at least one of the cell identifiers, the current PCI value associated with each cell, neighbour relation information, and the performance metrics include at least one of the interference measurements, the signal quality indicators, thehandover return statistics or the call failure statistics. In one or more embodiments, the configuration data and the performance metrics collection may be periodic or triggered by threshold violations in network performance. Fault information, including the alarms or error reports associated with PCI misconfigurations, may also be collected for the identification of the PCI collision and the PCI confusions.

[0083] At step 404, the processing module 330 is configured to process the collected data to identify at least one cell among the one or more cells exhibiting at least one of the PCI collision or the PCI confusion. The processing module 330 analyzes the neighbor relations and the PCI assignments to detect whether any cell shares the same PCI with an adjacent or first-tier neighbor, thereby indicating the PCI collision, or whether the cell detects the same PCI in multiple second-tier or extended neighbors, thereby indicating the PCI confusion. In one or more embodiments, the identification process may leverage inter-cell distance metrics, the signal measurement reports, or topology graphs to accurately pinpoint conflict regions. The cells flagged for the conflict are marked as “the identified cells” for subsequent optimization.

[0084] At step 406, the PCI selection module 340 is configured to determine the target PCI value for each identified cell based on the predefined selection criteria. The PCI candidate list is generated by the generation module 360 by excluding one or more PCI values currently used by the neighboring cells of the one or more cells. The PCI value is selected from the PCI candidate list that satisfies the predefined selection criteria. In a non-limiting example, when a full PCI value range includes values from 0 to 1007 (say) and the Nbr cells of the identified cell are already using the PCI values 10, 25, and 120, the PCI candidate list may be formed by excluding these PCI values and retaining the remaining available PCI values for further evaluation.

[0085] The predefined selection criteria may include at least one of a minimum PCI reuse distance, PCI availability within a predetermined set of PCI values, interference score, or historical PCI usage pattern. The PCI is selected thatminimizes potential for the interference while adhering to operator-defined constraints. Each identified cell is mapped to the target PCI to resolve the detected conflict. In a non-limiting example, the predefined selection criteria may include, for example, the minimum PCI reuse distance, wherein the PCI values used by the cells within a predefined geographical or logical distance are excluded. The PCI availability within the predetermined set of PCI values assigned to a specific frequency layer or vendor domain. The interference score associated with each PCI value, wherein the interference score may be derived from historical performance data, and the PCI values associated with lower interference scores are prioritized. The historical PCI usage patterns, wherein the PCI values previously associated with high interference are not prioritized. The target PCI value is selected from the PCI candidate list as the PCI value that best satisfies one or more of these predefined selection criteria.

[0086] At step 408, the execution module 350 is configured to execute the PCI update operation for each cell requiring reconfiguration. In this step, the PCI change command corresponding to the determined target PCI value is transmitted to corresponding network nodes associated with the identified cells. The execution module 350 dispatches the PCI change command to the network elements, such as gNodeBs (gNBs) or eNodeBs, depending on the radio access technology involved. The PCI change command instruct the corresponding nodes to apply the new PCI value for the respective cells. In an embodiment, the transmission of the PCI change commands may be done via standard network management interfaces, such as the O1 interface in O-RAN architecture or proprietary APIs provided by the vendor. After the update, the MVSON unit 240 may initiate a post-update monitoring phase, wherein the network is observed to verify the successful application of the new PCI value and to confirm that the PCI collision or the PCI confusion previously associated with the identified cell has been resolved. The updated configuration is also stored in the CM module 214 to maintain accurate and up-to-date PCI records. In one or more embodiments, the method 400 may be executed in an automatedclosed-loop manner or in the open-loop mode, depending on operator preferences and network configuration policies.

[0087] FIG. 5 illustrates a detailed flowchart depicting an exemplary method 500 for identifying the PCI collisions and the PCI confusions to perform target PCI optimization in the wireless communication network, in accordance with an embodiment of the present disclosure. FIG. 5 shows the flow chart of the method 500 performed by the MVSON unit / system 240. The method 500 comprises a series of operations indicated by steps 502 through 554. Although method 500 shows example blocks of steps 502 to 554, in some embodiments, the method 500 may include additional steps, fewer steps or steps in different order than those depicted in FIG. 5. In other embodiments, the steps 502 to 554 may be combined or may be performed in parallel.

[0088] At step 502, the method 500 comprises retrieving, by the system 240, SelfOrganizing Network (SON) parameters and the configuration data and the performance metrics for the selected sites. The data elements include the cell identifiers, current PCI allocations, neighbor relationships, and the performance metrics essential for understanding cell behavior and interactions within the multivendor network environment 200. In one or more embodiments, the SON parameters may include, but not limited to, PCI thresholds, PCI rules, PCI ranges, conflict detection parameters, execution permissions, vendor-specific constraints, and performance-based limits.

[0089] At step 504, the method 500 comprises selecting, by the system 240, a first source cell from a list of cells that have been identified for PCI conflict evaluation. The first source cell becomes the primary cell to undergo the PCI conflict evaluation process.

[0090] At step 506, the method 500 comprises determining, by the system 240, if the selected cell’s PCI is within a forbidden list. The forbidden list typically contains the PCI values that are restricted due to their potential to cause the interference in coverage areas. If the result of determination is YES, the method 500 proceeds tostep 508, while if the result of the determination is NO, the method 500 proceeds to step 510.

[0091] At step 508, if the selected cell is identified as using a forbidden PCI, the system 240 updates the cell status marking it as a “victim cell” indicating that the selected cell is susceptible to PCI conflict and the method 500 moves to reporting step.

[0092] At step 510, the method 500 comprises retrieving,, by the system 240 for each selected cell, location-based information on the Intra FA cells and extended neighbors up to a specified tier (for instance X tier), providing a spatial context for conflict evaluation. Additionally, the system 240 fetches relationship data corresponding to the intra-FA cells and the extended neighbors. This information helps the system 240 understand logical or functional relationships between the selected cell and its neighbors. The system 240 further retrieves the PCI values of the intra-FA cells within a defined maximum PCI collision distance (beyond which the PCI conflicts are less likely to occur).

[0093] At step 512, the method 500 comprises calculating, by the system 240, a PCI conflict score for the cell by analyzing three potential conflict detection criteria (i.e., the location, the relation, and the PCI values). Each criterion represents a potential cause of the interference, and their combined score provides an overall measure of the likelihood of the PCI conflicts.

[0094] At step 514, the method 500 comprises updating a report for the current cell, documenting the calculated conflict scores and values from the three conflict detection criteria tables. The report serves as a record for PCI conflict analysis.

[0095] At step 516, the method 500 comprises determining, by the system 240, whether the current cell is last one in the list designated for evaluation. If the result of determination is YES, the method 500 proceeds to step 520, while if the result of the determination is NO, the method 500 proceeds to step 518.

[0096] At step 518, upon a determination that the current cell is not the last one in the list, the system 240 selects a next cell in the list and repeats the conflict detection process for the selected next cell using the same configuration data and the performance metrics (from step 506).

[0097] At step 520, the method 500 comprises (upon completing the evaluation for all cells) generating, by the system 240, a PCI collision report for the current execution cycle, summarizing the conflict detection values for each cell analyzed.

[0098] At step 522, the method 500 comprises assessing, by the system 240, each cell to determine whether any cell’s final conflict score for all three conflict detection criteria exceeds the predefined threshold, indicating a high likelihood of the PCI conflict. If the result of determination is YES, the method 500 proceeds to step 526, while if the result of the determination is NO, the method 500 proceeds to step 524.

[0099] At step 524, the method 500 comprises creating, by the system 240, a calculation report containing values from the three conflict detection criteria tables for the current execution cycle. The calculation report includes detailed metrics and serves as a reference for PCI conflict analysis.

[0100] At step 526, the method 500 comprises marking, by the system 240, the one or more cells as the victim cells upon the determination that one or more cells exceed the threshold. The system 240 then refines the list of victim cells by excluding locked cells (cells that may not be modified) and duplicate cells. The cell with the highest conflict score is prioritized as a primary candidate for the victim cell.

[0101] At step 528, the method 500 comprises selecting, by the system 240, the first victim cell from the list of identified candidates initiating PCI reassignment process.

[0102] At step 530, the method 500 comprises preparing, by the system 240, a candidate PCI list score for the current victim cell, containing allowed PCIs sorted from lowest to highest conflict score.

[0103] At step 532, the method 500 comprises selecting, by the system 240, the candidate PCI with lowest conflict score as the first option for reassignment to the victim cell.

[0104] At step 534, the method 500 comprises determining, by the system 240, if the selected candidate PCI meets specific conditions: Modulo4 condition or Mod4 condition (a requirement for PCI selection); minimum tier restrictions (to avoid conflicts with immediate neighbors) and acceptable collision distance thresholds. The mod 4 condition refers to a rule used in the LTE networks for PCI planning to avoid the interference. The Mod4 condition may ensure that the neighboring cells do not use the PC's that would cause the signal interference during handovers or data transmission.

[0105] If the result of determination at step 534 is YES, the method 500 proceeds to step 538, while if the result of the determination is NO, the method 500 proceeds to step 536.

[0106] At step 536, the method 500 comprises selecting, by the system 240, the next candidate PCI and the evaluation at step 534 is repeated.

[0107] At step 538, the method 500 comprises assigning, by the system 240, the candidate PCI to the victim cell upon the determination that the conditions are satisfied. The method 500 then moves to step 540.

[0108] At step 540, the method 500 comprises updating, by the system 240, the report with information about the new candidate PCI selected for the victim cell.

[0109] At step 542, the method 500 comprises determining, by the system 240, whether the current victim cell is the last one in the list of cells needing PCI adjustment. If the result of determination is YES, the method 500 proceeds to step 546, while if the result of the determination is NO, the method 500 proceeds to step 544.

[0110] At step 544, the method 500 comprises selecting, by the system 240, the next victim cell and repeating the PCI reassignment process (from step 330 onwards).

[0111] At step 546, the method 500 comprises preparing, by the system 240, a final list of all victim cells, including their suggested PCIs based on the reassignment process.

[0112] At step 548, the method 500 comprises determining, by the system 240, whether the PCI changes are permissible in the current network operation mode (e.g. open loop mode or closed loop mode). If the result of determination is YES, the method 500 proceeds to step 552, while if the result of the determination is NO, the method 500 proceeds to step 550.

[0113] At step 550, the method 500 comprises generating, by the system 240, a final report detailing information including the conflict scores for all three conflict detection criteria, identified victim cells, suggested PCIs, the HOSR PM, status of the PCI changes, and the like.

[0114] At step 552, the method 500 comprises initiating, by the system 240, the PCI change command in the network and awaiting confirmation of successful PCI reassignment.

[0115] At step 554, the method 500 comprises generating, by the system 240, the final report detailing the information including the conflict scores for all three conflict detection criteria, the identified victim cells, the suggested PCIs, the HOSR PM, and the status of PCI changes. This report may also include additional metrics, such as before and after performance indicators include the KPIs pre and post PCI change to evaluate the impact of the PCI reassignment on network quality and stability.

[0116] FIG. 6 illustrates a schematic block diagram of a computing system 600 for optimizing the PCI configuration in the wireless communication network, in accordance with an embodiment of the present disclosure.T1

[0117] The computing system 600 includes a network 610, a network interface 620, a processor 630, an Input / Output (I / O) interface 640 and a non -transitory computer readable storage medium 650 (hereinafter may also be referred to as the “storage medium 650” or the “storage media 650”).

[0118] The network interface 620 includes wireless network interfaces such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA) or wired network interfaces such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers-864 (IEEE-864).

[0119] The processor 630 may include various processing circuitry and communicate with the storage medium 650 and the I / O interface 540. The processor 630 is configured to execute instructions stored in the storage medium 650 and to perform various processes. The processor 630 may include an intelligent hardware device including a general -purpose processor, such as, for example, and without limitation, the CPU, the AP, the dedicated processor, or the like, the graphics-only processing unit such as the GPU, a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. The processor 630 may be configured to execute computer-readable instructions 652 stored in the storage medium 650 to cause the server to perform various functions.

[0120] The storage medium 650 stores a set of instructions 652 required by the processor 630 for controlling its overall operations.

[0121] The storage media 650 may include an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, or the like. For example, the storage media 650 may include, but are not limited to, hard drives, floppy diskettes, optical disks, ROMs, RAMs, EPROMs, EEPROMs, flash memory, magnetic or optical cards, solid-state memory devices, or other types of physical media suitable for storing electronic instructions. In one or more implementations, the storage media 650 includes a Compact Disk-Read OnlyMemory (CD-ROM), a Compact Disk-Read / Write (CD-R / W), and / or a Digital Video Disc (DVD).

[0122] In one or more implementations, the storage medium 650 stores computer program code configured to cause the computing system 600 to perform at least a portion of the processes and / or methods. Accordingly, in at least one embodiment, the computing system 600 performs the method for the optimizing the PCI configuration in the wireless communication network.

[0123] Now, referring to the technical abilities and advantageous effect of the present disclosure, the embodiments disclosed herein provide an automated detection of the PCI collisions and the PCI confusions by simultaneously analyzing the configuration data, performance metrics, and fault management data received from heterogeneous EMSs. The disclosed system enables accurate conflict detection across the gNBs deployed by different vendors.

[0124] Another technical advantage is the capability of the system to perform dynamic PCI selection based on multi -parameter criteria, including location-based adjacency, relation-based adjacency, PCI spacing rules, modulo constraints, and vendor-specific PCI allocation policies. The target PCI value is derived that minimizes interference potential and satisfies operator-defined SON parameters, resulting in optimized PCI reuse and reduced collision probability.

[0125] A further technical advantage is that the invention supports both open-loop and closed-loop operational modes. In closed-loop mode, the MVSON module not only computes optimized PCI values but also executes the PCI change commands through multiple EMSs, waits for confirmation, and iteratively adjusts the PCI values as required. This leads to a fully automated end-to-end PCI optimization workflow with minimal human intervention, improving operational efficiency and reducing configuration errors arising from manual PCI modifications.

[0126] Another technical advantage of the invention is the generation of detailed analytics reports, including conflict scores, candidate PCI lists, suggested victimcells, pre- and post-change KPIs, and the operational status. These reports enable visibility into network conditions and optimization decisions. The ability to track performance improvement after PCI changes provides a feedback loop that enhances subsequent optimization cycles.

[0127] Finally, by ensuring consistent PCI allocation across different vendor ecosystems, the invention enhances interoperability, reduces operational overhead, and enables uniform network performance improvement across the entire multivendor environment.

[0128] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

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

[0130] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehendedwithin the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.LIST OF REFERENCE NUMERALS

[0132] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100 - PCI collision scenario100’- PCI confusion scenario200- Multi-vendor communication environment / communication environment / communication system210 - Cognitive platform220 - Element Management Systems (EMSs)230 - Base station or gNBs240- Multi-Vendor Self Organizing Network (MVSON) unit / System 250- User Interface / Command Line Interface (UI / CLI)300-2- First communication bus300-4- Second communication bus302 - Processor304 - Memory306 - Communication interface308 - Input / Output interface310- Communication modules320 - Receiving module330 - Processing module340 - PCI selection module350- Execution module360 -Generation module400-Method for optimizing PCI configuration in a wireless communication network.402-408 - Operation steps of the method 400500- Exemplary method for identifying the PCI collisions and the PCI confusions to perform target PCI optimization in the wireless communication network502-554- Operation steps of the method 500600 - A computing system610 - Network620 - Network interface630 - Processor of the computing system640 - Input / Output (I / O) interface of the computing system650 - Non-transitory computer readable storage medium / storage medium / storage media652 - Set of instructions

Claims

We claim:

1. A method (400) for optimizing Physical Cell Identity (PCI) configuration in a wireless communication network, the method comprising:collecting, by a receiving module (320), configuration data and performance metrics from one or more cells within a defined coverage area; processing, by a processing module (330), the collected configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of a PCI collision or a PCI confusion;determining, by a PCI selection module (340), a target PCI value for each identified cell based on a predefined selection criteria; andexecuting, by an execution module (350), a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI configuration in the wireless communication network.

2. The method (400) as claimed in' claim 1, wherein the configuration data includes at least one of cell identifiers, current PCI value associated with each cell, neighbor relation information, and the performance metrics include at least one of interference measurements, signal quality indicators, handover return statistics or call failure statistics.

3. The method (400) as claimed in' claim 1, wherein executing the PCI update operation comprises:transmitting a PCI change command to a network node associated with each identified cell; andrecording, based on an execution of the PCI change command, an updated PCI configuration status for each identified cell, wherein the recording comprises storing the applied target PCI value, timestamp, and associated network node information in a PCI configuration database.

4. The method (400) as claimed in claim 1, further comprising generating, by a generation module (360), a PCI candidate list by excluding one or more PCI values currently used by neighboring cells of the one or more cells.

5. The method (400) as claimed in claim 1, wherein determining the target PCI value comprises selecting a PCI value from a PCI candidate list that satisfies the predefined selection criteria.

6. The method (400) as claimed in claim 1, wherein the predefined selection criteria comprise at least one of a minimum PCI reuse distance, PCI availability within a predetermined set of PCI values, interference score, or historical PCI usage pattern.

7. The method (400) as claimed in claim 1, wherein the identifying at least one cell among the one or more cells exhibiting the PCI collision comprises detecting, by the processing module, one or more neighboring cells with same PCI values.

8. A system (240) for optimizing Physical Cell Identity (PCI) configuration in a wireless communication network, the system comprising:a receiving module (320) configured to collect configuration data and performance metrics from one or more cells within a defined coverage area; a processing module (330) configured to process the collected configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of a PCI collision or a PCI confusion;a PCI selection module (340) configured to determine a target PCI value for each identified cell based on a predefined selection criteria; andan execution module (350) configured to execute a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI configuration in the wireless communication network.

9. The system (240) as claimed in' claim 8, wherein the configuration data includes at least one of cell identifiers, current PCI value associated with each cell, neighbor relation information, and the performance metrics include at least one of interference measurements, signal quality indicators, handover return statistics or call failure statistics.

10. The system (240) as claimed in' claim 8, wherein, to execute the PCI update operation, the execution module (350) is configured to:transmit a PCI change command to a network node associated with each identified cell; andrecord, based on an execution of the PCI change command, an updated PCI configuration status for each identified cell, wherein the recording comprises storing the applied target PCI value, timestamp, and associated network node information in a PCI configuration database.

11. The system (240) as claimed in claim 8, further comprising a generation module (360) configured to generate a PCI candidate list by excluding one or more PCI values currently used by neighboring cells of the one or more cells.

12. The system (240) as claimed in claim 8, wherein to determine the target PCI value, the PCI selection module is configured to select a PCI value from a PCI candidate list that satisfies the predefined selection criteria.

13. The system (240) as claimed in claim 8, wherein the predefined selection criteria comprise at least one of a minimum PCI reuse distance, PCI availability within a predetermined set of PCI values, interference score, or historical PCI usage pattern14. The system (240) as claimed in claim 8, wherein, to identify at least one cell among the one or more cells exhibiting the PCI collision, the processing module is configured to detect one or more neighboring cells with same PCI values.

15. A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:collecting configuration data and performance metrics from one or more cells within a defined coverage area;processing the collected configuration data and the performance metrics to identify at least one cell among the one or more cells exhibiting at least one of a PCI collision or a PCI confusion;determining a target PCI value for each identified cell based on a predefined selection criteria; andexecuting a PCI update operation based on the determined target PCI value for each identified cell to optimize the PCI configuration in the wireless communication network.

Images