WO2025156782A1 - Procédé et appareil de commande en boucle fermée - Google Patents
Procédé et appareil de commande en boucle ferméeInfo
- Publication number
- WO2025156782A1 WO2025156782A1 PCT/CN2024/131791 CN2024131791W WO2025156782A1 WO 2025156782 A1 WO2025156782 A1 WO 2025156782A1 CN 2024131791 W CN2024131791 W CN 2024131791W WO 2025156782 A1 WO2025156782 A1 WO 2025156782A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- request
- work object
- execution
- instance
- analysis
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
Definitions
- the present application relates to the field of communication technology, and in particular to a closed-loop control method and device.
- Closed-loop control is a method for managing networks and services.
- the entire closed-loop system operates without the involvement of human operators or other management entities, and is fully automated.
- Implementing closed-loop control in wireless communication systems is a research topic.
- Embodiments of the present application provide a closed-loop control method and apparatus to implement closed-loop control in a wireless communication system.
- a closed-loop control method which is applied to a closed-loop control loop CCL management function, and includes: receiving a first request, the first request including a first closed-loop work object, the first request being used to request creation of an instance of the first closed-loop work object; creating an instance of a first analysis work object based on the first closed-loop work object, the first analysis work object being used to request a second request to a management data analysis function MDAF; updating the instance of the first analysis work object based on a first analysis report corresponding to the second request; creating an instance of a first execution work object based on the instance of the first analysis work object; and replying to a first response, the first response including instance information of the first closed-loop work object.
- it also includes: sending a second request to the MDAF, the second request is used to request the MDAF to analyze the content included in the second request; receiving a second response from the MDAF, the second response includes the first analysis report, and the first analysis report includes indication information of the corresponding first model.
- the first analysis report also includes information indicating the impact on the network.
- the first execution work object includes one or more execution tasks, and also includes: sending a third request to the execution function, the third request including the one or more execution tasks, the third request being used to request creation of an instance of the first execution work object; receiving a third response from the execution function, the third response including the first execution result.
- the method further includes: creating an instance of a first monitoring work object based on the first closed-loop work object.
- the first monitoring work object includes one or more monitoring tasks, and also includes: sending a fourth request to the monitoring function, the fourth request including the one or more monitoring tasks, the fourth request being used to request creation of an instance of the first monitoring work object; receiving a fourth response from the monitoring function, the fourth response including the first monitoring result.
- creating an instance of the first execution work object based on the instance of the first analysis work object includes: obtaining the accuracy of the analysis report of the MDAF; when the accuracy of the analysis report of the MDAF is greater than a threshold, creating an instance of the first execution work object based on the instance of the first analysis work object.
- it also includes: sending a fifth request to the MDAF, the fifth request is used to request creation of an instance of a first execution result object, the first execution result object includes one or more execution results, and the fifth request includes the one or more execution results.
- the instance of the first closed-loop work object is associated with at least one of the following: the first analysis work object, the first analysis report corresponding to the first analysis work object, an instance of the first analysis work object, the first execution work object, the first execution result corresponding to the first execution work object, an instance of the first execution work object, the first monitoring work object, the first monitoring result corresponding to the first monitoring work object, or an instance of the first monitoring work object.
- receiving the first request includes: receiving a first request from an intent handler; and replying the first response includes: replying the first response to the intent handler.
- a closed-loop management method which is applied to a closed-loop control loop CCL management function, comprising: receiving a first request, the first request including a first closed-loop work object, the first request being used to request the creation of an instance of the first closed-loop work object; creating an instance of a first analysis work object based on the first closed-loop work object, the first analysis work object being used to send a request to a management data Requesting a second request according to the analysis function MDAF; when the accuracy of the analysis report of the MDAF is greater than a threshold, sending a second request to the MDAF, the second request is used to request the MDAF to analyze the content included in the second request, the second request includes a first indication, the first indication is used to instruct the MDAF to create an instance of a first execution work object; receiving a second response from the MDAF, the second response includes a first analysis report corresponding to the second request and a first execution result corresponding to the first execution work object.
- the first indication is further used to instruct the MDAF to create an instance of a first monitoring work object.
- the second response also includes a first monitoring result corresponding to the first monitoring work object.
- the first analysis report includes indicative information of the corresponding first model.
- the first analysis report also includes information indicating the impact on the network.
- the second response also includes: the first execution work object and/or the first monitoring work object.
- a closed-loop control method which is applied to a management data analysis function MDAF, and includes: receiving a second request from a closed-loop control loop CCL management function, the second request being used to request analysis of content included in the second request; determining a first analysis report based on the second request and a first model; and sending a second response to the CCL management function, the second response including the first analysis report, and the first analysis report including indication information of the first model.
- the first analysis report also includes information indicating the impact on the network.
- the second request includes a first indication for instructing the MDAF to create an instance of a first execution work object.
- it also includes: creating an instance of a first analysis work object based on the first analysis report; and creating an instance of the first execution work object based on the instance of the first analysis work object.
- the first execution work object includes one or more execution tasks, and also includes: sending a third request to the execution function, the third request including the one or more execution tasks, the third request being used to request creation of an instance of the first execution work object; receiving a third response from the execution function, the third response including the first execution result.
- the first indication is further used to instruct the MDAF to create an instance of a first monitoring work object.
- the method further includes: creating an instance of the first monitoring work object based on the instance of the first analysis work object.
- the first monitoring work object includes one or more monitoring tasks, and also includes: sending a fourth request to the monitoring function, the fourth request including the one or more monitoring tasks, the fourth request being used to request creation of an instance of the first monitoring work object; receiving a fourth response from the monitoring function, the fourth response including the first monitoring result.
- the second response also includes at least one of the following: the first execution work object, the first execution result, the first monitoring work object, or the first monitoring result.
- it also includes: receiving a fifth request from the CCL management function, the fifth request is used to request creation of an instance of a first execution result object, the first execution result object includes one or more execution results, and the fifth request includes the one or more execution results; based on the one or more execution results, determining whether to retrain the first model.
- a device that can implement the method of the first aspect.
- the device includes means for executing the method of the first aspect.
- the device can be implemented through hardware, software, or hardware executing the corresponding software implementation.
- the apparatus includes a unit for executing the above-mentioned first aspect.
- the apparatus includes a processor configured to execute the method of the first aspect.
- the device includes a processing circuit and an interface circuit.
- the interface circuit is configured to receive signals from a device outside the device and transmit them to the processing circuit, or to transmit signals from the processing circuit to the device outside the device.
- the processing circuit implements the method of the first aspect described above by means of a logic circuit or by executing code instructions.
- the processing circuit may be a processor, and the interface circuit may be a transceiver or an input/output interface.
- the device includes a processor and a memory; wherein the processor is used to execute a computer program or instructions stored in the memory; the memory is used to store the computer program or the instructions; when the computer program or the instructions are run, the method of the first aspect is executed.
- the device may be the first device, or a module or unit (for example, a chip, or a chip system, or a circuit) in the first device that corresponds one-to-one to the method/operation/step/action described in the first aspect, or a device that can be used in combination with the first device.
- a module or unit for example, a chip, or a chip system, or a circuit
- a device that can implement the method of the second aspect.
- the device includes means for executing the method of the second aspect.
- the device can be implemented in hardware, software, or by executing the corresponding software implementation in hardware.
- the apparatus includes a unit for executing the second aspect described above.
- the device includes a processor, which is used to execute the method of the second aspect above.
- the device includes a processing circuit and an interface circuit
- the interface circuit is used to receive signals from other devices outside the device and transmit them to the processing circuit or send signals from the processing circuit to other devices outside the device
- the processing circuit is used to implement the method in the above-mentioned second aspect through a logic circuit or executing code instructions.
- the device includes a processor and a memory; wherein the processor is used to execute a computer program or instructions stored in the memory; the memory is used to store the computer program or the instructions; when the computer program or the instructions are run, the method of the second aspect is executed.
- the device may be a second device, or a module or unit (for example, a chip, or a chip system, or a circuit) in the second device that corresponds one-to-one to the method/operation/step/action described in the second aspect, or may be capable of being used in combination with the second device.
- a module or unit for example, a chip, or a chip system, or a circuit
- a device that can implement the method of the third aspect.
- the device includes means for executing the corresponding method of the third aspect.
- the device can be implemented through hardware, software, or hardware executing the corresponding software implementation.
- the apparatus includes a unit for executing the third aspect described above.
- the device includes a processor, which is used to execute the method of the third aspect above.
- the device includes a processing circuit and an interface circuit
- the interface circuit is used to receive signals from other devices outside the device and transmit them to the processing circuit or send signals from the processing circuit to other devices outside the device
- the processing circuit is used to implement the method in the above-mentioned third aspect through a logic circuit or executing code instructions.
- the device includes a processor and a memory; wherein the processor is used to execute a computer program or instructions stored in the memory; the memory is used to store the computer program or the instructions; when the computer program or the instructions are run, the method of the third aspect is executed.
- the device may be a second device, or a module or unit (for example, a chip, or a chip system, or a circuit) in the second device that corresponds one-to-one to the method/operation/step/action described in the third aspect, or may be capable of being used in combination with the second device.
- a module or unit for example, a chip, or a chip system, or a circuit
- a computer-readable storage medium storing a computer program or instruction.
- the computer program or instruction When the computer program or instruction is run on a computer, the computer executes the method of the first aspect, the second aspect or the third aspect mentioned above.
- a computer program product includes a computer program or instructions for executing the method described in the first aspect, or the computer program product includes a computer program or instructions for executing the method described in the second aspect, or the computer program product includes a computer program or instructions for executing the method described in the third aspect.
- a chip comprising a processor coupled to a memory for executing a computer program or instruction stored in the memory, so that the chip implements the method of the first, second or third aspect above.
- a communication system comprising: a first communication device and a second communication device; wherein the first communication device is used to implement the method of the first aspect or the second aspect, and the second communication device is used to implement the method of the third aspect.
- FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application.
- FIG2 is a schematic diagram of the principle of closed-loop control provided by an embodiment of the present application.
- FIG3 is a flowchart of a closed-loop control according to an embodiment of the present application.
- FIG4 is a schematic diagram of a process provided by an embodiment of the present application.
- FIG5 is another flowchart of closed-loop control provided by an embodiment of the present application.
- FIG6 is another schematic diagram of a process flow provided in an embodiment of the present application.
- FIG7 is a schematic structural diagram of a device provided in an embodiment of the present application.
- FIG8 is another schematic diagram of the structure of the device provided in an embodiment of the present application.
- the number of nouns refers to "singular or plural," that is, “one or more.”
- “At least one” refers to one or more, and “more than one” refers to two or more.
- “And/or” describes the relationship between associated objects, indicating that three relationships can exist. For example, “A and/or B” can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural.
- FIG1 shows a possible, non-limiting system diagram.
- a communication system 10 includes a terminal 110 , an access network 120 , a core network 130 , and operations administration and maintenance (OAM) 140 .
- OAM operations administration and maintenance
- the terminal 110 can be connected to the access network 120 wirelessly.
- the access network 120 is connected to the core network 130 wirelessly or by wire.
- the core network elements in the core network 130 and the access network devices in the access network 120 can be different physical devices, or they can be a single physical device that integrates the logical functions of the core network elements and the logical functions of the wireless access network.
- a terminal may also be referred to as a terminal device, user equipment (UE), mobile station, or mobile terminal.
- Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities.
- a terminal can be a mobile phone, head-mounted display device, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home appliance, and the like. The embodiments of this application do not limit the device form factor of the terminal.
- the access network 120 includes access network devices, which may include base stations, evolved NodeBs (eNodeBs), access points (APs), transmission reception points (TRPs), next-generation NodeBs (gNBs), next-generation base stations in 6th-generation (6G) mobile communication systems, base stations in future mobile communication systems, or access nodes in wireless fidelity (WiFi) systems.
- Access network devices may include macro base stations, micro base stations, indoor stations, relay nodes, donor nodes, or wireless controllers in cloud radio access network (CRAN) scenarios.
- access network devices may include servers, wearable devices, vehicles, or onboard devices.
- access network devices in vehicle-to-everything (V2X) technology may include roadside units (RSUs).
- V2X vehicle-to-everything
- RSUs roadside units
- the core network 130 includes at least one core network element.
- the core network 130 includes an access and mobility management function (AMF) element, a session management function (SMF) element, a user plane function (UPF) element, a policy control function (PCF) element, a unified data management (UDM) element, and an application function (AF) element.
- AMF access and mobility management function
- SMF session management function
- UPF user plane function
- PCF policy control function
- UDM unified data management
- AF application function
- OAM 140 is a general term for a set of network management functions used to operate, manage, and maintain access network devices (network management of access network devices) and/or to operate, manage, and maintain core network elements (network management of core network elements).
- the OAM functions of access network devices and core network elements can be the same or different, without limitation.
- a transmission interface may exist between the two OAM functions.
- OAM may also be referred to as network management.
- access network equipment can be understood as a communication device with base station functions
- a terminal can be understood as a communication device with terminal functions
- a network element in the core network can be understood as a device with core network element functions.
- AMF can be understood as a communication device with AMF functions.
- OAM can be understood as a device with OAM functions.
- the solution provided in the embodiments of the present application can be applied to cellular systems related to the 3rd Generation Partnership Project (3GPP), such as the 4th generation (4G) mobile communication system, the 5G mobile communication system, or future evolution systems, such as the 6G mobile communication system, the communication perception integrated system, etc.
- 3GPP 3rd Generation Partnership Project
- 4G 4th generation
- 5G 5th generation
- 6G 6th generation
- the communication perception integrated system etc.
- the solution in the embodiments of the present application can be applied to other scenarios without limitation.
- the closed-loop control process includes: monitoring, analysis, decision-making and execution.
- the managed entity is monitored to obtain monitoring results. Once it is found that the monitored entity cannot meet the configured goals, the corresponding reasons can be analyzed, the corresponding solutions can be decided, and the corresponding solutions can be executed. In the entire closed-loop control process, there is no need for human operators or the participation of other management entities.
- the closed-loop control is fully automated. For example, a goal is configured for the monitored entity, and by monitoring the monitored entity, once it is found that the monitored entity deviates from the goal, the monitored entity can be automatically controlled according to the above-mentioned monitoring, analysis, decision-making and execution and other processing processes. Execute corresponding operations so that the monitored entity always meets the configured goals.
- the monitored entity could be the latency of a wireless communication network. This latency can be monitored periodically. Once the latency is found to be greater than a configured target, the network is analyzed, analysis results are obtained, and a corresponding solution is determined and implemented. For example, if the analysis of the wireless communication network reveals that congestion is causing increased latency, a corresponding solution might be to increase bandwidth or routing. In this case, the bandwidth or routing of the wireless communication network can be increased to ensure that the latency of the wireless communication network meets the configured target.
- An embodiment of the present application provides a closed-loop control method for implementing closed-loop control in a wireless communication system.
- the method includes: upon receiving an external request to create a closed-loop work object, a closed control loop (CCL) management function may create the closed-loop work object.
- CCL closed control loop
- the process of creating the closed-loop work object includes: creating an analysis work object; creating an execution work object; and further, creating a monitoring work object.
- the execution entities involved include: intent handler, CCL management function, management data analytics function (MDAF), execution function and monitoring function.
- the CCL management function and MDAF can be deployed in OAM
- the execution function and monitoring function can be deployed in OAM, or deployed in the network element of the core network.
- the intent handler can be located outside the wireless communication network, for example, it can correspond to a certain application or service.
- the execution function can also be a network element or network management function
- the monitoring function can also be a fault management (FM) or performance management (PM) management function.
- the embodiment of the present application provides a flow chart, including:
- Step 300 The intent handler sends a first request to the CCL management function, and the CCL management function receives the first request from the intent handler.
- the intent handler can create a first closed-loop work object based on the intent request.
- the intent request received by the intent handler mainly expresses: it is expected that a UPF network element will be deployed in Haidian District, Beijing.
- the UPF network element can meet the maximum number of PDU sessions of 25,000 and support a maximum number of user registrations of 2,500.
- the intent handler creates a first closed-loop work object based on the intent request. As shown in Table 1, the first closed-loop work object includes the following parameters:
- the intent handler sends a first request to the CCL management function, the first request being used to request the creation of an instance of a first closed-loop work object.
- the CCL management function may automatically trigger the creation of an instance of the first analysis work object and execute step 310.
- Step 310 The CCL management function creates an instance of a first analysis work object based on the first closed-loop work object.
- the first analysis work object may further trigger a second request to the MDAF.
- the second request may be one or more requests.
- the first request includes a first closed-loop work object.
- the CCL management function receives the first request, it can obtain the information contained in the first closed-loop work object in the first request; and create an instance of the first analysis work object based on the first closed-loop work object.
- the first analysis work object created by the CCL management function based on the first closed-loop work object includes one or more analysis tasks.
- the CCL management function sends a request (this request can be called a second request) to MDAF to request the analysis report corresponding to the analysis task. This process can be described as associating one analysis task with one request.
- the first closed-loop work object obtained by the CCL management function includes parameters as shown in Table 1.
- the CCL management function can trigger the creation of an instance of the first analysis work object and determine that the instance of the first analysis work object contains one or more analysis tasks.
- an analysis task is used to analyze the resources used to deploy the UPF. For example, the number of virtual machines required to deploy the UPF, the required virtual storage resources, the required virtual network bandwidth, etc.
- Step 320 The CCL management function sends a second request to the MDAF, and the MDAF receives the second request from the CCL management function.
- the second request is used to request the creation of an instance of the MDARequest object.
- the CCL management function may determine the second request based on the first analysis work object.
- the parameters in the second request are determined based on the parameters included in the first analysis work object.
- the second request is used to request MDAF to analyze the content included in the second request.
- MDAF receives the second request, it may determine the first analysis report based on the second request and/or select an appropriate first model.
- MDAF obtains the first analysis report in the second request. Take the content included therein, select a suitable first model and generate the input parameters of the first model according to the content included in the second request, and input the above input parameters into the first model to obtain the output parameters of the first model.
- the first model can be an artificial intelligence (AI) model or a machine learning (ML) model, referred to as a model for short, which can characterize the correspondence between input and output.
- AI artificial intelligence
- ML machine learning
- MDAF generates a first analysis report based on the first model, which can be replaced by: MDAF determines the first analysis report based on the first model and/or MDA capabilities.
- the first analysis report includes: a recommended operation.
- the recommended operation may be an operation recommended for the parameters requested in the second request.
- the second request is for requesting analysis of resources used for deploying a UPF
- the first analysis report includes: an operation recommended for deploying the UPF.
- a recommended virtualized network function (VNF) request to initiate for UPF deployment, a recommended virtualized network function (VNF) request to initiate, recommended virtualized network function descriptor (VNFD) information, etc.
- VNF virtualized network function
- VNFD recommended virtualized network function descriptor
- Step 330 MDAF sends a second response to the CCL management function, and the CCL management function receives the second response from MDAF.
- the second response includes a first analysis report.
- the first analysis report also includes indication information of the first model, such as an identifier of the first model (e.g., an identifier of an ML entity r) or a domain name DN, etc.
- the first analysis report also includes indication information of the impact on the network. For example, the time it takes to deploy the expected UPF, whether deploying the UPF according to the recommendations in the first analysis report will cause business interruption, or the resource consumption of deploying the UPF.
- the indication information of the first model can be replaced by: indication information of the first model and/or MDA capabilities.
- Step 320 and step 330 are optional and may not be performed.
- Step 340 The CCL management function creates an instance of the first analysis work object according to the first analysis report corresponding to the second request.
- the instance of the first analysis work object includes, in addition to the initial parameters of the first analysis work object, some or all parameters in the first analysis report.
- the instance of the first analysis work object also includes information indicating the first model and/or information indicating the impact on the network.
- creating an instance of the first analysis work object can also be described as updating the first analysis work object.
- Step 350 The CCL management function creates an instance of a first execution work object based on the instance of the first analysis work object.
- the CCL management function may create an instance of the first execution work object based on the instance of the first analysis work object.
- the instance of the first analysis work object includes a first analysis report
- the CCL management function may create an instance of the first execution work object based on the first analysis report.
- the CCL management function may consider the accuracy of the MDAF analysis report when creating the instance of the first execution work object. For example, the CCL management function may obtain the accuracy of the MDAF analysis report; when the accuracy of the MDAF analysis report is greater than (or greater than or equal to) a threshold, the CCL management function may create an instance of the first execution work object based on the instance of the first analysis work object.
- the third request includes one or more execution tasks, and the third request is used to request the creation of an instance of the first execution work object.
- the execution function receives the third request, it can perform corresponding operations according to the one or more execution tasks included in the third request to generate an implementation of the first execution work object.
- the instance of the first execution work object in addition to the parameters of the first execution work object, also includes a first execution result. For example, if the execution function executes the corresponding execution task successfully, the first execution result may be "success". Alternatively, if the execution function fails to execute the corresponding execution task, the first execution result may be "failure".
- an execution task can deploy UPF in a virtual network resource, then the execution function can, based on the execution task, deploy UPF in the corresponding virtual network resource. Deploy UPF in the process, and after the deployment of UPF is completed, feedback the corresponding first execution result to the CCL management function.
- Step 370 The execution function sends a third response to the CCL management function, and the CCL management function receives the third response from the execution function.
- the third response includes the first execution result.
- Step 360 and step 370 are optional and may not be performed.
- Step 380 The CCL management function creates an instance of the first monitoring work object based on the first closed-loop work object.
- the CCL management function may automatically trigger step 380 and create an instance of the first monitoring work object based on the first closed-loop work object.
- the CCL management function creates an instance of the first monitoring work object based on the target in the first closed-loop work object.
- the first monitoring work object includes one or more monitoring tasks. For example, one monitoring task may be to monitor whether the deployed UPF can support 25,000 PDU sessions during operation; another monitoring task may be to monitor whether the deployed UPF can support 2,500 user registrations during operation.
- Step 390 The CCL management function sends a fourth request to the monitoring function, and the monitoring function receives the fourth request from the CCL management function.
- the fourth request includes one or more monitoring tasks, and the fourth request is used to request the creation of an instance of the first monitoring work object.
- the monitoring function receives the fourth request, it can obtain one or more monitoring tasks in the fourth request.
- the monitoring function performs the corresponding monitoring operation according to one or more monitoring functions to determine the first monitoring result.
- the first monitoring result may be that the target is met or not met. For example, the monitoring function monitors whether the UPF can support 25,000 PDU sessions during operation, or monitors whether the UPF can support 2,500 user registrations during operation, etc. If the UPF can support the above targets during operation, the first monitoring result is that the target is met. If the UPF does not support the above targets during operation, the first monitoring result is that the target is not met.
- Step 3010 The monitoring function sends a fourth response to the CCL management function, and the CCL management function receives the fourth response from the monitoring function.
- the fourth response includes the first monitoring result.
- Steps 380 to 3010 are optional and may not be performed.
- the CCL management function may update the first execution work object shown in Table 2.
- the first execution work object may also include the following parameters as shown in Table 3:
- Step 3011 The CCL management function replies with a first response to the intent handler, and the intent handler receives the first response from the CCL management function.
- the CCL management function can update the first closed-loop work object, determine the instance of the first closed-loop work object, and the first response includes the instance information of the first closed-loop work object.
- the instance information of the first closed-loop work object includes: the identifier of the instance of the first closed-loop work object, or the parameters included in the instance and the corresponding values, etc.
- the instance of the first closed-loop work object can also be referred to as the updated first closed-loop work object.
- the instance of the first closed-loop work object is associated with at least one of the following: the first analysis work object, the first analysis report corresponding to the first analysis work object, the instance of the first analysis work object, the first execution work object, the first execution result corresponding to the first execution work object, the instance of the first execution work object, the first monitoring work object, the first monitoring result corresponding to the first monitoring work object, or the instance of the first monitoring work object, etc.
- the intent handler may obtain an instance of the first closed-loop work object in the first response. Based on the instance of the first closed-loop work object, the intent handler may generate an intent fulfillment report in the intent report. For details, refer to 3GPP TS 28.312.
- the intent handler can query the parameters of the first monitoring work object based on the DN of the first monitoring work object in the instance of the first closed-loop work object.
- the intent handler can query the parameters of the first analysis work object based on the DN of the first analysis work object in the instance of the first closed-loop work object.
- the intent handler can query the parameters of the first execution work object based on the DN of the first execution work object in the instance of the first closed-loop work object, etc.
- the CCL management function after receiving the second response from the MDAF, the CCL management function further includes:
- the CCL management function sends the instance of the successfully created first closed-loop work object to the intent handler, and the intent handler receives the instance of the successfully created first closed-loop work object sent by the CCL management function.
- the instance of the successfully created first closed-loop work object includes the parameters of the first closed-loop work object shown in Table 1, and may also include the following parameters, as shown in Table 5:
- the intent handler When the intent handler receives an instance of the successfully created first closed-loop work object, it generates an intent report (intent report).
- the intent report includes an intent feasibility check report (intent feasibility check report), and the intent feasibility check report refers to 3GPP TS28.312.
- the intent feasibility check report includes whether the recommended operation corresponding to the intent is feasible, and/or the impact of the recommended operation on the network, etc. If the intent handler agrees with the recommended operation corresponding to the intent, it will no longer reply to the CCL management function. If the intent handler disagrees with the recommended operation corresponding to the intent, it will send a renegotiation request to the CCL management function, such as updating the first closed-loop work object, or deleting the first closed-loop work object, etc. Within the waiting time of the analysis shown in Table 5, if the CCL management function does not receive a renegotiation request, steps 340 and 350 in Figure 3 are triggered to create an instance of the first execution work object.
- the CCL management function As described above, once the CCL management function has determined a specific execution plan based on the intent of the intent handler, it notifies the intent handler of the execution plan and its potential impact on the network. The intent handler can then decide whether to approve the specific execution plan and/or its impact on the network. If so, the CCL management function creates a first execution work object to execute the corresponding plan. During the execution of the plan, the intent handler's suggestions and requirements are fully considered, ensuring that the execution plan corresponding to the intent meets the intent handler's requirements.
- the CCL management function creates an instance of the first execution work object based on the instance of the first analysis work object.
- the CCL management function creates an instance of the first execution work object using other methods.
- the embodiment of the present application provides a flow chart, which at least includes:
- Step 410 The CCL management function determines the accuracy of the MDAF analysis report.
- the CCL management function creates an instance of the execution work object based on the MDAF analysis report.
- the execution function performs the corresponding operation according to the execution task of the execution work object; then, the monitoring function monitors the above operation and obtains the monitoring result.
- the accuracy of the MDAF analysis report can be determined by comparing monitoring results with preset targets. For example, if the CCL management function obtains four monitoring results, three of which meet the preset targets and one does not, the accuracy of the MDAF analysis report is 75%.
- the CCL management function may measure the accuracy of the MDAF analysis report based on one or more dimensions.
- the CCL management function may measure the accuracy of the MDAF analysis report based on dimensions such as MDA capability or model.
- MDAF may consider the following information as shown in Table 6:
- Step 420 Upon receiving a new request from the intent handler (e.g., the first request in the process of FIG3 ), the CCL management function creates an instance of the analysis work object, requests the corresponding analysis report from the MDAF, and receives the corresponding analysis report. The accuracy of the analysis report is obtained. When the accuracy of the analysis report is greater than a threshold, an instance of the first execution work object is created based on the analysis report, and a request is sent to the execution function for the instance of the execution work object.
- the intent handler e.g., the first request in the process of FIG3
- the CCL management function may obtain the MDA capability corresponding to the analysis report, i.e., the MDA capability based on which the analysis report was determined, and/or obtain the model corresponding to the analysis report, i.e., the model based on which the analysis report was determined.
- the CCL management function may determine the accuracy of the analysis report based on the MDA capability and/or the model identifier.
- the CCL management function can configure the execution policy locally.
- the locally configured execution policy includes the following parameters:
- the CCL management function may obtain the MDA capabilities and/or model identifiers corresponding to the analysis report. Based on the MDA capabilities and/or model identifiers, the CCL management function matches an execution policy. The CCL management function determines whether the accuracy of the analysis report exceeds the accuracy threshold configured in Table 7. If so, the CCL management function creates an execution work object based on the recommended actions in the analysis report. Alternatively, the CCL management function may create an execution work object based on other methods.
- the CCL after creating an execution work object, the CCL can request the execution function to perform the corresponding execution task, and can request the monitoring function to perform the corresponding monitoring task.
- the CCL management function determines that the accuracy of the MDAF analysis report exceeds a threshold, it can grant subsequent execution and monitoring permissions to the MDAF.
- the present application embodiment provides a flow chart, as shown in FIG5 , including:
- Step 500 The intent handler sends a first request to the CCL management function, and the CCL management function receives the first request from the intent handler.
- Step 510 The CCL management function creates an instance of a first analysis work object based on the first closed-loop work object.
- the first analysis work object is used to trigger a second request to the MDAF.
- steps 500 to 510 please refer to steps 300 and 310 in the process of FIG. 3 .
- Step 520 The CCL management function sends a second request to the MDAF, and the MDAF receives the second request from the CCL management function.
- the second request is used to request MDAF to analyze the parameters included in the second request.
- the CCL management function can obtain the accuracy of the MDAF analysis report.
- execution can be authorized to MDAF.
- the second request can carry a first instruction, which is used to instruct MDAF to create a first execution work object.
- a parameter named "execution allowed" may be added to the second request. If the parameter's value is the first value, it indicates that the CCL management function has authorized the execution function to MDAF. If the parameter's value is the second value, or if the parameter is not included in the second request, it indicates that the CCL management function has not authorized the execution function to MDAF.
- the CCL management function may determine whether to authorize execution to the MDAF based on a locally configured policy.
- a locally configured policy includes the following parameters:
- the CCL can authorize the execution to the MDAF; otherwise, the CCL executes the process of creating the first execution work object, see the description of Figure 3 of Example 1.
- MDAF may trigger steps 530 and 540 to create an instance of the first execution work object.
- Step 530 MDAF creates an instance of a first analysis work object according to the first analysis report.
- Step 540 MDAF creates an instance of a first execution work object according to the instance of the first analysis work object.
- the first execution work object includes one or more execution tasks.
- Step 550 The MDAF sends a third request to the execution function, and the execution function receives the third request from the MDAF.
- the third request includes one or more execution tasks, and the third request is used to request the creation of an instance of the first execution work object.
- Step 560 The execution function sends a third response to the MDAF, and the MDAF receives the third response from the execution function.
- the third response includes the first execution result.
- the first instruction in the second request is further used to instruct the MDAF to create an instance of the first monitoring work object.
- the process of FIG5 may further include steps 570 and 580.
- Step 570 MDAF creates an instance of a first monitoring work object according to the instance of the first analysis work object.
- the first monitoring work object includes one or more monitoring tasks.
- Step 580 The MDAF sends a fourth request to the monitoring function, and the monitoring function receives the fourth request from the MDAF.
- the fourth request includes one or more monitoring tasks, and the fourth request is used to request the creation of an instance of the first monitoring work object.
- Step 590 The monitoring function sends a fourth response to the MDAF, and the MDAF receives the fourth response from the monitoring function.
- the fourth response includes the first monitoring result.
- Step 5010 MDAF sends a second response to the CCL management function, and the CCL management function receives the second response from MDAF.
- the second response includes the first analysis report corresponding to the second request. Furthermore, the second response also includes at least one of the following: a first execution result corresponding to the first execution work object, a first monitoring result corresponding to the first monitoring work object, indication information of the first model corresponding to the first analysis report, indication information of network impact, the first execution work object, the first execution result, the first monitoring work object, or the first monitoring result.
- Step 5011 The CCL management function sends a first response to the intent handler, and the intent handler receives the first response from the CCL management function.
- step 5011 For the specific implementation process of step 5011, please refer to the description of step 3011 in Figure 3 of Example 1.
- the CCL management function can feed back the execution result to MDAF, and MDAF can retrain the model corresponding to the execution result based on the execution result, thereby improving the accuracy of the analysis report generated by the model in MDAF.
- the embodiment of the present application provides a flow chart, including:
- Step 610 The CCL management function sends a fifth request to the MDAF, and the MDAF receives the fifth request from the CCL management function.
- the fifth request is used to request creation of an instance of a first execution result object, the first execution result object includes one or more execution results, and the fifth request includes one or more execution results.
- the MDAF may determine whether to retrain the model based on the one or more execution results.
- MDAF can determine whether to retrain the model based on one or more execution results fed back by the CCL management function, thereby improving the accuracy of the model.
- solution of the fourth embodiment can be implemented alone, or can be implemented together with the solution of the first, second or third embodiment.
- each process the order of different steps is not limited. In addition, each process may include fewer steps or more steps than the flowchart or text description.
- the methods provided by the embodiments of the present application are introduced from the perspective of the interaction between the intent handler, CCL management function, execution function and monitoring function.
- the intent handler, CCL management function, execution function and monitoring function may include hardware structure and/or software module, and realize the above functions in the form of hardware structure, software module, or hardware structure plus software module. Whether a certain function among the above functions is executed in the form of hardware structure, software module, or hardware structure plus software module depends on the design constraints of the specific application of the technical solution.
- Figures 7 and 8 are schematic diagrams of possible devices provided in embodiments of the present application. These communication devices can implement one or more corresponding functions in the above-mentioned method embodiments. For example, functions implemented by CCL management functions or MDAF, etc., may thus achieve the beneficial effects of the above-mentioned method embodiments.
- the communication device 700 includes a processing unit 710 and a transceiver unit 720.
- a unit may also be referred to as a module.
- the processing unit may also be referred to as a processing module
- the transceiver unit may also be referred to as a transceiver module.
- a processing unit may also be referred to as a processor, processing board, processing module, processing device, etc.
- a communication unit may also be referred to as a transceiver, transceiver, transceiver module, transceiver device, etc.
- a communication unit may include at least one of a transmitting unit and a receiving unit. The transmitting unit and the receiving unit may be integrated or two independent units.
- the communication device 700 is used to implement the functions of the CCL management function in Figure 3, specifically: the transceiver unit 720 is used to receive a first request, the first request includes a first closed-loop work object, and the first request is used to request the creation of an instance of the first closed-loop work object; the processing unit 710 is used to create an instance of a first analysis work object based on the first closed-loop work object, and the first analysis work object is used to request a second request to the management data analysis function MDAF; according to the first analysis report corresponding to the second request, the instance of the first analysis work object is updated; according to the instance of the first analysis work object, an instance of the first execution work object is created; the transceiver unit 720 is also used to reply to a first response, and the first response includes instance information of the first closed-loop work object.
- the transceiver unit 720 is used to receive a first request, the first request includes a first closed-loop work object, and the first request is used to request the creation of
- the communication device 700 is used to implement the functions of the CCL management function in Figure 6, specifically: the transceiver unit 720 is used to receive a first request, the first request includes a first closed-loop work object, and the first request is used to request the creation of an instance of the first closed-loop work object; the processing unit 710 is used to create an instance of a first analysis work object based on the first closed-loop work object, and the first analysis work object is used to request a second request to the management data analysis function MDAF; the transceiver unit 720 is also used to send a second request to the MDAF when the accuracy of the analysis report of the MDAF is greater than a threshold, the second request is used to request the MDAF to analyze the content included in the second request, the second request includes a first indication, and the first indication is used to instruct the MDAF to create an instance of a first execution work object; the transceiver unit 720 is also used to receive a second response from the MDAF, the second response includes a first analysis report
- the communication device 700 is used to implement the functions of the MDAF in Figure 3 or 6, specifically: the transceiver unit 720 is used to receive a second request from the closed-loop control loop CCL management function, and the second request is used to request analysis of the content included in the second request; the processing unit 710 is used to determine a first analysis report based on the second request and the first model; the transceiver unit 720 is also used to send a second response to the CCL management function, and the second response includes the first analysis report, and the first analysis report includes indication information of the first model.
- processing unit 710 and the transceiver unit 720 For a more detailed description of the processing unit 710 and the transceiver unit 720, reference may be made to the descriptions of FIG. 3 to FIG. 6 in the above method embodiment, which will not be repeated here.
- each functional unit in the embodiments of the present application can be integrated into a physical device (for example, a processor), or each functional unit can be a separate physical device, or two or more units can be integrated into a unit for implementation.
- the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional modules.
- Figure 8 shows another schematic diagram of the structure of a communication device 800 provided in an embodiment of the present application.
- the communication device 800 shown in Figure 8 can be a hardware circuit implementation of the communication device 700 shown in Figure 7.
- Figure 8 only shows the main parts of the communication device.
- the communication device 800 includes a processor 810 and an interface circuit 820.
- the processor 810 and the interface circuit 820 are coupled to each other.
- processor 810 may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
- a general-purpose processor may be a microprocessor or any conventional processor.
- Interface circuit 820 may be a transceiver or input/output circuit, etc.
- the communication device 800 may further include a memory 830 for storing instructions executed by the processor 810, or storing input data required by the processor 810 to execute instructions, or storing data generated after the processor 810 executes instructions.
- instructions may also be referred to as computer programs, or computer program codes, etc.
- the memory 830 can be a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known in the art.
- RAM random access memory
- ROM read-only memory
- PROM programmable read-only memory
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- the processor 810 is used to implement the functions of the processing unit 710
- the interface circuit 820 is used to implement the functions of the transceiver unit 720 .
- the interface circuit 820 is used to receive signals from other communication devices outside the communication device 800 and transmit them to the processor 810, or send signals from the processor 810 to other communication devices outside the communication device.
- the processor 810 uses logic circuits or executes code instructions to implement the functions in Figures 3 to 6 above.
- An embodiment of the present application also provides a communication device, which includes a processor and a memory, the processor and the memory are coupled, and the processor is used to implement the functions in Figures 3 to 6.
- the processor can execute instructions in the memory so that the communication device implements one or more functions in the above-mentioned method embodiments, such as the functions implemented by Figures 3 to 6.
- An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium.
- the storage medium can also be an integral part of the processor.
- the processor and the storage medium can be located in an ASIC.
- the present application also provides a computer-readable storage medium storing instructions, which may also be referred to as computer programs, computer program codes, etc.
- the instructions are executed on a computer to cause the computer to perform the functions shown in FIG3 to FIG6 in the above method embodiment.
- the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device.
- the computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
- the computer program or instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless method.
- the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that integrates one or more available media.
- the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; an optical medium, such as a digital video disc; or a semiconductor medium, such as a solid-state drive.
- the computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.
- the present application also provides a computer program product, including a computer program or instructions, which, when executed on a computer, causes the method in Figures 3 to 6 to be executed.
- the computer program product includes one or more computer programs or instructions.
- the computer program or instructions When the computer program or instructions are loaded and executed on a computer, all or part of the methods in Figures 3 to 6 of the present application are executed. The process or function in.
- An embodiment of the present application also provides a chip, which includes a processor coupled to a memory, and the processor is used to execute computer programs or instructions stored in the memory, so that the chip implements the functions in Figures 3 to 6.
- An embodiment of the present application further provides a communication system, comprising: a first communication device and a second communication device.
- the first communication device is configured to implement the CCL management function described in Figures 3 to 6; the second communication device is configured to implement the MDAF function.
- the system further comprises a third communication device configured to implement the execution function; and optionally, a fourth communication device configured to implement the monitoring function.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
Procédé et appareil de commande en boucle fermée. Le procédé consiste à : recevoir une première requête, la première requête comprenant un premier objet de travail en boucle fermée, la première requête étant utilisée pour demander de créer une instance du premier objet de travail en boucle fermée ; sur la base du premier objet de travail en boucle fermée, créer une instance d'un premier objet de travail d'analyse, le premier objet de travail d'analyse étant utilisé pour envoyer une deuxième requête à une fonction d'analyse de données de gestion (MDAF) ; sur la base d'un premier rapport d'analyse correspondant à la deuxième requête, mettre à jour l'instance du premier objet de travail d'analyse ; sur la base de l'instance du premier objet de travail d'analyse, créer une instance d'un premier objet de travail d'exécution ; et répondre à une première réponse, la première réponse comprenant des informations d'instance du premier objet de travail en boucle fermée. Au moyen du procédé et de l'appareil, une commande en boucle fermée peut être réalisée dans un système de communication sans fil.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410117872.X | 2024-01-27 | ||
| CN202410117872.XA CN120389953A (zh) | 2024-01-27 | 2024-01-27 | 一种闭环控制方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2025156782A1 true WO2025156782A1 (fr) | 2025-07-31 |
Family
ID=96484174
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2024/131791 Pending WO2025156782A1 (fr) | 2024-01-27 | 2024-11-13 | Procédé et appareil de commande en boucle fermée |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN120389953A (fr) |
| WO (1) | WO2025156782A1 (fr) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113573331A (zh) * | 2020-04-29 | 2021-10-29 | 华为技术有限公司 | 一种通信方法、装置及系统 |
| WO2022067537A1 (fr) * | 2020-09-29 | 2022-04-07 | 华为技术有限公司 | Procédé de commande en boucle fermée de réseau et appareil associé |
| CN114339810A (zh) * | 2020-09-30 | 2022-04-12 | 华为技术有限公司 | 网络管理方法、装置及系统 |
| US20230097044A1 (en) * | 2021-09-28 | 2023-03-30 | Nokia Solutions And Networks Oy | Apparatus, method, and computer program |
-
2024
- 2024-01-27 CN CN202410117872.XA patent/CN120389953A/zh active Pending
- 2024-11-13 WO PCT/CN2024/131791 patent/WO2025156782A1/fr active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113573331A (zh) * | 2020-04-29 | 2021-10-29 | 华为技术有限公司 | 一种通信方法、装置及系统 |
| WO2022067537A1 (fr) * | 2020-09-29 | 2022-04-07 | 华为技术有限公司 | Procédé de commande en boucle fermée de réseau et appareil associé |
| CN114339810A (zh) * | 2020-09-30 | 2022-04-12 | 华为技术有限公司 | 网络管理方法、装置及系统 |
| US20230097044A1 (en) * | 2021-09-28 | 2023-03-30 | Nokia Solutions And Networks Oy | Apparatus, method, and computer program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN120389953A (zh) | 2025-07-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11770444B2 (en) | Edge computing for internet of things security with blockchain authentication | |
| US20220012645A1 (en) | Federated learning in o-ran | |
| WO2018219280A1 (fr) | Procédé et système de prise en charge de calcul en périphérie de réseau | |
| CN110521188B (zh) | 网络服务层中的分布式事务管理 | |
| EP4300922A1 (fr) | Procédé et appareil de mise en oeuvre de service de puissance de calcul natif, dispositif de réseau et terminal | |
| US20240340077A1 (en) | Satellite switching method, apparatus, storage medium, and chip system | |
| CN112042167A (zh) | 用于在实现移动边缘计算(mec)的通信网络中处理用户服务简档信息的方法和装置 | |
| WO2025007648A1 (fr) | Procédé de planification de tâche informatique et appareil de communication | |
| US11985195B2 (en) | Methods to enable data continuity service | |
| CN116074807A (zh) | 一种数据收集方法及通信装置 | |
| US20220006816A1 (en) | Terminal management and control method, apparatus, and system | |
| WO2025130494A1 (fr) | Procédé et appareil de communication | |
| US11134365B2 (en) | Resource link management at service layer | |
| WO2025156782A1 (fr) | Procédé et appareil de commande en boucle fermée | |
| WO2025066582A1 (fr) | Procédé et appareil de communication | |
| WO2024208017A1 (fr) | Procédé de communication, appareil de communication et système de communication | |
| US10091645B1 (en) | Handling mobile device administration in anchorless mobile networks | |
| WO2024007221A1 (fr) | Procédé et appareil de communication | |
| US20220124008A1 (en) | Automated Service Layer Message Flow Management In A Communications Network | |
| EP4568217A1 (fr) | Procédé et appareil d'analyse de données | |
| WO2025124135A1 (fr) | Procédé et appareil de communication | |
| CN120935585A (zh) | 信息传输方法及通信装置 | |
| US20240244465A1 (en) | Communication method and related device | |
| WO2025112924A1 (fr) | Système, procédé et dispositif de communication | |
| WO2025086065A1 (fr) | Procédé et appareil de communication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 24919862 Country of ref document: EP Kind code of ref document: A1 |