A1 policy creation method, apparatus, device, and storage medium

Abstract

The present application relates to an A1 policy creation method, an apparatus, a device, and a storage medium. The method comprises: a Near-RT RIC receives a policy placement request message sent by a Non-RT RIC, the policy placement request message being used for instructing to create an A1 policy within a first action range and being used for indicating whether to allow the A1 policy to work within part of the first action range; and if the Near-RT RIC has successfully created the A1 policy within part of the first action range and does not successfully create the A1 policy within another part of same, the Near-RT RIC sends to the Non-RT RIC a policy placement response message on the basis of an indication with respect to whether to allow the A1 policy to work within part of the first action range.

Description

A1 policy creation method, device, equipment, and storage medium Cross-references

[0001] This application refers to Chinese Patent Application No. 2024103525537, filed on March 26, 2024, entitled “A1 Policy Creation Method, Apparatus, Equipment and Storage Medium,” which is incorporated herein by reference in its entirety. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to an A1 policy creation method, apparatus, device, and storage medium. Background Art

[0003] In the Open Radio Access Network (O-RAN), the Near-RT RIC (Near Real-Time RAN Intelligent Controller) collects RAN (Radio Access Network) information through the E2 interface and obtains the A1 policy provided by the Non-RT RIC (Non Real-Time RAN Intelligent Controller) through the A1 interface. It then performs intelligent processing based on the A1 policy and RAN information to ultimately derive signaling and policies that guide RAN behavior.

[0004] However, currently, the process of providing A1 policy through the A1 interface is incomplete, affecting the interoperability of Near-RT RIC and Non-RT RIC devices. Summary of the Invention

[0005] Embodiments of the present application provide an A1 policy creation method, apparatus, device, and storage medium.

[0006] In a first aspect, a method for creating an A1 policy is provided, the method comprising:

[0007] A near-real-time radio access network intelligent controller Near-RT RIC receives a policy placement request message sent by a non-real-time radio access network intelligent controller Non-RT RIC, where the policy placement request message is used to indicate the creation of an A1 policy within a first scope of action and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope of action; if the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope of action and fails to successfully create the A1 policy within another partial scope, the Near-RT RIC sends a policy placement response message to the Non-RT RIC based on the indication of whether the A1 policy is allowed to take effect within the partial scope of the first scope of action.

[0008] In one embodiment, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully created the policy within the partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within the partial scope of the first scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executed the policy creation process, and an error occurred in the policy creation process.

[0009] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0010] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0011] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes the policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0012] In one of the embodiments, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0013] In one embodiment, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following:

[0014] The Near-RT RIC determines, based on a match between a capability scope of a built-in xApp and the first scope, multiple first xApps, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one of the multiple initiated RIC subscription processes succeeds, and at least one fails. The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of the built-in xApp and the first scope, wherein a total scope of the at least one RIC subscription process that fails to initiate is smaller than the first scope.

[0015] In a second aspect, an A1 policy creation method is provided, the method comprising:

[0016] The Non-RT RIC sends a policy placement request message to the Near-RT RIC, where the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope of action; and the Non-RT RIC receives a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0017] In one embodiment, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully creates the policy within a partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executes the policy creation process and an error occurs in the policy creation process.

[0018] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0019] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0020] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes the policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0021] In one of the embodiments, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0022] In one embodiment, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following:

[0023] The Near-RT RIC determines, based on a match between a capability scope of a built-in xApp and the first scope, multiple first xApps, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one of the multiple initiated RIC subscription processes succeeds, and at least one fails. The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of the built-in xApp and the first scope, wherein a total scope of the at least one RIC subscription process that fails to initiate is smaller than the first scope.

[0024] In a third aspect, an A1 policy creation device is provided for use in a Near-RT RIC, including:

[0025] a request receiving unit, configured to receive a policy placement request message sent by a Non-RT RIC, wherein the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action;

[0026] a response sending unit, configured to send a policy placement response message to the Non-RT RIC based on an indication of whether to allow the A1 policy to take effect within a portion of the first scope, if the Near-RT RIC successfully creates the A1 policy within a portion of the first scope and fails to successfully create the A1 policy within another portion of the scope.

[0027] In a fourth aspect, an A1 policy creation device is provided for use in a Non-RT RIC, comprising:

[0028] a request sending unit, configured to send a policy placement request message to the Near-RT RIC, wherein the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action;

[0029] A response receiving unit is configured to receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0030] In a fifth aspect, a communication device is provided, including a memory, a transceiver, and a processor:

[0031] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0032] Control the transceiver to receive a policy placement request message sent by a Non-RT RIC, where the policy placement request message is used to indicate creation of an A1 policy within a first scope and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; if the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, control the transceiver to send a policy placement response message to the Non-RT RIC based on the indication of whether the A1 policy is allowed to take effect within the partial scope of the first scope.

[0033] In one embodiment, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully created the policy within the partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within the partial scope of the first scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executed the policy creation process, and an error occurred in the policy creation process.

[0034] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0035] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0036] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes the policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0037] In one of the embodiments, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0038] In one embodiment, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following:

[0039] The Near-RT RIC determines, based on a match between a capability scope of a built-in xApp and the first scope, multiple first xApps, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one of the multiple initiated RIC subscription processes succeeds, and at least one fails. The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of the built-in xApp and the first scope, wherein a total scope of the at least one RIC subscription process that fails to initiate is smaller than the first scope.

[0040] In a sixth aspect, a communication device is provided, including a memory, a transceiver, and a processor:

[0041] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0042] Controlling the transceiver to send a policy placement request message to the Near-RT RIC, where the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action;

[0043] The transceiver is controlled to receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0044] In one embodiment, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully creates the policy within a partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executes the policy creation process and an error occurs in the policy creation process.

[0045] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0046] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0047] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes the policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0048] In one of the embodiments, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0049] In one embodiment, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following:

[0050] The Near-RT RIC determines, based on a match between a capability scope of a built-in xApp and the first scope, multiple first xApps, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one of the multiple initiated RIC subscription processes succeeds, and at least one fails. The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of the built-in xApp and the first scope, wherein a total scope of the at least one RIC subscription process that fails to initiate is smaller than the first scope.

[0051] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect above.

[0052] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the second aspect above.

[0053] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the embodiments below. The accompanying drawings are for illustration purposes only and are not to be considered as limiting the present application. The same reference numerals are used throughout the drawings to denote the same components. In the drawings:

[0055] FIG1 is a schematic diagram of the O-RAN architecture in one embodiment;

[0056] FIG2 is a schematic diagram of a flow chart of an A1 policy creation method according to an embodiment;

[0057] FIG3 is a flow chart of another A1 policy creation method according to an embodiment;

[0058] FIG4 is a flow chart of another A1 policy creation method according to an embodiment;

[0059] FIG5 is a schematic diagram of a flow chart of another A1 policy creation method according to an embodiment;

[0060] FIG6 is a schematic flow chart of another A1 policy creation method according to an embodiment;

[0061] FIG7 is a flow chart of another A1 policy creation method according to an embodiment;

[0062] FIG8 is a flow chart of another A1 policy creation method according to an embodiment;

[0063] FIG9 is a schematic flow chart of another A1 policy creation method according to an embodiment;

[0064] FIG10 is a structural block diagram of an A1 policy creation device according to an embodiment;

[0065] FIG11 is a structural block diagram of another A1 strategy creation device according to one embodiment;

[0066] FIG12 is a diagram showing the internal structure of a communication device in one embodiment. DETAILED DESCRIPTION

[0067] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0068] Endogenous intelligence is a key feature of next-generation mobile wireless networks, such as 6G. This feature emphasizes that AI (Artificial Intelligence) capabilities are inherent in and used by wireless access networks, facilitating the continuous optimization and evolution of wireless access networks and forming intelligent wireless access networks.

[0069] Please refer to Figure 1, which shows an exemplary radio access network architecture with external intelligent features. In the O-RAN (Open Radio Access Network), the Near-RT RIC (Near Real-Time RAN Intelligent Controller) collects RAN (Radio Access Network) information through the E2 interface and obtains the A1 policy (A1-P) provided by the Non-RT RIC (Non Real-Time RAN Intelligent Controller) through the A1 interface. The Near-RT RIC then intelligently processes the RAN information and A1 policy to obtain signaling used to guide RAN behavior (RAN behavior such as configuring radio parameters and mobility events).

[0070] As shown in Figure 1, the Near-RT RIC consists of the Near-RT RIC Platform and the eXtended Application (xApp). Intelligent processing resides in the xApp, which connects the Non-RT RIC and RAN. It forwards intelligent processing inputs (A1 policies, RAN information) from the Non-RT RIC and RAN to the xApp. Based on these inputs, the xApp performs intelligent processing and generates intelligent outputs (such as signaling). The Near-RT RIC Platform then delivers the intelligent outputs to the RAN.

[0071] However, currently, the process of providing A1 policy through the A1 interface is incomplete, affecting the interoperability of Near-RT RIC and Non-RT RIC devices.

[0072] In view of this, an embodiment of the present application provides an A1 policy creation method, which provides a solution for the situation where the Near-RT RIC successfully creates the A1 policy only within a part of the complete scope of the A1 policy, but fails to successfully create the A1 policy within another part, thereby improving the relevant process to a certain extent and improving the device interoperability of Near-RT RIC and Non-RT RIC.

[0073] It should be noted that the beneficial effects or technical problems solved by the embodiments of the present application are not limited to this one, but may also include other implicit or related problems. For details, please refer to the description of the following embodiments.

[0074] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0075] In one embodiment, as shown in FIG2 , an A1 policy creation method is provided, which is described by taking the application of the method to Near-RT RIC as an example, and includes the following steps:

[0076] Step 201: The Near-RT RIC receives a policy placement request message sent by the Non-RT RIC.

[0077] In actual applications, the Non-RT RIC can use the policy creation operation to send the new A1 policy to the Near-RT RIC for execution. The process is described in O-RAN.WG2.A1AP-v04.015.2.4.3.

[0078] In this process, the Non-RT RIC (also called A1-P Consumer) can send a policy placement request message to the Near-RT RIC (also called A1-P Producer). The policy placement request message is called an HTTP PUT Request message in English.

[0079] Among them, the Uniform Resource Identifier (URI) of the policy placement request message can be "… / policytypes / {policyTypeId} / policies / {policyId}", and the message body of the policy placement request message includes a policy object information element (PolicyObject) to instruct the Near-RT RIC to create an A1 policy with a type of policyTypeId, an identifier of policyId, and a description information recorded in PolicyObject.

[0080] As described in O-RAN.WG2.A1TD-v07.006.4.1, the structure of the policy object information element is exemplarily shown in Table 1:

[0081] Table 1

[0082] In Table 1, Attribute name means the attribute name, Data type means the data type, P means whether the data type is mandatory (M), conditionally optional (C), or optional (O), Cardinality means the number of occurrences of the data type, Description means description, and Applicability means applicability.

[0083] As shown in Table 1, the policy object information element includes a ScopeIdentifier, one or more xxObjectives (targets of the A1 policy), and one or more xxResources (resources of the A1 policy). The ScopeIdentifier indicates the scope of the A1 policy (hereinafter referred to as the first scope for convenience), as described in O-RAN.WG2.A1TD-v07.006.3.1. For example, the structure of the ScopeIdentifier is shown in Table 2:

[0084] Table 2

[0085] As described above, the policy placement request message can be used to instruct the creation of the A1 policy within the first scope of action.

[0086] Please refer to Table 2. In an optional embodiment of the present application, the first scope of action includes at least one of the following: UE (User Equipment) where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS (Quality of Service) flow where the policy is effective; cell where the policy is effective.

[0087] After receiving the policy placement request message, the Near-RT RIC can initiate the RIC subscription process to the appropriate E2 node based on the ScopeIdentifier, xxObjectives, and xxResources in the policy object information element. During the RIC subscription process, the Near-RT RIC requests the E2 node to control a certain RAN function (such as E2SM-RC, E2SM-CCC, etc.) to perform certain actions (such as sending specific reports, waiting to receive specific instructions, etc.) to optimize the RAN performance of the E2 node. When the RIC subscription process is successful, the Near-RT RIC successfully creates the A1 policy. Among them, the E2 node can be, for example, a CU (centralized unit), a DU (distributed unit), a gNB (new generation node B), etc.

[0088] In addition, in an embodiment of the present application, the policy placement request message may also indicate whether the A1 policy is allowed to take effect within a partial range of the first scope, where the partial range of the first scope may be understood as a non-empty proper subset of the first scope.

[0089] Allowing the A1 policy to take effect partially within the first scope means that the A1 policy is only effective within a portion of the first scope and not effective within the other portion. Disallowing the A1 policy to take effect partially within the first scope means that the A1 policy is only effective within the entire first scope and not effective within a portion of the first scope and not effective within the other portion.

[0090] Step 202: If the Near-RT RIC successfully creates the A1 policy within a portion of the first scope and fails to successfully create the A1 policy within another portion, the Near-RT RIC sends a policy placement response message to the Non-RT RIC based on an indication of whether to allow the A1 policy to take effect within the portion of the first scope.

[0091] The Near-RT RIC successfully creates the A1 policy in a part of the first scope, but fails to create the A1 policy in another part of the scope. This can be caused by the following two situations:

[0092] 1. The Near-RT RIC executed the A1 policy creation process in all areas of the first scope. However, the Near-RT RIC successfully created the A1 policy in part of the first scope, but encountered an error while creating the A1 policy in another part, and was unable to successfully create the A1 policy.

[0093] 2. The Near-RT RIC executes the A1 policy creation process within a portion of the first scope, but does not execute the A1 policy creation process within another portion of the first scope for various reasons. The A1 policy creation process executed by the Near-RT RIC may be fully or partially successful.

[0094] In an optional embodiment of the present application, the policy placement response message (HTTP PUT Response) may include a status code. If the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to successfully create the A1 policy within another portion, the Near-RT RIC may determine the status code in the policy placement response message based on an indication of whether the A1 policy is allowed to take effect within the portion of the first scope, and then send the policy placement response message to the Non-RT RIC based on the determined status code.

[0095] The A1 policy creation method provided in this embodiment indicates in a policy placement request message sent by a non-RT RIC to a near-RT RIC whether the A1 policy is allowed to take effect within a partial range of the first scope. Furthermore, when the Near-RT RIC successfully creates the A1 policy within a partial range of the first scope but fails to successfully create the A1 policy within another partial range, the Near-RT RIC sends a policy placement response message to the non-RT RIC based on the indication of whether the A1 policy is allowed to take effect within the partial range of the first scope. This improves the corresponding process when the A1 policy is successfully created only within a partial range of the first scope, thereby ensuring device interoperability between the Near-RT RIC and the non-RT RIC.

[0096] In an optional embodiment of the present application, two optional ways of indicating whether to allow the A1 policy to take effect within a partial range of the first scope of action are provided.

[0097] In the first manner, the policy placement request message may include an indication information element, which may be called Partial-success-allowed in English. The indication information element is used to indicate whether the A1 policy is allowed to take effect in a partial range of the first scope.

[0098] Wherein, in the case that the policy placement request message includes an indication information element, the indication information element may be located in a message header (HTTP Header) of the policy placement request message, or the indication information element may be located in a message body (HTTP Body) of the policy placement request message.

[0099] When the indication information element is located in the message header of the policy placement request message, the value of the indication information element can be true or false. In an optional embodiment, when the value of the indication information element is true, it indicates that the A1 policy is allowed to take effect within a partial scope of the first scope of action; when the value of the indication information element is false, it indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope of action.

[0100] When the indication information element is located in the message body of the policy placement request message, there are two optional implementation methods:

[0101] A. The indication cell is located in the policy object cell.

[0102] In an optional embodiment of the present application, an indication information element may be added to the information elements already included in the policy object information element. Please refer to Table 3, which shows an example of the structure of the policy object information element after the indication information element is added. As shown in Table 3, "policyPartialCreatedAllowedFlag" represents the indication information element, which can take a value of 1 or 0. In an optional embodiment, a value of 1 indicates that the A1 policy is allowed to take effect within a portion of the first scope of application, and a value of 0 indicates that the A1 policy is not allowed to take effect within a portion of the first scope of application.

[0103] Table 3

[0104] B. Add a PolicyOperationObject information element to the message body of the Policy Placement Request message. That is, the message body of the Policy Placement Request message contains both a PolicyObject information element and a PolicyOperationObject information element, with the Indication information element located within the PolicyOperationObject information element. See Table 4 for a possible structure of the PolicyOperationObject information element.

[0105] Table 4

[0106] As shown in Table 4, "policyPartialCreatedAllowedFlag" is an indicator element, which can take a value of 1 or 0. In an optional embodiment, a value of 1 indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, and a value of 0 indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope.

[0107] In the second manner, the policy placement request message may not include the indication information element, and the policy placement request message may implicitly indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0108] Among them, optionally, the implicit indication of whether the A1 policy is allowed to take effect within a partial scope of the first scope can be, for example: the policy placement request message defaults to indicating that the A1 policy is allowed to take effect within a partial scope of the first scope, or the policy placement request message defaults to indicating that the A1 policy is not allowed to take effect within a partial scope of the first scope.

[0109] In an optional embodiment of the present application, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to successfully create the A1 policy within another portion, including at least one of the following possible situations:

[0110] A. The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps. The total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one of the multiple initiated RIC subscription processes succeeds and at least one fails.

[0111] In actual applications, Near-RT RIC has multiple built-in xApps, each of which has a certain range of capabilities. That is, each xApp has the ability to initiate a RIC subscription process to E2 nodes within a specific range.

[0112] The Near-RT RIC can determine multiple first xApps based on the matching of the capabilities of the built-in xApp with the first scope of action, where the total capabilities of the multiple first xApps can cover the entire scope of the first scope of action. The Near-RT RIC can then initiate RIC subscription processes to multiple E2 nodes using the multiple first xApps. Among the multiple RIC subscription processes initiated by the multiple first xApps, at least one RIC subscription process succeeds, and at least one RIC subscription process fails.

[0113] In other words, in situation A, the Near-RT RIC executed the A1 policy creation process within the entire scope of the first scope. However, the Near-RT RIC successfully created the A1 policy within a part of the first scope, but an error occurred when creating the A1 policy within another part, and the A1 policy was not successfully created.

[0114] B. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp. The total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful.

[0115] In actual applications, among the multiple xApps built into the Near-RT RIC, there may only be xApps that match a portion of the first scope, but no xApps that match another portion of the first scope. In this case, the Near-RT RIC can determine at least one second xApp based on the matching between the capability scope of the built-in xApp and the first scope, wherein the total capability scope of the at least one second xApp cannot cover the entire scope of the first scope, but can only cover a portion of the first scope. Then, the Near-RT RIC can initiate a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the at least one RIC subscription process initiated by the at least one second xApp is fully or partially successful.

[0116] In other words, in situation B, the Near-RT RIC executes the A1 policy creation process within a part of the first scope, but because there is no matching xApp, the A1 policy creation process is not executed within another part of the first scope. The A1 policy creation process executed by the Near-RT RIC can be fully successful or partially successful.

[0117] C. The Near-RT RIC cannot initiate a RIC subscription process to at least one E2 node based on the matching between the capability scope of the built-in xApp and the first scope, wherein the total scope of the at least one RIC subscription process that cannot be initiated is smaller than the first scope.

[0118] The Near-RT RIC may determine multiple third xApps based on a match between the capability scope of the built-in xApp and the first scope, wherein the total capability scope of the multiple third xApps may cover the entire scope of the first scope, or the total capability scope of the multiple third xApps may not cover the entire scope of the first scope but may only cover a portion of the first scope, wherein at least one of the multiple third xApps is unable to initiate a RIC subscription process to the E2 node, and wherein the total scope of the at least one RIC subscription process that cannot be initiated is smaller than the first scope.

[0119] In other words, in case C, the Near-RT RIC successfully created the A1 policy in a part of the first scope, but failed to successfully create the A1 policy in the other scope because the xApp could not initiate the RIC subscription process.

[0120] In an optional embodiment of the present application, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, and the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope, but fails to successfully create the A1 policy within another partial scope, then the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully created the policy within the partial scope of the first scope. The first status code can be a status code starting with 2, for example, status code 214, status code 213, or status code 215.

[0121] In an optional embodiment of the present application, if the policy placement request message indicates that the A1 policy is not allowed to take effect within a part of the first scope, and the Near-RT RIC successfully creates the A1 policy within a part of the first scope, but fails to successfully create the A1 policy within another part, then the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC has executed the policy creation process, and an error has occurred in the policy creation process. The second status code can be a status code starting with 5, for example, a 512 status code, a 503 status code, or a 500 status code.

[0122] In one embodiment, as shown in FIG3 , an A1 policy creation method is provided. The method is described by taking the application of the method to a Non-RT RIC as an example, and includes the following steps:

[0123] Step 301: The Non-RT RIC sends a policy placement request message to the Near-RT RIC.

[0124] The policy placement request message is used to instruct the creation of the A1 policy within the first scope of action, and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope of action.

[0125] Step 302: The Non-RT RIC receives a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0126] In an optional embodiment of the present application, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, then if the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully creates the policy within the partial scope of the first scope.

[0127] In an optional embodiment of the present application, if the policy placement request message indicates that the A1 policy is not allowed to take effect within a part of the first scope, then if the Near-RT RIC successfully creates the A1 policy within a part of the first scope and fails to successfully create the A1 policy within another part, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC has executed the policy creation process and that an error occurred in the policy creation process.

[0128] In addition, the specific manner in which the policy placement request indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope, the situation in which the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope, and fails to successfully create the A1 policy within another partial scope, etc. are similar to those described in the above embodiments and will not be repeated here in the embodiments of the present application.

[0129] In order to make it easier for readers to understand the technical solution provided in the embodiment of the present application, the A1 policy creation method provided in the embodiment of the present application is explained below with reference to 6 examples.

[0130] Please refer to FIG4 , which shows a flowchart corresponding to the first example. As shown in FIG4 , the following steps are included:

[0131] Step 401: The Non-RT RIC sends a policy placement request message to the Near-RT RIC, wherein the message header of the policy placement request message includes an indication information element (Partial-success-allowed), and the value of the indication information element is true.

[0132] Step 402: The Near-RT RIC determines xApp1 and xApp2 based on a match between the capability scope of the built-in xApp and the first scope of action indicated by the policy placement request message.

[0133] The total capability range of xApp1 and xApp2 covers the entire range of the first scope. Specifically, xApp1 is responsible for creating the A1 policy on E2 node 1, and xApp2 is responsible for creating the A1 policy on E2 node 2.

[0134] Step 403: The Near-RT RIC sends a RIC subscription request message (RIC Subscription Request) to the E2 node 1 through xApp1 to initiate the RIC subscription process.

[0135] Step 404: The Near-RT RIC sends a RIC subscription request message to the E2 node 2 through xApp2 to initiate the RIC subscription process.

[0136] Step 405: E2 node 1 feeds back a RIC subscription response message (RIC Subscription Response) to the Near-RT RIC to indicate that the RIC subscription is successful.

[0137] Step 406: E2 node 2 feeds back a RIC subscription failure message (RIC Subscription Failure) to the Near-RT RIC to indicate that the RIC subscription has failed.

[0138] The reasons for subscription failure may include, for example, E2 node 2 overload, E2 node 2 message processing error, etc.

[0139] Step 407: The Near-RT RIC sends a policy placement response message to the Non-RT RIC. The policy placement response message includes a 214 status code, indicating that the A1 policy is successfully created within a partial scope of the first scope.

[0140] Please refer to FIG5 , which shows a flowchart corresponding to the second example. As shown in FIG5 , the following steps are included:

[0141] Step 501: The Non-RT RIC sends a policy placement request message to the Near-RT RIC, wherein the message header of the policy placement request message includes an indication information element (Partial-success-allowed), and the value of the indication information element is false.

[0142] Step 502: The Near-RT RIC determines xApp1 and xApp2 based on the matching between the capability scope of the built-in xApp and the first scope of action indicated by the policy placement request message.

[0143] The total capability range of xApp1 and xApp2 covers the entire range of the first scope. Specifically, xApp1 is responsible for creating the A1 policy on E2 node 1, and xApp2 is responsible for creating the A1 policy on E2 node 2.

[0144] Step 503: The Near-RT RIC sends a RIC subscription request message to the E2 node 1 through the xApp1 to initiate the RIC subscription process.

[0145] Step 504: The Near-RT RIC sends a RIC subscription request message to the E2 node 2 through xApp2 to initiate the RIC subscription process.

[0146] Step 505: E2 node 1 feeds back an RIC subscription response message to the Near-RT RIC to indicate that the RIC subscription is successful.

[0147] Step 506: E2 node 2 feeds back a RIC subscription failure message to the Near-RT RIC to indicate that the RIC subscription has failed.

[0148] Step 507: The Near-RT RIC sends a policy placement response message to the Non-RT RIC. The policy placement response message includes a 500 status code, indicating an internal server error. The Near-RT RIC executes the policy creation process, and an error occurs in the policy creation process.

[0149] Please refer to FIG6 , which shows a flowchart corresponding to the third example. As shown in FIG6 , the following steps are included:

[0150] Step 601: The Non-RT RIC sends a policy placement request message to the Near-RT RIC, wherein the policy object information element in the message body of the policy placement request message includes an indication information element PolicyPartialCreatedAllowedFlag with a value of 1.

[0151] Step 602: The Near-RT RIC determines xApp1 based on a match between the capability scope of the built-in xApp and the first scope of action indicated by the policy placement request message.

[0152] The capability scope of xApp1 covers a portion of the first scope. There is no xApp in the Near-RT RIC that matches the other portion of the first scope. Specifically, xApp1 is responsible for creating the A1 policy on E2 node 1, and there is no xApp in the Near-RT RIC that is responsible for creating the A1 policy on E2 node 2.

[0153] Step 603: The Near-RT RIC sends an RIC subscription request message to the E2 node 1 through the xApp1 to initiate the RIC subscription process.

[0154] Step 604: E2 node 1 feeds back an RIC subscription response message to the Near-RT RIC to indicate that the RIC subscription is successful.

[0155] Step 605: The Near-RT RIC sends a policy placement response message to the Non-RT RIC. The policy placement response message includes a 213 status code, indicating that the A1 policy is successfully created within a portion of the first scope.

[0156] Please refer to FIG7 , which shows a flowchart corresponding to the fourth example. As shown in FIG7 , the following steps are included:

[0157] Step 701: The Non-RT RIC sends a policy placement request message to the Near-RT RIC, wherein the policy object information element in the message body of the policy placement request message includes an indication information element PolicyPartialCreatedAllowedFlag with a value of 0.

[0158] Step 702: The Near-RT RIC determines xApp1 based on a match between the capability scope of the built-in xApp and the first scope indicated by the policy placement request message.

[0159] The capability scope of xApp1 covers a portion of the first scope. There is no xApp in the Near-RT RIC that matches the other portion of the first scope. Specifically, xApp1 is responsible for creating the A1 policy on E2 node 1, and there is no xApp in the Near-RT RIC that is responsible for creating the A1 policy on E2 node 2.

[0160] Step 703: The Near-RT RIC sends a policy placement response message to the Non-RT RIC. The policy placement response message includes a 503 status code, indicating that service is unavailable. The Near-RT RIC has executed a policy creation process, and an error has occurred in the policy creation process.

[0161] Please refer to FIG8 , which shows a flowchart corresponding to the fifth example. As shown in FIG8 , the process includes the following steps:

[0162] Step 801: The Non-RT RIC sends a policy placement request message to the Near-RT RIC. The message body of the policy placement request message includes both a policy object information element and a policy operation object information element. The policy operation object information element includes an indication information element PolicyPartialCreatedAllowedFlag, and the value of the indication information element is 1.

[0163] Step 802: The Near-RT RIC determines xApp1 and xApp2 based on the matching between the capability scope of the built-in xApp and the first scope of action indicated by the policy placement request message.

[0164] The total capability range of xApp1 and xApp2 covers the entire range of the first scope. Specifically, xApp1 is responsible for creating the A1 policy on E2 node 1, and xApp2 is responsible for creating the A1 policy on E2 node 2.

[0165] Step 803: The Near-RT RIC sends a RIC subscription request message to the E2 node 1 through xApp1 to initiate the RIC subscription process.

[0166] Step 804: E2 node 1 feeds back an RIC subscription response message to the Near-RT RIC to indicate that the RIC subscription is successful.

[0167] Step 805: The Near-RT RIC cannot initiate the RIC subscription process to the E2 node 2 through xApp2.

[0168] Possible reasons include xApp2 overloading, xApp2 not supporting this type of A1 policy, and xApp2 internal processing errors.

[0169] Step 806: The Near-RT RIC sends a policy placement response message to the Non-RT RIC. The policy placement response message includes a 215 status code, indicating that the A1 policy is successfully created within a partial scope of the first scope.

[0170] Please refer to FIG9 , which shows a flowchart corresponding to the sixth example. As shown in FIG9 , the following steps are included:

[0171] Step 901: The Non-RT RIC sends a policy placement request message to the Near-RT RIC. The message body of the policy placement request message includes both a policy object information element and a policy operation object information element. The policy operation object information element includes an indication information element PolicyPartialCreatedAllowedFlag, and the value of the indication information element is 0.

[0172] Step 902: The Near-RT RIC determines xApp1 and xApp2 based on a match between the capability scope of the built-in xApp and the first scope indicated by the policy placement request message.

[0173] The total capability range of xApp1 and xApp2 covers the entire range of the first scope. Specifically, xApp1 is responsible for creating the A1 policy on E2 node 1, and xApp2 is responsible for creating the A1 policy on E2 node 2.

[0174] Step 903: The Near-RT RIC sends an RIC subscription request message to the E2 node 1 through xApp1 to initiate the RIC subscription process.

[0175] Step 904: E2 node 1 feeds back an RIC subscription response message to the Near-RT RIC to indicate that the RIC subscription is successful.

[0176] Step 905: The Near-RT RIC cannot initiate the RIC subscription process to the E2 node 2 through xApp2.

[0177] Step 906: The Near-RT RIC sends a policy placement response message to the Non-RT RIC. The policy placement response message includes a 512 status code, indicating that the Near-RT RIC has executed the policy creation process and an error has occurred in the policy creation process.

[0178] It should be understood that, although the various steps in the flowcharts of Figures 2-9 are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in Figures 2-9 may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0179] In one embodiment, as shown in FIG10 , an A1 policy creation apparatus 1000 is provided for use in a Near-RT RIC, including a request receiving unit 1001 and a response sending unit 1002 .

[0180] The request receiving unit 1001 is used to receive a policy placement request message sent by the Non-RT RIC. The policy placement request message is used to instruct the creation of an A1 policy within the first scope and to indicate whether the A1 policy is allowed to take effect within a portion of the first scope.

[0181] The response sending unit 1002 is configured to send a policy placement response message to the Non-RT RIC based on an indication of whether to allow the A1 policy to take effect within a portion of the first scope if the Near-RT RIC successfully creates the A1 policy within a portion of the first scope and fails to successfully create the A1 policy within another portion of the scope.

[0182] In an optional embodiment of the present application, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully created the policy within the partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within the partial scope of the first scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executed the policy creation process, and an error occurred in the policy creation process.

[0183] In an optional embodiment of the present application, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0184] In an optional embodiment of the present application, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0185] In an optional embodiment of the present application, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes a policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0186] In an optional embodiment of the present application, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0187] In an optional embodiment of the present application, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to successfully create the A1 policy within another portion, including at least one of the following:

[0188] The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps, wherein the total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds, and at least one RIC subscription process fails. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to the at least one E2 node based on a match between the capability scope of the built-in xApp and the first scope, and wherein the total scope of the at least one RIC subscription process that fails to be initiated is smaller than the first scope.

[0189] In one embodiment, as shown in FIG11 , an A1 policy creation apparatus 1100 is provided for use in a Non-RT RIC, including a request sending unit 1101 and a response receiving unit 1102 .

[0190] The request sending unit 1101 is used to send a policy placement request message to the Near-RT RIC. The policy placement request message is used to instruct the creation of the A1 policy within the first scope and to indicate whether the A1 policy is allowed to take effect within a part of the first scope.

[0191] The response receiving unit 1102 is configured to receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0192] In an optional embodiment of the present application, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully creates the policy within a partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executed the policy creation process and an error occurred in the policy creation process.

[0193] In an optional embodiment of the present application, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0194] In an optional embodiment of the present application, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0195] In an optional embodiment of the present application, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes a policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0196] In an optional embodiment of the present application, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0197] In an optional embodiment of the present application, the Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to successfully create the A1 policy within another portion, including at least one of the following:

[0198] The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps, wherein the total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds, and at least one RIC subscription process fails. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to the at least one E2 node based on a match between the capability scope of the built-in xApp and the first scope, and wherein the total scope of the at least one RIC subscription process that fails to be initiated is smaller than the first scope.

[0199] The specific definition of the A1 policy creation device can be found in the definition of the A1 policy creation method above and will not be repeated here. Each unit in the above-mentioned A1 policy creation device can be implemented in whole or in part through software, hardware, or a combination thereof. Each of the above-mentioned units can be embedded in or independent of the processor in the communication device in hardware form, or can be stored in the memory of the communication device in software form, so that the processor can call and execute the corresponding operations of each of the above-mentioned units.

[0200] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0201] If the integrated unit is implemented 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 solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application.

[0202] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0203] Figure 12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. For example, the communication device may be a Near-RT RIC, or the communication device may be a Non-RT RIC. The communication device 1200 shown in Figure 12 includes: a processor 1201 and a memory 1202. The various components in the communication device 1200 are coupled together through a bus system 1203. It can be understood that the bus system 1203 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 1203 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, various buses are labeled as bus system 1203 in Figure 12. In addition, in an embodiment of the present application, a transceiver 1204 is also included. The transceiver can be multiple components, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

[0204] It is understood that the memory 1202 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1202 of the systems and methods described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0205] In some embodiments, the memory 1202 stores the following elements, executable modules or data structures, or subsets thereof, or extended sets thereof: an operating system 12021. The operating system 12021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, for implementing various basic services and processing hardware-based tasks.

[0206] Some or all of the methods disclosed in the above embodiments of the present application can be applied to the processor 1201, or implemented by the processor 1201, or implemented by the processor 1201 in conjunction with other components (such as a transceiver). The processor 1201 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 1201 or by instructions in the form of software. The above-mentioned processor 1201 can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 1202, and processor 1201 reads information in memory 1202 and, in conjunction with its hardware, completes the steps of the above method.

[0207] It is understood that the embodiments described in the embodiments of the present application can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSP devices, DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0208] For software implementation, the techniques described in the embodiments of the present application can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of the present application. The software code can be stored in a memory and executed by the processor 1201. The memory can be implemented in the processor 1201 or external to the processor 1201.

[0209] Specifically, the communication device shown in FIG12 may execute the method steps corresponding to the Near-RT RIC in the above method embodiment, and may also execute the method steps corresponding to the Non-RT RIC in the above method embodiment.

[0210] When executing the method steps corresponding to Near-RT RIC in the above method embodiment:

[0211] The processor 1201 is configured to read a computer program in a memory and perform the following operations: control the transceiver 1204 to receive a policy placement request message sent by a non-RT RIC, where the policy placement request message is used to indicate creation of an A1 policy within a first scope and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; if the near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, control the transceiver 1204 to send a policy placement response message to the non-RT RIC based on the indication of whether the A1 policy is allowed to take effect within the partial scope of the first scope.

[0212] In one of the embodiments, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully created the policy within the partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within the partial scope of the first scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executed the policy creation process, and an error occurred in the policy creation process.

[0213] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0214] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0215] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes a policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0216] In one of the embodiments, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0217] In one embodiment, the Near-RT RIC successfully creates the A1 policy in a portion of the first scope and fails to successfully create the A1 policy in another portion, including at least one of the following:

[0218] The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps, wherein the total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds, and at least one RIC subscription process fails. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to the at least one E2 node based on a match between the capability scope of the built-in xApp and the first scope, and wherein the total scope of the at least one RIC subscription process that fails to be initiated is smaller than the first scope.

[0219] When executing the method steps corresponding to Non-RT RIC in the above method embodiment:

[0220] Processor 1201 is configured to read a computer program in a memory and perform the following operations: control transceiver 1204 to send a policy placement request message to a Near-RT RIC, where the policy placement request message is used to instruct creation of an A1 policy within a first scope of action and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope of action; and control transceiver 1204 to receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0221] In one of the embodiments, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully creates the policy within a partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executes the policy creation process and an error occurs in the policy creation process.

[0222] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial scope of the first scope.

[0223] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0224] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes a policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0225] In one of the embodiments, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0226] In one embodiment, the Near-RT RIC successfully creates the A1 policy in a portion of the first scope and fails to successfully create the A1 policy in another portion, including at least one of the following:

[0227] The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps, wherein the total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds, and at least one RIC subscription process fails. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to the at least one E2 node based on a match between the capability scope of the built-in xApp and the first scope, and wherein the total scope of the at least one RIC subscription process that fails to be initiated is smaller than the first scope.

[0228] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0229] Receive a policy placement request message sent by a Non-RT RIC, where the policy placement request message is used to indicate creation of an A1 policy within a first scope and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; if the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, send a policy placement response message to the Non-RT RIC based on the indication of whether the A1 policy is allowed to take effect within the partial scope of the first scope.

[0230] In one embodiment, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, the policy placement response includes a first status code, which is used to indicate that the Near-RT RIC successfully created the policy within a partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope, the policy placement response includes a second status code, which is used to indicate that the Near-RT RIC executed the policy creation process, and an error occurred in the policy creation process.

[0231] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial range of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial range of the first scope.

[0232] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0233] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes a policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0234] In one embodiment, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0235] In one embodiment, the Near-RT RIC successfully creates the A1 policy in a portion of the first scope, but fails to create the A1 policy in another portion, including at least one of the following:

[0236] The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps, wherein the total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds, and at least one RIC subscription process fails. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to the at least one E2 node based on a match between the capability scope of the built-in xApp and the first scope, and wherein the total scope of the at least one RIC subscription process that fails to be initiated is smaller than the first scope.

[0237] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0238] Send a policy placement request message to the Near-RT RIC, where the policy placement request message is used to instruct the creation of the A1 policy within the first scope and to indicate whether the A1 policy is allowed to take effect within a partial scope of the first scope; and receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

[0239] In one embodiment, if the policy placement request message indicates that the A1 policy is allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a first status code, and the first status code is used to indicate that the Near-RT RIC successfully creates the policy within a partial scope of the first scope; if the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial scope of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a partial scope of the first scope and fails to successfully create the A1 policy within another partial scope, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC executes the policy creation process and an error occurs in the policy creation process.

[0240] In one embodiment, the policy placement request message includes an indication information element, which is used to indicate whether the A1 policy is allowed to take effect within a partial range of the first scope; or, the policy placement request message implicitly indicates whether the A1 policy is allowed to take effect within a partial range of the first scope.

[0241] In one embodiment, the indication information element is located in the message header of the policy placement request message; or, the indication information element is located in the message body of the policy placement request message.

[0242] In one embodiment, the message body of the policy placement request message includes a policy object information element, the policy object information element includes description information of the A1 policy, and the indication information element is located in the policy object information element; or, the message body of the policy placement request message includes a policy object information element and a policy operation object information element, and the indication information element is located in the policy operation object information element.

[0243] In one embodiment, the first scope of action includes at least one of the following: UE where the policy is effective; UE group where the policy is effective; network slice where the policy is effective; QoS flow where the policy is effective; cell where the policy is effective.

[0244] In one embodiment, the Near-RT RIC successfully creates the A1 policy in a portion of the first scope, but fails to create the A1 policy in another portion, including at least one of the following:

[0245] The Near-RT RIC determines multiple first xApps based on a match between the capability scope of the built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes through the multiple first xApps, wherein the total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds, and at least one RIC subscription process fails. The Near-RT RIC determines at least one second xApp based on a match between the capability scope of the built-in xApp and the first scope, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein the total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful. The Near-RT RIC fails to initiate a RIC subscription process to the at least one E2 node based on a match between the capability scope of the built-in xApp and the first scope, and wherein the total scope of the at least one RIC subscription process that fails to be initiated is smaller than the first scope.

[0246] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0247] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0248] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A method for creating an A1 strategy, wherein: The method comprises: A near-real-time radio access network intelligent controller Near-RT RIC receives a policy placement request message sent by a non-real-time radio access network intelligent controller Non-RT RIC, where the policy placement request message is used to instruct creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a partial scope of the first scope of action; If the Near-RT RIC successfully creates the A1 policy within a part of the first scope and fails to successfully create the A1 policy within another part, the Near-RT RIC sends a policy placement response message to the Non-RT RIC based on an indication of whether to allow the A1 policy to take effect within the part of the first scope.

2. The method according to claim 1, wherein If the policy placement request message indicates that the A1 policy is allowed to take effect within a partial range of the first scope, the policy placement response includes a first status code, where the first status code is used to indicate that the Near-RT RIC successfully creates the policy within the partial range of the first scope; If the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial range of the first scope, the policy placement response includes a second status code, which is used to indicate that the Near-RT RIC has executed a policy creation process and an error has occurred in the policy creation process.

3. The method according to claim 1 or 2, wherein: The first scope of action includes at least one of the following: User equipment UE on which the policy takes effect; UE group for which the policy is effective; Network slices where policies take effect; Quality of Service (QoS) flows where policies take effect; The cell where the policy takes effect.

4. The method according to any one of claims 1 to 3, wherein: The Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following: The Near-RT RIC determines multiple first xApps based on a match between a capability scope of a built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds and at least one RIC subscription process fails; The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful; The Near-RT RIC cannot initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of a built-in xApp and the first scope, wherein a total scope of at least one RIC subscription process that cannot be initiated is smaller than the first scope.

5. A method for creating an A1 strategy, wherein: The method comprises: The Non-RT RIC sends a policy placement request message to the Near-RT RIC, where the policy placement request message is used to instruct the creation of the A1 policy within the first scope and to indicate whether to allow the A1 policy to take effect within a portion of the first scope; The Non-RT RIC receives a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

6. The method according to claim 5, wherein: If the policy placement request message indicates that the A1 policy is allowed to take effect within a partial range of the first scope, then if the Near-RT RIC successfully creates the A1 policy within a partial range of the first scope but fails to successfully create the A1 policy within another partial range, the policy placement response includes a first status code, where the first status code is used to indicate that the Near-RT RIC successfully creates the policy within the partial range of the first scope; If the policy placement request message indicates that the A1 policy is not allowed to take effect within a part of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a part of the first scope and fails to successfully create the A1 policy within another part, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC has executed the policy creation process and that an error occurs in the policy creation process.

7. The method according to claim 5 or 6, wherein: The first scope of action includes at least one of the following: UEs where the policy is effective; UE group for which the policy is effective; Network slices where policies take effect; QoS flows where the policy is effective; The cell where the policy takes effect.

8. The method according to claim 6, wherein: The Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following: The Near-RT RIC determines multiple first xApps based on a match between a capability scope of a built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds and at least one RIC subscription process fails; The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful; The Near-RT RIC cannot initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of a built-in xApp and the first scope, wherein a total scope of at least one RIC subscription process that cannot be initiated is smaller than the first scope.

9. An A1 strategy creation device, wherein: Used in Near-RT RIC, including: a request receiving unit, configured to receive a policy placement request message sent by a Non-RT RIC, wherein the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action; a response sending unit, configured to send a policy placement response message to the Non-RT RIC based on an indication of whether to allow the A1 policy to take effect within a portion of the first scope, if the Near-RT RIC successfully creates the A1 policy within a portion of the first scope and fails to successfully create the A1 policy within another portion of the scope.

10. An A1 strategy creation device, wherein: Used in Non-RT RIC, including: a request sending unit, configured to send a policy placement request message to the Near-RT RIC, wherein the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action; A response receiving unit is configured to receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

11. A communication device, wherein: Including memory, transceiver, processor: memory for storing computer programs; a transceiver, configured to transmit and receive data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Controlling the transceiver to receive a policy placement request message sent by a Non-RT RIC, wherein the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action; If the Near-RT RIC successfully creates the A1 policy within a part of the first scope and fails to successfully create the A1 policy within another part, then based on the indication of whether to allow the A1 policy to take effect within the part of the first scope, control the transceiver to send a policy placement response message to the Non-RT RIC.

12. The communication device according to claim 11, wherein: If the policy placement request message indicates that the A1 policy is allowed to take effect within a partial range of the first scope, the policy placement response includes a first status code, where the first status code is used to indicate that the Near-RT RIC successfully creates the policy within the partial range of the first scope; If the policy placement request message indicates that the A1 policy is not allowed to take effect within a partial range of the first scope, the policy placement response includes a second status code, which is used to indicate that the Near-RT RIC has executed a policy creation process and an error has occurred in the policy creation process.

13. The communication device according to claim 11 or 12, characterized in that The first scope of action includes at least one of the following: User equipment UE on which the policy takes effect; UE group for which the policy is effective; Network slices where policies take effect; Quality of Service (QoS) flows where policies take effect; The cell where the policy takes effect.

14. The communication device according to any one of claims 11 to 13, characterized in that: The Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following: The Near-RT RIC determines multiple first xApps based on a match between a capability scope of a built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds and at least one RIC subscription process fails; The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful; The Near-RT RIC cannot initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of a built-in xApp and the first scope, wherein a total scope of at least one RIC subscription process that cannot be initiated is smaller than the first scope.

15. A communication device, wherein: Including memory, transceiver, processor: memory for storing computer programs; a transceiver, configured to transmit and receive data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Controlling the transceiver to send a policy placement request message to the Near-RT RIC, where the policy placement request message is used to instruct the creation of an A1 policy within a first scope of action and to indicate whether to allow the A1 policy to take effect within a portion of the first scope of action; The transceiver is controlled to receive a policy placement response message sent by the Near-RT RIC based on the policy placement request message.

16. The communication device according to claim 15, characterized in that If the policy placement request message indicates that the A1 policy is allowed to take effect within a partial range of the first scope, then if the Near-RT RIC successfully creates the A1 policy within a partial range of the first scope but fails to successfully create the A1 policy within another partial range, the policy placement response includes a first status code, where the first status code is used to indicate that the Near-RT RIC successfully creates the policy within the partial range of the first scope; If the policy placement request message indicates that the A1 policy is not allowed to take effect within a part of the first scope, then when the Near-RT RIC successfully creates the A1 policy within a part of the first scope and fails to successfully create the A1 policy within another part, the policy placement response includes a second status code, and the second status code is used to indicate that the Near-RT RIC has executed the policy creation process and that an error occurs in the policy creation process.

17. The communication device according to claim 15 or 16, characterized in that The first scope of action includes at least one of the following: UEs where the policy is effective; UE group for which the policy is effective; Network slices where policies take effect; QoS flows where the policy is effective; The cell where the policy takes effect.

18. The communication device according to claim 16, wherein: The Near-RT RIC successfully creates the A1 policy within a portion of the first scope, but fails to create the A1 policy within another portion, including at least one of the following: The Near-RT RIC determines multiple first xApps based on a match between a capability scope of a built-in xApp and the first scope, and initiates RIC subscription processes to multiple E2 nodes respectively through the multiple first xApps, wherein a total scope of the multiple initiated RIC subscription processes is equal to the first scope, and at least one RIC subscription process among the multiple initiated RIC subscription processes succeeds and at least one RIC subscription process fails; The Near-RT RIC determines, based on a match between a capability scope of the built-in xApp and the first scope, at least one second xApp, and initiates a RIC subscription process to at least one E2 node through the at least one second xApp, wherein a total scope of the at least one initiated RIC subscription process is smaller than the first scope, and the at least one initiated RIC subscription process is fully or partially successful; The Near-RT RIC cannot initiate a RIC subscription process to at least one E2 node based on a match between a capability scope of a built-in xApp and the first scope, wherein a total scope of at least one RIC subscription process that cannot be initiated is smaller than the first scope.

Images