Method and system for closed loop management

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An Assurance Closed Control Loop (ACCL) provider receives a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer, instantiates the DynamicACCLTrigger IOC upon receiving the first request, and transmits a first response to the consumer upon the instantiating, wherein the first request comprises at least one of a performance trigger information, a provisioning trigger information, a fault trigger information, and an ACCL required attribute information.

Description

METHOD AND SYSTEM FOR CLOSED LOOP MANAGEMENTThe subject matter relates to the field of wireless communication systems. More particularly the subject matter relates to a method and a system for dynamic initiation of Assurance Closed Control Loop (ACCL) without explicit request and for handling consumer feedback in the ACCL.5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.In a first aspect of the disclosure, provided herein is a method performed by an Assurance Closed Control Loop (ACCL) provider in a wireless communication system, the method comprising: receiving a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer; instantiating the DynamicACCLTrigger IOC upon receiving the first request; and transmitting a first response to the consumer upon the instantiating, wherein the first request comprises at least one of a performance trigger information, a provisioning trigger information, a fault trigger information, and an ACCL required attribute information.In a second aspect of the disclosure, provided herein an Assurance Closed Control Loop (ACCL) provider comprising: a transceiver; and at least one processor coupled to the transceiver, configured to: receive a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer, instantiate the DynamicACCLTrigger IOC upon receiving the first request, and transmit a first response to the consumer upon the instantiating, wherein the first request comprises at least one of a performance trigger information, a provisioning trigger information, a fault trigger information, and an ACCL required attribute information.The accompanying drawings, which are incorporated in and constitute a part of the disclosure, illustrate exemplary embodiments and together with the description, serve to explain the disclosed principles. In the figures, the left most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and / or methods in accordance with embodiments of the disclosure are now described below, by way of example only, and with reference to the accompanying figures.Fig. 1ais an exemplary representation of procedural flow use case where consumer requests a provider to create an MOI for dynamic ACCL trigger based on performance assurance triggers in accordance with an embodiment of the disclosure.Fig. 1b is an exemplary representation of procedural flow use case where consumer requests a provider to create an MOI for dynamic ACCL trigger based on provisioning and fault triggers in accordance with an embodiment of the disclosure.Figs. 2a and 2b illustrate methods for defining a set of information as part of new IOC in accordance with an embodiment of the disclosure.Fig. 2c illustrates a method for a set of information that is to be added as part of Assurance Report IOC in accordance with an embodiment of the disclosure.Fig. 2d illustrates a procedure for defining a set of information as part of new IOC in accordance with an embodiment of the disclosure.Fig. 2eillustrates a network resource mode enhancement in accordance with an embodiment of the disclosure.Fig. 3shows a block diagram of a system for closed loop management in a CCL system in accordance with an embodiment of the disclosure.Fig. 4 illustrates a flowchart showing a method for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request in accordance with an embodiment of the disclosure.Fig. 5 illustrates a flowchart showing a method for closed loop management in a CCL system for handling consumer feedback in accordance with an embodiment of the disclosure.It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the disclosure. Similarly, it will be appreciated that any flowcharts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether or not such computer or processor is explicitly shown.In the document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure.The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "comprises... a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the disclosure. The following description is, therefore, not to be taken in a limiting sense.5G communication system consists of 5G Access Network (AN), 5G Core Network (CN), and User Equipment (UE) (refer TS 23.501 [3]). The 5G system is expected to provide optimized support for a variety of different communication services, different traffic loads, and different end user communities. For example, communication services using network slicing may include Vehicle-to-everything (V2X) services. The 5G system aims to enhance its capability to meet Key Performance Indicators (KPIs) that emerging V2X applications require. For these advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed, are made more stringent. 5G seamless enhanced Mobile Broadband (eMBB)- as one of the key technologies to enable network slicing, Fixed Mobile Convergence (FMC) which includes Wireless-to-the-everything (WTTx) and Fibre-to-the-everything (FTTx), is expected to provide native support for network slicing. For optimization and resource efficiency, the 5G system may select most appropriate Third Generation Partnership Project (3GPP) or non-3GPP access technology for a communication service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE, massive Internet of Thing (mIoT) connections- support for mIoT brings many new requirements in addition to MBB enhancements. Communication services with massive IoT connections such as smart households, smart grid, smart agriculture, a smart meter, and the like, may require the support of a large number and high density IoT devices to be efficient and cost effective. Operators can use one or more network slice instances to provide these communication services, which require similar network characteristics, to different vertical industries. 3GPP TS 28.530 and 28.531 define a management of network slice in 5G networks. It also defines the concept of communication services, which are provided using one or multiple network slices. A Network Slice Instance (NSI) may support multiple Communication Service Instances (CSI). Similarly, a CSI may utilize multiple NSIs.CSI System Level Simulation (SLS) assurance is undergoing work as a part of Closed Loop SLS Assurance (eCOSLA) in 3GPP SA5 working group. The Closed Control Loop (CCL) is defined as an automated control loop where there is no direct involvement of a human operator or other management entity in the control loop. The human operator or management entity does not directly control details inside the process steps but provides control outside the loop. For example, the human operator or other management entity configures goals for the control loop, to make autonomous decisions within the boundaries of set goals. Once the control loop is configured with the goals, a controlled entity is adjusted according to the set goals. In the closed control loop, an input to the control loop provided by the human operation or other management entity may include the goals or policies. The output of the closed control loop may include a status of the closed control loop to the human operator or other management entity. Typically, the goals are set within certain parameter boundaries. The closed control loop automatically monitors the network and ascertains whether the set goals are breached. When the goal is breached, the loop re-configures a network to mitigate the breach.The existing Assurance Closed Control Loop (ACCL) mechanism enables consumers to request for initiation of an ACCL with the intent to maintain particular SLS. It is expected by consumers to monitor the network to identify if there has been some Service Level Agreement (SLA) breach. Therein in case of a breach, the consumers can take actions to mitigate the breach and can also decide to initiate an ACCL to maintain the required SLS in future. This process makes the entire system inefficient because consumers have to explicitly ask to initiate an ACCL.Further, in fully automated control loops, a Network Slice Management System operates autonomously based on the predefined goals and policies, and the Network Slice Management System continually adjusts the controlled entities to meet the predefined goals and policies. However, there is no mechanism for consumers of a CCL system to express satisfaction or provide feedback concerning performance of the CCL system and outcomes. In many cases, consumer satisfaction is a vital metric in assessing the effectiveness and efficiency of the automated CCL system. The satisfaction or feedback serves as a critical indicator of whether the CCLs are meeting intended objectives and whether the CCL systems are aligned with expectations and requirements of end-users / consumers. Without a reliable means to gauge consumer satisfaction, the necessary feedback to fine-tune and optimize the CCL system and parameters are lacking, and ultimately unable to improve the overall performance of the automated CCL system. The problems can include, lack of consumer feedback, performance improvement gap, inefficient optimization, limited user-centric consumer satisfaction, and the like. There is a lack of consumer feedback as there is no formalized process or mechanism in place to solicit and capture the consumer feedback from the consumers of CCL services. When there is an absence of the consumer feedback, valuable insights that helps to enhance CCL techniques, policies, and decision-making processes are missed. Further, without direct input from consumers, suboptimal CCL performance is risked, as there is lack of data to align automation techniques with expectations. The conventional systems do not follow a user-centric approach, potentially resulting in disconnect between CCL operations and the actual consumer satisfaction.The information disclosed above is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.It is desired to address the above-mentioned disadvantages or shortcomings in the wireless communication systems.In an embodiment, the disclosure relates to a method for closed loop management in a Closed Control Loop (CCL) system. The method comprises receiving a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer. Thereafter, the method comprises instantiating the DynamicACCLTrigger IOC upon receiving the first request, and sending a first response to the consumer upon the instantiating. The first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute.In another embodiment, the disclosure relates to a method for closed loop management in a CCL system. The method comprises receiving a feedback on an existing Assurance CCL (ACCL) from a consumer, and sending a response to the consumer upon receiving the feedback on the existing ACCL.In an embodiment, the disclosure relates to a system for closed loop management in a CCL system. The system comprises a processor, and a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which on execution, cause the processor to receive a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer. Thereafter, the processor is configured to instantiate the DynamicACCLTrigger IOC upon receiving the first request, and send a first response to the consumer upon the instantiating. The first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute.In another embodiment, the disclosure relates to a system for closed loop management in a CCL system. The system comprises a processor, and a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which on execution, cause the processor to receive a feedback on an existing Assurance CCL (ACCL) from a consumer, and send a response to the consumer upon receiving the feedback on the existing ACCL.The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.The invention describes an approach which enables dynamic initiation of ACCL indicating criteria to be used for dynamic ACCL configuration without explicit request from a consumer. Accordingly, the invention allows a producer to create an ACCL based on the criteria defined. Further, a dynamic closed control loop invocation criteria comprising various parameters which are categorized into performance-based criteria, provisioning based criteria, and fault-based criteria. According to an embodiment of the disclosure, the performance-based criteria provide information related to performance measurements and Key Performance Indicators (KPIs) that need to be monitored by the producer to identify whether values have crossed the threshold defined. This may include information regarding TargetNode, Measurement or KPI Name, direction of variation, trigger value, optimal value, ACCL target, etc.In an embodiment of the disclosure, the provisioning-based criteria defines various provisioning events that need to be monitored by the producer. The provisioning-based criteria may include a target node (particular IOC or a DN) along with provisioning location, provisioning event with provisioning time, PreOrPostEvent, and ACCLTarget, etc.According to an embodiment of the disclosure, the fault-based criteria define various fault related information that needs to be monitored by the producer to see if an ACCL is to be initiated. The fault-based criteria comprise various fields such as target node, AlarmseverityThreshold, AlarmTypeThreshold, ACCLTarget, etc.Thus, the invention triggers the ACCL dynamically. Therefore, the consumers do not have to worry about initiating an ACCL, when SLA is breached, since the invention enables dynamic initiation of ACCL without explicit request from the consumer.The invention discloses a mechanism which invocates an Assurance Closed Control Loop (ACCL) dynamically that can be configured by a consumer. The producer may create the ACCL based on predefined criteria. The following are the set of criteria defined.PERFORMANCE BASED CRITERIA:This may define information related to performance measurements and KPIs that need to be monitored by the producer to observe if the values have crossed the thresholds defined. It comprises the following fields:Target Node: The identification of the managed object for which the performance is being monitored.Measurement / KPI Name: Name of the measurement or the KPI.Direction: UP or DOWN.Trigger Value: The ACCL may be triggered when the value of the measurement or KPI exceeds more than the optimal value or when the value decreases below the optimal value. The direction will be decided by Direction.Optimal Value: The expected value of the measurement or KPI.Once the Trigger Value is reached, the producer may send a notification to the consumer stating that an ACCL is required. The notification may contain information needed to instantiate an ACCL. The ACCL may be triggered appropriately as follows:ACCLTarget: IOC or DN, this attribute defines the managed object for which the ACCL may perform assurance procedures. (Currently only slice and slicesubnet can be the ACCL targets, this requires applying ACCL to entities other than Slice and SliceSubnet e.g ManagedFunction, IntentIOC).assuranceTargetName = This attribute defines the target to be met for this ACCL. This may be the name of performance measurement or KPIs as defined in TS 28.552 and 28.554 respectively.assuranceTargetValue = This attribute defines the values of the target to be met for this. This may be the value for the performance measurement or KPIs.The producer may choose to instantiate the ACCL without sending any notification to the consumer. In that case, the ACCL may be triggered appropriately, considering the information that may be provided in the notification instead.PROVISIONING BASED CRITERIA:This may define various provisioning events that need to be monitored by the producer to identify if an ACCL is to be initiated. It comprises the following fields:Target Node: This can be a particular IOC or a DN. E.g Intent IOC.Provisioning Location: The ACCL may be created only when the object created is targeting a specific location.Provisioning Event (e.g Create{in case of an IOC}, Modify, Delete): The ACCL will be created when the given event occur on the given IOC or DN.Provisioning Time: The ACCL may be created only when the given event occur at a specified time.PreOrPostProvEvent: This may define if the ACCL is to be instantiated before or after the provisioning event is completed.The ACCL may be triggered appropriately as (may not need to be standardized as it may be internal to the ACCL Consumer).ACCLTarget: Target Node, this attribute defines the managed object for which the ACCL may perform assurance procedures.FAULT BASED CRITERIA:These criteria define various fault related information that need to be monitored by the producer to see if an ACCL is to be initiated. This may define information related to performance measurements and KPIs that need to be monitored by the producer to identify if the values have crossed the thresholds defined. It comprises the following fields:Target Node: This may define the node which need to be monitored for the emitted alarms (i.e objectInstance in AlarmInformation).AlarmSeverityThreshold: This may define the "perceivedSeverity" threshold (i.e threshold for each Severity). If total number of alarms, belonging to particular perceivedSeverity (e.g., critical, major etc.), goes beyond the threshold, an ACCL will be instantiated.AlarmTypeThreshold: This may define the "AlarmType" threshold (i.e., threshold for each AlarmType). If total number of alarms, belonging to a particular alarmType, goes beyond the threshold, an ACCL may be instantiated.The ACCL may be triggered appropriately as (may not need to be standardized as it will be internal to the ACCL Consumer).ACCLTarget: Target Node, this attribute defines the managed object for which the ACCL will perform assurance procedures.Procedure flow (Performance Triggers)As illustrated in Fig. 1a, the aspect of provisioning performance triggers mechanism according to an embodiment of the disclosure is executed as follows:1. Consumer sends create MOI, for DynamicACCLTrigger IOC, request to the ACCL producer.2. The producer instantiates the IOC and return the response.3. The producer may choose to collect all the measurements provided, in this case it sends a createMOI request, for PerfMetricJob IOC as defined in 3GPP TS 28.532, to PA MnS producer.4. The PA MnS producer sends the response.5. The PA MnS producer sends the notifications with the requested data as defined in 3GPP TS 28.532.6. The producer checks for the threshold crossing.7. As an alternative, to step 3, the producer may decide to monitor only those measurements which are provided in step 1. In this case it send the createMOI for ThresholdMonitor, as defined in 3GPP TS 28.532, to PA MnS producer.8. The PA MnS producer sends the response.9. The PA MnS producer sends the threshold crossing notification as and when a particular threshold is breached.10. The producer initiates an ACCL as defined in 3GPP TS 28.536. The flow will end here. The producer will consider the trigger information provided by the consumer in step 1.11. Alternatively, the producer may choose to notify the consumer about the required ACCL. This can be performed in two ways.11.1 The producer updated the value of the attribute "aCCLAllowed" to TRUE. The consumer may get notifyAttributeValueChange notification as defined in 3GPP TS 28.532.11.2 The producer may send an aCCLRequiredNotification as defined here. This notification will include information that has triggered the need for an ACCL.11.2.1 In case of performance trigger the notification may include the following information:11.2.1.1 Performance measurement that has crossed the threshold.11.2.1.2 KPI that has crossed the threshold.11.2.1.3 The managed entity that has produced the measurement.11.2.2 In case of provisioning trigger the notification may include the following information:11.2.2.1 Provisioning event.11.2.2.2 Managed entity on which the event has occurred.11.2.2.3 Serving location of the managed entity.11.2.2.4 Time at which the event has occurred.11.2.3 In case of fault trigger the notification may include the following information:11.2.3.1 Alarm information.11.2.3.2 Node that emitted the alarm.12. The consumer may then send createMOI for AssuranceClosedControlLoop IOC as defined in 3GPP TS 28.536. The consumer may consider the trigger information provided by the consumer in step 1.13. The producer may send the response.Procedure flow (Provisioning and Fault Triggers)As illustrated in Fig. 1b, the aspect of provisioning and fault triggers mechanism according to an embodiment of the disclosure is executed as follows:1. Consumer sends create MOI, for DynamicACCLTrigger IOC, request to the ACCL producer.2. The producer instantiated the IOC and returned the response.3. The producer may subscribe for provisioning and alarm notification using ntfSubscriptionControl as defined in 3GPP TS 28.622.4. The provisioning or fault producer sends a response.5. The provisioning / fault MnS producer sends the provisioning and / or alarm notifications as requested in the subscription.6. The producer initiates an ACCL as defined in 3GPP TS 28.536. The flow ends here.7. Alternatively, the producer may choose to notify the consumer about the required ACCL. This can be performed in two ways.i. The producer updated the value of the attribute "aCCLAllowed" to TRUE. The consumer will get notifyAttributeValueChange notification as defined in 3GPP TS 28.532.ii. The producer may send an aCCLRequiredNotification as defined here.8. The consumer may then send createMOI for AssuranceClosedControlLoop IOC as defined in 3GPP TS 28.536.9. The producer may send the response.NRM EnhancementsDynamicACCLTrigger IOC is shown below in table 1.[Table 1]The invention proposes a system and a method for handling consumer feedback in Closed Control Loop (CCL) system. In the invention, a feedback is received from a consumer. The feedback received from the consumer is referred as a new set of information. The new set of information is used to maintain each CCL system. Further, the CCL system consist of Instance Object Class (IOC) data. In an embodiment of the disclosure, the new set of information may be defined as part of a new IOC. The IOC may be name contained in Assurance Closed Control Loop IOC (3GPP TS 28.536) or directly into Subnetwork IOC (3GPP TS 28.622). In an embodiment of the disclosure, the new set of information may be added as part of Assurance Report IOC. The CCL system is fine-tuned according to the new set of information provided by the consumers along with Network Resource Model (NRM) enhancement. Hence, the overall performance of the automation technique can be improved.The invention introduces a new set of information to be maintained for each CCL. The information may include a Closed Control Loop (CCL) identification, a feedback time stamp, a satisfaction score, an execution revoke, and the like. The CCL identification information is included only when the IOC is name-contained in Sub Network. The feedback time stamp indicates a time at which the feedback is provided to the CCL. The satisfaction score indicates a numeric value for providing the consumer's satisfaction for the CCL. In an example, the numeric value may range from 1 to 10 (1 being the worse). The execution revoke defines that an action taken by the CCL may be proved to be so bad or not up to consumer satisfaction that a consumer may wish to revoke them. The execution revoke indicates whether the execute actions performed by the CCL needs to be revoked. Further, the execution revoke may also provide the particular action that need to be revoked. There are several methods to include the set of information as part of network resource model definition. The methods are described in detail below.Figs. 2a and 2b illustrate methods for defining the set of information as part of new IOC in accordance with an embodiment of the disclosure. In an embodiment of the disclosure, the set of information may be defined as part of a new Instance of Class (IOC). The IOC may be name contained in Assurance Closed Control Loop IOC (3GPP TS 28.536) (as shown in Fig. 2b), or the IOC may be name contained directly into Subnetwork IOC (3GPP TS 28.622) (as shown in Fig. 2a).Fig. 2c illustrates a method for the set of information that may be added as part of Assurance Report IOC in accordance with an embodiment of the disclosure. The set of information may be added as part of Assurance Report IOC in form of a new <<datatype>>.Fig. 2d illustrates a procedure for defining a set of information as part of new IOC in accordance with an embodiment of the disclosure. In the disclosure, the procedure for defining the set of information as part of new IOC allows the consumer to provide its feedback for a particular CCL. This functionality will enable consumer satisfaction and help with fine tuning the CCL algorithm thereby improving the overall performance of the automation technique.The method for defining the set of information as part of the new IOC is explained. In step 1, the CCL gets provisioned. In step 2, the consumer sends createMOI for CCLFeedback IOC to provide feedback on an existing CCL. In step 3, a producer sends a response. In step 4, alternatively, consumer may also send modifyMOIAttribute for AssuranceReport IOC to provide feedback on an existing CCL. In step 5, the producer sends the response. In step 6, the producer checks if the action performed needs to be revoked. The value of attribute RevokeAction will indicate if the actions are to be revoked. If yes, then it will also identify the particular action(s) to be revoked. In step 7, the producer revokes the actions as indicated by the consumer. The producer may interact with other MnS Producer to revokes those actions.Fig. 2e illustrates a Network Resource Mode (NRM) enhancement in accordance with an embodiment of the disclosure. The NRM enhancements is required to enable defining the set of information as part of new IOC. Further, the relationship between the NRM enhancement and defining the set of information as part of the new IOC is shown in Fig. 2e.The IOC contains information related to the consumer feedback for a particular CCL. The description of each class of CCL Feedback is provided in the below table 2:[Table 2]Fig. 1ais an exemplary representation of procedural flow use case where consumer requests a provider to create an MOI for dynamic ACCL trigger based on performance assurance triggers in accordance with an embodiment of the disclosure.In Fig. 1a, the environment (110a) includes a consumer (101), an ACCL provider (103), and a Performance (PA) Management Service (MnS) producer (also, referred as PA MnS provider) (105) as defined in 3GPP TS 28.535 and 28.536. The ACCL provider (103) is, also, referred as a producer or a system.Hereinafter, the operation of the ACCL provider (103) to create an MOI for dynamic ACCL trigger based on performance assurance triggers without explicit request is explained with reference to Fig. 1a.At step 111, the ACCL provider (103) receives a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from the consumer (101). In an embodiment of the disclosure, the first request is a create a Managed Object instance (createMOI) request. The first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute. The performance trigger information attribute comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field. The provisioning trigger information attribute comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field. The fault trigger information attribute comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field. The ACCL required attribute specifies if the ACCL is needed as part of the DynamicACCLTrigger IOC. Upon receiving the first request, the ACCL provider (103) instantiates the DynamicACCLTrigger IOC and sends a first response to the consumer (101) upon the instantiating at step 113. In an embodiment of the disclosure, the first response is a createMOI response.In an embodiment of the disclosure, the ACCL provider (103) may choose to collect all the measurements related to the performance trigger information provided by the consumer (101) and perform following steps.At step 115, the ACCL provider (103) sends a second request for Performance Metric production Job (PerfMetricJob) IOC to the PA MnS producer (105). The second request comprises the performance trigger information attribute. In an embodiment of the disclosure, the second request is a createMOI request. In response to the second request, the ACCL provider (103) receives a second response from the PA MnS producer (105) at step 117. In an embodiment of the disclosure, the second response is a createMOI response. At step 119, the ACCL provider (103) receives a notification from the PA MnS producer (105). The notification comprises data related to the performance trigger information attribute. In an embodiment of the disclosure, the notification is a NotifyFileReady notification. At step 121, the ACCL provider (103) checks if a threshold has reached for any of the performance trigger information attribute based on the data related to the performance trigger information attribute. If the threshold has reached for any of the performance trigger information attribute, the ACCL provider (103) initiates an ACCL based on the ACCL required attribute at step 129. This type of initiation is referred as implicit initiation or without explicit request from the consumer (101). For implicit initiation to happen, the ACCL required attribute is to be set to TRUE by the consumer (101) in the first request. If the ACCL required attribute is to be set to FALSE by the consumer (101) in the first request, then the initiation is referred as explicit initiation. In case of an explicit initiation, the ACCL provider (103) sends an ACCL required notification to the consumer (101) at step 131. In response to the notification, the ACCL provider (103) receives a third request at step 133. In an embodiment of the disclosure, the third request is a createMOI request. Upon receiving the third request, the ACCL provider (103) sends a third response to the consumer (101) at step 135. In an embodiment of the disclosure, the third response is a createMOI response.In an embodiment of the disclosure, the ACCL provider (103) may choose to collect only required measurement related to the performance trigger information provided by the consumer (101) and perform following steps.At step 123, the ACCL provider (103) sends a second request for threshold monitor (ThresholdMonitor) to the PA MnS producer (105). The second request comprises one of the performance trigger information attribute. In an embodiment of the disclosure, the second request is a createMOI request. In response to the second request, the ACCL provider (103) receives a second response from the PA MnS producer (105) at step 125. In an embodiment of the disclosure, the second response is a createMOI response. At step 127, the ACCL provider (103) receives a notification from the PA MnS producer (105). The notification comprises data related to the one of the performance trigger information attribute. In an embodiment of the disclosure, the notification is a NotifyThresholdCrossing notification. At step 129, the ACCL provider (103) checks if a threshold has reached for the one of the performance trigger information attribute based on the data related to the one of the performance trigger information attribute. If the threshold has reached for the one of the performance trigger information attribute, the ACCL provider (103) initiates an ACCL based on the ACCL required attribute at step 129. This type of initiation is referred as implicit initiation or without explicit request from the consumer (101). For implicit initiation to happen, the ACCL required attribute is to be set to TRUE by the consumer (101) in the first request. If the ACCL required attribute is to be set to FALSE by the consumer (101) in the first request, then the initiation is referred as explicit initiation. In case of an explicit initiation, the ACCL provider (103) sends an ACCL required notification to the consumer (101) at step 131. In response to the notification, the ACCL provider (103) receives a third request at step 133. In an embodiment of the disclosure, the third request is a createMOI request. Upon receiving the third request, the ACCL provider (103) sends a third response to the consumer (101) at step 135. In an embodiment of the disclosure, the third response is a createMOI response.Fig. 1bis an exemplary representation of procedural flow use case where consumer requests a provider to create an MOI for dynamic ACCL trigger based on provisioning and fault triggers in accordance with an embodiment of the disclosure.In Fig. 1b, the environment (100b) includes the consumer (101), the ACCL provider (103), and a Management Service (MnS) producer (also, referred as MnS provider) (107). The MnS producer or provider is, also, referred as General Provisioning (GenProv) or Fault triggers (FS) MnS provider as defined in 3GPP TS 28.533. The ACCL provider (103) is, also, referred as a producer or a system.Hereinafter, the operation of the ACCL provider (103) to create an MOI for dynamic ACCL trigger based on provisioning and fault triggers without explicit request is explained with reference to Fig. 1b.At step 111, the ACCL provider (103) receives a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from the consumer (101). In an embodiment of the disclosure, the first request is a create a Managed Object instance (createMOI) request. The first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute. The performance trigger information attribute comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field. The provisioning trigger information attribute comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field. The fault trigger information attribute comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field. The ACCL required attribute specifies if the ACCL is needed as part of the DynamicACCLTrigger IOC. Upon receiving the first request, the ACCL provider (103) instantiates the DynamicACCLTrigger IOC and sends a first response to the consumer (101) upon the instantiating at step 113. In an embodiment of the disclosure, the first response is a createMOI response.At step 141, the ACCL provider (103) sends a subscribing request for a provisioning and alarm notification to the MnS producer (107). The subscribing request comprises at least one of the provisioning trigger information attribute, and the fault trigger information attribute. In an embodiment of the disclosure, the subscribing request is a Subscribe for Notifications request. In response to the subscribing request, the ACCL provider (103) receives a second response from the MnS producer (107) at step 143. In an embodiment of the disclosure, the second response is a Subscription Acknowledgement (ACK) response. At step 145, the ACCL provider (103) receives the provisioning and alarm notification from the MnS producer (107). The provisioning and alarm notification comprises data related to the at least one of the provisioning trigger information attribute, and the fault trigger information attribute. At step 129, the ACCL provider (103) initiates an ACCL based on the ACCL required attribute. This type of initiation is referred as implicit initiation or without explicit request from the consumer (101). For implicit initiation to happen, the ACCL required attribute is to be set to TRUE by the consumer (101) in the first request. If the ACCL required attribute is to be set to FALSE by the consumer (101) in the first request, then the initiation is referred as explicit initiation. In case of an explicit initiation, the ACCL provider (103) sends an ACCL required notification to the consumer (101) at step 131. In response to the notification, the ACCL provider (103) receives a third request at step 133. In an embodiment of the disclosure, the third request is a createMOI request. Upon receiving the third request, the ACCL provider (103) sends a third response to the consumer (101) at step 135. In an embodiment of the disclosure, the third response is a createMOI response.Figs. 2a and 2b illustrate methods for defining the set of information as part of new IOC in accordance with an embodiment of the disclosure. In an embodiment of the disclosure, the set of information may be defined as part of a new Instance of Class (IOC). The IOC may be a name contained directly into SubNetwork IOC (as shown in Fig. 2a) or the IOC may be a name contained in Assurance Closed Control Loop IOC (as shown in Fig. 2b). Fig. 2c illustrates a method for the set of information that may be added as part of Assurance Report IOC in accordance with an embodiment of the disclosure. The set of information may be added as a part of Assurance Report IOC in form of a new <<datatype>> (as shown in Fig. 2c).Fig. 2d illustrates a procedure for defining a set of information as part of new IOC in accordance with an embodiment of the disclosure.In Fig. 2d, the environment (200) includes the consumer (101), and a producer (103). The producer is, also, referred as an ACCL provider (103) or a system.Hereinafter, the operation of the producer (103) for handling consumer feedback in the ACCL when the information is modelled as a part of an IOC named contained in SubNetwork or in AssuranceClosedControlLoop IOC is explained with reference to Fig. 2d.At step 221, the producer (103) provisions an existing ACCL. Thereafter, the producer (103) receives a feedback on an existing ACCL from the consumer (101) at step 223. The feedback is one of create a Managed Object instance (createMOI) request for CCLFeedback Information Object Class (IOC) contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC (not shown in Fig. 2d). The CCLFeedback IOC comprises at least one of a CCL identification attribute, a satisfaction score attribute, a feedback time attribute, and a revoke action attribute. Upon receiving the feedback on the existing ACCL, the producer (103) sends a response to the consumer (101) at step 225. In an embodiment of the disclosure, the response is a createMOI response. At step 231, the producer (103) checks if one or more actions performed by the ACCL need to be revoked based on a value of a revoke action attribute. The revoke action attribute is received in the feedback. Based on the value of the revoke action attribute, the producer (103) revokes the one or more actions performed by the ACCL at step 233.Hereinafter, the operation of the producer (103) for handling consumer feedback in the ACCL when the information is modelled as a part of an AssuranceReport IOC is explained with reference to Fig. 2d.At step 221, the producer (103) provisions an existing ACCL. Thereafter, the producer (103) receives a feedback on an existing ACCL from the consumer (101) at step 227. The feedback can be achieved by creating an new MOI or modifying an existing one. Upon receiving the feedback on the existing ACCL, the producer (103) sends a response to the consumer (101) at step 229. In an embodiment of the disclosure, the response is a createMOI response. At step 231, the producer (103) checks if one or more actions performed by the ACCL need to be revoked based on a value of a revoke action attribute. The revoke action attribute is received in the feedback. Based on the value of the revoke action attribute, the producer (103) revokes the one or more actions performed by the ACCL at step 233.Fig. 2e illustrates a Network Resource Mode (NRM) enhancement in accordance with an embodiment of the disclosure. The NRM enhancements is required to enable defining the set of information as part of new IOC. Further, the relationship between the NRM enhancement and defining the set of information as part of the new IOC is shown in Fig. 2e.The method and the system of the invention for dynamic initiation of ACCL without explicit request and for handling consumer feedback in the ACCL are applicable to, but not limited to, 5G, and 6G telecommunication networks.Fig. 3shows a block diagram of a system for closed loop management in a CCL system in accordance with an embodiment of the disclosure.The system (103) is, also, referred as an ACCL provider (103) (as shown in Figs. 1a and 1b) or a producer (as shown in Fig. 2d). The system (103) is common for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request and for closed loop management in the CCL system for handling consumer feedback.The system (103) comprises an Input-Output (I-O) interface (301), a processor (303), and a memory (305). In an embodiment of the disclosure, data (311) is stored within the memory (305).The I-O interface (301) employs communication protocols or methods such as, without limitation, audio, analog, digital, monoaural, Radio Corporation of America (RCA) connector, stereo, IEEE®-1394 high speed serial bus, serial bus, Universal Serial Bus (USB), infrared, Personal System / 2 (PS / 2) port, Bayonet Neill-Concelman (BNC) connector, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI®), Radio Frequency (RF) antennas, S-Video, Video Graphics Array (VGA), IEEE® 802.11b / g / n / x, Bluetooth, cellular e.g., Code-Division Multiple Access (CDMA), High-Speed Packet Access (HSPA+), Global System for Mobile communications (GSM®), Long-Term Evolution (LTE®), Worldwide interoperability for Microwave access (WiMax®), or the like.The memory (305) is communicatively coupled to the processor (303) of the system (103). The memory (305), also, stores processor-executable instructions which cause the processor (303) to execute the instructions for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request and for closed loop management in the CCL system for handling consumer feedback. The memory (305) includes, without limitation, memory drives, removable disc drives, etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.The processor (303) includes at least one data processor for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request and for closed loop management in the CCL system for handling consumer feedback. The processor (303) may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.The data (311) include, for example, first request data (313), feedback data (315), and miscellaneous data (317).The first request data (313) stores at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute. The performance trigger information attribute comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field. The target node field (also, referred as target node) indicates the identification of the MOI for which the performance is being monitored. The measurement field (also, referred as measurement or KPI name) indicates name of the measurement or the KPI. The direction field (also, referred as direction) indicates UP or DOWN direction. The trigger value field (also, referred as trigger value) indicates that the ACCL may be triggered when the value of the measurement or KPI exceeds more than the optimal value or when the value decreases below the optimal value. The direction will be decided by the direction field. The optimal value field (also, referred as optimal value) indicates the expected value of the measurement or KPI. The provisioning trigger information attribute comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field. The target node field (also, referred as target node) refers to a particular IOC or a DN (Domain Name as defined by 3GPP SA5 WG), for example, Intent IOC. The provisioning location field (also, referred as provisioning location) define that the ACCL may be created only when the object created is targeting a specific location. The provisioning event field (also, referred as provisioning event) (for example, Create{in case of an IOC}, Modify, Delete) defines that the ACCL will be created when the given event occurs on the given IOC or DN. The provisioning time field (also, referred as provisioning time) define that the ACCL may be created only when the given event occurs at a specified time. The pre or post provisioning event field (also, referred as PreOrPostProvEvent) defines if the ACCL is to be instantiated before or after the provisioning event is completed. The fault trigger information attribute comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field. The target node field (also, referred as target node) defines the node which need to be monitored for the emitted alarms (i.e., objectInstance in AlarmInformation). The alarm severity threshold field (also, referred as alarm severity threshold) defines the "perceivedSeverity" threshold (i.e., threshold for each Severity). If total number of alarms belonging to particular perceivedSeverity (e.g., critical, major, etc.) goes beyond the threshold, an ACCL will be instantiated. The alarm type threshold field (also, referred as alarm type threshold) defines the "AlarmType" threshold (i.e., threshold for each AlarmType). If total number of alarms belonging to a particular alarmType goes beyond the threshold, an ACCL may be instantiated. The ACCL required attribute specifies if the ACCL is needed as part of the DynamicACCLTrigger IOC. The value TRUE will indicate that the ACCL is required. The default will be FALSE.The feedback data (315) stores at least one of a CCL identification attribute, a satisfaction score attribute, a feedback time attribute, and a revoke action attribute. The satisfaction score attribute is a value ranging from 1 to 10. The revoke action attribute indicates whether actions taken by the ACCL are to be revoked and identifies one or more actions that need to be revoked. The CCL identification attribute indicates the identification of the CCL. The feedback time attribute indicates time at which the feedback was provided.The miscellaneous data (317) stores data, including meta data, user data, and temporary files, generated by the processor (303) of the system (103) for performing the various functions of the system (103).In an embodiment of the disclosure, the data (311) in the memory (305) are processed by modules (321) of the system (103). In an embodiment of the disclousre, the modules (321) are implemented as dedicated hardware units (e.g., circuits). As used herein, the term module refers to, for example, an Application-Specific Integrated Circuit (ASIC), an electronic circuit, a Programmable System on Chip (PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. In an embodiment of the disclosure, the modules (321) are communicatively coupled to the processor (303) for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request and for closed loop management in the CCL system for handling consumer feedback. The modules (321) when configured with the functionality defined in the disclosure results in a novel hardware.In one implementation, the modules (321) include, but are not limited to, a transceiver (323), an instantiating module (325), and a checking module (327). The modules (321), also, includes miscellaneous modules (329) to perform various miscellaneous functionalities of the system (103).For closed loop management in a CCL system for dynamic initiation of ACCL without explicit request, the modules (321) comprising the transceiver (323), the instantiating module (also, referred as provisioning module) (325), and the checking module (327) of the system (103) perform following functionalities.The transceiver (323) is configured to receive a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer (101). The first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute. Upon the instantiating, the transceiver (323) is configured to send a first response to the consumer (101).The transceiver (323) is configured to send a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer (105). The second request comprises the performance trigger information attribute. In response to the second request, the transceiver (323) is configured to receive a second response from the PA MnS producer (105). The transceiver (323) is configured to receive a notification from the PA MnS producer (105). The notification comprises data related to the performance trigger information attribute.The transceiver (323) is configured to send a second request to a Performance (PA) Management Service (MnS) producer (105). The second request comprises one of the performance trigger information attribute. In response to the second request, the transceiver (323) is configured to receive a second response from the PA MnS producer (105). The transceiver (323) is configured to receive a notification from the PA MnS producer (105). The notification comprises data related to the one of the performance trigger information attribute.The transceiver (323) is configured to send a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer (107). The subscribing request comprises at least one of the provisioning trigger information attribute, and the fault trigger information attribute. In response to the subscribing request, the transceiver (323) is configured to receive a second response from the MnS producer (107). The transceiver (323) is configured to receive the provisioning and alarm notification from the PA MnS producer (107). The provisioning and alarm notification comprises data related to the at least one of the provisioning trigger information attribute, and the fault trigger information attribute.The instantiating module (325) is configured to instantiate the DynamicACCLTrigger IOC upon receiving the first request.The checking module (327) is configured to check if a threshold has reached for any of the performance trigger information attribute based on the data related to the performance trigger information attribute. If the threshold has reached for any of the performance trigger information attribute, the checking module (327) is configured to initiate an ACCL based on the ACCL required attribute.The checking module (327) is configured to check if a threshold has reached for the one of the performance trigger information attribute based on the data related to the one of the performance trigger information attribute. If the threshold has reached for the one of the performance trigger information attribute, the checking module (327) is configured to initiate an ACCL based on the ACCL required attribute. The checking module (327) is configured to initiate an ACCL based on the ACCL required attribute upon receiving the provisioning and alarm notification.For closed loop management in the CCL system for handling consumer feedback, the modules (321) comprising the transceiver (323), the instantiating module (325), and the checking module (327) of the system (103) perform following functionalities.The transceiver (323) is configured to receive a feedback on an existing Assurance CCL (ACCL) from a consumer (101). Upon receiving the feedback on the existing ACCL, the transceiver (323) is configured to send a response to the consumer (101). The feedback is one of create a Managed Object instance (createMOI) request for CCLFeedback Information Object Class (IOC) contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC or modify a Managed Object instance (modifyMOIAttribute) request contained in an AssuranceReport IOC.The instantiating module (325) is configured to provision the existing ACCL prior to receiving the feedback on the existing ACCL from the consumer (101).The checking module (327) is configured to check if one or more actions performed by the ACCL need to be revoked based on a value of a revoke action attribute. The revoke action attribute is received in the feedback. Based on the value of the revoke action attribute, the checking module (327) is configured to revoke the one or more actions performed by the ACCL.Fig. 4 illustrates a flowchart showing a method for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request in accordance with an embodiment of the disclosure.As illustrated in Fig. 4, the method (400) include one or more steps for closed loop management in a CCL system for dynamic initiation of ACCL without explicit request. The method (400) may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method (400) is described is not intended to be construed as a limitation, and any number of the described method steps can be combined in any order to implement the method. Additionally, individual steps may be deleted from the methods without departing from the scope of the disclosure described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.At step 401, the transceiver (323) of the system (103) receives a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer (101). The first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute.At step 403, the instantiating module (325) of the system (103) instantiates the DynamicACCLTrigger IOC upon receiving the first request.At step 405, the transceiver (323) of the system (103) sends a first response to the consumer upon the instantiating.Fig. 5 illustrates a flowchart showing a method for closed loop management in a CCL system for handling consumer feedback in accordance with an embodiment of the disclosure.As illustrated in Fig. 5, the method (500) include one or more steps for closed loop management in a CCL system for handling consumer feedback. The method (500) may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform particular functions or implement particular abstract data types.The order in which the method (500) is described is not intended to be construed as a limitation, and any number of the described method steps can be combined in any order to implement the method. Additionally, individual steps may be deleted from the methods without departing from the scope of the disclosure described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.At step 501, the transceiver (323) of the system (103) receives a feedback on an existing ACCL from a consumer (101).At step 503, the transceiver (323) of the system (103) sends a response to the consumer (101) upon receiving the feedback on the existing ACCL.Some of the technical advantages of the disclosure are listed below.The method of disclosure enables dynamic initiation of ACCL without explicit request from the consumer. The consumer do not have to worry about initiating an ACCL. The ACCL can be automatically initiated once the breach of an SLS is detected by the producer. The IOC (i.e., DynamicACCLTrigger) of the disclosure indicates the criteria to be used for dynamic ACCL configuration based on performance, provisioning and fault. The producer creates an ACCL based on the criteria defined.The method of the disclosure enables the consumer to provide a feedback in CCL systems. The advantages of collecting feedback for the particular CCL are performance optimization, adaptability, identification of issues, enhanced user-centricity, continuous improvement and the like.Upon receiving the consumer feedback, the CCLs (also, referred as CCL systems) can be optimized for specific use cases and scenarios, enhancing the CCLs ability to meet service-level objectives, higher user satisfaction and deliver reliable outcomes.In the disclosure, the IOC allows CCLs to adapt to changing consumer needs and priorities. As consumer preferences evolve, CCLs can adjust their operations to better serve those preferences.The consumer feedback of the disclosure serves as an early warning system for identifying issues or anomalies in CCL performance. The consumer feedback allows for prompt corrective actions and prevents potential disruptions.The introduction of the IOC in the disclosure puts the user experience at the forefront. This allows consumers to provide direct feedback on their experiences with specific CCLs, ensuring that automation techniques align closely with user needs and expectations.The IOC of the disclosure facilitates a continuous improvement cycle. Regular feedback from consumers enables transparency and ongoing refinement of CCL operations, ensuring that the automation techniques evolve in response to changing requirements and technologies.Some of the clauses are mentioned below.[1]: A method for closed loop management in a Closed Control Loop (CCL) system, the method comprising:receiving a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer;instantiating the DynamicACCLTrigger IOC upon receiving the first request; andsending a first response to the consumer upon the instantiating,wherein the first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute.[2]: The method as described in [1], wherein the performance trigger information attribute comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field,wherein the provisioning trigger information attribute comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field,wherein the fault trigger information attribute comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field, andwherein the ACCL required attribute specifies if the ACCL is needed as part of the DynamicACCLTrigger IOC.[3]: The method as described in any of [1] to [2], further comprising:sending a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises the performance trigger information attribute;receiving a second response from the PA MnS producer in response to the second request;receiving a notification from the PA MnS producer, wherein the notification comprises data related to the performance trigger information attribute;checking if a threshold has reached for any of the performance trigger information attribute based on the data related to the performance trigger information attribute; andinitiating an ACCL based on the ACCL required attribute if the threshold has reached for any of the performance trigger information attribute.[4]: The method as described in any of [1] to [2], further comprising:sending a second request to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises one of the performance trigger information attribute;receiving a second response from the PA MnS producer in response to the second request;receiving a notification from the PA MnS producer, wherein the notification comprises data related to the one of the performance trigger information attribute;checking if a threshold has reached for the one of the performance trigger information attribute based on the data related to the one of the performance trigger information attribute; andinitiating an ACCL based on the ACCL required attribute if the threshold has reached for the one of the performance trigger information attribute.[5]: The method as described in any of [1] to [2], further comprising:sending a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer, wherein the subscribing request comprises at least one of the provisioning trigger information attribute, and the fault trigger information attribute;receiving a second response from the MnS producer in response to the subscribing request;receiving the provisioning and alarm notification from the PA MnS producer, wherein the provisioning and alarm notification comprises data related to the at least one of the provisioning trigger information attribute, and the fault trigger information attribute; andinitiating an ACCL based on the ACCL required attribute upon receiving the provisioning and alarm notification.[6]: A system for closed loop management in a Closed Control Loop (CCL) system, the system comprising:a processor; anda memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which on execution, cause the processor to:receive a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer;instantiate the DynamicACCLTrigger IOC upon receiving the first request; andsend a first response to the consumer upon the instantiating,wherein the first request comprises at least one of a performance trigger information attribute, a provisioning trigger information attribute, a fault trigger information attribute, and an ACCL required attribute.[7]: The system as described in [6], wherein the performance trigger information attribute comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field,wherein the provisioning trigger information attribute comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field,wherein the fault trigger information attribute comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field, andwherein the ACCL required attribute specifies if the ACCL is needed as part of the DynamicACCLTrigger IOC.[8]: The system as described in any of [6] to [7], wherein the processor is configured to:send a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises the performance trigger information attribute;receive a second response from the PA MnS producer in response to the second request;receive a notification from the PA MnS producer, wherein the notification comprises data related to the performance trigger information attribute;check if a threshold has reached for any of the performance trigger information attribute based on the data related to the performance trigger information attribute; andinitiate an ACCL based on the ACCL required attribute if the threshold has reached for any of the performance trigger information attribute.[9]: The system as described in any of [6] to [7], wherein the processor is configured to:send a second request to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises one of the performance trigger information attribute;receive a second response from the PA MnS producer in response to the second request;receive a notification from the PA MnS producer, wherein the notification comprises data related to the one of the performance trigger information attribute;check if a threshold has reached for the one of the performance trigger information attribute based on the data related to the one of the performance trigger information attribute; andinitiate an ACCL based on the ACCL required attribute if the threshold has reached for the one of the performance trigger information attribute.

[0010] : The system as described in any of [6] to [7], wherein the processor is configured to:send a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer, wherein the subscribing request comprises at least one of the provisioning trigger information attribute, and the fault trigger information attribute;receive a second response from the MnS producer in response to the subscribing request;receive the provisioning and alarm notification from the PA MnS producer, wherein the provisioning and alarm notification comprises data related to the at least one of the provisioning trigger information attribute, and the fault trigger information attribute; andinitiate an ACCL based on the ACCL required attribute upon receiving the provisioning and alarm notification.

[0011] : A method for closed loop management in a Closed Control Loop (CCL) system, the method comprising:receiving a feedback on an existing Assurance CCL (ACCL) from a consumer; andsending a response to the consumer upon receiving the feedback on the existing ACCL.

[0012] : The method as described in

[0011] , wherein prior to receiving the feedback on the existing ACCL from the consumer, the method comprising:provisioning the existing ACCL.

[0013] : The method as described in any of

[0010] to

[0011] , wherein the feedback is one of create a Managed Object instance (createMOI) request for CCLFeedback Information Object Class (IOC) contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC or modify a Managed Object instance (modifyMOIAttribute) request contained in an AssuranceReport IOC.

[0014] : The method as described in

[0013] , wherein the CCLFeedback IOC comprises at least one of a CCL identification attribute, a satisfaction score attribute, a feedback time attribute, and a revoke action attribute, andwherein the satisfaction score attribute is a value ranging from 1 to 10, andwherein the revoke action attribute indicates whether actions taken by the ACCL are to be revoked and identifies one or more actions that need to be revoked.

[0015] : The method as described in any of

[0011] to

[0014] , further comprising:checking if one or more actions performed by the ACCL need to be revoked based on a value of a revoke action attribute, wherein the revoke action attribute is received in the feedback; andrevoking the one or more actions performed by the ACCL based on the value of the revoke action attribute.

[0016] : A system for closed loop management in a Closed Control Loop (CCL) system, the system comprising:a processor; anda memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which on execution, cause the processor to:receive a feedback on an existing Assurance CCL (ACCL) from a consumer; andsend a response to the consumer upon receiving the feedback on the existing ACCL.

[0017] : The system as described in

[0016] , wherein prior to receiving the feedback on the existing ACCL from the consumer, the processor is configured to:provision the existing ACCL.

[0018] : The system as described in any of

[0016] to

[0017] , wherein the feedback is one of create a Managed Object instance (createMOI) request for CCLFeedback Information Object Class (IOC) contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC or modify a Managed Object instance (modifyMOIAttribute) request contained in an AssuranceReport IOC.

[0019] : The system as described in

[0018] , wherein the CCLFeedback IOC comprises at least one of a CCL identification attribute, a satisfaction score attribute, a feedback time attribute and a revoke action attribute, andwherein the satisfaction score attribute is a value ranging from 1 to 10, andwherein the revoke action attribute indicates whether actions taken by the ACCL are to be revoked and identifies one or more actions that need to be revoked.

[0020] : The system as described in any of

[0016] to

[0019] , wherein the processor is configured to:check if one or more actions performed by the ACCL need to be revoked based on a value of a revoke action attribute, wherein the revoke action attribute is received in the feedback; andrevoke the one or more actions performed by the ACCL based on the value of the revoke action attribute.According to an embodiment of the disclosure, wherein the performance trigger information comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field, wherein the provisioning trigger information comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field, wherein the fault trigger information comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field, and wherein the ACCL required attribute information indicates if an ACCL is needed as part of the DynamicACCLTrigger IOC.According to an embodiment of the disclosure, transmitting a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises the performance trigger information; receiving a second response from the PA MnS producer in response to the second request; receiving a notification from the PA MnS producer, wherein the notification comprises data associated with the performance trigger information; determining if a threshold has reached for any of the performance trigger information based on the data associated with the performance trigger information; and initiating an ACCL based on the ACCL required attribute information if the threshold has reached for any of the performance trigger information.According to an embodiment of the disclosure, transmitting a second request to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises one of the performance trigger information; receiving a second response from the PA MnS producer in response to the second request; receiving a notification from the PA MnS producer, wherein the notification comprises data associated with the one of the performance trigger information; determining if a threshold has reached for the one of the performance trigger information based on the data associated with the one of the performance trigger information; and initiating an ACCL based on the ACCL required attribute information if the threshold has reached for the one of the performance trigger information.According to an embodiment of the disclosure, transmitting a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer, wherein the subscribing request comprises at least one of the provisioning trigger information, and the fault trigger information; receiving a second response from the MnS producer in response to the subscribing request; receiving the provisioning and alarm notification from the MnS producer, wherein the provisioning and alarm notification comprises data associated with the at least one of the provisioning trigger information, and the fault trigger information; and initiating an ACCL based on the ACCL required attribute information upon receiving the provisioning and alarm notification.According to an embodiment of the disclosure, provisioning an existing ACCL; receiving a feedback information on the existing ACCL from the consumer; and transmitting a feedback response to the consumer upon receiving the feedback information on the existing ACCL.According to an embodiment of the disclosure, wherein the feedback information is one of create a Managed Object instance (createMOI) request for CCLFeedback IOC contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC or modify a Managed Object instance (modifyMOIAttribute) request contained in an AssuranceReport IOC.According to an embodiment of the disclosure, wherein the CCLFeedback IOC comprises at least one of a CCL identification information, a satisfaction score, a feedback time information, and a revoke action information, wherein the satisfaction score is a value ranging from 1 to 10, and wherein the revoke action information indicates whether actions taken by the ACCL are to be revoked and one or more actions that need to be revoked.According to an embodiment of the disclosure, wherein the at least one processor is further configured to: transmit a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises the performance trigger information, receive a second response from the PA MnS producer in response to the second request, receive a notification from the PA MnS producer, wherein the notification comprises data associated with the performance trigger information, determine if a threshold has reached for any of the performance trigger information based on the data associated with the performance trigger information attribute, and initiate an ACCL based on the ACCL required attribute information if the threshold has reached for any of the performance trigger information.According to an embodiment of the disclosure, wherein the at least one processor is further configured to: transmit a second request to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises one of the performance trigger information, receive a second response from the PA MnS producer in response to the second request, receive a notification from the PA MnS producer, wherein the notification comprises data associated with the one of the performance trigger information, determine if a threshold has reached for the one of the performance trigger information based on the data associated with the one of the performance trigger information, and initiate an ACCL based on the ACCL required attribute information if the threshold has reached for the one of the performance trigger information.According to an embodiment of the disclosure, wherein the at least one processor is further configured to: transmit a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer, wherein the subscribing request comprises at least one of the provisioning trigger information, and the fault trigger information, receive a second response from the MnS producer in response to the subscribing request, receive the provisioning and alarm notification from the MnS producer, wherein the provisioning and alarm notification comprises data associated with the at least one of the provisioning trigger information, and the fault trigger information, and initiate an ACCL based on the ACCL required attribute information upon receiving the provisioning and alarm notification.According to an embodiment of the disclosure, wherein the at least one processor is further configured to: provision an existing ACCL, receive a feedback information on the existing ACCL from the consumer, and transmit a feedback response to the consumer upon receiving the feedback information on the existing ACCL.Furthermore, one or more computer readable storage media may be utilized in implementing embodiments consistent with the disclosure. A computer readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer readable storage medium stores instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include Random Access Memory (RAM), Read Only Memory (ROM), volatile memory, non-volatile memory, hard drives, Compact Disc (CD) ROMs, Digital Versatile Disks (DVDs), flash drives, disks, and any other known physical storage media.The described operations may be implemented as a method, an individual unit, system, or article of manufacture using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof. The described operations may be implemented as code maintained in a "non-transitory computer readable medium", where a processor may read and execute the code from the computer readable medium. The processor is at least one of a microprocessor and a processor capable of processing and executing the queries. A non-transitory computer readable medium may include media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, and the like), optical storage (CD ROMs, DVDs, optical disks, and the like), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware, programmable logic, and the like) and the like. Further, non-transitory computer readable media include all computer readable media except for a transitory. The code implementing the described operations may further be implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC) and the like).The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly specified otherwise.The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.When a single device or article is described herein, it will be readily apparent that more than one device / article (whether or not they cooperate) may be used in place of a single device / article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device / article may be used in place of the more than one device or article, or a different number of devices / articles may be used instead of the shown number of devices or programs. The functionality and / or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality / features. Thus, other embodiments of the invention need not include the device itself.The illustrated operations of Figs. 4 to 5 show certain events occurring in a certain order. In an embodiment of the disclosure, certain operations may be performed in a different order, modified, or removed. Moreover, steps may be added to the above-described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the scope being indicated by the following claims.REFERRAL NUMERALS:

Claims

1.A method performed by an Assurance Closed Control Loop (ACCL) provider in a wireless communication system, the method comprising:receiving a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer;instantiating the DynamicACCLTrigger IOC upon receiving the first request; andtransmitting a first response to the consumer upon the instantiating,wherein the first request comprises at least one of a performance trigger information, a provisioning trigger information, a fault trigger information, and an ACCL required attribute information.2.The method of claim 1,wherein the performance trigger information comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field,wherein the provisioning trigger information comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field,wherein the fault trigger information comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field, andwherein the ACCL required attribute information indicates if an ACCL is needed as part of the DynamicACCLTrigger IOC.3.The method of in claim 1, further comprising:transmitting a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises the performance trigger information;receiving a second response from the PA MnS producer in response to the second request;receiving a notification from the PA MnS producer, wherein the notification comprises data associated with the performance trigger information;determining if a threshold has reached for any of the performance trigger information based on the data associated with the performance trigger information; andinitiating an ACCL based on the ACCL required attribute information if the threshold has reached for any of the performance trigger information.4.The method of claim 1, further comprising:transmitting a second request to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises one of the performance trigger information;receiving a second response from the PA MnS producer in response to the second request;receiving a notification from the PA MnS producer, wherein the notification comprises data associated with the one of the performance trigger information;determining if a threshold has reached for the one of the performance trigger information based on the data associated with the one of the performance trigger information; andinitiating an ACCL based on the ACCL required attribute information if the threshold has reached for the one of the performance trigger information.5.The method of claim 1, further comprising:transmitting a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer, wherein the subscribing request comprises at least one of the provisioning trigger information, and the fault trigger information;receiving a second response from the MnS producer in response to the subscribing request;receiving the provisioning and alarm notification from the MnS producer, wherein the provisioning and alarm notification comprises data associated with the at least one of the provisioning trigger information, and the fault trigger information; andinitiating an ACCL based on the ACCL required attribute information upon receiving the provisioning and alarm notification.6.The method of claim 1, further comprising:provisioning an existing ACCL;receiving a feedback information on the existing ACCL from the consumer; andtransmitting a feedback response to the consumer upon receiving the feedback information on the existing ACCL.7.The method of claim 6, wherein the feedback information is one of create a Managed Object instance (createMOI) request for CCLFeedback IOC contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC or modify a Managed Object instance (modifyMOIAttribute) request contained in an AssuranceReport IOC.8.The method of claim 7,wherein the CCLFeedback IOC comprises at least one of a CCL identification information, a satisfaction score, a feedback time information, and a revoke action information,wherein the satisfaction score is a value ranging from 1 to 10, andwherein the revoke action information indicates whether actions taken by the ACCL are to be revoked and one or more actions that need to be revoked.9.An Assurance Closed Control Loop (ACCL) provider in a wireless communication system, the ACCL provider comprising:a transceiver; andat least one processor coupled to the transceiver, configured to:receive a first request for Dynamic Assurance Closed Control Loop Trigger (DynamicACCLTrigger) Information Object Class (IOC) from a consumer,instantiate the DynamicACCLTrigger IOC upon receiving the first request, andtransmit a first response to the consumer upon the instantiating,wherein the first request comprises at least one of a performance trigger information, a provisioning trigger information, a fault trigger information, and an ACCL required attribute information.10.The ACCL provider of claim 9,wherein the performance trigger information comprises at least one of a target node field, a measurement field, a direction field, a trigger value field, and an optimal value field,wherein the provisioning trigger information comprises at least one of the target node field, a provisioning location field, a provisioning event field, a provisioning time field, and a pre or post provisioning event field,wherein the fault trigger information comprises at least one of the target node field, an alarm severity threshold field, and an alarm type threshold field, andwherein the ACCL required attribute information indicates if an ACCL is needed as part of the DynamicACCLTrigger IOC.11.The ACCL provider of claim 9, wherein the at least one processor is further configured to:transmit a second request for Performance Metric production Job (PerfMetricJob) IOC to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises the performance trigger information,receive a second response from the PA MnS producer in response to the second request,receive a notification from the PA MnS producer, wherein the notification comprises data associated with the performance trigger information,determine if a threshold has reached for any of the performance trigger information based on the data associated with the performance trigger information attribute, andinitiate an ACCL based on the ACCL required attribute information if the threshold has reached for any of the performance trigger information.12.The ACCL provider of claim 9, wherein the at least one processor is further configured to:transmit a second request to a Performance (PA) Management Service (MnS) producer, wherein the second request comprises one of the performance trigger information,receive a second response from the PA MnS producer in response to the second request,receive a notification from the PA MnS producer, wherein the notification comprises data associated with the one of the performance trigger information,determine if a threshold has reached for the one of the performance trigger information based on the data associated with the one of the performance trigger information, andinitiate an ACCL based on the ACCL required attribute information if the threshold has reached for the one of the performance trigger information.13.The ACCL provider of claim 9, wherein the at least one processor is further configured to:transmit a subscribing request for a provisioning and alarm notification to a Management Service (MnS) producer, wherein the subscribing request comprises at least one of the provisioning trigger information, and the fault trigger information,receive a second response from the MnS producer in response to the subscribing request,receive the provisioning and alarm notification from the MnS producer, wherein the provisioning and alarm notification comprises data associated with the at least one of the provisioning trigger information, and the fault trigger information, andinitiate an ACCL based on the ACCL required attribute information upon receiving the provisioning and alarm notification.14.The ACCL provider of claim 9, wherein the at least one processor is further configured to:provision an existing ACCL,receive a feedback information on the existing ACCL from the consumer, andtransmit a feedback response to the consumer upon receiving the feedback information on the existing ACCL.15.The ACCL provider of claim 14,wherein the feedback information is one of create a Managed Object instance (createMOI) request for CCLFeedback IOC contained in a Subnetwork IOC or createMOI request for CCLFeedback IOC contained in an AssuranceClosedControlLoop IOC or modify a Managed Object instance (modifyMOIAttribute) request contained in an AssuranceReport IOC,wherein the CCLFeedback IOC comprises at least one of a CCL identification information, a satisfaction score, a feedback time information and a revoke action information,wherein the satisfaction score is a value ranging from 1 to 10, andwherein the revoke action information indicates whether actions taken by the ACCL are to be revoked and one or more actions that need to be revoked.

Images