Task processing method and apparatus, and related device

Abstract

The present application relates to the technical field of communications and discloses a task processing method and apparatus, and a related device. The task processing method disclosed in embodiments of the present application comprises: a first network element receiving a first message, the first message being used for requesting to establish at least one sub-task of a target task; the first network element establishing the at least one sub-task; wherein the sub-task of the target task comprises: a first sub-task, the first sub-task being a sub-task requested by a terminal; and a second sub-task, the second sub-task being a sub-task requested by a second network element.

Description

Task processing method, device and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410315618.0 filed on March 19, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a task processing method, apparatus and related equipment. Background Art

[0004] Traditional communication systems are connection-oriented. Typical applications involve providing connections between specific terminals or between terminals and application servers. The network architecture provides complete session lifecycle management and Quality of Service (QoS) guarantees. Establishment operations in traditional communication systems are all connection-based, and established connections can only provide services to the requesting party, resulting in limited flexibility. Summary of the Invention

[0005] The embodiments of the present application provide a task processing method, apparatus and related equipment, which can solve the problem that in traditional communication systems, establishment operations are all based on connection establishment, and the established connection can only provide services to the requesting party, resulting in poor flexibility.

[0006] In a first aspect, a task processing method is provided, comprising:

[0007] The first network element receives a first message, where the first message is used to request to establish at least one subtask of the target task;

[0008] The first network element establishes the at least one subtask;

[0009] The subtasks of the target task include:

[0010] A first subtask, where the first subtask is a subtask requested by the terminal;

[0011] The second subtask is a subtask requested by the second network element.

[0012] In a second aspect, a task processing method is provided, comprising:

[0013] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0014] or,

[0015] receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask;

[0016] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0017] The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0018] The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

[0019] A third aspect provides a task processing method, including:

[0020] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0021] receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask;

[0022] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0023] The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask;

[0024] The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

[0025] In a fourth aspect, a task processing device is provided, comprising:

[0026] A first receiving module is configured to receive a first message, wherein the first message is used to request the establishment of at least one subtask of a target task;

[0027] An establishing module, configured to establish the at least one subtask;

[0028] The subtasks of the target task include:

[0029] A first subtask, where the first subtask is a subtask requested by the terminal;

[0030] The second subtask is a subtask requested by the second network element.

[0031] In a fifth aspect, a task processing device is provided, comprising:

[0032] Execution module, used to:

[0033] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0034] or,

[0035] receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask;

[0036] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0037] The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0038] The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

[0039] In a sixth aspect, a task processing device is provided, comprising:

[0040] Execution module, used to:

[0041] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0042] receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask;

[0043] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0044] The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask;

[0045] The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

[0046] In the seventh aspect, a communication device is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0047] In an eighth aspect, a first network element is provided, comprising a processor and a communication interface, wherein the communication interface is configured to:

[0048] receiving a first message, wherein the first message is used to request to establish at least one subtask of a target task;

[0049] The first network element establishes the at least one subtask;

[0050] The subtasks of the target task include:

[0051] A first subtask, where the first subtask is a subtask requested by the terminal;

[0052] The second subtask is a subtask requested by the second network element.

[0053] In a ninth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is configured to:

[0054] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0055] or,

[0056] receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask;

[0057] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0058] The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0059] The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

[0060] In a tenth aspect, a second network element is provided, comprising a processor and a communication interface, wherein the processor is configured to:

[0061] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0062] receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask;

[0063] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0064] The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask;

[0065] The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

[0066] In the eleventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0067] In the twelfth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, or implement the steps of the method described in the second aspect, or implement the steps of the method described in the third aspect.

[0068] In the thirteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0069] In the fourteenth aspect, an information sending and receiving system is provided, including: a first access network device and a core network device, wherein the first access network device can be used to execute the steps of the method described in the first aspect, and the core network device can be used to execute the steps of the method described in the second aspect, or implement the steps of the method described in the third aspect.

[0070] In an embodiment of the present application, a first network element receives a first message requesting the establishment of at least one subtask of a target task; the first network element establishes the at least one subtask; wherein the subtasks of the target task include: a first subtask requested by a terminal; and a second subtask requested by a second network element. In this way, the first network element can establish subtasks for both the terminal and the second network element via the first message, thereby improving the flexibility of service processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0072] FIG2 is a flowchart of a task processing method according to an embodiment of the present application;

[0073] FIG3 is a second flow chart of a task processing method provided in an embodiment of the present application;

[0074] FIG4 is a third flow chart of a task processing method provided in an embodiment of the present application;

[0075] FIG5 is a fourth flow chart of a task processing method provided in an embodiment of the present application;

[0076] FIG6a is a fifth flowchart of a task processing method provided in an embodiment of the present application;

[0077] FIG6 b is a sixth flowchart of a task processing method provided in an embodiment of the present application;

[0078] FIG7 is a seventh flowchart of a task processing method provided in an embodiment of the present application;

[0079] FIG8 is a flowchart of an eighth task processing method provided in an embodiment of the present application;

[0080] FIG9 is a ninth flowchart of a task processing method provided in an embodiment of the present application;

[0081] FIG10 is a flowchart of a task processing method according to an embodiment of the present application;

[0082] FIG11 is a flowchart of a task processing method according to an embodiment of the present application;

[0083] FIG12 is a flowchart of a task processing method according to an embodiment of the present application;

[0084] FIG13 is a flowchart of a task processing method according to an embodiment of the present application;

[0085] FIG14 is a structural diagram of a task processing device according to an embodiment of the present application;

[0086] FIG15 is a second structural diagram of a task processing device provided in an embodiment of the present application;

[0087] FIG16 is a third structural diagram of a task processing device provided in an embodiment of the present application;

[0088] FIG17 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0089] FIG18 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

[0090] FIG19 is a schematic diagram of a structure of a network side device according to an embodiment of the present application;

[0091] FIG20 is a second structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0092] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0093] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0094] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0095] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0096] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0097] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0098] For ease of understanding, some of the contents involved in the embodiments of this application are explained below:

[0099] 1. Protocol Data Unit (PDU) Session

[0100] A PDU session refers to the communication process between a user equipment (UE) and a data network (DN). Once a PDU session is established, a data transmission channel between the UE and the DN is established. Therefore, in related technologies, if a UE wants to transmit data to an application, it must first establish a PDU session. In other words, a PDU session is a communication resource established between the UE and the application in a 5G network.

[0101] The PDU session establishment process is briefly described as follows:

[0102] The UE initiates a PDU session establishment request to the network (sent to the SMF via the AMF). The UE allocates a PDU session ID and reports it to the network. The SMF allocates corresponding transmission resources (communication resources) for the UE's PDU session, including selecting the user plane node UPF and triggering the establishment of the user plane. After the user plane is established, the UE can use the user plane corresponding to the established PDU session for data transmission.

[0103] The PDU session modification process is briefly described as follows:

[0104] The UE initiates a PDU session modification request to the network (sent to the SMF via the AMF), in which the UE carries information such as the PDU session ID, the requested QoS rule, and the requested QoS flow description; the SMF authorizes and modifies the corresponding PDU session based on the UE's request.

[0105] 2. Synaesthesia and computing integration

[0106] Traditional communication systems are connection-oriented. Typical applications involve providing connections between specific terminals or between terminals and application servers. The network architecture provides a complete lifecycle management mechanism for sessions (e.g., the creation, modification, and deletion of end-to-end communication tunnels, anchor migration, and other processes) and QoS guarantees. Its primary purpose is to provide connectivity for data transmission, support user mobility, and guarantee a reliable service experience.

[0107] In terms of resource types, non-cloud-based deployed devices typically use dedicated computing resources, with low demands on both computing and storage resources. Unlike traditional communications services, artificial intelligence (AI) is a data- and computing-intensive service. To enable 6G networks to have native AI capabilities, 6G networks need to introduce new resource dimensions, including heterogeneous computing and storage resources, new computing tasks (such as AI-related computing), and new data types (such as AI computing input and output data), and corresponding management and control mechanisms need to be designed. On the other hand, 6G networks will have more comprehensive perception capabilities, including target detection, positioning (distance and angle), speed measurement, and 3D imaging, and will introduce solutions based on radar echoes. The above-mentioned new network capabilities, such as AI capabilities and perception capabilities, will involve the coordination and deployment of computing power, connections, algorithms, and data resources in multi-node scenarios to jointly achieve a specific goal.

[0108] The existing 5G system can only provide a pipeline for data transmission, which is insufficient to support the 6G network's goal of integrated telecom computing. The impact of this integration on network architecture requires further study. When a second network element (such as an AF) initiates hybrid services such as telecom computing, there is no mature process for establishing and responding to these services.

[0109] The task processing method, apparatus, and related equipment provided by the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0110] 2 is a flowchart of a task processing method provided by an embodiment of the present application. As shown in FIG2 , the task processing method includes the following steps:

[0111] Step 101: A first network element receives a first message, where the first message is used to request the establishment of at least one subtask of a target task.

[0112] Step 102: The first network element establishes the at least one subtask;

[0113] The subtasks of the target task include:

[0114] A first subtask, where the first subtask is a subtask requested by the terminal;

[0115] The second subtask is a subtask requested by the second network element.

[0116] A task can refer to a comprehensive service, or a collection of comprehensive services, including communication, information, interpersonal communication, and computing, provided on-demand by a network system (such as a 6G network system) based on external service requests (including UEs, over-the-top (OTT) services, or AF services). OTT services provide various application services to users via the internet. Task management is the management process of providing communication functions and other additional network system functions (such as positioning, interpersonal communication, and computing) in response to external service requests.

[0117] It should be noted that a task can be composed of subtasks, and a task can also be described as a service, business or event, etc. The subtasks of a task can be described as tasks in a service, business or event. For example, a subtask can be a service or a task in a comprehensive service including communication, information, synaesthesia and computing.

[0118] Optionally, the subtasks in the embodiments of the present application include at least one of the following types: perception subtask (or described as perception task), computing subtask (or described as computing task), artificial intelligence AI subtask (or described as AI task), data subtask (or described as data task), positioning subtask (or described as positioning task), communication subtask (or described as communication task), IP Multimedia System (IMS) subtask (or described as IMS task); for another example, the subtasks may also include but are not limited to computing subtasks, information processing subtasks (or described as information processing tasks), multimedia subtasks (or described as multimedia tasks), immersive subtasks (or described as immersive tasks), communication subtasks, etc. Among them, the computing subtasks include AI computing tasks and non-AI computing tasks; the information processing subtasks include positioning information processing, synaesthesia information processing, etc.; the immersive subtasks include extended reality (XR) tasks, virtual reality (VR) tasks, etc.

[0119] The subtasks can be understood as completing an independent function, with multiple subtasks combined to support the completion of a single task. A task can be a combination of multiple functions or subtasks, such as an automated parking task or an environmental reconstruction task. These tasks require not only computational subtasks but also positioning subtasks, and may also require AI subtasks. Multiple functions are combined to complete a single task.

[0120] It should be noted that when the target task is a single type of task, the target task may include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

[0121] The first network element may receive a first message sent by the terminal or the second network element.

[0122] Among them, the first network element can be a newly added network element, such as a task management (TM) network element, or it can be jointly set up with a network element in the core network (such as AMF, SMF, PCF), that is, the function of the first network element is realized through the network element in the core network; the second network element can be a device outside the communication network, such as an application function (AF).

[0123] It should be noted that the first network element can establish the at least one subtask based on the first message. The first network element can establish the at least one subtask based on the relevant information of the target task carried by the first message or the subtask relevant information of the at least one subtask. For example, the first network element can determine the subtask management function or the subtask execution function based on the filled task template, task description information, task requirement description information, task data network name (Data Network Name, DNN) information, task slicing information, task strategy information or task identifier carried by the first message, request the subtask management function to allocate subtask resources or send subtask configuration-related information to the subtask execution function.

[0124] In the embodiment of the present application, the subtask management function can also be described as a subtask management function or a control function; the subtask execution function can also be described as a subtask function, or a subtask execution node, or a subtask resource node.

[0125] For example, the first message carries a filled task template, task description information, task requirement description information or task policy information, and the first network element can determine the subtask management function or subtask execution function that meets the subtask requirements of the filled task template, task description information, task requirement description information or task policy information.

[0126] For example, the first message carries task data network name DNN information, task slice information or task identifier. The first network element can obtain or store the association between task DNN information, task slice information or task identifier and subtask requirements from other devices. The first network element can determine the subtask management function or subtask execution function that meets the subtask requirements corresponding to the task DNN information, task slice information or task identifier.

[0127] It should be noted that the at least one subtask of the target task established by the first network element may be a partial subtask or all subtasks of the target task, and this embodiment of the present application does not limit this.

[0128] In one embodiment, the first network element can determine the subtask policy information or subtask QoS of the associated target task based on task DNN information, task slice information or task identifier, and the first network element can determine the subtask management function or subtask execution function that meets the subtask policy information or subtask QoS of the target task.

[0129] It should be noted that the filled task template can also be briefly described as a filled task template; the task description information can also be briefly described as a task description; the task requirement description information can also be briefly described as a task requirement description; the task strategy information can also be briefly described as a task strategy; the task slice information can also be briefly described as a task slice; and the DNN information can also be briefly described as DNN.

[0130] In an embodiment of the present application, a first network element receives a first message requesting the establishment of at least one subtask of a target task; the first network element establishes the at least one subtask; wherein the subtasks of the target task include: a first subtask requested by a terminal; and a second subtask requested by a second network element. In this way, the first network element can establish subtasks for both the terminal and the second network element via the first message, thereby improving the flexibility of service processing.

[0131] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0132] the first subtask;

[0133] the second subtask;

[0134] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0135] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0136] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0137] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0138] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0139] Among them, there are subtasks of the same type in the first subtask and the second subtask, which can be understood as overlapping subtasks on the terminal side and the second network element side.

[0140] It should be noted that the first subtask can be understood as a subtask on the terminal side; the second subtask can be understood as a subtask on the second network element side; the third subtask can be understood as an overlapping subtask on the terminal side and the second network element side, and the requirements of the third subtask on the terminal side are different from those of the third subtask on the second network element side. For example, the third subtasks are all communication services, and the requirements of the communication services contracted by the terminal are different from those of the communication services contracted by the second network element. For another example, the first subtask and the second subtask are both perception subtasks, the first subtask is dynamic obstacle detection, and the second subtask is static lane line / building position detection. The fourth subtask can be understood as the first subtask + the third subtask (that is, merging the overlapping subtasks into the terminal side subtasks); the fifth subtask can be understood as the second subtask - the third subtask (that is, removing the subtasks on the second network element side that overlap with the terminal); the sixth subtask can be understood as the first subtask - the third subtask (that is, removing the subtasks on the terminal side that overlap with the second network element); the seventh subtask can be understood as the second subtask + the third subtask (that is, merging the overlapping subtasks into the second network element side subtasks).

[0141] Assume that the first subtask includes a communication subtask and a perception subtask, wherein the perception subtask is dynamic obstacle detection;

[0142] The second subtask includes a computation subtask and a perception subtask, wherein the perception subtask is static lane line / building position detection;

[0143] The third subtask is the perception subtask, which includes dynamic obstacle detection and static lane line / building position detection;

[0144] The fourth subtask is the communication subtask and the perception subtask. The perception subtask includes dynamic obstacle detection and static lane / building position detection (already merged with the third subtask).

[0145] The fifth subtask is the computation subtask (excluding the perception subtask in the second subtask);

[0146] The sixth subtask is the communication subtask (excluding the perception subtask in the first subtask);

[0147] The seventh subtask is the calculation subtask and the perception subtask. The perception subtask includes dynamic obstacle detection and static lane line / building position detection (the third subtask has been merged).

[0148] In one embodiment, the first network element receives at least one first message, where the first message may be used to request the network to allocate network resources for the subtask;

[0149] The first network element sends a sixth message to respond to the subtask request in the first message.

[0150] The subtask in the first message or the sixth message includes at least one of the following:

[0151] Terminal-side subtasks;

[0152] Second network element side subtask;

[0153] Subtasks that overlap between the terminal side and the second network element side;

[0154] Merge subtasks on the terminal side;

[0155] The merging subtask on the second network element side;

[0156] The remaining subtasks on the terminal side;

[0157] The remaining subtasks on the second network element side.

[0158] Optionally, the first message is a message sent by the terminal, and the first message carries: subtask related information of the first subtask; or

[0159] The first message is a message sent by the second network element, and the first message carries: subtask related information of the second subtask.

[0160] Among them, the subtask related information may include: a filled subtask template; subtask description information; subtask requirement description information; subtask quality of experience (QoE) description information; subtask policy information; subtask quality of service QoS description information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identification information of the subtask management function; identification information of the subtask execution function; subtask requirement information; subtask slicing information; or subtask data network name DNN information, etc.

[0161] In addition, the task template can be used to indicate the requirements of the UE, AF or network for the task. The task template may include at least one of the following:

[0162] (1) Task description information: used to indicate the target type of the task, that is, to indicate what kind of task it is. For example, if the task is to perceive the traffic congestion in the target area, the task description information is "traffic congestion"; if the task is to park the vehicle at a suitable location or a specified location, the task description information is "automatic parking"; or, used to identify specific task parameters, including at least one of the following: DNN information, single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI), AF identifier, application (Application, APP) identifier.

[0163] (2) Task QoE description information: used to indicate the level of user experience achieved.

[0164] (3) Task strategy information or task quality information, which is used to indicate the service quality requirements of the task and includes at least one of the following:

[0165] Task feedback time or task delay: used to indicate the time limit from when the UE or AF initiates a task to when it receives a task response;

[0166] Task accuracy: used to indicate the probability of successfully completing a task;

[0167] Comprehensive energy consumption: used to indicate the energy consumption required to complete a task, including the energy consumption of the network or terminal.

[0168] Data density: used to indicate the number of bits transmitted per unit time.

[0169] (4) Task parameters: Parameters used to indicate a specific task, which may include subtask configuration information. For example, if a task includes a perception task and a computing task, the task parameters include the perception task configuration and the computing task configuration.

[0170] a. If the subtask type is a perception subtask, the perception subtask configuration includes at least one of the following:

[0171] Perception measurement mode: This may include at least one of the following modes: UE self-transmitting and self-receiving, other UEs transmitting and the UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, or base station transmitting and base station receiving. "Transmitting" refers to sending measurement signals, and "receiving" refers to receiving measurement signals and performing measurements.

[0172] Sensing services: These services may include at least one of the following: Delay Critical LSS (Large Sensing Range with High Real-Time Requirements); Delay Critical SSS (Large Sensing Range with Low Real-Time Requirements); and Delay Critical SSS (Small Sensing Range with Low Real-Time Requirements). These services may also be represented by numbers, letters, or other character strings.

[0173] Perception purpose: may include one or more applications that require perception services supported by the perception device, such as respiratory monitoring, surrounding traffic environment monitoring, etc.

[0174] Perception measurement signal: indicates a signal supported by the perception device (which can be sent or received, or both) and used for perception measurement. For example, it may include at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), multipath angle of arrival, multipath angle of departure, multipath delay, and Doppler frequency.

[0175] Perceptual measurement accuracy: may include at least one of the following: perceptual resolution and perceptual error.

[0176] Perception resolution: refers to the ability to distinguish multiple perception targets from different dimensions, including distance resolution, velocity resolution, angle resolution, etc.

[0177] Perception range: refers to the effective range of specific perception parameters under the premise of meeting certain perception performance indicators (such as perception accuracy), specifically including perception distance range, perception speed range, perception angle range, etc.

[0178] Perception latency: used to quantitatively describe the real-time requirements of perception services, such as the maximum latency from generating a perception service request to feeding back the perception result.

[0179] Perception update frequency: the reciprocal of the time interval between two adjacent perception results.

[0180] b. If the subtask type is a computing subtask, the computing subtask configuration includes at least one of the following:

[0181] Data processing methods: including at least one of the following: denoising, privacy protection, standardization, and normalization;

[0182] Data processing delay: used to indicate the overall delay between data collection and data calculation;

[0183] Calculation accuracy: used to indicate the accuracy of data collection and the overall accuracy of data calculation;

[0184] Computing power information: includes at least one of the following: computing power size and computing power type.

[0185] c. If the subtask type is an AI subtask, the AI ​​subtask configuration includes at least one of the following:

[0186] Model complexity refers to the computational complexity of the model, such as the number of floating point operations (FLOPs) or multiplications and additions required; model training latency; model inference latency; model identification; model download address; data source information (or data source address); computing power; and calculation type.

[0187] The following is an example of a task template:

[0188] Taking automatic parking as an example, the framework of the automatic parking task template can include general parameters, perception task parameters, and calculation task parameters. The task template is as follows:

[0189] {

[0190] General parameters: task type; task feedback time (10s, 20s...); accuracy (95%, 90%...);...

[0191] Sensing task parameters: Sensing measurement mode (UE sends and receives independently, other UE sends and the UE receives, base station sends and the UE receives, UE sends and the base station receives, base station sends and the base station receives); sensing purpose (surrounding environment monitoring); ...

[0192] Computing task parameters: data processing method (denoising, privacy protection, standardization, normalization, etc.); data processing delay (10s, 20s, etc.);

[0193] }

[0194] The task template here is a framework description (without specific numerical description), which is filled by the UE or AF or translated by the TM in combination with the task policy / QoS description information to obtain a task instance.

[0195] In addition, a task instance may refer to an ongoing task with a corresponding task context. Different network elements may store different task contexts for the same task instance.

[0196] In addition, a task session may refer to the process of communication between a UE and a first network element (such as a TM) and related subtask execution functions. A task session may correspond to one or more subtask sessions (a subtask session refers to the process of communication between the first network element and the subtask execution function). Establishing a task session is to establish a data transmission channel between the UE and the first network element and the related subtask execution function. In other words, a task session is a network resource established between the UE and the first network element and the related subtask execution function in the operator network. A task session may sometimes also be referred to as a task connection or a task bearer.

[0197] In addition, the task session identifier can be used to identify the task session, which is allocated by the UE and sent to the network or allocated by the first network element. The subtask session identifier is used to identify the subtask session. The task session identifier and the subtask identifier have a one-to-one mapping relationship or a one-to-many mapping relationship (one task is a combined task).

[0198] Among them, the slice information may include S-NSSAI.

[0199] In this embodiment, the terminal sends information related to the sub-task on the terminal side, and the first network element establishes the task on the terminal side based on the information related to the sub-task on the terminal side sent by the terminal; or, the second network element sends information related to the sub-task on the second network element side, and the first network element establishes the task on the second network element side based on the information related to the sub-task on the second network element side sent by the second network element.

[0200] Optionally, when the first message is a message sent by the terminal, the method further includes:

[0201] The first network element sends a second message to the second network element, where the second message is used to request subtask related information of a subtask corresponding to the second network element;

[0202] The first network element receives a third message sent by the second network element;

[0203] Wherein, the third message carries: subtask related information of the second subtask; or

[0204] The third message carries at least one of the following: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0205] The third message carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0206] In one implementation, when the subtask requirements of the terminal and the second network element are orthogonal, the third message carries: subtask related information of the second subtask.

[0207] It should be noted that, in the embodiments of the present application, orthogonal subtask requirements refer to the absence of overlap or the absence of subtasks of the same type. The subtask requirements of the terminal and the second network element are orthogonal, that is, the subtasks on the terminal side do not overlap with the subtasks on the second network element side, or the subtasks of the same type do not exist. It should be understood that although the subtask requirements of the terminal and the second network element are orthogonal, the subtask requirements of the terminal may also affect the subtask requirements of the second network element, that is, the subtask requirements of the terminal may also be associated with the subtask requirements of the second network element.

[0208] In one embodiment, when the subtask requirements of the terminal and the second network element overlap, and the second network element completes the merging of the requirements on both ends, the third message carries at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask. The overlapping subtask requirements of the terminal and the second network element may refer to the existence of overlapping subtasks on the terminal side and the second network element side, that is, the same type of subtasks exist in the first subtask and the second subtask.

[0209] In one embodiment, when the subtask requirements of the terminal and the second network element overlap and the second network element does not merge the dual-end requirements, the third message carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0210] In this implementation, when the first message is a message sent by the terminal, the second network element interacts with the first network element about the subtask requirements of the second network element, so that the first network element can establish a subtask for the second network element according to the dynamic subtask requirements of the second network element.

[0211] Optionally, when the first message is a message sent by the second network element, the method further includes:

[0212] The first network element sends a fourth message to the terminal, where the fourth message is used to request subtask related information of a subtask corresponding to the terminal;

[0213] The first network element receives a fifth message sent by the terminal;

[0214] Wherein, the fifth message carries: subtask related information of the first subtask; or

[0215] The fifth message carries at least one of the following: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0216] The fifth message carries: subtask related information of the first subtask and subtask related information of the third subtask.

[0217] In one implementation, when the subtask requirements of the terminal and the second network element are orthogonal, the fifth message carries: subtask related information of the first subtask.

[0218] In one embodiment, when the subtask requirements of the terminal and the second network element overlap and the terminal completes the merging of the dual-end requirements, the fifth message carries at least one of the following: subtask related information of the fourth subtask and subtask related information of the fifth subtask.

[0219] In one embodiment, when the subtask requirements of the terminal and the second network element overlap and the terminal does not merge the requirements of both ends, the fifth message carries: subtask related information of the first subtask and subtask related information of the third subtask.

[0220] In this implementation, when the first message is a message sent by the second network element, the terminal interacts with the first network element about the terminal's subtask requirements, so that the first network element can establish a subtask for the terminal according to the terminal's dynamic subtask requirements.

[0221] Optionally, when there is no subtask of the same type between the first subtask and the second subtask, the second message carries: subtask indication information of the second subtask; or the fourth message carries: subtask indication information of the first subtask;

[0222] or

[0223] In the case where the first subtask and the second subtask contain subtasks of the same type, the second message carries: subtask indication information or the first information of the seventh subtask; or the fourth message carries: subtask indication information or the second information of the fourth subtask;

[0224] The first information includes at least one of the following: subtask related information of the first subtask; subtask related information of the third subtask;

[0225] The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask;

[0226] The subtask instruction information includes at least one of the following:

[0227] Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

[0228] In one embodiment, when the same type of subtasks exist in the first subtask and the second subtask, the second message carries: subtask indication information or first information of the seventh subtask, and the second network element can obtain the second network element side subtask requirement information that the first network element wants to obtain through the subtask indication information of the seventh subtask, and obtain the terminal side subtask requirement through the first information provided by the first network element.

[0229] In one embodiment, when the same type of subtasks exist in the first subtask and the second subtask, the fourth message carries: subtask indication information or second information of the fourth subtask. The terminal can obtain the terminal-side subtask requirement information that the first network element wants to obtain through the subtask indication information of the fourth subtask, and obtain the subtask requirement on the second network element side through the second information provided by the first network element.

[0230] Optionally, when there is no subtask of the same type between the first subtask and the second subtask, if the second subtask is associated with the first subtask, the second message also carries subtask related information of the first subtask; or, the fourth message also carries subtask related information of the second subtask.

[0231] In this embodiment, if the second subtask is associated with the first subtask, the second message also carries subtask-related information of the first subtask, so that the second network element can refer to the subtask-related information of the first subtask to feedback the subtask requirements on the second network element side to the first network element; or, if the second subtask is associated with the first subtask, the fourth message also carries subtask-related information of the second subtask, so that the terminal can refer to the subtask-related information of the second subtask to feedback the subtask requirements on the terminal side to the first network element.

[0232] Optionally, the number of the first message is one, and the first message is a message sent by the terminal, or the first message is a message sent by the second network element;

[0233] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0234] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0235] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0236] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0237] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0238] Among them, the relevant information of the target task may include at least one of the following: the filled template of the target task; the template identifier of the target task; the policy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the policy information of the target task; the task identifier of the target task; the description information of the target task; and the requirement description information of the target task.

[0239] In one implementation, when the subtask requirements of the terminal and the second network element are orthogonal, the first message carries: subtask related information of the first subtask and subtask related information of the second subtask.

[0240] In one embodiment, when the subtask requirements of the terminal and the second network element overlap, and the overlapping subtask requirements of the terminal and the second network element are merged into the requirements on the terminal side, the first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask.

[0241] In one embodiment, when the subtask requirements of the terminal and the second network element overlap, and the overlapping subtask requirements of the terminal and the second network element are merged into the requirements on the second network element side, the first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask.

[0242] In one embodiment, when the subtask requirements of the terminal and the second network element overlap, and the overlapping subtask requirements of the terminal and the second network element are sent separately, the first message carries: subtask related information of the first subtask, subtask related information of the second subtask and subtask related information of the third subtask.

[0243] It should be noted that the first message may be sent by the terminal or the second network element, and the number of the first message is one, that is, relevant information of multiple subtasks is transmitted in the same data packet.

[0244] Optionally, the first network element receives a first message, including: the first network element receives multiple first messages; the multiple first messages are messages sent by the terminal, or the multiple first messages are messages sent by the second network element; the first target message in the multiple first messages carries: subtask related information of the fourth subtask; the second target message in the multiple first messages carries: subtask related information of the fifth subtask; or

[0245] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0246] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0247] In one embodiment, when there is overlap in the subtask requirements of the terminal and the second network element, the overlapping subtasks of the terminal and the second network element can be merged into the subtasks of the terminal or the second network element, and the subtask requirements of the terminal and the second network element can be divided into multiple first messages for sending.

[0248] In one embodiment, when overlapping subtasks are merged into terminal-side subtasks, the first target message among the multiple first messages carries: subtask related information of the fourth subtask; the second target message among the multiple first messages carries: subtask related information of the fifth subtask.

[0249] In one embodiment, when the overlapping subtasks of the terminal and the second network element are merged into the second network element side subtask, the first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask.

[0250] In one embodiment, when the overlapping subtasks of the terminal and the second network element are sent separately, the first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0251] In one embodiment, when the subtask requirements of the terminal and the second network element are orthogonal, the subtask requirements of the terminal and the second network element can be divided into multiple first messages for sending, and the first target message in the multiple first messages carries: subtask related information of the first subtask; the second target message in the multiple first messages carries: subtask related information of the second subtask.

[0252] It should be noted that the first message may be sent by the terminal or the second network element, and the number of the first message may be multiple, that is, relevant information of multiple subtasks is transmitted in different data packets.

[0253] Optionally, the first network element receiving the first message includes: the first network element receiving multiple first messages, where the multiple first messages include a message sent by the terminal and a message sent by the second network element;

[0254] The message sent by the terminal carries: subtask related information of the first subtask; the message sent by the second network element carries subtask related information of the second subtask; or

[0255] The message sent by the terminal carries: subtask related information of the first subtask and subtask related information of subtasks of the same type as the second subtask in the first subtask; the message sent by the second network element carries: subtask related information of the second subtask and subtask related information of subtasks of the same type as the first subtask in the second subtask.

[0256] In one embodiment, when the subtask requirements of the terminal and the second network element are orthogonal, they can send their respective subtask requirements separately, and the message sent by the terminal carries: subtask related information of the first subtask; the message sent by the second network element carries subtask related information of the second subtask.

[0257] In one embodiment, when the subtask requirements of the terminal and the second network element overlap, and the terminal and the second network element respectively send their own subtask requirements, the terminal and the second network element may additionally indicate the overlapping subtask requirements, and the message sent by the terminal carries: subtask related information of the first subtask and subtask related information of the third subtask; the message sent by the second network element carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0258] It should be noted that the name of the message sent by the terminal in the multiple first messages may be the same as or different from the name of the message sent by the second network element, which is not limited in this embodiment.

[0259] Optionally, the subtask related information includes at least one of the following:

[0260] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask quality of task (QoT) information; subtask slicing information; subtask data network name (DNN) information.

[0261] Optionally, the first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following:

[0262] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0263] In one implementation, the target task template may be understood as a requested task template or a filled task template. The second network element may set the task template according to at least one of the following and use the set task template as the target task template:

[0264] The second network element sets the task description information in the task template as the task type of the target task;

[0265] The second network element sets the task QoE in the task template as the QoE of the target task;

[0266] The second network element sets the task strategy information in the task template as the task strategy information of the target task;

[0267] The second network element sets the task quality information in the task template as the task quality information of the target task;

[0268] The second network element sets the task parameters in the task template as the task parameters of the target task.

[0269] Among them, the task description information can be used to indicate the target type of the task, that is, to indicate what kind of task it is. For example, if the task is to perceive the traffic congestion situation in the target area, the task description information is "traffic congestion situation"; if the task is to park the vehicle at a suitable location or a designated location, the task description information is "automatic parking"; or it can be used to identify specific task parameters, including at least one of the following: task DNN, task-associated S-NSSAI, AF identification and APP identification.

[0270] DNN information can be used to characterize the DNN assigned to a task, and slice information can be used to characterize the slice assigned to a task.

[0271] Task strategy information or task quality (QoT) information can be used to indicate the service quality requirements of the task, including at least one of the following: task feedback time or task latency: used to indicate the time limit from when the task consumer or requester (for example, a terminal or a second network element, etc.) initiates a task request to when the task response is received; task accuracy: used to indicate the probability of successful completion of the task or to indicate the degree to which the terminal's expected value or the task provider's promised value is consistent with the actual value; comprehensive energy consumption: used to indicate the energy consumption required to complete the task, including the energy consumption of the network or terminal, and the network includes but is not limited to the core network and the access network; data density: used to indicate the number of bits transmitted per unit time.

[0272] The task identifier can be used to identify the task. The identifier of the subtask management function can be the identifier of the function used to manage the subtask. The identifier of the subtask execution function can be the identifier of the function used to execute the subtask. The subtask policy information is used to indicate the quality of service requirements of the subtask.

[0273] In addition, QoT can be understood or replaced by QoS, or task requirement description information, or task requirement information, or QoS description information.

[0274] Optionally, the method further includes:

[0275] The first network element sends a sixth message;

[0276] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0277] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0278] Optionally, the method further includes:

[0279] The first network element sends a sixth message;

[0280] In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following:

[0281] The number of task requests exceeds the maximum value; the task request is not allowed; the sender of the first message is not authorized.

[0282] The sender of the first message may be a terminal or a second network element.

[0283] It should be noted that the name of the message used to indicate rejection of the request corresponding to the first message and the name of the message used to indicate approval of the request corresponding to the first message may be the same as or different from each other.

[0284] The fact that the sender of the first message is not authorized can indicate that the sender of the first message is illegal. The fact that the sender of the first message is not authorized can be understood as the fact that there is no service level agreement for the target task signed between the first network element and the sender of the first message, or the fact that there is no service level agreement signed between the sender of the first message and the first network element.

[0285] In this embodiment, the first network element sends a sixth message or a sixth message to the sender of the first message, and the sixth message or the sixth message is used to indicate the agreement of the request corresponding to the first message or to indicate the rejection of the request corresponding to the first message, so that the sender of the first message can know the response result of the request corresponding to the first message; in addition, through the content carried by the sixth message or the sixth message, the sender of the first message can know the task establishment status of the target task.

[0286] Optionally, when the sender of the first message is the terminal, the method further includes:

[0287] The first network element sends a seventh message to the second network element;

[0288] The seventh message carries at least one of the following items of the target task:

[0289] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the execution order of subtasks; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0290] The target subtask includes at least one of the following: the second subtask; the seventh subtask; and the fifth subtask.

[0291] Optionally, when the sender of the first message is the second network element, the method further includes:

[0292] The first network element sends a seventh message to the terminal;

[0293] The seventh message carries at least one of the following items of the target task:

[0294] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0295] The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

[0296] In this embodiment, when the sender of the first message is the terminal, the method also includes: the first network element sends a seventh message to the second network element; or, when the sender of the first message is the second network element, the method also includes: the first network element sends the seventh message to the terminal; notifying the terminal of its subtask related information through the first network element, so that the terminal can obtain the relevant information of its subtask; or, notifying the second network element of its subtask related information through the first network element, so that the second network element can obtain the relevant information of its subtask.

[0297] In the embodiment of the present application, the network system may include a first network element, a second network element, a third network element, a fourth network element, a fifth network element, a sixth network element, a seventh network element, an eighth network element, and a ninth network element. The first network element may be used for task management, and the first network element may include: a newly added network element TM, or be co-located with an existing network element (e.g., AMF, SMF, PCF).

[0298] The second network element may include a third-party server whose content or service is built on top of the basic telecommunications service, such as an OTT server; or the second network element may include an application function, such as AF (Application Function).

[0299] The third network element (TNE) can be located between the 6G core network and external third-party application functions (possibly also some internal AFs), responsible for exposing network capabilities and internal network information. All external applications that want to access internal data of the 6G core network must go through the TNE. The TNE provides corresponding security guarantees to ensure the security of external applications accessing the 3GPP network, and provides functions such as external application demand or target customization capability exposure, mobility status event subscription, and AF request distribution. The TNE can include network exposure functions such as NEF.

[0300] The fourth network element can determine the required AI resources, AI units, and data sources based on the AI ​​service category and the internal requirements of the AI ​​service. The fourth network element may include AI service management functions.

[0301] The fifth network element may determine the required sensing resources, sensing units and data sources according to the sensing service category and the internal requirements of the sensing service. The fifth network element may include a sensing management function.

[0302] The sixth network element can be used for computing service resource management, specifically, to allocate, update, and release computing resources on demand; as well as to update and maintain the status of computing resource nodes. The sixth network element may include: computing power control functions, computing power control plane, AI resource management functions, etc.

[0303] The seventh network element can be used for AI model management, model ID allocation, model classification, model acquisition (determining the appropriate model based on internal needs), model storage, and model version management. The seventh network element can include AI model management functions, AI model control functions, AI algorithm control functions, algorithm control functions, or algorithm control planes.

[0304] The eighth network element can be used to perform service processing and implement service policy rules. Specifically, it can perform AI service computing and processing (user plane execution process) according to the command of the sixth network element or the first network element; and update the AI ​​resource status to the sixth network element or the first network element. The eighth network element can include: AI resource nodes, computing power execution nodes, computing power execution functions or computing power execution planes, etc.

[0305] The ninth network element may be used for sensing service processing, including data collection, data processing, etc. The ninth network element may include a sensing execution function.

[0306] In one embodiment, the first network element (such as a TM) is a 3GPP internal network element, configured to implement one or more of the following functions:

[0307] 1. Task Verification: Verify whether a task is a legitimate task requested by a legitimate UE or AF. Task verification includes at least one of the following: whether the AF allows the task template request, whether the task request comes from a legitimate UE (whether the UE has a task contract), whether the task request comes from a legitimate AF (based on whether there is a task agreement between the TM and the AF), and whether the task exceeds the upper limit of the number of tasks associated with the UE or AF.

[0308] Optionally, if the task request comes from the AF, the task verification function can be implemented by the NEF.

[0309] 2. Task Template Generation: The task template is determined through negotiation with the AF. The task template is a description of a customized task that the network assigns to the UE. It can be thought of as a questionnaire, where the requester "checks" some required or optional parameters to express their requirements for the task. The task template contains at least one of the following:

[0310] Task template identifier, used to identify the task template;

[0311] Task description;

[0312] Description of the task's quality of experience (QoE);

[0313] Task strategy or QoS description;

[0314] Task parameters.

[0315] 3. Task translation or decomposition: Translate or decompose the task request into a task instance, which is an ongoing task. The task instance includes at least one of the following:

[0316] (1) Task description;

[0317] (2) Task type, used to indicate whether the task is a single task, a combined task, or multiple tasks. The single task is any one of communication, perception, computing, and AI. The combined task is any combination of the above tasks.

[0318] (3) Task strategy or QoS;

[0319] (4) Security-related parameters, which are information used to encrypt transmitted signaling or data;

[0320] (5) Subtask type, used to indicate the type of subtask, including at least one of the following: perception, calculation, AI;

[0321] (6) Subtask policy or QoS, used to indicate the quality of service requirements of the subtask.

[0322] If the subtask type is a perception subtask, the subtask policy or QoS is the perception subtask configuration value (including specific configuration information);

[0323] If the subtask type is a computing subtask, the subtask policy or QoS is the computing subtask configuration value (including specific configuration information);

[0324] If the subtask type is an AI subtask, the subtask policy or QoS is the AI ​​subtask configuration value (including specific configuration information);

[0325] (7) Subtask temporal relationship, including at least one of the following:

[0326] a. Subtask execution order, which indicates the temporal relationship of subtask execution and includes at least one of the following implementation methods:

[0327] TM informs the subsequent subtask execution node of the information of the previous subtask execution node;

[0328] TM serves as the central control node for task execution. The previous subtask execution node informs TM of the previous subtask result, and TM informs the subsequent subtask execution node of the previous subtask result.

[0329] For example, a task includes a perception subtask and a computing subtask. TM determines that the perception subtask is a preceding subtask, then TM informs the computing execution function of the address of the perception execution function. After the computing execution function receives data from the perception execution function, the computing execution function can start executing the computing subtask.

[0330] b. Subtask bearer establishment order, used to indicate the timing relationship of subtask bearer establishment, including at least one of:

[0331] Random establishment;

[0332] concurrent builds;

[0333] Establish by priority.

[0334] The subtask timing relationship may be part of a subtask strategy or QoS.

[0335] Due to differences in scenarios and requirements, task instances can be further categorized as follows: they contain general parameters and specific parameters. General parameters describe the QoS requirements for the complete task and include at least one of the following: task description, task type, task policy or QoS, and security-related parameters. Specific parameters describe the QoS requirements for specific subtasks and include at least one of the following: subtask type, subtask policy or QoS, and subtask execution order.

[0336] It is worth noting that TM can also use any of the following methods to determine the task policy or QoS, subtask policy or QoS:

[0337] Obtained from PCF or policy charging function;

[0338] The task policy or QoS, subtask policy or QoS is determined according to information obtained from the PCF or the policy charging function.

[0339] 4. Allocate a task ID or a task session ID, and optionally, allocate a subtask ID or a subtask session ID;

[0340] 5. Allocate task slices or task DNNs, and optionally, subtask slices or subtask DNNs;

[0341] 6. Select a subtask management function or subtask execution function. The TM selects a subtask management function or subtask execution function that can meet the subtask QoS. Specifically, the TM can query the NRF, UDM, or UDR to determine the appropriate subtask management function or subtask execution function, or the TM can determine the appropriate subtask management function or subtask execution function based on stored or maintained information (such as whether the task is supported, computing power, etc.).

[0342] In this embodiment, the first network element is a TM and the second network element is an AF. This describes only the case of adding a new TM network element. However, this does not limit the enhancement of existing network elements (e.g., AMF, SMF, PCF, NEF) to implement TM functions. For example, the PCF and TM are not limited to being co-located. In this case, the AF initiates a task request to the PCF, and the PCF is responsible for all or part of the TM functions.

[0343] In the embodiment of the present application, only the case of direct interaction between the second network element and the first network element is described, but it is not limited to whether there is a transit node, for example, it is not limited to the existence of NEF or other control nodes. In this case, the messages between the second network element and the first network element can be transmitted through NEF or other control nodes.

[0344] In the embodiment of the present application, only the transmission process of the control signaling is described, and the specific transmission resources used by the control signaling are not limited. For example, the control information can be transmitted through one or more of the following: task-related radio resource control (RRC) (which can also be subtask-related radio resource control RRC), task-related non-access stratum (NAS) signaling (which can also be subtask-related non-access stratum NAS signaling), or task-related radio signaling bearer (SRB) (which can also be subtask-related radio signaling bearer SRB).

[0345] The embodiments of the present application do not limit whether the TM responsible for routing and the TM responsible for task management are the same functional node or different functional nodes. The embodiments of the present application do not limit the data transmission method between the AF and the TM, and the TM and the subtask function. The data between the AF and the TM, and the TM and the subtask function can be transmitted through one or more of the following: the task data protocol data unit of the Packet Data Convergence Protocol (PDCP) (can also be the subtask PDCP), the task data protocol data unit of the Service Data Adaptation Protocol (SDAP) (can also be the subtask SDAP), the task data radio bearer (DRB) (can also be the subtask DRB), or the task quality of service QoS flow (can also be the subtask QoT flow), the Session Initiation Protocol (SIP), the Hypertext Transfer Protocol (HTTP), and the Transport Layer Security (TLS) protocol.

[0346] Referring to FIG3 , FIG3 is a flowchart of a task processing method provided in an embodiment of the present application, which is executed by a terminal. As shown in FIG3 , the task processing method includes the following steps:

[0347] Step 201: A terminal sends a first message to a first network element, where the first message is used to request the establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, which is a subtask requested by the terminal; and a second subtask, which is a subtask requested by a second network element.

[0348] or,

[0349] receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask;

[0350] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0351] The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0352] The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

[0353] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0354] the first subtask;

[0355] the second subtask;

[0356] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0357] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0358] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0359] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0360] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0361] Optionally, when there is no subtask of the same type between the first subtask and the second subtask, the fourth message carries: subtask indication information of the first subtask; or

[0362] In the case that the first subtask and the second subtask have subtasks of the same type, the fourth message carries: subtask indication information or second information of the fourth subtask;

[0363] The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask;

[0364] The subtask instruction information includes at least one of the following:

[0365] Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

[0366] Optionally, the number of the first message is one;

[0367] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0368] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0369] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0370] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0371] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0372] Optionally, the sending the first message to the first network element includes sending multiple first messages to the first network element;

[0373] The first target message among the multiple first messages carries: subtask related information of the fourth subtask; the second target message among the multiple first messages carries: subtask related information of the fifth subtask; or

[0374] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0375] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0376] Optionally, the subtask related information includes at least one of the following:

[0377] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

[0378] Optionally, the first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following:

[0379] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0380] Optionally, the method further includes:

[0381] The terminal receives a sixth message sent by the first network element;

[0382] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0383] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0384] Optionally, the method further includes:

[0385] The terminal receives a sixth message sent by the first network element;

[0386] In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following:

[0387] The number of task requests exceeds the maximum value; the task request is not allowed; the terminal is not authorized.

[0388] Optionally, after receiving the fourth message sent by the first network element, the method further includes:

[0389] The terminal receives a seventh message sent by the first network element;

[0390] The seventh message carries at least one of the following items of the target task:

[0391] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0392] The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

[0393] It should be noted that this embodiment is an implementation of the terminal corresponding to the embodiment shown in FIG2 . For its specific implementation, please refer to the relevant description of the embodiment shown in FIG2 . To avoid repeated description, this embodiment will not be described again.

[0394] Referring to FIG. 4 , FIG. 4 is a flowchart of a task processing method provided in an embodiment of the present application, which is executed by the second network element. As shown in FIG. 4 , the task processing method includes the following steps:

[0395] Step 301: A second network element sends a first message to a first network element, where the first message is used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, which is a subtask requested by a terminal; and a second subtask, which is a subtask requested by the second network element.

[0396] receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask;

[0397] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0398] The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask;

[0399] The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

[0400] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0401] the first subtask;

[0402] the second subtask;

[0403] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0404] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0405] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0406] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0407] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0408] Optionally, in the case that there is no subtask of the same type between the first subtask and the second subtask, the second message carries: subtask indication information of the second subtask; or

[0409] In the case that the first subtask and the second subtask have subtasks of the same type, the second message carries: subtask indication information or first information of the seventh subtask;

[0410] The first information includes at least one of the following: subtask related information of the first subtask; subtask related information of the third subtask;

[0411] The subtask instruction information includes at least one of the following:

[0412] Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

[0413] Optionally, the number of the first message is one;

[0414] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0415] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0416] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0417] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0418] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0419] Optionally, the sending the first message to the first network element includes sending multiple first messages to the first network element;

[0420] The first target message among the multiple first messages carries: subtask related information of the fourth subtask; the second target message among the multiple first messages carries: subtask related information of the fifth subtask; or

[0421] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0422] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0423] Optionally, the subtask related information includes at least one of the following:

[0424] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

[0425] Optionally, the first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following:

[0426] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0427] Optionally, the method further includes:

[0428] The second network element receives a sixth message sent by the first network element;

[0429] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0430] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0431] Optionally, the method further includes:

[0432] The second network element receives a sixth message sent by the first network element;

[0433] In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following:

[0434] The number of task requests exceeds the maximum value; the task request is not allowed; the second network element is not authorized.

[0435] Optionally, after receiving the second message sent by the first network element, the method further includes:

[0436] The second network element receives a seventh message sent by the first network element;

[0437] The seventh message carries at least one of the following items of the target task:

[0438] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the execution order of subtasks; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0439] The target subtask includes at least one of the following: the second subtask; the seventh subtask; and the fifth subtask.

[0440] It should be noted that this embodiment is an implementation method of the second network element corresponding to the embodiment shown in Figure 2. Its specific implementation method can refer to the relevant description of the embodiment shown in Figure 2. To avoid repetition, this embodiment will not be repeated.

[0441] The embodiment of the present application establishes tasks by merging subtask requirements within a network system (such as 6G) or outside a network system; and can solve the problem of how to send overlapping requirements.

[0442] The task processing method of the embodiment of the present application is described below through several specific embodiments.

[0443] In the following embodiments, description is made by taking the case where the first network element is a TM and the second network element is an AF as an example.

[0444] Example 1:

[0445] As shown in Figure 5, the task processing method includes the following steps:

[0446] Step (1): The TM receives a first message, where the first message is used to request the network to allocate network resources for the task.

[0447] The first message includes at least one of the following:

[0448] Filled task template; task description (e.g., "traffic congestion", "environment reconstruction"); task requirement description; task QoE description (agent UE forwarding); DNN and S-NSSAI information; task policy or QoS description; task identifier or task session identifier.

[0449] Optionally, the first message may be at least one of the following: a task establishment request message, a task resource request message, a service establishment request message, or a business establishment request message.

[0450] The sender of the first message may include a UE or an AF.

[0451] The sending method of the first message includes method 1-1, method 1-2 or method 1-3.

[0452] Method 1-1:

[0453] As shown in FIG6a , the UE sends the subtask related information on the UE side (such as in mode 1-1a ); as shown in FIG6b , the AF sends the subtask related information on the AF side (such as in mode 1-1b ).

[0454] Mode 1-1a: The UE sends a first message to the TM, which carries information related to the subtask on the UE side;

[0455] In one embodiment, the first message includes at least one of the following:

[0456] Filled in first subtask template; first subtask description (for example, "traffic congestion situation", "environment reconstruction"); first subtask requirement description; first subtask QoE description; task template identifier; task policy identifier; DNN or S-NSSAI information; first subtask policy or QoS description; first subtask identifier or first subtask session identifier.

[0457] In one implementation, the first message carries a task template identifier or task policy number. Based on the task template identifier or task policy identifier, the TM determines whether to negotiate the subtask with the AF. For example, a single bit indicating whether negotiation with the AF is required can help the TM determine whether to inquire with the AF about subtask requirements and which AF to inquire with. Task templates include those that require negotiation between the TM and AF, as well as those that do not.

[0458] It should be noted that the first message may be forwarded to the TM by another network element, such as at least one of the following: an AMF, an SMF, or a control network element. The control network element has at least one of the following functions: mobility management, connection management, and session management. If the TM and SMF are co-located, the first message may be a PDU session establishment request message.

[0459] Mode 1-1b: The AF sends a first message to the TM, which carries information related to the subtask on the AF side;

[0460] In one embodiment, the first message includes at least one of the following:

[0461] Filled second subtask template; second subtask description (e.g., "traffic congestion", "environment reconstruction"); second subtask requirement description; task template identifier; task strategy identifier; DNN or S-NSSAI information; second subtask strategy; second subtask identifier.

[0462] It should be noted that: the first message can be forwarded to the TM by a third network element. The third network element is a network element located between the 6G core network and the external third-party application function body (possibly also some internal AF), which is responsible for opening network capabilities and internal network information; all external applications that want to access the internal data of the 6G core network need to go through the third network element. The third network element provides corresponding security guarantees to ensure the security of external applications to the 3gpp network, and provides functions such as external application demand or target customization capability opening, mobility status event subscription, AF request distribution, etc. The third network element is a network opening function, such as NEF.

[0463] In one implementation, the first message carries a task template identifier or a task policy number. Based on the task template identifier or task policy identifier, the TM determines whether to negotiate a subtask with the UE. For example, a single bit indicating whether negotiation with the UE is required can help the TM determine whether to inquire about subtask requirements from the UE and which UE to inquire about. Task templates include those that require negotiation between the TM and the UE, as well as those that do not.

[0464] Method 1-2:

[0465] The UE or AF sends a first message to the TM, where the first message carries subtask related information on the UE side and subtask related information on the AF side. For example:

[0466] As shown in Figure 7, the UE sends subtask related information on the UE side and subtask related information on the AF side (such as method 1-2a); or, as shown in Figure 8, the AF sends subtask related information on the AF side and subtask related information on the UE side (such as method 1-2b).

[0467] Method 1-2a: The UE sends a first message to the TM.

[0468] Method 1-2a-1: Subtask requirements are merged into a task requirement. Outside the 6G network, the UE instructs the UE and AF on how to charge through the task template ID.

[0469] At this time, the first message includes at least one of the following:

[0470] Filled task template; task description (e.g., “traffic congestion”, “environment reconstruction”); task requirement description; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0471] Method 1-2a-2: The UE initiates a task request, multiple subtasks are transmitted in one packet, and the subtasks are merged into a task within the 6G network.

[0472] Method 1-2a-2-1:

[0473] In the case where the subtask requirements of the UE and the AF are orthogonal, the first message includes at least one of the following:

[0474] Filled in first subtask template; first subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier; filled in second subtask template; second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0475] Method 1-2a-2-2:

[0476] In the case of overlapping UE and AF requirements, the overlapping tasks are merged outside the 6G network.

[0477] Method 1-2a-2-2a:

[0478] In the case of merging overlapping subtask requirements of the UE and the AF into requirements on the UE side, the first message includes at least one of the following:

[0479] Filled-in fourth subtask template; fourth subtask description; fourth subtask requirement description; fourth subtask template identifier; fourth subtask strategy; fourth subtask strategy identifier; fourth subtask identifier; filled-in fifth subtask template; fifth subtask description; fifth subtask requirement description; fifth subtask template identifier; fifth subtask strategy; fifth subtask strategy identifier; fifth subtask identifier; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0480] Method 1-2a-2-2b:

[0481] In the case of merging overlapping subtask requirements of the UE and the AF into requirements on the AF side, the first message includes at least one of the following:

[0482] The filled-in seventh subtask template; the seventh subtask description; the seventh subtask requirement description; the seventh subtask template identifier; the seventh subtask strategy; the seventh subtask strategy identifier; the seventh subtask identifier; the filled-in sixth subtask template; the sixth subtask description; the sixth subtask requirement description; the sixth subtask template identifier; the sixth subtask strategy; the sixth subtask strategy identifier; the sixth subtask identifier; the task template identifier; the task strategy identifier; the DNN or S-NSSAI information; the task strategy; the task identifier.

[0483] Method 1-2a-2-3:

[0484] In the case where the overlapping subtask requirements of the UE and the AF are sent separately, the first message includes at least one of the following:

[0485] The filled first subtask template; the first subtask description; the first subtask requirement description; the first subtask template identifier; the first subtask strategy; the first subtask policy identifier; the first subtask identifier; the filled second subtask template; the second subtask description; the second subtask requirement description; the second subtask template identifier; the second subtask strategy; the second subtask policy identifier; the second subtask identifier; the filled third subtask template; the third subtask description; the third subtask requirement description; the third subtask template identifier; the third subtask strategy; the third subtask policy identifier; the third subtask identifier; the task template identifier; the task strategy identifier; the DNN or S-NSSAI information; the task strategy; the task identifier.

[0486] Method 1-2a-3:

[0487] The UE initiates a multi-subtask request, and multiple subtasks can be transmitted in different data packets. The 6G network can process based on the subtasks without merging them into tasks.

[0488] Method 1-2a-3-1:

[0489] In the case where the subtask requirements of the UE and the AF are orthogonal, the subtask requirements of the UE and the AF may be divided into multiple first messages for transmission.

[0490] The first message includes at least one of the following:

[0491] Filled first subtask template; first subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier; DNN or S-NSSAI information.

[0492] Or the first message includes at least one of the following:

[0493] Filled second subtask template; second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier; DNN or S-NSSAI information.

[0494] Method 1-2a-3-2:

[0495] In the case where the subtask requirements of the UE and the AF overlap, the overlapping subtasks of the UE and the AF may be merged into the subtasks of the UE or the AF, and the requirements of the UE and the AF may be divided into multiple first messages for transmission.

[0496] Method 1-2a-3-2a:

[0497] In the case of merging overlapping subtasks into a UE-side subtask, the first message includes at least one of the following:

[0498] Filled fourth subtask template; fourth subtask description; fourth subtask requirement description; fourth subtask template identifier; fourth subtask strategy; fourth subtask strategy identifier; fourth subtask identifier; DNN or S-NSSAI information.

[0499] Or the first message includes at least one of the following:

[0500] Filled fifth subtask template; fifth subtask description; fifth subtask requirement description; fifth subtask template identifier; fifth subtask strategy; fifth subtask strategy identifier; fifth subtask identifier; DNN or S-NSSAI information.

[0501] Method 1-2a-3-2b:

[0502] In the case of merging overlapping subtasks of the UE and the AF into the AF-side subtask, the first message includes at least one of the following:

[0503] Filled seventh subtask template; seventh subtask description; seventh subtask requirement description; seventh subtask template identifier; seventh subtask strategy; seventh subtask strategy identifier; seventh subtask identifier; DNN or S-NSSAI information.

[0504] Or the first message includes at least one of the following:

[0505] Filled sixth subtask template; sixth subtask description; sixth subtask requirement description; sixth subtask template identifier; sixth subtask strategy; sixth subtask strategy identifier; sixth subtask identifier; DNN or S-NSSAI information.

[0506] Method 1-2a-3-3:

[0507] In the case where overlapping subtasks of the UE and the AF are sent separately, the first message includes at least one of the following:

[0508] Filled-in first subtask template; first subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier; filled-in third subtask template; third subtask description; third subtask requirement description; third subtask template identifier; third subtask strategy; third subtask strategy identifier; third subtask identifier; DNN or S-NSSAI information.

[0509] Or the first message includes at least one of the following:

[0510] Filled second subtask template; second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier; filled third subtask template; third subtask description; third subtask requirement description; third subtask template identifier; third subtask strategy; third subtask strategy identifier; third subtask identifier; DNN or S-NSSAI information.

[0511] Mode 1-2b: AF sends the first message to TM.

[0512] As shown in FIG8 , the content included in the first message is the same as that in Mode 1-2a-1, Mode 1-2a-2, and Mode 1-2a-3 in Mode 1-2a.

[0513] Mode 1-3: As shown in FIG9 , the UE and the AF respectively send a first message to the TM.

[0514] The more reasonable usage scenario of this method is that the UE and AF have not negotiated in advance, so they send orthogonal subtasks, or send non-orthogonal but uncombined subtasks.

[0515] Method 1-3-1:

[0516] In the case where the subtask requirements of the UE and the AF are orthogonal, the respective subtask requirements may be sent separately, and the first message sent by the UE includes at least one of the following:

[0517] Filled first subtask template; first subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0518] The first message sent by the AF includes at least one of the following:

[0519] Filled second subtask template; second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0520] Method 1-3-2:

[0521] In the case where the subtask requirements of the UE and the AF overlap, and the UE and the AF send their own subtask requirements respectively, the UE and the AF may additionally indicate the overlapping subtask requirements.

[0522] At this time, the first message sent by the UE includes at least one of the following:

[0523] Filled in first subtask template; first subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier; filled in third subtask template; third subtask description; third subtask requirement description; third subtask template identifier; third subtask strategy; third subtask strategy identifier; third subtask identifier; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0524] The first message sent by the AF includes at least one of the following:

[0525] Filled second subtask template; second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier; filled third subtask template; third subtask description; third subtask requirement description; third subtask template identifier; third subtask strategy; third subtask strategy identifier; third subtask identifier; task template identifier; task strategy identifier; DNN or S-NSSAI information; task strategy; task identifier.

[0526] Step (2): TM performs the first target operation.

[0527] The TM performs a first target operation, including at least one of the following:

[0528] a. The TM verifies whether the task is a reasonable task requested by a legitimate UE or AF. Specifically, if the UE or AF has signed a contract for the task, the TM determines that the task request is legitimate; if the UE or AF does not have a contract for the task, the TM determines that the task request is invalid. The TM may directly reject the task request and directly execute step (7).

[0529] b. The TM translates or decomposes the task request into task instances.

[0530] The subtasks of the task include at least one of the following: a perception subtask, a computing subtask, an AI subtask, and a communication subtask.

[0531] Specifically, if the task request includes a populated task template, the TM maps the task template to the task instance; if the task request does not include a populated task template, the TM generates a task instance for the task according to at least one of the following:

[0532] a first message received;

[0533] TM local configuration or local policy or operator policy;

[0534] The TM stores or maintains a task context associated with the target task. For example, if the TM has generated a task instance for a similar task that can meet the service requirements of the task requested by the UE, the TM can directly use the task instance.

[0535] A task instance associated with a target task stored or maintained in a UDM or UDR;

[0536] The intelligent module within TM can generate corresponding task instances based on the task description. This intelligent function is trained based on a large amount of input and output data (task description-task instance) and achieves appropriate accuracy, which can be used to generate task instances.

[0537] Step (3): Dynamic demand interaction (optional step).

[0538] Case 1: If step (1) adopts method 1-1a, then step (3) adopts method 3-1a;

[0539] Case 2: If step (1) adopts method 1-1b, then step (3) adopts method 3-1b;

[0540] Case 3: If step (1) adopts method 1-2 or 1-3, there is no step (3).

[0541] Method 3-1a: Dynamic interaction between TM and AF.

[0542] Step (31) TM sends a second message to AF to request subtask requirement information from AF.

[0543] The TM can determine the AF for negotiation by at least one of the following:

[0544] Based on the task template identification or policy identification of step (1);

[0545] The AF is determined based on the AF identifier obtained during the task negotiation process. As shown in FIG6a , the TM sends the second message to the AF in the following ways:

[0546] Method 3-1a-31-1:

[0547] In a case where the subtask requirements of the UE and the AF are orthogonal and the dynamic requirement of the AF is unrelated to the first subtask requirement, the second message is used to request the second subtask requirement, including at least one of the following:

[0548] Second subtask description; second subtask requirement description (for example, rendering scale, inference accuracy, inference latency); second subtask identifier; second subtask type.

[0549] Method 3-1a-31-2:

[0550] In a case where the subtask requirements of the UE and the AF are orthogonal, but the dynamic requirement of the AF is related to the first subtask requirement, the second message is used to request the second subtask requirement, including at least one of the following:

[0551] Indication information of the second subtask (for example, second subtask description; second subtask requirement description (for example, rendering scale, inference accuracy, inference latency); second subtask identifier; or second subtask type); filled-in first subtask template; first subtask description; first subtask QoS; first subtask QoE; first subtask requirement description; first subtask template identifier; first subtask policy; first subtask policy identifier; first subtask identifier.

[0552] Method 3-1a-31-3:

[0553] In the case where the subtask requirements of the UE and the AF overlap, the second message is used to request the seventh subtask requirement, including at least one of the following:

[0554] Indicative information of the seventh subtask (e.g., seventh subtask description; seventh subtask requirement description (e.g., rendering scale, inference accuracy, inference latency); seventh subtask identifier; or seventh subtask type); populated first subtask template; first subtask description; first subtask QoS; first subtask QoE; first subtask requirement description; first subtask template identifier; first subtask policy; first subtask policy identifier; first subtask identifier; third subtask description; third subtask requirement description; third subtask template identifier; third subtask policy; third subtask policy identifier; third subtask identifier;

[0555] Step (32): The AF sends a third message to the TM in response to the second message.

[0556] Method 3-1a-32-1:

[0557] In the case where the subtask requirements of the UE and the AF are orthogonal, the third message is used to feedback the second subtask requirement, including at least one of the following:

[0558] Second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier.

[0559] Method 3-1a-32-2:

[0560] In the case where the subtask requirements of the UE and the AF overlap and the AF completes the merging of the requirements of both ends, the third message is used to feedback the seventh subtask requirement, including at least one of the following:

[0561] Seventh subtask description; seventh subtask requirement description; seventh subtask template identifier; seventh subtask policy; seventh subtask policy identifier; seventh subtask identifier; sixth subtask description (optional); sixth subtask requirement description (optional); sixth subtask QoS (optional); sixth subtask QoE (optional); sixth subtask template identifier (optional); sixth subtask policy (optional); sixth subtask policy identifier (optional); sixth subtask identifier (optional).

[0562] Method 3-1a-32-3:

[0563] In the case where the subtask requirements of the UE and the AF overlap and the AF does not merge the requirements of both ends, the third message is used to feedback the second subtask requirement, including at least one of the following:

[0564] Second subtask description; second subtask requirement description; second subtask template identifier; second subtask strategy; second subtask strategy identifier; second subtask identifier; third subtask description; third subtask requirement description; third subtask template identifier; third subtask strategy; third subtask strategy identifier; third subtask identifier.

[0565] Method 3-1b: Dynamic interaction between TM and UE.

[0566] The process is similar to method 3-1a.

[0567] Step (31) The TM sends a fourth message to the UE, requesting the UE for subtask requirement information.

[0568] The TM can determine that the UE is negotiating by at least one of the following:

[0569] Based on the task template identification or policy identification of step (1);

[0570] The UE is determined based on the UE identifier obtained during the task negotiation process. As shown in FIG6b , the TM sends the fourth message to the UE in the following ways:

[0571] Method 3-1b-31-1:

[0572] In a case where the subtask requirements of the AF and the UE are orthogonal and the dynamic requirements of the UE are unrelated to the second task requirements, the fourth message is used to request the first subtask requirements, including at least one of the following:

[0573] First subtask description; first subtask requirement description (for example, rendering scale, inference accuracy, inference latency); first subtask identifier; first subtask type.

[0574] Method 3-1b-31-2:

[0575] In the case where the subtask requirements of the AF and the UE are orthogonal, but the dynamic requirement of the UE is related to the second subtask requirement, the fourth message is used to request the first subtask requirement, including at least one of the following:

[0576] Indicative information of the first subtask (for example, first subtask description; first subtask requirement description (for example, rendering scale, inference accuracy, inference latency); first subtask identifier; or first subtask type); filled-in second subtask template; second subtask description; second subtask QoS; second subtask QoE; second subtask requirement description; second subtask template identifier; second subtask policy; second subtask policy identifier; second subtask identifier.

[0577] Method 3-1b-31-3:

[0578] In the case where the subtask requirements of the AF and the UE overlap, the fourth message is used to request the fourth subtask requirement, including at least one of the following:

[0579] Indicative information of the fourth subtask (e.g., fourth subtask description; fourth subtask requirement description (e.g., rendering scale, inference accuracy, inference latency); fourth subtask identifier; or fourth subtask type); populated second subtask template; second subtask description; second subtask QoS; second subtask QoE; second subtask requirement description; second subtask template identifier; second subtask policy; second subtask policy identifier; second subtask identifier; third subtask description; third subtask requirement description; third subtask template identifier; third subtask policy; third subtask policy identifier; third subtask identifier;

[0580] Step (32): The UE sends a fifth message to the TM in response to the fourth message.

[0581] Method 3-1b-32-1:

[0582] In the case where the subtask requirements of the AF and the UE are orthogonal, the fifth message is used to feedback the first subtask requirement, including at least one of the following:

[0583] First subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier.

[0584] Method 3-1b-32-2:

[0585] In the case where the subtask requirements of the AF and the UE overlap and the UE completes the merging of the requirements of both ends, the fifth message is used to feedback the fourth subtask requirement, including at least one of the following:

[0586] Fourth subtask description; fourth subtask requirement description; fourth subtask template identifier; fourth subtask policy; fourth subtask policy identifier; fourth subtask identifier; fifth subtask description (optional); fifth subtask requirement description (optional); fifth subtask QoS (optional); fifth subtask QoE (optional); fifth subtask template identifier (optional); fifth subtask policy (optional); fifth subtask policy identifier (optional); fifth subtask identifier (optional).

[0587] Method 3-1b-32-3:

[0588] In the case where the subtask requirements of the AF and the UE overlap and the UE does not merge the requirements of both ends, the fifth message is used to feedback the first subtask requirement, including at least one of the following:

[0589] First subtask description; first subtask requirement description; first subtask template identifier; first subtask strategy; first subtask strategy identifier; first subtask identifier; third subtask description; third subtask requirement description; third subtask template identifier; third subtask strategy; third subtask strategy identifier; third subtask identifier.

[0590] Step (4): TM performs the second target operation.

[0591] The TM performs a second target operation, including at least one of the following:

[0592] The TM allocates a task identifier or a task session identifier, and optionally allocates a subtask identifier or a subtask session identifier;

[0593] If the first message includes a task identifier or a task session identifier, the TM may use it as a reference.

[0594] The task session is used to exchange task-related information (including signaling and data) between the UE or AF and the TM and related subtask execution functions.

[0595] The TM allocates task slices or task DNNs, and optionally allocates subtask slices and / or subtask DNNs;

[0596] The TM selects a subtask management function that can satisfy the subtask QoS.

[0597] Specifically, the TM may query the NRF, UDM, or UDR to determine the appropriate subtask management function, or the TM may determine the appropriate subtask management function based on stored or maintained subtask capabilities.

[0598] It should be noted that, when step (3) is executed, the second target operation further includes: the TM translates or decomposes at least one subtask request obtained through dynamic interaction into a task instance.

[0599] Step (5): Execute the third operation: determine subtask configuration, select subtask execution nodes, and allocate subtask resources.

[0600] Method 1: The TM selects the subtask management function, which performs the third operation.

[0601] Mode 2: TM performs the third operation.

[0602] TM determines the subtask execution nodes and resources.

[0603] Method 5-1: Select the execution node using the subtask management function.

[0604] The TM performs information interaction with the determined subtask management function to determine information of the subtask execution node.

[0605] The subtask management function selects a subtask execution function that meets the requirements according to the subtask strategy or QoS, and the subtask execution function is used to execute the corresponding subtask.

[0606] It should be noted that, as shown in Figure 10, steps 5-1a to 5-1c are performed on demand. If the TM determines the order in which the subtask bearers are established, the TM can interact with the subtask management function according to the order in which the subtask bearers are established. For example, if the task includes a perception task and a computing task, and the TM determines to establish the perception task bearer first, followed by the computing task bearer, the TM will first interact with the perception management function to establish the perception task bearer, and then with the computing management function to establish the computing task bearer.

[0607] 5-1a: If the TM determines that the subtask includes a perception task, the TM sends a perception task request message to the perception management function to request the network to allocate perception resources, including at least one of the following: perception subtask strategy or QoS, perception subtask execution order, and perception subtask identifier.

[0608] The perception management function selects an appropriate perception execution function according to the perception task request information and allocates a subtask identifier or a subtask session identifier, and optionally allocates a subtask slice or a subtask DNN;

[0609] The perception management function sends perception execution function information to the TM, including at least one of the following: perception execution function Internet Protocol (IP) address, identifier (ID) information, fully qualified domain name (FQDN), subtask identifier or subtask session identifier, and allocated subtask slice or subtask DNN;

[0610] 5-1b: If the TM determines that the subtask includes a computing task, the TM sends computing task request information to the computing management function to request the network to allocate computing resources, including at least one of the following: computing subtask policy or QoS, computing subtask execution order, and computing subtask identifier.

[0611] The computing management function selects an appropriate computing execution function according to the computing task request information and allocates a subtask identifier or a subtask session identifier, and optionally allocates a subtask slice or a subtask DNN;

[0612] The computing management function sends computing execution function information to TM, including at least one of the following: computing execution function IP address, ID information, FQDN, computing power information of the computing execution function (computing power size, type), subtask identifier or subtask session identifier, and allocated subtask slices or subtask DNN.

[0613] 5-1c: If the TM determines that the subtask includes an AI task, the TM sends an AI task request message to the AI ​​management function to request the network to allocate AI resources, including at least one of the following: AI subtask policy or QoS, AI subtask execution order, and AI subtask identifier.

[0614] Model complexity refers to the computational complexity of the model, such as the number of floating point operations (FLOPs) or multiplications and additions required; model training latency; model inference latency; model identification; model download address; data source information (data source address); computing power; and calculation type.

[0615] The AI ​​management function selects a suitable AI execution function (or AI resource node) according to the AI ​​task request information, allocates a subtask identifier or a subtask session identifier, and optionally allocates a subtask slice or a subtask DNN.

[0616] The AI ​​management function sends AI execution function information to the TM, including at least one of the following: AI execution function IP address, ID information, FQDN, model acquisition address, model training address, AI resource node address, subtask identifier or subtask session identifier, and allocated subtask slice or subtask DNN.

[0617] It should be noted that the interaction between the TM and the subtask management function is on-demand. The subtask management function can dynamically notify the TM of the collected dynamic information of the subtask execution function, for example, notifying the TM of the remaining computing power information of the calculation execution function.

[0618] Method 5-2: TM selects the execution node.

[0619] The TM selects a subtask execution function that can satisfy the subtask QoS.

[0620] The subtask execution function is responsible for executing at least one of the following functions: a perception subtask, a computation subtask, or an AI subtask. Specifically, the TM may query the NRF, UDM, or UDR to determine the appropriate subtask execution function, or the TM may determine the appropriate subtask execution function based on stored or maintained subtask capabilities. In embodiments of the present application, the subtask execution function may include a terminal device, an access network device, or an independently deployed execution unit.

[0621] As shown in Figure 11, the TM configures the subtask information to the corresponding subtask execution function, and the subtask information includes at least one of the following: subtask identification, subtask policy or QoS, and at least one of the subtask execution order is configured to the corresponding subtask execution function, for example, the perception subtask information is configured to the selected perception execution function, and the computing subtask information is configured to the selected computing execution function.

[0622] 5-2a: If the TM determines that the subtask includes a perception subtask, the TM configures the perception subtask information to the selected perception execution function, which is used to instruct the perception execution function to perform the information required for the perception subtask.

[0623] The perception execution function sends a perception subtask response to the TM, and the perception subtask response can be acceptance or rejection. If the response is rejection, the TM needs to select a perception execution function that can execute the perception subtask again.

[0624] 5-2b: If the TM determines that the subtask includes a computing subtask, the TM configures computing subtask information to the selected computing execution function, which is used to instruct the computing execution function on information required to execute the computing subtask.

[0625] The computation execution function sends a computation subtask response to the TM. The computation subtask response can be an acceptance or rejection. If the response is a rejection, the TM needs to select another computation execution function that can execute the computation subtask. Optionally, the computation subtask response may also include computing power information (computing power size, type) of the computation execution function.

[0626] 5-2c: If the TM determines that the subtask includes an AI subtask, the TM configures the selected AI execution function with AI subtask information, which is used to instruct the AI ​​execution function on information required to execute the AI ​​subtask.

[0627] The AI ​​execution function sends an AI subtask response to the TM. The AI ​​subtask response can be an acceptance or rejection. If the response is a rejection, the TM must select another AI execution function capable of executing the AI ​​subtask. Optionally, the AI ​​subtask response may also include at least one of the following: model acquisition address, AI resource node address, model training address, supported AI frameworks, and supported AI libraries and versions.

[0628] Step (6): Create task context.

[0629] The TM creates a task context according to the received subtask information, which is used to record the relationship between the task requirement information and the task instance.

[0630] Specifically, when receiving a similar task requirement, the TM may determine a task instance that can be used for the task according to the stored task context.

[0631] Optionally, the TM associates the task identifier or task session identifier with the subtask identifier or subtask session identifier.

[0632] The TM associates the task context with the terminal. Specifically, the TM may retrieve the associated task context using the terminal identifier.

[0633] Step (7): Task establishment response.

[0634] Case 1: If step (1) adopts method 1-1a or 1-2a, then step (7) can adopt method 7-1 or method 7-3a.

[0635] Case 2: If step (1) adopts method 1-1b or 1-2b, then step (7) can adopt method 7-2 or method 7-3b.

[0636] Case 3: If step (1) adopts method 3, then step (7) can adopt method 7-3a, 7-3b or 7-3c.

[0637] It should be noted that whoever initiates the request needs to respond to whom, and the other party can be notified optionally. For example, the correspondence between the method used in step (7) and the method used in step (3) is shown in the following table. The method in step (7) and the method in step (3) that are checked are adaptable methods.

[0638] Method 7-1: TM sends an establishment response to the UE.

[0639] In this manner, the TM sends a sixth message to the UE, which is used to respond to the first message sent by the UE and indicate the result of the task or subtask request.

[0640] When the response message to the first message is an acceptance message, the sixth message includes at least one of the following:

[0641] Task identifier or task session identifier; subtask identifier or subtask session identifier; subtask execution function identifier (expression includes but is not limited to ID, IP address, FQDN); subtask management function identifier (expression includes but is not limited to ID, IP address, FQDN); task policy or QoS; subtask policy or QoS; subtask execution order; task slice or task DNN; subtask slice or subtask DNN.

[0642] In the case that the response message to the first message is a rejection message, the sixth message may optionally carry the rejection reason, including but not limited to: the number of task requests exceeds the maximum value; the task request is not allowed; the UE is illegal.

[0643] Method 7-2: TM sends an establishment response to AF.

[0644] In this manner, the TM sends a sixth message to the AF, which is used to respond to the first message sent by the AF and indicate the result of the task or subtask request.

[0645] When the response message to the first message is an acceptance message, the sixth message includes at least one of the following:

[0646] Task ID or task session ID; subtask ID or subtask session ID; subtask execution function ID (expression includes but is not limited to ID, IP address, FQDN); subtask management function ID (expression includes but is not limited to ID, IP address, FQDN); task strategy; subtask strategy; subtask execution order; task slice or task DNN; subtask slice or subtask DNN.

[0647] In the case that the response message to the first message is a rejection message, the sixth message may optionally carry the rejection reason, including but not limited to: the number of task requests exceeds the maximum value; the task request is not allowed; the AF is illegal.

[0648] Method 7-3: TM responds to both UE and AF.

[0649] Method 7-3a: TM responds to the task to the UE and responds to the subtask to the AF.

[0650] In this manner, the TM sends a sixth message to the UE in response to the first message sent by the UE, indicating the result of the task or subtask request. The TM sends a seventh message to the AF in response to the AF side subtask establishment requirement.

[0651] If the response message to the first message is an acceptance message, the sixth message includes at least one of the following:

[0652] Task identifier or task session identifier; subtask identifier or subtask session identifier; subtask execution function identifier (expression includes but is not limited to ID, IP address, FQDN); subtask management function identifier (expression includes but is not limited to ID, IP address, FQDN); task policy or QoS; subtask policy or QoS; subtask execution order; task slice or task DNN; subtask slice or subtask DNN.

[0653] The response message of the first message is a rejection message, and the sixth message may optionally carry a rejection reason, including but not limited to: the number of task requests exceeds the maximum value; the task request is not allowed; the UE is illegal.

[0654] The subtask in the sixth message may be the first subtask, the fourth subtask, or the sixth subtask.

[0655] If the response message to the first message is an acceptance message, the seventh message includes at least one of the following:

[0656] Task identifier or task session identifier; subtask identifier or subtask session identifier; subtask execution function identifier (expression includes but is not limited to ID, IP address, FQDN); subtask management function identifier (expression includes but is not limited to ID, IP address, FQDN); task policy or QoS; subtask policy or QoS; subtask execution order; task slice or task DNN; subtask slice or subtask DNN.

[0657] The response message of the first message is a rejection message, and the seventh message may optionally carry the rejection reason, including but not limited to: the number of task requests exceeds the maximum value; the task request is not allowed; the AF is illegal.

[0658] The subtask in the seventh message may be the second subtask, the seventh subtask, or the fifth subtask.

[0659] Method 7-3b: TM responds to the task to the AF and responds to the subtask to the UE.

[0660] In this manner, the TM sends a sixth message to the AF in response to the first message sent by the AF, indicating the result of the task or subtask request. The TM sends a seventh message to the UE in response to the UE-side subtask establishment request.

[0661] The subtask in the sixth message may be the second subtask, the seventh subtask, or the fifth subtask.

[0662] The subtask in the seventh message may be the first subtask, the fourth subtask, or the sixth subtask.

[0663] Method 7-3c: TM responds to the UE and the AF with a subtask.

[0664] In this manner, the TM sends a seventh message to the UE and the AF, which is used to respond to the first message sent by the UE and the AF and indicate the result of the subtask request.

[0665] The subtask in the seventh message sent to the UE may be the first subtask, the fourth subtask, or the sixth subtask.

[0666] The subtask in the seventh message sent to the AF may be the second subtask, the seventh subtask, or the fifth subtask.

[0667] It should be noted that step (0) may be included before step (1).

[0668] Step (0), policy negotiation or pre-negotiation process.

[0669] Method 0-1: AF and TM negotiate the task template.

[0670] As shown in Figure 12, steps ac are the negotiation process for task templates. The task templates here are customized. Customization here means that the task provider and the operator have signed a task-level agreement, and each task in the agreement has a task template. Steps ac are optional.

[0671] a. The AF sends an eighth message to the TM, requesting the 3GPP network to develop a task template that meets the service requirements for one or more tasks. The eighth message includes at least one of the following:

[0672] Application Service Provider ID (ASPID) information, used to identify an application server. The representation includes but is not limited to ASPID, IP address, FQDN, and AF ID.

[0673] Task description;

[0674] Task template identifier, used to identify a task template, which can be expressed as a task template ID;

[0675] DNN or S-NSSAI, if templates are generated for multiple task requests, multiple different DNNs or S-NSSAIs can be carried;

[0676] The expected task template time window is used to indicate the time when the task template is applicable. It can be a continuous time or a set of time intervals.

[0677] The desired task template applicable area is used to indicate the geographical area (such as cell ID, Tracking Area Identity (TAI), geographic location) or network area (such as Public Land Mobile Network (PLMN) ID, Stand-alone Non-Public Network (SNPN) ID) to which the task template is applicable;

[0678] Subscribe to task template change notifications to notify AF when task templates are upgraded or changed;

[0679] The task QoS description includes at least one of the following: a task QoS reference (such as a standardized 6QI value, a task QoS index value), and individual task QoS parameters.

[0680] Specifically, the eighth message can be a task template negotiation request message or a task template generation request message. The eighth message can be sent to the TM via a third network element (e.g., NEF) or directly from the AF to the TM. A new interaction message, Nnef_taskNegotiation service or Ntm_taskNegotiation service, can be added here for the AF to request 3GPP to formulate or generate a task template.

[0681] b. The TM generates or develops a task template for one or more tasks based on at least one of the following:

[0682] The eighth message received;

[0683] TM local configuration or local policy or operator policy;

[0684] The task template associated with the target task stored or maintained by the TM. For example, if the TM has generated or formulated a similar task template that can meet the business requirements of the task requested by the AF, the TM can directly use the task template;

[0685] A task template associated with a target task stored or maintained in a UDM or UDR;

[0686] The intelligent function within TM can generate or formulate corresponding task templates based on the task description. This intelligent function is trained based on a large amount of input and output data (task description-task template) and achieves appropriate accuracy, which can be used to generate task templates.

[0687] The negotiated task template is a description of a customized task given by the network to the UE. It can be understood as a questionnaire, where the requester "checks" some required or optional parameter requirements to express their needs for the task.

[0688] c. TM sends a response message of the eighth message to AF, which is used to instruct AF to formulate a task template that meets the task requirements for one or more tasks.

[0689] Method 0-2: AF performs task model translation.

[0690] As shown in FIG13 , the AF performs task translation or decomposition to determine the task instance.

[0691] a. The UE and AF interact through the application layer, and the UE obtains the task instance.

[0692] b. The AF sends a task policy or QoS update request to the TM to request the network to update the resources reserved for the task, including at least one of the following: AF ID, task QoS description, and task QoS priority.

[0693] Example 2:

[0694] As shown in FIG9 , similar to the first embodiment, the second embodiment includes the following steps:

[0695] Step (0), policy negotiation or pre-negotiation process: The policy negotiation process of step (0) adopts the method 0-1 in the first embodiment.

[0696] Step (1): The TM receives a first message, wherein the first message is used to request the network to allocate network resources for the task. In step (1), the method 1-1a in the first embodiment is adopted.

[0697] Step (2): TM performs the first target operation.

[0698] Step (3): Dynamic demand interaction. Step (3) adopts the method 3-1a in the first embodiment.

[0699] Step (4): TM executes the second target operation (in this case, the second target operation includes task translation or task decomposition).

[0700] Step (5): performing the third operation;

[0701] Step (6): Create task context;

[0702] Step (7): Task establishment response. Step 7 adopts the method 7-1 or method 7-3a in the first embodiment.

[0703] Example 3:

[0704] As shown in FIG6a and FIG6b, similar to the first embodiment, the third embodiment includes the following steps:

[0705] Step (0), policy negotiation or pre-negotiation process: The policy negotiation process of step (0) adopts the method 0-1 in the first embodiment.

[0706] Step (1): The TM receives a first message, wherein the first message is used to request the network to allocate network resources for the task. In step (1), the method 1-2a in the first embodiment is adopted.

[0707] Step (2): TM performs the first target operation.

[0708] Step (3): This step in Example 1 is not performed.

[0709] Step (4): TM performs the second target operation;

[0710] Step (5): performing the third operation;

[0711] Step (6): Create task context;

[0712] Step (7): Task establishment response. Step 7 adopts the method 7-1 or method 7-3a in the first embodiment.

[0713] Example 4:

[0714] As shown in FIG7 , similar to the first embodiment, the third embodiment includes the following steps:

[0715] Step (0), policy negotiation or pre-negotiation process: The policy negotiation process of step (0) adopts the method 0-1 in the first embodiment.

[0716] Step (1): The TM receives a first message, wherein the first message is used to request the network to allocate network resources for the task. In step (1), the method 1-2b in the first embodiment is adopted.

[0717] Step (2): TM performs the first target operation.

[0718] Step (3): This step in Example 1 is not performed.

[0719] Step (4): TM performs the second target operation;

[0720] Step (5): performing the third operation;

[0721] Step (6): Create task context;

[0722] Step (7): Task establishment response. Step 7 adopts the method 7-2 or method 7-3b in the first embodiment.

[0723] Embodiment 5:

[0724] As shown in FIG8 , similar to the first embodiment, the third embodiment includes the following steps:

[0725] Step (0), policy negotiation or pre-negotiation process: The policy negotiation process of step (0) adopts the method 0-1 in the first embodiment, and there is no offline negotiation process between the UE and the AF.

[0726] Step (1): The TM receives a first message, wherein the first message is used to request the network to allocate network resources for the task. In step (1), the methods 1-3 in the first embodiment are adopted.

[0727] Step (2): TM performs the first target operation.

[0728] Step (3): This step in Example 1 is not performed.

[0729] Step (4): TM performs the second target operation;

[0730] Step (5): performing the third operation;

[0731] Step (6): Create task context;

[0732] Step (7): Task establishment response. Step 7 adopts the method 7-3c in the first embodiment.

[0733] It should be noted that the method 0-2 in step (0) of embodiment 1 can also be combined with embodiments 2 to 5; the method 2 in step (5) can also be combined with embodiments 2 to 5.

[0734] It should be noted that communication, perception, and computing are the three most important basic capabilities for building a freely connected physical and digital world. In related technologies, 6G will natively support communication, perception, and computing services. This means that 6G networks need to introduce new resource dimensions and provide on-demand comprehensive services or a collection of comprehensive services including communication, information, synaesthesia, and computing based on external business requests (including requests from UE or OTT). In related technologies, the network contracts with the UE and AF for different services in a task. For example, in a game task, the network contracts with the UE for communication services and with the AF for computing power services. At this time, the following problems need to be solved: how do the UE and AF initiate task requests to the network; how does the network allocate multiple resources (such as perception, computing resources, and communication) based on the task requests from the UE and AF; and how to ensure coordination between the allocated resources to ensure that the overall service quality requirements corresponding to the task are met.

[0735] In an embodiment of the present application, a service establishment and response process is designed based on TM when the UE and AF / OTT both initiate hybrid service requirements such as telecommuting and computing, so that the network can respond to the telecommuting and computing hybrid service requirements initiated by both the UE and AF, which can solve the above technical problems.

[0736] The task processing method provided in the embodiment of the present application can be executed by a task processing device. In the embodiment of the present application, the task processing device provided in the embodiment of the present application is described by taking the task processing method executed by the task processing device as an example.

[0737] Please refer to FIG. 14 , which is a structural diagram of a task processing device provided in an embodiment of the present application. The first network element includes the task processing device. As shown in FIG. 14 , the task processing device 400 includes:

[0738] A first receiving module 401 is configured to receive a first message, wherein the first message is used to request the establishment of at least one subtask of a target task;

[0739] An establishing module 402, configured to establish the at least one subtask;

[0740] The subtasks of the target task include:

[0741] A first subtask, where the first subtask is a subtask requested by the terminal;

[0742] The second subtask is a subtask requested by the second network element.

[0743] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0744] the first subtask;

[0745] the second subtask;

[0746] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0747] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0748] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0749] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0750] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0751] Optionally, the first message is a message sent by the terminal, and the first message carries: subtask related information of the first subtask; or

[0752] The first message is a message sent by the second network element, and the first message carries: subtask related information of the second subtask.

[0753] Optionally, when the first message is a message sent by the terminal, the apparatus further includes:

[0754] A first sending module is configured to send a second message to a second network element, where the second message is used to request subtask related information of a subtask corresponding to the second network element;

[0755] A second receiving module, configured to receive a third message sent by the second network element;

[0756] Wherein, the third message carries: subtask related information of the second subtask; or

[0757] The third message carries at least one of the following: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0758] The third message carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0759] Optionally, when the first message is a message sent by the second network element, the apparatus further includes:

[0760] A second sending module is used to send a fourth message to the terminal, where the fourth message is used to request subtask related information of the subtask corresponding to the terminal;

[0761] A third receiving module, configured to receive a fifth message sent by the terminal;

[0762] Wherein, the fifth message carries: subtask related information of the first subtask; or

[0763] The fifth message carries at least one of the following: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0764] The fifth message carries: subtask related information of the first subtask and subtask related information of the third subtask.

[0765] Optionally, in the case that there is no subtask of the same type between the first subtask and the second subtask, the second message carries: subtask indication information of the second subtask;

[0766] or

[0767] In the case that the first subtask and the second subtask have subtasks of the same type, the second message carries: subtask indication information or first information of the seventh subtask;

[0768] The first information includes at least one of the following: subtask related information of the first subtask; subtask related information of the third subtask;

[0769] The subtask instruction information includes at least one of the following:

[0770] Subtask description information; subtask QoT; subtask identifier; subtask type information.

[0771] Optionally, in the case that there is no subtask of the same type between the first subtask and the second subtask, the fourth message carries: subtask indication information of the first subtask;

[0772] or

[0773] In the case that the first subtask and the second subtask have subtasks of the same type, the fourth message carries: subtask indication information or second information of the fourth subtask;

[0774] The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask;

[0775] The subtask instruction information includes at least one of the following:

[0776] Subtask description information; subtask QoT; subtask identifier; subtask type information.

[0777] Optionally, when there is no subtask of the same type between the first subtask and the second subtask, if the second subtask is associated with the first subtask, the second message also carries subtask related information of the first subtask; or, the fourth message also carries subtask related information of the second subtask.

[0778] Optionally, the number of the first message is one, and the first message is a message sent by the terminal, or the first message is a message sent by the second network element;

[0779] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0780] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0781] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0782] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0783] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0784] Optionally, the first network element receives a first message, including: the first network element receives multiple first messages; the multiple first messages are messages sent by the terminal, or the multiple first messages are messages sent by the second network element; the first target message in the multiple first messages carries: subtask related information of the fourth subtask; the second target message in the multiple first messages carries: subtask related information of the fifth subtask; or

[0785] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0786] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0787] Optionally, the first network element receiving the first message includes, the first network element receiving multiple first messages, where the multiple first messages include a message sent by the terminal and a message sent by the second network element;

[0788] The message sent by the terminal carries: subtask related information of the first subtask; the message sent by the second network element carries subtask related information of the second subtask; or

[0789] The message sent by the terminal carries: subtask related information of the first subtask and subtask related information of subtasks of the same type as the second subtask in the first subtask; the message sent by the second network element carries: subtask related information of the second subtask and subtask related information of subtasks of the same type as the first subtask in the second subtask.

[0790] Optionally, the subtask related information includes at least one of the following:

[0791] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

[0792] Optionally, the first message carries at least one of the following:

[0793] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0794] Optionally, the device further comprises:

[0795] A third sending module, configured to send a sixth message to the sender of the first message;

[0796] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0797] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0798] Optionally, the device further comprises:

[0799] a fourth sending module, configured to send a sixth message;

[0800] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0801] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0802] Optionally, the device further comprises:

[0803] a fifth sending module, configured to send a sixth message;

[0804] In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following:

[0805] The number of task requests exceeds the maximum value; the task request is not allowed; the sender of the first message is not authorized.

[0806] Optionally, when the sender of the first message is the terminal, the apparatus further includes:

[0807] a fifth sending module, configured to send a seventh message to the second network element;

[0808] The seventh message carries at least one of the following items of the target task:

[0809] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the execution order of subtasks; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0810] The target subtask includes at least one of the following: the second subtask; the seventh subtask; and the fifth subtask.

[0811] Optionally, when the sender of the first message is the second network element, the apparatus further includes:

[0812] a sixth sending module, configured to send a seventh message to the terminal;

[0813] The seventh message carries at least one of the following items of the target task:

[0814] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0815] The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

[0816] The task processing device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0817] The task processing device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0818] Please refer to FIG. 15 , which is a structural diagram of a task processing device provided in an embodiment of the present application. A terminal includes the task processing device. As shown in FIG. 15 , the task processing device 500 includes:

[0819] The execution module 501 is used to:

[0820] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0821] or,

[0822] receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask;

[0823] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0824] The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0825] The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

[0826] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0827] the first subtask;

[0828] the second subtask;

[0829] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0830] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0831] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0832] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0833] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0834] Optionally, when there is no subtask of the same type between the first subtask and the second subtask, the fourth message carries: subtask indication information of the first subtask; or

[0835] In the case that the first subtask and the second subtask have subtasks of the same type, the fourth message carries: subtask indication information or second information of the fourth subtask;

[0836] The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask;

[0837] The subtask instruction information includes at least one of the following:

[0838] Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

[0839] Optionally, the number of the first message is one;

[0840] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0841] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0842] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0843] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0844] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0845] Optionally, the sending the first message to the first network element includes sending multiple first messages to the first network element;

[0846] The first target message among the multiple first messages carries: subtask related information of the fourth subtask; the second target message among the multiple first messages carries: subtask related information of the fifth subtask; or

[0847] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0848] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0849] Optionally, the subtask related information includes at least one of the following:

[0850] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

[0851] Optionally, the first message carries at least one of the following:

[0852] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0853] Optionally, the device further comprises:

[0854] A first receiving module, configured to receive a sixth message sent by the first network element;

[0855] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0856] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0857] Optionally, the device further comprises:

[0858] A second receiving module, configured to receive a seventh message sent by the first network element;

[0859] The seventh message carries at least one of the following items of the target task:

[0860] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0861] The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

[0862] The task processing device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0863] The task processing device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0864] Please refer to FIG. 16 , which is a structural diagram of a task processing device provided in an embodiment of the present application. The second network element includes the task processing device. As shown in FIG. 16 , the task processing device 600 includes:

[0865] The execution module 601 is used to:

[0866] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0867] receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask;

[0868] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0869] The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask;

[0870] The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

[0871] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0872] the first subtask;

[0873] the second subtask;

[0874] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0875] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0876] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0877] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0878] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0879] Optionally, in the case that there is no subtask of the same type between the first subtask and the second subtask, the second message carries: subtask indication information of the second subtask; or

[0880] In the case that the first subtask and the second subtask have subtasks of the same type, the second message carries: subtask indication information or first information of the seventh subtask;

[0881] The first information includes at least one of the following: subtask related information of the first subtask; subtask related information of the third subtask;

[0882] The subtask instruction information includes at least one of the following:

[0883] Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

[0884] Optionally, the number of the first message is one;

[0885] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0886] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0887] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0888] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0889] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0890] Optionally, the sending the first message to the first network element includes sending multiple first messages to the first network element;

[0891] The first target message among the multiple first messages carries: subtask related information of the fourth subtask; the second target message among the multiple first messages carries: subtask related information of the fifth subtask; or

[0892] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0893] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0894] Optionally, the subtask related information includes at least one of the following:

[0895] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

[0896] Optionally, the first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following:

[0897] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0898] Optionally, the device further comprises:

[0899] A first receiving module, configured to receive a sixth message sent by the first network element;

[0900] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0901] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0902] Optionally, the device further comprises:

[0903] A second receiving module, configured to receive a sixth message sent by the first network element;

[0904] In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following:

[0905] The number of task requests exceeds the maximum value; the task request is not allowed; the second network element is not authorized.

[0906] Optionally, the device further comprises:

[0907] A second receiving module, configured to receive a seventh message sent by the first network element;

[0908] The seventh message carries at least one of the following items of the target task:

[0909] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the execution order of subtasks; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0910] The target subtask includes at least one of the following: the second subtask; the seventh subtask; and the fifth subtask.

[0911] The task processing device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0912] The task processing device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0913] Optionally, as shown in FIG17 , an embodiment of the present application further provides a communication device 700, comprising a processor 701 and a memory 702, wherein the memory 702 stores a program or instruction that can be run on the processor 701. For example, when the communication device 700 is a first network element, the program or instruction, when executed by the processor 701, implements the various steps of the embodiment of the task processing method applied to the first network element, and can achieve the same technical effect. To avoid repetition, it is not described again here. When the communication device 700 is a terminal, the program or instruction, when executed by the processor 701, implements the various steps of the embodiment of the task processing method applied to the terminal, and can achieve the same technical effect. To avoid repetition, it is not described again here. When the communication device 700 is a second network element, the program or instruction, when executed by the processor 701, implements the various steps of the embodiment of the task processing method applied to the second network element, and can achieve the same technical effect. To avoid repetition, it is not described again here.

[0914] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiment shown in FIG3 . This terminal embodiment corresponds to the above-mentioned first device or second device side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effects.

[0915] Specifically, Figure 18 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0916] The terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809 and at least some of the components of the processor 810.

[0917] Those skilled in the art will appreciate that the terminal 800 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 810 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 18 does not constitute a limitation of the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be described in detail here.

[0918] It should be understood that in an embodiment of the present application, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042, and the GPU 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 806 may include a display panel 8061, and the display panel 8081 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include two parts: a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0919] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 801 may transmit the data to the processor 810 for processing. Furthermore, the radio frequency unit 801 may send uplink data to the network-side device. Typically, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0920] The memory 809 can be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 809 may include a volatile memory or a non-volatile memory, or the memory 809 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 809 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0921] Processor 810 may include one or more processing units. Optionally, processor 810 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 810.

[0922] The radio frequency unit 801 is used for:

[0923] Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element;

[0924] or,

[0925] receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask;

[0926] The third subtask includes subtasks of the same type as those in the first subtask and the second subtask;

[0927] The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0928] The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

[0929] Optionally, the first message carries subtask related information of at least one of the following subtasks:

[0930] the first subtask;

[0931] the second subtask;

[0932] a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask;

[0933] a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask;

[0934] a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask;

[0935] a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask;

[0936] A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

[0937] Optionally, when there is no subtask of the same type between the first subtask and the second subtask, the fourth message carries: subtask indication information of the first subtask; or

[0938] In the case that the first subtask and the second subtask have subtasks of the same type, the fourth message carries: subtask indication information or second information of the fourth subtask;

[0939] The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask;

[0940] The subtask instruction information includes at least one of the following:

[0941] Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

[0942] Optionally, the number of the first message is one;

[0943] The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or

[0944] The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or

[0945] The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or

[0946] The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or

[0947] The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

[0948] Optionally, the sending the first message to the first network element includes sending multiple first messages to the first network element;

[0949] The first target message among the multiple first messages carries: subtask related information of the fourth subtask; the second target message among the multiple first messages carries: subtask related information of the fifth subtask; or

[0950] The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or

[0951] The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

[0952] Optionally, the subtask related information includes at least one of the following:

[0953] Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

[0954] Optionally, the first message carries at least one of the following:

[0955] Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

[0956] Optionally, the radio frequency unit 801 is configured to: receive a sixth message sent by the first network element;

[0957] Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task:

[0958] Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

[0959] Optionally, the radio frequency unit 801 is configured to: receive a seventh message sent by the first network element;

[0960] The seventh message carries at least one of the following items of the target task:

[0961] Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information;

[0962] The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

[0963] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment Figure 2, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0964] Specifically, the terminal of the embodiment of the present application also includes: instructions or programs stored in the memory 809 and can be run on the processor 810. The processor 810 calls the instructions or programs in the memory 809 to execute the method of execution of each module shown in Figure 15 and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0965] The present application also provides a network-side device, which is a first network element or a second network element and includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 2 or Figure 4. This network-side device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0966] Specifically, an embodiment of the present application further provides a network-side device. The network-side device can be a first network element or a second network element. As shown in Figure 19, the network-side device 900 includes: an antenna 901, a radio frequency device 902, a baseband device 903, a processor 904, and a memory 905. The antenna 901 is connected to the radio frequency device 902. In the uplink direction, the radio frequency device 902 receives information via the antenna 901 and sends the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be transmitted and sends it to the radio frequency device 902. The radio frequency device 902 processes the received information and sends it through the antenna 901.

[0967] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 903 , which includes a baseband processor.

[0968] The baseband device 903 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 19, one of the chips is, for example, a baseband processor, which is connected to the memory 905 through a bus interface to call the program in the memory 905 and execute the network device operations shown in the above method embodiment.

[0969] The network side device may further include a network interface 909, which is, for example, a Common Public Radio Interface (CPRI).

[0970] Specifically, the network side device 900 of the embodiment of the present application also includes: instructions or programs stored in the memory 905 and can be run on the processor 904. The processor 904 calls the instructions or programs in the memory 905 to execute the methods executed by the modules shown in Figure 14 or Figure 16, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0971] Specifically, an embodiment of the present application further provides a network-side device. The network-side device may be a first network element or a second network element. As shown in FIG20 , the network-side device 1000 includes: a processor 1001, a network interface 1002, and a memory 1003. The network interface 1002 may be, for example, a common public radio interface (CPRI).

[0972] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 1003 and can be run on the processor 1001. The processor 1001 calls the instructions or programs in the memory 1003 to execute the method of execution of each module shown in Figure 14 or Figure 16, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0973] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned task processing method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0974] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0975] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned task processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0976] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0977] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned task processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0978] An embodiment of the present application also provides a task processing system, including: a first network element, a terminal and a second network element, wherein the first network element can be used to execute the steps of the task processing method applied to the first network element as described above, the terminal can be used to execute the steps of the task processing method applied to the terminal as described above, and the second network element can be used to execute the steps of the task processing method applied to the second network element as described above.

[0979] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0980] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0981] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A task processing method, comprising: The first network element receives a first message, where the first message is used to request to establish at least one subtask of the target task; The first network element establishes the at least one subtask; The subtasks of the target task include: A first subtask, where the first subtask is a subtask requested by the terminal; The second subtask is a subtask requested by the second network element.

2. The method according to claim 1, wherein The first message carries subtask related information of at least one of the following subtasks: the first subtask; the second subtask; a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask; a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask; a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask; a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask; A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

3. The method according to claim 2, wherein, when the first message is a message sent by the terminal, the method further comprises: The first network element sends a second message to the second network element, where the second message is used to request subtask related information of a subtask corresponding to the second network element; The first network element receives a third message sent by the second network element; Wherein, the third message carries: subtask related information of the second subtask; or The third message carries at least one of the following: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or The third message carries: subtask related information of the second subtask and subtask related information of the third subtask.

4. The method according to claim 2, wherein, when the first message is a message sent by the second network element, the method further comprises: The first network element sends a fourth message to the terminal, where the fourth message is used to request subtask related information of a subtask corresponding to the terminal; The first network element receives a fifth message sent by the terminal; Wherein, the fifth message carries: subtask related information of the first subtask; or The fifth message carries at least one of the following: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or The fifth message carries: subtask related information of the first subtask and subtask related information of the third subtask.

5. The method according to claim 3, wherein: In the case that there is no subtask of the same type between the first subtask and the second subtask, the second message carries: subtask indication information of the second subtask; or In the case that the first subtask and the second subtask have subtasks of the same type, the second message carries: subtask indication information or first information of the seventh subtask; The first information includes at least one of the following: subtask related information of the first subtask; subtask related information of the third subtask; The subtask instruction information includes at least one of the following: Subtask description information; subtask QoT; subtask identifier; subtask type information.

6. The method according to claim 4, wherein: In the case that there is no subtask of the same type between the first subtask and the second subtask, the fourth message carries: subtask indication information of the first subtask; or In the case that the first subtask and the second subtask have subtasks of the same type, the fourth message carries: subtask indication information or second information of the fourth subtask; The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask; The subtask instruction information includes at least one of the following: Subtask description information; subtask QoT; subtask identifier; subtask type information.

7. The method according to claim 2, wherein: The number of the first message is one, and the first message is a message sent by the terminal, or the first message is a message sent by the second network element; The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

8. The method according to claim 2, wherein: The first network element receives a first message, including the first network element receiving multiple first messages; the multiple first messages are messages sent by the terminal, or the multiple first messages are messages sent by the second network element; a first target message in the multiple first messages carries: subtask related information of the fourth subtask; and a second target message in the multiple first messages carries: subtask related information of the fifth subtask; or The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

9. The method according to claim 2, wherein: The first network element receiving a first message includes the first network element receiving a plurality of first messages, where the plurality of first messages include a message sent by the terminal and a message sent by the second network element; The message sent by the terminal carries: subtask related information of the first subtask; The message sent by the second network element carries subtask related information of the second subtask; or The message sent by the terminal carries: subtask related information of the first subtask and subtask related information of subtasks of the same type as the second subtask within the first subtask; The message sent by the second network element carries: subtask related information of the second subtask and subtask related information of subtasks of the same type as the first subtask in the second subtask.

10. The method according to any one of claims 2 to 9, wherein: The subtask related information includes at least one of the following: Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

11. The method according to any one of claims 1 to 10, wherein The first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following: Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

12. The method according to any one of claims 1 to 11, further comprising: The first network element sends a sixth message; Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task: Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

13. The method according to any one of claims 1 to 11, further comprising: The first network element sends a sixth message; In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following: The number of task requests exceeds the maximum value; the task request is not allowed; the sender of the first message is not authorized.

14. The method according to any one of claims 2 to 13, wherein when the sender of the first message is the terminal, the method further comprises: The first network element sends a seventh message to the second network element; The seventh message carries at least one of the following items of the target task: Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the execution order of subtasks; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information; The target subtask includes at least one of the following: the second subtask; the seventh subtask; and the fifth subtask.

15. The method according to any one of claims 2 to 13, wherein when the sender of the first message is the second network element, the method further comprises: The first network element sends a seventh message to the terminal; The seventh message carries at least one of the following items of the target task: Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information; The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

16. A task processing method, comprising: Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element; or, receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask; The third subtask includes subtasks of the same type as those in the first subtask and the second subtask; The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask; The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

17. The method according to claim 16, wherein The first message carries subtask related information of at least one of the following subtasks: the first subtask; the second subtask; a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask; a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask; a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask; a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask; A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

18. The method according to claim 16, wherein In the case that there is no subtask of the same type between the first subtask and the second subtask, the fourth message carries: subtask indication information of the first subtask; or In the case that the first subtask and the second subtask have subtasks of the same type, the fourth message carries: subtask indication information or second information of the fourth subtask; The second information includes at least one of the following: subtask related information of the second subtask; subtask related information of the third subtask; The subtask instruction information includes at least one of the following: Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

19. The method according to claim 17, wherein The number of the first message is one; The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

20. The method according to claim 17, wherein The sending the first message to the first network element includes sending multiple first messages to the first network element; The first target message among the multiple first messages carries: subtask related information of the fourth subtask; The second target message among the multiple first messages carries: subtask related information of the fifth subtask; or The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

21. The method according to any one of claims 16 to 20, wherein: The subtask related information includes at least one of the following: Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

22. The method according to any one of claims 16 to 21, wherein: The first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following: Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

23. The method according to any one of claims 16 to 22, further comprising: The terminal receives a sixth message sent by the first network element; Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task: Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

24. The method according to any one of claims 16 to 23, further comprising: The terminal receives a sixth message sent by the first network element; In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following: The number of task requests exceeds the maximum value; the task request is not allowed; the terminal is not authorized.

25. The method according to any one of claims 16 to 23, wherein: After receiving the fourth message sent by the first network element, the method further includes: The terminal receives a seventh message sent by the first network element; The seventh message carries at least one of the following items of the target task: Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the order of subtask execution; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information; The target subtask includes at least one of the following: the first subtask; the fourth subtask; and the sixth subtask.

26. A task processing method, comprising: Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element; receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask; The third subtask includes subtasks of the same type as those in the first subtask and the second subtask; The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask; The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

27. The method according to claim 26, wherein The first message carries subtask related information of at least one of the following subtasks: the first subtask; the second subtask; a third subtask, the third subtask including subtasks of the same type as those in the first subtask and the second subtask; a fourth subtask, the fourth subtask including subtasks of the second subtask that are of the same type as the first subtask, and the first subtask; a fifth subtask, wherein the fifth subtask is a subtask in the second subtask excluding the subtask of the same type as the first subtask; a sixth subtask, the sixth subtask being a subtask of the first subtask excluding the subtask of the same type as the second subtask; A seventh subtask includes subtasks of the same type as the second subtask in the first subtask, and the second subtask.

28. The method according to claim 26, wherein In the case that there is no subtask of the same type between the first subtask and the second subtask, the second message carries: subtask indication information of the second subtask; or In the case that the first subtask and the second subtask have subtasks of the same type, the second message carries: subtask indication information or first information of the seventh subtask; The first information includes at least one of the following: subtask related information of the first subtask; subtask related information of the third subtask; The subtask instruction information includes at least one of the following: Subtask description information; subtask requirement description information; subtask identifier; subtask type information.

29. The method according to claim 27, wherein The number of the first message is one; The first message carries: relevant information of a target task, where the target task includes the first subtask and the second subtask; or The first message carries: subtask related information of the first subtask and subtask related information of the second subtask; or The first message carries: subtask related information of the fourth subtask and subtask related information of the fifth subtask; or The first message carries: subtask related information of the seventh subtask and subtask related information of the sixth subtask; or The first message carries: subtask related information of the first subtask, subtask related information of the second subtask, and subtask related information of the third subtask.

30. The method of claim 27, wherein: The sending the first message to the first network element includes sending multiple first messages to the first network element; The first target message among the multiple first messages carries: subtask related information of the fourth subtask; The second target message among the multiple first messages carries: subtask related information of the fifth subtask; or The first target message among the multiple first messages carries: subtask related information of the seventh subtask; the second target message among the multiple first messages carries: subtask related information of the sixth subtask; or The first target message among the multiple first messages carries: subtask related information of the first subtask and subtask related information of the third subtask; the second target message among the multiple first messages carries: subtask related information of the second subtask and subtask related information of the third subtask.

31. The method according to any one of claims 26 to 30, wherein: The subtask related information includes at least one of the following: Task template of subtask; subtask description information; subtask quality of experience (QoE) description information; subtask policy information; subtask identifier; subtask session identifier; subtask template identifier; subtask policy identifier; subtask type information; identifier information of subtask management function; identifier information of subtask execution function; subtask QoT; subtask slicing information; subtask data network name (DNN) information.

32. The method according to any one of claims 26 to 31, wherein: The first message carries relevant information of the target task, and the relevant information of the target task includes at least one of the following: Target task template; the identifier of the task template of the target task; the task strategy identifier of the target task; the data network name DNN information of the target task; the slicing information of the target task; the task strategy information of the target task; the task identifier of the target task; the task description information of the target task; the QoT of the target task.

33. The method according to any one of claims 26 to 32, further comprising: The second network element receives a sixth message sent by the first network element; Wherein, when the sixth message is used to indicate approval of the request corresponding to the first message, the sixth message carries at least one of the following items of the target task: Task identifier; task session identifier; subtask identifier; subtask session identifier; identification information of the subtask execution function; identification information of the subtask management function; task strategy information; subtask strategy information; task QoT; subtask QoT; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

34. The method according to any one of claims 26 to 33, further comprising: The second network element receives a sixth message sent by the first network element; In a case where the sixth message is used to indicate rejection of the request corresponding to the first message, the sixth message carries first indication information, where the first indication information is used to indicate at least one of the following: The number of task requests exceeds the maximum value; the task request is not allowed; the second network element is not authorized.

35. The method according to any one of claims 26 to 33, wherein after receiving the second message sent by the first network element, the method further comprises: The second network element receives a seventh message sent by the first network element; The seventh message carries at least one of the following items of the target task: Task identification; task session identification; task strategy information; task QoT; instruction information for indicating the execution order of subtasks; task slicing information; task DNN information; target subtask identification; target subtask session identification; identification information of the target subtask execution function; identification information of the target subtask management function; target subtask strategy information; target subtask QoT; target subtask slicing information; target subtask DNN information; The target subtask includes at least one of the following: the second subtask; the seventh subtask; and the fifth subtask.

36. A task processing device comprising: A first receiving module is configured to receive a first message, wherein the first message is used to request the establishment of at least one subtask of a target task; An establishing module, configured to establish the at least one subtask; The subtasks of the target task include: A first subtask, where the first subtask is a subtask requested by the terminal; The second subtask is a subtask requested by the second network element.

37. A task processing device comprising: Execution module, used to: Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the subtask of the target task includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element; or, receiving a fourth message from the first network element and sending a fifth message to the first network element, the fourth message being used to request subtask-related information of the subtask corresponding to the terminal, the fifth message carrying at least one of the following: subtask-related information of the fourth subtask and subtask-related information of the fifth subtask; or the fifth message carrying: subtask-related information of the first subtask and subtask-related information of the third subtask; The third subtask includes subtasks of the same type as those in the first subtask and the second subtask; The fourth subtask includes subtasks of the second subtask that are of the same type as the first subtask, and the first subtask; The fifth subtask is a subtask in the second subtask except for the subtask of the same type as the first subtask.

38. A task processing device comprising: Execution module, used to: Sending a first message to a first network element, the first message being used to request establishment of at least one subtask of a target task; wherein the at least one subtask includes at least one of the following: a first subtask, the first subtask being a subtask requested by the terminal; and a second subtask, the second subtask being a subtask requested by the second network element; receiving a second message from the first network element, and sending a third message to the first network element, the third message being used to request subtask-related information of the subtask corresponding to the second network element, the third message carrying: subtask-related information of the second subtask; or the third message carrying at least one of the following: subtask-related information of the seventh subtask and subtask-related information of the sixth subtask; or the third message carrying: subtask-related information of the second subtask and subtask-related information of the third subtask; The third subtask includes subtasks of the same type as those in the first subtask and the second subtask; The sixth subtask is a subtask of the first subtask other than a subtask of the same type as the second subtask; The seventh subtask includes subtasks of the first subtask that are of the same type as the second subtask, and the second subtask.

39. A communication device comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the program or instructions implement the steps of the task processing method as described in any one of claims 1 to 15, or implement the steps of the task processing method as described in any one of claims 16 to 25, or implement the steps of the task processing method as described in any one of claims 26 to 35.

40. A chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the task processing method according to any one of claims 1 to 15, or to implement the steps of the task processing method according to any one of claims 16 to 25, or to implement the steps of the task processing method according to any one of claims 26 to 35.

41. A readable storage medium storing a program or instruction, wherein when the program or instruction is executed by a processor, the program or instruction implements the steps of the task processing method according to any one of claims 1 to 15, or implements the steps of the task processing method according to any one of claims 16 to 25, or implements the steps of the task processing method according to any one of claims 26 to 35.

42. A computer program / program product, which, when executed by at least one processor, implements the steps of the task processing method according to any one of claims 1 to 15, or implements the steps of the task processing method according to any one of claims 16 to 25, or implements the steps of the task processing method according to any one of claims 26 to 35.

Images