Task management method, network architecture, device, equipment, program product and medium

Abstract

The invention provides a task management method, a network architecture, a device, equipment, a program product and a medium, and relates to the technical field of communication. The method is applied to network equipment in a distributed task scheduling network, the distributed task scheduling network comprises a service network element, the network equipment and at least one network function entity, and the method comprises the following steps: acquiring task information of a target task sent by the service network element; obtaining subtask information of at least one subtask corresponding to the target task according to the task information; determining a first target network function entity corresponding to each subtask from the at least one network function entity, the first target network function entity being a network function entity capable of providing a service for executing the subtask; and sending the subtask information of the subtask to the first target network function entity corresponding to the subtask. According to the scheme of the invention, the problem of resource waste caused by resource reservation in the existing scheme is solved.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a task management method, network architecture, device, equipment, program product and medium. Background Art

[0002] In order to flexibly add personalized business applications, the fifth generation mobile communication technology (5G) introduced the concept of multi-access edge computing (MEC). The basic idea is to try to increase policy diversion and cloud computing capabilities in the communication network, and support deployment at the mobile access edge to reduce the end-to-end delay of mobile services.

[0003] In the existing 5G solution, MEC is used as a plug-in for the 5G system. The Radio Access Network (RAN) and the User Plane Function (UPF) are both used as communication channels to execute the pre-configured diversion strategy rules of the system (such as specifying the target IP address of the message, etc.), and route the uplink service data initiated by the User Equipment (UE) to the MEC device, or receive service data from the MEC to the UE.

[0004] However, in the existing solutions, since network deployment and business operation strategies are pre-statically configured, resources need to be reserved according to the maximum resources, resulting in serious waste of resources and difficulty in adapting to the multi-scenario business requirements of the Sixth Generation Mobile Communication Technology (6G). Summary of the invention

[0005] The purpose of the present invention is to provide a task management method, network architecture, device, equipment, program product and medium, which solves the problem of resource waste due to the need for resource reservation in existing solutions.

[0006] To achieve the above object, an embodiment of the present invention provides a task management method, which is applied to a network device in a distributed task scheduling network, wherein the distributed task scheduling network includes: a service network element, the network device and at least one network function entity, and the method includes:

[0007] Obtaining task information of the target task sent by the service network element;

[0008] Obtaining subtask information of at least one subtask corresponding to the target task according to the task information;

[0009] Determine, from the at least one network function entity, a first target network function entity corresponding to each of the subtasks, where the first target network function entity is a network function entity that can provide a service for executing the subtask;

[0010] The subtask information of the subtask is sent to the first target network function entity corresponding to the subtask.

[0011] Optionally, the method further comprises:

[0012] Obtaining a subtask execution result sent by the first target network function entity;

[0013] In the case where the subtask execution result indicates that the subtask execution fails, determining whether there is a second target network function entity, where the second target network function entity is a network function entity other than the first target network function entity that can provide a service for executing the subtask;

[0014] In a case where it is determined that the second target network functional entity exists, the subtask information of the subtask is sent to the second target network functional entity.

[0015] Optionally, the method further comprises:

[0016] In the case where it is determined that the second target network function entity does not exist, a prompt message is sent to the service network element, where the prompt message is used to prompt that the execution of the target task has failed.

[0017] Optionally, the task information includes at least one of the following:

[0018] Task name;

[0019] Quality of Service (QoS);

[0020] Services related to the stated objectives;

[0021] The coordinates of the service associated with the target task;

[0022] The execution sequence of services related to the target task.

[0023] To achieve the above object, an embodiment of the present invention provides a task management method, which is applied to a service network element in a distributed task scheduling network, wherein the distributed task scheduling network includes: the service network element, a network device and at least one network function entity, including:

[0024] Send task information of the target task.

[0025] Optionally, the method further comprises:

[0026] Acquire prompt information sent by the network device, where the prompt information is used to prompt that the target task fails to be executed;

[0027] According to the prompt information, adjust the task information to obtain target task information;

[0028] The target task information is sent to the network device.

[0029] To achieve the above object, an embodiment of the present invention provides a task management device, which is applied to a network device in a distributed task scheduling network, wherein the distributed task scheduling network includes: a service network element, the network device and at least one network function entity, and the device includes:

[0030] A first acquisition module, used to acquire task information of the target task sent by the service network element;

[0031] A first processing module, configured to obtain subtask information of at least one subtask corresponding to the target task according to the task information;

[0032] A second processing module is used to determine a first target network function entity corresponding to each of the subtasks from the at least one network function entity, where the first target network function entity is a network function entity that can provide a service for executing the subtask;

[0033] The first sending module is used to send the subtask information of the subtask to the first target network function entity corresponding to the subtask.

[0034] Optionally, the device further comprises:

[0035] A second acquisition module, used to obtain the subtask execution result sent by the first target network function entity;

[0036] A third processing module is used to determine whether there is a second target network function entity when the subtask execution result indicates that the subtask execution fails, where the second target network function entity is a network function entity other than the first target network function entity that can provide a service for executing the subtask;

[0037] The third sending module is used to send the subtask information of the subtask to the second target network function entity when it is determined that the second target network function entity exists.

[0038] Optionally, the device further comprises:

[0039] The fourth sending module is used to send a prompt message to the service network element when it is determined that the second target network function entity does not exist, and the prompt message is used to prompt that the target task execution fails.

[0040] Optionally, the task information includes at least one of the following:

[0041] Task name;

[0042] Quality of Service (QoS);

[0043] Services related to the stated objectives;

[0044] The coordinates of the service associated with the target task;

[0045] The execution sequence of services related to the target task.

[0046] To achieve the above object, an embodiment of the present invention provides a task management device, which is applied to a service network element in a distributed task scheduling network, wherein the distributed task scheduling network includes: the service network element, a network device and at least one network function entity, and the device includes:

[0047] The second sending module is used to send task information of the target task.

[0048] Optionally, the device further comprises:

[0049] A third acquisition module is used to acquire prompt information sent by the network device, where the prompt information is used to prompt that the target task fails to execute;

[0050] A fourth processing module, used to adjust the task information according to the prompt information to obtain target task information;

[0051] The fifth sending module is used to send the target task information to the network device.

[0052] To achieve the above object, an embodiment of the present invention provides a device, which is a network device in a distributed task scheduling network, wherein the distributed task scheduling network comprises: a service network element, the network device and at least one network function entity, including a processor and a transceiver, wherein the transceiver is used to obtain task information of a target task sent by the service network element;

[0053] The processor is used to obtain subtask information of at least one subtask corresponding to the target task according to the task information;

[0054] The processor is further configured to determine, from the at least one network function entity, a first target network function entity corresponding to each of the subtasks, where the first target network function entity is a network function entity that can provide a service for executing the subtask;

[0055] The transceiver is further configured to send subtask information of the subtask to the first target network function entity corresponding to the subtask.

[0056] Optionally, the transceiver is further used to obtain a subtask execution result sent by the first target network function entity;

[0057] The processor is further configured to, when the subtask execution result indicates that the subtask execution fails, determine whether there is a second target network function entity, where the second target network function entity is a network function entity other than the first target network function entity that can provide a service for executing the subtask;

[0058] The processor is further configured to, when it is determined that the second target network functional entity exists, send the subtask information of the subtask to the second target network functional entity.

[0059] Optionally, the processor is further used to send a prompt message to the service network element when it is determined that the second target network function entity does not exist, wherein the prompt message is used to prompt that the execution of the target task has failed.

[0060] Optionally, the task information includes at least one of the following:

[0061] Task name;

[0062] Quality of Service (QoS);

[0063] Services related to the stated objectives;

[0064] The coordinates of the service associated with the target task;

[0065] The execution sequence of services related to the target task.

[0066] To achieve the above-mentioned purpose, an embodiment of the present invention provides a device, which is a service network element in a distributed task scheduling network, and the distributed task scheduling network includes: the service network element, network equipment and at least one network function entity, and the device includes a processor and a transceiver, wherein the transceiver is used to send task information of the target task.

[0067] Optionally, the transceiver is further used to obtain prompt information sent by the network device, where the prompt information is used to prompt that the target task fails to be executed;

[0068] The processor is further configured to adjust the task information according to the prompt information to obtain target task information;

[0069] The transceiver is also used to send the target task information to the network device.

[0070] To achieve the above-mentioned purpose, an embodiment of the present invention provides a device, including a transceiver, a processor, a memory, and a program or instruction stored in the memory and executable on the processor; when the processor executes the program or instruction, it implements the task management method applied to the network device as above, or implements the task management method applied to the service network element as above.

[0071] To achieve the above-mentioned purpose, a computer program product is provided, including computer instructions, which, when executed by a processor, implement the steps of the task management method applied to a network device as above, or implement the steps of the task management method applied to a service network element as above.

[0072] To achieve the above-mentioned purpose, an embodiment of the present invention provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps in the task management method applied to the network device as above, or the steps in the task management method applied to the service network element as above are implemented.

[0073] The beneficial effects of the above technical solution of the present invention are as follows:

[0074] In the method of the embodiment of the present invention, the network device can obtain the task information of the target task sent by the service network element, and then obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtasks without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] Figure 1 Schematic diagram of providing edge computing power to RAN;

[0076] Figure 2 is a flowchart of a task management method according to an embodiment of the present invention;

[0077] Figure 3 A schematic diagram of a distributed task scheduling network according to an embodiment of the present invention;

[0078] Figure 4 A schematic diagram of the business logic of providing edge computing power for the RAN of an embodiment of the present invention;

[0079] Figure 5 A flowchart of a task management method according to another embodiment of the present invention;

[0080] Figure 6 is a structural diagram of a task management device according to an embodiment of the present invention;

[0081] Figure 7 is a structural diagram of a task management device according to another embodiment of the present invention;

[0082] Figure 8 is a structural diagram of a device according to an embodiment of the present invention;

[0083] Fig. 9 This is a structural diagram of a device according to another embodiment of the present invention. DETAILED DESCRIPTION

[0084] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0085] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present invention. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0086] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0087] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0088] In the embodiments provided in the present application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0089] Below, the related technology is briefly described.

[0090] The 5G core network control plane relies on the cloud-native concept and defines the service-based network architecture (SBA) in the standard. Among them, the network entity is redefined in the form of network function (NF). Each NF provides independent network function service (NF Service, NFS) to the outside world and can call each other. It is hoped that the communication network will achieve the transformation from the traditional rigid network (fixed functions of network elements, fixed connections between network elements, solidified signaling interaction, etc.) to a service-based flexible network. However, NF is still a standard network element, and any changes to it need to go through a long process from the definition of the 3rd Generation Partnership Project (3GPP) to the development of manufacturers and then to the commercial use of operators.

[0091] In the existing 5G solution, MEC is used as a plug-in for the 5G system. It usually obtains service data from the 5G system in two ways. In these ways, RAN and User Plane Function (UPF) are used as communication channels to execute the pre-configured diversion strategy rules of the system (such as specifying the target IP address of the message, etc.), route the uplink service data initiated by the UE to the MEC device, or receive service data from the MEC to the UE.

[0092] It should be noted that the current communication network is used as a data pipeline, and the network deployment and business operation strategies are all statically pre-configured. Therefore, in order to expand computing, AI and other capabilities through the MEC model, it is still necessary to manually deploy related applications in advance and modify the configuration parameters of the involved weekly network elements, resulting in a long service opening cycle, high costs, and customization is not universal.

[0093] For example, when UE performs virtual reality (VR), in order to meet the requirements of low latency and high computing power at the same time, it is necessary to add MEC computing services on the RAN side. According to the existing 5G model, considering user roaming, it is necessary to deploy computing functions in all RAN equipment rooms in advance and reserve resources according to the maximum traffic model; it is necessary to manually configure the QoS guarantee policy of VR services on PCF and all RANs; it is necessary to customize the RAN version to support forwarding VR service uplink traffic to VR computing services instead of sending it to UPF by default.

[0094] The 6G wireless network architecture will not only be a network that provides communication connection management, but will also evolve into a new platform-based network device that integrates multiple elements, including communication, perception, computing, data, intelligence, and security. These elements can be efficiently deployed and flexibly combined on demand to meet diverse business demands. They also have intelligent decision-making and adaptive capabilities, and can interact with businesses in both directions to achieve optimal QoS and business utilization. Therefore, the traditional method of pre-statically deploying networks and customized development has been unable to meet the needs of new business scenarios.

[0095] In summary, the following technical issues need to be addressed in the 6G network architecture:

[0096] (1) Native integration: All functional elements of Tonggansuan Intelligent Security can evolve independently and connect seamlessly based on a common mechanism. They can be combined on demand to provide users with personalized customized network services to meet the needs of different scenarios.

[0097] (2) Open network architecture. Traditional RAN and CN are dedicated integrated solutions, with equipment from a small number of manufacturers forming a partially closed network, which is costly and slow to innovate. The 6G network needs to be an open platform that enables services and provides a unified operating environment support for internal and external applications. Third parties can easily add new application capabilities to the network.

[0098] (3) Intelligent decision-making and adaptive capabilities. Traditional mobile networks use PRB resource reservation (usually according to the maximum resource specification, such as Figure 1 As shown in the figure, the quality of service tasks is guaranteed by deploying computing services in advance near the RAN where the user may roam) or carrying QoS Flow (for example, statically configuring the QoS Flow corresponding to the computing service in the PCR). However, in traditional mobile networks, service policies need to be planned in advance and manually configured on devices from multiple manufacturers, which is difficult to implement and requires maximum resource reservation, which can easily cause serious waste of resources and make it difficult to better adapt to the multi-scenario service requirements of 6G.

[0099] like Figure 2 As shown, a task management method according to an embodiment of the present invention is applied to a network device in a distributed task scheduling network, wherein the distributed task scheduling network includes: a service network element, the network device and at least one network function entity, and the method includes:

[0100] Step 201: Acquire task information of the target task sent by the service network element.

[0101] It should be noted that if Figure 3As shown, with the idea of ​​cloudification / service-oriented, the distributed task scheduling network can be divided into a business domain and a basic domain, wherein the business domain includes the communication plane, computing plane, data plane, etc. in the network, and the business network element can specifically include one or more of the communication plane network element, computing plane network element, data plane network element, etc., while the basic domain that is not related to the business can specifically include network equipment (i.e., the distributed task scheduling concentration point) and at least one network function entity. Among them, the business network element sends tasks to the network equipment, the network equipment sends subtasks to the network function entity, the network function entity feeds back the status to the network equipment, and the network equipment feeds back the status to the business network element. In step 201, the task information of the target task can be sent from the business network element to the network equipment, or the network equipment can actively obtain the task information of the target task.

[0102] Step 202: Obtain subtask information of at least one subtask corresponding to the target task according to the task information.

[0103] Here, the network device may decompose the target task according to the task information, decompose it into one or more subtasks, and obtain subtask information of each subtask.

[0104] In some optional embodiments, the task information may specifically include at least one of the following: task name; quality of service QoS; services related to the target task; coordinates of services related to the target task; execution timing of services related to the target task. Therefore, in step 202, when the network device decomposes the target task, it may decompose the target task according to the services related to the target task. For example, if three services are required to execute the target task, the target task may be decomposed into three subtasks, each subtask corresponding to a service, and the subtask may be subsequently assigned to a network function entity that can provide the service corresponding to the subtask. It is understandable that there may be a situation where multiple network function entities can provide the same service, and there may also be a situation where one network function entity can provide multiple services. For example, if three services are required to execute the target task, the target task may be decomposed into two subtasks, one of which includes two services, and the two subtasks may be assigned to different network function entities.

[0105] Step 203: Determine a first target network function entity corresponding to each of the subtasks from the at least one network function entity, where the first target network function entity is a network function entity that can provide a service for executing the subtask.

[0106] For example, for a certain subtask, there may be multiple network function entities that can provide services to execute the subtask. The network device can further select a network function entity as the first target network function entity corresponding to the subtask, and subsequently assign the subtask to the network function entity.

[0107] Step 204: Send the subtask information of the subtask to the first target network function entity corresponding to the subtask.

[0108] Through step 204, the subtask can be assigned to the first target network function entity selected for the subtask in step 203. After that, after receiving the subtask information, the first target network function entity can execute the subtask corresponding to the subtask information and obtain the subtask execution result.

[0109] In this embodiment, the network device can obtain the task information of the target task sent by the service network element, and then obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtask without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation.

[0110] In some embodiments, the method further includes: obtaining a subtask execution result sent by the first target network function entity; if the subtask execution result indicates that the subtask execution fails, determining whether there is a second target network function entity, the second target network function entity being a network function entity other than the first target network function entity that can provide a service for executing the subtask; if it is determined that the second target network function entity exists, sending the subtask information of the subtask to the second target network function entity. If it is determined that the second target network function entity does not exist, sending a prompt message to the service network element, the prompt message being used to prompt that the target task execution fails.

[0111] It should be noted that if Figure 3 As shown, the distributed task management Client on the network function entity can monitor the QoS execution status on the network function entity and determine whether the network function entity successfully executes the subtask. If the network function entity fails to execute the subtask, it can feedback to the network device.

[0112] In the embodiment of the present invention, the network device can perform dynamic task scheduling, that is, if the first target network function entity fails to execute a subtask, the network device can reschedule and assign the subtask to other network function entities that can execute the subtask (such as the second target network function entity). It should be noted that if the network device confirms that there is no second target network function entity (i.e., a network function entity that can provide services for executing the subtask other than the first target network function entity), it is determined that the subtask cannot be successfully executed, and it can further determine that the target task execution failed, and feedback can be given to the service network element, such as sending a prompt message to the service network element to prompt that the target task execution failed.

[0113] Next, the task management method of the embodiment of the present invention is described by taking UE performing VR computing as an example.

[0114] like Figure 4 As shown in the figure, the network device (i.e., the distributed task scheduling center) receives the VR computing tasks issued by the computing plane and the communication plane, and the network device automatically decomposes the VR computing tasks into subtasks and sends them to the RAN where the UE is located and the cloud platform and UPF device where the UE is located. Among them, the cloud platform is responsible for pulling up new computing nearby RAN1. RAN1 and UPF execute the QoS policy of the subtask, and the local distributed task management Client monitors the QoS execution.

[0115] Specifically, the network equipment is responsible for decomposing the original task (i.e., the target task, such as the VR computing task here) into subtasks and assigning them to specific network elements (i.e., network functional entities), carrying which services of the network element are needed for the current task, as well as the QoS requirements for the services. For example, if the target task is a communication task, the QoS flow policy in the current 5G standard can be sent to RAN and UPF; if the target task is a computing task, in addition to sending the QoS Flow policy to RAN, RAN1 can also be notified that it needs to start or reserve computing services for the computing task according to the given QoS requirements, and needs to monitor the delay between the UE and the computing service.

[0116] Here, the distributed task management client monitors the QoS execution of the local node (that is, the network function entity where the distributed task management client is located) in real time. If it is monitored that the local node cannot meet the QoS requirements (for example, scenarios such as user roaming or network element overload may cause the network element to fail to meet the bandwidth / delay threshold in the subtask QoS), it will report to the network device (that is, the subtask execution result obtained by the network function entity executing the subtask is fed back to the network device), and the network device can reallocate tasks according to the current resource situation in the entire domain. For example: increase the physical resources of the computing service in RAN1, or control the UE to switch to a cell with good channel quality. If the network device cannot find a solution that can meet the task QoS, the network device can notify the upper-layer service (that is, the service network) of the task execution exception, and the upper-layer service can subsequently adjust the target task application QoS demand or stop the target task.

[0117] Through the above process, in the case of subtask execution failure, the network device can re-allocate the subtask according to the situation. If it is impossible to adjust the subtask allocation plan that meets the business requirements, the service network element can be notified that the VR computing task execution failed, so that the service network element can adjust the QoS requirements of the target task or decide to stop the target task. In this way, through the task distributed management mechanism, the execution quality of each network function entity on the subtask is automatically monitored, and the network device can adjust the task distribution in real time to meet the needs of the original task.

[0118] In this embodiment, through the distributed task automatic scheduling mechanism, the network device (i.e., the distributed task scheduling concentration point) can automatically decompose the original task (i.e., the target task) into subtasks according to the network element granularity, and through the subtask automatic distribution mechanism, the subtasks are assigned to the network function entity, and the network function entity enables related services on demand and executes the subtask strategy. In this way, task adaptation can be achieved through the distributed task scheduling of the network device. Compared with the existing solution in which the business strategy needs to be planned in advance and manually configured on multiple devices, and the business deployment cycle is long, the task management method of the embodiment of the present invention can flexibly and efficiently adjust the network deployment and subtask allocation, and can better meet the needs of new businesses.

[0119] In some embodiments, the task information includes at least one of the following: task name; quality of service QoS; services related to the target task; coordinates of the services related to the target task; and execution timing of the services related to the target task.

[0120] In some other embodiments, the subtask information of the subtask may specifically include at least one of the following information: the task name of the target task; the QoS of the subtask; the service related to the subtask; and the execution sequence of the service related to the subtask.

[0121] It should be noted that, in the embodiment of the present invention, the business task description can be transmitted between the basic domain and the business domain through a unified syntax definition, that is, when the business network element issues a task (that is, sends the task information of the target task), a standard task syntax can be used to describe the target task. Here, the task syntax can specifically be a set of business policies issued by the business domain, which is a demand for connection, computing power and QoS guarantee put forward to the basic domain. Specifically, the task information of the target task described by the task syntax can include: task name, services involved in the task (there may be multiple), service coordinates, service execution sequence and task QoS. Among them, task QoS can specifically include: computing power requirements for each service, connection relationships between services, latency and bandwidth, etc. It does not include metrics for the business itself. For example, Figure 1 The RAN side adds AI computing power services for UE. The tasks need to include: hardware resources for AI computing power allocation, latency / bandwidth requirements between UE and AI services, but do not include indicators such as the training cycle and accuracy of the AI ​​algorithm itself.

[0122] In the above embodiment, the network device (i.e., the distributed task scheduling concentration point) can provide an interface to the outside world, receive target tasks issued by service network elements such as the communication plane and the computing plane, and decompose the target tasks into different subtasks according to a unified syntax and issue them to the corresponding network function entities; the distributed task scheduling concentration point can also collect the execution status of subtasks from the network function entities and dynamically adjust the allocation of subtasks; if it is impossible to adjust the subtask allocation plan that meets the business requirements, the distributed task scheduling concentration point can return a business failure prompt to the business network element.

[0123] It should be noted that the 5G core network control plane has been service-oriented, and it is expected that 6G will be further expanded to include the core network user plane, RAN, and even the end-to-end service-oriented network architecture of the remote UE. On this basis, the embodiments of the present invention can realize the native integration of multiple factors such as synaesthesia, intelligent computing, and security through the distributed task management mechanism. It supports unified business task intent input grammatical logic, automatic deployment, automatic configuration, and execution according to the grammatical description, and provides a mechanism that changes dynamically with the upper-layer business scenarios, and dynamically feedbacks and automatically adjusts according to the business situation. It can make intelligent decisions based on the business execution situation to adjust resources such as cell switching, spectrum allocation, bandwidth allocation, and business routing, thereby improving the overall network efficiency and performance.

[0124] The task management method of this embodiment supports using the traditional network's QoS Flow-based strategy as a communication subtask, thereby enabling a smooth upgrade of the 5G network, meeting the evolution requirements of the 6G network architecture, and realizing the native integration capabilities of multiple factors such as telepathy, computing, intelligence, and security.

[0125] like Figure 5As shown, a task management method of an embodiment of the present invention is applied to a service network element in a distributed task scheduling network, wherein the distributed task scheduling network includes: the service network element, a network device and at least one network function entity, including:

[0126] Step 501, sending task information of the target task.

[0127] Here, the service network element may specifically be one or more of a communication plane network element, a computing plane network element, a data plane network element, and the like.

[0128] In this embodiment, the service network element can send the task information of the target task, so that after the network device obtains the task information of the target task, it can obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtask without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation.

[0129] In some embodiments, the method further includes: obtaining prompt information sent by the network device, the prompt information being used to prompt that the target task has failed to execute; adjusting the task information according to the prompt information to obtain target task information; and sending the target task information to the network device.

[0130] Here, the adjustment task information may specifically be the adjustment of the QoS demand of the target task, or other items in the adjustment task information. In addition, after receiving the prompt information, the service network element may also decide not to execute the target task.

[0131] In the task management method of this embodiment, the service network element can send the task information of the target task, so that the network device can decompose the target task according to the task information after obtaining the task information of the target task, obtain subtasks, and then assign the subtasks to network function entities suitable for executing the subtasks. In the event of task execution failure, the task information of the target task can be adjusted so that the network device can reallocate the task. In this way, distributed scheduling management of tasks can be implemented without reserving resources in advance on the network function entity, thereby realizing distributed task management and avoiding resource waste due to resource reservation.

[0132] like Figure 3 As shown, a network architecture of an embodiment of the present invention includes:

[0133] Service network elements, network equipment and at least one network function entity;

[0134] Wherein, the service network element is used to: send task information of the target task;

[0135] The network device is used to: obtain the task information, obtain subtask information of at least one subtask corresponding to the target task according to the task information, and determine a first target network function entity corresponding to each subtask from the at least one network function entity, and send the subtask information of the subtask to the first target network function entity corresponding to the subtask, wherein the first target network function entity is a network function entity that can provide a service for executing the subtask;

[0136] The first target network function entity is used to: receive the subtask information, execute the subtask corresponding to the subtask information, and obtain the subtask execution result.

[0137] It should be noted that the business network elements, network devices and network function entities in the network architecture can be specifically referred to the various embodiments of the aforementioned task management method, which can achieve the same technical effects and will not be repeated here.

[0138] The network architecture of this embodiment provides a communication network architecture implementation plan based on distributed task management. The network equipment can decompose the target tasks issued by the business network element to obtain subtasks, and then assign the subtasks to network function entities suitable for executing the subtasks. In this way, distributed scheduling management of tasks can be achieved without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation. This network architecture supports the integration of multiple business functional elements into a unified basic domain framework, which can meet the business needs of native integration of telepathic computing and intelligent security in 6G scenarios, and can also use the communication capabilities of traditional 5G networks as communication subtasks under the new architecture to achieve smooth network upgrades.

[0139] like Figure 6 As shown, a task management device according to an embodiment of the present invention is applied to a network device in a distributed task scheduling network, wherein the distributed task scheduling network includes: a service network element, the network device and at least one network function entity, and the device includes:

[0140] A first acquisition module 610 is used to acquire task information of the target task sent by the service network element;

[0141] A first processing module 620 is used to obtain subtask information of at least one subtask corresponding to the target task according to the task information;

[0142] A second processing module 630 is configured to determine, from the at least one network function entity, a first target network function entity corresponding to each of the subtasks, where the first target network function entity is a network function entity that can provide a service for executing the subtask;

[0143] The first sending module 640 is configured to send the subtask information of the subtask to the first target network function entity corresponding to the subtask.

[0144] In this embodiment, the network device can obtain the task information of the target task sent by the service network element, and then obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtask without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation.

[0145] Optionally, the device further comprises:

[0146] A second acquisition module, used to obtain the subtask execution result sent by the first target network function entity;

[0147] A third processing module is used to determine whether there is a second target network function entity when the subtask execution result indicates that the subtask execution fails, where the second target network function entity is a network function entity other than the first target network function entity that can provide a service for executing the subtask;

[0148] The third sending module is used to send the subtask information of the subtask to the second target network function entity when it is determined that the second target network function entity exists.

[0149] Optionally, the device further comprises:

[0150] The fourth sending module is used to send a prompt message to the service network element when it is determined that the second target network function entity does not exist, and the prompt message is used to prompt that the target task execution fails.

[0151] Optionally, the task information includes at least one of the following:

[0152] Task name;

[0153] Quality of Service (QoS);

[0154] Services related to the stated objectives;

[0155] The coordinates of the service associated with the target task;

[0156] The execution sequence of services related to the target task.

[0157] It should be noted here that the above-mentioned task management device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned task management method embodiment applied to network equipment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0158] like Figure 7 As shown, a task management device according to an embodiment of the present invention is applied to a service network element in a distributed task scheduling network, wherein the distributed task scheduling network includes: the service network element, a network device and at least one network function entity, and the device includes:

[0159] The second sending module 710 is used to send task information of the target task.

[0160] In this embodiment, the service network element can send the task information of the target task, so that after the network device obtains the task information of the target task, it can obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtask without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation.

[0161] Optionally, the device further comprises:

[0162] A third acquisition module is used to acquire prompt information sent by the network device, where the prompt information is used to prompt that the target task fails to execute;

[0163] A fourth processing module, used to adjust the task information according to the prompt information to obtain target task information;

[0164] The fifth sending module is used to send the target task information to the network device.

[0165] It should be noted here that the above-mentioned task management device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned task management method embodiment applied to the service network element, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0166] like Figure 8 As shown, a device 800 of an embodiment of the present invention is a network device in a distributed task scheduling network, and the distributed task scheduling network includes: a service network element, the network device and at least one network function entity, including a processor 810 and a transceiver 820, wherein the transceiver 820 is used to obtain task information of a target task sent by the service network element;

[0167] The processor 810 is configured to obtain subtask information of at least one subtask corresponding to the target task according to the task information;

[0168] The processor 810 is further configured to determine, from the at least one network function entity, a first target network function entity corresponding to each of the subtasks, where the first target network function entity is a network function entity that can provide a service for executing the subtask;

[0169] The transceiver 820 is further configured to send the subtask information of the subtask to the first target network function entity corresponding to the subtask.

[0170] In this embodiment, the network device can obtain the task information of the target task sent by the service network element, and then obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtask without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation.

[0171] Optionally, the transceiver 820 is further configured to obtain a subtask execution result sent by the first target network function entity;

[0172] The processor 810 is further configured to, when the subtask execution result indicates that the subtask execution fails, determine whether there is a second target network function entity, where the second target network function entity is a network function entity other than the first target network function entity that can provide a service for executing the subtask;

[0173] The processor 810 is further configured to send the subtask information of the subtask to the second target network functional entity when it is determined that the second target network functional entity exists.

[0174] Optionally, the processor 810 is further configured to, when determining that the second target network function entity does not exist, send a prompt message to the service network element, wherein the prompt message is used to prompt that the execution of the target task has failed.

[0175] Optionally, the task information includes at least one of the following:

[0176] Task name;

[0177] Quality of Service (QoS);

[0178] Services related to the stated objectives;

[0179] The coordinates of the service associated with the target task;

[0180] The execution sequence of services related to the target task.

[0181] It should be noted here that the above-mentioned device provided by the embodiment of the present invention can implement all the method steps implemented by the above-mentioned task management method embodiment applied to network equipment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0182] A device according to an embodiment of the present invention can be used as follows Figure 8 In the structure shown, the device is a service network element in a distributed task scheduling network, and the distributed task scheduling network includes: the service network element, network equipment and at least one network function entity, and the device includes a processor and a transceiver, wherein the transceiver is used to send task information of the target task.

[0183] In this embodiment, the service network element can send the task information of the target task, so that after the network device obtains the task information of the target task, it can obtain the subtask information of at least one subtask corresponding to the target task according to the task information, and then determine the first target network function entity corresponding to each subtask from at least one network function entity, and send the subtask information of the subtask to the first target network function entity. In this way, the target task can be decomposed into subtasks and sent to the network function entity suitable for executing the subtask without reserving resources in advance on the network function entity, thus realizing distributed task management and avoiding resource waste caused by resource reservation.

[0184] Optionally, the transceiver is further used to obtain prompt information sent by the network device, where the prompt information is used to prompt that the target task fails to be executed;

[0185] The processor is further configured to adjust the task information according to the prompt information to obtain target task information;

[0186] The transceiver is also used to send the target task information to the network device.

[0187] It should be noted here that the above-mentioned device provided by the embodiment of the present invention can implement all the method steps implemented by the above-mentioned task management method embodiment applied to the service network element, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0188] A device according to another embodiment of the present invention, such as Fig. 9 As shown, it includes a transceiver 910, a processor 900, a memory 920, and a program or instruction stored in the memory 920 and executable on the processor 900; when the processor 900 executes the program or instruction, it implements the above-mentioned task management method applied to the network device, or implements the above-mentioned task management method applied to the service network element.

[0189] The transceiver 910 is used to receive and send data under the control of the processor 900.

[0190] Among them, Fig. 9 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 900 and memory represented by memory 920. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 910 may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 900 is responsible for managing the bus architecture and general processing, and the memory 920 may store data used by the processor 900 when performing operations.

[0191] The present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above Figure 2 or Figure 5 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0192] A computer-readable storage medium according to an embodiment of the present invention stores a program or instruction thereon, and when the program or instruction is executed by a processor, the steps in the task management method described above are implemented, and the same technical effect can be achieved. To avoid repetition, it is not described here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0193] It should be further explained that the terminals described in this specification include but are not limited to smart phones, tablet computers, etc., and many of the functional components described are called modules in order to more particularly emphasize the independence of their implementation methods.

[0194] In the embodiment of the present invention, module can be implemented with software so that it can be executed by various types of processors. For example, an executable code module of an identification can include one or more physical or logical blocks of computer instructions, for example, it can be constructed as an object, process or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different positions, and when these instructions are logically combined together, it constitutes a module and realizes the specified purpose of the module.

[0195] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed among different programs, and distributed across a plurality of memory devices. Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form. The operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0196] When a module can be implemented by software, considering the level of existing hardware technology, a person skilled in the art can build a corresponding hardware circuit to implement the corresponding function of the module that can be implemented by software without considering the cost. The hardware circuit includes a conventional very large scale integration (VLSI) circuit or gate array and existing semiconductors such as logic chips, transistors, or other discrete components. The module can also be implemented by a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0197] The above exemplary embodiments are described with reference to the accompanying drawings, and many different forms and embodiments are feasible without departing from the spirit and teachings of the present invention. Therefore, the present invention should not be constructed as a limitation of the exemplary embodiments proposed herein. More specifically, these exemplary embodiments are provided so that the present invention will be perfect and complete, and the scope of the present invention will be conveyed to those who are familiar with the technology. In these figures, the component sizes and relative sizes may be exaggerated for clarity. The terms used here are only based on the purpose of describing specific exemplary embodiments and are not intended to be limiting. As used herein, unless the text clearly indicates otherwise, the singular forms "one", "an" and "the" are intended to include these multiple forms. It will be further understood that the terms "including" and / or "comprising" when used in this specification indicate the presence of the features, integers, steps, operations, components and / or components, but do not exclude the presence or increase of one or more other features, integers, steps, operations, components, components and / or their groups. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0198] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A task management method, applied to a network device in a distributed task scheduling network, the distributed task scheduling network comprising: The service network element, the network device and at least one network function entity, wherein the method comprises: Obtaining task information of the target task sent by the service network element; Obtaining subtask information of at least one subtask corresponding to the target task according to the task information; Determine, from the at least one network function entity, a first target network function entity corresponding to each of the subtasks, where the first target network function entity is a network function entity that can provide a service for executing the subtask; The subtask information of the subtask is sent to the first target network function entity corresponding to the subtask.

2. The method according to claim 1, characterized in that The method further comprises: Obtaining a subtask execution result sent by the first target network function entity; In the case where the subtask execution result indicates that the subtask execution fails, determining whether there is a second target network function entity, where the second target network function entity is a network function entity other than the first target network function entity that can provide a service for executing the subtask; In a case where it is determined that the second target network functional entity exists, the subtask information of the subtask is sent to the second target network functional entity.

3. The method according to claim 2, characterized in that The method further comprises: In the case where it is determined that the second target network function entity does not exist, a prompt message is sent to the service network element, where the prompt message is used to prompt that the execution of the target task has failed.

4. The method according to claim 1, characterized in that The task information includes at least one of the following: Task name; Quality of Service (QoS); Services related to the stated objectives; The coordinates of the service associated with the target task; The execution sequence of services related to the target task.

5. A task management method, applied to a service network element in a distributed task scheduling network, the distributed task scheduling network comprising: The service network element, network equipment and at least one network function entity are characterized by comprising: Send task information of the target task.

6. The method according to claim 5, characterized in that Also includes: Acquire prompt information sent by the network device, where the prompt information is used to prompt that the target task fails to be executed; According to the prompt information, adjust the task information to obtain target task information; The target task information is sent to the network device.

7. A network architecture, characterized in that: include: Service network elements, network equipment and at least one network function entity; Wherein, the service network element is used to: send task information of the target task; The network device is used to: obtain the task information, obtain subtask information of at least one subtask corresponding to the target task according to the task information, and determine a first target network function entity corresponding to each subtask from the at least one network function entity, and send the subtask information of the subtask to the first target network function entity corresponding to the subtask, wherein the first target network function entity is a network function entity that can provide a service for executing the subtask; The first target network function entity is used to: receive the subtask information, execute the subtask corresponding to the subtask information, and obtain the subtask execution result.

8. A task management device, applied to a network device in a distributed task scheduling network, the distributed task scheduling network comprising: The service network element, the network device and at least one network function entity, wherein the device comprises: A first acquisition module, used to acquire task information of the target task sent by the service network element; A first processing module, configured to obtain subtask information of at least one subtask corresponding to the target task according to the task information; A second processing module is used to determine a first target network function entity corresponding to each of the subtasks from the at least one network function entity, where the first target network function entity is a network function entity that can provide a service for executing the subtask; The first sending module is used to send the subtask information of the subtask to the first target network function entity corresponding to the subtask.

9. A task management device, applied to a service network element in a distributed task scheduling network, the distributed task scheduling network comprising: The service network element, network equipment and at least one network function entity are characterized by comprising: The second sending module is used to send task information of the target task.

10. A device, the device being a network device in a distributed task scheduling network, the distributed task scheduling network comprising: The service network element, the network device and at least one network function entity, characterized in that the device comprises: a transceiver and a processor; The transceiver is used to obtain task information of the target task sent by the service network element; The processor is used to obtain subtask information of at least one subtask corresponding to the target task according to the task information; The processor is further configured to determine, from the at least one network function entity, a first target network function entity corresponding to each of the subtasks, where the first target network function entity is a network function entity that can provide a service for executing the subtask; The transceiver is further configured to send subtask information of the subtask to the first target network function entity corresponding to the subtask.

11. A device, the device being a service network element in a distributed task scheduling network, the distributed task scheduling network comprising: The service network element, network equipment and at least one network function entity are characterized in that the equipment includes: a transceiver and a processor; The transceiver is used to send task information of the target task.

12. A device comprising: A transceiver, a processor, a memory, and a program or instruction stored in the memory and executable on the processor; characterized in that when the processor executes the program or instruction, it implements the task management method as described in any one of claims 1 to 4, or implements the task management method as described in any one of claims 5 to 6.

13. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the task management method according to any one of claims 1 to 4, or implement the steps of the task management method according to any one of claims 5 to 6.

14. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or instruction is executed by the processor, the steps of the task management method according to any one of claims 1 to 4 or the steps of the task management method according to any one of claims 5 to 6 are implemented.

Images