Communication method, device and system

Abstract

The embodiment of the invention discloses a communication method, device and system, relates to the technical field of communication, and can support generation of a QoS strategy of a new service in a communication network. The method comprises the following steps: a policy control function network element obtains task information and requirement information of a first service; the task information comprises related information of the task obtained by decomposition mapping of the first service. And the policy control function network element generates a QoS parameter of the first service according to the requirement information of the first service. And the policy control function network element generates the QoS parameter of the task according to the task information and the QoS parameter of the first service.

Description

Technical Field

[0001] The present application relates to the field of communication technologies, and in particular to communication methods, devices and systems. Background Art

[0002] With the development of communication technology, some new services are being considered in wireless communication networks, such as services involving artificial intelligence (AI) and perception services. In order to support these new services, the network needs to efficiently coordinate heterogeneous resources in multiple dimensions such as connection, computing, data and models (or algorithms). The quality of service (QoS) mechanism in the fifth generation (5G) wireless communication network is based on the protocol data unit (PDU) session as the management object to ensure the quality of the communication connection, which is no longer applicable to wireless communication networks that introduce new services.

[0003] Therefore, how to ensure the service quality of new services introduced into wireless communication networks is an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present application provide a communication method, device and system, which can support the generation of QoS policies for new services in a wireless communication network to ensure the service quality of multiple services.

[0005] The embodiments of the present application adopt the following technical solutions:

[0006] In the first aspect, a communication method is provided, which can be executed by a policy control function network element, or by a component of the policy control function network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the policy control function network element functions. The following is an explanation using the policy control function network element as an example of the execution subject of the method, and the method includes: the policy control function network element obtains task information and requirement information of the first service; the task information includes relevant information of the task obtained by decomposing and mapping the first service. The policy control function network element generates QoS parameters for the first service based on the requirement information of the first service. Further, the policy control function network element generates QoS parameters for the task based on the task information and the QoS parameters of the first service.

[0007] Based on the communication method provided in the embodiment of the present application, the policy control function network element can generate service-level QoS parameters, and further generate task-level QoS parameters, which are applicable to communication networks managed at task granularity to ensure the service quality of the first service. Therefore, the communication method provided in the embodiment of the present application supports the generation of QoS policies for new services in the communication network.

[0008] In one possible design, the policy control function network element obtains requirement information of the first service, including: the policy control function network element obtains relevant information of the first service, the relevant information of the first service includes one or more of the following: requirement information of the first service or identification information of the first service, and there is a mapping relationship between the identification information of the first service and the requirement information of the first service.

[0009] Based on this solution, the policy control function network element can obtain the requirement information of the first service through the identification information of the first service, thereby saving signaling overhead.

[0010] In a possible design, the identification information of the first service includes at least one of the following: information of a user who triggers the first service, information of a terminal device related to the first service, or information of an application service provider.

[0011] This solution provides a variety of identification information of the first service, which can be applied to different scenarios.

[0012] In one possible design, the policy control function network element generates QoS parameters of the first service based on the requirement information of the first service, including: the policy control function network element generates a QoS template corresponding to the first service based on the relevant information of the first service, and the QoS template includes a mapping relationship between the QoS parameters of the first service and the identification information of the first service.

[0013] Based on this solution, the policy control function network element can establish a mapping relationship between the QoS parameters of the first service and the identification information of the first service. If other network elements obtain the identification information of the first service, they can obtain the QoS parameters of the first service based on the mapping relationship.

[0014] In one possible design, the QoS parameters of the first service include multiple sets of QoS parameters, where each set of QoS parameters has a different priority.

[0015] Based on this solution, a set of QoS parameters for actual application can be flexibly selected according to the priority of each set of QoS parameters.

[0016] In one possible design, the method also includes: the policy control function network element sends the QoS parameters of the first service to the unified data pool network element.

[0017] Based on this solution, the policy control function network element can store the QoS parameters of the first service in the unified data pool network element, which is convenient for the policy control function network element or other network elements to read.

[0018] In one possible design, the task information includes at least one of deployment information or topology information of the task.

[0019] Based on this solution, the policy control function network element can obtain the deployment information and / or topology information of the task, which can help the policy control function network element generate appropriate QoS parameters for the task.

[0020] In a possible design, the policy control function network element generates the QoS parameters of the task according to the task information and the QoS parameters of the first service, including: the policy control function network element generates the policy and charging control rules according to the task information and the QoS parameters of the first service. The policy and charging rules include the QoS parameters of the task, and a mapping relationship between the QoS parameters of the task and at least one of the execution network element or the task data flow that executes the task.

[0021] Based on this solution, the policy control function network element can bind the QoS parameters of the task to at least one of the execution network element or the task data flow while generating the QoS parameters of the task, so as to facilitate the management of QoS.

[0022] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, information about the network element executing the transmission starting point of the task's business data flow, and information about the network element executing the transmission end point of the task's business data flow.

[0023] Based on this solution, connection-related content that may be included in policies and charging rules is provided, so that QoS management can be performed on the connection dimension of the task according to the policies and charging rules.

[0024] In one possible design, the policies and charging rules also include the type of business data flow of the task, and the type of business data flow includes calculation, data or algorithm type.

[0025] Based on this solution, in view of the multiple dimensions involved in the task, the business data flow of the task can also be divided into different types, so as to facilitate QoS management of the business data flow of the task according to the type.

[0026] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to computing, an identifier indicating the specific QoS requirement related to computing, information of an execution network element used to perform computing functions, an identifier of a computing subtask, and a computing type of the computing subtask.

[0027] Based on this solution, the computing-related contents that may be included in the policies and charging rules are provided, so that the QoS management of the computing dimension of the task can be performed according to the policies and charging rules.

[0028] In one possible design, the policy and charging rules include at least one of the following: specific QoS requirement information related to the data, an identifier indicating the specific QoS requirement related to the data, a data type, and a data size.

[0029] Based on this solution, data-related content that may be included in policies and charging rules is provided, so that QoS management can be performed on the data dimension of the task according to the policies and charging rules.

[0030] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, the algorithm type, the algorithm level, and the application method.

[0031] Based on this solution, algorithm-related content that may be included in policies and charging rules is provided, so that QoS management can be performed on the algorithm dimension of the task according to the policies and charging rules.

[0032] In one possible design, the method further includes: the policy control function network element sends the QoS parameters of the task to the anchor network element, and the QoS parameters of the task are used by the anchor network element to generate resource-level QoS parameters. The resource-level QoS parameters include at least one of the following: connection dimension, computing dimension, data dimension, and algorithm dimension.

[0033] Based on this solution, the anchor network element can obtain the QoS parameters of the task and further generate resource-level QoS parameters, so that the anchor network element can directly perform QoS management on the four-dimensional resources according to the resource-level QoS parameters.

[0034] On the second aspect, a communication method is provided, which can be executed by an anchor network element, or by a component of the anchor network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the functions of the anchor network element. The following is an illustration of the anchor network element as the execution subject of the method, and the method includes: the anchor network element obtains the QoS parameters of the task, and generates resource-level QoS parameters based on the QoS parameters of the task and the execution network element that executes the task. Among them, the resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension and algorithm dimension. The anchor network element sends the resource-level QoS parameters to the execution network element.

[0035] Based on the communication method provided in the embodiment of the present application, the anchor network element can generate resource-level QoS parameters including four dimensions, so that QoS management can be directly performed on the four dimensions, which is suitable for new services in the communication network that require coordinated four-dimensional resources. Therefore, the communication method provided in the embodiment of the present application supports the generation of QoS policies for new services in the communication network.

[0036] In a possible design, the task is obtained by decomposing and mapping the first service, and the QoS parameters of the task are obtained according to the QoS parameters of the first service.

[0037] Based on this solution, decomposition mapping from services to tasks and then from tasks to resources can be achieved.

[0038] In one possible design, the method further includes: the anchor network element obtains the task scheduling result, the scheduling result includes the template description information and dependency relationship of the task. The anchor network element obtains the task information according to the scheduling result, the task information includes at least one of the deployment information or topology information of the task.

[0039] In one possible design, the method also includes: the anchor network element sends task information to the policy control function network element, and the task information is used by the policy control function network element to generate QoS parameters for the task.

[0040] Based on this solution, the anchor network element can send the obtained task information to the policy control function network element, so that the policy control function network element generates the QoS parameters of the task.

[0041] In one possible design, the anchor network element obtains the service quality QoS parameters of the task, including: the anchor network element obtains the policy and billing control rules, the policy and billing rules include the QoS parameters of the task, and the mapping relationship between the QoS parameters of the task and at least one of the execution network element that executes the task or the task data flow.

[0042] Based on this solution, the anchor network element can obtain the mapping relationship between the QoS parameters of the task and at least one of the execution network element or the task data flow, so that the anchor network element can generate resource-level QoS parameters according to the mapping relationship.

[0043] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, information about the network element executing the transmission starting point of the task's business data flow, and information about the network element executing the transmission end point of the task's business data flow.

[0044] Based on this solution, connection-related content that may be included in policies and charging rules is provided, so that the anchor network element can generate QoS parameters of the connection dimension according to the policies and charging rules.

[0045] In one possible design, the policies and charging rules also include the type of business data flow of the task, and the type of business data flow includes calculation, data or algorithm type.

[0046] Based on this solution, in view of the multiple dimensions involved in the task, the business data flow of the task can also be divided into different types, so as to facilitate QoS management of the business data flow of the task according to the type.

[0047] In one possible design, the QoS parameters of the connection dimension include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, and a packet identification rule; wherein the packet identification rule is used to distinguish service data flows corresponding to different QoS requirements.

[0048] Based on this solution, the possible contents of the QoS parameters of the connection dimension are provided, and the QoS management of the connection dimension can be performed based on the QoS parameters of the connection dimension.

[0049] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to computing, an identifier indicating the specific QoS requirement related to computing, information of an execution network element used to perform computing functions, an identifier of a computing subtask, and a computing type of the computing subtask.

[0050] Based on this solution, the calculation-related contents that may be included in the policies and charging rules are provided, so that the anchor network element can generate QoS parameters of the calculation dimension according to the policies and charging rules.

[0051] In one possible design, the QoS parameters of the computing dimension include at least one of the following: specific QoS requirement information related to computing, an identifier indicating the specific QoS requirements related to computing, and a computing subtask identification rule; wherein the computing subtask identification rule is used to distinguish computing subtasks corresponding to different QoS requirements.

[0052] Based on this solution, the possible contents of the QoS parameters of the computing dimension are provided, and the QoS management of the computing dimension can be performed based on the QoS parameters of the computing dimension.

[0053] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to the data, an identifier indicating the specific QoS requirement related to the data, a data type, and a data size.

[0054] Based on this solution, data-related content that may be included in policies and charging rules is provided, so that the anchor network element can generate QoS parameters in the data dimension according to the policies and charging rules.

[0055] In one possible design, the QoS parameters of the data dimension include at least one of the following: specific QoS requirement information related to the data, an identifier indicating the specific QoS requirement related to the data, and a data subtask identification rule; wherein the data subtask identification rule is used to distinguish data subtasks corresponding to different QoS requirements.

[0056] Based on this solution, the possible contents of the QoS parameters of the data dimension are provided, and the QoS management of the data dimension can be performed based on the QoS parameters of the data dimension.

[0057] In one possible design, the policies and charging rules include at least one of the following: specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, the algorithm type, the algorithm level, and the application method.

[0058] Based on this solution, algorithm-related content that may be included in policies and charging rules is provided, so that the anchor network element can generate QoS parameters of the algorithm dimension according to the policies and charging rules.

[0059] In one possible design, the QoS parameters of the algorithm dimension include at least one of the following: specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, and an algorithm subtask identification rule; wherein the algorithm subtask identification rule is used to distinguish algorithm subtasks corresponding to different QoS requirements.

[0060] Based on this solution, the possible contents of the QoS parameters in the algorithm dimension are provided, and the QoS management in the algorithm dimension can be performed based on the QoS parameters in the algorithm dimension.

[0061] In one possible design, the method also includes: the anchor network element receives notification information from the execution network element, where the notification information is used to notify the execution network element that QoS requirements related to connection, calculation, data or algorithm cannot be met.

[0062] Based on this solution, the anchor network element can determine which execution network element cannot meet the corresponding QoS requirement according to the notification of the execution network element, so as to adjust the strategy in a targeted manner to ensure that the QoS requirement can be met.

[0063] On the third aspect, a communication method is provided, which can be executed by an execution network element, or by a component of the execution network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can realize all or part of the execution network element functions. The following is an example of an execution network element as the execution subject of the method, and the method includes: the execution network element obtains resource-level QoS parameters; the resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension, and algorithm dimension. The execution network element executes the task according to the resource-level QoS parameters.

[0064] Based on the communication method provided in the embodiment of the present application, the executing network element can perform targeted processing on four-dimensional resources when executing tasks according to the acquired resource-level QoS parameters, thereby providing four-dimensional QoS management for new services in the communication network.

[0065] In a possible design, resource-level QoS parameters are obtained based on task QoS parameters, wherein the task is obtained by decomposing and mapping the first service, and the QoS parameters of the task are obtained based on the QoS parameters of the first service.

[0066] Based on this solution, decomposition mapping from services to tasks and then from tasks to resources can be achieved.

[0067] In one possible design, the QoS parameters of the connection dimension include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, and a packet identification rule; wherein the packet identification rule is used to distinguish service data flows corresponding to different QoS requirements.

[0068] Based on this solution, the possible contents of the QoS parameters of the connection dimension are provided, and the QoS management of the connection dimension can be performed based on the QoS parameters of the connection dimension.

[0069] In one possible design, the QoS parameters of the computing dimension include at least one of the following: specific QoS requirement information related to computing, an identifier indicating the specific QoS requirements related to computing, and a computing subtask identification rule; wherein the computing subtask identification rule is used to distinguish computing subtasks corresponding to different QoS requirements.

[0070] Based on this solution, the possible contents of the QoS parameters of the computing dimension are provided, and the QoS management of the computing dimension can be performed based on the QoS parameters of the computing dimension.

[0071] In one possible design, the QoS parameters of the data dimension include at least one of the following: specific QoS requirement information related to the data, an identifier indicating the specific QoS requirement related to the data, and a data subtask identification rule; wherein the data subtask identification rule is used to distinguish data subtasks corresponding to different QoS requirements.

[0072] Based on this solution, data-related content that may be included in policies and charging rules is provided, so that the anchor network element can generate QoS parameters in the data dimension according to the policies and charging rules.

[0073] In one possible design, the QoS parameters of the algorithm dimension include at least one of the following: specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, and an algorithm subtask identification rule; wherein the algorithm subtask identification rule is used to distinguish algorithm subtasks corresponding to different QoS requirements.

[0074] Based on this solution, the possible contents of the QoS parameters in the algorithm dimension are provided, and the QoS management in the algorithm dimension can be performed based on the QoS parameters in the algorithm dimension.

[0075] In one possible design, the method also includes: the execution network element sends a notification message to the anchor network element, where the notification message is used to notify the execution network element that QoS requirements related to connection, calculation, data or algorithm cannot be met.

[0076] Based on this solution, the execution network element can notify the anchor network element that it cannot meet the corresponding QoS requirement, so that the anchor network element can adjust the strategy in a targeted manner.

[0077] In a fourth aspect, a communication method is provided, which can be executed by a task orchestration network element, or by a component of the task orchestration network element (such as a processor, a chip, or a chip system, etc.), or by a logic module or software that can implement all or part of the functions of the task orchestration network element. The following is an example of an example in which the task orchestration network element is used as the execution subject of the method, and the method includes: the task orchestration network element obtains the QoS parameters of the first service. The task orchestration network element performs task orchestration according to the QoS parameters of the first service, and obtains an orchestration result with the task as the granularity; the orchestration result includes the template description information and dependency relationship of the task obtained by decomposing and mapping the first service.

[0078] Based on the communication method provided in the embodiment of the present application, the task orchestration network element can orchestrate the tasks obtained by decomposing and mapping the first service to obtain an orchestration result at a task granularity, which is suitable for orchestrating tasks for new services in the communication network, especially complex new services, to achieve QoS hierarchical management from services to tasks.

[0079] In one possible design, the method further includes: the task orchestration network element sends an orchestration result to the anchor network element, the orchestration result is used by the anchor network element to obtain task information, and the task information includes at least one of deployment information or topology information of the task.

[0080] Based on this solution, the task scheduling network element can send task information to the anchor network element, and the task information can assist the anchor network element to perform QoS management at the task granularity.

[0081] In a possible design, the task orchestration network element obtains the QoS parameters of the first service, including: the task orchestration network element obtains a QoS template corresponding to the first service, the QoS template including a mapping relationship between the QoS parameters of the first service and identification information of the first service.

[0082] Based on this solution, the task orchestration network element can obtain the mapping relationship between the QoS parameters of the first service and the identification information of the first service. If the subsequent task orchestration network element obtains the identification information of the first service, it can determine the QoS parameters of the first service according to the mapping relationship.

[0083] In one possible design, the QoS parameters of the first service include multiple sets of QoS parameters, where each set of QoS parameters has a different priority.

[0084] Based on this solution, a set of QoS parameters for actual application can be flexibly selected according to the priority of each set of QoS parameters.

[0085] In one possible design, the task scheduling network element obtains the QoS parameters of the first service, and performs task scheduling according to the QoS parameters of the first service, including: the task scheduling network element obtains the QoS parameters of the first priority of the first service, and performs task scheduling according to the QoS parameters of the first priority. If the scheduling according to the QoS parameters of the first priority fails, the method further includes: the task scheduling network element obtains the QoS parameters of the second priority of the first service, and performs task scheduling according to the QoS parameters of the second priority.

[0086] Based on this solution, the task scheduling network element can first schedule tasks according to the QoS parameters of the first priority. If the scheduling fails, it can try scheduling again according to the QoS parameters of the second priority, so as to avoid not scheduling again due to the failure of the initial scheduling, resulting in no scheduling results.

[0087] In a fifth aspect, a communication device is provided for implementing the above-mentioned various methods. The communication device includes a module, unit, or means corresponding to the above-mentioned method, and the module, unit, or means can be implemented by hardware, software, or by hardware executing the corresponding software. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.

[0088] In some possible designs, the communication device may include a transceiver module and a processing module. The transceiver module, which may also be referred to as a transceiver unit, is used to implement the sending and / or receiving functions in the first aspect, the second aspect, the third aspect, or the fourth aspect and any possible implementation thereof. The transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface. The processing module may be used to implement the processing functions in the first aspect, the second aspect, the third aspect, or the fourth aspect and any possible implementation thereof.

[0089] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in the above-mentioned first aspect, second aspect, third aspect or fourth aspect and any possible implementation methods thereof.

[0090] In a sixth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute a computer program or instruction so that the communication device executes any of the methods described above.

[0091] In a seventh aspect, a communication device is provided, comprising: at least one processor; the processor is used to execute a computer program or instruction stored in a memory so that the communication device performs any of the methods described above. In a possible implementation, the memory may be coupled to the processor, or may be independent of the processor. In a possible implementation, the communication device also includes the memory. Optionally, the memory and the processor are integrated together.

[0092] In the fifth to seventh aspects, the communication device may be the policy control function network element in the first aspect or any implementation of the first aspect, or a device including the policy control function network element, or a device included in the policy control function network element, such as a chip. Alternatively, the communication device may be the anchor network element in the second aspect or any implementation of the second aspect, or a device including the anchor network element, or a device included in the anchor function network element, such as a chip. Alternatively, the communication device may be the execution network element in the third aspect or any implementation of the third aspect, or a device including the execution network element, or a device included in the execution network element, such as a chip. Alternatively, the communication device may be the task orchestration network element in the fourth aspect or any implementation of the fourth aspect, or a device including the task orchestration network element, or a device included in the task orchestration network element, such as a chip or a chip system.

[0093] In an eighth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer-readable storage medium is run on a communication device, the communication device can execute any of the above aspects or any of its implementation methods.

[0094] In a ninth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute any of the above-mentioned aspects or any of its implementation methods.

[0095] In a tenth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided, wherein the communication device includes a processor for implementing the functions involved in any of the above aspects or any of its implementation methods.

[0096] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0097] In some possible designs, when the device is a chip system, it can be composed of a chip, or it can also include a chip and other discrete devices.

[0098] It can be understood that when the communication device provided in any one of the fifth to seventh aspects is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0099] Among them, the technical effects brought about by any implementation method in the fifth to tenth aspects can refer to the technical effects brought about by the corresponding implementation methods in the first to fourth aspects, and will not be repeated here.

[0100] It should be noted that various possible implementation methods of any one of the above aspects can be combined under the premise that there is no contradiction between the solutions.

[0101] In an eleventh aspect, a communication system is provided, which includes a policy control function network element that executes the method of the first aspect, an anchor network element that executes the method of the second aspect, and an execution network element that executes the method of the third aspect.

[0102] In some possible designs, the communication system may also include a task orchestration network element that executes the fourth aspect of the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0103] Figure 1 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0104] Figure 2 A schematic diagram of a core network architecture of a communication system provided in an embodiment of the present application;

[0105] Figure 3 A schematic diagram of a protocol stack provided in an embodiment of the present application;

[0106] Figure 4 A schematic diagram of a communication method provided in an embodiment of the present application;

[0107] Figure 5 A schematic diagram of another communication method provided in an embodiment of the present application;

[0108] Figure 6 A schematic diagram of another communication method provided in an embodiment of the present application;

[0109] Figure 7 A schematic diagram of another communication method provided in an embodiment of the present application;

[0110] Figure 8 A possible flow chart provided for an embodiment of the present application;

[0111] Fig. 9 Another possible flow chart provided for an embodiment of the present application;

[0112] Fig.10 Another possible flow chart provided for an embodiment of the present application;

[0113] Fig.11 Another possible flow chart provided for an embodiment of the present application;

[0114] Fig.12 Another possible flow chart provided for an embodiment of the present application;

[0115] Fig.13 A schematic diagram of an end-to-end connection architecture provided in an embodiment of the present application;

[0116] Fig.14 A schematic diagram of the composition of a communication device provided in an embodiment of the present application;

[0117] Fig.15 A schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0118] In order to facilitate understanding of the technical solutions of the embodiments of the present application, a brief introduction to the related technologies of the embodiments of the present application is first given as follows.

[0119] 1. New services in communication networks:

[0120] With the development of communication technology, some new services are being considered for introduction in wireless communication networks (networks that evolve after 5G, such as the sixth generation (6G)). For example, services involving AI and perception services. With the introduction of these new services, some new services may emerge. For example, in new services involving AI, AI is also used as a service (in this article, "AI as a service" can be referred to as "AI service"), which can provide AI services such as model training, model reasoning, and model verification. In perception services, devices with perception capabilities can perceive the characteristics of the target by sending and receiving signals, and can provide perception services such as high-precision positioning, high-resolution imaging, parameter measurement, gesture / motion recognition, and vital signs monitoring. For another example, 6G networks may also provide computing services (such as computing offloading), data services (such as data collection or data recycling), and other services.

[0121] In order to support these new businesses and services, the network needs to coordinate and schedule four dimensions of heterogeneous resources, namely connection, computing, data and model (or algorithm). In this article, "dimension" can also be called "element".

[0122] At the network level, the process of completing a specific goal through the collaboration of multi-dimensional resources can be defined as a "task". In the task-centric architecture, task anchors (TA) and task executors (TE) are introduced. Among them, TA is responsible for the life cycle management of tasks, such as the deployment, startup, deletion, modification or monitoring of tasks, and the regulation of four-dimensional resources for tasks. TE is responsible for the specific execution of tasks and performs data interaction in business logic. Based on TA and TE, the task processing flow can be: after the task trigger source triggers the task, the task request is sent to TA, and TA deploys the task to one or more TEs for execution.

[0123] In a possible scenario, task scheduling (TS) can also be introduced. TS is mainly responsible for task control, establishing and maintaining task context information, real-time perception of network status changes, and realizing four-dimensional resource collaborative scheduling and other functions.

[0124] In order to achieve service decoupling, the core network (CN) and the radio access network (RAN) can independently deploy TA and TE. For example, on the core network side, the task control function (TCF) network element can provide TA functions, and the task process function (TPF) network element can provide TE functions. On the access network side, the cluster node (cNode) can provide TA functions, and the service node (sNode) can provide TE functions.

[0125] In addition, in one possible scenario, the terminal device may also provide TE functionality.

[0126] In one possible scenario, an entity that provides TE functions can also provide TS functions. For example, TPF, sNode or terminal equipment can provide both TE functions and TS functions.

[0127] For the four dimensions of data, computing, algorithm, and connection, a task can be split into dimension-level subtasks. Based on this, when deploying tasks, TA can deploy dimension-level subtasks to TE for execution. It can be understood that due to the connection dimension of the task, including the connection paths between TEs that execute different subtasks, it does not have to be specifically executed by a certain TE, so there are no subtasks in the connection dimension. Therefore, a task can be split into subtasks in the data dimension (hereinafter referred to as data subtasks), subtasks in the computing dimension (hereinafter referred to as computing subtasks), and subtasks in the algorithm dimension (hereinafter referred to as algorithm subtasks). The number of each type of subtask can be one or more.

[0128] In a possible scenario, TE executes a dimension-level subtask, which can also be referred to as TE executing a corresponding function. For example, TE executes a calculation subtask, which can also be referred to as TE executing a calculation function.

[0129] In a possible implementation, for the four dimensions of connection, computing, data and algorithm, different modules can be responsible for resources of different dimensions inside the network element that provides TA functions. For example, the data dimension resources of the task can be managed by the data controller (DC), the computing dimension resources of the task can be managed by the computing controller (CC), the algorithm dimension resources of the task can be managed by the algorithm control (heterarchical intelligent collaboration controller, HicC) module, and the connection dimension resources of the task can be managed by the connection control (network controller, NC) module, including the establishment, addition, deletion and modification of the connection path between TEs.

[0130] Similarly, different modules can be responsible for different types of subtasks within the network element that provides TE functions. For example, the data execution agent (DA) can be responsible for the specific execution of data subtasks, the computing execution agent (CE) module can be responsible for the specific execution of computing subtasks, and the algorithm execution agent (HicA) module can be responsible for the specific execution of algorithm subtasks.

[0131] In summary, after the communication network introduces new services, some new services will no longer use PDU sessions as management objects, but will evolve to use task sessions as management objects for task-granular lifecycle management. The dimensions involved in these new services have also evolved from pure connection to four dimensions: connection, computing, data, and algorithm, and involve multiple network nodes with complex topology. The QoS policy generation mechanism in the 5G network uses PDU sessions as management objects, and can only provide QoS guarantees and differentiated services for end-to-end connections in a simple path of terminal equipment-RAN-CN, which is not suitable for generating QoS policies for new services. Therefore, how the QoS policy generation mechanism should be designed for new services introduced into the communication network is an urgent problem to be solved. In order to solve this problem, an embodiment of the present application provides a communication method that can support the generation of QoS policies for new services introduced into the communication network to ensure the QoS of the service.

[0132] The specific implementation of the QoS method provided by the embodiment of the present application is introduced below. In the description of the embodiment of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship. For example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. These three situations, where A and B can be singular or plural. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit the differences. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0133] In the embodiments of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information is called information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved by means of the arrangement order of each piece of information agreed in advance (for example, specified by the protocol), thereby reducing the indication overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and indicated uniformly to reduce the indication overhead caused by indicating the same information separately.

[0134] It should be understood that the information to be indicated can be sent as a whole, or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in the embodiment of the present application. Among them, the sending period and / or sending time of these sub-information can be pre-defined, for example, pre-defined according to a protocol, or can be configured by the sending end device by sending configuration information to the receiving end device.

[0135] In an embodiment of the present application, "pre-definition", "pre-definition", "pre-configuration" or "pre-configuration" can be implemented by pre-saving the corresponding code, table or other methods that can be used to indicate relevant information in the device. For example, it can be burned into the device when the device leaves the factory, or configured when accessing the network for the first time. The embodiment of the present application does not limit its specific implementation method. Among them, "saving" can mean saving in one or more memories. The one or more memories can be a separate setting or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories can also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of memory can be any form of storage medium, which is not limited by the embodiment of the present application.

[0136] The "protocol" involved in the embodiments of the present application may refer to a protocol family in the communication field, a standard protocol with a similar protocol family frame structure, or a related protocol used in future communication systems, and the embodiments of the present application do not make specific limitations on this.

[0137] In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that the device will make corresponding processing under certain objective circumstances. It does not limit the time, nor does it require the device to have a judgment action when implementing it, nor does it mean that there are other limitations.

[0138] In the embodiments of the present application, "sending information to... (taking the anchor network element as an example)" can be understood as the destination end of the information is the anchor network element. It can include sending information to the anchor network element directly or indirectly. "Receiving information from... (taking the anchor network element as an example)" can be understood as the source end of the information is the anchor network element, which can include receiving information from the anchor network element directly or indirectly. The information may be processed as necessary between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in the present application can be understood similarly and will not be repeated here.

[0139] The technical solution provided in this application can be used in various communication systems, such as 5G wireless communication systems and other communication systems, such as 6G communication systems and other communication systems evolved after 5G. In addition, the term "system" can be interchangeably used with "network".

[0140] It should be noted that the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0141] It should be noted that the names of the network elements appearing in this document, such as TCF network element, TPF network element, cNode, sNode, etc., and the modules inside the network elements, are only possible exemplary names. If the names actually used for network elements or modules inside network elements in subsequent communication networks (such as 6G networks) are different from the names appearing in this document, it does not affect the application of the communication method provided in the embodiments of the present application.

[0142] In a possible, non-limiting communication system to which the embodiments of the present application are applicable, the RAN architecture may be as follows: Figure 1 shown. Figure 1 In order to facilitate task processing, RAN nodes are divided into two categories: cNode and sNode. Among them, cNode is a regional centralized coordination node of multiple sNodes, responsible for providing TA functions on the RAN side, such as signaling interaction functions related to RAN side tasks. sNode is responsible for providing TE functions on the RAN side, and in some scenarios, it can also provide TS functions on the RAN side, such as scheduling and execution functions of RAN side tasks.

[0143] In the RAN architecture of the communication system to which the embodiments of the present application are applicable, the RAN nodes can be connected wirelessly or by wire. Figure 1 As shown, the cNode and the sNode communicate via the YI interface. Different sNodes communicate via the Y3 interface. Different cNodes communicate via the Y2 interface. In the RAN architecture of the communication system to which the embodiment of the present application is applicable, the RAN node can communicate with the terminal device ( Figure 1 In some scenarios, the terminal device may also provide TE function and / or TS function.

[0144] In the RAN architecture of the communication system to which the embodiments of the present application are applicable, the core network element and the RAN node may be different physical devices, or may be the same physical device that integrates the core network logical functions and the radio access network logical functions. If the core network element and the RAN node are different physical devices, the RAN node may be connected and / or communicate with the core network element in a wired or wireless manner.

[0145] The RAN architecture of the communication system to which the embodiments of the present application are applicable may also include other RAN nodes, for example, wireless relay equipment and / or wireless backhaul equipment ( Figure 1 Not shown in the figure) etc.

[0146] Figure 1 The RAN architecture shown may be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as the RAN architecture in a 6G mobile communication system. It may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloud radio access network, CRAN), or a RAN architecture in a communication system that integrates two or more of the above systems.

[0147] In one possible scenario, the RAN nodes in the 5G network can also be enhanced to provide TE functions on the RAN side.

[0148] In a possible, non-limiting communication system to which the embodiments of the present application are applicable, the core network architecture may be as follows: Figure 2As shown. Among them, the TCF network element provides the TA function on the core network side. The TPF network element provides the TE function on the core network side, and in some scenarios, it can also provide the TS function on the core network side. The control plane connection function (connection function-control, CF-C) network element and the user plane connection function (connection function-user, CF-U) network element provide the control plane and user plane functions of the connection respectively. Mobility management (mobility management, MM) is responsible for providing the mobility management function of the terminal equipment, saving the location information of the terminal equipment, etc. The unified data management (unified data management, UDM) network element is mainly responsible for user contract management, access authorization, authentication information generation and other functions. The policy control function (policycontrol function, PCF) network element is responsible for providing policy rules to network entities for implementation. The trusted anchor agent (trust anchor agent, TAA) network element is responsible for ensuring the reliability, integrity and confidentiality of the data, and preventing the data from various security and privacy attacks from entities inside and outside the network.

[0149] Optionally, the core network architecture of the communication system to which the embodiment of the present application is applicable may also include other network elements. For example, it may also include a unified data repository (UDR) network element, a task orchestration network element, or a network data analytics function (NWDAF) network element. Among them, the unified data repository network element is mainly responsible for storing subscription data and policy rules. The task orchestration network element is mainly responsible for orchestrating tasks. The network data analysis function network element is mainly responsible for providing network analysis services based on the request data of the network service.

[0150] The embodiments of the present application do not limit the name of the task orchestration network element. For example, it can be called a network AI management and orchestration (NAMO) network element.

[0151] In a possible, non-limiting communication system to which the embodiments of the present application are applicable, a RAN node may communicate with a terminal device via a wireless air interface (Uu interface), and its protocol stack includes a control plane protocol and a user plane protocol. RAN nodes may communicate with each other via a Yn interface, and its protocol stack may also include a control plane protocol and a user plane protocol. The control plane is responsible for signaling interaction, and the user plane is responsible for data interaction.

[0152] In a possible implementation, the control plane protocol stack and the user plane protocol stack between the RAN node and the terminal device can be as follows: Figure 3 As shown. Among them, the task resource control (TRC) layer of the control plane can be obtained by enhancing the radio resource control (RRC) layer in the 5G protocol stack. On the basis of the existing functions of the RRC layer, additional control functions related to tasks such as AI, computing, and data processing are added. The task resource scheduling (TRS) of the user plane can be obtained by enhancing the media access control (MAC) layer in the 5G protocol stack. For example, on the basis of the existing air interface resource scheduling function of the MAC layer, an additional computing power scheduling function is added. In addition, a task resource data (TRD) layer is added above the service data adaptation protocol (SDAP) layer. The TRD layer can provide task-related AI training / inference / model processing and other functions, and the TRD sublayer can provide task data encapsulation functions. Figure 3 The specific functions of the remaining layers in the 5G network, such as the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the TRS layer, the physical (PHY) layer and the SDAP layer, can be referred to the existing 5G communication protocol and will not be expanded here.

[0153] In the embodiments of the present application, the terminal device may refer to a user-side device with wireless transceiver functions. The terminal device may also be referred to as a terminal, user equipment (UE), access terminal, user unit, user station, mobile station (MS), remote station, remote terminal, mobile terminal (MT), user terminal, wireless communication device, user agent or user device, etc.

[0154] Exemplarily, the terminal device can be a drone, an Internet of Things (IoT) device (e.g., a sensor, an electric meter, a water meter, etc.), a V2X device, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an on-board device (e.g., a terminal on a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed rail, etc.), a vehicle device (e.g., a whole vehicle device, an on-board module, an on-board chip, an on-board unit (OBU) or a telematics box (T-BOX), etc.), a wearable device (also called a wearable smart device, such as a smart watch, a smart bracelet, a pedometer, a smart glasses, etc.), a tablet computer or a computer with wireless transceiver function, a virtual reality (VR) terminal, an industrial control (industrial The invention relates to wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, vehicles with vehicle-to-vehicle (V2V) communication capabilities, intelligent networked vehicles, drones with UAV to UAV (U2U) communication capabilities, etc. The terminal device can be mobile or fixed, and this application does not make specific restrictions on this.

[0155] RAN nodes, sometimes also called access network equipment, RAN entities or access nodes, are network elements of the radio access network and are responsible for air interface related functions. Systems using different radio access technologies may have different names for RAN nodes.

[0156] In one possible scenario, the RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation evolved base station (ng-eNodeB, ng-eNB), a cluster node or service node in a 6G mobile communication system, a base station in a future mobile communication system, etc. The RAN node may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application may also be a logical node, a logical module, or software that can implement all or part of the functions of the RAN node.

[0157] In another possible scenario, multiple RAN nodes collaborate to assist the terminal device in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0158] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, CU, CU-CP, CU-UP, DU and RU are described as examples in this application. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0159] Combine the following Figure 1 , Figure 2 The communication system shown describes the communication method provided in the embodiment of the present application.

[0160] It should be noted that in the following embodiments of the present application, the message names between network elements, the names of parameters, or the names of information are only examples. In other embodiments, they may also be other names, and the method provided in the present application does not make any specific limitations on this.

[0161] It is understandable that in the embodiments of the present application, each network element or entity may perform some or all of the steps in the embodiments of the present application, and these steps or operations are only examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, each step may be performed in a different order presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

[0162] See also Figure 4 The communication method provided in the embodiment of the present application includes steps S401-S403:

[0163] S401. The policy control function network element obtains task information and requirement information of a first service.

[0164] First, the requirement information for the policy control function network element to obtain the first service is introduced.

[0165] The requirement information of the first service includes requirements for QoS indicators related to the first service, for example, requirements for at least one indicator such as service success rate, service response delay, system energy efficiency, service coverage or service density.

[0166] In a possible implementation, the requirement information of the first service may be determined based on an agreement signed between a user of the first service and a provider of the first service. For example, the requirement information of the first service may be service level agreement (SLA) information.

[0167] Regarding the policy control function network element obtaining the requirement information of the first service, in a possible implementation, the policy control function network element may obtain relevant information of the first service, and the relevant information of the first service includes at least one of the following: the requirement information of the first service or the identification information of the first service. There is a mapping relationship between the identification information of the first service and the requirement information of the first service.

[0168] If the relevant information of the first service includes identification information of the first service, the policy control function network element may determine the requirement information of the first service corresponding to the identification information of the first service according to a predefined mapping relationship between the identification information of the first service and the requirement information of the first service.

[0169] For example, the policy control function network element may predefine a one-to-one correspondence between identification information of different services and requirement information of different services. If the policy control function network element obtains the identification information of the first service, the policy control function network element may determine the requirement information of the service corresponding to the identification information of the first service according to the predefined correspondence, and determine the requirement information of the corresponding service as the requirement information of the first service.

[0170] In the embodiment of the present application, predefined can also be understood as preset, preconfigured, pre-set, protocol-defined or pre-agreed. This is a unified explanation, and similar expressions can be understood in the following.

[0171] If the relevant information of the first service includes identification information of the first service and requirement information of the first service, optionally, the policy control function network element may establish a mapping relationship between the identification information of the first service and the requirement information of the first service.

[0172] If the relevant information of the first service includes requirement information of the first service, optionally, the policy control function network element may determine the identification information of the first service corresponding to the requirement information of the first service according to a predefined mapping relationship between the identification information of the first service and the requirement information of the first service.

[0173] The identification information of the first service can also be understood as information that can be used to jointly define the first service in combination with the requirement information of the first service. Exemplarily, the identification information of the first service can include at least one of the following: information of a user or third party that triggers the first service, information of a terminal device related to the first service, or information of an application service provider (ASP).

[0174] Exemplarily, the third party may be a vendor of over the top (OTT) services provided by the operator. The vendor of the OTT service may directly trigger the first service at the network level.

[0175] For example, the identification information of the first service may include the identification number (identity, ID) (user ID) of the user who triggers the first service (if the user is a UE, the user ID is the UE ID), the internet protocol (IP) triplet information of the server of the OTT service that triggers the first service, the information of the services provided by the network required by the manufacturer of the OTT service, the address of the UE involved in the first service (when a task session and / or a PDU session has been established) and the information of the ASP that provides the first service. Among them, the IP triplet information includes the IP address, the transport layer protocol and the port.

[0176] The first service is jointly defined by the identification information of the first service and the requirement information of the first service. If the identification information and the requirement information of the two services are different, then they can be considered as different services. If the identification information and the requirement information of the two services are the same, then they can be considered as the same service. In one possible scenario, if the requirement information of the two services is different and the identification information is the same, or if the identification information of the two services is different and the requirement information is the same, the two services can be considered as different services. In another possible scenario, if the requirement information of the two services is different and the identification information is the same, or if the identification information of the two services is different and the requirement information is the same, the two services can be considered as the same service.

[0177] Optionally, the policy control function network element may also obtain service data flow (SDF) information. Exemplarily, the SDF information may include IP quintuple information of the service data. The IP quintuple information includes a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol.

[0178] Optionally, the policy control function network element can also obtain type information of the first service. Among them, the type information of the first service can indicate which major category the first service belongs to. For example, the type information of the first service can indicate that the first service is an AI service, a computing service, a data service, or a perception service. Alternatively, the type information of the first service can also indicate which subcategory of the major category the first service belongs to. For example, assuming that the first service is an AI service, the type information of the first service can also indicate whether the first service is a model training, model reasoning, or model verification service.

[0179] The embodiment of the present application does not limit which network element the policy control function network element obtains the requirement information of the first service from. Exemplarily, the policy control function network element may obtain the requirement information of the first service from an application function network element.

[0180] The following describes how the policy control function network element obtains task information.

[0181] The first service may be decomposed and mapped to obtain one or more tasks, and the task information includes relevant information of the tasks obtained by decomposing and mapping the first service.

[0182] Optionally, the task information may include at least one of deployment information of the task or topology information of the task.

[0183] The deployment information of the task may include at least one of the identification information of the task or the information of the network element responsible for executing the task. For example, the deployment information of the task may include the ID of the task and the ID of the network element responsible for executing the task.

[0184] The topology information of the task may indicate the connection mode between the network elements involved in the task. For example, the topology information of the task may describe at least one of the following connection modes: RAN-RAN (RAN side, connection between different RAN nodes), CN-RAN-UE (connection between core network elements, RAN nodes and terminal devices), UE-RAN-UE (connection between different terminal devices and RAN nodes).

[0185] In a possible implementation, if the deployment information of a task includes the identification information of the task and the information of the network element responsible for executing the task, there may be a mapping relationship between the identification information of the task and the information of the network element responsible for executing the task. For example, the deployment information of the task may include the IDs of multiple tasks and the ID of the network element responsible for executing the task corresponding to each task ID.

[0186] In the embodiments of the present application, "a network element responsible for executing a task" or similar expressions, such as "a network element that executes a task", may be referred to as an execution network element, and is described uniformly herein. The execution network element may provide a TE function, and the specific TE function may be referred to in the above description, which will not be expanded here.

[0187] In addition, in a possible scenario, the execution network element may also provide a TS function. For details of the TS function, please refer to the above introduction and will not be expanded here.

[0188] The embodiment of the present application does not limit which network element the policy control function network element obtains the task information from. Exemplarily, the policy control function network element may obtain the requirement information of the first service from the anchor network element.

[0189] In the embodiment of the present application, the anchor network element is a network element that provides a TA function, which is uniformly described here. For example, the anchor network element may be a TCF or a cNode.

[0190] Optionally, when the policy control function network element obtains the task information, it can also obtain the identification information of the QoS parameters of the first service. For example, the anchor network element sends the task information and the identification information of the QoS parameters of the first service to the policy function control network element. The policy control function network element can determine the QoS parameters of the first service to which the task belongs based on the identification information of the QoS parameters of the first service, thereby further generating the QoS parameters of the task. Among them, the QoS parameters of the first service and the QoS parameters of the task are specifically introduced below and will not be expanded here.

[0191] Understandably, Figure 4 The process shown is only a logical schematic process provided for the convenience of understanding the embodiment of the present application, and does not represent the actual timing of the embodiment of the present application. The embodiment of the present application does not limit Figure 4 The timing between different actions within the same step, and Figure 4 For example, S401 is for the policy control function network element to obtain task information and the requirement information of the first service, which does not mean that the policy control function network element obtains the task information and the requirement information of the first service at the same time. In one possible situation, the policy control function network element may first obtain the requirement information of the first service and then obtain the task information. For another example, Figure 4 In the figure, S402 comes after S401, which does not mean that the policy control function network element completes S401 first and then S402. In one possible situation, the policy control function network element may first obtain the requirement information of the first service, and then generate the service quality QoS parameters of the first service according to the requirement information of the first service, and then obtain the task information.

[0192] Optionally, in addition to the task information and the requirement information of the first service, the policy control function network element may also obtain other information that can assist in generating the network policy. For example, the policy control function network element may also obtain at least one of the following information: billing related information, data statistics or forecast information of certain network functions or network services, bandwidth requirement information, or information indicating the data format (e.g., media type information). The embodiment of the present application does not limit which network element or network elements the policy control function network element obtains the above information from.

[0193] S402: The policy control function network element generates QoS parameters for the first service according to the requirement information of the first service.

[0194] In S402, the policy control function network element may classify and merge according to the requirement information of the first service to generate one or more sets of QoS parameters for the first service. For example, the policy control function network element may classify the requirement information requiring the QoS indicator to be within a certain range into one set of QoS parameters and classify the requirement information requiring the QoS indicator to be within another range into another set of QoS parameters according to different requirements for a certain QoS indicator in the requirement information of the first service.

[0195] The QoS parameters of the first service may include QoS indicators and control strategies of the first service. At this time, the QoS parameters of the first service are service-level.

[0196] For example, a set of QoS parameters for the first service may include information indicating at least one indicator such as service success rate, service response delay, system energy efficiency, service coverage or service density, and information indicating the value corresponding to each indicator. Among them, indicators such as service success rate, service response delay, system energy efficiency, service coverage or service density are QoS indicators for the first service. The value corresponding to each indicator represents the control strategy for the indicator. For example, the value corresponding to the service response delay is 1ms, which means that the end-to-end delay requirement for the first service is 1ms.

[0197] Optionally, the QoS parameters of the first service may be identified by identification information, and one piece of identification information may uniquely identify a set of QoS parameters.

[0198] In a possible implementation, the identification information of the QoS parameters of the first service may be generated by a policy control function network element. For example, the policy control function network element may generate a different service identification number (service ID) for each set of QoS parameters of the first service.

[0199] In another possible implementation, the identification information of the QoS parameters of the first service may be predefined. For example, the policy control function network element selects a different service ID for each set of QoS parameters of the first service from the service IDs predefined by the operator.

[0200] Optionally, if the first service has multiple sets of QoS parameters, each set of QoS parameters may have a different priority.

[0201] For example, if the first service belongs to a very important person (VIP) who has signed a contract with the operator, the QoS parameters of the first priority can be a set of QoS parameters with the highest requirements. If the first service belongs to a non-VIP business, the QoS parameters of the first priority can be a set of QoS parameters with lower requirements.

[0202] Optionally, if in S401, the policy control function network element obtains relevant information of the first service, then in S402, the policy control function network element may generate a QoS template corresponding to the first service based on the relevant information of the first service. The QoS template includes a mapping relationship between the QoS parameters of the first service and the identification information of the first service. For how to generate the QoS template corresponding to the first service, please refer to the above introduction to different situations of the relevant information of the first service, which will not be expanded here.

[0203] Optionally, after S402, the following steps may also be included:

[0204] The policy control function network element sends the QoS parameters of the first service to the unified data pool network element. Correspondingly, after receiving the QoS parameters of the first service, the unified data pool network element can store the QoS parameters of the first service.

[0205] If, in S402, the policy control function network element generates a QoS template corresponding to the first service, the policy control function network element may send the QoS template corresponding to the first service to the unified data pool network element.

[0206] S403: The policy control function network element generates QoS parameters of the task according to the task information and the QoS parameters of the first service.

[0207] Based on this solution, the policy control function network element can generate service-level QoS parameters and further generate task-level QoS parameters, which is suitable for new services managed at task granularity and can support the generation of QoS policies for new services in communication networks.

[0208] In S403, the QoS parameters of the task include the QoS index and control strategy of the task obtained by the first service decomposition mapping. At this time, the QoS parameters of the task are at the task level.

[0209] For example, the QoS parameters of a task may include information indicating at least one indicator such as task success rate, task response delay, system energy efficiency, task coverage or task density, and information indicating the value corresponding to each indicator. Among them, indicators such as task success rate, task response delay, system energy efficiency, task coverage or task density are QoS indicators of the task. The value corresponding to each indicator represents the control strategy for the indicator. For example, the value corresponding to the task response delay is 1ms, which means that the end-to-end delay requirement of the task is 1ms.

[0210] Optionally, the QoS parameters of the task may include at least one of the following: QoS specific requirement information or an identifier indicating the QoS specific requirement. There may be a predefined mapping relationship between the identifier indicating the QoS specific requirement and the QoS specific requirement, so that the corresponding QoS specific requirement can be determined by the identifier indicating the QoS specific requirement.

[0211] Exemplarily, the QoS specific requirement information may include task indicators and values ​​corresponding to the task indicators.

[0212] Exemplarily, the identifier indicating the specific QoS requirement may be a 6G QoS identifier (6G QoS identifier, 6QI).

[0213] For generating the QoS parameters of the task, in a possible implementation, the policy control function network element may generate a policy and charging (PCC) rule (PCCrule) according to the task information and the QoS parameters of the first service. The policy and charging rule includes the QoS parameters of the task, and a mapping relationship between the QoS parameters of the task and at least one of an execution network element or a task data flow (TDF) that executes the task.

[0214] The task data flow can be understood as the data transmission generated when the execution network element executes the task. In other words, the task data flow is at the task level.

[0215] In a possible scenario, if the business to which the first service belongs involves one or more of the four dimensions (connection, computing, data, and algorithm), the task data flow can be understood as the data transmission generated when the executing network element executes the data subtask, computing subtask, or algorithm subtask.

[0216] Optionally, the policy and charging rule may further include identification information (rule ID) of the policy and charging rule.

[0217] Optionally, if in S401, the policy control function network element obtains the mapping relationship between the identification information of the task and the information of the execution network element that executes the task, then when the policy control function network element generates the QoS parameters of the task, it can generate the mapping relationship between the QoS parameters of the task and the execution network element that executes the task based on the acquired mapping relationship.

[0218] In a possible scenario, if the business to which the first service belongs involves multiple dimensions, the QoS parameters of the task generated by the policy control function network element may include QoS parameters related to the dimensions involved.

[0219] Exemplarily, if the business to which the first service belongs involves four dimensions: connection, computing, data and algorithm, the QoS parameters of the task generated by the policy control function network element may include: QoS parameters related to connection, QoS parameters related to computing, QoS parameters related to data and QoS parameters related to algorithm.

[0220] The following takes the business to which the first service belongs involving at least one dimension of connection, calculation, data or algorithm as an example to introduce the possible contents of the policy and charging rules generated by the policy control function network element.

[0221] If the business to which the first service belongs involves a connection dimension, the policies and charging rules generated by the policy control function network element may include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirements related to the connection, information about the network element executing the transmission starting point of the task's business data flow, and information about the network element executing the transmission end point of the task's business data flow.

[0222] Optionally, each business data flow of the task can be classified based on which dimension of computation, data, or algorithm the data transmitted by the business data flow of the task (i.e., the task data flow) is related to. In other words, the business data flow of the task can include different types of business data flows, where different types can include computation, data, or algorithm types. In this case, the policy and charging rules can also include information on the type of the business data flow of the task.

[0223] The transmission starting point execution network element of the task's service data flow is the starting point execution network element on the transmission path of the task's service data flow, and the transmission end point execution network element of the task's service data flow is the end point execution network element on the transmission path of the task's service data flow. Optionally, the transmission paths of each service data flow of the task can be the same or different.

[0224] Exemplarily, the information of the network element executing the transmission starting point of the task's business data flow may include at least one item of information such as the ID or IP of the network element executing the transmission starting point of the task's business data flow. The information of the network element executing the transmission ending point of the task's business data flow is similar and will not be repeated here.

[0225] Among them, exemplarily, the QoS specific requirement information related to the connection may include at least one of the following: guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR) or allocation and retention priority (ARP), etc.

[0226] Exemplarily, the identifier indicating the specific QoS requirement associated with the connection may be 6QI.

[0227] If the business to which the first service belongs involves a computing dimension, the policies and charging rules generated by the policy control function network element may include at least one of the following: specific QoS requirement information related to computing, an identifier indicating the specific QoS requirements related to computing, information of an execution network element used to perform the computing function, an identifier of a computing subtask, or a computing type of a computing subtask.

[0228] Among them, a task can be decomposed into one or more computing subtasks.

[0229] The execution network element for executing the computing function may refer to the execution network element for executing the computing subtask. For example, the information of the execution network element for executing the computing function may include at least one of the information such as the ID or IP of the execution network element for executing each computing subtask.

[0230] In a possible scenario, an execution network element that performs a computing function may also perform an algorithm function and / or a data function. In other words, an execution network element that performs a computing function may also be an execution network element that performs an algorithm function and / or a data function.

[0231] The computing type of the computing subtask can be divided based on the computing specifications of the computing subtask (or the computing resources required for the computing subtask). For example, the computing resources may include computing power types, such as central processing unit (CPU), graphics processing unit (GPU) or field-programmable gate array (FPGA), and computing power requirements, such as million floating-point operations per second (MFLOPS).

[0232] Exemplarily, the specific QoS requirement information related to computing may include at least one of the following: giga floating-point operations per second (GFLOPS), MFLOPS, or ARP, etc.

[0233] Exemplarily, the identifier indicating specific QoS requirements related to computing may be 6QI.

[0234] Exemplarily, the identifier of the computing subtask may be the ID of the computing subtask.

[0235] If the business to which the first service belongs involves the data dimension, the policies and charging rules generated by the policy control function network element may include at least one of the following: specific QoS requirement information related to the data, an identifier indicating the specific QoS requirements related to the data, the data type, the data scale (also referred to as the data magnitude), or information of the execution network element used to perform the data function.

[0236] Exemplarily, the information of the execution network element for executing the data function may include at least one of the information such as the ID or IP of the execution network element for executing the data function.

[0237] Exemplarily, the QoS specific requirement information related to data may include at least one of the following: latency or ARP, etc. The latency may include at least one of data transmission delay or data processing delay.

[0238] Exemplarily, the identifier indicating specific QoS requirements associated with the data may be 6QI.

[0239] The data type is used to indicate the dimension to which the data corresponds. For example, the data type may include at least one of calculated data, model data, or data data. Calculated data indicates that the data corresponds to a calculated dimension; model data indicates that the data corresponds to a model dimension; and data data indicates that the data corresponds to a data dimension. For example, if the data is perception data, it may indicate that the data corresponds to a data dimension and needs to be processed specifically by a data function.

[0240] Exemplarily, the data size may include at least one of the following: bit, byte, kilobyte (KB), megabyte (MB), gigabyte (GB) or terabyte (TB).

[0241] If the business to which the first service belongs involves an algorithm dimension, the policies and charging rules generated by the policy control function network element may include at least one of the following: specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirements related to the algorithm, the algorithm type, the algorithm level, the application method, or information of the execution network element used to execute the algorithm function.

[0242] Exemplarily, the information of the execution network element used to execute the algorithm function may include at least one of the information such as the ID or IP of the execution network element that executes the algorithm function.

[0243] The algorithm level may indicate the requirements for the model structure or scale. For example, the algorithm level may indicate that the model needs to be iteratively trained 100 times, or may indicate that the model parameter scale is 7 billion.

[0244] Exemplarily, the specific QoS requirement information related to the algorithm may include at least one of the following: training and inference latency, inference accuracy, or ARP, etc.

[0245] Exemplarily, the identifier indicating the specific QoS requirements associated with the algorithm may be 6QI.

[0246] Exemplarily, the algorithm type may be a recursive algorithm, a sorting algorithm, a hash algorithm, or the like.

[0247] The application mode may indicate the mode of applying the algorithm-related QoS parameters. For example, the application mode may indicate when to use the algorithm-related QoS parameters of the first priority, and whether to enable the algorithm-related QoS parameters of the second priority if the algorithm-related QoS parameters of the first priority cannot be met.

[0248] Optionally, after S403, the embodiment of the present application may further include the following steps:

[0249] S404: The policy control function network element sends the QoS parameters of the task to the anchor network element.

[0250] Correspondingly, after receiving the QoS parameters of the task, the anchor network element can generate resource-level QoS parameters according to the QoS parameters of the task. The resource-level QoS parameters include at least one of the following: connection dimension, calculation dimension, data dimension and algorithm dimension.

[0251] The specific implementation of the anchor network element generating resource-level QoS parameters according to the task QoS parameters is introduced below and will not be expanded here.

[0252] In a possible implementation of S404, the policy control function network element may send policies and charging rules to the anchor network element. The contents of the policies and charging rules may refer to the above introduction to S403 and will not be elaborated here.

[0253] See also Figure 5 Another communication method provided in an embodiment of the present application includes steps S501-S503:

[0254] S501. The anchor network element obtains QoS parameters of the task.

[0255] The QoS parameters of the task may be specifically referred to the above description of the QoS parameters of the task in S403, which will not be elaborated here.

[0256] The embodiment of the present application does not limit the network element from which the anchor network element obtains the QoS parameters of the task. For example, the anchor network element may obtain the QoS parameters of the task from a policy control function network element.

[0257] In a possible implementation of S501, the anchor network element may obtain policies and charging rules. The policies and charging rules include QoS parameters of the task, and a mapping relationship between the QoS parameters of the task and at least one of the execution network element or task data flow that executes the task. In this implementation, the specific contents of the policies and charging rules can be referred to the introduction of the policies and charging rules in S403 above, which will not be expanded here.

[0258] Optionally, the embodiment of the present application may further include the following steps: the anchor network element obtains the orchestration result of the task, and the orchestration result includes the task template description information and the dependency relationship of the task.

[0259] The task template description information is used to describe the task or the subtasks decomposed from the task. For example, it may include at least one of the following information: task type (for example, the type of the subtask is algorithm, calculation or data), resource requirement (this information may indicate the size of resources required for the task or subtask), computational complexity (this information may indicate the complexity of the operation required to execute the task or subtask), and runtime description (for example, the time from the start to the end of a task or subtask).

[0260] The task dependency may include the dependency between different tasks obtained by the first service decomposition mapping. For example, assume that the first service decomposition mapping obtains task A, task B, and task C. The task dependency may be: the execution of task A depends on the execution of task B, and the execution of task C depends on the execution of task A and task B.

[0261] Optionally, the task scheduling result may further include information of an execution network element that executes the task.

[0262] The embodiment of the present application does not limit the network element from which the anchor network element obtains the task scheduling result. For example, the anchor network element can obtain the task scheduling result from the task scheduling network element.

[0263] Optionally, when the anchor network element obtains the task scheduling result, it can also obtain the identification information of the QoS parameter of the first service. For example, the task scheduling network element sends the identification information of the QoS parameter of the first service and the scheduling result to the anchor network element.

[0264] The embodiment of the present application does not limit the time sequence between the anchor network element obtaining the QoS parameters of the task and the anchor network element obtaining the scheduling result of the task. For example, the anchor network element may first obtain the scheduling result of the task and then obtain the QoS parameters of the task.

[0265] Furthermore, the anchor network element can obtain task information according to the orchestration result, and the task information includes deployment information and topology information of the task. The task information can be specifically referred to the introduction of the task information in S401 above, which will not be expanded here.

[0266] Optionally, the anchor network element may also send task information to the policy control function network element. Correspondingly, after receiving the task information, the policy control function network element may generate QoS parameters for the task according to the task information. The policy control function network element may generate QoS parameters for the task according to the task information in detail, as described above in the introduction to S403, which will not be expanded here.

[0267] In a possible implementation, when the anchor network element sends the task information to the policy control function network element, the QoS parameter of the first service may also be sent to the policy control function network element.

[0268] Furthermore, after the anchor network element obtains the QoS parameters of the task, it can complete the binding of the task session with the QoS parameters of the task. The anchor network element can also classify the task data flow according to the QoS parameters of the task, obtain the task QoS flow, and complete the binding of the task QoS parameters with the task QoS flow. Among them, a task QoS flow can include one or more task data flows with the same QoS requirements.

[0269] Among them, the task QoS flow can be understood as the minimum granularity for QoS management of anchor network elements and execution network elements. The anchor network elements and execution network elements can provide QoS guarantee and differentiated services based on the task QoS flow.

[0270] S502: The anchor network element generates resource-level QoS parameters according to the QoS parameters of the task and the execution network element that executes the task. The resource-level QoS parameters include at least one of the following: connection dimension, calculation dimension, data dimension, and algorithm dimension.

[0271] In S502, the anchor network element may decompose and map the task QoS parameters according to the QoS parameters related to connection, calculation, data or algorithm in the task QoS parameters to generate resource-level QoS parameters.

[0272] For the execution network element that executes the task, in one possible implementation, the anchor network element may be determined according to the obtained task scheduling result. In another possible implementation, the anchor network element may determine it by itself. For example, the anchor network element may select the execution network element that executes the task according to the capability of the execution network element.

[0273] In a possible implementation of S502, the anchor network element may determine the subtasks to be executed for each execution network element according to the differences in processing capabilities of each execution network element in various dimensions, and determine the corresponding resource-level QoS parameters.

[0274] The following introduces the possible contents of the resource-level QoS parameters generated by the anchor network element based on different situations of the QoS parameters included in the task QoS parameters.

[0275] Case 1: The QoS parameters of the task include QoS parameters related to the connection. For example, the policy and charging rules acquired by the anchor network element include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, information about the execution network element of the transmission start point of the task's service data flow, and information about the execution network element of the transmission end point of the task's service data flow. For details, please refer to the above introduction to S403.

[0276] In this case, the resource-level QoS parameters generated by the anchor network element may include a connection dimension. In one possible implementation, the QoS parameters of the connection dimension may include at least one of the following: QoS specific requirement information related to the connection, an identifier indicating the QoS specific requirement related to the connection or a packet detection rule (PDR). The packet detection rule is used to distinguish service data flows corresponding to different QoS requirements.

[0277] The following introduces a possible implementation method for distinguishing business data flows corresponding to different QoS requirements based on group identification rules. Group identification rules include specific detection rules, and different group identification rules are associated with different QoS requirements. If it is determined that the business data flow matches the group identification rule according to the specific detection rule, it can be determined that the business data flow corresponds to the QoS requirement associated with the matched group identification rule, so that the business data flows corresponding to different QoS requirements can be distinguished. Furthermore, based on the QoS requirements corresponding to different business data flows, the business data flows corresponding to the same QoS requirements can be divided into the same task QoS flow.

[0278] Case 2: The QoS parameters of the task include QoS parameters related to computing. For example, the policy and charging rules acquired by the anchor network element include at least one of the following: specific QoS requirement information related to computing, an identifier indicating specific QoS requirements related to computing, information of an execution network element for executing a computing function, an identifier of a computing subtask, or a computing type of a computing subtask. For details, please refer to the above introduction to S403.

[0279] In this case, the resource-level QoS parameters generated by the anchor network element may include a computing dimension. In one possible implementation, the QoS parameters of the computing dimension may include at least one of the following: specific QoS requirement information related to computing, an identifier indicating specific QoS requirements related to computing, or a computing subtask identification rule (computing detection rule, CDR). The computing subtask identification rule is used to distinguish computing subtasks corresponding to different QoS requirements.

[0280] The following introduces a possible implementation method for distinguishing computing subtasks corresponding to different QoS requirements based on computing subtask identification rules. The computing subtask identification rules include specific detection rules, and different computing subtask identification rules are associated with different QoS requirements. If, according to the specific detection rules, it is determined that the computing subtask matches the computing subtask identification rule, it can be determined that the computing subtask corresponds to the QoS requirement associated with the matched computing subtask identification rule, so that the computing subtasks corresponding to different QoS requirements can be distinguished.

[0281] Case 3: The QoS parameters of the task include QoS parameters related to data. For example, the policy and charging rules acquired by the anchor network element include at least one of the following: specific QoS requirement information related to data, an identifier indicating specific QoS requirements related to data, a data type or a data size. For details, please refer to the introduction to S403 above.

[0282] In this case, the resource-level QoS parameters generated by the anchor network element may include a data dimension. In one possible implementation, the QoS parameters of the data dimension may include at least one of the following: specific QoS requirement information related to the data, an identifier indicating the specific QoS requirement related to the data, or a data subtask identification rule (date detection rule, DDR). Among them, the data subtask identification rule is used to distinguish data subtasks corresponding to different QoS requirements. Distinguishing data subtasks corresponding to different QoS requirements according to the data subtask identification rule can be specifically referred to distinguishing computing subtasks corresponding to different QoS requirements according to the computing subtask identification rule, which will not be expanded here.

[0283] Case 4: The QoS parameters of the task include QoS parameters related to the algorithm. For example, the policy and charging rules obtained by the anchor network element include at least one of the following: QoS specific requirement information related to the algorithm, an identifier indicating the QoS specific requirement related to the algorithm, the algorithm type, the algorithm level or the application method. For details, please refer to the introduction of S403 above.

[0284] In this case, the resource-level QoS parameters generated by the anchor network element may include an algorithm dimension. In one possible implementation, the QoS parameters of the algorithm dimension may include at least one of the following: specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, or an algorithm subtask identification rule (model detection rule, MDR). Among them, the algorithm subtask identification rule is used to distinguish algorithm subtasks corresponding to different QoS requirements. For details on distinguishing algorithm subtasks corresponding to different QoS requirements according to the algorithm subtask identification rule, please refer to distinguishing computing subtasks corresponding to different QoS requirements according to the computing subtask identification rule, which will not be expanded here.

[0285] S503: The anchor network element sends resource-level QoS parameters to the execution network element.

[0286] Correspondingly, after receiving the resource-level QoS parameters, the execution network element can execute the task according to the resource-level QoS parameters.

[0287] Based on the communication method provided in the embodiment of the present application, resource-level QoS parameters including four dimensions can be generated, and new services in the communication network also need to coordinate four-dimensional resources. Therefore, the communication method provided in the embodiment of the present application can support the generation of QoS policies for new services in the communication network.

[0288] In a possible implementation of S503, the anchor network element may send corresponding resource-level QoS parameters to the execution network element of each subtask obtained by task decomposition.

[0289] In a possible scenario, the information carrying resource-level QoS parameters sent by the anchor network element to the execution network element may have different names depending on the different execution network elements. Exemplarily, if the execution network element is a terminal device, the information carrying resource-level QoS parameters may also be referred to as a QoS rule (QoS rule), or in other words, the QoS parameters are included in the QoS rule. For another example, if the execution network element is a TPF network element or an sNode, the information carrying resource-level QoS parameters may be referred to as a QoS profile (QoS profile), or in other words, the resource-level QoS parameters are included in the QoS profile. However, the embodiments of the present application do not limit the name of the information used to carry resource-level QoS parameters.

[0290] Optionally, after S503, the embodiment of the present application may further include the following steps:

[0291] The anchor network element receives notification information from the execution network element, where the notification information is used to notify the execution network element that the corresponding QoS requirement (QoS requirement related to connection, calculation, data or algorithm) cannot be met.

[0292] Optionally, after receiving the notification information, the anchor network element may schedule network resources to ensure that the execution network element can meet the corresponding QoS requirements.

[0293] Optionally, after receiving the notification information, the anchor network element may feedback to other network elements that the execution network element cannot meet the corresponding QoS requirement. For example, the anchor network element may feedback to the policy control function network element that the execution network element cannot meet the corresponding QoS requirement.

[0294] In addition, in a possible situation, the anchor network element may determine whether to send the resource-level QoS parameters to the execution network element according to the functions that the modules inside the execution network element are responsible for.

[0295] For example, assuming that the resource-level QoS parameters include the data-dimensional QoS parameters, if the module responsible for executing the data function (hereinafter referred to as the data execution module) in the execution network element also integrates the calculation and algorithm functions, the anchor network element can directly send the resource-level QoS parameters to the data execution module.

[0296] If the data execution module, the module responsible for executing the computing function (hereinafter referred to as the computing execution module) and the module responsible for executing the algorithm function (hereinafter referred to as the algorithm execution module) are independent modules inside the execution network element, that is, the data execution module does not integrate the computing and algorithm functions, then the computing execution module can be managed by the module responsible for controlling the task computing resources inside the anchor network element (hereinafter referred to as the computing control module), and the algorithm execution module can be managed by the module responsible for controlling the task algorithm resources inside the anchor network element (hereinafter referred to as the algorithm control module). It can also be understood that the execution computing and / or algorithm functions provided by the execution network element are managed by the corresponding modules in the anchor network element. In this case, after the anchor network element obtains the resource-level QoS parameters, the module responsible for controlling the task data resources inside the anchor network element (hereinafter referred to as the data control module) can call the corresponding computing and / or algorithm functions to the computing control module and / or the algorithm control module. If the computing function is called, the data control module can send the corresponding QoS parameters of the computing dimension to the computing control module. If the algorithm function is called, the data control module can send the corresponding QoS parameters of the algorithm dimension to the algorithm control module.

[0297] For another example, assuming that the resource-level QoS parameters include the algorithm-dimensional QoS parameters, if the algorithm execution module in the execution network element also integrates the computing and data functions, the anchor network element can directly send the resource-level QoS parameters to the algorithm execution module.

[0298] If the data execution module, the computing execution module and the algorithm execution module are independent modules inside the execution network element, that is, the algorithm execution module does not integrate computing and data functions, then the computing execution module can be managed by the computing control module inside the anchor network element, and the data execution module can be managed by the data control module inside the anchor network element. It can also be understood that the execution computing and / or data functions provided by the execution network element are managed by the corresponding modules in the anchor network element. In this case, after the anchor network element obtains the resource-level QoS parameters, the algorithm control module inside the anchor network element can call the corresponding computing and / or data functions to the computing control module and / or the data control module. If the computing function is called, the algorithm control module can send the corresponding computing dimension QoS parameters to the computing control module. If the data function is called, the algorithm control module can send the corresponding data dimension QoS parameters to the data control module.

[0299] For another example, if the QoS parameters at the resource level include QoS parameters at the computing dimension level, the anchor network element may directly send the QoS parameters at the computing dimension level to the computing execution module.

[0300] In one possible scenario of the above example, when the data control or algorithm control module calls a computing function, it can determine a new execution network element that executes the computing function, as well as identification information of a new computing subtask (such as a new computing subtask ID), and send it to the computing control module.

[0301] In one possible scenario of the above example, when the data control module calls the algorithm function, it can determine the QoS parameters of the new algorithm dimension and send them to the algorithm control module.

[0302] In one possible scenario of the above example, when the algorithm control module calls the data function, it can determine the QoS parameters of the new data dimension and send them to the data control module.

[0303] In the embodiments of the present application, the description of the interaction between the internal modules of the network element is to facilitate the understanding of the technical solution of the present application, while the description of the logical interaction between the internal modules does not mean that there must be actual interaction steps between the internal modules when the network element executes the communication method of the embodiments of the present application.

[0304] See also Figure 6 Another communication method provided in an embodiment of the present application includes steps S601-S602:

[0305] S601: An executing network element obtains a resource-level QoS parameter, wherein the resource-level QoS parameter includes at least one of the following: a connection dimension, a computing dimension, a data dimension, or an algorithm dimension.

[0306] The resource-level QoS parameters may be specifically referred to the above introduction to the resource-level QoS parameters in S502, which will not be elaborated here.

[0307] The embodiment of the present application does not limit the network element from which the execution network element obtains the resource-level QoS parameters. Exemplarily, the execution network element may obtain the resource-level QoS parameters from an anchor network element.

[0308] S602: The execution network element executes the task according to the resource-level QoS parameters.

[0309] Based on the communication method provided in the embodiment of the present application, tasks can be executed according to resource-level QoS parameters, thereby achieving QoS management of four-dimensional resources of the task.

[0310] In a possible implementation of S602, the execution network element may adjust the policy or allocate resources in a targeted manner according to the acquired resource-level QoS parameters to meet the requirements of the resource-level QoS parameters. For example, assuming that the resource-level QoS parameters include latency requirements, the execution network element may allocate computing power that can meet the latency requirements in a targeted manner to execute the corresponding function.

[0311] In one possible scenario, when the execution network element executes a task, different types of subtasks can be executed by internal modules responsible for different functions. Alternatively, when the execution network element executes a task, multiple types of subtasks can be executed by an internal module that integrates multiple functions. For example, assuming that the module responsible for executing the computing function (which can be called the computing execution module) inside the execution network element also integrates the algorithm and data functions, the computing execution module can execute the computing subtask, the algorithm subtask, and the data subtask.

[0312] In another possible situation, the anchor network element may manage some modules in the execution network element, thereby scheduling corresponding functions to execute subtasks. For details, please refer to the introduction of S503 above, which will not be repeated here.

[0313] Optionally, if the executing network element finds that it cannot meet the QoS requirements related to connection, computing, data or algorithms in the acquired resource-level QoS parameters, the executing network element may send a notification message to the anchor network element, and the notification message is used to notify the executing network element that it cannot meet the QoS requirements related to connection, computing, data or algorithms.

[0314] See also Figure 7 Another communication method provided in an embodiment of the present application includes steps S701-S702:

[0315] S701. The task scheduling network element obtains QoS parameters of a first service.

[0316] The QoS parameters of the first service may be specifically referred to the above introduction to the QoS parameters of the first service in S402, which will not be elaborated here.

[0317] The embodiment of the present application does not limit the network element from which the task orchestration network element obtains the QoS parameters of the first service. For example, the task orchestration network element may obtain the QoS parameters of the first service from a unified data pool network element. Optionally, the QoS parameters of the first service stored in the unified data pool network element may be generated by a policy control function network element.

[0318] Optionally, a possible implementation of S701 may be: the task scheduling network element obtains a QoS template corresponding to the first service. The QoS template includes a mapping relationship between the QoS parameters of the first service and the identification information of the first service. The QoS template corresponding to the first service may be specifically referred to the introduction to S401 above, which will not be expanded here.

[0319] Optionally, before S701, the embodiment of the present application may further include the following steps:

[0320] The task orchestration network element is input into a use case after the instantiation of the first service, wherein the use case may include identification information of the first service or identification information of a QoS parameter of the first service.

[0321] At this time, S701 may be: the task scheduling network element obtains the corresponding QoS parameter of the first service according to the identification information of the first service or the identification information of the QoS parameter of the first service.

[0322] S702: The task scheduling network element performs task scheduling according to the QoS parameters of the first service to obtain a scheduling result with tasks as the granularity, wherein the scheduling result includes the template description information and dependency relationship of the task obtained by decomposing and mapping the first service.

[0323] Based on the communication method provided in the embodiment of the present application, a task scheduling function can be provided for new services in the communication network, especially some more complex services, thereby realizing QoS hierarchical management from services to tasks.

[0324] The arrangement result may be specifically referred to the above introduction to S501, which will not be elaborated here.

[0325] Optionally, after S702, the embodiment of the present application may further include the following steps:

[0326] The task orchestration NE sends the orchestration result to the anchor NE.

[0327] Correspondingly, after receiving the orchestration result, the anchor network element can obtain task information according to the orchestration result, wherein the task information includes deployment information and topology information of the task. The anchor network element obtains the task information according to the orchestration result, and the details can be referred to the introduction of S501 above, which will not be expanded here.

[0328] Optionally, if the QoS parameters of the first service include multiple sets of QoS parameters, and each set of QoS parameters has a different priority, the task scheduling network element may first obtain the first priority QoS parameters of the first service, and perform task scheduling according to the first priority QoS parameters.

[0329] Furthermore, if the orchestration based on the first priority QoS parameters fails and no orchestration result is obtained, the task orchestration network element can obtain the second priority QoS parameters of the first service and perform task orchestration according to the second priority QoS parameters.

[0330] Similarly, if the scheduling based on the QoS parameters of the second priority fails, the task scheduling network element may further obtain the QoS parameters of the second priority of the first service and perform task scheduling until the scheduling result is obtained.

[0331] In a possible scenario, the above embodiments may be applied in combination, or may be applied independently.

[0332] In the above embodiment combined with the application scenario, a possible exemplary process includes: the policy control function network element generates the QoS parameters of the first service, further generates the QoS parameters of the task, and sends the QoS parameters of the task to the anchor network element. The anchor network element can generate resource-level QoS parameters based on the acquired QoS parameters of the task, and send them to the execution network element.

[0333] Assume that the policy control function network element is a PCF network element. The unified data pool network element is a UDR network element. The application function network element is an AF (application function) network element. The task orchestration network element is a NAMO network element. The anchor network elements include the TCF network element and the cNode. The execution network elements include the TPF network element, the sNode and the UE. The number of each type of network element can be one or more.

[0334] Figure 8 A schematic diagram of a possible exemplary process is shown in FIG. Figure 8 As shown, the exemplary process includes the following steps:

[0335] S801. The AF network element inputs the service requirements of the first service and the identification information of the first service to the PCF network element, wherein the identification information includes at least one of the following: the use ID of the user triggering the first service, the UE IP of the UE involved in the first service, the SDF information, and the ASP information of the first service.

[0336] For details of S801, please refer to the above introduction to S401, which will not be elaborated here.

[0337] S802: The PCF network element classifies and merges the input of the AF network element, generates a service QoS template, and transmits the service QoS template to the UDR network element. The service QoS template includes a mapping relationship between the QoS parameters of the first service and the identification information of the first service.

[0338] The UDR network element stores the received service QoS template.

[0339] Optionally, each type of QoS of the first service may be identified by a unique Service ID.

[0340] For details of S802, please refer to the above introduction to S402, which will not be elaborated here.

[0341] S803. After the use case is input, the NAMO network element applies to the UDR network element for the service QoS parameters of the corresponding first service according to the SDF information in the use case, at least one of the ASP information or the UE information, or the service ID predefined by the operator. In a possible implementation, when applying for the first time, the NAMO network element applies for the service QoS parameters of the first priority.

[0342] For details of S803, please refer to the above introduction to S701, which will not be elaborated here.

[0343] S804, the NAMO network element performs task scheduling based on the QoS parameters of the first service. If the scheduling based on the service QoS parameters of the first priority fails, the NAMO network element applies to the UDR network element for the service QoS parameters of the second priority and continues scheduling until the scheduling result is obtained.

[0344] S805, NAMO network element transmits the orchestration result to TCF network element and cNode. The orchestration result includes task template description and task dependency. The task template description may include the following information: task type, resource requirement, computational complexity, and running time.

[0345] For details of S804-S805, please refer to the above introduction to S702, which will not be elaborated here.

[0346] S806. The TCF network element and the cNode network element obtain task information according to the orchestration result, and input the task information to the PCF network element.

[0347] The task information includes: the Service ID of the QoS parameter of the first service, the ID of the task obtained by decomposing and mapping the first service, the ID of the execution network element that executes the task, and the task topology information.

[0348] For details of S806, please refer to the above introduction to S501, which will not be elaborated here.

[0349] S807. The PCF network element completes the decomposition of the service QoS parameters into task QoS parameters, generates PCC rules, and inputs them to the TCF network element or cNode.

[0350] The PCC rule includes rule ID, TDF detection, TDF template, 6QI and QoS requirements.

[0351] Among them, TDF detection and TDF template are used to characterize the mapping relationship between TDF and task QoS parameters. Task QoS parameters include 6QI and QoS requirement information, 6QI is an identifier indicating specific QoS requirements, and QoS requirement information is specific QoS requirements.

[0352] For details of S807, please refer to the above introduction to S403, which will not be elaborated here.

[0353] Furthermore, the TCF network element or cNode completes the binding of the task QoS parameters and the task QoS flow according to the PCC rule.

[0354] S808, the TCF network element or cNode completes the mapping of the task QoS parameters to the resource-level QoS parameters, and passes the four-dimensional resource-level QoS parameters to the TPF, sNode or UE. Among them, the resource-level QoS parameters passed to the UE can be included in the QoS rule (QoS rule). The resource-level QoS parameters passed to the TPF or sNode can be included in the QoS profile (QoS profile).

[0355] For details of S808, please refer to the above introduction to S502, which will not be elaborated here.

[0356] In the scenario of combining the above embodiments with the application, another possible exemplary process includes: the policy control function network element sends the QoS parameters of the task to the anchor network element. The anchor network element generates resource-level QoS parameters based on the acquired task QoS parameters and sends them to the execution network element. The execution network element executes the task based on the resource-level QoS parameters.

[0357] The resource-level QoS parameters include four dimensions: connection dimension, computing dimension, data dimension, and calculation dimension. The following introduces possible exemplary processes for different dimensions.

[0358] Assume that the policy control function network element is a PCF network element. The anchor network elements include a TCF network element and a cNode. The execution network elements include a TPF network element, an sNode and a UE. The number of each type of network element can be one or more.

[0359] Fig. 9 FIG. 1 is a schematic diagram of an exemplary process related to the connection dimension. Fig. 9 As shown, the exemplary process includes the following steps:

[0360] S901. The PCF network element transmits the PCC rules to the TCF network element or cNode. In the PCC rules, the connection-related content includes at least one of the following: TDF template (including the ID / IP of the transmission start point execution network element, the ID / IP of the transmission end point execution network element, and the transmission type), 6QI, and connection-related QoS requirements (such as GFBR / MFBR / ARP, etc.).

[0361] For details of S901, please refer to the above introduction to S403, which will not be elaborated here.

[0362] S902. The TCF network element or cNode further splits the task QoS parameters into resource-level QoS parameters and sends them to the TPF network element, sNode or UE.

[0363] Among them, among the resource-level QoS parameters, the QoS parameters of the connection dimension include PDR and QoS configuration / QoS rules (such as 6QI, ARP, GFBR / MFBR, etc.).

[0364] Optionally, the TCF network element or cNode may also send QoS enforcement rules (QER) to the TPF network element, sNode or UE. The QER may indicate which set of QoS parameters to use in different situations. The TPF network element, sNode or UE may select the QoS parameters to use based on the QER.

[0365] Optionally, the method may further include S903: when the TPF, sNode or UE finds that the corresponding QoS requirement cannot be met when executing the connection function, it reports the situation to the TCF network element or cNode through a notification message.

[0366] Fig.10 is a schematic diagram of an exemplary process related to calculation dimensions. Fig.10 The calculation control CC module shown is a module in the TCF network element or cNode that is responsible for managing the calculation dimension resources of the task. The calculation execution CE module is a module in the TPF network element, sNode or UE that is responsible for executing the calculation function.

[0367] Understandably, Fig.10 The interaction diagrams between the modules and network elements shown are logical interaction diagrams given to facilitate understanding of the process and do not represent the actual application. Fig.10 The modules shown send and receive information.

[0368] like Fig.10 As shown, the exemplary process includes the following steps:

[0369] S1001. The PCF network element transmits the PCC rules to the TCF network element or cNode. Among them, the PCC rules, the content related to computing includes at least one of the following: computing flow template (including the ID / IP of the execution network element that executes the computing function, the computing type), 6QI, and computing-related QoS requirements (such as GFLOPS / MFLOPS / ARP, etc.).

[0370] For details of S1001, please refer to the above introduction to S403, which will not be elaborated here.

[0371] S1002. The TCF network element or cNode further splits the task QoS parameters into resource-level QoS parameters and sends them to the TPF network element, sNode or UE.

[0372] Among them, among the resource-level QoS parameters, the QoS parameters of the computing dimension include CDR and QoS configuration / QoS rules (such as 6QI, ARP, GFLOPS or MFLOPS, etc.).

[0373] In one possible implementation, the 6QI included in the QoS parameters of the calculation dimension may also be referred to as 6QI-C.

[0374] In a possible implementation, the CC module in the TCF network element or the CC module in the cNode may generate the resource-level QoS parameters.

[0375] S1003. The CE module performs calculation functions according to the QoS parameters of the calculation dimension.

[0376] Specifically, the CE module in the TPF network element, sNode or UE performs the calculation function according to the QoS parameters of the calculation dimension.

[0377] Optionally, the TCF network element or cNode may also send a QER to the TPF network element, sNode or UE. The TPF network element, sNode or UE may select a QoS parameter to be used according to the QER.

[0378] Optionally, the process may further include S1004: when the TPF, sNode or UE finds that the corresponding QoS requirement cannot be met when executing the computing function, the process reports the result to the TCF network element or cNode through a notification message.

[0379] Fig.11 is a schematic diagram of an exemplary process related to data dimensions. Fig.11 The data control DC module shown is the module responsible for the data dimension resources of the TCF network element or cNode responsible for the control task. Fig.10 The algorithm control HicC module is the module in the TCF network element or cNode that is responsible for the algorithm dimension resources of the control task. The data execution DA module is the module in the TPF network element, sNode or UE that is responsible for executing data functions. Fig.10 The algorithm execution HicA module is a module in the TPF network element, sNode or UE that is responsible for executing the algorithm function.

[0380] Understandably, Fig.11 The interaction diagrams between the modules and network elements shown are logical interaction diagrams given to facilitate understanding of the process and do not represent the actual application. Fig.11 The modules shown send and receive information.

[0381] like Fig.11 As shown, the exemplary process includes the following steps:

[0382] S1101. The PCF network element transmits the PCC rules to the TCF network element or cNode. Among the PCC rules, the data-related content includes at least one of the following: data level template (including data type and data size), 6QI, data-related QoS requirements (such as latency / ARP, etc.).

[0383] For details of S1101, please refer to the above introduction to S403, which will not be elaborated here.

[0384] S1102, TCF network element or cNode (for example, the DC module therein) further splits the task QoS parameters into resource-level QoS parameters and sends them to TPF network element, sNode or UE. Among them, in the resource-level QoS parameters, the QoS parameters of the data dimension include DDR and data-related QoS requirements. In a possible implementation, the 6QI included in the QoS parameters of the data dimension can also be called 6QI-D.

[0385] Based on different situations, S1102 has two different implementations: S1102a and S1102b.

[0386] If the DA module is integrated (DA includes computing and algorithm functions in addition to data functions), and the functions integrated in the DA module are sufficient to meet the QoS requirements included in the resource-level QoS parameters, then the exemplary process includes S1102a: the TCF network element or cNode passes the resource-level QoS parameters directly to the DA module.

[0387] If the DA module is non-integrated, or the calculation and / or algorithm functions integrated in the DA are insufficient to meet the QoS requirements included in the resource-level QoS parameters, the exemplary process includes S1102b: the DC module in the TCF network element or cNode calls the calculation and / or algorithm functions to the CC module and / or HicC module (i.e., calls the CE module and / or HicA module), and passes the corresponding QoS parameters to the CC module and / or Hic C module. Exemplarily, the QoS parameters of the calculation dimension sent to the CC module can be included in the calculation request message. The QoS parameters of the algorithm dimension sent to the HicC module can be included in the algorithm request message.

[0388] Optionally, when the DC module calls the computing function to the CC module, it may also send the ID of a new network element that executes the computing function and a new computing subtask ID to the CC module.

[0389] Optionally, when the DC module calls the algorithm function to the HicC module, the QoS parameters sent to the HicC module may be QoS parameters of a new algorithm dimension.

[0390] Optionally, the method may further include S1103: the TPF network element, sNode or UE requests data from a data storage function (DSF) network element, and the DSF network element feeds back data accordingly. The DSF network element is responsible for storing data and / or models.

[0391] like Fig.11 As shown, if the exemplary process includes S1102a, it also includes S1104a: the DA module executes a data function (eg, data processing).

[0392] If the exemplary process includes S1102b, it also includes S1104b: the called CE module and / or HicA module, and the DA module perform a data function (eg, data processing).

[0393] Optionally, the process may further include S1105: when the TPF, sNode or UE finds that the corresponding QoS requirement cannot be met when executing a data function, the process reports the problem to the TCF network element or cNode through a notification message.

[0394] Fig.12 is a schematic diagram of an exemplary process related to the algorithm dimension. Fig.12 The DC module, CC module, HicC module, DA module, CE module, HicA module or DSF network element shown in the figure can refer to the above description. Fig.11 Introduction.

[0395] Understandably, Fig.12 The interaction diagrams between the modules and network elements shown are logical interaction diagrams given to facilitate understanding of the process and do not represent the actual application. Fig.12 The modules shown send and receive information.

[0396] like Fig.12 As shown, the exemplary process includes the following steps:

[0397] S1201. The PCF network element transmits the PCC rules to the TCF network element or cNode. Among them, the algorithm-related content in the PCC rules includes at least one of the following: model level template (including model type, model level and application mode), 6QI, algorithm-related QoS requirements (such as training and inference latency, inference accuracy or ARP, etc.).

[0398] For details of S1201, please refer to the above introduction to S403, which will not be elaborated here.

[0399] S1202, TCF network element or cNode further splits the task QoS parameters into resource-level QoS parameters and sends them to TPF network element, sNode or UE. Among them, in the resource-level QoS parameters, the algorithm-dimensional QoS parameters include MDR and algorithm-related QoS requirements. In a possible implementation, the 6QI included in the algorithm-dimensional QoS parameters can also be called 6QI-M.

[0400] Based on different situations, S1202 has two different implementations: S1202a and S1202b.

[0401] If the HicA module is integrated (HicA includes computing and data functions in addition to algorithm functions), and the functions integrated in the HicA module are sufficient to meet the QoS requirements included in the resource-level QoS parameters, then the exemplary process includes S1202a: the TCF network element or cNode directly passes the resource-level QoS parameters to the HicA module.

[0402] If the HicA module is non-integrated, the exemplary process includes S1202b: the HicC module in the TCF network element or cNode calls the calculation and / or data function (i.e., calls the CE and / or DA module) to the CC module and / or DC module, and passes the corresponding QoS parameters to the CC module and / or DC module. Exemplarily, the QoS parameters of the calculation dimension sent to the CC module can be included in the calculation request message. The QoS parameters of the data dimension sent to the DC module can be included in the data request message.

[0403] Optionally, when the HicC module calls the calculation function to the CC module, it may also send the ID of a new network element that executes the calculation function and a new calculation subtask ID to the CC module.

[0404] Optionally, when the HicC module calls a data function to the DC module, the QoS parameters sent to the DC module may be QoS parameters of a new data dimension.

[0405] Optionally, S1203 may also be included: the TPF network element, sNode or UE requests the DSF network element for the model and data, and the DSF network element accordingly feeds back the model and data. When the TPF network element, sNode or UE obtains the model and data, data plane preprocessing is not required and the model and data can be directly obtained.

[0406] like Fig.12 As shown, if the exemplary process includes S1202a, it also includes S1204a: the HicA module executes an algorithm function (eg, algorithm processing).

[0407] If the exemplary process includes S1202b, it also includes S1204b: the called CE module and / or DA module, and the HicA module execute the algorithm function (eg, algorithm processing).

[0408] Optionally, the process may further include S1205: when the TPF, sNode or UE finds that the corresponding QoS requirement cannot be met when executing the algorithm function, the process reports the result to the TCF network element or cNode through a notification message.

[0409] In one possible scenario, Figure 8 , Fig. 9 , Fig.10 , Fig.11 and Fig.12 The various processes shown in the flow chart can be combined and applied. Figure 8 , Fig. 9 , Fig.10 , Fig.11 or Fig.12 The process shown can also be applied independently.

[0410] In addition, different network elements in the above embodiments may also form a variety of end-to-end connection architectures. Fig.13 A possible end-to-end architecture applicable to the embodiments of the present application. Fig.13 As shown, the connected network elements can communicate with each other.

[0411] based on Fig.13 For the architecture shown, a possible QoS parameter generation mechanism can be:

[0412] The PCF network element can obtain information from the charging function (CHF) network element, the NWDAF network element, and the AF network element. Among them, the CHF network element can provide billing-related information. The NWDAF network element can provide data statistics or forecast information of certain network functions or network services. The AF network element can provide user ID, UE IP, media type, bandwidth requirements, ASP information, SDF information, the type of the first service (for example, the first service is an AI service, a perception service, a computing service, or a data service), the requirement information of the first service, etc. Based on the above-obtained information, the PCF network element can generate service-level QoS parameters and store them in the UDR network element. After the NAMO network element obtains the use case input by the AF network element, it can obtain the corresponding service-level QoS parameters from the UDR network element, and perform task orchestration according to the service-level QoS parameters to obtain the orchestration result. The NAMO network element passes the orchestration result to each TA (in the form of Fig.13 The TCF network element and cNode in the example). The TCF network element and cNode obtain the task information according to the orchestration result and provide the task information to the PCF network element. The PCF network element decomposes and maps the service-level QoS parameters according to the task information, generates the task-level QoS parameters, and passes the task-level QoS parameters to the TCF network element or cNode. Finally, the TCF network element and cNode determine the TE (in terms of Fig.13 Taking the TPF network element, sNode and UE in the example), the task-level QoS parameters are decomposed and mapped, and the resource-level QoS parameters are generated and passed to the corresponding TPF network element, sNode or UE.

[0413] It can be seen that based on the communication method provided in the embodiment of the present application, end-to-end QoS differentiation and guarantee services can be provided for new services in the communication network.

[0414] The above mainly introduces the scheme provided by the embodiment of the present application from the perspective of interaction between various network elements. Accordingly, the embodiment of the present application also provides a communication device, which is used to implement the above various methods. The communication device can be each network element in the above method embodiment, or a device including each network element, or a component that can be used for each network element. It can be understood that in order to implement the above functions, the communication device includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware 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 to exceed the scope of the present application.

[0415] The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be understood that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0416] Fig.14 The structure diagram of a communication device 1400 is shown. The communication device 1400 includes a processing module 1401 and a transceiver module 1402. Optionally, the communication device 1400 may also include a storage module 1403. The transceiver module 1402, which may also be called a transceiver unit, is used to implement the transceiver function, for example, it may be a transceiver circuit, a transceiver, a transceiver or a communication interface.

[0417] Taking the communication device 1400 as the policy control function network element in the above embodiment as an example, in a possible implementation manner:

[0418] The transceiver module 1402 is used to obtain task information and requirement information of the first service; the task information includes relevant information of the task obtained by decomposing and mapping the first service. The processing module 1401 is used to generate QoS parameters of the first service according to the requirement information of the first service. The processing module 1401 is also used to generate QoS parameters of the task according to the task information and the QoS parameters of the first service.

[0419] Optionally, the transceiver module 1402 obtains the requirement information of the first service, including: obtaining relevant information of the first service, the relevant information of the first service including one or more of the following: the requirement information of the first service or the identification information of the first service, and there is a mapping relationship between the identification information of the first service and the requirement information of the first service.

[0420] Optionally, the processing module 1401 generates QoS parameters for the first service according to the requirement information of the first service, including: generating a QoS template corresponding to the first service according to the relevant information of the first service, the QoS template including a mapping relationship between the QoS parameters of the first service and the identification information of the first service.

[0421] Optionally, the transceiver module 1402 is further configured to send QoS parameters of the first service to the unified data pool network element.

[0422] Optionally, the processing module 1401 generates the QoS parameters of the task according to the task information and the QoS parameters of the first service, including: generating a policy and charging control rule according to the task information and the QoS parameters of the first service. The policy and charging rule include the QoS parameters of the task, and a mapping relationship between the QoS parameters of the task and at least one of the execution network element or the task data flow that executes the task.

[0423] Optionally, the transceiver module 1402 is further used to send the QoS parameters of the task to the anchor network element, and the QoS parameters of the task are used by the anchor network element to generate resource-level QoS parameters. The resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension, and algorithm dimension.

[0424] Taking the communication device 1400 as the anchor network element in the above embodiment as an example, in a possible implementation manner:

[0425] The transceiver module 1402 is used to obtain the QoS parameters of the task. The processing module 1401 is used to generate the resource-level QoS parameters according to the QoS parameters of the task and the execution network element that executes the task; the resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension and algorithm dimension. The transceiver module 1402 is also used to send the resource-level QoS parameters to the execution network element.

[0426] Optionally, the transceiver module 1402 is further used to obtain the task scheduling result, which includes the template description information and dependency relationship of the task. The processing module 1401 is further used to obtain task information according to the scheduling result, which includes at least one of the deployment information or topology information of the task.

[0427] Optionally, the transceiver module 1402 is further used to send task information to the policy control function network element, and the task information is used for the policy control function network element to generate QoS parameters of the task.

[0428] Optionally, the transceiver module 1402 obtains the QoS parameters of the task, including: obtaining policies and billing control rules, the policies and billing rules include the QoS parameters of the task, and a mapping relationship between the QoS parameters of the task and at least one of the execution network elements or task data flows that execute the task.

[0429] Optionally, the transceiver module 1402 is further used to receive notification information from the execution network element, where the notification information is used to notify the execution network element that QoS requirements related to connection, calculation, data or algorithm cannot be met.

[0430] Taking the communication device 1400 as an execution network element in the above embodiment as an example, in a possible implementation manner:

[0431] The transceiver module 1402 is used to obtain resource-level QoS parameters; the resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension or algorithm dimension. The processing module 1401 is used to execute tasks according to the resource-level QoS parameters.

[0432] Optionally, the transceiver module 1402 is further used to send notification information to the anchor network element, where the notification information is used to notify the execution network element that QoS requirements related to connection, calculation, data or algorithm cannot be met.

[0433] Taking the communication device 1400 as the task scheduling network element in the above embodiment as an example, in a possible implementation manner:

[0434] The transceiver module 1402 is used to obtain the QoS parameters of the first service. The processing module 1401 is used to perform task scheduling according to the QoS parameters of the first service to obtain a scheduling result with tasks as the granularity; the scheduling result includes the template description information and dependency relationship of the tasks obtained by decomposing and mapping the first service.

[0435] The transceiver module 1402 is used to obtain the QoS parameters of the first service. The processing module 1401 is used to perform task scheduling according to the QoS parameters of the first service to obtain a scheduling result with tasks as the granularity; the scheduling result includes the template description information and dependency relationship of the tasks obtained by decomposing and mapping the first service.

[0436] Optionally, the transceiver module 1402 is further configured to send an orchestration result to the anchor network element, where the orchestration result is used for the anchor network element to obtain task information, where the task information includes at least one of deployment information or topology information of the task.

[0437] Optionally, the transceiver module 1402 obtains the QoS parameters of the first service, including: obtaining a QoS template corresponding to the first service, the QoS template including a mapping relationship between the QoS parameters of the first service and identification information of the first service.

[0438] Optionally, the transceiver module 1402 obtains the QoS parameters of the first service, including: obtaining the QoS parameters of the first priority of the first service. The processing module 1401 performs task scheduling according to the QoS parameters of the first service, including: performing task scheduling according to the QoS parameters of the first priority. If the scheduling according to the QoS parameters of the first priority fails, the transceiver module 1402 is further used to obtain the QoS parameters of the second priority of the first service, and the processing module 1401 is further used to schedule tasks according to the QoS parameters of the second priority.

[0439] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.

[0440] Optionally, Fig.14 The modules in the system may also be referred to as units. For example, the processing module may be referred to as a processing unit, and the transceiver module may be referred to as a transceiver unit. Fig.14 In the illustrated embodiment, the names of the various units may not be the names shown in the figure. For example, the transceiver module may also be called a communication module or a communication unit.

[0441] Fig.14 If each unit in the embodiment is implemented in the form of a software function module 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 is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The storage medium for storing computer software products includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program codes.

[0442] In the embodiment of the present application, the communication device 1400 is presented in the form of dividing each functional module in an integrated manner. The "module" here may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and a memory that executes one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0443] In a simple embodiment, those skilled in the art will appreciate that the communication device 1400 may be used Fig.15 The form of the communication device shown.

[0444] like Fig.15 As shown, the communication device 1500 includes one or more processors 1501, a communication line 1502, and at least one communication interface ( Fig.15 The example in which the communication interface 1504 and a processor 1501 are included is merely exemplary), and a memory 1503 may also be included optionally.

[0445] The processor 1501 may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present application.

[0446] The communication line 1502 may include a path for connecting different components.

[0447] The communication interface 1504 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, terminal, wireless local area network (WLAN), etc. For example, the transceiver module may be a device such as a transceiver or a transceiver. Optionally, the communication interface 1504 may also be a transceiver circuit or an input / output interface located in the processor 1501, for realizing signal input and signal output of the processor.

[0448] The memory 1503 may be a device with a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a communication line 1502. The memory may also be integrated with the processor.

[0449] The memory 1503 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 1501. The processor 1501 is used to execute the computer-executable instructions stored in the memory 1503, thereby realizing the communication method provided in the embodiment of the present application.

[0450] Alternatively, optionally, in an embodiment of the present application, the processor 1501 may also perform processing-related functions in the communication method provided in the following embodiments of the present application, and the communication interface 1504 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiments of the present application.

[0451] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0452] In a specific implementation, as an embodiment, the processor 1501 may include one or more CPUs, such as Fig.15 CPU0 and CPU1 in.

[0453] In a specific implementation, as an embodiment, the communication device 1500 may include multiple processors, such as Fig.151501 and processor 1507 in the embodiment. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include but are not limited to at least one of the following: a CPU, a microprocessor, a digital signal processing (DSP), a microcontroller unit (MCU), or an artificial intelligence processor, etc., and each computing device may include one or more cores for executing software instructions to perform calculations or processing.

[0454] In a specific implementation, as an embodiment, the communication device 1500 may further include an output device 1505 and an input device 1506. The output device 1505 communicates with the processor 1501 and may display information in a variety of ways. For example, the output device 1505 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1506 communicates with the processor 1501 and may receive user input in a variety of ways. For example, the input device 1506 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0455] The above-mentioned communication device 1500 may also be sometimes referred to as a communication device, which may be a general device or a dedicated device. For example, the communication device 1500 may be the terminal device, access network device or a device having Fig.15 The embodiment of the present application does not limit the type of the communication device 1500.

[0456] also, Fig.15 The structure shown in the figure does not constitute a limitation on the communication device, except Fig.15 In addition to the components shown, the communication device 1500 may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0457] Optionally, Fig.14 The functions / implementation processes of the transceiver module 1402 and the processing module 1401 can be Fig.15 The processor 1501 in the communication device 1500 shown calls the computer execution instructions stored in the memory 1503 to implement. Or, Fig.14 The function / implementation process of the processing module 1401 in Fig.15The processor 1501 in the communication device 1500 shown calls the computer execution instructions stored in the memory 1503 to implement, Fig.14 The function / implementation process of the transceiver module 1402 can be Fig.15 It is implemented by the communication interface 1504 in the communication device 1500 shown in FIG.

[0458] It should be understood that one or more of the above modules or units can be implemented by software, hardware or a combination of the two. When any of the above modules or units are implemented in software, the software exists in the form of computer program instructions and is stored in a memory, and the processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC or ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions for calculation or processing in the processor, it can further include necessary hardware accelerators, such as FPGA, programmable logic device (PLD), or logic circuits that implement dedicated logic operations.

[0459] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a DSP chip, an MCU, an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0460] Optionally, an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the method in any of the above method embodiments. In one possible design, the communication device also includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the method in any of the above method embodiments. Of course, the memory may not be in the communication device. When the communication device is a chip system, it may be composed of chips, or it may include chips and other discrete devices, which is not specifically limited in the embodiments of the present application.

[0461] Optionally, an embodiment of the present application further provides a computer-readable storage medium, which stores a computer program or instruction, and when the computer-readable storage medium is run on a communication device, the communication device can execute the method described in any of the above method embodiments or any of its implementation methods.

[0462] Optionally, an embodiment of the present application further provides a communication system, which includes the network device described in the above method embodiment and the terminal device described in the above method embodiment.

[0463] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more servers that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)).

[0464] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other changes to the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0465] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, a person skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: The method comprises: Acquire task information and requirement information of the first service; the task information includes relevant information of the task obtained by decomposing and mapping the first service; generating a quality of service QoS parameter for the first service according to the requirement information of the first service; Generate the QoS parameters of the task according to the task information and the QoS parameters of the first service.

2. The method according to claim 1, characterized in that The obtaining the requirement information of the first service includes: Relevant information of the first service is obtained, where the relevant information of the first service includes one or more of the following: requirement information of the first service or identification information of the first service, and there is a mapping relationship between the identification information of the first service and the requirement information of the first service.

3. The method according to claim 2, characterized in that The identification information of the first service includes at least one of the following: information of a user triggering the first service, information of a terminal device related to the first service, or information of an application service provider.

4. The method according to claim 2 or 3, characterized in that: Generating the QoS parameter of the first service according to the requirement information of the first service includes: A QoS template corresponding to the first service is generated according to the relevant information of the first service, where the QoS template includes a mapping relationship between the QoS parameters of the first service and the identification information of the first service.

5. The method according to any one of claims 1 to 4, characterized in that: The QoS parameters of the first service include multiple sets of QoS parameters, wherein each set of QoS parameters has a different priority.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Send the QoS parameter of the first service to the unified data pool network element.

7. The method according to any one of claims 1 to 6, characterized in that: The task information includes at least one of deployment information or topology information of the task.

8. The method according to any one of claims 1 to 7, characterized in that: The step of generating the QoS parameter of the task according to the task information and the QoS parameter of the first service comprises: Based on the task information and the QoS parameters of the first service, generate policies and charging control rules, the policies and charging rules including the QoS parameters of the task, and a mapping relationship between the QoS parameters of the task and at least one of the execution network element or task data flow that executes the task.

9. The method according to claim 8, characterized in that The policy and charging rules include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, information about the execution network element of the transmission starting point of the service data flow of the task, information about the execution network element of the transmission end point of the service data flow of the task, specific QoS requirement information related to calculation, an identifier indicating the specific QoS requirement related to calculation, information about the execution network element used to perform the calculation function, an identifier of the calculation subtask, the calculation type of the calculation subtask, specific QoS requirement information related to data, an identifier indicating the specific QoS requirement related to data, a data type, a data scale, specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, an algorithm type, an algorithm level, and an application method.

10. The method according to claim 9, characterized in that The policy and charging rules also include the type of business data flow of the task, and the type of business data flow includes calculation, data or algorithm type.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: The QoS parameters of the task are sent to the anchor network element; the QoS parameters of the task are used by the anchor network element to generate resource-level QoS parameters, and the resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension and algorithm dimension.

12. A communication method, characterized in that: The method comprises: Get the QoS parameters of the task; Generate resource-level QoS parameters according to the QoS parameters of the task and the execution network element executing the task; the resource-level QoS parameters include at least one of the following: connection dimension, calculation dimension, data dimension and algorithm dimension; The resource-level QoS parameters are sent to the execution network element.

13. The method according to claim 12, characterized in that The task is obtained by decomposing and mapping the first service, and the QoS parameters of the task are obtained according to the QoS parameters of the first service.

14. The method according to claim 12 or 13, characterized in that The quality of service (QoS) parameters of the task are obtained, including: Acquire a policy and charging control rule, wherein the policy and charging control rule includes a QoS parameter of the task, and a mapping relationship between the QoS parameter of the task and at least one of an execution network element or a task data flow that executes the task.

15. The method according to claim 14, characterized in that The policy and charging rules include at least one of the following: specific QoS requirement information related to the connection, an identifier indicating the specific QoS requirement related to the connection, information about the execution network element of the transmission starting point of the service data flow of the task, information about the execution network element of the transmission end point of the service data flow of the task, specific QoS requirement information related to calculation, an identifier indicating the specific QoS requirement related to calculation, information about the execution network element used to perform the calculation function, an identifier of the calculation subtask, the calculation type of the calculation subtask, specific QoS requirement information related to data, an identifier indicating the specific QoS requirement related to data, a data type, a data scale, specific QoS requirement information related to the algorithm, an identifier indicating the specific QoS requirement related to the algorithm, an algorithm type, an algorithm level, and an application method.

16. The method according to claim 15, characterized in that The policy and charging rules also include the type of business data flow of the task, and the type of business data flow includes calculation, data or algorithm type.

17. The method according to claim 15 or 16, characterized in that The QoS parameter of the connection dimension includes at least one of the following: the QoS specific requirement information related to the connection, the identifier indicating the QoS specific requirement related to the connection, and a packet identification rule; wherein the packet identification rule is used to distinguish service data flows corresponding to different QoS requirements; and / or, The QoS parameter of the computing dimension includes at least one of the following: the specific QoS requirement information related to the computing, the identifier indicating the specific QoS requirement related to the computing, and the computing subtask identification rule; wherein the computing subtask identification rule is used to distinguish computing subtasks corresponding to different QoS requirements; and / or, The QoS parameter of the data dimension includes at least one of the following: the specific QoS requirement information related to the data, the identifier indicating the specific QoS requirement related to the data, and a data subtask identification rule; wherein the data subtask identification rule is used to distinguish data subtasks corresponding to different QoS requirements; and / or, The QoS parameters of the algorithm dimension include at least one of the following: the specific QoS requirement information related to the algorithm, the identifier indicating the specific QoS requirement related to the algorithm, and the algorithm subtask identification rule; wherein the algorithm subtask identification rule is used to distinguish the algorithm subtasks corresponding to different QoS requirements.

18. The method according to any one of claims 12 to 17, characterized in that: The method further comprises: Notification information is received from the execution network element, where the notification information is used to notify the execution network element that a QoS requirement related to connection, calculation, data or algorithm cannot be met.

19. A communication method, characterized in that: The method comprises: Obtaining resource-level quality of service (QoS) parameters; the resource-level QoS parameters include parameters of at least one of the following dimensions: connection dimension, calculation dimension, data dimension, or algorithm dimension; The task is executed according to the QoS parameters of the resource level.

20. The method according to claim 19, characterized in that The resource-level QoS parameters are obtained based on the QoS parameters of the task, wherein the task is obtained by decomposing and mapping the first service, and the QoS parameters of the task are obtained based on the QoS parameters of the first service.

21. The method according to claim 19 or 20, characterized in that The QoS parameter of the connection dimension includes at least one of the following: the QoS specific requirement information related to the connection, the identifier indicating the QoS specific requirement related to the connection, and a packet identification rule; wherein the packet identification rule is used to distinguish service data flows corresponding to different QoS requirements; and / or, The QoS parameter of the computing dimension includes at least one of the following: the specific QoS requirement information related to the computing, the identifier indicating the specific QoS requirement related to the computing, and the computing subtask identification rule; wherein the computing subtask identification rule is used to distinguish computing subtasks corresponding to different QoS requirements; and / or, The QoS parameter of the data dimension includes at least one of the following: the specific QoS requirement information related to the data, the identifier indicating the specific QoS requirement related to the data, and a data subtask identification rule; wherein the data subtask identification rule is used to distinguish data subtasks corresponding to different QoS requirements; and / or, The QoS parameters of the algorithm dimension include at least one of the following: the specific QoS requirement information related to the algorithm, the identifier indicating the specific QoS requirement related to the algorithm, and the algorithm subtask identification rule; wherein the algorithm subtask identification rule is used to distinguish the algorithm subtasks corresponding to different QoS requirements.

22. The method according to any one of claims 19 to 21, characterized in that: The execution network element is a terminal device.

23. The method according to any one of claims 1 to 22, characterized in that: The first service is an artificial intelligence (AI) service, a computing service, a data service or a perception service.

24. A policy control function network element, characterized in that: The policy control function network element includes a module or unit for executing the method according to any one of claims 1-11.

25. An anchor network element, characterized in that: The anchor network element comprises a module or unit for executing the method according to any one of claims 12-18.

26. An execution network element, characterized in that: The execution network element includes a module or unit for executing the method described in any one of claims 19-23.

27. A communication device, characterized in that: The communication device comprises: a processor; the processor is used to execute a computer program or instruction stored in a memory, so that the communication device performs the method as described in any one of claims 1-11 or 12-18 or 19-23.

28. A chip system, characterized in that: include: processor and interface circuits; The interface circuit is used to receive computer execution instructions and transmit them to the processor; The processor is configured to execute the computer-executable instructions so that the communication device performs the method according to any one of claims 1-11, 12-18, or 19-23.

29. A computer-readable storage medium, characterized in that: A computer program or instruction is stored thereon, and when the computer program or instruction is executed by a computer, the computer is caused to execute the method according to any one of claims 1-11, 12-18 or 19-23.

30. A communication system, characterized in that: The communication system includes a policy control function network element, an anchor network element and an execution network element; The policy control function network element is used to obtain task information and requirement information of the first service, generate a quality of service QoS parameter of the first service according to the requirement information of the first service, generate a QoS parameter of the task according to the task information and the QoS parameter of the first service, and send the QoS parameter of the task to the anchor network element; wherein the task information includes relevant information of the task obtained by decomposing and mapping the first service; The anchor network element is used to receive the QoS parameters of the task from the policy control function network element, and generate resource-level QoS parameters according to the execution network element that executes the task, and send the resource-level QoS parameters to the execution network element; the resource-level QoS parameters include at least one of the following: connection dimension, calculation dimension, data dimension and algorithm dimension; The execution network element is used to receive the resource-level QoS parameters from the anchor network element, and execute tasks according to the resource-level QoS parameters.

Images