Quality-of-service policy generation method and apparatus

Abstract

The present application provides a policy generation method and a policy generation apparatus. The method comprises: a second network function sending to a first network function a service type subscribed to by at least one node, and triggering a node to send a triggered first service to the first network function; and the first network function determining a quality-of-service (QoS) policy for the first service on the basis of the service type and the first service. In the present application, a second network function is newly added, and the second network function can provide a service type subscribed to by a network node served by a first network function for use by a first network device to generate a QoS policy for a triggered service. The technical solution of the present application can implement QoS policy generation in an AI4NET application scenario.

Description

Quality of Service Policy Generation Method and Device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 26, 2023, with application number 202311821009.4 and application name “Service Quality Strategy Generation Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a method and device for generating a quality of service (QoS) policy. Background Art

[0003] The sixth-generation (6G) communication system introduces artificial intelligence (AI) technology, giving rise to AI as a service (AIaaS). This has led to two basic application scenarios: network for AI (NET4AI) and AI for network (AI4NET). In AI4NET scenarios, operators (e.g., core network equipment and / or access network equipment) can act as service providers, while nodes within the network (e.g., terminal devices or radio access network (RAN) equipment) can act as both service enablers and service consumers. The network only needs to generate QoS policies based on information from each node within the network. The current QoS policy generation mechanism of 5G communication systems is not applicable to AI4NET scenarios, and there are currently no technical solutions for QoS policy generation in AI4NET scenarios. Summary of the Invention

[0004] This application provides a QoS policy generation method and a QoS policy generation device, which can realize the generation of QoS policies in AI4NET application scenarios.

[0005] In the first aspect, a QoS policy generation method is provided, which can be executed by a first network function, or by a module (such as a chip or circuit) in the first network function, or by a logical node, logical module or software that can implement all or part of the first network function. This application is not limited to this.

[0006] The method includes: a first network function receives first information from a first node, where the first information is used to indicate a first service triggered by the first node; the first network function receives second information from a second network function, where the second information includes a service type of each node in at least one node, where the at least one node is a node served by the first network function; the first network function determines a first QoS policy for the first service based on the first information and the second information, where the first QoS policy includes a QoS requirement for at least one sixth node to complete the first service, where the at least one sixth node belongs to the at least one node.

[0007] This application adds a second network function that can provide the service types subscribed to by the network nodes served by the first network function, which is used by the first network function to generate a QoS policy for the triggered service. The above method can realize the generation of QoS policy in AI4NET application scenarios.

[0008] In combination with the first aspect, in certain implementations of the first aspect, the above method also includes: the first network function obtains the updated service type of the at least one node from each node in the at least one node; the first network function determines the first QoS policy of the first service based on the first information and the second information, including: the first network function determines the first QoS policy of the first service based on the first information, the second information, and the updated service type of each node in at least one node obtained from the at least one node.

[0009] The second network function periodically updates the stored subscription information of each node in the network, rather than updating in real time. Through the above method, the first network function can obtain the real-time subscription information of at least one node, thereby improving the accuracy of the determined first QoS policy.

[0010] In combination with the first aspect, in some implementations of the first aspect, the first information may include indication information of the first node and indication information of the first service.

[0011] Exemplarily, the indication information of the first node may be an identifier of the first node, and the indication information of the first service may be an identifier of the first service.

[0012] In combination with the first aspect, in some implementations of the first aspect, the first information further includes a service requirement of the first node for the first service.

[0013] The first network function can pre-configure templates for multiple services. Each service template includes information such as the service type, the service's requirements for various heterogeneous resources, the service's computational complexity, and the service's runtime. The first network function can directly call the template corresponding to the service based on the indication information of the service triggered by the trigger source and determine the first QoS policy based on the template, thereby reducing the processing delay of the first network function. If the triggering node has other service requirements for the triggered service, the first network function determines the first QoS policy based on the other service requirements of the triggering node for the triggered service.

[0014] In conjunction with the first aspect, in certain implementations of the first aspect, the second information further includes at least one of the following information:

[0015] The node type of each node in at least one node, the service priority of the service type of each node in at least one node, the computing power type, algorithm type, data type, connection topology that each node in at least one node can provide, the computing power resources, algorithm resources, data resources, air interface resources, connection quality, etc. that each node in at least one node can provide.

[0016] Exemplarily, the node type of each node in the above-mentioned at least one node and the service priority of the service type of each node in the at least one node included in the above-mentioned second information can be considered as the subscription information of at least one node, and the computing power type, algorithm type, data type, connection topology, computing power resources, algorithm resources, data resources, air interface resources, connection quality, etc. that each node in the at least one node can provide included in the above-mentioned second information can be considered as the capability information of at least one node, and this application does not limit this.

[0017] In combination with the first aspect, in some implementations of the first aspect, the above-mentioned first network function can be deployed in a base station, or the above-mentioned first network function can be deployed on a centralized unit (CU), or the above-mentioned first network function can be deployed on a cluster control node (cluster node, cNode).

[0018] Exemplarily, the above-mentioned first network function is deployed on the CU, including: when the base station is an open access network (open RAN, ORAN), the first network function can be deployed on the control plane (CU control plan, CU-CP) of the CU in the ORAN system.

[0019] Alternatively, the first network function can be deployed on a near real-time RAN intelligent controller (near real time RAN intelligent controller, near real time RIC) in the ORAN system, which is not limited in this application.

[0020] In conjunction with the first aspect, in certain implementations of the first aspect, when the first network function is deployed within a base station, or when the first network function is deployed on a CU, the method further includes: the first network function decomposes the first service into N tasks based on the first information and the second information and determines N QoS policies for the N tasks, where the N tasks correspond one-to-one to the N QoS policies; and the first network function sends fourth information according to the second QoS policy, where the fourth information is used to instruct at least one second node to execute a second QoS configuration for the second task. The second QoS policy belongs to the N QoS policies, the second task belongs to the N tasks, and the second QoS policy is the QoS policy for the second task. Exemplarily, when the first network function is deployed within a base station, the first network function directly indicates to at least one second node the second QoS configuration for executing the second task. The parameters of the second QoS configuration of each of the at least one second node may be the same, partially the same, or different, and this application does not limit this.

[0021] Exemplarily, when the first network function is deployed on the CU, if at least one second node includes a terminal device, the second QoS configuration indicated by the first network function to the terminal device for performing the second task needs to be forwarded through a distributed unit (DU).

[0022] Through the above method, the first network function can decompose the above first service into N tasks and determine a QoS policy for each of the N tasks, thereby realizing the generation of task-level QoS policies and ensuring the QoS of the first service.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the above method also includes: the first network function receives eighth information, and the eighth information is used to request a change of the second QoS policy; the first network function changes the above second QoS policy to a fifth QoS policy based on the eighth information; the first network function sends ninth information according to the fifth QoS policy, and the ninth information is used to instruct at least one fourth node to perform a fourth QoS configuration of the second task.

[0024] Illustratively, the eighth information includes at least one of the following information:

[0025] The indication information of the second QoS configuration of each node in the at least one second node mentioned above, and the first parameter of the changed QoS configuration, the first parameter including at least one of a 6G QoS indicator (6QI), allocation and retention priority (ARP), flow bit rate (FBR), floating point operations per second (FLOPS), etc.

[0026] Through the above method, when the status of the execution node of the second task is abnormal, a request can be made to change the current QoS policy, which is beneficial to the dynamic adjustment and closed-loop guarantee of the QoS policy.

[0027] In combination with the first aspect, in certain implementations of the first aspect, when the first network function is deployed on a cNode, the method further includes: the first network function decomposes the first service into N tasks based on the first information and the second information and determines N QoS policies for the N tasks, and the N tasks correspond one-to-one to the N QoS policies; the first network function sends fifth information to the first cNode, and the fifth information is used to instruct at least one third node to execute a third QoS policy for a third task, and the fifth information is used for the first cNode to determine at least one fourth QoS policy corresponding to at least one third node, and the at least one third node corresponds one-to-one to the at least one fourth QoS policy. The third QoS policy includes the QoS requirements for at least one third node to complete the third task, the third QoS policy belongs to the N QoS policies, the third task belongs to the N tasks, and the third QoS policy is the QoS policy for the third task.

[0028] Exemplarily, when the first network function is deployed on a cNode, the third QoS policy of the third task determined by the first network function requires the cNode to be further decomposed into at least one third node corresponding to at least one fourth QoS policy.

[0029] It should be noted that the QoS requirements included in the third strategy are overall QoS requirements for various resource elements (computation, algorithms, connections and data) for performing the third task, but the QoS requirements included in the above-mentioned fourth QoS strategy are generally requirements for certain resource elements (computation, algorithms, connections or data) provided by each node in at least one third node that performs the third task.

[0030] Through the above method, the generation of resource-level QoS policy can be achieved to ensure the QoS of the first service.

[0031] In combination with the first aspect, in certain implementations of the first aspect, the above method also includes: the first network function receives thirteenth information, and the thirteenth information is used to request a change of the third QoS policy; the first network function changes the above third QoS policy to a sixth QoS policy based on the thirteenth information; the first network function sends fourteenth information to the second cNode according to the sixth QoS policy, and the fourteenth information is used by the second cNode to determine at least one seventh QoS policy corresponding to at least one fifth node, and the at least one fifth node corresponds one-to-one to the at least one seventh QoS policy.

[0032] Illustratively, the thirteenth information includes at least one of the following information:

[0033] The indication information of the third QoS configuration of each node in the above-mentioned at least one third node, and the second parameter of the changed QoS configuration, where the second parameter includes at least one of 6QI, ARP, FBR, FLOPS, etc.

[0034] Through the above method, when the status of the execution node of the third task is abnormal, a request can be made to change the current QoS policy, which is beneficial to the dynamic adjustment and closed-loop guarantee of the QoS policy.

[0035] On the second aspect, a QoS policy change method is provided, which can be executed by the first network device, or by a module (such as a chip or circuit) in the first network device, or by a logical node, logical module or software that can implement all or part of the first network device. This application does not limit this.

[0036] The method includes: a first network device determines that the state of a second node used to perform a second task is abnormal; the first network device switches the second QoS configuration used by the second node to perform the second task to an alternative QoS configuration; the first network device sends seventh information to the second node, where the seventh information is used to indicate the alternative QoS configuration.

[0037] Exemplarily, the abnormal state of the second node includes: the second node cannot meet the second QoS configuration or the resource redundancy of the second node, etc.

[0038] Through the above method, when the status of the execution node of the second task is abnormal, a request can be made to change the current QoS configuration, which is beneficial to dynamic adjustment and closed-loop guarantee of QoS configuration.

[0039] In combination with the second aspect, in certain implementations of the second aspect, the above method also includes: the first network device receives sixth information from the second node, and the sixth information is used to request re-configuration of the QoS of the second node; the above first network device switches the second QoS configuration used by the second node to perform the second task to an alternative QoS configuration, including: the first network device switches the second QoS configuration used by the second node to perform the second task to an alternative QoS configuration based on the above sixth information.

[0040] Exemplarily, the sixth information includes at least one of the following information:

[0041] The indication information of the second QoS configuration of the above-mentioned second node, and the third parameter of the changed QoS configuration, the third parameter including at least one information of 6QI, ARP, FBR, and FLOPS.

[0042] Through the above method, when the status of the second node is abnormal, the second node can report the expected QoS configuration parameter value to the first network device, which helps the first network device switch to the required QoS configuration as soon as possible and improve the efficiency of QoS configuration.

[0043] If the second node still cannot meet the alternative QoS configuration or the resources of the second node after using the alternative QoS configuration are still redundant, the above method also includes: the first network device sends eighth information to the first network function, and the eighth information is used to request a change in the QoS policy.

[0044] Exemplarily, the first network device is a base station, or the first network device is a CU, or the first network device is a cNode.

[0045] Through the above method, when the status of the execution node of the second task is abnormal, a request can be made to change the current QoS policy, which is beneficial to the dynamic adjustment and closed-loop guarantee of the QoS policy.

[0046] In a third aspect, a QoS policy generation method is provided, which can be executed by a second network function, or by a module (such as a chip or circuit) in the second network function, or by a logical node, logical module or software that can implement all or part of the second network function. This application does not limit this.

[0047] The method includes: a second network function sends second information to a first network function, the second information including a service type of each node in at least one node, the at least one node is a node served by the first network function, the second information is used by the first network function to determine a first QoS policy for the first service, the first QoS policy including a QoS requirement for at least one sixth node to complete the first service, the at least one sixth node belonging to the at least one node.

[0048] This application adds a second network function that can provide the service types subscribed to by the network nodes served by the first network function, which is used by the first network function to generate a QoS policy for the triggered service. The above method can realize the generation of QoS policy in AI4NET application scenarios.

[0049] In conjunction with the third aspect, in certain implementations of the third aspect, the second information further includes at least one of the following information:

[0050] The node type of each node in at least one node, the service priority of the service type of each node in at least one node, the computing power type, algorithm type, data type, connection topology that each node in at least one node can provide, the computing power resources, algorithm resources, data resources, air interface resources, connection quality, etc. that each node in at least one node can provide.

[0051] Exemplarily, the node type of each node in the above-mentioned at least one node and the service priority of the service type of each node in the at least one node included in the above-mentioned second information can be considered as the subscription information of at least one node, and the computing power type, algorithm type, data type, connection topology, computing power resources, algorithm resources, data resources, air interface resources, connection quality, etc. that each node in the at least one node can provide included in the above-mentioned second information can be considered as the capability information of at least one node, and this application does not limit this.

[0052] In combination with the third aspect, in certain implementations of the third aspect, the above method also includes: the second network function sends third information to the first node, where the third information is used to indicate the first network function corresponding to the first node, and the first node is the triggering node of the first service.

[0053] The third information is also used to indicate multiple candidate first network functions.

[0054] In combination with the third aspect, in certain implementations of the third aspect, the second network function periodically updates information included in the second information.

[0055] Alternatively, the second network function periodically updates subscription information of at least one node and / or capability information of at least one node.

[0056] This application does not limit the period for the second network function to update the subscription information of at least one node and / or the capability information of at least one node.

[0057] Through the above method, the second network function can dynamically maintain the stored subscription information and / or capability information of the network node.

[0058] In combination with the third aspect, in certain implementations of the third aspect, the above-mentioned first network function can be deployed in the base station, or the above-mentioned first network function can be deployed on the CU, or the above-mentioned first network function can be deployed on the cNode.

[0059] In a fourth aspect, a communication device is provided, comprising: a transceiver unit for receiving first information from a first node, the first information being used to indicate a first service triggered by the first node; the transceiver unit is also used to receive second information from a second network function, the second information including a service type of each node in at least one node, the at least one node being the node served by the communication device; the communication device also comprises: a processing unit for determining a first QoS policy for the first service based on the first information and the second information, the first QoS policy including a QoS requirement for at least one sixth node to complete the first service, the at least one sixth node belonging to the at least one node mentioned above.

[0060] In combination with the fourth aspect, in certain implementations of the fourth aspect, the above-mentioned transceiver unit is also used to obtain the updated service type of the at least one node from each node in the at least one node; the above-mentioned processing unit is used to determine the first QoS policy of the first service based on the first information and the second information, including: the above-mentioned processing unit is also used to determine the first QoS policy of the first service based on the first information, the second information and the updated service type of each node in at least one node obtained from at least one node.

[0061] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information may include indication information of the first node and indication information of the first service.

[0062] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first information further includes a service requirement of the first node for the first service.

[0063] In conjunction with the fourth aspect, in certain implementations of the fourth aspect, the second information further includes at least one of the following information:

[0064] The node type of each node in at least one node, the service priority of the service type of each node in at least one node, the computing power type, algorithm type, data type, connection topology that each node in at least one node can provide, the computing power resources, algorithm resources, data resources, air interface resources, connection quality, etc. that each node in at least one node can provide.

[0065] In combination with the fourth aspect, in certain implementations of the fourth aspect, the above-mentioned communication device can be deployed in a base station, or the above-mentioned communication device can be deployed on a centralized unit (CU), or the above-mentioned communication device can be deployed on a cluster control node (cluster node, cNode).

[0066] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the above-mentioned communication device is deployed in a base station, or when the above-mentioned communication device is deployed on a CU, the above-mentioned processing unit is further used to decompose the first service into N tasks based on the above-mentioned first information and the above-mentioned second information and determine N QoS policies for the N tasks, and the N tasks correspond one-to-one to the N QoS policies; the above-mentioned transceiver unit is also used to send fourth information according to the second QoS policy, and the fourth information is used to instruct at least one second node to execute the second QoS configuration of the second task. The second QoS policy belongs to the above-mentioned N QoS policies, the second task belongs to the above-mentioned N tasks, and the second QoS policy is the QoS policy of the second task.

[0067] In combination with the fourth aspect, in certain implementations of the fourth aspect, the above-mentioned transceiver unit is also used to receive eighth information, which is used to request a change to the second QoS policy; the above-mentioned processing unit is also used to change the above-mentioned second QoS policy to a fifth QoS policy based on the eighth information; the above-mentioned transceiver unit is also used to send ninth information to at least one fourth node according to the fifth QoS policy item, and the ninth information is used to instruct at least one fourth node to perform the fourth QoS configuration of the second task.

[0068] Illustratively, the eighth information includes at least one of the following information:

[0069] The indication information of the second QoS configuration of each node in the above-mentioned at least one second node, and the first parameter of the changed QoS configuration, where the first parameter includes at least one of 6QI, ARP, FBR, FLOPS, etc.

[0070] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the first network function is deployed on a cNode, the processing unit is further used to decompose the first service into N tasks based on the first information and the second information and determine N QoS policies for the N tasks, and the N tasks correspond one-to-one to the N QoS policies; the transceiver unit is also used to send fifth information to the first cNode, and the fifth information is used to instruct at least one third node to execute a third QoS policy for a third task, and the fifth information is used for the first cNode to determine at least one fourth QoS policy corresponding to at least one third node, and the at least one third node corresponds one-to-one to at least one fourth QoS policy. The third QoS policy includes the QoS requirements for at least one third node to complete the third task, the third QoS policy belongs to the N QoS policies, the third task belongs to the N tasks, and the third QoS policy is the QoS policy for the third task.

[0071] In combination with the fourth aspect, in certain implementations of the fourth aspect, the above-mentioned transceiver unit is also used to receive thirteenth information, which is used to request a change to the third QoS policy; the above-mentioned processing unit is also used to change the above-mentioned third QoS policy to a sixth QoS policy based on the thirteenth information; the above-mentioned transceiver unit is also used to send fourteenth information to the second cNode according to the sixth QoS policy, and the fourteenth information is used to indicate at least one seventh QoS policy corresponding to at least one fifth node, and the at least one fifth node corresponds one-to-one to the at least one seventh QoS policy.

[0072] Illustratively, the thirteenth information includes at least one of the following information:

[0073] The indication information of the third QoS configuration of each node in the above-mentioned at least one third node, and the second parameter of the changed QoS configuration, where the second parameter includes at least one of 6QI, ARP, FBR, FLOPS, etc.

[0074] In the fifth aspect, a communication device is provided, which includes: a processing unit for determining that the state of a second node used to perform a second task is abnormal; the processing unit is also used to switch the second QoS configuration used by the second node to perform the second task to an alternative QoS configuration; the above-mentioned communication device also includes: a transceiver unit for sending seventh information to the second node, and the seventh information is used to indicate the alternative QoS configuration.

[0075] Exemplarily, the abnormal state of the second node includes: the second node cannot meet the second QoS configuration or the resource redundancy of the second node, etc.

[0076] In combination with the fifth aspect, in certain implementations of the fifth aspect, the above-mentioned transceiver unit is also used to receive sixth information from the second node, and the sixth information is used to request reconfiguration of the QoS of the second node; the above-mentioned processing unit is used to switch the second QoS configuration used by the second node to perform the second task to an alternative QoS configuration, including: the above-mentioned processing unit is used to switch the second QoS configuration used by the second node to perform the second task to an alternative QoS configuration based on the above-mentioned sixth information.

[0077] Exemplarily, the sixth information includes at least one of the following information:

[0078] The indication information of the second QoS configuration of the above-mentioned second node, and the third parameter of the changed QoS configuration, the third parameter including at least one information of 6QI, ARP, FBR, and FLOPS.

[0079] If the second node still cannot meet the alternative QoS configuration or the resources of the second node after using the alternative QoS configuration are still redundant, the above-mentioned transceiver unit is also used to send eighth information to the first network function, and the eighth information is used to request a change in the QoS policy.

[0080] Exemplarily, the communication device is a base station, or the communication device is a CU, or the communication device is a cNode.

[0081] In a sixth aspect, a communication device is provided, comprising: a transceiver unit for sending second information to a first network function, the second information including the service type of each node in at least one node, the at least one node being the node served by the first network function, the second information being used by the first network function to determine a first QoS policy for the first service, the first QoS policy including at least one sixth node to complete the QoS requirements for the first service, the at least one sixth node belonging to the at least one node mentioned above.

[0082] In conjunction with the sixth aspect, in certain implementations of the sixth aspect, the second information further includes at least one of the following information:

[0083] The node type of each node in at least one node, the service priority of the service type of each node in at least one node, the computing power type, algorithm type, data type, connection topology that each node in at least one node can provide, the computing power resources, algorithm resources, data resources, air interface resources, connection quality, etc. that each node in at least one node can provide.

[0084] In combination with the sixth aspect, in certain implementations of the sixth aspect, the above-mentioned transceiver unit is also used to send third information to the first node, where the third information is used to indicate the first network function corresponding to the first node, and the first node is the triggering node of the first service.

[0085] The third information is also used to indicate multiple candidate first network functions.

[0086] In combination with the sixth aspect, in certain implementations of the sixth aspect, the above-mentioned communication device also includes: a processing unit, used to periodically update the information included in the second information.

[0087] Alternatively, the communication device periodically updates subscription information of at least one node and / or capability information of at least one node.

[0088] In combination with the sixth aspect, in certain implementations of the sixth aspect, the above-mentioned first network function can be deployed in the base station, or the above-mentioned first network function can be deployed on the CU, or the above-mentioned first network function can be deployed on the cNode.

[0089] In the seventh aspect, a communication device is provided, comprising a processor, wherein the processor is used to cause the communication device to perform the method described in the first aspect and any possible embodiment of the first aspect, or to cause the communication device to perform the method described in the second aspect and any possible embodiment of the second aspect, or to cause the communication device to perform the method described in the third aspect and any possible embodiment of the third aspect, by executing a computer program or instruction or through a logic circuit.

[0090] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.

[0091] In a possible implementation, the communication device further includes a communication interface, which is used to input and / or output signals.

[0092] In an eighth aspect, a communication device is provided, comprising a logic circuit and an input / output interface, the input / output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect and any possibility of the first aspect, or to execute the method described in the second aspect and any possibility of the second aspect, or to execute the method described in the third aspect and any possibility of the third aspect.

[0093] In the ninth aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect and any possibility of the first aspect is executed, or the method described in the second aspect and any possibility of the second aspect is executed, or the method described in the third aspect and any possibility of the third aspect is executed.

[0094] In the tenth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect and any possible method of the first aspect to be executed, or cause the method described in the second aspect and any possible method of the second aspect to be executed, or cause the method described in the third aspect and any possible method of the third aspect to be executed.

[0095] In the eleventh aspect, a communication system is provided, which includes the above-mentioned first network function and / or the above-mentioned second network function and / or the above-mentioned first network device, the first network function is used to execute the method described in the above-mentioned first aspect and any possibility of the first aspect, the second network function is used to execute the method described in the above-mentioned second aspect and any possibility of the second aspect, and the first network device is used to execute the method described in the above-mentioned third aspect and any possibility of the third aspect.

[0096] For the relevant explanations and descriptions of the beneficial effects of the fourth to eleventh aspects, please refer to the descriptions of the first to third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0097] FIG1 shows a schematic diagram of a communication system 100 applicable to an embodiment of the present application.

[0098] FIG2 shows a schematic flow chart of a QoS policy generation method 200 provided in this application.

[0099] FIG3 shows a schematic diagram of a network architecture 1 applicable to an embodiment of the present application.

[0100] FIG4 shows a schematic diagram of a second network architecture applicable to an embodiment of the present application.

[0101] FIG5 shows a schematic diagram of a third network architecture applicable to an embodiment of the present application.

[0102] FIG6 shows a schematic flow chart of a QoS policy generation method 300 provided in this application.

[0103] FIG7 shows a schematic flow chart of a QoS policy generation method 400 provided in this application.

[0104] FIG8 shows a schematic flow chart of a QoS policy changing method 500 provided in this application.

[0105] FIG9 shows a schematic flow chart of a QoS policy changing method 600 provided in this application.

[0106] FIG10 is a schematic block diagram of a communication device 1000 applicable to an embodiment of the present application.

[0107] FIG11 is a schematic block diagram of a communication device 1100 applicable to an embodiment of the present application.

[0108] FIG12 is a schematic block diagram of a communication device 1200 applicable to an embodiment of the present application. DETAILED DESCRIPTION

[0109] The technical solution in this application will be described below with reference to the accompanying drawings.

[0110] The technical solution provided in this application can be applied to communication systems such as 6G.

[0111] As an example, Figure 1 shows a schematic architecture diagram of a communication system, which may include terminal equipment (also referred to as user equipment (UE)), RAN equipment, core network (CN) equipment, etc.

[0112] A terminal device in this application may be referred to as an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0113] The terminal device can be a device that provides voice / data to users, for example, a handheld device or vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0114] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0115] In addition, in the embodiment of the present application, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0116] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to implement the function, such as a chip system or chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0117] It should be noted that the terminal device and the RAN device can communicate with each other using a certain air interface technology. The terminal devices can also communicate with each other using a certain air interface technology.

[0118] The term "RAN device" in this application refers to a device that provides access to a communications network for authorized users in a specific area. Specifically, it may include wireless network devices in a 3rd Generation Partnership Project (3GPP) network or access points in a non-3GPP network. For ease of description, the term "RAN device" will be used below.

[0119] RAN equipment can adopt different wireless access technologies. There are currently two types of wireless access technologies: 3GPP access technology (for example, the wireless access technology adopted in the fifth generation (5rd generation, 5G) system or 6G system) and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standard specifications. For example, the RAN equipment in the 5G system is called the next generation Node Base station (gNodeB), and the RAN equipment in the 6G system is called the cluster node (cNode) and the serving node (sNode). Non-3GPP access technologies may include air interface technologies represented by access points (APs) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. RAN equipment can allow terminal devices and the 3GPP core network to interconnect and communicate using non-3GPP technologies.

[0120] RAN equipment is responsible for radio resource management, quality of service (QoS) management, data compression and encryption, and other functions on the air interface side. RAN equipment provides access services to terminal devices and forwards control signals and user data between terminal devices and the core network.

[0121] RAN equipment may include, for example, but is not limited to: a macro base station, a micro base station (also known as a small station), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc. It may also be a gNodeB or a transmission point (TRP or TP) in a 5G (e.g., NR) system, one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G system, or a network node constituting a gNodeB or a transmission point, such as a distributed unit (DU), or a base station in a next-generation communication 6G system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the RAN equipment.

[0122] In addition to providing basic connectivity services, the RAN equipment provided in this application also needs to provide AI services to effectively enable AIaaS in future communication systems. Therefore, future communication systems need to achieve the provision of AI services through the collaborative capabilities of heterogeneous resources (connectivity, computing, AI data, AI models, etc.), which will drive the evolution of future RAN architectures.

[0123] Among them, the process of achieving a specific goal through the collaboration of heterogeneous resources at the network level is defined as a "task". In other words, a task refers to the process of collaborating heterogeneous resources such as computing, algorithms, connections and data to achieve a specific goal.

[0124] It should be noted that the "task" defined in this application is different from the connection task. The connection task is usually that the user establishes a connection session with the core network network function through the wireless access network, thereby establishing a channel for the user to transmit data and allocating corresponding connections and air interface resources, so that data can be transmitted between the user and the external network. The task in this application refers to the process of achieving the goal by coordinating various heterogeneous resources in order to provide various new services (for example, AI services) to users or network nodes.

[0125] Currently, the QoS policy generation mechanism in 5G communication systems is as follows: the application function (AF) provides the policy control function (PCF) on the core network side with application layer service requirements. These application layer service requirements generally include service QoS requirements (for example, bandwidth requirements, service type, etc.). The PCF combines the application layer service requirements, its own pre-configured information, and information obtained from various network functions in the core network (for example, session management function (SMF), access and mobility management function (AMF), charging function (CHF), network data analytics function (NWDAF), unified data repository (UDR), etc.) to generate policy and charging control (PCC) rules. These PCC rules are generally at the service data flow (SDF) granularity.

[0126] The PCF generates PCC rules and passes them to the SMF. The SMF combines the PCC rules, its own configuration information, and the user registration information obtained from the UDR to bind the PCC rules to the corresponding QoS flow. The QoS flow is used to transmit SDFs classified according to the PCC rules. A QoS flow may correspond to multiple PCC rules, meaning that a single QoS flow can be used to transmit multiple SDFs with the same QoS requirements. The QoS flow is the minimum granularity for 5G QoS management.

[0127] The SMF passes packet detection rules (PDR) and QoS enforcement rules (QER) to the user plane function (UPF). Based on these rules, the UPF identifies the SDF and assigns it to the specified QoS flow.

[0128] The SMF delivers the QoS Profile to the RAN, which then maps the QoS flow to the data radio bearer (DRB).

[0129] The SMF delivers QoS rules to the user, which enables the user to identify the SDF and determine the QoS flow corresponding to the SDF, and complete the mapping between the QoS flow and the DRB.

[0130] The introduction of AIaaS into the 6G communication system brought about two types of application scenarios: NET4AI and AI4NET. In the AI4NET application scenario, operators (for example, core network equipment and / or access network equipment) can act as service providers, and each node within the network (for example, terminal equipment or RAN equipment) can be both a service enabler and a service consumer. The network only needs to generate QoS policies based on information from each node within the network. When generating the QoS policy of the current 5G communication system, a third-party server is required to provide the application layer service requirements to the PCF on the core network side. Therefore, the QoS policy generation mechanism of the current 5G communication system cannot be applied to the AI4NET application scenario.

[0131] Based on the above technical status, the present application provides a QoS policy generation method 200, which can be applied in AI4NET application scenarios, but is not limited to this application scenario.

[0132] FIG2 is a schematic flowchart of a QoS policy generation method 200 provided in an embodiment of the present application.

[0133] In this embodiment, the method is illustrated by taking the first node, the first network function, and the second network function as the execution entities of the interaction diagram as examples, but this application does not limit the execution entities of the interaction diagram. For example, the first network function in Figure 2 can also be a chip, a chip system, or a processor that supports the method that can be implemented by the first network function, or it can be a logic module or software that can implement all or part of the first network function.

[0134] The QoS policy generation method 200 may include the following steps:

[0135] In step S210, the second network function sends third information to the first node, where the third information is used to indicate the first network function corresponding to the first node. Correspondingly, the first node receives the third information from the second network function.

[0136] Specifically, the first node is a triggering node of a first service. Exemplarily, the first service may be an AI service.

[0137] Specifically, the first node is used to trigger the first service, and the first node may also be a trigger source of the first service. Exemplarily, the first node may be a terminal device or a RAN device in the network, which is not limited in this application.

[0138] In step S212, the first node sends first information to the first network function based on the third information, where the first information is used to indicate the first service triggered by the first node. Accordingly, the first network function receives the first information from the first node.

[0139] The first information may include indication information of the first node and indication information of the first service. Exemplarily, the indication information of the first node may be an identifier of the first node, and the indication information of the first service may be a service identifier (service ID) of the first service.

[0140] Optionally, if the first node has other requirements for the triggered first service, the first information may further include the service requirements of the first node for the first service. Exemplarily, the service requirements of the first node for the first service included in the first information include at least one of the following information:

[0141] The transmission bandwidth requirement, the area scale requirement involved in the first service, or the node scale requirement involved in the first service. The area scale involved in the first service may be the size of the area involved in the first service, and the node scale involved in the first service may be the number of nodes that complete the first service.

[0142] In step S214, the second network function sends second information to the first network function, where the second information includes a service type of each node in the at least one node. Accordingly, the first network function receives the second information from the second network function.

[0143] Specifically, the second network function is used to store the service type of each node in the network. Exemplarily, the second network function may be an endpoint management function (EMF). The second network function may also be named other names. This application does not limit the specific name of the second network function.

[0144] The at least one node is a node served by the first network function, or the at least one node is a node in an area where the first network function is located. The first node is one of the at least one node.

[0145] Exemplarily, the service type of each node in the at least one node mentioned above can be AI data service, AI training service, AI verification service, AI reasoning service, high-precision positioning service, etc., which is not limited in this application.

[0146] Step S216: The first network function determines a first QoS policy for the first service based on the first information and the second information.

[0147] Specifically, the first network function is used to generate a QoS policy for the AI ​​service. Exemplarily, the first network function may be a PCF, or may be another name. This application does not limit the specific name of the first network function.

[0148] The first QoS policy includes at least one sixth node completing the QoS requirement of the first service, and the at least one sixth node belongs to the at least one node.

[0149] Exemplarily, the QoS requirement for the at least one sixth node included in the first QoS policy to complete the first service includes at least one of the following parameters:

[0150] 6G QoS indicator (6QI), allocation and retention priority (ARP), flow bit rate (FBR), floating point operations per second (FLOPS), etc.

[0151] Illustratively, the at least one sixth node may be part of or all of the at least one node, which is not limited in this application.

[0152] In one possible implementation, because the second network function periodically updates the information included in the second information, which may not be updated in real time, the first QoS policy for the first service determined by the first network function based on the first information and the second information may not be very accurate. Therefore, the first network function may obtain the updated service type of each of the at least one node from the at least one node, thereby enabling the first network function to determine the first QoS policy for the first service based on the first information, the second information, and the updated service type of the at least one node obtained from the at least one node, thereby improving the accuracy of the first QoS policy.

[0153] The second network function periodically updates the second information, including information such as the service type of at least one node, every 24 hours. For example, the second network function updates the service type of at least one node at 12:00 PM on the 1st, 12:00 PM on the 2nd, and 12:00 PM on the 3rd. Therefore, the second information received by the first network function from the second network function between 12:00 PM on the 1st and 12:00 PM on the 2nd includes the same service type of at least one node. However, as time passes from 12:00 PM on the 1st to 12:00 PM on the 2nd, the number of nodes in the at least one node whose service type changes may gradually increase, making the first QoS policy determined by the first network function inaccurate. Therefore, when the second network device has been updated for a long time since the last update of the service type of at least one node (for example, more than 12 hours have passed since the last update), the first network function obtains the real-time updated service type of each node in the at least one node from the at least one node.

[0154] The service type of the at least one node obtained by the first network function from the at least one node may be different from the service type of the at least one node obtained by the first network function from the second network function. In this case, the first network function determines the first QoS policy based on the real-time service type of the at least one node obtained from the at least one node. The first network function may also learn the period at which the second network function updates the service type of the at least one node.

[0155] The QoS policy generation method 200 provided in this application adds a second network function, which can store the service type subscribed by each node in the network, and can be used as the information input for the first network function to generate QoS policies for AI services triggered by trigger sources in the network, thereby realizing the generation of QoS policies in AI4NET application scenarios.

[0156] The first network function in the above-mentioned QoS policy generation method 200 may be deployed to a RAN device, so that the first network function may obtain real-time status information of at least one node.

[0157] The following embodiments use the RAN device as an xNodeB and the first network function as a PCF to illustrate how the first network function is deployed on the RAN device. For simplicity, the following embodiments refer to the first network function deployed on the RAN device as RAN-PCF. Taking the 6G communication system as an example, the RAN-PCF provided in this application can be deployed on the xNodeB of the following three network architectures:

[0158] Network architecture 1: The RAN-PCF is built into the xNodeB, and the RAN-PCF and xNodeB are integrated into a unified resource control entity.

[0159] As shown in Figure 3, network architecture 1 exemplarily includes three xNodeBs: xNodeB1, xNodeB2, and xNodeB3. xNodeB1 is wirelessly connected to UE1, xNodeB2 is wirelessly connected to UE2, and xNodeB3 is wirelessly connected to UE3 and UE4. The RAN-PCF can be deployed within xNodeB1 and can serve xNodeB1, xNodeB2, and xNodeB3.

[0160] Alternatively, the RAN-PCF may be deployed in the xNodeB2 and / or xNodeB3 shown in FIG3 , which is not limited in this application.

[0161] Network Architecture 2: In some possible scenarios, an xNodeB may include multiple xNodeB nodes, and the RAN-PCF is deployed on the xNodeB node. For example, an xNodeB node may be a centralized unit (CU) or a distributed unit (DU), and multiple DUs may be centrally controlled by one CU. The CU implements some of the functions of the xNodeB, and the DU implements some of the functions of the xNodeB. For example, the CU and DU may be divided according to the protocol layer functions of the wireless network they possess. For example, the functions of the packet data convergence protocol (PDCP) layer and above protocol layers (for example, the radio resource control (RRC) layer) are set in the CU, and the functions of the protocol layers below the PDCP, such as the radio link control (RLC) layer, the medium access control (MAC) layer, and the physical (PHY) layer, are set in the DU. It should be noted that this division of the protocol layers is only an example, and division can also be performed at other protocol layers. In addition, in some embodiments, the CU control plane (CU control plan, CU-CP) and the CU user plane (CU user plan, CU-UP) of the CU can be separated and implemented as different entities, namely the CU-CP entity and the CU-UP entity. In this network architecture 2, the signaling generated by the CU can be sent to the UE via the DU, or the signaling generated by the UE can be sent to the CU via the DU. The DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the UE or CU without parsing it.

[0162] For example, as shown in Figure 4(a), an xNodeB may include nodes CU1 and DU1, or nodes CU2, DU2, and DU3. CU1 transmits information to UE1 via DU1, CU2 transmits information to UE2 via DU2, and CU2 transmits information to UE3 via DU3. The RAN-PCF may be deployed on CU1 and may serve both CU1 and CU2.

[0163] Alternatively, the RAN-PCF may also be deployed on CU2 shown in (a) of FIG4 , which is not limited in this application.

[0164] As another example, as shown in Figure 4(b), the xNodeB can also be an open access network (ORAN). In an ORAN system, the CU and DU described above can have different names. For example, the CU in the ORAN system can be an open CU (O-CU), and the DU in the ORAN system can be an open DU (O-DU). Furthermore, in some embodiments, the O-CU control plane (O-CU control plan, O-CU-CP) and the O-CU user plane (O-CU user plan, O-CU-UP) can be separated and implemented as separate entities, namely the O-CU-CP entity and the O-CU-UP entity. In this second network architecture, signaling generated by the O-CU can be sent to the UE via the O-DU, or signaling generated by the UE can be sent to the O-CU via the O-DU. The O-DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the UE or O-CU without parsing it. Alternatively, signaling generated by the O-CU-CP can be sent to the UE via the O-DU, or signaling generated by the UE can be sent to the O-CU-CP via the O-DU. The O-DU may not parse the signaling but directly encapsulate it through the protocol layer and transparently transmit it to the UE or O-CU; alternatively, the signaling generated by the O-CU-CP may be sent to the O-DU through the O-CU-UP, and then sent to the UE by the O-DU, or the signaling generated by the UE may be sent to the O-CU-UP through the O-DU, and then sent to the O-CU-UP by the O-CU-UP. The xNodeB shown in Figure 4(b) may include O-CU1-CP, O-CU1-UP, O-CU2-CP, O-CU2-UP, O-DU1, and O-DU2 nodes. Among them, the O-CU1-CP can transmit information to UE1 through O-DU1, and the O-CU2-CP can transmit information to UE2, UE3, and UE4 through O-DU2. The RAN-PCF can be deployed on the O-CU1-CP. And the RAN-PCF can serve the O-CU1-CP and O-CU2-CP.

[0165] Alternatively, the RAN-PCF may also be deployed on the O-CU2-CP shown in (b) of FIG4 , which is not limited in this application.

[0166] In addition, FIG4(b) also includes a near real time RAN intelligent controller (near real time RIC) for controlling real-time service transmission.

[0167] In another example, as shown in FIG4( c ), the RAN-PCF may be deployed on the near real-time RIC and may serve the O-CU1-CP and the O-CU2-CP.

[0168] The deployment method shown in Figure 4(b) is applicable to scenarios where the various units in the ORAN system are centrally deployed. In this deployment method, the RAN-PCF can coordinate with more nodes when generating QoS policies. The deployment method shown in Figure 4(c) is applicable to scenarios where the various units in the ORAN system are dispersed. In this deployment method, the RAN-PCF has a better latency in obtaining real-time status information of the served nodes.

[0169] Network Architecture 3: In the task-centric architecture, task anchors (TAs) and task executors (TEs) are introduced. TAs and TEs manage tasks and support task lifecycle management. They ensure the QoS and smooth execution of tasks through the coordination and deployment of computing, algorithms, connections, and data.

[0170] TA can also be understood as the control plane function, and TE is the data processing function. TA is used to provide task management and control functions. The control function may include being responsible for the lifecycle management of the task, completing task deployment, startup, deletion, modification, monitoring, etc. based on the requirements of the task, and regulating network resources to ensure the requirements of the task. In addition to the control function, the management and control function also has the function of selecting the control function. For example, a node with a management and control function can select another node to perform the control function of the task. TE is responsible for the execution of the task and performs data interaction in business logic. This application does not limit the specific names of the TA responsible for the control plane function and the TE responsible for the data processing function.

[0171] To achieve the above task structure, this application proposes a hierarchical xNodeB architecture that can more efficiently provide AI services. Figure 5(a) shows a schematic diagram of the overall network architecture applicable to this hierarchical xNodeB architecture. This network architecture can include 6GC and a hierarchical xNodeB architecture.

[0172] The hierarchical xNodeB architecture introduces a centralized coordinating node to provide task coordination within and between regions. For example, the hierarchical xNodeB architecture includes cluster control nodes (cNodes) and service serving nodes (sNodes), which together form an xNodeB.

[0173] cNode: Provides regional centralized coordination of multiple sNodes and cross-regional cNode coordination. Within a cluster, it provides a task anchor. On the air interface, it does not provide connection functionality, or only provides connection control.

[0174] sNode: Business service node, provides task scheduling and execution functions; on the air interface, provides connection and / or data functions.

[0175] Optionally, this application does not limit the specific names of the cNode responsible for providing the regional centralized coordination function of multiple sNodes and the sNode responsible for providing the scheduling and execution functions of the tasks. For example, cNode and sNode are respectively referred to as network elements (NEs), without limitation. If the functions of cNode and sNode are split (microservice architecture is adopted within the base station), the network functions within cNode and sNode can be further defined.

[0176] The cNode can be responsible for task-based control plane functions (such as TA) and data processing functions (for example, when the cNode has computing power, it can also deploy a task scheduler (TS) and TE to perform data processing tasks). The sNode is responsible for some task-based control plane and user plane functions, such as TS and TE.

[0177] In this network architecture, different nodes communicate through interfaces. For example, cNodes and sNodes are connected to each other through the Y1 interface, cNodes are connected to each other through the Y2 interface, and sNodes are connected to each other through the Y3 interface. For another example, a cNode can connect to the 6GC through the Tx interface. Specifically, it can connect to the network access function (NAF) through the T3 interface, connect to the connection control plane function (CF-C) through the T4 interface, and connect to the task control function (TCF) / task process function (TPF) through the T2 interface. For another example, an sNode can connect to the 6GC through the Ty interface. Specifically, it can connect to the NAF through the T5 interface, connect to the CF-C through the T6 interface, and connect to the user plane function (CF-U) through the T7 interface.

[0178] The above interface names are only for illustrative purposes, and the embodiments of the present application do not limit the names of the above interfaces.

[0179] The RAN-PCF can be deployed on the cNode described in Figure 5(a), as shown in Figure 5(b). For example, the hierarchical xNodeB in Figure 5(b) may include cNode1, cNode2, cNode3, and sNode1. cNode1 is connected to UE1, cNode2 is connected to UE2, and cNode3 is connected to UE3 and sNode1. cNode1, cNode2, and cNode3 provide TA, while sNode1, UE1, UE2, and UE3 provide TS and TE. The RAN-PCF can be deployed on cNode1 in Figure 5(b).

[0180] Alternatively, the RAN-PCF may also be deployed on cNode2 and / or cNode3 as shown in FIG5( b ), which is not limited in this application.

[0181] The above details the deployment of the RAN-PCF in different network architectures. The following describes the QoS policy generation method 200 provided by the present application in detail, taking the above three network architectures as examples. The following embodiments are described using the second network function as an EMF as an example.

[0182] The QoS policy generation method 300 described below is applicable to the above-mentioned network architecture 1 and the above-mentioned network architecture 2, and the QoS policy generation method 400 described below is applicable to the above-mentioned network architecture 3. First, the QoS policy generation method 300 is introduced. As shown in the schematic flow chart of Figure 6, the QoS policy generation method 300 may include the following steps:

[0183] Step S310: The first node triggers the first service.

[0184] In step S314, the EMF sends third information to the first node, where the third information indicates the RAN-PCF corresponding to the first node, which is denoted as RAN-PCF#1. Accordingly, the first node receives the third information from the EMF.

[0185] Optionally, the third information is further used to indicate a candidate RAN-PCF, denoted as RAN-PCF#2. When the first node cannot connect to RAN-PCF#1, it may attempt to connect to RAN-PCF#2. The first information may also indicate more candidate RAN-PCFs, which is not limited in this application.

[0186] Exemplarily, the third information may indicate RAN-PCF#1 through the mapping table in Table 1 below. Taking the network architecture 1 as an example, the mapping table may be represented by Table 1 below:

[0187] Table 1

[0188] As can be seen from Table 1 above, the RAN-PCF corresponding to at least one node in network architecture 1 is deployed on xNodeB1. The first node can be any of xNodeB1, xNodeB2, xNodeB3, UE1, UE2, UE3, and UE4 in network architecture 1. The first node can determine, based on the third information, that the RAN-PCF corresponding to the first node is RAN-PCF#1.

[0189] Optionally, before the above step S314, step S312 may be further included, in which the first node requests the EMF to obtain the RAN-PCF corresponding to the first node, or the first node requests to obtain a list of RAN-PCFs corresponding to the first node.

[0190] Step S316: The first node sends first information to RAN-PCF#1 based on the third information, where the first information is used to indicate the first service triggered by the first node. Accordingly, RAN-PCF#1 receives the first information from the first node.

[0191] The first information may include indication information of the first node and indication information of the first service. The first service may include multiple services, in which case the indication information of the first service is a collection of indication information of the multiple services. Exemplarily, the indication information of the first node is an identifier of the first node, the indication information of the first service is a service identifier of the first service, and the collection of indication information of the multiple services is a collection of service identifiers of the multiple services.

[0192] Optionally, if the first node has other requirements for the triggered first service, the first information may further include the service requirements of the first node for the first service.

[0193] Step S318: EMF sends second information to RAN-PCF#1, where the second information includes the service type of each node in the at least one node. Correspondingly, RAN-PCF#1 receives the second information from EMF.

[0194] Exemplarily, the service type of each node in the above-mentioned at least one node may be one or more of AI data service, AI training service, AI verification service, AI reasoning service, high-precision positioning service, etc., which is not limited in this application.

[0195] Optionally, the second information may further include at least one of the following:

[0196] The node type of each node in the at least one node, the service priority of each node in the at least one node for the service type subscribed by each node in the at least one node, the computing power type, algorithm type, data type, connection topology, computing power resources, algorithm resources, data resources, etc., air interface resources, connection quality, etc. that each node in the at least one node can provide. Among them, the service type of each node in the at least one node, the node type of each node in the at least one node, the service priority of each node in the at least one node for the service type subscribed by each node in the at least one node, etc. included in the second information can be considered as subscription information of each node in the at least one node, and the computing power type, algorithm type, data type, connection topology, computing power resources, algorithm resources, data resources, etc., air interface resources, connection quality, etc. that each node in the at least one node can provide, included in the second information, can be considered as capability information of each node in the at least one node.

[0197] The above EMF is used to store subscription information, capability information, etc. of each node in the network.

[0198] Step S320: RAN-PCF#1 determines a first QoS policy for the first service based on the first information and the second information, thereby obtaining a service-level QoS policy.

[0199] The first QoS policy includes an overall QoS requirement for at least one sixth node to complete the first service, and the at least one sixth node belongs to the at least one node. The overall QoS requirement for at least one sixth node to complete the first service included in the first QoS policy includes at least one of the following parameters:

[0200] 6QI, ARP, FBR, FLOPS, etc.

[0201] Exemplarily, RAN-PCF#1 may preconfigure a template for the first service, and RAN-PCF#1 may call the preconfigured template for the first service according to the indication information of the first service, thereby quickly determining the service requirements corresponding to the first service. The template for the first service may also be preconfigured on the triggering source side of the first service (e.g., the first node side). For example, if the first service is an AI service, RAN-PCF#1 may preconfigure an AI service template and call the AI ​​service template according to the AI ​​service triggered by the first node.

[0202] Next, the first service needs to be orchestrated, decomposing the first service into N tasks. The orchestration of the first service can be performed by the network AI management and orchestration (NAMO) functional element on the management plane, or directly by the RAN-PCF#1.

[0203] Exemplarily, when the number of execution nodes of the first service involved in the above-mentioned first QoS policy is large, or the area where the execution nodes of the first service involved in the above-mentioned first QoS policy are located is large, the above-mentioned RAN-PCF#1 can send the determined above-mentioned first QoS policy to NAMO, requesting NAMO to orchestrate the above-mentioned first service; when the number of execution nodes of the first service involved in the above-mentioned first QoS policy is small, or the area where the execution nodes of the first service involved in the above-mentioned first QoS policy are located is small, the above-mentioned RAN-PCF#1 can directly orchestrate the above-mentioned first service, avoiding signaling interaction between RAN-PCF#1 and NAMO, and speeding up the service orchestration time.

[0204] Specifically, the service orchestration for the first service may include the following two methods:

[0205] Method 1: NAMO without involving the management plane, in which RAN-PCF#1 orchestrates the first service, specifically including step S322: RAN-PCF#1 decomposes the first service into N tasks based on the first information and the second information, and determines N QoS policies for the N tasks, thereby obtaining a task-level QoS policy. The N tasks correspond one-to-one to the N QoS policies, where N is a positive integer greater than 1.

[0206] The QoS policy corresponding to each of the N tasks includes a QoS requirement for some or all of the at least one sixth node to complete the task.

[0207] RAN-PCF#1 may also determine indication information of each of the N tasks and indication information of the execution node of each of the N tasks. For example, the indication information of each task may be an identifier of each task, and the indication information of the execution node of each task may be an identifier of the execution node of each task.

[0208] Method 2: Involving NAMO on the management plane, NAMO orchestrates the first service, specifically including steps S324 to S330.

[0209] In step S324, RAN-PCF#1 sends information #1 to NAMO, where the information #1 is used to request the orchestration of the first service. Correspondingly, NAMO receives the information #1 from RAN-PCF#1.

[0210] Specifically, the above information #1 includes the above first QoS policy.

[0211] Step S326: NAMO decomposes the first service into N tasks based on information #1 and determines N QoS policies for the N tasks.

[0212] NAMO can also determine the indication information of each task in the N tasks and the indication information of the execution node of each task in the N tasks. For example, the indication information of each task can be the identifier of each task, and the indication information of the execution node of each task can be the identifier of the execution node of each task.

[0213] In step S328, NAMO sends information #2 to RAN-PCF#1, where the information #2 includes the N QoS policies for the N tasks. Accordingly, RAN-PCF#1 receives information #2 from NAMO.

[0214] Compared with the above-mentioned method 2, the above-mentioned method 1 does not require NAMO of the management plane to perform service orchestration. Instead, RAN-PCF#1 directly performs service orchestration, which saves time for service orchestration.

[0215] In step S330, RAN-PCF#1 sends fourth information based on the second QoS policy, where the fourth information is used to instruct at least one second node to execute the second QoS configuration for the second task. The second QoS policy belongs to the N QoS policies, the second task belongs to the N tasks, and the second QoS policy is the QoS policy for the second task.

[0216] Exemplarily, RAN-PCF#1 sends fourth information to the second node#1A and the second node#2A according to the second QoS policy. The second node#1A and the second node#2A can be considered as the at least one second node.

[0217] Taking the network architecture 1 shown in FIG3 as an example, the second node #1A may be xNodeB2, and the second node #2A may be xNodeB3; alternatively, the second node #1A may be xNodeB1, and the second node #2A may be UE1; alternatively, the second node #1A may be xNodeB2, and the second node #2A may be UE2; alternatively, the second node #1A may be xNodeB3, and the second node #2A may be UE3 and / or UE4; alternatively, the second node #1A may be xNodeB1 and xNodeB2, and the second node #2A may be UE1 and UE2. This application does not limit this. When the second node #1A may be xNodeB2, and the second node #2A may be xNodeB3, the second QoS configuration indicated by RAN-PCF#1 to xNodeB2 is QoS configuration #1A, and the second QoS configuration indicated to xNodeB3 is QoS configuration #2A. The configuration parameters of QoS configuration #1A and the configuration parameters of QoS configuration #2A may be the same, partially the same, or completely different. In which, when the UE (for example, UE1, UE2, UE3 or UE4) is an execution node of the second task, the second QoS configuration of the UE can be directly configured by the RAN-PCF and transmitted to the UE through the xNodeB connected to the UE; or, the second QoS configuration of the UE can be generated by the xNodeB connected to the UE based on the second QoS configuration indicated by the RAN-PCF, which is not limited in this application.

[0218] Taking the network architecture 2 described in FIG4(a) as an example, the second node #1A may be CU1, and the second node #2A may be CU2; alternatively, the second node #1A may be CU1, and the second node #2A may be UE1, and this application does not limit this. When the second node #1A is CU1, and the second node #2A is CU2, the second QoS configuration indicated by RAN-PCF#1 to CU1 is QoS configuration #3A, and the second QoS configuration indicated to CU2 is QoS configuration #4A. The configuration parameters of QoS configuration #3A and the configuration parameters of QoS configuration #4A may be the same, partially the same, or completely different. Among them, when the UE (for example, UE1, UE2, UE3 or UE4) is an execution node of the second task, the second QoS configuration of the UE can be directly configured by the RAN-PCF, and transmitted to the UE through the CU and DU connected to the UE respectively; or, the second QoS configuration of the UE can be generated by the CU connected to the UE based on the second QoS configuration indicated by the RAN-PCF, and transmitted to the UE through the DU connected to the UE; or, the second QoS configuration of the UE can be generated by the DU connected to the UE based on the second QoS configuration indicated by the CU connected to the UE, and indicated to the UE. This application does not limit this.

[0219] Taking the network architecture 2 described in (b) of Figure 4 as an example, the second node #1A may be an O-CU1-CP, and the second node #2A may be an O-CU2-CP; or, the second node #1A may be an O-CU1-CP, and the second node #2A may be UE1, and this application does not limit this. When the second node #1A is an O-CU1-CP, and the second node #2A is an O-CU2-CP, the second QoS configuration indicated by RAN-PCF#1 to the O-CU1-CP is QoS configuration #5A, and the second QoS configuration indicated to the O-CU2-CP is QoS configuration #6A. The configuration parameters of the QoS configuration #5A and the configuration parameters of the QoS configuration #6A may be the same, partially the same, or not at all the same. Among them, when the UE (for example, UE1, UE2, UE3 or UE4) is an execution node of the second task, the second QoS configuration of the UE can be directly configured by the RAN-PCF, and transmitted to the UE through the O-CU and O-DU connected to the UE respectively; or, the second QoS configuration of the UE can be generated by the O-CU connected to the UE based on the second QoS configuration indicated by the RAN-PCF, and transmitted to the UE through the O-DU connected to the UE; or, the second QoS configuration of the UE can be generated by the O-DU connected to the UE based on the second QoS configuration indicated by the O-CU connected to the UE, and indicated to the UE. This application does not limit this.

[0220] The sending of the second QoS configuration of the network architecture 2 described in (c) of FIG. 4 is similar to the sending of the second QoS configuration of the network architecture 2 described in (b) of FIG. 4 above, and will not be repeated here.

[0221] Exemplarily, the fourth information may be a QoS control rule, and the second QoS configuration included in the QoS control rule includes at least one of the following parameters:

[0222] 6QI, ARP, FBR, FLOPS, etc.

[0223] Additionally, the QoS configuration #1A, QoS configuration #2A, QoS configuration #3A, QoS configuration #4A, QoS configuration #5A, and QoS configuration #6A also include at least one of the following configuration parameters:

[0224] 6QI, ARP, FBR, FLOPS, etc.

[0225] It should be noted that the above step S330 is only an example of the execution of the second task among N tasks. RAN-PCF#1 will also send information to the execution nodes corresponding to other tasks according to other strategies among the above N QoS strategies to instruct the execution of other tasks. This application will not go into details about this.

[0226] Through the above-mentioned QoS policy generation method 300, it can be seen that RAN-PCF#1 generates two-level QoS policies. The first level is the generation of service-level QoS policies, and the second level is the generation of task-level QoS policies. By generating two-level QoS policies, the service quality of the first service can be guaranteed.

[0227] Next, a QoS policy generation method 400 is introduced. As shown in the schematic flowchart of FIG7 , the QoS policy generation method 400 may include the following steps:

[0228] Steps S410 to S428 may refer to the above-mentioned steps S310 to S328 and will not be described in detail here.

[0229] In step S430, RAN-PCF#1 sends fifth information to the first cNode. This fifth information instructs at least one third node to execute a third QoS policy for a third task. The third QoS policy belongs to the N QoS policies, and the third task belongs to the N tasks. The third QoS policy is the QoS policy for the third task. Accordingly, the first cNode receives the fifth information from RAN-PCF#1.

[0230] The third QoS policy includes a QoS requirement for at least one third node to complete a third task. The QoS requirement for at least one third node to complete a third task included in the third QoS policy includes at least one of the following parameters:

[0231] 6QI, ARP, FBR, FLOPS, etc.

[0232] The fifth information may also carry indication information of the first service, indication information of the third task, indication information of at least one third node, etc. Exemplarily, the indication information of the first service is an identifier of the first service, the indication information of the third task is an identifier of the third task, and the indication information of the at least one third node is an identifier of the at least one third node.

[0233] It should be noted that the above step S430 is only an example of the execution of the third task among N tasks. RAN-PCF#1 will also send information to the cNode corresponding to other tasks according to other strategies among the above N QoS strategies to instruct the execution of other tasks. This application will not go into details one by one.

[0234] Step S432: The first cNode determines at least one fourth QoS policy corresponding to the at least one third node based on the fifth information, where the at least one third node corresponds to the at least one fourth QoS policy in a one-to-one manner.

[0235] Step S434: The first cNode sends information #3 to at least one third node according to at least one fourth QoS policy, where the information #3 is used to instruct the at least one third node to execute a third QoS configuration of a third task.

[0236] Exemplarily, the first cNode sends information #3 to the third node #1B based on QoS policy #1B. Information #3 is used to instruct the third node #1B to execute a third QoS configuration for a third task. QoS policy #1B belongs to the at least one fourth QoS policy. QoS policy #1B is the QoS policy corresponding to the third node #1B. The QoS requirements included in QoS policy #1B are requirements for certain resource elements (computing, algorithms, connections, or data) required for the third node #1B to execute the third task.

[0237] It should be noted that the above step S434 is only an example of the third node #1B performing the third task. The first cNode will also send information #3 to other third nodes according to other strategies in the above at least one fourth QoS strategy to instruct other third nodes to perform the third QoS configuration of the third task. This application will not go into details about this.

[0238] Taking the network architecture 3 shown in Figure 5 as an example, the first cNode may be cNode3, and the at least one third node may include sNode1 and UE3; alternatively, the first cNode may be cNode1, and the at least one third node may include UE1, although this application does not limit this. When the first cNode is cNode3 and the at least one third node includes sNode1 and UE3, cNode3 determines QoS policy #1B corresponding to sNode1 and QoS policy #2B corresponding to UE3 based on the third QoS policy. QoS policy #1B includes QoS requirements for sNode1 to complete the third task, and QoS policy #2B includes QoS requirements for UE3 to complete the third task. The QoS requirements included in QoS policy #1B are requirements for certain resource elements (computing, algorithms, connections, or data) used by sNode1 to perform the third task, while the QoS requirements included in QoS policy #2B are requirements for certain resource elements (computing, algorithms, connections, or data) used by UE3 to perform the third task, thereby obtaining resource-level QoS policies. The resource elements included in QoS policy #1B and QoS policy #2B may be different. The QoS policy #1B and QoS policy #2B herein are examples of the at least one fourth QoS policy.

[0239] Exemplarily, the information #3 sent by the first cNode to the sNode may be a QoS profile, and the information #3 sent by the first cNode to the UE may be QoS rules, which is not limited in this application.

[0240] It should be noted that the QoS requirements included in each of the above N QoS policies are requirements for the various resource elements (computing, algorithms, connections and data) required for each task, but the QoS requirements included in each of the above at least one QoS policy are generally requirements for a certain resource element (computing, algorithms, connections or data) required for each task.

[0241] The QoS policy generation method 400 described above generates a three-level QoS policy. The RAN-PCF generates two levels of QoS policy: the first level is for service-level QoS policy generation, and the second level is for task-level QoS policy generation. Based on this, the cNode generates a third-level resource-level QoS policy to ensure the quality of service for the first service.

[0242] The above describes a method for generating a QoS policy. When an execution node cannot meet the QoS configuration of the executed task or there is redundancy in the computing resources, algorithm resources, data resources, connection topology, etc. of the execution node, the QoS state of the execution node is abnormal, and the current QoS configuration of the execution node needs to be changed. Based on this, the present application can provide a method for changing a QoS policy. The QoS policy changing method 500 described below is applicable to the above-mentioned network architecture one and the above-mentioned network architecture two, and the QoS policy changing method 600 described below is applicable to the above-mentioned network architecture three. First, the QoS policy changing method 500 is introduced, as shown in the schematic flow chart of Figure 8.

[0243] In order to facilitate the explanation of the technical solution of the QoS policy change method 500, it is assumed that the execution of the QoS policy change method 500 is performed on the basis of the above-mentioned QoS policy generation method 300. It should be noted that the execution of the QoS policy change method 500 can also be performed on the basis of other QoS policy generation methods, and this application does not limit this. Assuming that the QoS status of UE2 in the network architecture 1 shown in Figure 3 is abnormal, the current QoS configuration of UE2 is the second QoS configuration, and the UE2 can be an example of at least one second node in the above-mentioned QoS policy generation method 300. Specifically, the QoS policy change method 500 may include the following steps:

[0244] There are two ways to report QoS status anomalies of UE2:

[0245] Method 1: Step S510 , xNodeB 2 serving UE 2 discovers that the QoS status of UE 2 is abnormal.

[0246] Method 2 includes the following steps S512 to S514:

[0247] Step S512: UE2 itself triggers a QoS status abnormality.

[0248] In step S514, UE2 sends sixth information to xNodeB2, where the sixth information is used to request reconfiguration of QoS. Correspondingly, xNodeB2 receives the sixth information from UE2.

[0249] Exemplarily, the sixth information may be carried in UE assistance information (UAI).

[0250] Illustratively, the sixth information includes at least one of the following information:

[0251] The indication information of the second QoS configuration of UE2 and the third parameter of the changed QoS configuration. The third parameter includes at least one of the following parameters:

[0252] 6QI, ARP, FBR, FLOPS. Exemplarily, the indication information of the second QoS configuration may be an identifier of the second QoS configuration.

[0253] Step S516: xNodeB2 switches the second QoS configuration of UE2 to the alternative QoS configuration.

[0254] Step S518: xNodeB2 sends seventh information to UE2, where the seventh information is used to indicate an alternative QoS configuration after the handover.

[0255] Exemplarily, the seventh information may be a QoS control rule, and the alternative QoS configuration included in the QoS control rule includes at least one of the following parameters:

[0256] 6QI, ARP, FBR, FLOPS, etc.

[0257] UE2 uses the alternative QoS configuration to perform the second task. When UE2 still cannot meet the alternative QoS configuration, the QoS policy changing method 500 further includes:

[0258] In step S520, xNodeB2 sends eighth information to RAN-PCF#1, where the eighth information is used to request to change the second QoS policy. Accordingly, RAN-PCF#1 receives the eighth information from xNodeB2.

[0259] Exemplarily, the eighth information includes at least one of the following parameters:

[0260] Indication information of the second QoS configuration of each node in at least one second node, and a first parameter of the desired changed QoS configuration, where the first parameter includes at least one information of 6QI, ARP, FBR, FLOPS, etc.

[0261] Step S522: RAN-PCF#1 changes the second QoS policy to a fifth QoS policy based on the eighth information.

[0262] In step S524, RAN-PCF#1 sends ninth information according to the fifth QoS policy. The ninth information is used to instruct at least one fourth node to perform the fourth QoS configuration of the second task. Step S524 here can refer to step S330 in the QoS policy generation method 300 and will not be repeated here.

[0263] Among them, at least one fourth node used to perform the second task after changing the QoS policy can be completely the same as, partially the same as, or different from, the at least one second node used to perform the second task before changing the QoS policy. This application does not limit this.

[0264] Next, the QoS policy change method 600 is introduced, as shown in the schematic flow chart of Figure 9. To facilitate the explanation of the technical solution of the QoS policy change method 600, it is assumed that the execution of the QoS policy change method 600 is performed on the basis of the above-mentioned QoS policy generation method 400. It should be noted that the execution of the QoS policy change method 600 can also be performed on the basis of other QoS policy generation methods, and this application does not limit this. Assume that the QoS status of UE2 in the network architecture 3 shown in Figure 5 is abnormal, and the current QoS configuration of UE2 is the third QoS configuration. The UE2 can be an example of at least one third node in the above-mentioned QoS policy generation method 400.

[0265] Specifically, the QoS policy changing method 600 may include the following steps:

[0266] There are two ways to report QoS status anomalies of UE2:

[0267] Method 1 includes the following steps S610 to S612:

[0268] Step S610: sNode2 serving UE2 discovers that the QoS status of UE2 is abnormal. Although sNode2 is not shown in the network architecture 3 shown in FIG5 , it can be considered that the network architecture 3 shown in FIG5 also includes sNode2 serving UE2.

[0269] In step S612, sNode2 sends a tenth message to cNode2, where the tenth message is used to request reconfiguration of QoS for UE2. Correspondingly, cNode2 receives the tenth message from sNode2.

[0270] Method 2 includes the following steps S614 to S616:

[0271] Step S614: UE2 itself triggers a QoS status abnormality.

[0272] Step S616: UE2 sends an eleventh message to cNode2, where the eleventh message is used to request reconfiguration of QoS. Correspondingly, cNode2 receives the eleventh message from UE2.

[0273] Exemplarily, the eleventh information may be carried in UE assistance information (UAI).

[0274] Illustratively, the eleventh information includes at least one of the following information:

[0275] The third QoS configuration indication information of UE2 and the fourth parameter of the changed QoS configuration. The fourth parameter includes at least one of the following parameters:

[0276] 6QI, ARP, FBR, FLOPS. Exemplarily, the indication information of the sixth QoS configuration may be the identifier of the third QoS configuration.

[0277] Step S618: cNode2 switches the third QoS configuration of UE2 to the alternative QoS configuration.

[0278] Step S620: cNode2 sends twelfth information to UE2, where the twelfth information is used to indicate an alternative QoS configuration after the handover.

[0279] Exemplarily, the twelfth information may be a QoS control rule (QoS control rules), and the alternative QoS configuration included in the QoS control rule includes at least one of the following parameters:

[0280] 6QI, ARP, FBR, FLOPS, etc.

[0281] UE2 uses the alternative QoS configuration to perform the second task. When the computing resources, algorithm resources, data resources, connection topology, etc. after UE2 uses the alternative QoS configuration still have redundancy, the QoS policy change method 600 further includes:

[0282] In step S624, cNode2 sends the thirteenth message to RAN-PCF#1, where the thirteenth message is used to request to change the third QoS policy. Accordingly, RAN-PCF#1 receives the thirteenth message sent by cNode2.

[0283] Illustratively, the thirteenth information includes at least one of the following information:

[0284] Indication information of the third QoS configuration of each node in at least one third node, and a second parameter of the expected changed QoS configuration, where the second parameter includes at least one parameter of 6QI, ARP, FBR, FLOPS, etc.

[0285] Step S626: RAN-PCF#1 changes the third QoS policy to a sixth QoS policy based on the thirteenth information.

[0286] In step S628, RAN-PCF#1 sends fourteenth information to cNode2, which is used to instruct at least one fifth node to execute the sixth QoS policy of the third task. Step S628 here can refer to step S430 in the QoS policy generation method 400, and will not be repeated here.

[0287] Among them, at least one fifth node used to perform the third task after changing the QoS policy can be completely the same as, partially the same as, or different from, the at least one third node used to perform the third task before changing the QoS policy. This application does not limit this.

[0288] For the subsequent steps, refer to steps S432 to S434 in the QoS policy generation method 400 .

[0289] Finally, the device embodiment of the embodiment of the present application is introduced.

[0290] To implement the various functions of the method provided herein, the first node, the first network function, and the second network function may each include hardware structures and / or software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular one of the aforementioned functions is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0291] Figure 10 is a schematic block diagram of a communication device 1000 according to an embodiment of the present application. The communication device 1000 includes a processor 1010 and a communication interface 1020. Optionally, the processor 1010 and the communication interface 1020 may be interconnected via a bus 1030. The communication device 1000 may be a first network function, a second network function, or a first node.

[0292] Optionally, the communication device 1000 may further include a memory 1040. The memory 1040 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), and is used to store relevant instructions and data.

[0293] The processor 1010 may be one or more central processing units (CPUs). In the case where the processor 1010 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0294] When the communication device 1000 is a first network function, illustratively, the communication device 1000 is used to perform the following operations: receiving first information from a first node, or receiving second information from a second network function, or determining a first QoS policy for a first service based on the first information and the second information, etc.

[0295] When the communication device 1000 is the second network function, illustratively, the communication device 1000 is configured to perform the following operations: sending the third information to the first node, or sending the second information to the first network function, etc.

[0296] When the communication device 1000 is a first node, illustratively, the communication device 1000 is configured to perform the following operations: receiving third information from a second network function, or sending first information to a first network function, etc.

[0297] The above contents are merely exemplary descriptions. When the communication device 1000 is the first network function / the second network function / the first node, it will be responsible for executing the methods or steps related to the first network function / the second network function / the first node in the aforementioned method embodiments.

[0298] The above description is merely exemplary. For details, please refer to the contents of the above method embodiments. The implementation of each operation in FIG10 may also correspond to the corresponding description of the method embodiments shown in FIG2 to FIG9.

[0299] Figure 11 is a schematic block diagram of a communication device 1100 according to an embodiment of the present application. Communication device 1100 may be a first network function, a second network function, or a first node, or may be a chip or module within the first network function, the second network function, or the first node, configured to implement the methods described in the above embodiments. Communication device 1100 includes a transceiver unit 1110 and a processing unit 1120. The following provides an exemplary description of transceiver unit 1110 and processing unit 1120.

[0300] The transceiver unit 1110 may include a transmitting unit and a receiving unit. The transmitting unit is used to perform the transmitting operation of the communication device 1100, and the receiving unit is used to perform the receiving operation of the communication device 1100. For ease of description, this embodiment of the application combines the transmitting unit and the receiving unit into a single transceiver unit. This is described here as a unified description and will not be repeated later.

[0301] When the communication device 1100 is a first network function, exemplarily, the transceiver unit 1110 is used to receive first information from a first node and to receive second information from a second network function, and the processing unit 1120 is used to determine a first QoS policy for the first service based on the first information and the second information.

[0302] When the communication device 1100 is a second network function, illustratively, the transceiver unit 1110 is configured to send the third information to the first node and to send the second information to the first network function.

[0303] When the communication device 1100 is a first node, illustratively, the transceiver unit 1110 is configured to receive third information from the second network function and to send second information to the first network function.

[0304] When the communication device 1100 is the first network function / the second network function / the first node, it will be responsible for executing the methods or steps related to the first network function, the second network function or the first node in the aforementioned method embodiments.

[0305] Optionally, the communication device 1100 further includes a storage unit 1130, which is used to store a program or code for executing the aforementioned method.

[0306] The device embodiments shown in Figures 10 and 11 are used to implement the contents described in Figures 2 to 9. The specific execution steps and methods of the devices shown in Figures 10 and 11 can refer to the contents described in the above method embodiments.

[0307] Figure 12 is a schematic block diagram of a communication device 1200 according to an embodiment of the present application. The communication device 1200 is configured to implement the functions of the first network function, the second network function, and the first node. The communication device 1200 may be a chip in the first network function, the second network function, or the first node.

[0308] Communication device 1200 includes an input / output interface 1220 and a processor 1210. Input / output interface 1220 may be an input / output circuit. Processor 1210 may be a signal processor, a chip, or other integrated circuit capable of implementing the method of the present application. Input / output interface 1220 is used for inputting or outputting signals or data.

[0309] For example, when the communication device 1200 is a first network function, the input / output interface 1220 is configured to receive first information from a first node and second information from a second network function. The processor 1210 is configured to determine a first QoS policy for a first service based on the first information and the second information.

[0310] For example, when the communication device 1200 is the second network function, the input / output interface 1220 is used to send the third information to the first node and to send the second information to the first network function.

[0311] For example, when the communication device 1200 is a first node, the input / output interface 1220 is used to receive third information from the second network function and to send first information to the first network function.

[0312] In one possible implementation, the processor 1210 implements the first network function or the second network function or the function implemented by the first node by executing instructions stored in the memory.

[0313] Optionally, the communication device 1200 further includes a memory.

[0314] Optionally, the processor and memory are integrated together.

[0315] Optionally, the memory is outside the communication device 1200 .

[0316] In one possible implementation, the processor 1210 may be a logic circuit, which inputs / outputs messages or signals through the input / output interface 1220. The logic circuit may be a signal processor, a chip, or other integrated circuit that can implement the method of the embodiment of the present application.

[0317] The above description of the communication device 1200 is only an exemplary description. The communication device 1200 can be used to execute the method described in the above embodiments. For specific content, please refer to the description of the above method embodiments, which will not be repeated here.

[0318] The present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0319] The present application also provides a chip, comprising: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is configured to execute code in a memory. When the code is executed, the processor is configured to execute the methods in the above examples. Optionally, the chip also includes a memory, which is configured to store computer programs or code.

[0320] The present application also provides a processor, which is coupled to a memory and is used to execute the method and function involving the first network function, the second network function, or the first node in any of the above embodiments.

[0321] The present application provides a computer program product comprising instructions. When the computer program product is run on a computer, the method of the aforementioned embodiment is implemented.

[0322] The present application also provides a computer program. When the computer program is executed in a computer, the method of the aforementioned embodiment is implemented.

[0323] The present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.

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

[0325] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0326] In the several embodiments provided in this application, the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0327] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the technical solutions of the embodiments of the present application.

[0328] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0329] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of each method embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

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

Claims

1. A method for generating a Quality of Service (QoS) policy, characterized in that The method includes: A first network function receives first information from a first node, where the first information is used to indicate a first service triggered by the first node; The first network function receives second information from a second network function, where the second information includes the service types of each node in at least one node, and the at least one node is the node served by the first network function; The first network function determines a first QoS policy for the first service based on the first information and the second information, where the first QoS policy includes the QoS requirements for at least one sixth node to complete the first service, and the at least one sixth node belongs to the at least one node.

2. The method according to claim 1, wherein The method further includes: The first network function obtains the updated service types of each node in the at least one node from the at least one node; The first network function determines a first QoS policy for the first service based on the first information and the second information, including: The first network function determines the first QoS policy based on the first information, the second information, and the updated service types of each node in the at least one node obtained from the at least one node.

3. The method according to claim 1 or 2, characterized in that, The first information includes the indication information of the first node and the indication information of the first service.

4. The method according to any one of claims 1 to 3, characterized in that The first information further includes the service requirements of the first node for the first service.

5. The method according to any one of claims 1 to 4, characterized in that, The second information further includes at least one of the following information: The node types of each node in the at least one node, the service priorities of the service types of each node in the at least one node, the computing power types, algorithm types, data types, connection topologies, the computing power resources, algorithm resources, data resources, radio resources, and connection quality that each node in the at least one node can provide.

6. The method according to any one of claims 1 to 5, characterized in that The first network function is deployed in a base station, or the first network function is deployed on a centralized unit CU, or the first network function is deployed on a cluster control node cNode.

7. The method according to claim 6, characterized in that, When the first network function is deployed in a base station, or when the first network function is deployed on a centralized unit CU, the method further includes: The first network function decomposes the first service into N tasks and determines N QoS policies for the N tasks based on the first information and the second information, where the N tasks and the N QoS policies correspond one by one; The first network function sends fourth information according to a second QoS policy, where the fourth information is used to indicate the second QoS configuration for at least one second node to execute a second task, where the second QoS policy belongs to the N QoS policies, the second task belongs to the N tasks, and the second QoS policy is the QoS policy for the second task, N is a positive integer greater than 1.

8. The method according to claim 7, wherein The method further includes: The first network function receives eighth information, where the eighth information is used to request to change the second QoS policy; The first network function changes the second QoS policy to a fifth QoS policy based on the eighth information; The first network function sends a ninth message according to the fifth QoS policy, where the ninth message is used to indicate a fourth QoS configuration for at least one fourth node to execute the second task.

9. The method according to claim 8, wherein The eighth message includes at least one of the following pieces of information: Indication information of the second QoS configuration of each node in the at least one second node, and first parameters of the changed QoS configuration, where the first parameters include at least one of the following pieces of information: 6G QoS identifier 6QI, allocation and retention priority ARP, flow bit rate FBR, floating-point operations per second FLOPS.

10. The method according to claim 6, wherein When the first network function is deployed on a cluster control node cNode, the method further includes: The first network function decomposes the first service into N tasks based on the first information and the second information and determines N Qos policies for the N tasks, where the N tasks correspond one-to-one with the N Qos policies; The first network function sends a fifth message to a first cNode, where the fifth message is used to indicate a third QoS policy for at least one third node to execute a third task, and the fifth message is used for the first cNode to determine at least one fourth QoS policy corresponding to the at least one third node, where the at least one fourth QoS policy corresponds one-to-one with the at least one third node, where the third QoS policy includes QoS requirements for the at least one third node to complete the third task, and each fourth QoS policy in the at least one fourth QoS policy includes resource requirements for the corresponding third node to execute the third task, the third QoS policy belongs to the N QoS policies, the third task belongs to the N tasks, and the third QoS policy is the QoS policy of the third task, M is a positive integer greater than or equal to 1, and N is a positive integer greater than 1.

11. The method according to claim 10, wherein The method further includes: The first policy control function receives a thirteenth message, where the thirteenth message is used to request a change to the third QoS policy; The first policy control function changes the third QoS policy to a sixth QoS policy based on the thirteenth message; The first policy control function sends a fourteenth message to a second cNode, where the fourteenth message is used to indicate the sixth QoS policy, and the fourteenth message is used for the second cNode to determine at least one seventh QoS policy corresponding to the at least one fifth node, where the at least one seventh QoS policy corresponds one-to-one with the at least one fifth node, where the sixth QoS policy includes QoS requirements for the at least one fifth node to complete the third task, and each seventh QoS policy in the at least one seventh QoS policy includes resource requirements for the corresponding fifth node to execute the third task.

12. The method according to claim 11, wherein The thirteenth message includes at least one of the following pieces of information: Indication information of the third QoS configuration of each node in the at least one third node, and second parameters of the changed QoS configuration; The second parameters include at least one of the following pieces of information: 6G QoS identifiers 6QI, Allocation and Retention Priority ARP, Flow Bit Rate FBR, Floating Point Operations Per Second FLOPS.

13. A method for changing a Quality of Service (QoS) policy, characterized in that, The method includes: A first network device determines that the status of a second node for executing a second task is abnormal; The first network device switches a second QoS configuration of the second node for executing the second task to an alternative QoS configuration; The first network device sends seventh information to the second node, where the seventh information is used to indicate the alternative QoS configuration.

14. The method according to claim 13, wherein The abnormal status of the second node includes: The second node cannot meet the second QoS configuration or there is resource redundancy in the second node.

15. The method according to claim 13 or 14, characterized in that, The method further includes: The first network device receives sixth information from the second node, where the sixth information is used to request reconfiguring the QoS of the second node; The first network device switches the second QoS configuration of the second node for executing the second task to an alternative QoS configuration, including: The first network device switches the second QoS configuration of the second node for executing the second task to the alternative QoS configuration based on the sixth information.

16. The method according to claim 15, wherein The sixth information includes at least one of the following information: Indication information of the second QoS configuration of the second node, third parameters of the changed QoS configuration; The third parameters include at least one of the following information: 6G QoS identifiers 6QI, Allocation and Retention Priority ARP, Flow Bit Rate FBR, Floating Point Operations Per Second FLOPS.

17. The method according to any one of claims 13 to 16, characterized in that If the second node still cannot meet the alternative QoS configuration or there is still resource redundancy in the second node after using the alternative QoS configuration, the method further includes: The first network device sends eighth information to a first network function, where the eighth information is used to request changing the QoS policy.

18. The method according to any one of claims 13 to 17, characterized in that, The first network device is a base station, or the first network device is a Centralized Unit CU, or the first network device is a Cluster Control Node cNode.

19. A method for generating a Quality of Service (QoS) policy, characterized in that, The method includes: A second network function sends second information to a first network function, where the second information includes the service type of each node in at least one node, the at least one node is the node served by the first network function, and the second information is used for the first network function to determine a first Quality of Service QoS policy for a first service, and the first Qos policy includes the QoS requirements for the first service completed by at least one sixth node, and the at least one sixth node belongs to the at least one node.

20. The method according to claim 19, wherein The second information further includes at least one of the following information: The node type of each node in the at least one node, the service priority of the service type of each node in the at least one node, the computing power type that each node in the at least one node can provide, algorithm type, data type, connection topology, the computing power resources, algorithm resources, data resources, radio resources, and connection quality that each node in the at least one node can provide.

21. The method according to claim 19 or 20, characterized in that, The method further includes: The second network function sends third information to the first node, where the third information is used to indicate the first network function corresponding to the first node, and the first node is the trigger node of the first service.

22. The method according to claim 21, wherein The third information is further used to indicate candidate first network functions.

23. The method according to any one of claims 19 to 22, characterized in that, The method further includes: The second network function periodically updates at least one piece of information included in the second information.

24. The method according to any one of claims 19 to 23, characterized in that, The first network function is deployed in a base station, or the first network function is deployed on a centralized unit (CU), or the first network function is deployed on a cluster control node (cNode).

25. A communication device, characterized in that, Comprising a processor and a communication interface, the processor is configured to, by executing a computer program or instruction, cause the communication device to execute the method according to any one of claims 1 to 12, or cause the communication device to execute the method according to any one of claims 13 to 18, or cause the communication device to execute the method according to any one of claims 19 to 24.

26. The communication device according to claim 25, characterized in that, The communication device further includes a memory for storing the computer program or instruction.

27. The communication device according to claim 25, wherein The communication device further includes a communication interface for inputting and / or outputting signals.

28. A computer-readable storage medium, characterized in that, A computer program or instruction is stored on the computer-readable storage medium, and when the computer program or the instruction runs on a computer, cause the method according to any one of claims 1 to 12 to be executed, or cause the method according to any one of claims 13 to 18 to be executed, or cause the method according to any one of claims 19 to 24 to be executed.

29. A computer program product, characterized in that, Containing instructions, when the instructions run on a computer, cause the method according to any one of claims 1 to 12 to be executed, or cause the method according to any one of claims 13 to 18 to be executed, or cause the method according to any one of claims 19 to 24 to be executed.

Images