Strategy management method and device and processor readable storage medium

Abstract

The invention provides a strategy management method and device and a processor readable storage medium, and relates to the technical field of communication. The method comprises the following steps: a first entity receives first indication information sent by a second entity, and / or receives first indication information sent by an application program in a non-real-time radio access network controller (Non-RT RIC); the first entity executes A1 policy management according to the first indication information; wherein the first indication information is used for indicating the execution priority of the A1 strategy. According to the method and the device, the problem that no corresponding solution is provided for strategy and / or configuration conflicts caused by strategy inconsistency between rApps at present can be solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a policy management method and device and a processor readable storage medium. BACKGROUND

[0002] In an open radio access network (O-RAN), an application (rApp) running in a non-real-time radio access network controller (Non-RT RIC) can send various policies and / or configurations to a Near-RT RIC based on its own tasks, optimization targets, etc. Different third-party vendors deploy rApps in the Non-RT RIC, which can cause conflicts between the policies and / or configurations sent by different rApps to the Near-RT RIC. However, there is currently no corresponding solution to the policy and / or configuration conflicts caused by inconsistent policies between rApps. SUMMARY

[0003] The present application provides a policy management method and device and a processor readable storage medium, which solves the problem that there is currently no corresponding solution to the policy and / or configuration conflicts caused by inconsistent policies between rApps.

[0004] Embodiments of the present application provide a policy management method, comprising:

[0005] A first entity receives first indication information sent by a second entity, and / or receives first indication information sent by an application in a Non-RT RIC;

[0006] The first entity performs A1 policy management according to the first indication information.

[0007] The first indication information is used to indicate the execution priority of the A1 policy.

[0008] Optionally, the first entity comprises one of the following:

[0009] An A1 policy function entity in the Non-RT RIC;

[0010] A Near-Real Time RAN Intelligent Controller (Near-RT RIC);

[0011] And / or,

[0012] The second entity comprises one of the following:

[0013] application management function entity in the non-RT RIC;

[0014] A1 policy function entity in the non-RT RIC;

[0015] function entity in the SMO architecture other than the non-RT RIC.

[0016] Optionally, the first indication information comprises at least one of:

[0017] A1 policy priority;

[0018] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0019] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0020] Optionally, before the first entity receives the first indication information sent by the second entity, the method further comprises at least one of:

[0021] the first entity receives first request information sent by an application in the non-RT RIC, and sends first query information to the second entity according to the first request information; wherein the first request information is used to request creation and / or update of an A1 policy, and the first query information is used to request provision of execution priority of the A1 policy;

[0022] the first entity sends first subscription information to the second entity; wherein the first subscription information is used to subscribe to execution priority of an A1 policy.

[0023] Optionally, the first entity receives the first indication information sent by the second entity and / or receives first indication information sent by an application in the non-RT RIC, comprising at least one of:

[0024] the first entity receives second request information sent by the second entity; wherein the second request information is used to request creation and / or update of an A1 policy, and the second request information comprises the first indication information;

[0025] the first entity receives third request information sent by an application in the non-RT RIC; wherein the third request information is used to request creation and / or update of an A1 policy, and the third request information comprises the first indication information.

[0026] Optionally, the first entity performs A1 policy management according to the first indication information, comprising:

[0027] The first entity performs conflict detection on the at least two A1 policies, and determines a conflict detection result;

[0028] If the conflict detection result is that there is a conflict between the at least two A1 policies, the first entity performs A1 policy management according to the first indication information;

[0029] The first entity determines that there is a conflict between the at least two A1 policies by at least one of the following manners:

[0030] There is overlap between configuration parameters of the at least two A1 policies;

[0031] There is a conflict between policy actions of the at least two A1 policies.

[0032] Optionally, the performing of the A1 policy management comprises at least one of the following:

[0033] For the A1 policy with the conflict, the A1 policy creation and / or update is rejected;

[0034] For the A1 policy with the conflict, the A1 policy creation and / or update is suspended;

[0035] For the A1 policy with the conflict, the A1 policy is deleted;

[0036] For the A1 policy whose creation and / or update has been rejected or suspended, the creation and / or update process of the A1 policy is retried;

[0037] For the at least two A1 policies with the conflict, the at least two A1 policies are merged.

[0038] Optionally, in the case of a second A1 policy and a first A1 policy requested to be created and / or updated by a first application, the first entity performs A1 policy management according to the first indication information, comprising:

[0039] If it is determined according to the first indication information that the execution priority of the first A1 policy is lower than or equal to the execution priority of the second A1 policy, the first entity sends rejection information to the first application; wherein the rejection information is used to indicate that the creation and / or update of the first A1 policy is rejected;

[0040] and / or,

[0041] If it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, the first entity performs the creation and / or update process of the first A1 policy.

[0042] Optionally, the first entity determines the priority relationship between the execution priority of the first A1 policy and the execution priority of the second A1 policy by at least one of the following manners:

[0043] If the A1 policy priority corresponding to the first A1 policy is higher than the A1 policy priority corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy.

[0044] If the A1 policy priority corresponding to the first A1 policy is lower than the A1 policy priority corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy.

[0045] If the A1 policy priority corresponding to the first A1 policy is equal to the A1 policy priority corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy.

[0046] If the first identification information corresponding to the first A1 policy is a first value, and / or the first identification information corresponding to the second A1 policy is a second value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy.

[0047] If the first identification information corresponding to the first A1 policy is a second value, and / or the first identification information corresponding to the second A1 policy is a first value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy.

[0048] If the second identification information corresponding to the first A1 policy is a first value, and / or the second identification information corresponding to the second A1 policy is a second value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy.

[0049] The first identification information being the first value indicates that other A1 policies are allowed to be preempted, and the first identification information being the second value indicates that other A1 policies are not allowed to be preempted. The second identification information being the first value indicates that the first A1 policy is not allowed to be preempted by other A1 policies, and the second identification information being the second value indicates that the first A1 policy is allowed to be preempted by other A1 policies.

[0050] Optionally, after the first entity sends the rejection information to the first application, the method further comprises:

[0051] The first entity receives first deletion request information sent by a second application; wherein the first deletion request information is used to request deletion of the second A1 policy;

[0052] The first entity sends the first deletion request information to a Near-RT RIC;

[0053] The first entity receives feedback information sent by the Near-RT RIC;

[0054] In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity sends retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0055] Optionally, after the first entity sends the rejection information to the first application, the method further comprises:

[0056] The first entity receives first deletion request information sent by a second application; wherein the first deletion request information is used to request deletion of the second A1 policy;

[0057] The first entity deletes the second A1 policy, and sends retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0058] Optionally, the first entity performs the creation and / or update process of the first A1 policy, comprising:

[0059] The first entity sends the rejection information to the first application, and sends second deletion request information to a Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy;

[0060] The first entity receives feedback information sent by the Near-RT RIC;

[0061] In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity sends retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0062] Optionally, before the first entity sends the retry information to the first application, the method further comprises:

[0063] The first entity receives third identification information sent by the first application; wherein the third identification information is used to indicate whether the first application allows retry of A1 policy execution;

[0064] The first entity sends retry information to the first application, including:

[0065] In a case where the third identification information indicates that the first application allows the retry A1 policy execution, the first entity sends the retry information to the first application.

[0066] Optionally, the first entity performs a creation and / or update process of the first A1 policy, including:

[0067] The first entity sends second deletion request information to the Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy;

[0068] The first entity receives feedback information sent by the Near-RT RIC;

[0069] In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity performs the creation and / or update process of the first A1 policy.

[0070] Embodiments of the present application provide a policy management method, including:

[0071] An application in the Non-RT RIC sends first indication information to a first entity; wherein the first indication information is used to indicate an execution priority of an A1 policy.

[0072] Optionally, the first indication information includes at least one of the following:

[0073] An A1 policy priority;

[0074] A priority of at least one policy action corresponding to an A1 policy;

[0075] First identification information corresponding to an A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0076] Second identification information corresponding to an A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0077] Optionally, the application in the Non-RT RIC sends first indication information to a first entity, including:

[0078] The application in the Non-RT RIC sends third request information to the first entity; wherein the third request information is used to request creation and / or update of an A1 policy, and the third request information includes the first indication information.

[0079] Optionally, before the application in the Non-RT RIC sends the first indication information to the first entity, the method further comprises:

[0080] The application in the Non-RT RIC sends second subscription information to a second entity, wherein the second subscription information is used to subscribe to the execution priority of the A1 policy.

[0081] Optionally, before the application in the Non-RT RIC sends the first indication information to the first entity, the method further comprises:

[0082] The application in the Non-RT RIC sends second query information to a second entity, wherein the second query information is used to request the execution priority of the A1 policy.

[0083] The application in the Non-RT RIC receives response information sent by the second entity, wherein the response information is used to indicate the execution priority supported by the A1 policy.

[0084] Optionally, the policy management method further comprises at least one of the following:

[0085] The application in the Non-RT RIC receives rejection information sent by the first entity, wherein the rejection information is used to indicate rejection of creation and / or update of the A1 policy.

[0086] The application in the Non-RT RIC receives retry information sent by the first entity, wherein the retry information is used to instruct the application to retry the creation and / or update process of the A1 policy.

[0087] The application in the Non-RT RIC sends third identification information to the first entity, wherein the third identification information is used to indicate whether the application allows retry of the A1 policy execution.

[0088] The application in the Non-RT RIC sends first deletion request information to the first entity, wherein the first deletion request information is used to request deletion of the A1 policy.

[0089] Embodiments of the present application provide a policy management method, comprising:

[0090] The second entity sends first indication information to the first entity and / or sends the first indication information to the application in the Non-RT RIC.

[0091] The first indication information is used to indicate the execution priority of the A1 policy.

[0092] Optionally, the first indication information comprises at least one of the following:

[0093] A1 policy priority;

[0094] A1 policy priority of at least one policy action corresponding to the A1 policy;

[0095] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0096] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0097] Optionally, the second entity sends first indication information to the first entity, and / or sends the first indication information to an application in the Non-RT RIC, comprising:

[0098] The second entity receives first query information sent by the first entity, and / or receives second query information sent by the application in the Non-RT RIC; wherein the first query information and / or the second query information are used to request to provide execution priority of the A1 policy; the second entity sends the first indication information to the first entity according to the first query information; and / or sends response information of the second query information to the application; wherein the response information is used to indicate execution priority supported by the A1 policy.

[0099] Optionally, before the second entity sends first indication information to the first entity, and / or sends the first indication information to the application in the Non-RT RIC, further comprising:

[0100] The second entity receives first subscription information sent by the first entity; wherein the subscription information is used to subscribe to execution priority of the A1 policy;

[0101] and / or,

[0102] The second entity receives second subscription information sent by the application in the Non-RT RIC; wherein the second subscription information is used to subscribe to execution priority of the A1 policy.

[0103] Embodiments of the present application provide a policy management device, comprising a memory, a transceiver, and a processor;

[0104] The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0105] receive first indication information sent by a second entity, and / or receive first indication information sent by an application in a Non-RT RIC;

[0106] perform A1 policy management according to the first indication information;

[0107] The first indication information is used to indicate an execution priority of the A1 policy.

[0108] Optionally, the first indication information comprises at least one of the following:

[0109] an A1 policy priority;

[0110] a priority of at least one policy action corresponding to the A1 policy;

[0111] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0112] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0113] Optionally, the A1 policy management comprises at least one of the following:

[0114] rejecting creation and / or update of an A1 policy in case of conflict;

[0115] suspending creation and / or update of an A1 policy in case of conflict;

[0116] deleting an A1 policy in case of conflict;

[0117] retrying creation and / or update process of an A1 policy that has been rejected or suspended from creation and / or update;

[0118] merging at least two A1 policies in case of conflict.

[0119] Optionally, in the case of a second A1 policy and a first A1 policy requested to be created and / or updated by a first application, the processor is configured to read the computer program in the memory and perform the following operations:

[0120] if it is determined according to the first indication information that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy, sending rejection information to the first application; wherein the rejection information is used to indicate rejection of creation and / or update of the first A1 policy;

[0121] and / or,

[0122] If it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, a creation and / or update process of the first A1 policy is performed.

[0123] Optionally, the processor is configured to read a computer program in the memory and perform the following operations:

[0124] receiving first deletion request information sent by a second application; wherein the first deletion request information is used to request deletion of the second A1 policy;

[0125] sending the first deletion request information to a Near-RT RIC;

[0126] receiving feedback information sent by the Near-RT RIC;

[0127] in a case where the feedback information indicates that the second A1 policy is successfully deleted, sending retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0128] Optionally, the processor is configured to read a computer program in the memory and perform the following operations:

[0129] receiving first deletion request information sent by a second application; wherein the first deletion request information is used to request deletion of the second A1 policy;

[0130] deleting the second A1 policy, and sending retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0131] Optionally, the processor is configured to read a computer program in the memory and perform the following operations:

[0132] sending the rejection information to the first application, and sending second deletion request information to a Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy;

[0133] receiving feedback information sent by the Near-RT RIC;

[0134] in a case where the feedback information indicates that the second A1 policy is successfully deleted, sending retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0135] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0136] receiving third identification information sent by the first application; wherein the third identification information is used to indicate whether the first application allows retry A1 policy execution;

[0137] sending retry information to the first application, including:

[0138] in a case where the third identification information indicates that the first application allows retry A1 policy execution, sending the retry information to the first application.

[0139] Optionally, the processor is configured to read the computer program in the memory and perform the following operations:

[0140] sending second deletion request information to the Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy;

[0141] receiving feedback information sent by the Near-RT RIC;

[0142] in a case where the feedback information indicates that the second A1 policy is successfully deleted, performing a creation and / or update process of the first A1 policy.

[0143] Embodiments of the present application provide a policy management device, comprising:

[0144] a first receiving unit configured to receive first indication information sent by a second entity and / or receive first indication information sent by an application in a Non-RT RIC;

[0145] a processing unit configured to perform A1 policy management according to the first indication information;

[0146] wherein the first indication information is used to indicate an execution priority of an A1 policy.

[0147] Embodiments of the present application provide a policy management device, comprising a memory, a transceiver, and a processor;

[0148] wherein the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0149] sending first indication information to a first entity; wherein the first indication information is used to indicate an execution priority of an A1 policy.

[0150] Embodiments of the present application provide a policy management device, comprising:

[0151] The first sending unit is configured to send first indication information to the first entity, wherein the first indication information is used to indicate the execution priority of the A1 policy.

[0152] The embodiment of the present application provides a policy management device, which comprises a memory, a transceiver and a processor.

[0153] The memory is configured to store a computer program; the transceiver is configured to transceive data under the control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations:

[0154] The first indication information is sent to the first entity and / or an application in the Non-RT RIC.

[0155] The first indication information is used to indicate the execution priority of the A1 policy.

[0156] The embodiment of the present application provides a policy management device, which comprises:

[0157] The sending unit is configured to send first indication information to the first entity and / or an application in the Non-RT RIC.

[0158] The first indication information is used to indicate the execution priority of the A1 policy.

[0159] The embodiment of the present application provides a processor-readable storage medium, which stores a computer program, and the computer program is used to make the processor execute the steps of the policy management method.

[0160] The embodiment of the present application provides a computer program product, which comprises computer instructions, and the computer instructions are executed by a processor to realize the steps of the policy management method.

[0161] The above technical solution of the present application has the following beneficial effects:

[0162] In the embodiment of the present application, the first entity obtains the first indication information, i.e., the execution priority of the A1 policy, through the second entity and / or the application in the Non-RT RIC, so that the A1 policy management can be performed based on the execution priority of different A1 policies, the conflict between A1 policies is solved or the conflict between A1 policies is avoided, and the problem that there is no corresponding solution to the policy and / or configuration conflict caused by the inconsistent policies between rApps is solved. BRIEF DESCRIPTION OF DRAWINGS

[0163] Figure 1Figure 1 shows a flow chart representing the process of creating a single Al policy in the Near-RT RIC according to an embodiment of the application;

[0164] Figure 2 Figure 2 shows a flow chart representing the method of policy management on the first entity side according to an embodiment of the application;

[0165] Figure 3 Figure 3 shows a schematic diagram representing the process of Al policy management according to an embodiment of the application;

[0166] Figure 4 Figure 4 shows a flow chart representing the method of policy management on the application side according to an embodiment of the application;

[0167] Figure 5 Figure 5 shows a flow chart representing the method of policy management on the second entity side according to an embodiment of the application;

[0168] Figure 6 Figure 6 shows a flow chart representing the process of querying the Al policy execution priority according to an embodiment of the application;

[0169] Figure 7 Figure 7 shows a flow chart representing the process of subscribing to the Al policy execution priority according to an embodiment of the application;

[0170] Figure 8 Figure 8 shows a flow chart representing the process of Al policy execution priority transmission according to an embodiment of the application;

[0171] Figure 9 Figure 9 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0172] Figure 10 Figure 10 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0173] Figure 11 Figure 11 shows a flow chart representing the process of Al policy execution priority transmission according to an embodiment of the application;

[0174] Figure 12 Figure 12 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0175] Figure 13 Figure 13 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0176] Figure 14 Figure 14 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0177] Figure 15 Figure 15 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0178] Figure 16 Figure 16 shows a flow chart representing the interaction of the method of policy management according to an embodiment of the application;

[0179] Figure 17 Figure 1 is a block diagram illustrating a policy management device on a first entity side according to an embodiment of the present application;

[0180] Figure 18 Figure 2 is a block diagram illustrating a policy management device on a first entity side according to another embodiment of the present application;

[0181] Figure 19 Figure 3 is a block diagram illustrating a policy management device on an application side according to an embodiment of the present application;

[0182] Figure 20 Figure 4 is a block diagram illustrating a policy management device on an application side according to another embodiment of the present application;

[0183] Figure 21 Figure 5 is a block diagram illustrating a policy management device on a second entity side according to an embodiment of the present application;

[0184] Figure 22 Figure 6 is a block diagram illustrating a policy management device on a second entity side according to another embodiment of the present application. DETAILED DESCRIPTION

[0185] In order to make the technical problems solved by the present application, technical solutions and advantages more clear, the following will be described in detail with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help the overall understanding of the embodiments of the present application. Therefore, those skilled in the art should understand that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. In addition, in order to be clear and concise, the description of known functions and structures is omitted.

[0186] It should be understood that the term "one embodiment" or "an embodiment" as referred to herein throughout the specification means that a specific feature, structure, or characteristic in connection with an embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "in one embodiment" or "in an embodiment" throughout the specification are not necessarily referring to the same embodiment. Furthermore, the various specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0187] In various embodiments of the present application, it should be understood that the size of the serial number of the following processes does not mean the order of execution, and the execution order of the processes should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0188] In addition, the terms "system" and "network" are often used interchangeably herein.

[0189] The technical solutions provided by the embodiments of the present application can be applied to various systems, such as a 5G system, a 6G system, and the like. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a long term evolution advanced (LTE-A) system, a universal mobile system (UMTS), a worldwide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, a 6G system, and the like. The various systems all include terminal devices and RAN devices. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), a 6G system, and the like.

[0190] The RAN device and the terminal device can each use one or more antennas for multi-input multi-output (MIMO) transmission. The MIMO transmission can be single user MIMO (SU-MIMO) or multiple user MIMO (MU-MIMO). According to the shape and number of root antenna combinations, the MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO. It can also be a diversity transmission or a precoding transmission or a beamforming transmission, and the like.

[0191] The term "and / or" in the embodiments of the present application describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after it.

[0192] The term "multiple" in the embodiments of the present application means two or more, and other quantifiers are similar.

[0193] The technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor are within the scope of protection of the present application.

[0194] The related technologies involved in the present application will be introduced as follows:

[0195] 1) Description of A1 policy conflict between rApps in O-RAN:

[0196] The logical function entity generating the A1 policy management service is exposed to the rApp through the R1 interface, referred to as the "A1 policy function" entity, which implements the following functions:

[0197] Perform A1 policy conflict resolution;

[0198] If multiple policy generating rApps set A1 policy statements that contradict A1 policy statements to the same or overlapping policy scope identifier, the A1 policy function entity decides to reject one or more A1 policy creation and / or modification requests, or temporarily suspend the implementation of one or more A1 policies.

[0199] 2) Process of creating and updating A1 Policy:

[0200] Create a single A1 policy in the determined Near-RT RIC, see Table 1 and Figure 1 as shown.

[0201] Table 1

[0202]

[0203]

[0204] Since the rApps have respective work or optimization targets, there may be conflicts in the execution process. For example, the A1 policy sent by the rApp with the energy saving target is to close some cells to achieve the energy saving target, while the A1 policy sent by the rApp with the quality of service (Qos) improvement target is to maintain the current cell resources and improve the bandwidth. In addition, for the same type of A1 policy, the optimization range sent by different rApps may also have overlapping parts, for example, the target value setting of the A1 policy based on the terminal or user equipment (UE) throughput improvement target and the A1 policy based on the slice service level agreement (slice SLA) UE throughput may not be consistent. How to handle the A1 policy conflicts between different rApps in the Non-RT RIC is a problem to be solved at present.

[0205] Embodiments of the present application provide a policy management method, device and processor readable storage medium, to solve the problem that there is no corresponding solution for the policy and / or configuration conflicts caused by the inconsistency of the policies between rApps. The method and device are based on the same application concept, and since the principles of solving problems are similar, the implementation of the device and the method can be mutually referred to, and the repeated parts will not be described again.

[0206] As shown in Figure 2 Embodiments of the present application provide a policy management method, comprising the following steps:

[0207] Step 21: The first entity receives the first indication information sent by the second entity, and / or receives the first indication information sent by the application program in the Non-RT RIC.

[0208] Step 22: The first entity performs A1 policy management according to the first indication information; wherein the first indication information is used to indicate the execution priority of the A1 policy.

[0209] Optionally, the first entity comprises at least one of the following:

[0210] A1 policy function (A1 Policy Function) entity in the Non-RT RIC;

[0211] Near-RT RIC;

[0212] and / or,

[0213] The second entity comprises at least one of the following:

[0214] application management function entity in the non-RT RIC;

[0215] A1 policy function entity in the non-RT RIC;

[0216] Function entities in the SMO architecture other than the non-RT RIC.

[0217] Optionally, the application can be an rApp requesting to create and / or update the A1 policy, or can also be an rApp with a management function in the non-RT RIC. For example, the application in the non-RT RIC sends first indication information to the first entity, which can be that rApp1 in the non-RT RIC provides the first indication information (i.e., the execution priority of the A1 policy requested by rApp1 to create and / or update) to the first entity, or that the rApp with a management function in the non-RT RIC provides the first indication information (i.e., the execution priority of the A1 policy requested by rApp1 to create and / or update) to the first entity, and the like, which is not limited in the embodiments of the present application.

[0218] Example 1: In the case where the first entity is the A1 policy function entity in the non-RT RIC, that is, the A1 policy function entity can obtain the first indication information corresponding to the rApp from the application management function entity in the non-RT RIC, or the A1 policy function entity can obtain the first indication information corresponding to the rApp from the function entities in the SMO architecture other than the non-RT RIC, or the rApp (such as the rApp requesting to create and / or update the A1 policy, or the rApp with a management function, and the like) provides the first indication information corresponding thereto to the A1 policy function entity, so that the A1 policy function entity can perform A1 policy management according to the first indication information corresponding to the rApp to solve the conflicts between A1 policies or avoid the conflicts between A1 policies.

[0219] Example 2: In the case where the first entity is the Near-RT RIC, that is, the A1 policy function entity can notify the Near-RT RIC of the first indication information corresponding to the rApp, so that the Near-RT RIC can perform A1 policy management according to the first indication information corresponding to the rApp to solve the conflicts between A1 policies or avoid the conflicts between A1 policies. Optionally, the A1 policy function entity can obtain the first indication information in a similar manner as in Example 1, which is not limited in the embodiments of the present application.

[0220] Optionally, the process of the first entity performing the A1 policy management includes processes such as conflict detection, conflict arbitration, and conflict resolution, as shown in Figure 3

[0221] For example, conflict detection is to detect whether there is a conflict between different A1 policies, such as whether there is an overlap between the configuration parameters of different A1 policies or the degree of overlap between the configuration parameters of different A1 policies, or whether there is a conflict between the policy actions of different A1 policies, such as the policy action of an A1 policy is to close some cells to achieve energy saving, and the policy action of another A1 policy is to maintain the current cell resources to improve Qos, etc. The embodiments of the present application are not limited thereto.

[0222] For example, the conflict detection scenario includes but is not limited to the following cases: when a certain rApp requests to create and / or update an A1 policy, the first entity determines that there is a conflict between the A1 policy requested to be created and / or updated by the rApp and a certain (or certain) A1 policy that has been created (or executed); or when multiple rApps request to create and / or update A1 policies, the first entity determines that there is a conflict between the A1 policies requested to be created and / or updated by the multiple rApps, etc. The embodiments of the present application are not limited thereto.

[0223] For example, conflict arbitration refers to making a decision on the execution priority of different A1 policies that have a conflict, and obtaining a decision result of the execution priority of the A1 policies. For example, when the first entity knows the execution priority of different A1 policies based on the first indication information, it can determine the decision result of the execution priority of different A1 policies based on the first indication information.

[0224] For example, conflict resolution refers to using a corresponding conflict resolution method to handle the conflict between A1 policies based on the decision result of the execution priority of the A1 policies that have a conflict. Optionally, the conflict resolution method includes but is not limited to one or a combination of the following: rejection, suspension, deletion, retry, merge, etc. For example, reject to create and / or update an A1 policy with low execution priority; or suspend the creation and / or update of an A1 policy first, and then retry the creation and / or update process of the A1 policy after the A1 policy conflict is eliminated; or delete an A1 policy with low priority to eliminate the A1 policy conflict; or merge A1 policies that have a conflict (such as merging A1 policy configuration parameters that have an overlap), etc. The embodiments of the present application are not limited thereto. ​

[0225] Optionally, the execution priority of the A1 policy can be determined by the priority (Prioirty) of the A1 policy itself and / or the preemption related capability (Preemption) corresponding to the A1 policy. For example, the first indication information includes at least one of the following:

[0226] A1 policy priority; for example, the A1 policy priority can represent the importance or importance degree of the A1 policy. For example, different A1 policies are configured with corresponding A1 policy priorities, and the A1 policy priority can be represented by an index or a priority level value. For example, the smaller the index or priority level value of the A1 policy priority is, the higher the A1 policy priority is, and the higher the execution priority of the A1 policy is; or, the larger the index or priority level value of the A1 policy priority is, the higher the A1 policy priority is, and the higher the execution priority of the A1 policy is. The embodiments of the present application are not limited thereto.

[0227] The priority of at least one policy action corresponding to the A1 policy; for example, one A1 policy corresponds to one policy type or one policy object, one policy object can correspond to one or more policy actions, and the policy action is described by a policy statement. For example, the policy statement can be to close a certain cell or certain cells to achieve energy saving, or the policy statement can also be to maintain the current cell resources to improve Qos, etc. For example, each policy statement corresponding to one A1 policy can be configured with a policy action priority, and the execution priority of the A1 policy can be determined based on the policy action priority of each policy statement corresponding to the A1 policy. For example, the highest policy action priority (or the policy action priority of a specific policy statement) of the policy action priorities of each policy statement corresponding to the A1 policy is taken as the A1 policy priority, and the execution priority of the A1 policy is determined based on the A1 policy priority. Of course, the embodiments of the present application are not limited thereto.

[0228] The first identification information corresponding to the A1 policy is used to indicate whether the A1 policy allows preemption of the execution of other A1 policies. For example, the first identification information can be referred to as preemption identification information, which is used to indicate whether the A1 policy has preemption capability. For example, if the first identification information indicates that preemption of the execution of other A1 policies is allowed, it means that the A1 policy has preemption capability, or if the first identification information indicates that preemption of the execution of other A1 policies is not allowed, it means that the A1 policy does not have preemption capability. For example, the preemption identification information indicates that, in the creation and / or update process, if a configuration and / or policy conflict occurs with other A1 policies, the A1 policy has the capability to preempt other A1 policies by deleting or interrupting the execution of other A1 policies.

[0229] The second identification information corresponding to the A1 policy is used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies. For example, the second identification information can be referred to as preemption protection information, which is used to indicate whether the execution of the A1 policy has the capability of not being preempted. For example, if the second identification information indicates that preemption of the execution of the A1 policy is not allowed, it means that the execution of the A1 policy has the capability of not being preempted, or if the second identification information indicates that preemption of the execution of the A1 policy is allowed, it means that the execution of the A1 policy does not have the capability of not being preempted. For example, the preemption protection indicates that, in the execution process, if a configuration and / or policy conflict occurs with other A1 policies, the execution of the A1 policy has the capability of not being interrupted.

[0230] In the above scheme, the first entity obtains the first indication information, i.e., the execution priority of the A1 policy, through the second entity and / or an application program in the Non-RT RIC, so that the A1 policy management can be performed based on the execution priority of different A1 policies to solve the conflict between A1 policies or avoid the conflict between A1 policies, thereby solving the problem that there is no corresponding solution for the policy and / or configuration conflict caused by inconsistent policies between rApps.

[0231] Optionally, before the first entity receives the first indication information sent by the second entity, the method further includes at least one of the following manners:

[0232] Manner 1: The first entity receives first request information sent by an application program in the Non-RT RIC; wherein the first request information is used to request creation and / or update of the A1 policy;

[0233] According to the first request information, the first query information is sent to the second entity; wherein the first query information is used to request to provide the execution priority of the A1 policy.

[0234] For example, the rApp requiring creation and / or update of the A1 policy can send first request information to the first entity, or the rApp requiring creation and / or update of the A1 policy can send first request information to the first entity through an rApp having a management function, etc. The first entity receiving the first request information sent by the rApp can be an A1 policy function entity as the first entity receiving the first request information sent by the rApp. In the case that the first entity receives the A1 policy creation and / or update request of the rApp, the first entity queries the execution priority of the A1 policy from a second entity (such as an application management function entity or a function entity other than Non-RT RIC in the SMO architecture, etc.). In this way, the first entity can perform A1 policy management in the case of knowing the execution priority of the A1 policy, so as to solve the conflict between A1 policies or avoid the conflict between A1 policies.

[0235] For example, the rApp requiring creation and / or update of the A1 policy can send first request information to the first entity, or the rApp requiring creation and / or update of the A1 policy can send first request information to the first entity through an rApp having a management function, etc. Specifically, the rApp can send first request information to an A1 policy function entity, and the A1 policy function entity forwards the first request information to a Near-RT RIC as the first entity, etc. In the case that the first entity receives the A1 policy creation and / or update request of the rApp, the first entity queries the execution priority of the A1 policy from a second entity (such as an A1 policy function entity or an application management function entity or a function entity other than Non-RT RIC in the SMO architecture, etc.). In this way, the first entity can perform A1 policy management in the case of knowing the execution priority of the A1 policy, so as to solve the conflict between A1 policies or avoid the conflict between A1 policies.

[0236] Option 2: The first entity sends first subscription information to the second entity; wherein the first subscription information is used to subscribe to the execution priority of the A1 policy.

[0237] For example, the A1 policy function entity as the first entity can subscribe to the execution priority of the A1 policy from a second entity (such as an application management function entity or a function entity other than Non-RT RIC in the SMO architecture, etc.). In this way, the first entity can perform A1 policy management in the case of the A1 policy creation and / or update request of the rApp, so as to solve the conflict between A1 policies or avoid the conflict between A1 policies.

[0238] For example, the Near-RT RIC as the first entity can subscribe to the execution priority of the A1 policy from a second entity (such as an A1 policy function entity or an application management function entity or a function entity other than the Non-RT RIC in the SMO architecture), so that the first entity can perform A1 policy management to resolve conflicts between A1 policies or avoid conflicts between A1 policies based on the execution priority of the A1 policy.

[0239] Optionally, the first entity receives first indication information sent by a second entity, including:

[0240] The first entity receives second request information sent by the second entity; wherein the second request information is used to request creation and / or update of an A1 policy, and the second request information includes the first indication information.

[0241] For example, the second entity (such as an A1 policy function entity or a function entity other than the Non-RT RIC in the SMO architecture) can receive an A1 policy creation and / or subscription request sent by an rApp (such as an rApp requiring creation and / or update of an A1 policy or an rApp having a management function), and forward the A1 policy creation and / or subscription request of the rApp to the Near-RT RIC as the first entity. Optionally, the second entity can learn the execution priority of the A1 policy by querying or subscribing, or learn the execution priority of the A1 policy from the A1 policy creation and / or subscription request of the rApp, and the embodiments of the present application are not limited thereto.

[0242] Optionally, the first entity receives first indication information sent by an application in a Non-RT RIC, including:

[0243] The first entity receives third request information sent by the application in the Non-RT RIC; wherein the third request information is used to request creation and / or update of an A1 policy, and the third request information includes the first indication information.

[0244] For example, the rApp (such as an rApp requiring creation and / or update of an A1 policy or an rApp having a management function) can query or subscribe to the execution priority of the A1 policy from an application management function entity or a function entity other than the Non-RT RIC in the SMO architecture, and notify the first entity (such as an A1 policy function entity or a Near-RT RIC) of the execution priority of the A1 policy when initiating creation and / or update of the A1 policy to the A1 policy function entity.

[0245] Optionally, the first entity performs A1 policy management according to the first indication information, including:

[0246] The first entity performs conflict detection on the at least two A1 policies to determine a conflict detection result.

[0247] If the conflict detection result is that there is a conflict between the at least two A1 policies, the first entity performs A1 policy management according to the first indication information.

[0248] For example, as an A1 policy function entity or Near-RT RIC, etc., as the first entity, when initiating A1 policy creation and / or update for an rApp, a conflict detection process can be started to detect whether there is a policy and / or configuration conflict between the A1 policy initiated for creation and / or update and one or more other A1 policies initiated for creation and / or update, or to detect whether there is a policy and / or configuration conflict between the A1 policy initiated for creation and / or update and one or more other A1 policies that have been created or executed. If there is a conflict, conflict arbitration can be performed based on the execution priority of different A1 policies, and A1 policy management is performed according to the corresponding arbitration result.

[0249] Optionally, the first entity determines that there is a conflict by at least one of the following ways:

[0250] There is overlap between configuration parameters of the at least two A1 policies; for example, there is overlap between target value settings of an A1 policy targeting to improve UE throughput and an A1 policy targeting to UE throughput based on slice SLA, etc., without being limited thereto in the embodiments of the present application.

[0251] There is a conflict between policy actions of the at least two A1 policies. For example, there is a conflict between an A1 policy with a policy action of shutting down some cells to achieve energy saving and an A1 policy with a policy action of maintaining current cell resources to improve Qos, etc., without being limited thereto in the embodiments of the present application.

[0252] Optionally, the A1 policy management includes at least one of the following ways:

[0253] Way 1: For the A1 policy with a conflict, the A1 policy creation and / or update is rejected.

[0254] For example, for A1 policy creation and / or update initiated by an rApp, if the conflict detection process determines that there is a conflict between the A1 policy initiated for creation and / or update by the rApp and other A1 policies, and the conflict arbitration process determines that the execution priority of the A1 policy initiated for creation and / or update by the rApp is low, the A1 policy creation and / or update of the rApp is rejected to avoid A1 policy conflicts.

[0255] Manner 2: For the A1 policy with conflict, suspend the A1 policy creation and / or update.

[0256] For example: for the A1 policy creation and / or update initiated by the rApp, if the conflict detection process determines that the A1 policy created and / or updated by the rApp has conflict with other A1 policies, and the conflict arbitration process determines that the A1 policy created and / or updated by the rApp has higher execution priority, then the A1 policy creation and / or update of the rApp can be suspended first to wait for conflict elimination (such as waiting for the execution of other A1 policies and / or waiting for the deletion of other created A1 policies, or using other conflict elimination methods, etc.), so as to avoid A1 policy conflict.

[0257] Manner 3: For the A1 policy with conflict, delete the A1 policy.

[0258] For example: for the A1 policy initiated for creation and / or update, if the conflict detection process determines that the A1 policy initiated for creation and / or update has conflict with other created A1 policies, and the conflict arbitration process determines that the created A1 policy has lower execution priority, then the created A1 policy can be deleted to eliminate the conflict.

[0259] Manner 4: For the A1 policy that has been rejected or suspended for creation and / or update, retry the creation and / or update process of the A1 policy.

[0260] For example: for the A1 policy initiated for creation and / or update, if the conflict detection process determines that the A1 policy initiated for creation and / or update has conflict with other created A1 policies, and the conflict arbitration process determines that the A1 policy initiated for creation and / or update has higher execution priority, then the creation and / or update of the A1 policy can be suspended first, and after the deletion of other created A1 policies in conflict, the creation and / or update process of the A1 policy is retried, that is, conflict elimination is performed before the creation and / or update of the A1 policy, so as to avoid the occurrence of A1 policy conflict.

[0261] Manner 5: For at least two A1 policies with conflict, merge the at least two A1 policies.

[0262] For example, for the first A1 policy initiated to create and / or update, there is a conflict between the first A1 policy and the second other A1 policy in the conflict detection process (for example, there is an overlap between the configuration parameters of the first A1 policy and the second A1 policy), the first A1 policy and the second A1 policy can be merged. For example, in the case of the first entity being an A1 policy function entity, the first A1 policy is created or updated by the first rApp, and the second A1 policy is created or updated by the second rApp, the A1 policy function entity can create or update the A1 policies corresponding to the first rApp and / or the second rApp respectively, and send the merged A1 policy to the Near-RT RIC.

[0263] Optionally, in the case of the second A1 policy and the first A1 policy requested by the first application program to create and / or update, the first entity performs A1 policy management according to the first indication information, including:

[0264] If it is determined according to the first indication information that the execution priority of the first A1 policy is lower than or equal to the execution priority of the second A1 policy, the first entity sends rejection information to the first application program; wherein the rejection information is used to indicate rejection of creating and / or updating the first A1 policy;

[0265] and / or,

[0266] If it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, the first entity performs the first A1 policy creation and / or update process.

[0267] Optionally, the second A1 policy can be an A1 policy requested by the second application program to create and / or update, or can also be an A1 policy created or updated by the second application program, etc., which is not limited in the embodiments of the present application.

[0268] For example, taking the first application program as an rApp requesting to create and / or update an A1 policy, and the second application program as another rApp requesting to create and / or update an A1 policy as an example, if it is determined according to the first indication information that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy, the first A1 policy is rejected to be created and / or updated, and the second A1 policy creation and / or update process is performed. And / or, if it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, the first A1 policy creation and / or update process is performed, and the second A1 policy is rejected to be created and / or updated.

[0269] For example, taking the first application as an rApp requesting to create and / or update an Al policy and the second application as another rApp having created an Al policy, if it is determined according to the first indication information that the execution priority of the first Al policy is lower than or equal to the execution priority of the second Al policy, the creation and / or update of the first Al policy is rejected; and / or if it is determined according to the first indication information that the execution priority of the first Al policy is higher than the execution priority of the second Al policy, the second Al policy can be directly deleted or the first Al policy creation and / or update process is executed after the second application successfully requests to delete the second Al policy.

[0270] Optionally, the first entity determines the priority relationship between the execution priority of the first Al policy and the execution priority of the second Al policy by at least one of the following manners:

[0271] Manner 1: If the Al policy priority corresponding to the first Al policy is higher than the Al policy priority corresponding to the second Al policy, it is determined that the execution priority of the first Al policy is higher than the execution priority of the second Al policy.

[0272] For example, taking the smaller index value or priority value as the higher Al policy priority as an example, if the index value of the Al policy priority corresponding to the first Al policy is “1” and the index value of the Al policy priority corresponding to the second Al policy is “3”, it is determined that the execution priority of the first Al policy is higher than the execution priority of the second Al policy.

[0273] Manner 2: If the Al policy priority corresponding to the first Al policy is lower than the Al policy priority corresponding to the second Al policy, it is determined that the execution priority of the first Al policy is lower than the execution priority of the second Al policy.

[0274] For example, taking the smaller index value or priority value as the higher Al policy priority as an example, if the index value of the Al policy priority corresponding to the first Al policy is “3” and the index value of the Al policy priority corresponding to the second Al policy is “1”, it is determined that the execution priority of the first Al policy is lower than the execution priority of the second Al policy.

[0275] Manner 3: If the Al policy priority corresponding to the first Al policy is equal to the Al policy priority corresponding to the second Al policy, it is determined that the execution priority of the first Al policy is lower than the execution priority of the second Al policy.

[0276] For example, taking the case that the smaller the index value or priority value, the higher the priority of the Al policy, if the index values of the Al policy priorities corresponding to different Al policies are the same, it is determined that the Al policy corresponding to the Al policy initiated by the later to create and / or update has a lower Al policy execution priority. For example: the first application initiates the creation and / or update of the first Al policy, the index value of the Al policy priority corresponding to the first Al policy is "3", and the index value of the Al policy priority corresponding to the second Al policy that has been created is also "3". Since the second Al policy has been created in advance, it is determined that the Al policy execution priority of the first Al policy is lower than that of the second Al policy.

[0277] Method 4: If the first identification information corresponding to the first Al policy is a first value, and / or the first identification information corresponding to the second Al policy is a second value, it is determined that the priority relationship is that the Al policy execution priority of the first Al policy is higher than that of the second Al policy.

[0278] Method 5: If the first identification information corresponding to the first Al policy is a second value, and / or the first identification information corresponding to the second Al policy is a first value, it is determined that the priority relationship is that the Al policy execution priority of the first Al policy is higher than that of the second Al policy.

[0279] For example, if the first identification information corresponding to the first Al policy is a first value, the first identification information being the first value is used to indicate that the execution of other Al policies is allowed to be preempted, it is determined that the first Al policy has the ability to preempt the execution of other Al policies, and it is determined that the execution priority of the first Al policy is higher than that of the second Al policy. Conversely, if the first identification information corresponding to the second Al policy is a first value, it is determined that the second Al policy has the ability to preempt the execution of other Al policies, and it is determined that the execution priority of the second Al policy is higher than that of the first Al policy.

[0280] For example, if the first identification information corresponding to the first Al policy is a first value, and the first identification information corresponding to the second Al policy is a second value, the second value of the first identification information is used to indicate that the execution of other Al policies is not allowed to be preempted, that is, the first Al policy has the capability of preempting the execution of other Al policies, and the second Al policy does not have the capability of preempting the execution of other Al policies, it is determined that the execution priority of the first Al policy is higher than the execution priority of the second Al policy. Conversely, if the first identification information corresponding to the first Al policy is a second value, and the first identification information corresponding to the second Al policy is a first value, that is, the first Al policy does not have the capability of preempting the execution of other Al policies, and the second Al policy has the capability of preempting the execution of other Al policies, it is determined that the execution priority of the second Al policy is higher than the execution priority of the first Al policy.

[0281] Mode 6: If the second identification information corresponding to the first Al policy is a first value, and / or the second identification information corresponding to the second Al policy is a second value, it is determined that the priority relationship is that the execution priority of the first Al policy is higher than the execution priority of the second Al policy.

[0282] The second value of the second identification information is used to indicate that the second Al policy is allowed to be preempted by other Al policies.

[0283] For example, taking the first Al policy as an Al policy requested to be created and / or updated by a first application program, and the second Al policy as an Al policy requested to be created and / or updated by a second application program, if the second identification information corresponding to the first Al policy is a first value, and / or the second identification information corresponding to the second Al policy is a second value, that is, the first Al policy has the capability of not being preempted by other Al policies, and / or the second Al policy is allowed to be preempted by other Al policies, it is determined that the execution priority of the first Al policy is higher than the execution priority of the second Al policy.

[0284] For example, taking the first Al policy as an Al policy requested to be created and / or updated by a first application program, and the second Al policy as an Al policy requested to be created and / or updated by a second application program, if the second identification information corresponding to the first Al policy is a second value, and / or the second identification information corresponding to the second Al policy is a first value, that is, the first Al policy is allowed to be preempted by other Al policies, and / or the second Al policy has the capability of not being preempted by other Al policies, it is determined that the execution priority of the first Al policy is lower than the execution priority of the second Al policy.

[0285] It should be noted that, when the first indication information includes the A1 policy priority, and further includes at least one of the first identification information and / or the second identification information, the first identification information and / or the second identification information are used to perform conflict arbitration (i.e., determine the priority relationship). Alternatively, in the case that the first identification information corresponding to different A1 policies is the same, the conflict arbitration (i.e., determining the priority relationship) can be further performed according to the second identification information and / or the A1 policy priority; or, in the case that the first identification information and the second identification information corresponding to different A1 policies are the same, the conflict arbitration (i.e., determining the priority relationship) can be further performed according to the A1 policy priority, and the embodiments of the present application are not limited thereto.

[0286] For example, if the first identification information corresponding to the first A1 policy and the second A1 policy is the first value, that is, the first A1 policy and the second A1 policy both have the ability to preempt the execution of other A1 policies, the priority relationship can be determined based on whether the first A1 policy and / or the second A1 policy is configured with the second identification information, and / or based on the A1 policy priority between the first A1 policy and the second A1 policy. Correspondingly, if the first identification information corresponding to the first A1 policy and the second A1 policy is the second value, that is, the first A1 policy and the second A1 policy both do not have the ability to preempt the execution of other A1 policies, the priority relationship can be determined based on whether the first A1 policy and / or the second A1 policy is configured with the second identification information, and / or based on the A1 policy priority between the first A1 policy and the second A1 policy, and the embodiments of the present application are not limited thereto.

[0287] Optionally, after the first entity sends the rejection information to the first application program, the first entity further includes:

[0288] The first entity receives first deletion request information sent by a second application program; wherein the first deletion request information is used to request to delete the second A1 policy;

[0289] The first entity sends the first deletion request information to the Near-RT RIC;

[0290] The first entity receives feedback information sent by the Near-RT RIC;

[0291] In the case that the feedback information indicates that the second A1 policy is successfully deleted, the first entity sends retry information to the first application program; wherein the retry information is used to instruct the first application program to retry the creation and / or update process of the first A1 policy.

[0292] For example, taking the first entity as an A1 policy function entity and the first application as an rApp requesting to create and / or update a first A1 policy and the second application as another rApp having created a second A1 policy, if it is determined according to the first indication information that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy, the creation and / or update of the first A1 policy is rejected. Further, after the creation and / or update of the first A1 policy is rejected, if the second application actively requests to delete the second A1 policy, the A1 policy function entity can notify the first application to reattempt to initiate the creation and / or update process of the first A1 policy after the second A1 policy is successfully deleted by the Near-RT RIC, so that for the A1 policy whose creation and / or update is rejected, the creation and / or update process of the A1 policy can be retried after the conflict is resolved, so as to ensure the reliability of the creation and / or update of the A1 policy in the case of avoiding the occurrence of A1 policy or configuration conflicts.

[0293] Optionally, after the first entity sends the rejection information to the first application, the method further comprises:

[0294] The first entity receives first deletion request information sent by a second application, wherein the first deletion request information is used to request to delete the second A1 policy.

[0295] The first entity deletes the second A1 policy, and sends retry information to the first application, wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

[0296] For example, taking the first entity as a Near-RT RIC and the first application as an rApp requesting to create and / or update a first A1 policy and the second application as another rApp having created a second A1 policy, if it is determined according to the first indication information that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy, the creation and / or update of the first A1 policy is rejected. Further, after the creation and / or update of the first A1 policy is rejected, if the second application actively requests to delete the second A1 policy, the Near-RT RIC can delete the second A1 policy and notify the first application to reattempt to initiate the creation and / or update process of the first A1 policy, so that for the A1 policy whose creation and / or update is rejected, the creation and / or update process of the A1 policy can be retried after the conflict is resolved, so as to ensure the reliability of the creation and / or update of the A1 policy in the case of avoiding the occurrence of A1 policy or configuration conflicts.

[0297] Optionally, the first entity performing the creation and / or update process of the first A1 policy comprises:

[0298] The first entity sends the rejection information to the first application program, and sends second deletion request information to the Near-RT RIC; wherein the second deletion request information is used to request deletion of the second Al policy;

[0299] The first entity receives feedback information sent by the Near-RT RIC;

[0300] In a case where the feedback information indicates that the second Al policy is successfully deleted, the first entity sends retry information to the first application program; wherein the retry information is used to instruct the first application program to retry the creation and / or update process of the first Al policy.

[0301] For example, taking the first entity as an Al policy function entity, in a case where the first application program is an rApp requesting creation and / or update of a first Al policy, and the second application program is another rApp having created a second Al policy, if it is determined according to the first indication information that the execution priority of the first Al policy is higher than that of the second Al policy, the creation and / or update of the first Al policy can be rejected first, and the Near-RT RIC is requested to delete the second Al policy. Further, after the Near-RT RIC successfully deletes the second Al policy, the first application program can be notified to reattempt to initiate the creation and / or update process of the first Al policy. In this way, for the application programs that have conflicts, the Al policy creation and / or update can be suspended first, and after the conflicts are resolved, the Al policy creation and / or update process is retried, so as to ensure the reliability of the Al policy creation and / or update in the case where Al policy or configuration conflicts do not occur.

[0302] Optionally, before the first entity sends the retry information to the first application program, the method further includes:

[0303] The first entity receives third identification information sent by the first application program; wherein the third identification information is used to indicate whether the first application program allows retry of Al policy execution;

[0304] The first entity sends the retry information to the first application program, including:

[0305] In a case where the third identification information indicates that the first application program allows retry of Al policy execution, the first entity sends the retry information to the first application program.

[0306] For example, the first application program can carry the third identification information in the request information of the A1 policy creation and / or update when initiating the A1 policy creation and / or update request. The third identification information can be a notification destination identifier (NotifyDesitinationURI). When the first application program initiates the A1 policy creation and / or update request, and indicates that the first application program supports reattempting to create and / or update the A1 policy after the creation and / or update of the A1 policy is rejected or aborted, the first entity can send retry information to the first application program to notify the first application program to reattempt to initiate the A1 policy creation and / or update process.

[0307] Optionally, the first entity performing the first A1 policy creation and / or update process comprises:

[0308] The first entity sends second deletion request information to the Near-RT RIC, wherein the second deletion request information is used to request to delete the second A1 policy.

[0309] The first entity receives feedback information sent by the Near-RT RIC.

[0310] In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity creates and / or updates the first A1 policy.

[0311] For example, taking the first entity as an A1 policy function entity, in a case where the first application program is an rApp requesting to create and / or update a first A1 policy, and the second application program is another rApp having created a second A1 policy, if it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, the creation and / or update of the first A1 policy can be first suspended, and the Near-RT RIC is requested to delete the second A1 policy. Further, after the Near-RT RIC successfully deletes the second A1 policy, the creation and / or update process of the first A1 policy is continued. In this way, for the application programs that have conflicts, the A1 policy creation and / or update can be first suspended and the conflict resolution process is performed, and after the conflict is resolved, the A1 policy creation and / or update process is performed, so that the reliability of the A1 policy creation and / or update is ensured in a case where A1 policy or configuration conflicts do not occur.

[0312] For example, taking the first entity as the Near-RT RIC, in the case where the first application is an rApp requesting to create and / or update the first A1 policy and the second application is another rApp having created the second A1 policy, if it is determined according to the first indication information that the execution priority of the first A1 policy is higher than that of the second A1 policy, the creation and / or update of the first A1 policy can be suspended, and the second A1 policy can be deleted to eliminate the conflict. Further, after the second A1 policy is successfully deleted, the creation and / or update process of the first A1 policy is continued. In this way, the A1 policy creation and / or update process is performed after the conflict is resolved, thereby guaranteeing the reliability of the A1 policy creation and / or update in the case where the A1 policy or configuration conflict is avoided.

[0313] As shown in Figure 4 Embodiments of the present application provide a policy management method, comprising the following steps:

[0314] Step 41: An application in the Non-RT RIC sends first indication information to the first entity; wherein the first indication information is used to indicate the A1 policy execution priority.

[0315] Optionally, the application can be an rApp requesting to create and / or update the A1 policy, or can also be an rApp in the Non-RT RIC having a management function. For example, the Non-RT RIC application sending the first indication information to the first entity can be that the rApp1 in the Non-RT RIC provides the first indication information (i.e. the execution priority of the A1 policy requested to be created and / or updated by the rApp1) to the first entity, or that the rApp in the Non-RT RIC having a management function provides the first indication information (i.e. the execution priority of the A1 policy requested to be created and / or updated by the rApp1) to the first entity, etc., which is not limited in the embodiments of the present application.

[0316] It should be noted that the policy management method of the application side in the Non-RT RIC in the embodiments of the present application and the above-mentioned policy management method of the first entity side are based on the same inventive concept, and the embodiments of the two can be referred to each other and can achieve the same technical effects, and the repeated parts will not be described again, but the differences between the two will be described.

[0317] Optionally, the first entity comprises at least one of the following:

[0318] An A1 policy function entity in the Non-RT RIC;

[0319] A Near-RT RIC.

[0320] Optionally, the first indication information comprises at least one of the following:

[0321] a priority of the A1 policy;

[0322] a priority of at least one policy action corresponding to the A1 policy;

[0323] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0324] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0325] Optionally, the application in the Non-RT RIC sends the first indication information to the first entity, comprising:

[0326] the application in the Non-RT RIC sends third request information to the first entity; wherein the third request information is used to request creation and / or update of the A1 policy, and the third request information comprises the first indication information.

[0327] Optionally, before the application in the Non-RT RIC sends the first indication information to the first entity, the method further comprises:

[0328] the application in the Non-RT RIC sends second subscription information to the second entity; wherein the second subscription information is used to subscribe to the execution priority of the A1 policy.

[0329] In this embodiment, the application in the Non-RT RIC can subscribe to the execution priority of the A1 policy from the second entity (such as the application management function entity in the Non-RT RIC or a function entity other than the Non-RT RIC in the SMO architecture). In this way, when initiating creation and / or update of the A1 policy, the application can notify the first entity of the execution priority of the A1 policy.

[0330] For example, the execution priority of the A1 policy obtained by the application in the Non-RT RIC from the second entity can be a priority supported by the A1 policy, such as the highest priority supported by the A1 policy, or a priority range supported by the A1 policy, etc.

[0331] It should be noted that the execution priority supported by the A1 policy can represent the execution capability of the A1 policy. For example, the smaller the index value corresponding to the A1 policy priority of the A1 policy, the higher the A1 policy priority. For example, the application program queries the second entity for the index value corresponding to the A1 policy priority supported by a certain A1 policy, which is "1", indicating that the highest priority supported by the A1 policy is "1". When the application program initiates an A1 policy creation and / or update request to the first entity, the index value corresponding to the A1 policy priority of the A1 policy can be indicated as "1", or the index value corresponding to the A1 policy priority of the A1 policy can also be indicated as other values lower than "1", such as "2" or "3" or other index values lower than "1" in the priority index range, and the embodiments of the present application are not limited thereto.

[0332] Optionally, before the application program in the Non-RT RIC sends the first indication information to the first entity, the method further comprises the following steps:

[0333] The application program in the Non-RT RIC sends second query information to the second entity, wherein the second query information is used to request to provide the execution priority of the A1 policy;

[0334] The application program in the Non-RT RIC receives response information sent by the second entity, wherein the response information is used to indicate the execution priority supported by the A1 policy.

[0335] In this embodiment, before initiating the A1 policy creation and / or update, the application program in the Non-RT RIC can query the execution priority of the A1 policy from the second entity (such as the application program management function entity in the Non-RT RIC or the function entity other than the Non-RT RIC in the SMO architecture). Optionally, the application program can determine the actual execution priority of the A1 policy according to the execution priority supported by the A1 policy provided by the second entity, and notify the first entity of the actual execution priority of the A1 policy when initiating the A1 policy creation and / or update (for details, please refer to the above embodiments, which will not be repeated here).

[0336] Optionally, the policy management method further comprises at least one of the following:

[0337] The application program in the Non-RT RIC receives rejection information sent by the first entity, wherein the rejection information is used to indicate the rejection of creating and / or updating the A1 policy;

[0338] The application program in the Non-RT RIC receives retry information sent by the first entity, wherein the retry information is used to instruct the application program to retry the creation and / or update process of the A1 policy.

[0339] The application in the Non-RT RIC sends third identification information to the first entity; wherein the third identification information is used to indicate whether the application allows retry A1 policy execution;

[0340] The application in the Non-RT RIC sends first deletion request information to the first entity; wherein the first deletion request information is used to request deletion of the A1 policy.

[0341] It should be noted that the above-mentioned policy management method provided by the embodiments of the present application can realize the method steps corresponding to the policy management method embodiments on the first entity side, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments in the embodiments will not be described in detail.

[0342] As shown in Figure 5 The embodiments of the present application provide a policy management method, comprising the following steps:

[0343] Step 51: The second entity sends first indication information to the first entity, and / or sends first indication information to the application in the Non-RT RIC; wherein the first indication information is used to indicate the execution priority of the A1 policy.

[0344] Optionally, the first entity comprises at least one of the following:

[0345] A1 policy function entity in the Non-RT RIC;

[0346] Near-RT RIC;

[0347] And / or,

[0348] The second entity comprises at least one of the following:

[0349] Application management function entity in the Non-RT RIC;

[0350] A1 policy function entity in the Non-RT RIC;

[0351] Functional entity in the SMO architecture except the Non-RT RIC.

[0352] Optionally, the first indication information comprises at least one of the following:

[0353] A1 policy priority;

[0354] Priority of at least one policy action corresponding to the A1 policy;

[0355] The first identification information corresponding to the A1 policy is used to indicate whether the A1 policy allows preemption of execution of other A1 policies.

[0356] The second identification information corresponding to the A1 policy is used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0357] Optionally, the second entity sends first indication information to the first entity, and / or sends the first indication information to an application in the Non-RT RIC, including:

[0358] The second entity receives first query information sent by the first entity, and / or receives second query information sent by the application in the Non-RT RIC; wherein the first query information and / or the second query information is used to request to provide an execution priority of an A1 policy;

[0359] The second entity sends the first indication information to the first entity according to the first query information, and / or sends response information of the second query information to the application in the Non-RT RIC; wherein the response information is used to indicate an execution priority supported by the A1 policy.

[0360] Optionally, before the second entity sends first indication information to the first entity, and / or sends the first indication information to an application in the Non-RT RIC, further including:

[0361] The second entity receives first subscription information sent by the first entity; wherein the subscription information is used to subscribe to an execution priority of an A1 policy;

[0362] And / or,

[0363] The second entity receives second subscription information sent by the application; wherein the second subscription information is used to subscribe to an execution priority of an A1 policy.

[0364] It should be noted that the policy management method of the second entity in the embodiment of the present application is based on the same inventive concept as the policy management method of the first entity and / or the policy management method of the application in the Non-RT RIC. The policy management method can implement the method steps corresponding to the policy management method of the first entity and / or the policy management method of the application in the Non-RT RIC, and can achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiment will not be described in detail.

[0365] The first entity, the second entity and the application in the Non-RT RIC involved in the embodiments of the present application belong to RAN devices. Depending on the specific application scenario, the RAN device may include a base station, or may be a device in the access network that communicates with the wireless terminal device through one or more sectors on the air interface, or other names. The base station may include multiple cells that provide services for the terminal. The RAN device can be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The RAN device can also coordinate the attribute management of the air interface. For example, the RAN device involved in the embodiments of the present application may be a RAN device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a RAN device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolved RAN device (eNB or e-NodeB) in the Long Term Evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present application. In some network structures, the RAN device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0366] The following describes the policy management method of this application in conjunction with specific embodiments:

[0367] Example 1: A1 policy capability query service;

[0368] like Figure 6 As shown, a flowchart of querying the execution priority of the A1 strategy is given, which specifically includes:

[0369] Step 61: The first entity or rApp (eg, an rApp that needs to create and / or update an A1 policy or an rApp with management functions) queries the second entity via the R1 interface for the A1 policy execution priority and carries a list of A1 policy types supported by the current rApp.

[0370] Step 62: The second entity sends the A1 policy type list and the corresponding A1 policy execution priorities to the first entity or rApp (eg, an rApp that needs to create and / or update an A1 policy or an rApp with management functions).

[0371] Example 2: A1 policy capability configuration (or subscription) service;

[0372] like Figure 7 As shown, a flowchart of subscribing to the A1 policy execution priority is given, specifically including:

[0373] Step 71: When the A1 policy execution priority changes, the second entity sends the A1 policy type list and the corresponding A1 policy execution priority to the first entity or rAPP (eg, rApp that needs to create and / or update A1 policies or rApp with management functions).

[0374] Step 72: The first entity or rAPP (eg, an rApp that needs to create and / or update an A1 policy or an rApp with management functions) returns a response indicating that the A1 policy capability configuration is successful.

[0375] Embodiment 3: An rApp (such as an rApp that needs to create and / or update an A1 policy or an rApp with management functions) provides the first entity with an A1 policy execution priority;

[0376] like Figure 8 As shown, a flowchart of an A1 strategy execution priority transmission is given, specifically including:

[0377] Step 81: The rApp reads the A1 policy execution priority (eg, A1 policy priority and / or preemption capability information) from the second entity.

[0378] Step 82: When creating or updating an A1 policy, the rApp sets the A1 policy execution priority corresponding to the A1 policy (eg, A1 policy priority and / or preemption capability).

[0379] Step 83: When the first entity (eg, A1 policy function entity) finds during conflict detection that the currently created or updated A1 policy has configuration and / or policy conflicts with other A1 policies, it uses the corresponding A1 policy execution priority to perform conflict arbitration.

[0380] Embodiment 4: Conflict arbitration based on A1 policy priority;

[0381] In the A1 policy creation and / or update process, the first entity first performs conflict detection, and if a configuration and / or policy conflict is detected, the execution order of the A1 policy that has a conflict is determined based on the A1 policy execution priority, as shown in the following table. Figure 9 As an example, the first entity is an A1 policy function entity, and the second entity is an rApp management function entity, and the specific process includes:

[0382] Step 91: rApp1 queries the A1 policy 1 execution priority configuration information through the rApp management function entity, and obtains that the maximum settable A1 policy priority is “1” (for example, “1” corresponds to the highest priority).

[0383] Step 92: rApp1 sends an A1 policy 1 creation request to the A1 policy function entity and sets the A1 policy priority to “3”.

[0384] It should be noted that the A1 policy priority corresponding to the A1 policy 1 is configured as the highest priority, and when the A1 policy creation request is initiated, the corresponding A1 policy priority can be set to “1” or other lower A1 policy priorities, such as “3”, and the embodiments of the present application are not limited thereto.

[0385] Step 93: The A1 policy function entity performs conflict detection and determines that there is no configuration or policy that conflicts with the A1 policy 1.

[0386] Step 94: The A1 policy function entity sends an A1 policy 1 creation request to the Near-RT RIC.

[0387] Step 95: The Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0388] Step 96: After the A1 policy 1 is created successfully, the Near-RT RIC sends a creation success response to the A1 policy function entity.

[0389] Step 97: The A1 policy function entity feeds back an A1 policy 1 creation success response to the rApp1.

[0390] Step 98: rApp2 queries the A1 policy execution priority configuration information through the rApp management function entity, and obtains that the maximum settable A1 policy priority is “5” (for example, “1” corresponds to the highest priority).

[0391] Step 99: rApp2 sends an A1 policy 2 creation request to the A1 policy function entity and sets the A1 policy priority to “5”.

[0392] Step 910: The A1 policy function entity performs conflict detection and determines that there is a conflict between the A1 policy 1 and the A1 policy 2.

[0393] The A1 policy function entity performs conflict arbitration and determines that the priority "5" of the A1 policy 2 is greater than the priority "3" of the A1 policy 1; therefore, the A1 policy function entity determines that the arbitration result is that the execution priority of the A1 policy 2 is lower than the execution priority of the A1 policy 1.

[0394] Step 911: The A1 policy function entity sends a response of A1 policy 2 creation failure to the rApp 2.

[0395] Embodiment 5: Conflict arbitration based on preemption flag and / or preemption protection;

[0396] In the A1 policy creation and / or update process, the first entity first performs conflict detection, and if a configuration and / or policy conflict is detected, a conflict arbitration process is performed through a preemption flag and / or preemption protection to determine the execution order of the A1 policies in conflict, as shown in Figure 10 Taking the first entity as the A1 policy function entity and the second entity as the rApp management function entity as an example, the specific process includes:

[0397] Step 101: The rApp 1 queries the preemption capability configuration information of the A1 policy 1 through the rApp management function entity, and obtains that the preemption protection flag is TRUE or "1", that is, the second identification information corresponding to the A1 policy 1 indicates that the execution of the A1 policy 1 is not allowed to be preempted by other A1 policies, which means that if the A1 policy 1 is executed, it cannot be interrupted by other A1 policies in conflict.

[0398] Step 102: The rApp 1 sends a creation request of the A1 policy 1 and sets the preemption protection flag as TRUE.

[0399] Step 103: The A1 policy function entity performs conflict detection and determines that there is no configuration and / or policy in conflict with the A1 policy 1.

[0400] Step 104: The A1 policy function entity sends a creation request of the A1 policy 1 to the Near-RT RIC.

[0401] Step 105: The Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0402] Step 106: After the A1 policy 1 is created successfully, the Near-RT RIC sends a response of the A1 policy 1 creation success to the A1 policy function entity.

[0403] Step 107: The A1 policy function entity sends a response of the A1 policy 1 creation success.

[0404] Step 108: rApp2 queries the preemption capability configuration information of A1 policy 2 through the rApp management function entity, and obtains that the preemption flag is false (FALSE) or "0", that is, the first identification information corresponding to A1 policy 2 indicates that A1 policy 2 is not allowed to preempt the execution of other A1 policies, that is, when A1 policy 2 is executed, it cannot interrupt the execution of other A1 policies that conflict with it.

[0405] Step 109: rApp2 sends a create request for A1 policy 2 and sets the preemption flag to FALSE.

[0406] Step 1010: The A1 policy function entity performs conflict detection: There is a conflict between A1 policy 1 and A1 policy 2.

[0407] The A1 policy function entity performs conflict arbitration: A1 policy 1 is configured with the preemption protection flag set to TRUE, and A1 policy 1 is configured with the preemption flag set to FALSE. Therefore, the A1 policy function entity determines the arbitration result as: A1 policy 2 cannot be executed.

[0408] Step 1011: Send a response to rApp2 indicating that A1 policy 2 creation failed.

[0409] It should be noted that if the preemption protection flag is FALSE or "0", it means that the execution of the A1 policy can be interrupted by other conflicting A1 policies. If the preemption flag is TRUE or "1", it means that the execution of the A1 policy can interrupt the execution of other conflicting A1 policies.

[0410] Example 6: The first entity obtains the A1 policy execution priority by itself;

[0411] like Figure 11 As shown in FIG, another flowchart of the A1 strategy execution priority transmission is given, and the specific process includes:

[0412] Step 111: rApp sends a request to create or update the A1 policy.

[0413] Step 112: The first entity (e.g., A1 policy functional entity) discovers during conflict detection that the currently created or updated A1 policy has a configuration and / or policy conflict with other A1 policies, and queries the second entity (e.g., rApp management functional entity) for the corresponding A1 policy execution priority (e.g., including A1 policy priority and / or preemption capability information).

[0414] Step 113: The first entity (eg, the A1 policy function entity) performs conflict arbitration.

[0415] Example 7: Conflict arbitration based on A1 policy priority;

[0416] In this embodiment, the first entity directly queries the second entity for the A1 policy priority corresponding to the A1 policy 1. Specifically, during the creation and / or update of the A1 policy 1, the first entity first performs conflict detection. If a configuration and / or policy conflict is detected, the first entity performs a conflict arbitration process by querying the second entity for the A1 policy priority corresponding to the A1 policy 1 to determine the execution order of the A1 policies in conflict, as shown in Figure 12 For example, the first entity is an A1 policy function entity, and the second entity is an rApp management function entity, i.e., the A1 policy function entity directly queries the rApp management function entity for the A1 policy priority corresponding to the rApp, which specifically includes:

[0417] Step 121: The rApp 1 sends a creation request for the A1 policy 1.

[0418] Step 122: The A1 policy function entity performs conflict detection and determines that there is no configuration and / or policy in conflict with the A1 policy requested by the rApp 1 to be created.

[0419] Step 123: The A1 policy function entity sends a creation request for the A1 policy 1 to the Near-RT RIC.

[0420] Step 124: The Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0421] Step 125: After the A1 policy is created successfully, the Near-RT RIC sends a response to the A1 policy function entity that the creation of the A1 policy 1 is successful.

[0422] Step 126: The A1 policy function entity sends a response that the creation of the A1 policy 1 is successful.

[0423] Step 127: The rApp 2 sends a creation request for the A1 policy 2.

[0424] Step 128: The A1 policy function entity performs conflict detection and determines that there is a conflict between the A1 policy 1 and the A1 policy 2.

[0425] Step 129: The A1 policy function entity queries the rApp management function entity for the A1 policy priority corresponding to the A1 policy 1 and the A1 policy 2 of the A1 policy 1 and the A1 policy 2, and learns that the A1 policy priority corresponding to the A1 policy 1 is “3”, and the A1 policy priority corresponding to the A1 policy 2 is “5”.

[0426] The A1 policy function entity determines that the arbitration result is that the execution priority of the A1 policy 2 is lower than that of the A1 policy 1.

[0427] Step 1210: Send a response to the rApp 2 that the creation of the A1 policy 2 fails.

[0428] Embodiment 8: Conflict arbitration based on preemption flag and / or preemption protection;

[0429] In this embodiment, the first entity directly queries the preemption flag and / or preemption protection corresponding to the A1 policy from the second entity. Specifically, during the A1 policy creation and / or update process, the first entity first performs conflict detection. If a configuration and / or policy conflict is detected, the first entity directly queries the preemption flag and / or preemption protection corresponding to the A1 policy from the second entity, and performs a conflict arbitration process to determine the execution order of the A1 policy in conflict, as shown in Figure 13 As an example, the first entity is the A1 policy function entity, and the second entity is the rApp management function entity, i.e., the A1 policy function entity directly queries the preemption flag and / or preemption protection corresponding to the rApp from the rApp management function entity. The specific process includes:

[0430] Step 131: rApp1 sends a creation request for A1 policy 1.

[0431] Step 132: The A1 policy function entity performs conflict detection and determines that there is no configuration and / or policy that conflicts with the A1 policy requested to be created by the rApp1.

[0432] Step 133: The A1 policy function entity sends a creation request for A1 policy 1 to the Near-RT RIC.

[0433] Step 134: The Near-RT RIC interacts with the xApp to create A1 policy 1.

[0434] Step 135: After the A1 policy is created successfully, the Near-RT RIC sends a response to the A1 policy function entity that the creation of A1 policy 1 is successful.

[0435] Step 136: The A1 policy function entity sends a response that the creation of A1 policy 1 is successful.

[0436] Step 137: rApp2 sends a creation request for A1 policy 2.

[0437] Step 138: The A1 policy function entity performs conflict detection and determines that there is a conflict between A1 policy 1 and A1 policy 2.

[0438] Step 139: The A1 policy function entity queries the preemption capability (such as: preemption flag and / or preemption protection) of A1 policy 1 and A1 policy 2 from the rApp management function entity, and learns that A1 policy 1 has preemption protection.

[0439] The A1 policy function entity performs conflict arbitration. Since the A1 policy 1 has preemption protection, the A1 policy function entity determines that the execution priority of the A1 policy 2 is lower than that of the A1 policy 1.

[0440] Step 1310: Send a response of A1 policy 2 creation failure to the rApp 2.

[0441] Embodiment 9: Conflict resolution based on retry procedure after preemption failure

[0442] In the A1 policy creation and / or update process, if the rApp sets the NotifyDesitinationURI (i.e., the third identification information) in the A1 policy creation and / or update request, the A1 policy conflicts with other A1 policies during the creation or execution process, and after the A1 policy is rejected and / or execution is aborted, the first entity is responsible for sending a retry notification to the previously rejected rApp, triggering the retry procedure of the rApp, as shown in Figure 14 As an example, the first entity is the A1 policy function entity, and the second entity is the rApp management function entity, which specifically includes:

[0443] Step 141: The rApp 1 queries the configuration information of the A1 policy priority and preemption capability corresponding to the A1 policy 1 through the rApp management function entity, determines that the A1 policy priority range is “3”-“8” (for example, “1” corresponds to the highest priority), and the preemption protection flag is TRUE.

[0444] Step 142: The rApp 1 sends a creation request of the A1 policy 1 to the A1 policy function entity and sets the A1 policy priority to “5” and the preemption protection flag to TRUE.

[0445] Step 143: The A1 policy function entity performs conflict detection and determines that there is no configuration or policy conflicting with the A1 policy 1.

[0446] Step 144: The A1 policy function entity sends a creation request of the A1 policy 1 to the Near-RT RIC.

[0447] Step 145: The Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0448] Step 146: After the A1 policy 1 is created successfully, the Near-RT RIC sends a response of successful creation to the A1 policy function entity.

[0449] Step 147: The A1 policy function entity feeds back a response of successful creation of the A1 policy 1 to the rApp 1.

[0450] Step 148: rApp2 queries the rApp management function entity for the A1 policy priority and pre-emption capability configuration information corresponding to A1 policy 2, and determines that the A1 policy priority range is "2"~"5" (for example, "1" corresponds to the highest priority), and the pre-emption flag is FALSE.

[0451] Step 149: rApp2 sends a creation request for A1 policy 2 to the A1 policy function entity and sets the A1 policy priority to "5" and the pre-emption flag to FALSE.

[0452] Step 1410: The A1 policy function entity performs conflict detection and determines that there is a conflict between A1 policy 1 and A1 policy 2.

[0453] The A1 policy function entity performs conflict arbitration and determines that the A1 policy priority "5" corresponding to A1 policy 2 is equal to the A1 policy priority "5" corresponding to A1 policy 1, and rApp1 has pre-emption protection. Therefore, the A1 policy function entity determines that the arbitration result is that the execution priority of A1 policy 2 is lower than the execution priority of A1 policy 1.

[0454] Step 1411: The A1 policy function entity sends a response of A1 policy 2 creation failure to rApp2.

[0455] Step 1412: rApp1 triggers a deletion process to delete A1 policy 1, and sends a deletion request for A1 policy 1 to the A1 policy function entity.

[0456] Step 1413: The A1 policy function entity sends a deletion request for A1 policy 1 to the Near-RT RIC.

[0457] Step 1414: The Near-RT RIC interacts with the xApp to delete A1 policy 1.

[0458] Step 1415: After A1 policy 1 is successfully deleted, the Near-RT RIC sends a successful deletion response to the A1 policy function entity.

[0459] Step 1416: The A1 policy function entity feeds back a response of A1 policy 1 successful deletion to rApp1.

[0460] Step 1417: Since A1 policy 1 of rApp1 has been deleted, the A1 policy function entity determines that rApp2 allows to retry the A1 policy creation process based on the NotifyDesitinationURI of rApp2, and then the A1 policy function entity sends a retry notification to rApp2, and rApp2 triggers the creation process of A1 policy 2 again.

[0461] Embodiment 10: Conflict resolution based on pre-emption success;

[0462] In the A1 policy creation and / or update process, if the rApp sets the NotifyDesitinationURI (i.e., the third identification information) in the A1 policy creation and / or update request, the A1 policy creation or execution process conflicts with its A1 policy, and after the A1 policy is rejected and / or the execution is aborted, the first entity is responsible for sending a retry notification to the previously rejected rApp, triggering the rApp's retry process, as shown in Figure 15 As an example, taking the first entity as the A1 policy function entity and the second entity as the rApp management function entity, the specific process includes the following steps.

[0463] Step 151: The rApp1 queries the configuration information of the A1 policy priority and preemption capability corresponding to the A1 policy 1 through the rApp management function entity, and determines that the A1 policy priority range is "3"~"8" (for example, "1" corresponds to the highest priority).

[0464] Step 152: The rApp1 sends a creation request of the A1 policy 1 to the A1 policy function entity and sets the A1 policy priority as "5", as well as the retry notification target.

[0465] Step 153: The A1 policy function entity performs conflict detection and determines that there is no configuration or policy conflicting with the A1 policy 1.

[0466] Step 154: The A1 policy function entity sends a creation request of the A1 policy 1 to the Near-RT RIC.

[0467] Step 155: The Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0468] Step 156: After the A1 policy 1 is created successfully, the Near-RT RIC sends a response of the successful creation to the A1 policy function entity.

[0469] Step 157: The A1 policy function entity feeds back a response of the successful creation of the A1 policy 1 to the rApp1.

[0470] Step 158: The rApp2 queries the configuration information of the A1 policy priority and preemption capability corresponding to the A1 policy 2 through the rApp management function entity, and determines that the A1 policy priority range is "2"~"5" (for example, "1" corresponds to the highest priority).

[0471] Step 159: The rApp2 sends a creation request of the A1 policy 2 to the A1 policy function entity and sets the A1 policy priority as "3", as well as the retry notification target.

[0472] Step 1510: The A1 policy function entity performs conflict detection and determines that there is a conflict between the A1 policy 1 and the A1 policy 2.

[0473] The A1 policy function entity performs conflict arbitration and determines that the A1 policy priority "3" corresponding to the A1 policy 2 is greater than the A1 policy priority "5" corresponding to the A1 policy 1. Therefore, the A1 policy function entity determines that the arbitration result is that the execution priority of the A1 policy 2 is higher than the execution priority of the A1 policy 1.

[0474] Processing scheme 1:

[0475] Step 1511: The A1 policy function entity first rejects the creation of the A1 policy 2, that is, sends a creation failure notification to the rApp 2.

[0476] Step 1512: The A1 policy function entity requests the Near-RT RIC to delete the A1 policy 1.

[0477] Step 1513: The Near-RT RIC interacts with the xApp and deletes the A1 policy 1.

[0478] Step 1514: After the A1 policy 1 is successfully deleted, the Near-RT RIC sends a successful deletion response to the A1 policy function entity.

[0479] Step 1515: The A1 policy function entity notifies the rApp 1 that the A1 policy 1 is successfully deleted.

[0480] Step 1516: The A1 policy function entity sends a retry notification to the rApp 2 based on the NotifyDesitinationURI of the rApp 2, and the rApp 2 triggers the creation process of the A1 policy 2 again.

[0481] Processing scheme 2:

[0482] Step 1517: First, keep the creation process of the A1 policy 2.

[0483] Step 1518: The A1 policy function entity requests the Near-RT RIC to delete the A1 policy 1.

[0484] Step 1519: The Near-RT RIC interacts with the xApp and deletes the A1 policy 1.

[0485] Step 1520: After the A1 policy 1 is successfully deleted, the Near-RT RIC sends a successful deletion response to the A1 policy function entity.

[0486] Step 1521: The A1 policy function entity notifies the rApp 1 that the A1 policy 1 is successfully deleted.

[0487] Step 1522: The A1 policy function entity sends a creation request of the A1 policy 1 to the Near-RT RIC, and the Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0488] Embodiment 11: Conflict resolution based on policy merging;

[0489] Figure 16 As shown, the conflict resolution process based on policy merging specifically includes:

[0490] Step 161: The rApp1 queries the configuration information of the A1 policy priority and preemption capability corresponding to the A1 policy 1 through the rApp management function entity, and determines that the A1 policy priority range is “3”-“8” (for example, “1” corresponds to the highest priority).

[0491] Step 162: The rApp1 sends a creation request of the A1 policy 1 to the A1 policy function entity and sets the A1 policy priority to “5”.

[0492] Step 163: The A1 policy function entity performs conflict detection and determines that there is no configuration or policy conflicting with the A1 policy 1.

[0493] Step 164: The A1 policy function entity sends a creation request of the A1 policy 1 to the Near-RT RIC.

[0494] Step 165: The Near-RT RIC interacts with the xApp to create the A1 policy 1.

[0495] Step 166: After the A1 policy 1 is successfully created, the Near-RT RIC sends a response of successful creation to the A1 policy function entity.

[0496] Step 167: The A1 policy function entity feeds back a response of successful creation of the A1 policy 1 to the rApp1.

[0497] Step 168: The rApp2 queries the configuration information of the A1 policy priority and preemption capability corresponding to the A1 policy 2 through the rApp management function entity, and determines that the A1 policy priority range is “2”-“5” (for example, “1” corresponds to the highest priority).

[0498] Step 169: The rApp2 sends a creation request of the A1 policy 2 to the A1 policy function entity and sets the A1 policy priority to “3”.

[0499] Step 1610: The A1 policy function entity performs conflict detection and determines that there is an A1 policy conflict between the A1 policy 1 and the A1 policy 2.

[0500] The A1 policy function entity performs conflict arbitration and determines that the A1 policy priority "3" corresponding to A1 policy 2 is greater than the A1 policy priority "5" corresponding to A1 policy 1. Therefore, the A1 policy function entity determines the arbitration result as follows: the execution priority of A1 policy 2 is higher than the execution priority of A1 policy 1.

[0501] Step 1611: After a conflict is detected, if policy configuration merging is possible, the A1 policy function entity maintains the creation process of the current A1 policy 2 and merges it with the A1 policy 1 previously created by rApp1.

[0502] Step 1612: The A1 policy function entity sends an update message to the Near-RT RIC, notifying the Near-RT RIC of the merged policy through the update message.

[0503] Step 1613: The Near-RT RIC updates the A1 policy 1 by interacting with the xApp.

[0504] Step 1614: The Near-RT RIC sends a response indicating that the A1 policy 1 update is successful to the A1 policy function entity.

[0505] Step 1615: The A1 policy function entity sends a notification of successful creation of A1 policy 2 to rApp2.

[0506] In an embodiment of the present application, configuration and / or policy conflicts based on the A1 policy are detected, and a conflict arbitration mechanism based on the A1 policy priority and / or preemption capability is introduced in Non-RTRIC, as well as conflict resolution mechanisms based on deletion, notification retry, merging, etc., to control the priority and execution order of the A1 policy. This can better implement the network optimization policy executed by the rApp and effectively avoid the occurrence of configuration and / or policy conflicts.

[0507] The above embodiments have introduced the policy management method of the present application. The following embodiments will further illustrate the corresponding policy management device with reference to the accompanying drawings.

[0508] like Figure 17 As shown, this embodiment provides a policy management device, including a memory 171, a transceiver 172, and a processor 173; wherein the memory 171 is used to store computer programs; the transceiver 172 is used to send and receive data under the control of the processor 173; for example, the transceiver 172 is used to receive and send data under the control of the processor 173; the processor 173 is used to read the computer program in the memory 171 and perform the following operations:

[0509] receive first indication information sent by a second entity, and / or receive first indication information sent by an application in a non-real-time radio access network controller (Non-RT RIC);

[0510] perform A1 policy management according to the first indication information.

[0511] The first indication information is used to indicate an execution priority of the A1 policy.

[0512] Optionally, the first entity includes at least one of the following:

[0513] an A1 policy function entity in the Non-RT RIC;

[0514] a near-real-time radio access network controller (Near-RT RIC);

[0515] and / or,

[0516] The second entity includes at least one of the following:

[0517] an application management function entity in the Non-RT RIC;

[0518] an A1 policy function entity in the Non-RT RIC;

[0519] a function entity in the SMO architecture other than the Non-RT RIC.

[0520] Optionally, the first indication information includes at least one of the following:

[0521] an A1 policy priority;

[0522] a priority of at least one policy action corresponding to the A1 policy;

[0523] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0524] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0525] Optionally, the processor 173 is configured to read a computer program in the memory 171 and perform at least one of the following operations:

[0526] receive first request information sent by an application in the Non-RT RIC, and send first query information to the second entity according to the first request information; the first request information is used to request creation and / or update of an A1 policy, and the first query information is used to request provision of an execution priority of the A1 policy;

[0527] send first subscription information to the second entity, wherein the first subscription information is used to subscribe to the execution priority of the A1 policy.

[0528] Optionally, the processor 173 is configured to read a computer program in the memory 171 and perform at least one of the following operations:

[0529] receive second request information sent by the second entity, wherein the second request information is used to request to create and / or update the A1 policy, and the second request information comprises the first indication information;

[0530] receive third request information sent by an application in the Non-RT RIC, wherein the third request information is used to request to create and / or update the A1 policy, and the third request information comprises the first indication information.

[0531] Optionally, the processor 173 is configured to read a computer program in the memory 171 and perform the following operations:

[0532] perform conflict detection on the at least two A1 policies to determine a conflict detection result;

[0533] if the conflict detection result is that there is a conflict between the at least two A1 policies, perform A1 policy management according to the first indication information;

[0534] wherein the first entity determines that there is a conflict between the at least two A1 policies by at least one of the following manners:

[0535] there is overlap between configuration parameters of the at least two A1 policies;

[0536] there is a conflict between policy actions of the at least two A1 policies.

[0537] Optionally, the processor 173 is configured to read a computer program in the memory 171 and perform at least one of the following operations:

[0538] for the A1 policy with the conflict, reject creation and / or update of the A1 policy;

[0539] for the A1 policy with the conflict, suspend creation and / or update of the A1 policy;

[0540] for the A1 policy with the conflict, delete the A1 policy;

[0541] for the A1 policy whose creation and / or update has been rejected or suspended, retry the creation and / or update process of the A1 policy;

[0542] merge the at least two A1 policies in case of a conflict.

[0543] Optionally, in case of a second A1 policy and a first A1 policy requested to be created and / or updated by a first application, the processor 173 is configured to read the computer program in the memory 171 and perform the following operations:

[0544] if it is determined according to the first indication information that the execution priority of the first A1 policy is lower than or equal to the execution priority of the second A1 policy, sending a rejection information to the first application, wherein the rejection information is used to indicate rejection of creation and / or update of the first A1 policy;

[0545] and / or,

[0546] if it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, performing the first A1 policy creation and / or update process.

[0547] Optionally, the processor 173 is configured to read the computer program in the memory 171 and determine the priority relationship between the execution priority of the first A1 policy and the execution priority of the second A1 policy by at least one of the following ways:

[0548] if the A1 policy priority corresponding to the first A1 policy is higher than the A1 policy priority corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy;

[0549] if the A1 policy priority corresponding to the first A1 policy is lower than the A1 policy priority corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy;

[0550] if the A1 policy priority corresponding to the first A1 policy is equal to the A1 policy priority corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy;

[0551] if the first identification information corresponding to the first A1 policy is a first value, and / or the second identification information corresponding to the second A1 policy is a second value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy;

[0552] If the first identification information corresponding to the first A1 policy is a second value, and / or the first identification information corresponding to the second A1 policy is a first value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy.

[0553] If the second identification information corresponding to the first A1 policy is a first value, and / or the second identification information corresponding to the second A1 policy is a second value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy.

[0554] The first identification information being the first value indicates that other A1 policies are allowed to be preempted, and the first identification information being the second value indicates that other A1 policies are not allowed to be preempted. The second identification information being the first value indicates that the first A1 policy is not allowed to be preempted by other A1 policies, and the second identification information being the second value indicates that the first A1 policy is allowed to be preempted by other A1 policies.

[0555] Optionally, the processor 173 is configured to read the computer program in the memory 171 to further perform the following operation:

[0556] receive first deletion request information sent by a second application program; the first deletion request information is used to request deletion of the second A1 policy;

[0557] send the first deletion request information to a Near-RT RIC;

[0558] receive feedback information sent by the Near-RT RIC;

[0559] in a case where the feedback information indicates that the second A1 policy is successfully deleted, send retry information to the first application program; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 policy.

[0560] Optionally, the processor 173 is configured to read the computer program in the memory 171 to further perform the following operation:

[0561] receive first deletion request information sent by a second application program; the first deletion request information is used to request deletion of the second A1 policy;

[0562] delete the second A1 policy, and send retry information to the first application program; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 policy.

[0563] Optionally, the processor 173 is configured to read the computer program in the memory 171 and perform the following operations:

[0564] sending the rejection information to the first application, and sending second deletion request information to the Near-RT RIC; the second deletion request information is used to request deletion of the second A1 policy;

[0565] receiving feedback information sent by the Near-RT RIC;

[0566] in a case where the feedback information indicates that the second A1 policy is successfully deleted, sending retry information to the first application; the retry information is used to instruct the first application to retry the first A1 policy creation and / or update process.

[0567] Optionally, the processor 173 is configured to read the computer program in the memory 171 and perform the following operations:

[0568] receiving third identification information sent by the first application; the third identification information is used to indicate whether the first application allows retry of A1 policy execution;

[0569] sending retry information to the first application, including:

[0570] in a case where the third identification information indicates that the first application allows retry of A1 policy execution, sending the retry information to the first application.

[0571] Optionally, the processor 173 is configured to read the computer program in the memory 171 and perform the following operations:

[0572] sending second deletion request information to the Near-RT RIC; the second deletion request information is used to request deletion of the second A1 policy;

[0573] receiving feedback information sent by the Near-RT RIC;

[0574] in a case where the feedback information indicates that the second A1 policy is successfully deleted, performing the first A1 policy creation and / or update process.

[0575] wherein, in a case where the feedback information indicates that the second A1 policy is successfully deleted, Figure 17In particular embodiments, the bus architecture can include any number of interconnecting buses and bridges, depending on the specific application of the processor 173 and the memory 171 represented by the various circuits linked thereto. The bus architecture can also include various other circuits, such as peripheral device circuits, voltage regulators, power management circuits, and the like, which are well-known in the art, thus, further description of these other circuits is not required here. The bus interface provides an interface to the transceiver 172. The transceiver 172 can be a plurality of elements, including a transmitter and a receiver, which provides a means for communicating with various other apparatus over a transmission medium, including a wireless channel, a wired channel, optical cable, and the like.

[0576] The processor 173 is responsible for managing the bus architecture and general processing, and the memory 171 can store data used by the processor 173 in executing operations.

[0577] Optionally, the processor 173 can be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.

[0578] The processor executes any of the methods provided by the embodiments of the present application by invoking computer program stored in the memory. The processor and the memory can also be physically arranged separately.

[0579] It should be noted that the above policy management apparatus provided by the embodiments of the present application can implement all the method steps achieved by the first entity side policy management method embodiments and achieve the same technical effects, and thus, the same parts and beneficial effects of the method embodiments are not described in detail here.

[0580] As shown in Figure 18 The embodiments of the present application provide a policy management apparatus 1800, which comprises:

[0581] A first receiving unit 1810 is configured to receive first indication information sent by a second entity, and / or receive first indication information sent by an application program in a non-real-time radio access network controller (Non-RT RIC);

[0582] A processing unit 1820 is configured to perform A1 policy management according to the first indication information.

[0583] The first indication information is used to indicate the execution priority of the A1 policy.

[0584] Optionally, the first entity includes at least one of the following:

[0585] A1 strategy functional entity in Non-RT RIC;

[0586] Near-RT RIC (Near Real-Time Radio Access Network Controller)

[0587] and / or,

[0588] The second entity includes at least one of the following:

[0589] Application management functional entity in Non-RT RIC;

[0590] A1 strategy functional entity in Non-RT RIC;

[0591] Functional entities in the SMO architecture except Non-RT RIC.

[0592] Optionally, the first indication information includes at least one of the following:

[0593] A1 strategy priority;

[0594] The priority of at least one policy action corresponding to the A1 policy;

[0595] The first identification information corresponding to the A1 policy is used to indicate whether the A1 policy is allowed to preempt the execution of other A1 policies;

[0596] The second identification information corresponding to the A1 policy is used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies.

[0597] Optionally, the policy management device 1800 further includes at least one of the following:

[0598] A second receiving unit is configured to receive a first request message sent by an application in the non-RT RIC, and send a first query message to the second entity based on the first request message; wherein the first request message is used to request creation and / or update of an A1 policy, and the first query message is used to request provision of an execution priority of the A1 policy;

[0599] The first sending unit is configured to send first subscription information to the second entity; wherein the first subscription information is used to subscribe to the execution priority of the A1 policy.

[0600] Optionally, the first receiving unit 1810 is further configured to perform at least one of the following:

[0601] receive second request information sent by the second entity; wherein the second request information is used to request creation and / or update of the A1 policy, and the second request information comprises the first indication information;

[0602] receive third request information sent by an application in the Non-RT RIC; wherein the third request information is used to request creation and / or update of the A1 policy, and the third request information comprises the first indication information.

[0603] Optionally, the processing unit 1820 is further configured to:

[0604] perform conflict detection on the at least two A1 policies to obtain a conflict detection result;

[0605] if the conflict detection result indicates that there is a conflict between the at least two A1 policies, perform A1 policy management according to the first indication information.

[0606] The first entity determines that there is a conflict between the at least two A1 policies by at least one of the following manners:

[0607] configuration parameters of the at least two A1 policies overlap;

[0608] policy actions of the at least two A1 policies conflict.

[0609] Optionally, the performing A1 policy management comprises at least one of the following:

[0610] rejecting creation and / or update of an A1 policy that has a conflict;

[0611] suspending creation and / or update of an A1 policy that has a conflict;

[0612] deleting an A1 policy that has a conflict;

[0613] retrying creation and / or update of an A1 policy that has been rejected or suspended from creation and / or update;

[0614] merging the at least two A1 policies that have a conflict.

[0615] Optionally, in the case of a second A1 policy and a first A1 policy requested to be created and / or updated by a first application, the processing unit 1820 is further configured to:

[0616] If it is determined according to the first indication information that the execution priority of the first A1 policy is lower than or equal to the execution priority of the second A1 policy, sending a rejection message to the first application; wherein the rejection message is used to indicate a rejection of creating and / or updating the first A1 policy;

[0617] and / or,

[0618] If it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, the first A1 policy creation and / or update process is executed.

[0619] Optionally, the processing unit 1820 determines the priority relationship between the execution priority of the first A1 policy and the execution priority of the second A1 policy by at least one of the following methods:

[0620] If the A1 policy priority corresponding to the first A1 policy is higher than the A1 policy priority corresponding to the second A1 policy, determining that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy;

[0621] If the A1 policy priority corresponding to the first A1 policy is lower than the A1 policy priority corresponding to the second A1 policy, determining that the priority relationship is that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy;

[0622] If the A1 policy priority corresponding to the first A1 policy is equal to the A1 policy priority corresponding to the second A1 policy, determining that the priority relationship is that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy;

[0623] If the first identification information corresponding to the first A1 policy is a first value, and / or the first identification information corresponding to the second A1 policy is a second value, determining that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy;

[0624] If the first identification information corresponding to the first A1 policy is the second value, and / or the first identification information corresponding to the second A1 policy is the first value, determining that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy;

[0625] If the second identification information corresponding to the first A1 policy is a first value, and / or the second identification information corresponding to the second A1 policy is a second value, determining that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy;

[0626] The first identification information is a first value for indicating that execution of other A1 strategies is allowed to be preempted, and the first identification information is a second value for indicating that execution of other A1 strategies is not allowed to be preempted; the second identification information is a first value for indicating that the second A1 strategy is not allowed to be preempted by other A1 strategies, and the second identification information is a second value for indicating that the second A1 strategy is allowed to be preempted by other A1 strategies.

[0627] Optionally, the policy management apparatus 1800 further includes:

[0628] a third receiving unit, configured to receive first deletion request information sent by a second application program; the first deletion request information is used to request deletion of the second A1 strategy;

[0629] a second sending unit, configured to send the first deletion request information to a Near-RT RIC;

[0630] a fourth receiving unit, configured to receive feedback information sent by the Near-RT RIC;

[0631] a third sending unit, configured to send retry information to the first application program in a case where the feedback information indicates that the second A1 strategy is successfully deleted; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 strategy.

[0632] Optionally, the policy management apparatus 1800 further includes:

[0633] a fifth receiving unit, configured to receive first deletion request information sent by a second application program; the first deletion request information is used to request deletion of the second A1 strategy;

[0634] a deletion unit, configured to delete the second A1 strategy;

[0635] a fourth sending unit, configured to send retry information to the first application program; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 strategy.

[0636] Optionally, the processing unit 1820 is further configured to:

[0637] a fifth sending unit, configured to send the rejection information to the first application program, and send second deletion request information to a Near-RT RIC; the second deletion request information is used to request deletion of the second A1 strategy;

[0638] a sixth receiving unit, configured to receive feedback information sent by the Near-RT RIC;

[0639] The sixth sending unit is configured to send retry information to the first application program in a case where the feedback information indicates that the second A1 policy is successfully deleted; wherein the retry information is used to instruct the first application program to retry the creation and / or update process of the first A1 policy.

[0640] Optionally, the policy management apparatus 1800 further includes:

[0641] The seventh receiving unit is configured to receive third identification information sent by the first application program; wherein the third identification information is used to indicate whether the first application program allows retry of A1 policy execution.

[0642] The third sending unit, the fourth sending unit and the sixth sending unit are further configured to send retry information to the first application program in a case where the third identification information indicates that the first application program allows retry of A1 policy execution.

[0643] Optionally, the processing unit 1820 is further configured to:

[0644] send second deletion request information to the Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy;

[0645] receive feedback information sent by the Near-RT RIC;

[0646] execute the creation and / or update process of the first A1 policy in a case where the feedback information indicates that the second A1 policy is successfully deleted.

[0647] It should be noted that the above policy management apparatus provided by the embodiments of the present application can realize all the method steps achieved by the first entity side policy management method embodiments, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail herein.

[0648] As shown in Figure 19 The embodiments of the present application provide a policy management apparatus, which includes a memory 191, a transceiver 192 and a processor 193; wherein the memory 191 is used to store a computer program; the transceiver 192 is used to transceive data under the control of the processor 193; for example, the transceiver 192 is used to receive and send data under the control of the processor 193; and the processor 193 is used to read the computer program in the memory 191 and perform the following operations:

[0649] send first indication information to a first entity; wherein the first indication information is used to indicate the execution priority of an A1 policy.

[0650] Optionally, the first indication information comprises at least one of the following:

[0651] A1 policy priority;

[0652] A1 policy corresponding to at least one policy action priority;

[0653] A1 policy corresponding to first identification information, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0654] A1 policy corresponding to second identification information, used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies.

[0655] Optionally, the processor 193 is configured to read the computer program in the memory 191 and perform the following operations:

[0656] sending third request information to the first entity; wherein the third request information is used to request creation and / or update of an A1 policy, and the third request information comprises the first indication information.

[0657] Optionally, the processor 193 is configured to read the computer program in the memory 191 and perform the following operations:

[0658] sending second subscription information to a second entity; wherein the second subscription information is used to subscribe to the execution priority of the A1 policy.

[0659] Optionally, the processor 193 is configured to read the computer program in the memory 191 and perform the following operations:

[0660] sending second query information to a second entity; wherein the second query information is used to request to provide the execution priority of the A1 policy;

[0661] receiving response information sent by the second entity; wherein the response information is used to indicate the execution priority supported by the A1 policy.

[0662] Optionally, the processor 193 is configured to read the computer program in the memory 191 and perform at least one of the following operations:

[0663] receiving rejection information sent by the first entity; wherein the rejection information is used to indicate rejection of creation and / or update of the A1 policy;

[0664] receiving retry information sent by the first entity; wherein the retry information is used to indicate that the application retries the creation and / or update process of the A1 policy;

[0665] The third identification information is used to indicate whether the application program allows retry of the A1 policy execution.

[0666] The first deletion request information is used to request deletion of the A1 policy.

[0667] Wherein, in Figure 19 The bus architecture can include any number of interconnected buses and bridges, which link together various circuits, including the one or more processors represented by the processor 193 and the memory represented by the memory 191. The bus architecture can also link together various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and thus will not be further described herein. The bus interface provides an interface. The transceiver 192 can be a plurality of elements, i.e., including a transmitter and a receiver, which provide units for communicating with various other devices on transmission media, including wireless channels, wired channels, optical cables, and the like. The processor 193 is responsible for managing the bus architecture and general processing, and the memory 191 can store data used by the processor 193 in performing operations.

[0668] The processor 193 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD), and the processor can also adopt a multi-core architecture.

[0669] It should be noted that the above policy management device provided by the embodiments of the present application can implement all method steps achieved by the above application program side policy management method embodiments, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail.

[0670] As Figure 20 shown, the embodiments of the present application provide a policy management device 2000, which comprises:

[0671] The first sending unit 2010 is configured to send first indication information to a first entity, wherein the first indication information is used to indicate an execution priority of an A1 policy.

[0672] Optionally, the first indication information comprises at least one of the following:

[0673] A1 policy priority.

[0674] a priority of at least one policy action corresponding to the A1 policy;

[0675] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0676] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0677] Optionally, the first sending unit 2010 is further configured to:

[0678] send third request information to the first entity, wherein the third request information is used to request creation and / or update of the A1 policy, and the third request information comprises the first indication information.

[0679] Optionally, the policy management apparatus 2000 further comprises:

[0680] a second sending unit, configured to send second subscription information to a second entity, wherein the second subscription information is used to subscribe to an execution priority of the A1 policy.

[0681] Optionally, the policy management apparatus 2000 further comprises:

[0682] a third sending unit, configured to send second query information to the second entity, wherein the second query information is used to request provision of the execution priority of the A1 policy.

[0683] the application program in the Non-RT RIC receives response information sent by the second entity, wherein the response information is used to indicate the execution priority supported by the A1 policy.

[0684] Optionally, the policy management apparatus 2000 further comprises at least one of:

[0685] a first receiving unit, configured to receive rejection information sent by the first entity, wherein the rejection information is used to indicate rejection of creation and / or update of the A1 policy;

[0686] a second receiving unit, configured to receive retry information sent by the first entity, wherein the retry information is used to instruct the application program to retry the creation and / or update process of the A1 policy;

[0687] a fourth sending unit, configured to send third identification information to the first entity, wherein the third identification information is used to indicate whether the application program is allowed to retry execution of the A1 policy;

[0688] A fifth sending unit is configured to send first deletion request information to the first entity, wherein the first deletion request information is used to request deletion of the A1 policy.

[0689] It should be noted that the policy management apparatus provided in the embodiments of the present application can realize all the method steps achieved by the application-side policy management method embodiments and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments are not described in detail herein.

[0690] As shown in Figure 21 The embodiments of the present application provide a policy management apparatus, which comprises a memory 211, a transceiver 212, and a processor 213. The memory 211 is configured to store a computer program. The transceiver 212 is configured to transceive data under the control of the processor 213. The processor 213 is configured to read the computer program in the memory 211 and perform the following operations:

[0691] sending first indication information to the first entity and / or sending the first indication information to an application in a Non-Real-Time Radio Access Network Controller (Non-RT RIC);

[0692] The first indication information is used to indicate the execution priority of the A1 policy.

[0693] Optionally, the first indication information comprises at least one of the following:

[0694] A1 policy priority;

[0695] A1 policy corresponding to at least one policy action priority;

[0696] A1 policy corresponding to first identification information, which is used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0697] A1 policy corresponding to second identification information, which is used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies.

[0698] Optionally, the processor 213 is further configured to read the computer program in the memory 211 and perform the following operations:

[0699] receiving first query information sent by the first entity and / or receiving second query information sent by the application in the Non-RT RIC, wherein the first query information and / or the second query information is used to request to provide the execution priority of the A1 policy;

[0700] The first indication information is sent to the first entity according to the first query information, and / or response information of the second query information is sent to an application program in the Non-RT RIC, wherein the response information is used to indicate an execution priority supported by the A1 policy.

[0701] Optionally, the processor 213 is configured to read the computer program in the memory 211 to further perform the following operations:

[0702] The first subscription information sent by the first entity is received, wherein the subscription information is used to subscribe to an execution priority of an A1 policy.

[0703] And / or,

[0704] The second subscription information sent by the application program in the Non-RT RIC is received, wherein the second subscription information is used to subscribe to an execution priority of an A1 policy.

[0705] In the above Figure 21 The bus architecture can include any number of interconnecting buses and bridges, depending on the specific application of the processor 213 and the various circuits represented by the memory 211. The bus architecture can also include various other circuits, such as peripheral devices, voltage stabilizers and power management circuits, which are well known in the art and will not be described further. The bus interface provides an interface. The transceiver 212 can be a plurality of elements, including a transmitter and a receiver, which provide units for communicating with various other devices on transmission media, including wireless channels, wired channels, optical cables, and the like. The processor 213 is responsible for managing the bus architecture and general processing, and the memory 211 can store data used by the processor 213 in performing operations.

[0706] The processor 213 can be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0707] It should be noted that the above policy management device provided by the embodiments of the present application can realize all the method steps realized by the above-mentioned second entity side policy management method embodiments, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail.

[0708] As Figure 22 shown, an embodiment of the present application provides a policy management apparatus 2200, comprising:

[0709] a sending unit 2210 configured to send first indication information to a first entity, and / or send the first indication information to an application in a Non-RT RIC (Non-Real-Time Radio Controller);

[0710] wherein the first indication information is used to indicate an execution priority of an A1 policy.

[0711] Optionally, the first indication information comprises at least one of the following:

[0712] an A1 policy priority;

[0713] a priority of at least one policy action corresponding to the A1 policy;

[0714] first identification information corresponding to the A1 policy, used to indicate whether the A1 policy allows preemption of execution of other A1 policies;

[0715] second identification information corresponding to the A1 policy, used to indicate whether execution of the A1 policy is allowed to be preempted by other A1 policies.

[0716] Optionally, the sending unit 2210 is further configured to:

[0717] receive first query information sent by the first entity, and / or receive second query information sent by an application in the Non-RT RIC; wherein the first query information and / or the second query information is used to request to provide an execution priority of an A1 policy;

[0718] send the first indication information to the first entity according to the first query information; and / or send response information of the second query information to at least one application in the Non-RT RIC; wherein the response information is used to indicate an execution priority supported by the A1 policy.

[0719] Optionally, the policy management apparatus 2200 further comprises:

[0720] a first receiving unit configured to receive first subscription information sent by the first entity; wherein the subscription information is used to subscribe to an execution priority of an A1 policy;

[0721] and / or,

[0722] The second receiving unit is configured to receive second subscription information sent by at least one application program in the Non-RT RIC, wherein the second subscription information is used to subscribe to an execution priority of the A1 policy.

[0723] It should be noted that the above policy management apparatus provided by the embodiments of the present application can realize all the method steps achieved by the second entity side policy management method embodiment, and achieve the same technical effects. Therefore, the same parts and beneficial effects of the method embodiments will not be described in detail herein.

[0724] It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, another division mode can be used. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0725] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solutions of the present application, essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0726] The embodiments of the present application also provide a processor-readable storage medium, which stores a computer program. The computer program is used to make the processor execute the steps of the above policy management method, and can achieve the same technical effects. To avoid repetition, details will not be described herein.

[0727] The embodiments of the present application also provide a computer program product, which includes computer instructions. When the computer instructions are executed by a processor, the various processes of the above policy management method embodiments are realized, and the same technical effects can be achieved. To avoid repetition, details will not be described herein.

[0728] The processor-readable storage media can be any available media or data storage device that can be accessed by a processor including, but not limited to, magnetic storage devices (e.g., floppy disks, hard disks, tape, etc.), optical storage devices (e.g., CD-ROMs, DVDs, BDs, HVDs, etc.), semiconductor memory devices (e.g., ROMs, EPROMs, EEPROMs, NAND FLASH, solid state drives (SSDs), etc.), and the like.

[0729] Those skilled in the art will appreciate that embodiments of the present application can be supplied as a method, a system, or a computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, magnetic disks and optical storage media) embodying computer program code, or the like.

[0730] The present application is described in reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present application. It will be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general purpose computer, a special purpose computer, an embedded processor, or a Figure 1 one or more flows and / or blocks Figure 1 means for performing the function specified by one or more blocks

[0731] These processor-executable instructions can also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instructions means which implement the function specified by the flow Figure 1 one or more flows and / or blocks Figure 1 means for performing the function specified by one or more blocks

[0732] These processor-executable instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions executed on the computer or other programmable apparatus provide steps for implementing the function specified by the flow Figure 1 one or more flows and / or blocks Figure 1 means for performing the function specified by one or more blocks

[0733] In addition, it should be noted that, in the apparatus and method of the present application, it is obvious that each component or each step can be decomposed and / or recombined. These decompositions and / or recombinations should be regarded as equivalent schemes of the present application. Moreover, the steps of performing the above-mentioned series of processes can naturally be performed in chronological order according to the order of description, but do not necessarily need to be performed in chronological order, and some steps can be performed in parallel or independently of each other. For those of ordinary skill in the art, it will be understood that all or any steps or components of the method and apparatus of the present application can be implemented in any computing device (including processors, storage media, etc.) or a network of computing devices with hardware, firmware, software or a combination thereof, which can be achieved by those of ordinary skill in the art using their basic programming skills after reading the description of the present application.

[0734] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A policy management method characterized by, Comprise: A first entity receives first indication information sent by a second entity, and / or receives first indication information sent by an application in a non-real-time radio access network controller (Non-RT RIC); The first entity performs A1 policy management according to the first indication information; Wherein, the first indication information is used to indicate the execution priority of A1 policy.

2. The policy management method of claim 1, wherein, The first entity comprises one of the following: A1 policy function entity in Non-RT RIC; Near real-time radio access network controller (Near-RT RIC); And / or, The second entity comprises one of the following: Application management function entity in Non-RT RIC; A1 policy function entity in Non-RT RIC; Function entity in SMO architecture except Non-RT RIC.

3. The policy management method of claim 1, wherein, The first indication information comprises at least one of the following: A1 policy priority; The priority of at least one policy action corresponding to A1 policy; First identification information corresponding to A1 policy, used to indicate whether A1 policy allows preemption of execution of other A1 policies; Second identification information corresponding to A1 policy, used to indicate whether the execution of A1 policy is allowed to be preempted by other A1 policies.

4. The policy management method of claim 1, wherein, Before the first entity receives the first indication information sent by the second entity, it further comprises at least one of the following: The first entity receives first request information sent by the application in Non-RT RIC, and sends first query information to the second entity according to the first request information; wherein, the first request information is used to request to create and / or update A1 policy, and the first query information is used to request to provide the execution priority of A1 policy; The first entity sends first subscription information to the second entity; wherein, the first subscription information is used to subscribe to the execution priority of A1 policy.

5. The policy management method according to claim 1 or 4, characterized by, The first entity receives the first indication information sent by the second entity, and / or receives the first indication information sent by the application in the Non-RT RIC, which comprises at least one of the following: The first entity receives second request information sent by the second entity; wherein, the second request information is used to request to create and / or update A1 policy, and the second request information comprises the first indication information; The first entity receives third request information sent by the application in Non-RT RIC; wherein, the third request information is used to request to create and / or update A1 policy, and the third request information comprises the first indication information.

6. The policy management method of claim 1, wherein, The first entity performs A1 policy management according to the first indication information, which comprises: The first entity performs conflict detection on at least two A1 policies to determine conflict detection results; If the conflict detection result is that there is conflict between the at least two A1 policies, the first entity performs A1 policy management according to the first indication information; Wherein, the first entity determines that there is conflict between the at least two A1 policies by at least one of the following ways: There is overlap between configuration parameters of at least two A1 policies; There is a conflict between policy actions of at least two A1 policies.

7. The policy management method according to any one of claims 1 to 6, characterized by, The A1 policy management performed by the first entity comprises at least one of: rejecting creation and / or update of the A1 policy in case of conflict; suspending creation and / or update of the A1 policy in case of conflict; deleting the A1 policy in case of conflict; retrying the creation and / or update process of the A1 policy in case of the A1 policy whose creation and / or update has been rejected or suspended; merging at least two A1 policies in case of conflict.

8. The policy management method of claim 7, wherein, In a case where a second A1 policy conflicts with a first A1 policy requested to be created and / or updated by a first application, the first entity performs A1 policy management according to the first indication information, comprising: if it is determined according to the first indication information that the execution priority of the first A1 policy is lower than or equal to that of the second A1 policy, the first entity sends rejection information to the first application, wherein the rejection information is used to indicate rejection of creation and / or update of the first A1 policy; and / or, if it is determined according to the first indication information that the execution priority of the first A1 policy is higher than that of the second A1 policy, the first entity performs the creation and / or update process of the first A1 policy.

9. The policy management method of claim 8, wherein, The first entity determines the priority relationship between the execution priority of the first A1 policy and that of the second A1 policy by at least one of the following manners: if the A1 policy priority corresponding to the first A1 policy is higher than that corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than that of the second A1 policy; if the A1 policy priority corresponding to the first A1 policy is lower than that corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is lower than that of the second A1 policy; if the A1 policy priority corresponding to the first A1 policy is equal to that corresponding to the second A1 policy, it is determined that the priority relationship is that the execution priority of the first A1 policy is lower than that of the second A1 policy; if the first identification information corresponding to the first A1 policy is a first value, and / or the second identification information corresponding to the second A1 policy is a second value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than that of the second A1 policy; if the first identification information corresponding to the first A1 policy is the second value, and / or the second identification information corresponding to the second A1 policy is the first value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than that of the second A1 policy; If the second identification information corresponding to the first A1 policy is a first value, and / or the second identification information corresponding to the second A1 policy is a second value, it is determined that the priority relationship is that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy. The first identification information is a first value, which is used to indicate that the execution of other A1 policies is allowed to be preempted, and the first identification information is a second value, which is used to indicate that the execution of other A1 policies is not allowed to be preempted. The second identification information is a first value, which is used to indicate that the second A1 policy is not allowed to be preempted by other A1 policies, and the second identification information is a second value, which is used to indicate that the second A1 policy is allowed to be preempted by other A1 policies.

10. The policy management method of claim 8, wherein, After the first entity sends the rejection information to the first application program, the method further includes: The first entity receives first deletion request information sent by a second application program; the first deletion request information is used to request deletion of the second A1 policy; The first entity sends the first deletion request information to a Near-RT RIC; The first entity receives feedback information sent by the Near-RT RIC; In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity sends retry information to the first application program; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 policy.

11. The policy management method of claim 8, wherein, After the first entity sends the rejection information to the first application program, the method further includes: The first entity receives first deletion request information sent by a second application program; the first deletion request information is used to request deletion of the second A1 policy; The first entity deletes the second A1 policy, and sends retry information to the first application program; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 policy.

12. The policy management method of claim 8, wherein, The first entity performs the creation and / or update process of the first A1 policy, including: The first entity sends the rejection information to the first application program, and sends second deletion request information to a Near-RT RIC; the second deletion request information is used to request deletion of the second A1 policy; The first entity receives feedback information sent by the Near-RT RIC; In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity sends retry information to the first application program; the retry information is used to instruct the first application program to retry a creation and / or update process of the first A1 policy.

13. The policy management method according to any one of claims 10 to 12, characterized by, Before the first entity sends the retry information to the first application program, the method further includes: The first entity receives third identification information sent by the first application program; the third identification information is used to indicate whether the first application program allows retrying A1 policy execution; The first entity sends the retry information to the first application program, including: In a case where the third identification information indicates that the first application program allows the retry A1 policy execution, the first entity sends the retry information to the first application program.

14. The policy management method of claim 10, wherein, The first entity performs a creation and / or update process of the first A1 policy, including: The first entity sends second deletion request information to the Near-RT RIC; wherein the second deletion request information is used to request to delete the second A1 policy; The first entity receives feedback information sent by the Near-RT RIC; In a case where the feedback information indicates that the second A1 policy is successfully deleted, the first entity performs the creation and / or update process of the first A1 policy.

15. A policy management method characterized by, Including: An application in a non-real-time radio access network controller Non-RT RIC sends first indication information to a first entity; wherein the first indication information is used to indicate an execution priority of an A1 policy.

16. The policy management method of claim 15, wherein, The first indication information includes at least one of the following: A1 policy priority; A1 policy corresponding to at least one priority of a policy action; A1 policy corresponding to first identification information, used to indicate whether the A1 policy allows to preempt the execution of other A1 policies; A1 policy corresponding to second identification information, used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies.

17. The policy management method of claim 15, wherein, The application in the non-real-time radio access network controller Non-RT RIC sends first indication information to a first entity, including: The application in the Non-RT RIC sends third request information to the first entity; wherein the third request information is used to request to create and / or update an A1 policy, and the third request information includes the first indication information.

18. The policy management method of any of claims 15-17, wherein, Before the application in the non-real-time radio access network controller Non-RT RIC sends the first indication information to the first entity, further including: The application in the Non-RT RIC sends second subscription information to a second entity; wherein the second subscription information is used to subscribe to the execution priority of the A1 policy.

19. The policy management method of any of claims 15-17, wherein, Before the application in the non-real-time radio access network controller Non-RT RIC sends the first indication information to the first entity, further including: The application in the Non-RT RIC sends second query information to a second entity; wherein the second query information is used to request to provide the execution priority of the A1 policy; The application in the Non-RT RIC receives response information sent by the second entity; wherein the response information is used to indicate the execution priority supported by the A1 policy.

20. The policy management method of claim 17, wherein, Further including at least one of the following: The application in the Non-RT RIC receives rejection information sent by the first entity; wherein the rejection information is used to indicate to reject to create and / or update the A1 policy; The application in the Non-RT RIC receives retry information sent by the first entity; wherein the retry information is used to indicate that the application retries the creation and / or update process of the A1 policy; The application in the Non-RT RIC sends third identification information to the first entity; wherein the third identification information is used to indicate whether the application allows retry A1 policy execution; The application in the Non-RT RIC sends first deletion request information to the first entity; wherein the first deletion request information is used to request deletion of A1 policy.

21. A policy management method, characterized by, Comprise: The second entity sends first indication information to the first entity, and / or sends first indication information to the application in the Non-Real-Time Radio Access Network Controller Non-RT RIC; Wherein, the first indication information is used to indicate the execution priority of A1 policy.

22. The policy management method of claim 21, wherein, The first indication information comprises at least one of the following: A1 policy priority; The priority of at least one policy action corresponding to A1 policy; The first identification information corresponding to A1 policy is used to indicate whether the A1 policy allows preemption of execution of other A1 policies; The second identification information corresponding to A1 policy is used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies.

23. The policy management method of claim 21, wherein, The second entity sends first indication information to the first entity, and / or sends first indication information to the application in the Non-Real-Time Radio Access Network Controller Non-RT RIC, comprising: The second entity receives first query information sent by the first entity, and / or receives second query information sent by the application in the Non-RT RIC; wherein the first query information and / or the second query information is used to request to provide the execution priority of A1 policy; The second entity sends the first indication information to the first entity according to the first query information; and / or sends response information to the application in response to the second query information; wherein the response information is used to indicate the execution priority supported by A1 policy.

24. The policy management method of claim 21, wherein, Before the second entity sends first indication information to the first entity, and / or sends first indication information to the application in the Non-Real-Time Radio Access Network Controller Non-RT RIC, it further comprises: The second entity receives first subscription information sent by the first entity; wherein the subscription information is used to subscribe to the execution priority of A1 policy; And / or, The second entity receives second subscription information sent by the application in the Non-RT RIC; wherein the second subscription information is used to subscribe to the execution priority of A1 policy.

25. A policy management apparatus, characterized by comprising: Comprise memory, transceiver, processor; Wherein, the memory is used to store computer programs; the transceiver is used to transceive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Receive first indication information sent by the second entity, and / or receive first indication information sent by the application in the Non-Real-Time Radio Access Network Controller Non-RT RIC; According to the first indication information, execute A1 policy management; Wherein, the first indication information is used to indicate the execution priority of A1 policy.

26. The policy management apparatus of claim 25, wherein, The first indication information comprises at least one of the following: A1 policy priority; The priority of at least one policy action corresponding to A1 policy; The first identification information corresponding to the A1 policy is used to indicate whether the A1 policy allows preemption of execution of other A1 policies. The second identification information corresponding to the A1 policy is used to indicate whether the execution of the A1 policy is allowed to be preempted by other A1 policies.

27. The policy management apparatus according to claim 25 or 26, wherein, The execution A1 policy management includes at least one of the following: For the A1 policy with the conflict, the creation and / or update of the A1 policy is rejected; For the A1 policy with the conflict, the creation and / or update of the A1 policy is suspended; For the A1 policy with the conflict, the A1 policy is deleted; For the A1 policy whose creation and / or update has been rejected or suspended, the creation and / or update process of the A1 policy is retried; For at least two A1 policies with conflicts, the at least two A1 policies are merged.

28. The policy management apparatus of claim 27, wherein, In the case of a second A1 policy and a first A1 policy requested to be created and / or updated by a first application, the processor is configured to read the computer program in the memory and perform the following operations: If it is determined according to the first indication information that the execution priority of the first A1 policy is lower than the execution priority of the second A1 policy, a rejection information is sent to the first application; wherein the rejection information is used to indicate that the creation and / or update of the first A1 policy is rejected; And / or, If it is determined according to the first indication information that the execution priority of the first A1 policy is higher than the execution priority of the second A1 policy, a creation and / or update process of the first A1 policy is performed.

29. The policy management apparatus of claim 28, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Receive first deletion request information sent by a second application; wherein the first deletion request information is used to request deletion of the second A1 policy; Send the first deletion request information to a Near-RT RIC (Near-Real Time Radio Access Controller); Receive feedback information sent by the Near-RT RIC; In the case where the feedback information indicates that the second A1 policy is successfully deleted, retry information is sent to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

30. The policy management apparatus of claim 28, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Receive first deletion request information sent by a second application; wherein the first deletion request information is used to request deletion of the second A1 policy; Delete the second A1 policy, and send retry information to the first application; wherein the retry information is used to instruct the first application to retry the creation and / or update process of the first A1 policy.

31. The policy management apparatus of claim 28, wherein, The processor is configured to read the computer program in the memory and perform the following operations: Send the rejection information to the first application, and send second deletion request information to a Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy; Receive feedback information sent by the Near-RT RIC; In a case where the feedback information indicates that the second A1 policy is successfully deleted, retry information is sent to the first application program; wherein the retry information is used to instruct the first application program to retry the creation and / or update process of the first A1 policy.

32. The policy management apparatus according to any one of claims 29 to 31, wherein, The processor is configured to read a computer program in the memory and perform the following operations: receiving third identification information sent by the first application program; wherein the third identification information is used to indicate whether the first application program allows retry of A1 policy execution; sending retry information to the first application program, comprising: in a case where the third identification information indicates that the first application program allows retry of A1 policy execution, sending the retry information to the first application program.

33. The policy management apparatus of claim 29, wherein, The processor is configured to read a computer program in the memory and perform the following operations: sending second deletion request information to the Near-RT RIC; wherein the second deletion request information is used to request deletion of the second A1 policy; receiving feedback information sent by the Near-RT RIC; in a case where the feedback information indicates that the second A1 policy is successfully deleted, performing the creation and / or update process of the first A1 policy.

34. A policy management apparatus, characterized by comprising: comprising: a first receiving unit, configured to receive first indication information sent by a second entity, and / or receive first indication information sent by an application program in a Non-Real-Time Radio Access Network Controller (Non-RT RIC); a processing unit, configured to perform A1 policy management according to the first indication information. The first indication information is used to indicate an execution priority of an A1 policy.

35. A policy management apparatus, characterized by comprising: comprising a memory, a transceiver, and a processor; The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations: sending first indication information to a first entity; wherein the first indication information is used to indicate an execution priority of an A1 policy.

36. A policy management apparatus, characterized by comprising: comprising: a first sending unit, configured to send first indication information to a first entity; wherein the first indication information is used to indicate an execution priority of an A1 policy.

37. A policy management apparatus, characterized by comprising: comprising a memory, a transceiver, and a processor; The memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; and the processor is configured to read the computer program in the memory and perform the following operations: sending first indication information to a first entity, and / or sending first indication information to an application program in a Non-Real-Time Radio Access Network Controller (Non-RT RIC); The first indication information is used to indicate an execution priority of an A1 policy.

38. A policy management apparatus, characterized by comprising: comprising: a sending unit, configured to send first indication information to a first entity, and / or send first indication information to an application program in a Non-Real-Time Radio Access Network Controller (Non-RT RIC); The first indication information is used to indicate an execution priority of an A1 policy.

39. A processor-readable storage medium, comprising: The processor readable storage medium stores a computer program, and the computer program is used to make the processor perform the steps of the policy management method in any one of claims 1 to 24.

40. A computer program product, characterised in that, comprising computer instructions which, when executed by a processor, implement the steps of the policy management method according to any one of claims 1 to 24.

Images