Communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and apparatus, capable of improving the recovery efficiency from base station outage. The method may comprise: receiving an outage recovery intention request from an IDMS consumer, wherein the outage recovery intention request comprises outage object information, outage duration information, and importance evaluation information, the outage object information is used for indicating at least one outage object, the outage duration information is used for indicating an allowed maximum outage duration for each outage object among the at least one outage object, and the importance evaluation information is used for indicating an importance level of each outage object; and on the basis of the outage recovery intention request, determining an outage recovery intention, wherein the outage recovery intention is used for instructing to, in descending order of the importance level of the at least one outage object, restore each outage object to normal operation within a target duration for the outage object, and the target duration for each outage object is determined on the basis of the maximum outage duration and importance level of the outage object.

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202510284876.1, filed on March 10, 2025, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a communication method and apparatus. Background Technology

[0003] The impact of network outages in communication networks is generally significant, as it directly affects the quality of service for users. Taking base station outages as an example, this refers to the base station equipment losing its operational capability and being unable to provide normal service; it is a major factor influencing network interruptions. Industry statistics show that over half of the fault incidents experienced by operators are related to base station outages, and the duration of outages is a key performance indicator for operators. A prolonged outage can severely impact the performance of an entire district / county or even a city-level branch. Therefore, timely restoration of base station outages is crucial for operators.

[0004] Therefore, how to improve the recovery efficiency of base station outages has become an urgent problem to be solved by those skilled in the art. Summary of the Invention

[0005] This application provides a communication method and apparatus that can improve the recovery efficiency of base station outages.

[0006] In a first aspect, embodiments of this application provide a communication method, which may include: receiving a service termination and recovery intent request from an intent-driven management service (IDMS) consumer, the service termination and recovery intent request including service termination object information, service termination duration information, and importance evaluation information, wherein the service termination object information is used to indicate at least one service termination object, the service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information is used to indicate the importance level of each service termination object; and determining a service termination and recovery intent based on the service termination and recovery intent request, wherein the service termination and recovery intent is used to instruct that each service termination object be restored to normal within a target duration in descending order of the importance level of the at least one service termination object, and the target duration of each service termination object is determined based on the maximum service termination duration and importance level of each service termination object.

[0007] In one possible implementation, the method can be executed by the IDMS producer.

[0008] Using the communication method provided in this application, the IDMS consumer directly or indirectly specifies the outage object in the outage recovery intention request, i.e., the expected target entity that needs troubleshooting, and expresses multiple troubleshooting goals, i.e., the desired time (i.e., target duration) for resolving the outage issue of this object. Considering the differences in the services affected by different base stations or cells, the IDMS consumer can also specify its importance factors and corresponding weights in the outage recovery intention request. The IDMS producer calculates the importance of each outage object based on this information and matches an appropriate target duration for each outage object accordingly, thereby performing troubleshooting operations. This improves the recovery efficiency of the outage object.

[0009] In one possible implementation, the target duration of each outgoing object is inversely proportional to the importance of that outgoing object.

[0010] Using the communication method provided in this application embodiment, the more important the out-of-service object, the higher the processing priority, and the shorter the corresponding target duration. This allows the most important out-of-service objects to be restored first in the shortest time, thereby improving the restoration efficiency of out-of-service objects.

[0011] In one possible implementation, the method further includes: based on the service outage recovery intention, troubleshooting the at least one service outage object in descending order of importance.

[0012] In one possible implementation, the decommissioned object information includes the identifier of the at least one decommissioned object; and / or, the importance evaluation information includes the importance level of each decommissioned object.

[0013] The communication method provided in this application directly indicates the importance of each out-of-service object in the importance evaluation information. This eliminates the need to request each out-of-service object or PM to report the importance factor of each out-of-service object. Based on the importance factor and corresponding weight of each out-of-service object, the importance of each out-of-service object is determined. Therefore, communication overhead can be reduced, thereby improving the recovery efficiency of out-of-service objects.

[0014] In one possible implementation, the out-of-service object information includes the identifier of the at least one out-of-service object, or includes at least one of the object type or constraint of the at least one out-of-service object, wherein the object type includes a base station or a cell, and the constraint includes the coverage area of ​​the out-of-service object; and / or, the importance evaluation information includes at least one importance factor for evaluating the importance of the out-of-service object and the weight of each of the at least one importance factor.

[0015] Using the communication method provided in this application embodiment, the IDMS producer requests each decommissioned object or PM to report the importance factor of each decommissioned object, and determines the importance of each decommissioned object based on the importance factor and corresponding weight. This allows for real-time and flexible adjustment of the importance of each decommissioned object, thereby improving the recovery efficiency of decommissioned objects.

[0016] In one possible implementation, the importance of each de-service object is determined based on a target importance factor of each de-service object and the weight of that target importance factor, wherein the at least one importance factor includes the target importance factor of each de-service object.

[0017] In one possible implementation, before determining the service termination and recovery intention based on the service termination and recovery intention request, the method further includes: sending importance request information to a service termination object management device, the importance request information being used to request a target importance factor for each service termination object, the importance request information including at least one importance factor and an identifier for each service termination object; and receiving importance feedback information from the service termination object management device, the importance feedback information being used to indicate the target importance factor for each service termination object.

[0018] In one possible implementation, after determining the service termination intention based on the service termination intention request, the method further includes: the IDMS producer troubleshooting the at least one service termination object in descending order of importance based on the service termination intention.

[0019] In one possible implementation, before the IDMS producer troubleshoots the at least one out-of-service object, the method may further include: the IDMS producer sending a fault cause request to the analysis / processing NF, the fault cause request being used to request analysis of the fault cause of each out-of-service object; and receiving fault cause feedback from the analysis / processing NF, the fault cause feedback being used to indicate the fault cause of each out-of-service object.

[0020] Accordingly, the IDMS producer can troubleshoot the at least one out-of-service object based on the outage recovery intention and the fault cause feedback.

[0021] Optionally, troubleshooting of the at least one out-of-service object can be performed by the IDMS or by the analysis / processing NF, and this application embodiment does not limit this.

[0022] In one possible implementation, after the IDMS producer troubleshoots the at least one out-of-service object, the method may further include: the IDMS producer sending an out-of-service recovery intention report to the IDMS consumer, the out-of-service recovery intention report indicating whether to recover from the failure according to the importance of the at least one out-of-service object, and that each out-of-service object recovers to normal within the target duration of each out-of-service object.

[0023] Optionally, the outage recovery intent report is also used to indicate the cause of failure for each outage object.

[0024] Secondly, embodiments of this application also provide a communication method, which may include: sending a service termination and recovery intention request to an intent-driven management service (IDMS) producer. The service termination and recovery intention request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object, the service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information is used to indicate the importance of each service termination object.

[0025] In one possible implementation, the method can be executed by an IDMS consumer.

[0026] It should be noted that the communication method provided in the second aspect is the same process as the communication method provided in the first aspect. Therefore, the detailed descriptions and beneficial effects in the second aspect can be found in the corresponding descriptions in the first aspect, and will not be repeated here.

[0027] Thirdly, embodiments of this application also provide a communication method, which may include: receiving a service termination and recovery intention request from an Intent-Driven Management Service (IDMS) consumer, the service termination and recovery intention request including at least one of termination object information, importance evaluation information, termination rate information, or termination duration information, wherein the termination object information is used to indicate at least one termination object, the importance evaluation information is used to indicate the importance of each of the at least one termination object, the termination rate information is used to indicate a target ratio of the currently acceptable number of termination objects to the total number of objects, and the termination duration information is used to indicate an acceptable target duration when the ratio of the current number of termination objects to the total number of objects is less than or equal to the target ratio; and determining a service termination and recovery intention based on the service termination and recovery intention request, the service termination and recovery intention being used to instruct, within the target duration, to restore the at least one termination object to normal operation in descending order of importance, until the ratio of the currently remaining number of termination objects to the total number of objects is less than or equal to the target ratio.

[0028] In one possible implementation, the method can be executed by the IDMS producer.

[0029] Using the communication method provided in this application, IDMS consumers can tolerate a certain level of service outages. Therefore, they will specify the acceptable level of outages in the outage recovery intention request in the form of "maximum outage rate" and "maximum number of outages." Furthermore, a "maximum outage duration" will be provided as the maximum allowable resolution time in the overall outage scenario when the outage rate or number of outages reaches a specified value. IDMS producers can restore faults according to their importance to achieve the required outage rate / number of outages within a specified time, thus improving the recovery efficiency of outages.

[0030] It should be noted that the above outage rate information is used to indicate the maximum acceptable outage rate after troubleshooting, i.e., the target ratio.

[0031] Optionally, the above service outage rate information can be replaced with service outage number information, which is used to indicate the maximum acceptable number of service outages after troubleshooting, i.e., the target number.

[0032] It should also be noted that the above-mentioned outage duration information is used to indicate the maximum acceptable resolution time, i.e., the target time, when troubleshooting reaches the maximum outage rate or maximum number of outages.

[0033] Optionally, the embodiments of this application do not limit the content included in the intention to restore service after service termination.

[0034] In one possible implementation, the request to restore service after a server outage may include information about the outage object, importance evaluation information, and outage rate information (or number of outages).

[0035] In another possible implementation, the service termination and recovery intention request may include information about the terminated object, importance evaluation information, and service termination duration information.

[0036] In another possible implementation, the request to restore service may include information about the service being terminated, importance evaluation information, termination rate information (or number of terminations), and termination duration information.

[0037] In other words, the intention to restore service termination can constrain only the maximum termination rate (or the maximum number of terminations); or only the maximum resolution time; or both the maximum termination rate (or the maximum number of terminations) and the maximum resolution time.

[0038] In one possible implementation, the method further includes: based on the service outage recovery intention, within the target duration, troubleshooting the at least one outage object in descending order of importance, until the ratio of the current remaining number of outage objects to the total number of objects is less than or equal to the target ratio.

[0039] Fourthly, embodiments of this application also provide a communication method, which may include: sending a service termination and recovery intention request to an intent-driven management service (IDMS) producer. The service termination and recovery intention request includes at least one of service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object, the importance evaluation information is used to indicate the importance of each of the at least one service termination object, the service termination rate information is used to indicate the target ratio of the currently acceptable number of service termination objects to the total number of objects, and the service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0040] In one possible implementation, the method can be executed by an IDMS consumer.

[0041] It should be noted that the communication method provided in the fourth aspect corresponds to the communication method provided in the third aspect. Therefore, the detailed descriptions and beneficial effects in the fourth aspect can be found in the corresponding descriptions in the third aspect, and will not be repeated here.

[0042] Fifthly, embodiments of this application also provide a communication device for implementing the methods described in the above aspects or any possible implementation thereof, the device including units for implementing the methods described in the above aspects or any possible implementation thereof.

[0043] Sixthly, embodiments of this application also provide a communication device, which includes at least one processor and a communication interface. The at least one processor transmits signals and / or data through the communication interface. When the at least one processor executes program code or instructions, it implements the methods described in the above aspects or any possible implementation thereof.

[0044] Alternatively, the communication device may be a chip device.

[0045] In a seventh aspect, this application also provides a computer-readable storage medium for storing a computer program, the computer program including instructions for implementing the methods described in the foregoing aspects or any possible implementation thereof.

[0046] Eighthly, this application also provides a computer program product containing instructions that, when executed on a computer or processor, cause the computer or processor to implement the methods described in the foregoing aspects or any possible implementation thereof.

[0047] The communication device, computer storage medium, computer program product, and chip device provided in the embodiments of this application are all used to execute the communication method provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the communication method provided above, and will not be repeated here. Attached Figure Description

[0048] Figure 1 is a schematic block diagram of a communication system 100 provided in an embodiment of this application;

[0049] Figure 2 is a schematic diagram of the 3rd generation partnership project (3GPP) network architecture applicable to the communication system 100 provided in the embodiments of this application;

[0050] Figure 3 is a schematic diagram of the open radio access network (O-RAN) network architecture applicable to the communication system 100 provided in the embodiments of this application;

[0051] Figure 4 is a schematic diagram of the autonomous platform (A-platform) network architecture applicable to the communication system 100 provided in the embodiments of this application;

[0052] Figure 5 is a schematic flowchart of the communication method 200 provided in an embodiment of this application;

[0053] Figure 6 is a schematic diagram of the service recovery intention provided in an embodiment of this application;

[0054] Figure 7 is another schematic diagram of the intention to restore service according to an embodiment of this application;

[0055] Figure 8 is another schematic diagram of the intention to restore service provided in the embodiments of this application;

[0056] Figure 9 is a schematic flowchart of the communication method 300 provided in an embodiment of this application;

[0057] Figure 10 is another schematic diagram of the intention to restore service provided in the embodiments of this application;

[0058] Figure 11 is another schematic diagram of the intention to restore service provided in the embodiments of this application;

[0059] Figure 12 is a schematic block diagram of a communication device 400 provided in an embodiment of this application;

[0060] Figure 13 is a schematic block diagram of the communication device 500 provided in an embodiment of this application;

[0061] Figure 14 is a schematic block diagram of a communication device 600 provided in an embodiment of this application;

[0062] Figure 15 is a schematic block diagram of a communication device 700 provided in an embodiment of this application. Detailed Implementation

[0063] Figure 1 is a schematic block diagram of a communication system 100 provided in an embodiment of this application. As shown in Figure 1, the system 100 may include an intent-driven management service (IDMS) consumer 110 and an IDMS producer 120. The IDMS consumer 110 is the entity requesting IDMS. The IDMS producer 120 is the entity providing IDMS.

[0064] Optionally, the system 100 may further include a service termination object management device 130. This service termination object management device 130 is used to provide relevant information about service termination objects to determine their importance.

[0065] Optionally, the out-of-service object management device 130 can be an out-of-service object or performance management (PM). The out-of-service object can be a base station (group) or a cell (group); the PM can be a performance management module within the network, responsible for collecting measurable key performance indicators (KPIs) for all out-of-service objects.

[0066] It should be noted that the "out-of-service objects" mentioned in this application embodiment refer to objects that are unable to provide services (i.e., out-of-service objects) due to various fault reasons.

[0067] Optionally, the system 100 may further include a network function (NF) 140. This NF 140 is used to analyze the cause of an object's failure or to handle the failure (i.e., troubleshooting).

[0068] Alternatively, the IDMS producer 120 can also be used to handle faults.

[0069] Optionally, the above system 100 can be applied to various network architectures, and the embodiments of this application do not limit this.

[0070] In the first possible implementation, the system 100 can be adapted to a 3GPP network architecture.

[0071] For example, Figure 2 illustrates a schematic diagram of the 3GPP network architecture applicable to the communication system 100 provided in this application embodiment. As shown in Figure 2, the 3GPP network may include a radio access network (RAN) and operation, administration and maintenance (OAM). The RAN may include base stations / cells, and the OAM may include element management service (EMS) and network management service (NMS). The EMS may include configuration management (CM) / performance management (PM) and analysis / processing (NF). For example, the NMS and the EMS can communicate via a 3GPP interface.

[0072] For example, the IDMS consumer 110 can be located in the NMS in Figure 2, the IDMS producer 120 can be located in the EMS in Figure 2, the outage object management device 130 can be the base station / cell or PM in Figure 2, and the analysis / processing NF 140 can be the analysis / processing NF in Figure 2.

[0073] Optionally, a third-party application server can be deployed on the 3GPP network shown in Figure 2, which can provide IDMS services. For example, the NMS and the third-party application server can communicate through the third-party application service interface.

[0074] For example, the IDMS consumer 110 may be located on a third-party application server in Figure 2, and the IDMS producer 120 may be located on an NMS in Figure 2.

[0075] In the second possible implementation, the system 100 can be adapted to an O-RAN network architecture.

[0076] For example, Figure 3 illustrates a schematic diagram of the O-RAN network architecture applicable to the communication system 100 provided in this application embodiment. As shown in Figure 3, the O-RAN network may include O-RAN and service management and orchestration (SMO). O-RAN may include base stations / cells, and SMO may include non-real-time RAN intelligent controllers (Non-RT RICs) and other SMO service producers. The Non-RT RIC may include raPP, CM / PM, and analytics / processing NF.

[0077] For example, the IDMS consumer 110 may be located in other SMO service producers in Figure 3, the IDMS producer 120 may be located in raPP in Non-RT RIC in Figure 3, the outage object management device 130 may be a base station / cell or PM in Figure 3, and the analysis / processing NF 140 may be an analysis / processing NF in Figure 3.

[0078] Optionally, a third-party application server can be deployed on the O-RAN network in Figure 3, which can provide IDMS services. For example, the SMO and the third-party application server can communicate through the third-party application service interface (such as the R1 interface).

[0079] For example, the IDMS consumer 110 may be located in the third-party application server in Figure 3, and the IDMS producer 120 may be located in the Non-RT RIC in Figure 3.

[0080] In a third possible implementation, system 100 can be adapted to an A-platform network architecture.

[0081] For example, Figure 4 illustrates a schematic diagram of the A-platform network architecture applicable to the communication system 100 provided in this application embodiment. As shown in Figure 4, the A-platform network may include RAN and OAM, wherein the RAN may include base stations / cells, the OAM may include network agents, service agents, A-platform, and analysis / processing NF, and the A-platform may include CM / PM.

[0082] Optionally, a third-party application server can be deployed on the A-platform network shown in Figure 4, which can provide IDMS services. For example, the OAM and the third-party application server can communicate through the third-party application service interface.

[0083] For example, the IDMS consumer 110 may be located in the third-party application server in Figure 4, the IDMS producer 120 may be located in the OAM in Figure 4, the outage object management device 130 may be the base station / cell in Figure 4 or the PM in the OAM, and the analysis / processing NF 140 may be the analysis / processing NF in the OAM in Figure 4.

[0084] In existing technologies, when a system detects a failure in a service-out object, it issues a fault work order. The fault handling system processes each received work order one by one. This may result in less important fault work orders arriving first. When network management resources are limited, prioritizing the processing of less important fault work orders may consume too many resources and may cause later critical fault work orders to not be processed first. Therefore, the recovery efficiency of service-out objects is low.

[0085] To address the aforementioned issues, this application provides a communication method and apparatus. The method involves an IDMS consumer sending a service termination and recovery intention request to an IDMS producer. This request includes termination object information, termination duration information, and importance evaluation information. The termination object information indicates at least one termination object, the termination duration information indicates the maximum allowed termination duration for each of the at least one termination object, and the importance evaluation information indicates the importance level of each termination object. Based on the service termination and recovery intention request, a service termination and recovery intention is determined. This intention instructs each termination object to return to normal operation within a target duration, ordered from highest to lowest importance, according to the target duration of the at least one termination object. The target duration for each termination object is determined based on its maximum termination duration and importance level.

[0086] By using the method and apparatus provided in the embodiments of this application, the target duration corresponding to different levels of importance of the service termination object is given in the service termination recovery intention, so as to ensure that high-priority service termination objects can be recovered quickly, while low-priority service termination objects can be processed within a longer time window, thereby optimizing resource allocation and improving the recovery efficiency of service termination objects.

[0087] The communication system provided by the embodiments of this application has been described above with reference to Figures 1 to 4. The communication method applied to the above communication system will be further described below.

[0088] Figure 5 shows a schematic flowchart of a communication method 200 provided in an embodiment of this application. This method 200 can be used in the system 100 described above. As shown in Figure 5, the method 200 may include the following steps.

[0089] S201. The IDMS consumer sends a service termination and recovery intention request to the IDMS producer. The service termination and recovery intention request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object. The service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object. The importance evaluation information is used to indicate the importance of each service termination object.

[0090] In one possible implementation, the IDMS consumer can be IDMS consumer 110 in the system 100 described above, and the IDMS producer can be IDMS producer 120 in the system 100 described above.

[0091] Optionally, the information on the object that has withdrawn from service can indicate the at least one object that has withdrawn from service in a variety of ways, and this application embodiment does not limit this.

[0092] In one possible implementation, the decommissioned object information may include the identifier of the at least one decommissioned object.

[0093] For example, the outage object information may include: "base station A" and "base station B".

[0094] In another possible implementation, the out-of-service object information may include at least one of the object type or constraint of the at least one out-of-service object, wherein the object type includes a base station or a cell, and the constraint includes the coverage area of ​​the out-of-service object.

[0095] For example, the outage object information may include: object type: base station; coverage area: area A, area B, and area C. That is, the base station in coverage area 1 is base station A, the base station in coverage area 2 is base station B, and the base station in coverage area 3 is base station C.

[0096] Optionally, the importance evaluation information can indicate the importance of each decommissioned object in a variety of ways, and the embodiments of this application do not limit this.

[0097] In one possible implementation, the importance evaluation information may include the degree of importance of each decommissioned object.

[0098] For example, taking the at least one out-of-service object as including "base station A" and "base station B", the importance evaluation information may include: the importance level of "base station A" is level 1, and the importance level of "base station B" is level 2, wherein level 1 is more important than level 2.

[0099] In other words, this importance assessment information directly indicates the importance of each object that has left the service.

[0100] In one possible implementation, the importance evaluation information may include at least one importance factor for evaluating the importance of a decommissioned object and a weight for each of the at least one importance factor.

[0101] For example, taking the base station as the object type of the out-of-service object, the at least one importance factor may include: base station type (weight 30%), service object (weight 30%), and backup mechanism (weight 40%).

[0102] For example, taking the object type of the deactivated object as a cell, the at least one importance factor may include: cell type (weight 50%) and number of active users (weight 50%).

[0103] In other words, this importance evaluation information can indirectly indicate the importance of each decommissioned object. Each decommissioned object also needs to report its own target importance factor based on this importance evaluation information. The IDMS producer can determine the importance of each decommissioned object based on its target importance factor and corresponding weight.

[0104] In one possible implementation, the importance of each de-service object can be determined based on a target importance factor of each de-service object and the weight of that target importance factor, wherein the at least one importance factor includes the target importance factor of each de-service object.

[0105] Optionally, before the IDMS producer determines the service termination and recovery intention based on the service termination and recovery intention request, the method further includes: sending importance request information to the service termination object management device, the importance request information being used to request a target importance factor for each service termination object, the importance request information including at least one importance factor and an identifier for each service termination object; and receiving importance feedback information from the service termination object management device, the importance feedback information being used to indicate the target importance factor for each service termination object.

[0106] In other words, the IDMS producer can determine the importance of each decommissioned object based on the target importance factor of each decommissioned object reported in the importance feedback information and the weight of each target importance factor indicated by the importance information evaluation information.

[0107] In one possible implementation, the service termination object management device can be the service termination object management device 130 in the system 100 described above.

[0108] Optionally, the IDMS producer may send importance request information to each decommissioned object to request the target importance factor of each decommissioned object; or, the IDMS producer may send importance request information to the PM to request the target importance factor of each decommissioned object among the at least one decommissioned object.

[0109] S202. Based on the service outage recovery intention request, the IDMS producer determines the service outage recovery intention, which is used to instruct that each of the at least one outage objects be restored to normal within a target duration in descending order of importance, and the target duration of each outage object is determined based on the maximum outage duration and importance of each outage object.

[0110] In other words, the IDMS producer creates or generates a service termination recovery intent based on the service termination recovery intent request.

[0111] In one possible implementation, the IDMS producer can determine the target duration for each decommissioned object based on the importance of each decommissioned object and the maximum decommissioning duration of each decommissioned object.

[0112] In one possible implementation, the importance of each deprecated object can be inversely proportional to the target duration.

[0113] Optionally, after S202, the method further includes: the IDMS producer troubleshooting the at least one out-of-service object based on the out-of-service recovery intention, in descending order of importance of the at least one out-of-service object.

[0114] Optionally, before the IDMS producer troubleshoots the at least one out-of-service object, the method 200 may further include: the IDMS producer sending a fault cause request to the analysis / processing NF, the fault cause request being used to request analysis of the fault cause of each out-of-service object; and receiving fault cause feedback from the analysis / processing NF, the fault cause feedback being used to indicate the fault cause of each out-of-service object.

[0115] Accordingly, the IDMS producer can troubleshoot the at least one out-of-service object based on the outage recovery intention and the fault cause feedback.

[0116] Optionally, troubleshooting of the at least one out-of-service object can be performed by the IDMS or by the analysis / processing NF, and this application embodiment does not limit this.

[0117] Optionally, after the IDMS producer troubleshoots the at least one out-of-service object, the method 200 may further include: the IDMS producer sending an out-of-service recovery intention report to the IDMS consumer, the out-of-service recovery intention report indicating whether to recover from the failure according to the importance of the at least one out-of-service object, and that each out-of-service object recovers to normal within the target duration of each out-of-service object.

[0118] Optionally, the outage recovery intent report is also used to indicate the cause of failure for each outage object.

[0119] Using the communication method provided in this application, the IDMS consumer directly or indirectly specifies the outage object in the outage recovery intention request, i.e., the expected target entity that needs troubleshooting, and expresses multiple troubleshooting goals, i.e., the desired time (i.e., target duration) for resolving the outage issue of this object. Considering the differences in the services affected by different base stations or cells, the IDMS consumer can also specify its importance factors and corresponding weights in the outage recovery intention request. The IDMS producer calculates the importance of each outage object based on this information and matches an appropriate target duration for each outage object accordingly, thereby performing troubleshooting operations. This improves the recovery efficiency of the outage object.

[0120] In one possible implementation, the communication method provided in this application embodiment may include the following steps:

[0121] (1) The IDMS consumer sends a service termination and recovery intention request to the IDMS producer. The service termination and recovery intention request includes service termination object information, service termination duration information and importance evaluation information. The service termination object information is used to indicate at least one service termination object. The service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object. The importance evaluation information is used to indicate the importance of each service termination object.

[0122] For example, the unservice object intent request may include:

[0123] (a) Object type: Base station;

[0124] (b) Constraints: Coverage of Region 1, Region 2 and Region 3;

[0125] (c) Importance factors and weights: Factor 1: Base station type - weight 30%, Factor 2: Service target - weight 30%, Factor 3: Backup mechanism - weight 40%.

[0126] Based on the above request for service termination, it can be determined that the base station in coverage area 1 is base station A, the base station in coverage area 2 is base station B, and the base station in coverage area 3 is base station C.

[0127] (2) The IDMS producer sends an importance request message to the PM. The importance request message is used to request the target importance factor of each decommissioned object. The importance request message includes at least one importance factor and the identifier of each decommissioned object.

[0128] For example, the importance request information may include:

[0129] (a) Object identifiers: “Base Station A”, “Base Station B”, and “Base Station C”;

[0130] (b) Importance factors: base station type, service targets and backup mechanisms.

[0131] (3) The IDMS producer receives the importance feedback information from the PM, which is used to indicate the target importance factor for each decommissioned object.

[0132] For example, the importance feedback information may include:

[0133] (a) "Base Station A" — Base station type and service target;

[0134] (b) "Base Station B" — Base Station Type;

[0135] (c) "Base Station C" — Base station type, service targets and backup mechanism.

[0136] (4) The IDMS producer determines the importance of each decommissioned object based on the target importance factor of each decommissioned object fed back in the importance feedback information and the weight of each target importance factor indicated by the importance information evaluation information.

[0137] For example, base station A is classified as Level 1; base station B as Level 2; and base station C as Level 3. The importance level is: Level 1 > Level 2 > Level 3.

[0138] (5) The IDMS producer creates a service recovery intent based on the importance of each service-out object and the maximum service outage duration of each service-out object. The service recovery intent is used to instruct each service-out object to be restored to normal within the target duration of each service-out object in descending order of the importance of the at least one service-out object. The target duration of each service-out object is determined based on the maximum service outage duration and importance of each service-out object.

[0139] For example, FIG6 illustrates a schematic diagram of a service termination and recovery intention provided in an embodiment of this application. As shown in FIG6, the service termination and recovery intention may include an object portion and a target portion. The object portion describes the at least one service termination object, and the target portion describes the recovery target of the service termination object.

[0140] As shown in Figure 6, the object portion may include:

[0141] (a) Object type: Base station;

[0142] (b) Constraints: Coverage of Region 1, Region 2 and Region 3;

[0143] (c) Importance factors and weights: Factor 1: Base station type - weight 30%, Factor 2: Service target - weight 30%, Factor 3: Backup mechanism - weight 40%.

[0144] As shown in Figure 6, the target portion may include:

[0145] (a) Objective 1: Objective duration <10min—Importance level 1;

[0146] (b) Objective 2: Objective duration <60min—Importance level 2;

[0147] (c) Objective 3: Objective duration <100min — Importance level 3.

[0148] For example, FIG7 shows another schematic diagram of the service termination and recovery intention provided in the embodiments of this application. As shown in FIG7, the service termination and recovery intention may include an object portion and a target portion. The object portion is used to describe the at least one service termination object, and the target portion is used to describe the recovery target of the service termination object.

[0149] As shown in Figure 7, the object portion may include:

[0150] (a) Object identifiers: Base station A, Base station B, and Base station C;

[0151] (b) Importance factors and weights: Factor 1: Base station type - weight 30%, Factor 2: Service target - weight 30%, Factor 3: Backup mechanism - weight 40%.

[0152] As shown in Figure 7, the target portion may include:

[0153] (a) Objective 1: Objective duration <10min—Importance level 1;

[0154] (b) Objective 2: Objective duration <60min—Importance level 2;

[0155] (c) Objective 3: Objective duration <100min — Importance level 3.

[0156] (6) The IDMS producer sends a fault cause request to the analysis / processing NF, which is used to request analysis of the fault cause of each out-of-service object.

[0157] (7) The IDMS producer receives fault cause feedback from the analysis / processing NF, which is used to indicate the fault cause of each outage object.

[0158] (8) The IDMS producer troubleshoots at least one out-of-service object based on the outage recovery intention and the fault cause feedback.

[0159] (9) The IDMS producer sends a service termination and recovery intention report to the IDMS consumer. The service termination and recovery intention report is used to indicate whether each terminated object will be restored to normal within the target duration of each terminated object.

[0160] For example, the request to terminate an object may also include:

[0161] (a) Identification of at least one out-of-service object: base station A, base station B, and base station C;

[0162] (b) Importance of at least one out-of-service object: Base station A—Level 1; Base station B—Level 2; Base station C—Level 3.

[0163] In other words, the importance evaluation information directly indicates the degree of importance of each object that has left the service.

[0164] For example, FIG8 illustrates another schematic diagram of a service termination and recovery intention provided in an embodiment of this application. As shown in FIG8, the service termination and recovery intention may include an object portion and a target portion. The object portion is used to describe the at least one service termination object, and the target portion is used to describe the recovery target of the service termination object.

[0165] As shown in Figure 8, the object portion may include:

[0166] (a) Object identifiers: Base station A, Base station B, and Base station C;

[0167] (b) Importance level: Base station A-level, base station B-level, and base station C-level.

[0168] As shown in Figure 8, the target portion may include:

[0169] (a) Objective 1: Objective duration <10min—Importance level 1;

[0170] (b) Objective 2: Objective duration <60min—Importance level 2;

[0171] (c) Objective 3: Objective duration <100min — Importance level 3.

[0172] Figure 9 shows a schematic flowchart of a communication method 300 provided in an embodiment of this application. This method 300 can be used in the system 100 described above. As shown in Figure 9, the method 300 may include the following steps.

[0173] S301. The IDMS consumer sends a service termination and recovery intention request to the IDMS producer. The service termination and recovery intention request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0174] In one possible implementation, the IDMS consumer can be IDMS consumer 110 in the system 100 described above, and the IDMS producer can be IDMS producer 120 in the system 100 described above.

[0175] It should be noted that the above outage rate information is used to indicate the maximum acceptable outage rate after troubleshooting, i.e., the target ratio.

[0176] Optionally, the above service outage rate information can be replaced with service outage number information, which is used to indicate the maximum acceptable number of service outages after troubleshooting, i.e., the target number.

[0177] It should also be noted that the above-mentioned outage duration information is used to indicate the maximum acceptable resolution time, i.e., the target time, when troubleshooting reaches the maximum outage rate or maximum number of outages.

[0178] Optionally, the embodiments of this application do not limit the content included in the intention to restore service after service termination.

[0179] In one possible implementation, the request to restore service after a server outage may include information about the outage object, importance evaluation information, and outage rate information (or number of outages).

[0180] In another possible implementation, the service termination and recovery intention request may include information about the terminated object, importance evaluation information, and service termination duration information.

[0181] In another possible implementation, the request to restore service may include information about the service being terminated, importance evaluation information, termination rate information (or number of terminations), and termination duration information.

[0182] In other words, the intention to restore service termination can constrain only the maximum termination rate (or the maximum number of terminations); or only the maximum resolution time; or both the maximum termination rate (or the maximum number of terminations) and the maximum resolution time.

[0183] S302. Based on the service termination and recovery intention request, the IDMS producer determines the service termination and recovery intention, which is used to instruct that within the target duration, in descending order of importance of the at least one terminated object, the at least one terminated object be restored to normal, until the ratio of the current remaining number of terminated objects to the total number of objects is less than or equal to the target ratio.

[0184] Optionally, after S302, the method 300 may further include: based on the service outage recovery intention, the IDMS producer troubleshoots the at least one outage object in descending order of importance within the target duration, until the ratio of the current remaining number of outage objects to the total number of objects is less than or equal to the target ratio.

[0185] Optionally, after the IDMS producer troubleshoots the at least one out-of-service object, the method 300 may further include: the IDMS producer sending an out-of-service recovery intention report to the IDMS consumer, the out-of-service recovery intention report indicating whether to recover the fault according to the importance of the at least one out-of-service object, and the ratio of the current remaining number of out-of-service objects to the total number of objects within the target duration is less than or equal to the target ratio.

[0186] It should be noted that for the parts not described in method 300, please refer to the corresponding parts in method 200; they will not be repeated here.

[0187] Using the communication method provided in this application, IDMS consumers can tolerate a certain level of service outages. Therefore, they will specify the acceptable level of outages in the outage recovery intention request in the form of "maximum outage rate" and "maximum number of outages." Furthermore, a "maximum outage duration" will be provided as the maximum allowed resolution time in the overall outage scenario when the outage rate or number of outages reaches a specified value. IDMS producers can restore faults according to their importance to achieve the required outage rate / number within a specified time, thus improving the recovery efficiency of outages.

[0188] In one possible implementation, the communication method provided in this application embodiment may include the following steps:

[0189] (1) The IDMS consumer sends a service termination and recovery intention request to the IDMS producer. The service termination and recovery intention request includes service termination object information, importance evaluation information, service termination rate information and service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0190] For example, the unservice object intent request may include:

[0191] (a) Object type: Base station;

[0192] (b) Constraints: Coverage of Region 1, Region 2 and Region 3;

[0193] (c) Importance factors and weights: Factor 1: Base station type - weight 30%, Factor 2: Service target - weight 30%, Factor 3: Backup mechanism - weight 40%;

[0194] (d) Maximum server termination rate: 10% (or maximum number of server terminations: 10);

[0195] (e) Maximum resolution time: 10 min.

[0196] Based on the above request for service termination, it can be determined that the base station in coverage area 1 is base station A, the base station in coverage area 2 is base station B, and the base station in coverage area 3 is base station C.

[0197] (2) The IDMS producer sends an importance request message to the PM. The importance request message is used to request the target importance factor of each decommissioned object. The importance request message includes at least one importance factor and the identifier of each decommissioned object.

[0198] For example, the importance request information may include:

[0199] (a) Object identifiers: “Base Station A”, “Base Station B”, and “Base Station C”;

[0200] (b) Importance factors: base station type, service targets and backup mechanisms.

[0201] (3) The IDMS producer receives the importance feedback information from the PM, which is used to indicate the target importance factor for each decommissioned object.

[0202] For example, the importance feedback information may include:

[0203] (a) "Base Station A" — Base station type and service target;

[0204] (b) "Base Station B" — Base Station Type;

[0205] (c) "Base Station C" — Base station type, service targets and backup mechanism.

[0206] (4) The IDMS producer determines the importance of each decommissioned object based on the target importance factor of each decommissioned object fed back in the importance feedback information and the weight of each target importance factor indicated by the importance information evaluation information.

[0207] For example, base station A is classified as Level 1; base station B as Level 2; and base station C as Level 3. The importance level is: Level 1 > Level 2 > Level 3.

[0208] (5) The IDMS producer creates a service recovery intention based on the importance of each service-out object, the target ratio, and the target duration. The service recovery intention is used to instruct that at least one service-out object be restored to normal in descending order of importance within the target duration, until the ratio of the current remaining number of service-out objects to the total number of objects is less than or equal to the target ratio.

[0209] For example, FIG10 shows another schematic diagram of the service termination and recovery intention provided in the embodiments of this application. As shown in FIG10, the service termination and recovery intention may include an object part and a target part. The object part is used to describe the at least one service termination object, and the target part is used to describe the recovery target of the service termination object.

[0210] As shown in Figure 10, the object portion may include:

[0211] (a) Object type: Base station;

[0212] (b) Constraints: Coverage of Region 1, Region 2 and Region 3;

[0213] (c) Importance factors and weights: Factor 1: Base station type - weight 30%, Factor 2: Service target - weight 30%, Factor 3: Backup mechanism - weight 40%.

[0214] As shown in Figure 10, the target portion may include:

[0215] (a) Target 1: Target ratio (i.e., maximum server quit rate) < 10%, or target number (i.e. maximum number of server quits) < 100.

[0216] (6) The IDMS producer sends a fault cause request to the analysis / processing NF, which is used to request analysis of the fault cause of each out-of-service object.

[0217] (7) The IDMS producer receives fault cause feedback from the analysis / processing NF, which is used to indicate the fault cause of each outage object.

[0218] (8) The IDMS producer troubleshoots at least one out-of-service object based on the outage recovery intention and the fault cause feedback.

[0219] (9) The IDMS producer sends a service termination and recovery intention report to the IDMS consumer. The service termination and recovery intention report is used to indicate whether each terminated object will be restored to normal within the target duration of each terminated object.

[0220] For example, the request to terminate an object may also include:

[0221] (a) Identification of at least one out-of-service object: base station A, base station B, and base station C;

[0222] (b) Importance level of at least one out-of-service object: Base station A—Level 1; Base station B—Level 2; Base station C—Level 3;

[0223] (c) Maximum server termination rate: 10% (or maximum number of server terminations: 10);

[0224] (d) Maximum resolution time: 10 min.

[0225] In other words, the importance evaluation information directly indicates the degree of importance of each object that has left the service.

[0226] For example, FIG11 shows another schematic diagram of the service termination and recovery intention provided in the embodiments of this application. As shown in FIG11, the service termination and recovery intention may include an object part and a target part. The object part is used to describe the at least one service termination object, and the target part is used to describe the recovery target of the service termination object.

[0227] As shown in Figure 11, the object portion may include:

[0228] (a) Object identifiers: Base station A, Base station B, and Base station C;

[0229] (b) Importance level: Base station A—Level 1, Base station B—Level 2; Base station C—Level 3;

[0230] As shown in Figure 11, the target portion may include:

[0231] (a) Target 1: Target ratio (i.e., maximum server quit rate) < 10%, or target number (i.e., maximum number of server quits) < 100;

[0232] (b) Objective 2: Target duration (maximum resolution time) < 10 min.

[0233] Therefore, steps (2) to (5) above can be replaced by: the IDMS producer creating a service termination and recovery intent based on the service termination and recovery intent request.

[0234] The communication method provided by the embodiments of this application has been described above with reference to Figures 5 to 11. The communication device provided by the embodiments of this application will be further described below.

[0235] Figure 12 provides a schematic block diagram of a communication device 400 provided in an embodiment of this application. As shown in Figure 12, the device 400 may include a receiving unit 401 and a determining unit 402.

[0236] Optionally, the device 400 may also include at least one of a fault clearing unit 403 or a sending unit 404.

[0237] In one possible implementation, the receiving unit 401 is configured to receive a service termination and recovery intention request from an IDMS consumer. The service termination and recovery intention request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information indicates at least one service termination object, the service termination duration information indicates the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information indicates the importance level of each service termination object. The determining unit 402 is configured to determine a service termination and recovery intention based on the service termination and recovery intention request. The service termination and recovery intention indicates that each service termination object should be restored to normal operation within a target duration, in descending order of the importance level of the at least one service termination object. The target duration for each service termination object is determined based on the maximum service termination duration and the importance level of each service termination object.

[0238] In one possible implementation, the target duration of each outgoing object is inversely proportional to the importance of that outgoing object.

[0239] In one possible implementation, the troubleshooting unit 403 is used to troubleshoot the at least one out-of-service object in descending order of importance based on the out-of-service recovery intention.

[0240] In one possible implementation, the decommissioned object information includes the identifier of the at least one decommissioned object; and / or, the importance evaluation information includes the importance level of each decommissioned object.

[0241] In one possible implementation, the out-of-service object information includes the identifier of the at least one out-of-service object, or includes at least one of the object type or constraint of the at least one out-of-service object, wherein the object type includes a base station or a cell, and the constraint includes the coverage area of ​​the out-of-service object; and / or, the importance evaluation information includes at least one importance factor for evaluating the importance of the out-of-service object and the weight of each of the at least one importance factor.

[0242] In one possible implementation, the importance of each de-service object is determined based on a target importance factor of each de-service object and the weight of that target importance factor, wherein the at least one importance factor includes the target importance factor of each de-service object.

[0243] In one possible implementation, the sending unit 404 is configured to send importance request information to the service termination object management device before the determining unit 402 determines the service termination recovery intention based on the service termination recovery intention request. The importance request information is used to request a target importance factor for each service termination object, and the importance request information includes at least one importance factor and an identifier for each service termination object. The receiving unit 401 is further configured to receive importance feedback information from the service termination object management device, and the importance feedback information is used to indicate the target importance factor for each service termination object.

[0244] In one possible implementation, the sending unit 404 is further configured to send a service outage recovery intention report to the IDMS consumer, the service outage recovery intention report being used to indicate whether to recover the fault according to the importance of the at least one outage object, and each outage object recovers to normal within the target duration of each outage object.

[0245] In another possible implementation, the receiving unit 401 is configured to receive a service termination and recovery intention request from an IDMS consumer. The service termination and recovery intention request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information indicates at least one service termination object; the importance evaluation information indicates the importance level of each of the at least one service termination object; the service termination rate information indicates a target ratio of the currently acceptable number of service termination objects to the total number of objects; and the service termination duration information indicates an acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio. The determining unit 402 is configured to determine a service termination and recovery intention based on the service termination and recovery intention request. The service termination and recovery intention indicates that within the target duration, the at least one service termination object should be restored to normal operation in descending order of importance, until the ratio of the currently remaining number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0246] In another possible implementation, the troubleshooting unit 403 is further configured to, based on the service outage recovery intention, troubleshoot the at least one outage object in descending order of importance within the target duration, until the ratio of the current remaining number of outage objects to the total number of objects is less than or equal to the target ratio.

[0247] In another possible implementation, the sending unit 404 is used to send a service outage recovery intention report to the IDMS consumer. The service outage recovery intention report is used to indicate whether to recover the fault according to the importance of the at least one outage object, and the ratio of the number of currently remaining outage objects to the total number of objects within the target duration is less than or equal to the target ratio.

[0248] Optionally, the device 400 can be used in the system 100 described above. Further, the device 400 can be used in the IDMS producer 120 in the system 100, such as a virtual device formed by software executed by the processor or controller on the IDMS producer 120.

[0249] It should be noted that the information interaction and execution process between the above-mentioned devices are based on the same concept as the embodiments of method 200 or method 300 of this application. Their specific functions and technical effects can be found in the method embodiments section, and will not be repeated here. In an optional example, the device 400 can specifically be the IDMS producer in the embodiments of method 200 or method 300 above. The device 400 can be used to execute the various processes and / or steps corresponding to the IDMS producer in the embodiments of method 200 or method 300 above. To avoid repetition, these will not be described again here.

[0250] One or more of the modules in the embodiments shown in Figure 12 can be implemented by software, hardware, firmware, or a combination thereof. The software or firmware includes, but is not limited to, computer program instructions or code, and can be executed by a hardware processor. The hardware includes, but is not limited to, various integrated circuits, such as central processing units (CPUs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), or application-specific integrated circuits (ASICs).

[0251] Figure 13 provides a schematic block diagram of a communication device 500 provided in an embodiment of this application. As shown in Figure 13, the device 500 may include a processor 501 and a communication interface 502, wherein the processor 501 and the communication interface 502 are coupled.

[0252] In an alternative example, those skilled in the art will understand that the device 500 can be the IDMS producer in the embodiments of method 200 or method 300 described above, and the device 500 can be the physical hardware structure of the IDMS producer. The device 500 can be used to execute the various processes and / or steps corresponding to the IDMS producer in the embodiments of method 200 or method 300 described above, and will not be described again here to avoid repetition.

[0253] The processor 501 in this embodiment may include one or more processing units. Optionally, the processing unit may include, but is not limited to, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor may be a microprocessor, a microcontroller, or any conventional processor.

[0254] For example, the processor 501 is configured to receive a service termination and recovery intent request from an Intent-Driven Management Service (IDMS) consumer via the communication interface 502. The service termination and recovery intent request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information indicates at least one service termination object, the service termination duration information indicates the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information indicates the importance level of each service termination object. Based on the service termination and recovery intent request, a service termination and recovery intent is determined. The service termination and recovery intent instructs each service termination object to recover to normal within a target duration, in descending order of the importance level of the at least one service termination object. The target duration for each service termination object is determined based on the maximum service termination duration and importance level of each service termination object.

[0255] For example, the processor 501 is configured to receive a service termination and recovery intent request from an Intent-Driven Management Service (IDMS) consumer via the communication interface 502. The service termination and recovery intent request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the currently acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio. Based on the service termination and recovery intent request, a service termination and recovery intent is determined. The service termination and recovery intent is used to instruct that within the target duration, the at least one service termination object be restored to normal in descending order of importance, until the ratio of the currently remaining number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0256] Optionally, the device 500 may also include a memory 503.

[0257] Memory 503 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0258] Specifically, memory 503 is used to store program code and instructions of device 500. Optionally, memory 503 is also used to store data obtained by processor 501 during the execution of the above-described method 200 or method 300, such as service termination / recovery intention requests, or service termination / recovery intentions.

[0259] Alternatively, the memory 503 may be a separate device or integrated into the processor 501.

[0260] It should be noted that Figure 13 only shows a simplified design of the device 500. In practical applications, the device 500 may also include other necessary components, including but not limited to any number of communication interfaces, processors, selectors, memories, etc., and all devices 500 that can implement this application are within the protection scope of this application.

[0261] In one possible design, the device 500 can be a chip. Optionally, the chip may further include one or more memories for storing computer-executable instructions, which, when the chip device is running, can be executed by a processor to cause the chip to perform the steps performed by the IDMS producer in the embodiments of method 200 or method 300 described above.

[0262] Optionally, the chip device can be a field-programmable gate array, a dedicated integrated circuit, a system-on-a-chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, or a programmable controller or other integrated chip to implement the relevant functions.

[0263] Figure 14 provides a schematic block diagram of a communication device 600 provided in an embodiment of this application. As shown in Figure 14, the device 600 may include a transmitting unit 601.

[0264] Optionally, the device 600 may also include a receiving unit 602.

[0265] In one possible implementation, the sending unit 601 is used to send a service termination and recovery intention request to the IDMS producer. The service termination and recovery intention request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object, the service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information is used to indicate the importance of each service termination object.

[0266] In one possible implementation, the receiving unit 602 is configured to receive a service outage recovery intention report from the IDMS producer, the service outage recovery intention report being used to indicate whether to recover the fault according to the importance of the at least one outage object, and each outage object recovers to normal within the target duration of each outage object.

[0267] In another possible implementation, the sending unit 601 is used to send a service termination and recovery intention request to the IDMS producer. The service termination and recovery intention request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0268] In one possible implementation, the receiving unit 602 is configured to receive a service termination recovery intention report from the IDMS producer, the service termination recovery intention report indicating whether to recover the fault according to the importance of the at least one service termination object, and the ratio of the current remaining number of service termination objects to the total number of objects within the target duration is less than or equal to the target ratio.

[0269] Optionally, the device 600 can be used in the system 100 described above. Further, the device 600 can be used in the IDMS consumer 110 in the system 100, such as a virtual device formed by software executed by the processor or controller on the IDMS consumer 110.

[0270] It should be noted that the information interaction and execution process between the above-mentioned devices are based on the same concept as the embodiments of method 200 or method 300 of this application. Their specific functions and technical effects can be found in the method embodiment section, and will not be repeated here. In an optional example, the device 600 can specifically be the IDMS consumer in the embodiments of method 200 or method 300 above. The device 600 can be used to execute the various processes and / or steps corresponding to the IDMS consumer 110 in the embodiments of method 200 or method 300 above. To avoid repetition, these will not be described again here.

[0271] One or more of the modules in the embodiments shown in Figure 14 can be implemented by software, hardware, firmware, or a combination thereof. The software or firmware includes, but is not limited to, computer program instructions or code, and can be executed by a hardware processor. The hardware includes, but is not limited to, various integrated circuits such as CPUs, DSPs, FPGAs, or ASICs.

[0272] Figure 15 provides a schematic block diagram of a communication device 700 provided in an embodiment of this application. As shown in Figure 15, the device 700 may include a processor 701 and a communication interface 702, wherein the processor 701 and the communication interface 702 are coupled.

[0273] In an alternative example, those skilled in the art will understand that the device 700 may specifically be the IDMS consumer in the embodiments of method 200 or method 300 described above, and the device 700 may be the physical hardware structure of the IDMS consumer. The device 700 may be used to execute the various processes and / or steps corresponding to the IDMS consumer in the embodiments of method 200 or method 300 described above, and will not be repeated here to avoid repetition.

[0274] The processor 701 in this embodiment may include one or more processing units. Optionally, the processing unit may include, but is not limited to, a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor may be a microprocessor, a microcontroller, or any conventional processor.

[0275] For example, the processor 701 is used to send a service termination and recovery intent request to the Intent Driven Management Service (IDMS) producer through the communication interface 702. The service termination and recovery intent request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object, the service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information is used to indicate the importance of each service termination object.

[0276] For example, the processor 701 is used to send a service termination and recovery intention request to the Intent-Driven Management Service (IDMS) producer through the communication interface 702. The service termination and recovery intention request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

[0277] Memory 703 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be ROM, PROM, EPROM, EEPROM, or flash memory. The volatile memory may be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as SRAM, DRAM, SDRAM, DDR SDRAM, ESDRAM, SLDRAM, and DR RAM.

[0278] Specifically, memory 703 is used to store program code and instructions of device 700. Optionally, memory 703 is also used to store data obtained by processor 701 during the execution of the above-described embodiments of method 200 or method 300, such as service termination / recovery intention requests.

[0279] Alternatively, the memory 703 may be a separate device or integrated into the processor 701.

[0280] It should be noted that Figure 15 only shows a simplified design of the device 700. In practical applications, the device 700 may also include other necessary components, including but not limited to any number of communication interfaces, processors, selectors, memories, etc., and all devices 700 that can implement this application are within the protection scope of this application.

[0281] In one possible design, the device 700 can be a chip. Optionally, the chip may further include one or more memories for storing computer-executable instructions. When the chip device is running, the processor can execute the computer-executable instructions stored in the memories to cause the chip to perform the steps performed by the communication device described in method 200 or method 300 above.

[0282] Optionally, the chip device can be a field-programmable gate array, a dedicated integrated circuit, a system-on-a-chip, a central processing unit, a network processor, a digital signal processing circuit, a microcontroller, or a programmable controller or other integrated chip to implement the relevant functions.

[0283] This application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, implement the method described in the above method embodiments.

[0284] This application also provides a computer program product that, when run on a processor, implements the method described in the above method embodiments.

[0285] The communication device, computer-readable storage medium, computer program product, or chip provided in the embodiments of this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects described in the corresponding methods provided above, and will not be repeated here.

[0286] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0287] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0288] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0289] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0290] The unit described as a separate component may or may not be physically separate. The component shown as a unit may or may not be a physical unit; that is, it may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0291] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0292] If this function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0293] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: Receive a service termination and recovery intent request from an intent-driven management service (IDMS) consumer. The service termination and recovery intent request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object. The service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object. The importance evaluation information is used to indicate the importance of each service termination object. Based on the service termination and recovery intention request, a service termination and recovery intention is determined. The service termination and recovery intention is used to instruct that each of the at least one service termination object be restored to normal within a target duration in descending order of importance. The target duration of each service termination object is determined based on the maximum service termination duration and importance of each service termination object.

2. The method according to claim 1, characterized in that, The target duration for each object that is terminated is inversely proportional to the importance of that object.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Based on the stated intention to restore service, troubleshooting is performed on the at least one service-deactivated object in descending order of importance.

4. The method according to any one of claims 1-3, characterized in that, The information about the deactivated object includes the identifier of at least one deactivated object; and / or, the importance evaluation information includes the importance level of each deactivated object.

5. The method according to any one of claims 1-3, characterized in that, The out-of-service object information includes the identifier of the at least one out-of-service object, or includes at least one of the object type or constraint conditions of the at least one out-of-service object, wherein the object type includes a base station or a cell, and the constraint condition includes the coverage area of ​​the out-of-service object; and / or, the importance evaluation information includes at least one importance factor for evaluating the importance of the out-of-service object and the weight of each of the at least one importance factor.

6. The method according to claim 5, characterized in that, The importance of each decommissioned object is determined based on the target importance factor of each decommissioned object and the weight of the target importance factor, wherein the at least one importance factor includes the target importance factor of each decommissioned object.

7. The method according to claim 6, characterized in that, Before determining the service termination / recovery intention based on the service termination / recovery intention request, the method further includes: An importance request message is sent to the decommissioned object management device. The importance request message is used to request a target importance factor for each decommissioned object. The importance request message includes at least one importance factor and an identifier for each decommissioned object. The importance feedback information is received from the decommissioned object management device, and the importance feedback information is used to indicate the target importance factor of each decommissioned object.

8. A communication method, characterized in that, include: Send a service termination and recovery intent request to the Intent-Driven Management Service (IDMS) producer. The service termination and recovery intent request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object. The service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object. The importance evaluation information is used to indicate the importance of each service termination object.

9. A communication method, characterized in that, include: Receive a service termination and recovery intent request from an Intent-Driven Management Service (IDMS) consumer. The service termination and recovery intent request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio. Based on the service termination and recovery intention request, a service termination and recovery intention is determined. The service termination and recovery intention is used to instruct that, within the target duration, at least one service termination object be restored to normal in descending order of importance, until the ratio of the current remaining number of service termination objects to the total number of objects is less than or equal to the target ratio.

10. The method according to claim 9, characterized in that, The method further includes: Based on the stated intention to restore service, within the target duration, troubleshooting is performed on the at least one deactivated object in descending order of importance until the ratio of the current remaining deactivated object number to the total number of objects is less than or equal to the target ratio.

11. A communication method, characterized in that, include: Send a service termination and recovery intent request to the Intent-Driven Management Service (IDMS) producer. The service termination and recovery intent request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

12. A communication device, characterized in that, include: A processor and a communication interface, wherein the processor and the communication interface are coupled, and the processor is used for: The communication interface receives a service termination and recovery intent request from an intent-driven management service (IDMS) consumer. The service termination and recovery intent request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information indicates at least one service termination object, the service termination duration information indicates the maximum allowed service termination duration for each of the at least one service termination object, and the importance evaluation information indicates the importance of each service termination object. Based on the service termination and recovery intention request, a service termination and recovery intention is determined. The service termination and recovery intention is used to instruct that each of the at least one service termination object be restored to normal within a target duration in descending order of importance. The target duration of each service termination object is determined based on the maximum service termination duration and importance of each service termination object.

13. The apparatus according to claim 12, characterized in that, The target duration for each object that is terminated is inversely proportional to the importance of that object.

14. The apparatus according to claim 12 or 13, characterized in that, The processor is also used for: Based on the stated intention to restore service, troubleshooting is performed on the at least one service-deactivated object in descending order of importance.

15. The apparatus according to any one of claims 12-14, characterized in that, The information about the deactivated object includes the identifier of at least one deactivated object; and / or, the importance evaluation information includes the importance level of each deactivated object.

16. The apparatus according to any one of claims 12-14, characterized in that, The out-of-service object information includes the identifier of the at least one out-of-service object, or includes at least one of the object type or constraint conditions of the at least one out-of-service object, wherein the object type includes a base station or a cell, and the constraint condition includes the coverage area of ​​the out-of-service object; and / or, the importance evaluation information includes at least one importance factor for evaluating the importance of the out-of-service object and the weight of each of the at least one importance factor.

17. The apparatus according to claim 16, characterized in that, The importance of each decommissioned object is determined based on the target importance factor of each decommissioned object and the weight of the target importance factor, wherein the at least one importance factor includes the target importance factor of each decommissioned object.

18. The apparatus according to claim 17, characterized in that, The processor is also used for: Before determining the service termination and recovery intention based on the service termination and recovery intention request, an importance request information is sent to the service termination object management device. The importance request information is used to request the target importance factor of each service termination object. The importance request information includes at least one importance factor and the identifier of each service termination object. The importance feedback information is received from the decommissioned object management device, and the importance feedback information is used to indicate the target importance factor of each decommissioned object.

19. A communication device, characterized in that, include: Send a service termination and recovery intent request to the Intent-Driven Management Service (IDMS) producer. The service termination and recovery intent request includes service termination object information, service termination duration information, and importance evaluation information. The service termination object information is used to indicate at least one service termination object. The service termination duration information is used to indicate the maximum allowed service termination duration for each of the at least one service termination object. The importance evaluation information is used to indicate the importance of each service termination object.

20. A communication device, characterized in that, include: A processor and a communication interface, wherein the processor and the communication interface are coupled, and the processor is used for: The communication interface receives a service termination and recovery intent request from an Intent-Driven Management Service (IDMS) consumer. The service termination and recovery intent request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio. Based on the service termination and recovery intention request, a service termination and recovery intention is determined. The service termination and recovery intention is used to instruct that, within the target duration, at least one service termination object be restored to normal in descending order of importance, until the ratio of the current remaining number of service termination objects to the total number of objects is less than or equal to the target ratio.

21. The apparatus according to claim 20, characterized in that, The processor is also used for: Based on the stated intention to restore service, within the target duration, troubleshooting is performed on the at least one deactivated object in descending order of importance until the ratio of the current remaining deactivated object number to the total number of objects is less than or equal to the target ratio.

22. A communication device, characterized in that, include: A processor and a communication interface, wherein the processor and the communication interface are coupled, and the processor is used for: The service termination and recovery intent request is sent to the Intent-Driven Management Service (IDMS) producer through the communication interface. The service termination and recovery intent request includes at least one of the following: service termination object information, importance evaluation information, service termination rate information, or service termination duration information. The service termination object information is used to indicate at least one service termination object. The importance evaluation information is used to indicate the importance of each of the at least one service termination object. The service termination rate information is used to indicate the target ratio of the current acceptable number of service termination objects to the total number of objects. The service termination duration information is used to indicate the acceptable target duration when the ratio of the current number of service termination objects to the total number of objects is less than or equal to the target ratio.

23. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed by a processor, implements the method as described in any one of claims 1-11.

24. A computer program product, characterized in that, When the computer program product is run on a processor, it implements the method as described in any one of claims 1-11.

Images