System and method for managing hierarchical relationship among entities in a computing environment

Abstract

Disclosed is a system (200) and a method (500) for managing hierarchical relationship among network entities in a computing environment. The system (200) detects removed (or status-changed) parent entity. Thereafter, the system (200) retrieves a policy configuration from a cache memory (215) and identifies child entities linked to the parent entity using the policy configuration. This enables faster and modifiable execution of operations without any overheads from the computing environment. The system (200), using the policy configuration, determines a stalling condition for the child entity and initiates stalling the child entity for a stalling period based on the stalling condition. The stalling of the child entity enables an option of reassociation with an active entity, based on a receipt of association request from the active entity, when attributes of the child entity match with a reassociation eligibility criteria defined by the policy governing the hierarchical relationship.

Description

SYSTEM AND METHOD FOR MANAGING HIERARCHICAL RELATIONSHIP AMONG ENTITIES IN A COMPUTING ENVIRONMENTTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of cloud computing. More particularly, the present disclosure relates to a system and a method for managing hierarchical relationship between network entities in a computing environment.BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely because of 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] Traditional Customer Relationship Management (CRM) systems are widely used across industries to maintain customer data, track interactions, and support business deci si on -making processes. However, these CRM systems often lack the advanced functionality necessary to effectively manage complex corporate customer hierarchy and enterprise structures. Organizations with large corporate clients (i.e., typically involving multi-level organizational setups) face challenges in accurately representing and maintaining relationships within the corporate customer hierarchy. These limitations often lead to inefficiencies, data inconsistencies, and a lack of visibility into the true nature of corporate relationships.

[0004] Managing customer onboarding or modifying existing customer information poses further challenges. The absence of comprehensive controls, validation checks,and real-time updates can result in processing errors and redundant processes execution. This complexity is compounded when an organizational operation requires multiple approvals or specific workflows due to the change in the operational logic, where the traditional CRM systems fail miserably.

[0005] Another critical issue faced by traditional CRM systems is degradation of performance while executing a code directly on the server to implement the operational logic, validation checks, or approval workflow. As the volume of data and complexity of operational rules increase, the server’s response times can slowdown significantly, impacting user experience and the overall system’s scalability. This issue is further exacerbated in scenarios where multiple layers of validation and modifications are required during onboarding or updating customer information. Such systems, designed without modularity or optimization, can struggle to handle large data and can lead to delays and errors. In view of the above-mentioned challenges, there is a requirement of a technical solution to address the broader problem.SUMMARY

[0006] 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.

[0007] According to an embodiment of the present disclosure, a method for managing hierarchical relationship among a plurality of network entities (hereinafter interchangeably referred to as ‘entities’) in a computing environment is provided. The method includes detecting, by a hierarchy inspection module, a removal or a status change for a parent entity from the plurality of entities in thehierarchical relationship. The method further includes retrieving, by a transceiver module, a policy configuration associated with the parent entity from a cache memory. Furthermore, the method includes identifying, by the hierarchy inspection module, one or more child entities linked with the parent entity based on the policy configuration. Furthermore, the method includes determining, by a processing module using the policy configuration, a stalling condition for each of the one or more child entities. Furthermore, the method includes initiating, by the processing module, a stalling period for each of the one or more child entities based on the stalling condition of corresponding child entity.

[0008] In some aspects of the present disclosure, upon initiating the stalling period, the method includes determining, by the processing module, whether an association request is received for a child entity from the one or more child entities within the stalling period. The association request corresponds to an association of the child entity with an active entity of the plurality of entities. Moreover, the method includes activating, in response to a receipt of the association request for the child entity by the processing module, the child entity based on a determination that the association of the child entity satisfies a policy governing the hierarchical relationship.

[0009] In some aspects of the present disclosure, each child entity of the one or more child entities is placed immediately lower to the parent entity in the hierarchical relationship among the plurality of entities in the computing environment.

[0010] In some aspects of the present disclosure, the stalling period is monitored by a scheduler or timer-based process that triggers a reassignment or a termination of the association of the child entity with the active entity based on an elapsed duration in the stalling period.

[0011] In some aspects of the present disclosure, in response to a determination that the association request is received for the child entity within the stalling period, the method includes validating, by a validation module, the association request againstallowed hierarchical relationship between one or more entity types for the plurality of entities in the computing environment, as specified in the policy governing the hierarchical relationship.

[0012] In some aspects of the present disclosure, the association of the child entity satisfies the policy when one or more attributes of the child entity match with a reassociation eligibility criteria defined by the policy governing the hierarchical relationship.

[0013] In some aspects of the present disclosure, upon the removal or the status change of the parent entity, the method comprises terminating, by the processing module, a child entity of the one or more child entities, based on a determination that the association request is not received within the stalling period, in accordance with a rule of the policy governing the hierarchical relationship.

[0014] In some aspects of the present disclosure, the policy configuration defines visibility or access rights for entity data based on one or more user roles and the one or more entity types for the plurality of entities in the computing environment.

[0015] According to another embodiment of the present disclosure, a system to manage hierarchical relationship among a plurality of entities in a computing environment is provided. The system includes a cache memory and a data processing circuitry. The data processing circuitry comprises a hierarchy inspection module, a transceiver module, and a processing module. The hierarchy inspection module is configured to detect a removal or a status change for a parent entity from the plurality of entities in the hierarchical relationship. The transceiver module configured to retrieve a policy configuration associated with the parent entity from the cache memory. The hierarchy inspection module is further configured to identify one or more child entities linked with the parent entity based on the policy configuration. The processing module is configured to determine, using the policy configuration, a stalling condition for each of the one or more child entities. Moreover, the processing module is further configured to initiate a stalling periodfor each of the one or more child entities based on the stalling condition of corresponding child entity.

[0016] According to yet another embodiment of the present disclosure, a computerprogram product for managing hierarchical relationship among a plurality of entities in a computing environment is provided. The computer-program product comprises computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations. The operations include detecting a removal or a status change for a parent entity from the plurality of entities in the hierarchical relationship. Moreover, the operations further include retrieving a policy configuration associated with the parent entity from a cache memory. Furthermore, the operations include identifying one or more child entities linked with the parent entity based on the policy configuration. Furthermore, the operations include determining, using the policy configuration, a stalling condition for each of the one or more child entities. Furthermore, the operations include initiating, a stalling period for each of the one or more child entities based on the stalling condition of corresponding child entity.BRIEF DESCRIPTION OF DRAWINGS

[0017] 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 disclosed herein. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed 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.

[0018] FIG. 1 is a block diagram illustrating exemplary components of a communication network, in accordance with an embodiment of the present disclosure.

[0019] FIG.2 is a block diagram illustrating exemplary components of a system to manage hierarchical relationship among network entities in a computing environment, in accordance with an embodiment of the present disclosure.

[0020] FIG.3 is a block diagram illustrating exemplary components of a Customer Relationship Management (CRM) server, in accordance with an embodiment of the present disclosure.

[0021] FIG. 4 is a block diagram illustrating exemplary components of a Customer Information Management Service (CIMS) node in the CRM server, in accordance with an embodiment of the present disclosure.

[0022] FIG. 5 illustrates a flow chart depicting a method for managing the hierarchical relationship among the network entities in the computing environment, in accordance with an embodiment of the present disclosure.LIST OF REFERENCE NUMERALSThe 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 as follows:100 - Communication Network102 - Core Network104 - Nodes106 - User Devices200 - System to manage hierarchical relationship among network entities 202 - Communication channels204 - Load Balancer206 - SE Server208 - Notification Hub210- OSS FMS212 - UAP214 - GIS System215 - Cache Memory216 - CRM Server302 - DMRS Node304 - CIMS Node306 - CPHS Node308 - COPS Node310 - UI Node312- CSMS Node314-L20 Node316 - Lite Node318 -AS Node320 - OAMS Node322 - CUS Node401 - Interface(s)402 - Data Processing Circuitry404 - Database406 - First Communication Bus408 - Transceiver Module410 - Hierarchy Inspection Module412 - Processing Module414 - Validation Module418 - Second Communication Bus420 - Instructions Repository422 - Data Repository500 - Method for managing the hierarchical relationship among the network entities502 - 520 - Operational Blocks of Method 500DETAILED DESCRIPTION OF THE INVENTION

[0023] 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 embodiments disclosed 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.

[0024] 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.

[0025] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “insome embodiments” which may each refer to one or more or all of the same or different embodiments. 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” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”

[0026] 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.”

[0027] In the following description, for the purposes of explanation, various specific details are set forth 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.

[0028] 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.

[0029] 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 forms unless the context of the invention indicates otherwise.

[0030] 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.

[0031] Aspects of the present disclosure relate to a system and method for managing network hierarchy (i.e., hierarchical relationship) of network entities (hereinafter interchangeably referred to as ‘entities’) in a computing environment. In some aspects of the present disclosure, the system provides management of hierarchical positions of the network entities based on a predefined set of hierarchical protocols (driven through a policy governing hierarchical relationship between network entities). In some aspects of the present disclosure, the system enables storage of the predefined set of hierarchical protocols in a cache memory directly accessed by the system that improves the efficiency of the management of hierarchy. The set of hierarchical protocols regulate adding / removing network entities at appropriate hierarchical positions into the communication network based on a set of predefined policies. The policy manages providing permission to the network entities for accessing and modifying data and handling a state of termination of network entities from the communication network. Some other aspects of the present disclosure relate to determination of deletion of network entities in the hierarchical structure and managing network entities associated with the removed network entity.

[0032] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 5, 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.

[0033] FIG. 1 illustrating exemplary components of a communication network 100, in accordance with an embodiment of the present disclosure. As illustrated in FIG.1, the communication network 100 includes a core network 102 coupled with a plurality of nodes including Node 104-1 through Node 104-N and configured to facilitate a secured communication among the plurality of nodes (collectively referred to as the “nodes 104”, and individually referred to as the “node 104”, hereinafter).

[0034] In an embodiment, each of the nodes are configured to be coupled with one or more user devices 106-1, 106-2, 106-3, 106-4, through 106-(N-l), 106-N (collectively referred to as the “user devices 106”, and individually referred to as the “user device 106”, hereinafter). In one aspect, the core network 102 may establish a secured communication between the one or more user devices 106 associated with the plurality of nodes 104. In another aspect, the core network 102 may establish a secured communication between the one or more user devices 106 associated with the same node 104.

[0035] In an exemplary embodiment, the core network 102 may effectively establish a secured communication between the user device 106-1 and the user device 106-2, where the user device 106-1 and the user device 106-2 both are coupled with the node 104-1. In another embodiment, the core network 102 may establish a secured communication between the user device 106-2 and the userdevice 106-N with equal effectiveness, where the user device 106-2 is coupled with the node 104-1 and the user device 106-N is coupled with the node 104-N.

[0036] In an exemplary embodiment, the core network 102 (also, referred to as ‘network 102’, herein) may be configured as a data processing server (or a combination of multiple data processing servers) and may be communicably operational or may be integrated with a user device 106 via a network coupled with a server. The core network 102 may pertain to 5G service-based architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the core network 102 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks. In some aspects of the present disclosure, the core network 102 may include operational entities (network entities) that may provide resources for establishment of a computing environment in the communication network 100.

[0037] Although FIG. 1 illustrates one example of the communication network 100, various changes may be made to FIG. 1. For example, the communication network 100 may include any number of nodes 104 and user devices 106 in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0038] FIG. 2 is a block diagram illustrating exemplary components of a system 200 to manage hierarchical relationship among network entities in a computing environment, in accordance with an embodiment of the present disclosure. The system 200 may include communication channel(s) 202, a load balancer 204, a Subscription Engine (SE) server 206, a notification hub 208, an Operation Support System Fulfillment Management System (OSS-FMS) 210, a Unified Assurance Platform (UAP) 212, a Geographical Information System (GIS) 214, and a Customer Relationship Management (CRM) Server 216.

[0039] The communication channel(s) 202 may be configured to render network and communication services to the network entities corresponding to user devices 106. In some aspects of the present disclosure, each network entity may be a user account associated with a hierarchical structure corresponding to a network service of the communication network 100 and is operated by way of the user device 106. Preferably, communication between the communication channels 202 and the CRM server 216 occurs via Hypertext Transfer Protocol Secure (HTTP), Web Services (WS), Representational State Transfer (REST) and event protocol over the Transmission Control Protocol (TCP) connector. Examples of communication channels 202 may include but are not limited to Marketplace User Interface (UI), Point of Sale (POS) or Market Point of Sale (mPOS), Customer Relationship Management User interface (CRM UI), Inbound / Outbound self, or customer care and the like. The load balancer 204 may be capable of distributing the incoming and outgoing requests between the communication channels 202 and the CRM server 216 based on the availability of the resources of each network entity.

[0040] The SE server 206 may be configured to enable the network entities to setup and manage subscription(s) for various network services and product catalogues offered to the network entities by a network service provider in the communication network 100. Preferably, the communication between the SE server 206 and the CRM server 216 occurs via HTTP, WS, REST and event protocol over the TCP connector. The notification hub 208 may be configured to initiate, manage, and / or distribute notifications (such as alerts, updates, or messages) to users of the user devices 106 (or the network components). The OSS-FMS 210 may be responsible for workflow orchestration, provisioning, and activation of network services. The OSS-FMS 210 may further facilitate managing of inventory operations such as dispatching, scheduling, and tracking field activities.

[0041] The UAP 212 may be responsible for implementing automations to simplify trouble-ticketing, service management and help desk operations. The UAP 212 provides installation details for assigning a technician based on availability andlocation of the network service. The GIS 214 may be configured to capture, store, manipulate, analyze, manage and / or render geographical data of the network entities in the communication network 100. Examples of geographical data may relate to a pin code, a geographical state, a district, and the like. The notification hub 208, the OSS-FMS 210, the UAP 212, and the GIS 214 may communicate with the CRM server 216 via the HTTP, WS, REST and event protocol over the TCP connector.

[0042] The CRM server 216 may include circuitry, logic, interface(s), codes, and / or hardware components (specifically in the form of microservice(s)) configured to manage hierarchical structure of the network entities associated with the user devices 106. Specifically, the CRM server 216 may manage arrangement and / or operation(s) of the network entities through a hierarchical relationship (corresponding to the hierarchical structure) in the communication network 100. In an exemplary scenario, the hierarchical relationship may include various elements abiding a set of pre-defined policies, protocols, and configurations. Specifically, the CRM server 216 enables storage of the predefined set of hierarchical protocols (driven through a policy governing hierarchical relationship between the network entities) in the cache memory 215. The hierarchical protocols may include hierarchical rule(s) that regulate adding / removing network entities at appropriate hierarchical positions into the communication network based on a set of predefined policies. The pre-defined policies manage providing permission to the network entities for accessing and modifying data and handling a state of termination of network entities. Particularly, the hierarchical rules may govern addition, deletion (i.e., removal / termination), reassignment, and stalling of the network entities. In an exemplary aspect of the present disclosure, the hierarchical rules may relate a condition with an outcome. For example, when the network entity is removed (or status changes from active to inactive) from the hierarchy, the hierarchical rules may define operations for identification of the child entities of the removed entity, determination of the policy configuration for each child entity, identification of the stalling period, determination whether association request for the child entity isreceived within its stalling period, verifying that the association request is received from an active network entity eligible for association, etc.

[0043] For example, the hierarchical relationship may include a Headquarters (HQ) network entity, which is at the top of the hierarchy, a Customer Acquisition Form Location (CL) network entity, which is responsible for handling documents related to user devices 106 corresponding to new network entities. The HQ network entity acts as a parent network entity to the CL network entity in the hierarchical relationship. The hierarchical relationship may further include a Billing Location (BL) network entity, which is responsible for payments related to various network services used by user device 106. The CL network entity acts as a parent network entity to the BL network entity in the hierarchical relationship. Furthermore, the hierarchical relationship may include an Authorized Signatory (AS) network entity which is responsible for document signing and review processes, a Billing Contact (BC) network entity which is responsible for handling billing data related queries, and an Installation Location (IL) network entity which handles all the data related to installation site. The BL element acts as a parent network entity to the AS network entity, BC network entity and the IL network entity in the hierarchical relationship. Furthermore, the hierarchical relationship may also include a General Contact (GC) network entity which is responsible for handling any general queries related to installation site and a Technical Contact (TC) network entity which is responsible for handling any technical queries related to installation site. The IL network entity acts as a parent network entity to the GC network entity and the TC network entity in the hierarchical relationship.

[0044] The CRM server 216 may further include circuitry, logic, interface(s), codes, and / or hardware components configured for creating new network entities based on the set of pre-defined policies, protocols, and configurations stored in a cache memory 215. The cache memory 215 may be equipped with an update mechanism for cache coherence. The update mechanism may update or refresh the cache memory 215 periodically, continuously, or on instance basis. In some aspects of thepresent disclosure, the update mechanism may be regulated by a policy governing hierarchical relationship between the network entities. The CRM server 216 may be configured to update the cache memory 215 keeping the policy current. The CRM server 216 may receive a creation request to create a new network entity from the user device 106. The CRM server 216 may further identify a type for the new network entity from the creation request. Furthermore, the CRM server 216 determines a parent network entity (hereinafter interchangeably referred to as ‘parent entity’) corresponding to the new network entity and determines whether the parent network entity is present in the communication network 100. Furthermore, the CRM server 216 further determines whether the parent network entity is active, in response to the determination of parent network entity is present in the communication network. Furthermore, the CRM server 216 determines the number of child network entities (hereinafter interchangeably referred to as ‘child entity’ when referred in singularity or ‘child entities’ when referred in plurality) under the parent network entity. Each network entity may hold a hierarchical position which is indicated through its policy configuration. In simpler words, the policy configuration for each network entity may be indictive of its hierarchical position, role(s), and association(s) in the hierarchy (i.e., parent entity and / or child entities). When the child network entities are less than the number set by the pre-defined polices and configuration, the CRM server 216 generates a request for the creation of network entity under the parent network entity to the CRM server 216. Furthermore, the CRM server 216 creates the network entity under the correct parent entity, in response to the request of creation of network entity under the parent network entity being approved by the CRM server 216.

[0045] In an exemplary scenario, the CRM server 216 may receive a request to create the AS network entity from the user device 106. The CRM server 216 may determine the type of parent network entity of AS network entity as BL network entity. The CRM server 216 may determine whether the BL network entity is present in the CRM. The CRM server 216 may further determine whether the BL network entity is active, in response to the determination of the BL network entity beingpresent in the CRM. Furthermore, the CRM server 216 may determine the number of child nodes of BL network entity, in response to the determination of the BL network entity being active. When the child network entities are less than the number set by the pre-defined polices and configuration, the CRM server 216 generates a request for the creation of AS network entity under the BL network entity to the CRM server 216. the CRM server 216 creates the AS network entity under the BL network entity, in response to the request of creation of AS network entity under the BL network entity being approved by the CRM server 216.

[0046] The CRM server 216 may also create different set of information related to business context referred to as views for the network entities based on the type of data required. The pre-defined polices may include a policy corresponding to control of view creation, wherein each network entity can have certain unique views. In an embodiment, the BL and IL network entity can hold account details as a view, in another embodiment, the AS network entity can hold associated contact details which are related to the network entity by family or peer relation. Yet in another embodiment, the BC, GC, and TC network entity can hold contact details as views. The pre-defined polices may also include a policy corresponding sharing of view, wherein the view data is shared by the parent and child network entity. In an embodiment, the BL network entity may not have its own contact details. In such scenario, a user may provide a linkage in policy where contact details of BC network entity are automatically copied into its parent network entity BL, while creating a new network entity. In another embodiment, the address details of GC and TC network entity cannot be individually created and rather, be copied from the parent network entity IL. The pre-defined policies may further include another policy corresponding to restricting certain network entities based on their role in the communication network 100. In an embodiment, the HQ network entity belonging to government department may avail right(s) to access account related data such as account details of its Billing Location, which cannot be accessed by any other frontend network entity apart from an administrative network entity or a super administrative network entity. In another embodiment, the payment details made byBL network entity (such as mode of payment, checksum and amount) cannot be viewed even by admin. This is the private access space of BL and HQ network entity. Hence, to view payment details pertaining to BL or HQ network entities, new roles are needed to be created in User interface that enables selective viewing permissions to the network entities for the payment details. Even BL element’s child network entities such as AS, BC, IL cannot have the rights to view it.

[0047] The CRM server 216 may also stall network entities, when a corresponding parent network entity is terminated. The CRM server 216 may also re-activate the stalled network entities when a new parent network entity for the stalled element is found, provided a set of properties of the new parent network entity matches with the set of pre-defined policies. The CRM server 216 may also maintain a data structure corresponding to the network entities that stores hierarchical details of the network entities (e.g., a child network entity, a parent network entity etc.). The CRM server 216 may also store a stalling variable to determine whether to terminate a child element after a termination of a corresponding parent element. When the stalling variable is true, the child element is stalled. Else, when the stalling variable is false the child network entity is terminated. The data structure further stores a time-to-live variable to store the time left for a stalling period of the child network entity when the parent element is terminated. The stalling period may be a buffer duration that may be allocated for reassociation of a network entity with another active network entity (i.e., higher than its hierarchy) when its parent entity is removed (or status changed from ‘active’ to ‘inactive’). Moreover, the data structure stores a status variable to store a status of each network entity. Specifically, the status of each network entity may be ‘active’ or ‘stalled’. In a scenario, when the HQ network entity is terminated, all associated child network entities of the HQ network entities may be auto terminated, except for AS element as the stalling variable corresponding to AS element has the state ‘True’. The status variable corresponding to AS network entity can be changed to ‘stalled’ until it is linked to another existing BL network entity of another HQ network entity. When the status variable corresponding to AS network entity is linked to BL network entity of another HQnetwork entity, the status variable corresponding to AS network entity is changed back to Active state. Else, when the value of status variable is equal to Stalled and the stalling period is over, the AS network entity is terminated.

[0048] Although FIG. 2 shows exemplary components of the system 200, in other implementations, the system 200 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the core network 102 may perform functions described as being performed by one or more other components of the system 200.

[0049] FIG. 3 is a diagram illustrating exemplary components of the CRM Server 216, in accordance with an embodiment of the present disclosure. As shown in FIG.3, the CRM server 216 may include a Document Management and Retrieval Service (DMRS) node 302, a Customer Information Management Service (CIMS) Node 304, a Customer Problem Handling Service (CPHS) Node 306, a Customer Order Processing Service (COPS) Node 308, a User Interface (UI) Node 310, a Customer State Management Service (CSMS) Node 312, a Lead to Order (L2O) Node 314, a Lite Node 316, an Analytics Service (AS) Node 318, an Operations, Administration and Maintenance Service (OAMS) Node 320, and a Common Utility Service (CUS) Node 322.

[0050] The DMRS node 302 may be configured to store, retrieve, and process forms and documents associated with the user device 106 which correspond to new or existing network entities in the communication network. The CIMS node 304 may be configured to manage creation of a new network entities in the communication network 100, creating views for the network entities, and handling termination of network entities from the communication network 100.

[0051] The CIMS node 304 may further be configured to identify a removed network entity from the hierarchical structure in the communication network 100.Moreover, the CIMS node 304 may be configured to retrieve a data structure entry corresponding to the removed network entity from the cache memory 215. The CIMS node 304 may also be configured to identify child network entities of the removed network entity from the data structure entry. Furthermore, the CIMS node 304 may be configured to determine a stalling state for each child network entity from the stalling variable included in the data structure entry. The CIMS node 304 may further be configured to terminate a child network entity, when the stalling state of the child network entity is ‘False’. Moreover, the CIMS I 304 may update the status variable of the child network entity to ‘stalled’, when the stalling state of the child network entity is ‘True’. Furthermore, the CIMS node 304 may be configured to retrieve the time-to-live variable from the data structure entry and determine a stalling period for the stalled child element. The CIMS node 304 may receive a stalling request and determine whether the stalling request is received within the stalling period. The CIMS node 304 may also be configured to terminate the child network entities, in response to the determination that the stalling request is not received within the stalling period. The CIMS node 304 may further be configured to identify an active network entity associated with the stalling request. The CIMS node 304 may also determine a set of properties of the active network entity, in response to the determination that the stalling request is received within the stalling period. Furthermore, the CIMS node 304 may be configured to compare the set of properties with the pre-defined policy. When the set of properties mismatch with the pre-defined policy, the CIMS node 304 may terminate the stalled child network entity. Else, when the set of properties match with the pre-defined policy, the CIMS node 304 may link the stalled child network entity with the active network entity.

[0052] The CPHS node 306 may be configured to handle service request(s) raised by the network entities. The service request(s) may correspond to customer complaint(s) related to network service(s) and / or communication service(s) associated with the network entities.

[0053] The COPS node 308 may be configured to receive order(s) from the network entities. The COPS node 308 may further be configured to check a status of the order (i.e., placed by the network entities). Furthermore, the COPS node 308 may be configured to delegate the orders to the OSS-FMS 210 for handling ‘Know Your Customer (KYC)’ compliance for the network entities.

[0054] The UI node 310 may be configured to operate as an internal frontend of the CRM server 216. The UI node 310 may further be configured to provide an interface to add or close leads and manage the status of existing leads. Furthermore, the UI node 310 may provide an interface for managing documents and / or order(s).

[0055] The CSMS node 312 may be configured to determine an activation status of each network entity. The CSMS node 312 may also be configured to identify the network and communication services to which the network entity is subscribed to. The AS node 318 may be configured to create and display dashboard entries of data and derive meaningful insight(s).

[0056] The L2O node 314 may be configured to keep a track of qualifying user devices 106 and manage the leads until they are converted into orders. The Lite node 316 may be configured to handle processes which include multi step approvals. The Lite node 316 may further be configured to manage digital KYC data entries.

[0057] The OAMS node 320 may be configured to manage the nodes (i.e., microservices) present in the CRM server 216. In a scenario, when any of the node of the CRM server 216 experiences a technical issue, the OAMS node 320 manages and repairs the node. Specifically, the OAMS node 320 may be configured to adjust configuration of the node(s) (i.e., microservice(s)) of the CRM server 216 experiencing the technical issue. The CUS node 322 may be configured to manage master data for the CRM server 216. Specifically, the master data may be used by various nodes in the CRM server 216 for deriving the overall functionality performed by the CRM server 216. The CUS node 322 may store a local copy ofdata associated with the network services, the communication services, and / or product catalogue(s) for the various nodes in the CRM server 216.

[0058] Although FIG. 3 shows exemplary components of the CRM server 216, in other implementations, the CRM server 216 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 3. Additionally, or alternatively, one or more components of the CRM server 216 may perform functions described as being performed by one or more other components of the CRM server 216.

[0059] FIG. 4 is a block diagram illustrating exemplary components of the CIMS node 304, in accordance with an embodiment of the present disclosure. The CIMS node 304 may be configured as a data processing server (or, in some embodiments, a micro-service) configured to manage the hierarchical relationship between the network entities in the computing environment. Preferably, the CIMS node 304 may include interface(s) 401, data processing circuitry 402, and a memory unit 404 communicatively coupled to each other by way of a first communication bus 406. The data processing circuitry may comprise multiple data processing engines. The data processing engines may be configured to perform operational tasks to facilitate the CRM server 216 for managing the hierarchical relationship among the network entities in the computing environment of the communication network 100.

[0060] The data processing circuitry 402 may include a transceiver module 408, a hierarchy inspection module 410, a processing module 412, and a validation module 414, communicatively coupled to each other by way of a second communication bus 418.

[0061] The transceiver module 408 may be configured to enable transfer of data from the memory unit 404 to various modules of the data processing circuitry 402. The transceiver module 408 may further be configured to enable a transfer of the input data from the various components of the CRM server 216 to the CIMS node304. In some aspects of the present disclosure, the transceiver module 408 may also be configured to receive input(s) and / or instructions from the various other components of the system 200. Furthermore, the transceiver module 408 may also be configured to enable transfer of the data and / or instructions between various other modules of the data processing circuitry 402.

[0062] Preferably, the hierarchy inspection module 410 may be configured to detect a removal or a status change (e.g., entity status changed from ‘active’ to inactive’) for a parent entity from the plurality of entities in the hierarchical relationship. Specifically, the CRM server 216 may maintain hierarchical information of the network entities in the computing environment. The hierarchy inspection module 410 may continuously inspect the hierarchical information to detect the removal or the status change for any network entity in the hierarchical relationship (i.e., hierarchical structure). In a non-limiting example, the hierarchical information may correspond to edges and / or weights between network entities connected together through the hierarchical relationship. Specifically, the edges may represent the hierarchical relationship between the network entities (e.g., parent entity and child entity) and the weight may represent count of child entities associated with the parent node. For example, a normalized ‘ 1 / 3’ weight on edges between two network entities indicate association of three child entities with the parent entity. In some aspects of the present disclosure, the CRM server 216 may store the hierarchical information in the form of an information graph where a higher hierarchical position indicates a parent entity and a lower hierarchical position indicates a child entity. Particularly, each child entity is placed immediately lower to a parent entity in the hierarchical relationship among the network entities in the computing environment. The hierarchy inspection module 410 may be configured to fetch the hierarchical information of the network entities from the CRM server 216 (periodically, continuously, or on instance bases) and analyze the hierarchical information of the network entities to identify whether a parent entity (i.e., having at least one child entity) is removed (or operational status of the parent entity is changed from ‘active’ to ‘inactive’).

[0063] The transceiver module 408 may be configured to retrieve a policy configuration associated with the detected parent entity (i.e., removed / status changed) from the cache memory 215. Particularly, the policy configuration defines hierarchical rules governing addition, deletion, reassignment, and stalling of entities in the computing environment. In some aspects of the present disclosure, the policy configuration defines visibility or access rights for each network entity in the computing environment. Specifically, each network entity may be associated with role(s) from multiple predefined operational roles in the computing environment. Moreover, each network entity may correspond to an entity type from multiple entity types in the computing environment. The policy configuration for each network entity defines the visibility and access rights of the network entity based on the corresponding role(s) and the entity type of the network entities.

[0064] The hierarchy inspection module 410 may further be configured to identify one or more child entities linked with the detected parent entity based on the policy configuration. Specifically, the hierarchy inspection module 410 may inspect the hierarchical information of the network entities to determine whether the parent entity (removed / status changed) is linked with the one or more child entities. Based on the determination that the parent entity is linked with the one or more child entities, the processing module 412 may be configured to utilize the policy configuration to determine a stalling condition for each of the one or more child entities. Preferably, the processing module 412 may retrieve information of the hierarchical position, the role(s), and / or the association(s) in the hierarchy (i.e., parent entity and / or child entities) from the policy configuration of each child entity. Each hierarchical position or role may be associated with a stalling condition that defines exemplary scenarios for stalling of the child entity (for example, removal or state change of the parent entity). Based on the information, the processing module 412 may determine the stalling condition for each child entity. In some aspects of the present disclosure, the stalling condition for a child entity may be indicative of a stalling period for the child entity. Specifically, the stalling condition may beassociated with a network entity being stalled, reassigned, or terminated, when its parent entity is removed or deactivated (i.e., status changed from active to inactive). Specifically, the processing module 412 may be equipped with a scheduler, through a timer-based process, that triggers reassignment or termination of the association of the child entity with the active entity based on an elapsed duration in the stalling period, for monitoring the stalling period. Particularly, the processing module 412 may be configured to generate an activation signal based on the association of the child entity with the new active entity, in response to the verification of the association request within the stalling period for the child entity. The activation signal may activate the stalled child entity to operate in association with the new parent entity.

[0065] The processing module 412 may also be configured to initiate the stalling period for each of the one or more child entities of the parent entity removed or deactivated, based on the stalling condition of the corresponding child entity. Preferably, the processing module 412 may determine whether the stalling condition for the child entity is met (i.e., the parent entity is removed or inactivated from the hierarchy). Upon determination that the stalling condition is met, the processing module 412 may transmit a trigger signal to the scheduler to initiate the timer-based process for monitoring lapse of the stalling period. Based on the trigger signal, the scheduler starts time monitoring of the lapse of the stalling period for the child entity. In some aspects of the present disclosure, upon initiating the stalling period, the processing module 412 may be configured to determine whether an association request is received for a child entity from the one or more child entities within the stalling period. The association request corresponds to an association of the child entity with an active entity of the plurality of entities. Moreover, the processing module 412 may also be configured to active the child entity based on a determination that the association of the child entity satisfies the policy governing the hierarchical relationship, in response to a receipt of the association request for the child entity.

[0066] The processing module 412 may be configured to determine whether the association request for the child entity is received from an active network entity, whether the association request for the child entity is received within the stalling period for the child entity, and whether the active entity is hierarchically capable of associating the child entity. Particularly, in response to a determination that the association request is received for the child entity within the stalling period, the validation module 414 may be configured to validate the association request against allowed hierarchical relationship between one or more entity types for the network entities in the computing environment, as specified in the policy governing the hierarchical relationship. In some aspects of the present disclosure, the association of the child entity satisfies the policy when one or more attributes of the child entity match with a reassociation eligibility criteria defined by the policy governing the hierarchical relationship. Particularly, the policy governing the hierarchical relationship between the network entities may comprise eligibility criteria for reassociation of the child entity with another active network entity in the network. The eligibility criteria may include multiple conditions such as, but not limited to, inactive or removed parent entity of the child entity, receipt of an association request from the active entity within the stalling period if the child entity, hierarchical status of the active entity requesting reassociation equal to the inactive or removed parent entity, etc. The validation module 414 may verify each attribute matching with corresponding conditions in the reassociation eligibility criteria before validating the association request. In some aspects of the present disclosure the attributes may include parametric values associated with the multiple conditions. In some aspects of the present disclosure, the validation module 414 may verify the association request from the active entity when each attribute of the parent entity is within a predefined threshold range, as suggested by the policy governing the hierarchical relationship for the child entity, or vice-versa. In an exemplary scenario, multiple parent entities may be removed from the hierarchy. In such a case, the processing module 412 may identify a time of removal of each parent entity and may prioritize child entities of the earlier removed parent entity. In another exemplary scenario, for simultaneous association requests received by a single child entity from differentT1entities and verified, the processing module 412 may associate the child entity with the requesting active entity with most attribute matched.

[0067] In another scenario, when any of the abovementioned conditions is not met (i.e., the association request is not received within the stalling period, the entity requesting association with the child entity is inactive, or the active entity does not match the reassociation eligibility criteria defined by the policy governing the hierarchical relationship), the processing module 412 may be configured to terminate the child entity in accordance with the rules of the policy governing the hierarchical relationship.

[0068] Various modules of the data processing circuitry 402 are presented to illustrate the functionality driven by the CIMS node 304. It will be apparent to a person having ordinary skill in the art that various engines in the data processing circuitry 402 are for illustrative purposes and not limited to any specific combination of hardware circuitry and / or software.

[0069] The memory unit 404 may be configured to store the data associated with the CIMS node 304. The memory unit 404 may further be configured to store instruction(s) for various tasks performed by the various components of the data processing circuitry 402. In some aspects of the present disclosure, the memory unit 404 may be configured to store the code(s), logic, and / or instructions as instruction object(s) in instructions repository 420 and data of the CIMS node 304 in the form of data objects in the data repository 422.

[0070] The instructions repository 420 may be configured to store instructions and / or codes for operation(s) of various components of the CIMS node 304. According to an embodiment of the present disclosure, the instructions repository 420 may be configured to store instructions and / or codes for operation(s) being performed by various components of the CIMS node 304. According to an embodiment of the present disclosure, the instructions repository 420 may beconfigured as a non-transitory storage medium. Examples of the instructions repository 420 configured as the non-transitory storage medium include hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the instruction memory, without deviating from the scope of the present disclosure.

[0071] The data repository 422 may be configured to store data object(s) associated with (and / or generated by) the CIMS node 304. Specifically, the data object(s) may store information of the policy configuration of each network entity in the computing environment, data of the policy governing the hierarchical relationship, details of the stalling condition for each network entity, data associated with stalling period of each network entity, and data associated with the rules of the policy corresponding to a network being stalled, reassigned, or terminated.

[0072] Although FIG. 4 illustrates one example of the CIMS node 304 that includes critical components of a microservice configured to manage the network hierarchy of network entities in the communication network 100, various changes may be made to FIG. 4, without deviating from the scope of the present disclosure. Further, the CIMS node 304 may include any number of components in addition to those shown in FIG. 4 without deviating from the scope of the present disclosure. Further, various components in FIG. 4 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0073] FIG. 5 illustrates a flow chart depicting a method 500 for managing the hierarchical relationship among the network entities in the computing environment, in accordance with an embodiment of the present disclosure. The method 500 includes multiple operational steps performed by the components of the CIMS node 304, as discussed in the description of FIG. 4. As will be apparent to a person of ordinary skill in the art, the operations of the CIMS node 304 are presented in brief for the sake of brevity by way of blocks 502 through 520, however, the scope of theoperations is defined through the specification of the CIMS node 304, as discussed in FIG. 4.

[0074] At block 502, the hierarchy inspection module 410 may detect the removal or the status change for the parent entity from the plurality of entities in the hierarchical relationship.

[0075] At block 504, the transceiver module 408 may retrieve the policy configuration associated with the parent entity from the cache memory 215.

[0076] At block 506, the hierarchy inspection module 410 may identify the one or more child entities linked with the parent entity based on the policy configuration.

[0077] At block 508, the processing module 412, using the policy configuration, may determine the stalling condition for each of the one or more child entities.

[0078] At block 510, the processing module 412 may initiate the stalling period for each of the one or more child entities based on the stalling condition of corresponding child entity.

[0079] At block 512, the processing module 412 may determine whether the association request for the child entity is received from the active entity within the stalling period of the child entity. When the association request for the child entity is received from the active entity within the stalling period of the child entity, the method 500 proceeds to block 514, else, the method 500 proceeds to block 522.

[0080] At block 514, the validation module 414 may validate the association request for the child entity against allowed hierarchical relationship between the one or more entity types for the plurality of entities in the computing environment, as specified in the policy governing the hierarchical relationship.

[0081] At block 516, when the validation module 414 may determine that the association request is valid, the method 500 proceeds to block 518. Else, when thevalidation module 414 determines that the association request is invalid, the method 500 proceeds to block 522.

[0082] At block 518, the processing module 412 may determine whether the association of the child entity with the active entity (as requested through the association request) satisfies the policy governing the hierarchical relationship. When the processing module 412 determines that the association of the child entity with the active entity satisfies the policy governing the hierarchical relationship, the method 500 proceeds to block 520. Else, the method 500 proceeds to block 522. Specifically, the association of the child entity satisfies the policy when one or more attributes of the child entity match with a reassociation eligibility criteria defined by the policy governing the hierarchical relationship.

[0083] At block 520, the processing module 412 may activate the child entity based on the determination that the association of the child entity satisfies a policy governing the hierarchical relationship. Thereafter, the method 500 halts.

[0084] At block 522, the processing module 412 may terminate the child entity in accordance with the rule(s) of the policy governing the hierarchical relationship.

[0085] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments may include providing the system 200 which stores the pre-defined policies and checks in the cache memory 215 which makes their execution faster and modifiable without any overheads from the computing environment. A further potential advantage of the one or more embodiments disclosed herein may include stalling the network entity when its parent network entity is terminated for a predefined period, prior to its termination or reallocation, which improves the management of the entire hierarchical relationship in the communication network 100.

[0086] 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.

[0087] 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.

[0088] 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 comprehended within 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.

Claims

We Claim:

1. A method (500) for managing hierarchical relationship among a plurality of entities in a computing environment, the method (500) comprising:detecting, by a hierarchy inspection module (410), a removal or a status change for a parent entity from the plurality of entities in the hierarchical relationship;retrieving, by a transceiver module (408), a policy configuration associated with the parent entity from a cache memory (215);identifying, by the hierarchy inspection module (410), one or more child entities linked with the parent entity based on the policy configuration;determining, by a processing module (412) using the policy configuration, a stalling condition for each of the one or more child entities; andinitiating, by the processing module (412), a stalling period for each of the one or more child entities based on the stalling condition of corresponding child entity.

2. The method (500) as claimed in claim 1, wherein, upon initiating the stalling period, the method (500) comprising:determining, by the processing module (412), whether an association request is received for a child entity from the one or more child entities within the stalling period, wherein the association request corresponds to an association of the child entity with an active entity of the plurality of entities; andactivating, in response to a receipt of the association request for the child entity by the processing module (412), the child entity based on a determination that the association of the child entity satisfies a policy governing the hierarchical relationship.

3. The method (500) as claimed in claim 1 , wherein each child entity of the one or more child entities is placed immediately lower to the parent entity in the hierarchical relationship among the plurality of entities in the computing environment.

4. The method (500) as claimed in claim 2, wherein the stalling period is monitored by a scheduler or timer-based process that triggers a reassignment or a termination of the association of the child entity with the active entity based on an elapsed duration in the stalling period.

5. The method (500) as claimed in claim 2, wherein, in response to a determination that the association request is received for the child entity within the stalling period, the method (500) comprising:validating, by a validation module (414), the association request against allowed hierarchical relationship between one or more entity types for the plurality of entities in the computing environment, as specified in the policy governing the hierarchical relationship.

6. The method (500) as claimed in claim 2, wherein, the association of the child entity satisfies the policy when one or more attributes of the child entity match with a reassociation eligibility criteria defined by the policy governing the hierarchical relationship.

7. The method (500) as claimed in claim 2, wherein, upon the removal or the status change of the parent entity, the method (500) comprises terminating, by the processing module (412), a child entity of the one or more child entities, based on a determination that the association request is not received within the stalling period, in accordance with a rule of the policy governing the hierarchical relationship.

8. The method (500) as claimed in claim 5, wherein the policy configuration defines visibility or access rights for entity data based on one or more user roles and the one or more entity types for the plurality of entities in the computing environment.

9. A system (200) to manage hierarchical relationship among a plurality of entities in a computing environment, the system (200) comprising:a cache memory (215); anddata processing circuitry (402) coupled to the cache memory (215), wherein the data processing circuitry (402) comprises:a hierarchy inspection module (410) configured to detect a removal or a status change for a parent entity from the plurality of entities in the hierarchical relationship;a transceiver module (408) configured to retrieve a policy configuration associated with the parent entity from the cache memory (215), whereinthe hierarchy inspection module (410) is further configured to identify one or more child entities linked with the parent entity based on the policy configuration; anda processing module (412) configured to:determine, using the policy configuration, a stalling condition for each of the one or more child entities; and initiate a stalling period for each of the one or more child entities based on the stalling condition of corresponding child entity.

10. The system (200) as claimed in claim 9, wherein, upon initiation of the stalling period, the processing module (412) is configured to:determine whether an association request is received for a child entity from the one or more child entities within the stalling period, wherein the association request corresponds to an association of the child entity with an active entity of the plurality of entities; andactivate, in response to a receipt of the association request for the child entity, the child entity based on a determination that the association of the child entity satisfies a policy governing the hierarchical relationship.

11. The system (200) as claimed in claim 9, wherein each child entity of the one or more child entities is placed immediately lower to the parent entity in thehierarchical relationship among the plurality of entities in the computing environment.

12. The system (200) as claimed in claim 10, wherein the stalling period is monitored by a scheduler or timer-based process that triggers reassignment or termination of the association of the child entity with the active entity based on an elapsed duration in the stalling period.

13. The system (200) as claimed in claim 10, wherein, the data processing circuitry (402) comprises a validation module (414) configured to validate the association request against allowed hierarchical relationship between one or more entity types for the plurality of entities in the computing environment, as specified in the policy governing the hierarchical relationship, in response to the determination that the association request is received for the child entity within the stalling period.

14. The system (200) as claimed in claim 10, wherein, the association of the child entity satisfies the policy when one or more attributes of the child entity match with a reassociation eligibility criteria defined by the policy governing the hierarchical relationship.

15. The system (200) as claimed in claim 10, wherein, upon the removal or the status change of the parent entity, the processing module (412) is configured to terminate a child entity of the one or more child entities based on a determination that the association request is not received within the stalling period, in accordance with a rule of the policy governing the hierarchical relationship.

16. The system (200) as claimed in claim 13, wherein policy configuration defines visibility or access rights for entity data based on one or more user roles and one or more entity types for the plurality of entities in the computing environment.

17. A computer-program product for managing hierarchical relationship among a plurality of entities in a computing environment, the 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:detecting a removal or a status change for a parent entity from the plurality of entities in the hierarchical relationship;retrieving a policy configuration associated with the parent entity from a cache memory (215);identifying one or more child entities linked with the parent entity based on the policy configuration;determining, using the policy configuration, a stalling condition for each of the one or more child entities; andinitiating, a stalling period for each of the one or more child entities based on the stalling condition of corresponding child entity.

Images