Task processing method, terminal, and network side device

Abstract

The present application belongs to the technical field of communications, and discloses a task processing method, a terminal, and a network side device. The task processing method of the embodiments of the present application comprises: a terminal sends a first message to a first network element, the first message being used for requesting modification of a target task or a sub-task in a target task; and the terminal receives a first response from the first network element, the first response being used for indicating a modification result of the target task or the sub-task in the target task.

Description

Task processing method, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on March 19, 2024, with application number 202410315455.6 and invention name “Task processing method, terminal and network side device”. The entire contents of the Chinese patent application 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, a terminal, and a network-side device. Background Art

[0004] The existing 5G system can only provide a pipeline for data transmission, which is not enough to support the 6G network to achieve the goal of integrated communication, perception and computing. In order to support the task-centric communication needs in the 6G network, the network needs to allocate resources such as communication, perception, and computing to the terminals.

[0005] However, how to meet the ever-changing task requirements for tasks that have already been created in the communication system is still a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0006] The embodiments of the present application provide a task processing method, a terminal, and a network-side device that can meet the continuously updated task requirements in a communication system.

[0007] In a first aspect, a task processing method is provided, including: a terminal sends a first message to a first network element, the first message being used to request modification of a target task or a subtask in the target task; the terminal receives a first response from the first network element, the first response being used to indicate a modification result of the target task or the subtask in the target task.

[0008] According to a second aspect, a task processing method is provided, including: a first network element receives a first message from a terminal, wherein the first message is used to request modification of a target task or a subtask in the target task; the first network element modifies the target task or the subtask in the target task according to the first message; the first network element sends a first response to the terminal, wherein the first response is used to indicate the modification result of the target task or the subtask in the target task.

[0009] According to a third aspect, a task processing method is provided, comprising at least one of the following items: a second network element sends a fourth message to a terminal, wherein the fourth message is used to indicate or request modification of a target task or a subtask in the target task; the second network element receives a fifth message sent by a first network element, wherein the fifth message is used to request subtask requirement information corresponding to the target task, and sends a fifth response to the first network element, wherein the fifth response is used to indicate the subtask requirement information corresponding to the target task.

[0010] In a fourth aspect, a task processing device is provided, including: a sending module for sending a first message to a first network element, wherein the first message is used to request modification of a target task or a subtask in the target task; and a receiving module for receiving a first response from the first network element, wherein the first response is used to indicate the modification result of the target task or the subtask in the target task.

[0011] In a fifth aspect, a task processing device is provided, including: a receiving module for receiving a first message from a terminal, wherein the first message is used to request modification of a target task or a subtask in the target task; a task modification module for modifying the target task or the subtask in the target task according to the first message; and a sending module for sending a first response to the terminal, wherein the first response is used to indicate the modification result of the target task or the subtask in the target task.

[0012] In the sixth aspect, a task processing device is provided, comprising at least one of the following: a sending module for sending a fourth message to a terminal, wherein the fourth message is used to indicate or request modification of a target task or a subtask in the target task; a receiving module for receiving a fifth message sent by a first network element, wherein the fifth message is used to request subtask requirement information corresponding to the target task, and sending a fifth response to the first network element, wherein the fifth response is used to indicate the subtask requirement information corresponding to the target task.

[0013] In a seventh aspect, a terminal 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.

[0014] In an eighth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect.

[0015] In the ninth aspect, a network side device is provided, which includes 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 steps of the method described in the second aspect or the third aspect are implemented.

[0016] In the tenth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0017] 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.

[0018] In the twelfth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect or the second aspect.

[0019] In the thirteenth aspect, a chip is provided, comprising 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 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.

[0020] In the fourteenth 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.

[0021] In an embodiment of the present application, the terminal sends a first message to the first network element to request modification of the target task or a subtask in the target task, and determines the modification result of the target task or the subtask in the target task based on the received first response. Thus, by providing a task-centric task modification process for task modification, it is possible to meet the constantly updated task requirements in the communication system while improving user experience and ensuring the rational use of network resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] FIG1 is a schematic structural diagram of a wireless communication system provided by an exemplary embodiment of the present application.

[0023] FIG2 is a flowchart of a task processing method according to an exemplary embodiment of the present application.

[0024] FIG3 is a second flowchart of a task processing method provided by an exemplary embodiment of the present application.

[0025] FIG4 a is one of the interactive flow diagrams of a task processing method provided by an exemplary embodiment of the present application.

[0026] FIG4 b is a second interactive flow diagram of a task processing method provided by an exemplary embodiment of the present application.

[0027] FIG4c is a third interactive flow diagram of a task processing method provided by an exemplary embodiment of the present application.

[0028] FIG4 d is a fourth interactive flow diagram of a task processing method provided by an exemplary embodiment of the present application.

[0029] FIG4e is a fifth interactive flow diagram of a task processing method provided by an exemplary embodiment of the present application.

[0030] FIG5 is a third flowchart of a task processing method provided by an exemplary embodiment of the present application.

[0031] FIG6 is a fourth flowchart of a task processing method provided by an exemplary embodiment of the present application.

[0032] FIG. 7 is a schematic diagram of a structure of a task processing device according to an exemplary embodiment of the present application.

[0033] FIG8 is a second structural diagram of a task processing device provided by an exemplary embodiment of the present application.

[0034] FIG9 is a third structural diagram of a task processing device provided by an exemplary embodiment of the present application.

[0035] FIG10 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.

[0036] FIG11 is a schematic structural diagram of a terminal provided by an exemplary embodiment of the present application.

[0037] FIG12 is a schematic structural diagram of a network-side device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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 (AS) 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.

[0043] 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 ( Function, AF), Task Management Function (TMF), etc. It should be noted that in the embodiment 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.

[0044] In addition, to facilitate understanding of the technical solutions provided by this application, the relevant technical features involved in this application are explained below, as follows.

[0045] 1. Mission: It is a comprehensive service (collection) provided on-demand by the 6G system based on external service requests, including communication, information, synaesthesia, computing, etc. The external service request can come from UE, OTT (Over The Top), etc.

[0046] 2. Task Management (TM): This is a management process that aims to respond to external business requests and provides communication functions and other 6G additional functions (such as positioning, telepathy, computing, etc.).

[0047] 3. Task template: used to indicate the task requirement information of the UE or network for the task. In this application, the task template may include but is not limited to at least one of task description information, task quality of experience (QoE) requirement information, task strategy or task quality (QoT) information, task parameters, etc.

[0048] The task description information is used to indicate the task information of the task, that is, to indicate the task. For example, if the task is to sense traffic congestion in the target area, the task description information is "traffic congestion"; for another example, if the task is to park the vehicle in a suitable or designated location, the task description information is "automatic parking".

[0049] Alternatively, the task description information is used to indicate application information of the task parameters, which may include but is not limited to at least one of the data network name (DNN), single network slice selection assistance information (S-NSSAI), AF identifier, and application (APP) identifier.

[0050] The task QoE requirement information is used to indicate the user's subjective perception of the quality and performance of the task, such as the user's perceived difficulty in completing the entire task process. In this application, the task QoE requirement information can be represented by the level of user experience achieved.

[0051] The task strategy or task quality information is used to indicate the service quality requirement of the task, which may include but is not limited to at least one of the following a)-d).

[0052] a) Task feedback time or task latency, which is used to indicate the upper limit of the time from when a task consumer or requester (e.g., UE, AF, etc.) initiates a task request to when it receives a task response.

[0053] b) Task accuracy, which indicates the probability of successful task completion or the degree to which the UE's expected value / the value promised by the task provider is consistent with the actual value.

[0054] c) Comprehensive energy consumption, which is used to indicate the energy consumption required to complete the task, and may include the energy consumption of the network or the terminal, where the network includes but is not limited to the core network and the access network.

[0055] d) Data density, which indicates the number of bits transmitted per unit time.

[0056] The task parameters are used to indicate task-specific parameters, which may include subtask configuration information. For example, if a task includes a perception subtask and a computing subtask, the task parameters include the perception subtask configuration and the computing subtask configuration.

[0057] Among them, if the subtask type is a perception subtask, the perception subtask configuration may include but is not limited to at least one of the perception measurement method, perception service, perception purpose, perception measurement signal, perception measurement accuracy, perception resolution, perception range, perception delay, and perception update frequency.

[0058] The sensing measurement mode may include at least one of the following modes: UE self-transmitting and self-receiving, other UE transmitting and UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, base station transmitting and base station receiving, etc. "Transmitting" refers to sending measurement signals, and "receiving" refers to receiving measurement signals and performing measurements.

[0059] The sensing services may include, but are not limited to, at least one of services with large-scale sensing (LSS) and high delay criticality, services with large sensing range and low delay criticality, services with small-scale sensing (SSS) and low delay criticality, and services with small sensing range and low delay criticality. The sensing services may also be represented by numbers, letters, or other character strings indicating these services.

[0060] The sensing purpose may include one or more applications supported by the sensing device and requiring sensing services, such as respiratory monitoring, surrounding traffic environment monitoring, etc.

[0061] The perception measurement signal is used to indicate a signal supported by the perception device (which can be sent or received, or both sent and received) for perception measurement. For example, the perception measurement signal may include, but is not limited to, at least one of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), multipath angle of arrival, multipath angle of departure, multipath delay, and Doppler frequency.

[0062] The perceptual measurement accuracy may include, but is not limited to, at least one of perceptual resolution and perceptual error.

[0063] The perception resolution refers to the ability to distinguish multiple perception targets from different dimensions. In this application, the perception resolution may include distance resolution, velocity resolution, angle resolution, etc.

[0064] The perception range refers to the effective range of a specific perception parameter under the premise of meeting certain perception performance indicators (such as perception accuracy). In this application, the perception range may include but is not limited to the perception distance range, perception speed range, perception angle range, etc.

[0065] The perception delay is used to quantitatively describe the real-time requirements of the perception service. For example, the perception delay can be the maximum delay from generating a perception service request to feeding back a perception result.

[0066] The perception update frequency is the reciprocal of the time interval between two adjacent perception results.

[0067] If the subtask type is a computing subtask, the computing subtask configuration may include but is not limited to at least one of data processing method, data processing delay, computing accuracy, and computing power information.

[0068] The data processing method may include at least one of denoising, privacy protection, standardization, and normalization.

[0069] The data processing delay is used to indicate the overall delay of data collection and data calculation.

[0070] The calculation accuracy is used to indicate the data acquisition accuracy and the overall accuracy of data calculation.

[0071] The computing power information may include at least one of computing power size and computing power type.

[0072] If the subtask type is an AI subtask, the computing subtask configuration may include but is not limited to at least one of model complexity, model training time, model inference time, model identification, model download address, data source information (or data source address), computing power, and computing type.

[0073] The model complexity refers to the complexity of the data that the model can fit.

[0074] Based on this, the following is an example of a task template.

[0075] Task description: Automatic parking:

[0076] Task type: multi-tasking;

[0077] Task strategy or task quality information: task feedback time (such as 10s, 20s...), accuracy (such as 95%, 90%...), etc.

[0078] Subtask type: Perception subtask

[0079] Perception subtask configuration information: perception measurement mode (such as UE self-transmitting and receiving, other UEs transmitting and UE receiving, base station transmitting and UE receiving, UE transmitting and base station receiving, base station transmitting and base station receiving), perception purpose (such as surrounding environment monitoring), etc.

[0080] Subtask type: Computational subtask

[0081] Computing subtask configuration information: data processing method (such as denoising, privacy protection, standardization, normalization...), data processing delay (such as 10s, 20s...), etc.

[0082] The task template here is a framework description without specific numerical description. The task instance is obtained after the UE fills it in or the TM (or TM network element, TM function, etc.) combines it with the task policy or task quality information to translate it.

[0083] Task instance: refers to the parameters or information of an ongoing task. In this application, the network will assign relevant parameters or information to the ongoing task. These parameters or information are task context. Considering that different networks require different task information, different network elements may store different task contexts for the same task instance.

[0084] Task session: refers to the process of communication between a UE and a TM, or refers to the process of communication between the UE, the TM, and related subtask functions. A task session can correspond to one or more subtask sessions (a subtask session refers to the process of communication between the TM and the subtask function). Establishing a task session means establishing a data transmission channel between the UE and the TM, or a data transmission channel between the UE, the TM, and related subtasks. In other words, a task session is a network resource established between the UE and the TM and related subtask functions in the operator's network. A task session can sometimes also be called a task connection or a task bearer. A task session or a subtask session can sometimes also be implemented by a PDU session. The task session in this application is different from the PDU session in the prior art (i.e., the data channel between the UE and the UPF). For example, in the prior art, if the UE wants to use the perception service, the UE will establish a PDU session (the data channel between the UE and the UPF). When the data reaches the UPF, the UPF may adopt some non-standard methods to transfer it to the perception execution node.

[0085] The task session identifier is used to identify the task session and is allocated by the UE and sent to the network, or allocated by the TM.

[0086] 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 (a task is a combined task). The subtask session identifier can be allocated by the UE and sent to the network, or the subtask session identifier can be allocated by the TM, the subtask management function, or the subtask function.

[0087] It should be noted that the target task or subtask in the embodiment of the present application is a task that is transmitted through a task session or a subtask session, and the transmission here can be the transmission of signaling or the transmission of data.

[0088] In addition, the subtask functions described in this application may include terminal devices, access network devices, or independently deployed execution units.

[0089] 4. The TM function is a core network element that can be used to implement one or more of the following functions: task verification, task template generation, task translation or disassembly, task management, task ID or task session ID allocation, task slicing or task DNN allocation, subtask management function or subtask function selection.

[0090] Task verification refers to verifying whether a task is a reasonable task requested by a permitted or authorized task consumer or requester (including but not limited to UE and AF). Task verification includes at least one of the following: verifying whether the AF is allowed to request a task template, whether the task request comes from a permitted or authorized UE (whether the UE has a task contract), whether the task request comes from a permitted or authorized 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.

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

[0092] Task template generation refers to the process of determining a task template through negotiation with the AF. This template describes a customized task for the UE, similar to a questionnaire. The requester expresses their task requirements by selecting required or optional parameters.

[0093] In this application, the task template may include at least one of a task template identifier, task description information, task QoE requirement information, task strategy or task quality information, and task parameters, wherein the task template identifier is used to identify the task template. Tasks of different task types may have one or more task templates.

[0094] The task translation or decomposition refers to translating or decomposing the task request into task instances, which are ongoing tasks. The task instance includes at least one of the following:

[0095] a) Task description information.

[0096] b) 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, and computing, and the combined task is any combination of the above tasks.

[0097] c) Task strategy or task quality information, which is used to indicate the service quality requirements of the task.

[0098] d) Security-related parameters: information used to encrypt transmitted signaling or data.

[0099] e) Subtask type, used to indicate the type of subtask. The subtask type may include at least one of a perception subtask, a computation subtask, and an AI subtask.

[0100] f) Subtask strategy or subtask quality information, used to indicate the service quality requirement of the subtask.

[0101] If the subtask type is a perception subtask, the subtask strategy or subtask quality information is a perception subtask configuration value (including specific information).

[0102] If the subtask type is a computing subtask, the subtask strategy or subtask quality information is the computing subtask configuration value (including specific information).

[0103] If the subtask type is an AI subtask, the subtask strategy or subtask quality information is the AI ​​subtask configuration value (including specific information).

[0104] g) The subtask timing relationship includes at least one of the subtask execution order and the subtask bearer establishment order. The subtask execution order is used to indicate the timing relationship of subtask execution, which includes at least one of the following implementation methods 1 and 2.

[0105] Method 1: TM informs the subsequent subtask execution function of the information of the previous subtask execution node.

[0106] Method 2: TM serves as the control node for task execution. The previous subtask execution function notifies TM of the previous subtask result, and TM notifies the subsequent subtask execution function of the previous subtask result.

[0107] 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 function of the perception function address. After the computing function receives data from the perception function, the computing function can start executing the computing subtask.

[0108] The subtask bearer establishment order is used to indicate the temporal relationship of subtask bearer establishment, which may include but is not limited to at least one of random establishment, concurrent establishment, establishment according to priority, etc.

[0109] It is worth noting that the subtask temporal relationship may be a part of the subtask strategy or subtask quality information.

[0110] In this application, due to differences in scenarios and requirements, the task instances can also be classified as follows, that is, the task instances can include general parameters and special parameters.

[0111] The general parameters are a description of the service quality requirements of the complete task, and include at least one of task description information, task type, task strategy or task quality information, and security-related parameters.

[0112] The dedicated parameter is a description of the service quality requirement of the specifically disassembled subtasks, and the dedicated parameter includes at least one of the subtask type, subtask strategy or subtask quality information, and subtask execution order.

[0113] It is worth noting that when the TM determines the task strategy or task quality information, subtask strategy or subtask quality information, its implementation method may include at least one of the following methods 1 and 2.

[0114] Method 1: Obtain the task policy or task quality information, subtask policy or task quality information from the PCF or a function responsible for policy billing.

[0115] Mode 2: Determine the task policy or task quality information, subtask policy or subtask quality information according to information obtained from the PCF or the policy charging function.

[0116] The task identifier or task session identifier allocation may include allocating a task identifier or a task session identifier, and allocating a subtask identifier or a subtask session identifier.

[0117] The task slice or task DNN allocation may include allocating task slices or task DNNs, and allocating subtask slices or subtask DNNs.

[0118] The subtask management function or subtask function selection refers to the TM selecting a subtask management function or subtask function that can meet the subtask quality requirements. For example, the TM may query the NRF, UDM, or UDR to determine the appropriate subtask management function or subtask function, or the TM may determine the appropriate subtask management function or subtask function based on stored or maintained information (such as whether the task is supported, computing power, etc.).

[0119] In this application, the subtask management function can be to configure a unified management function for different tasks such as perception subtasks, computing subtasks, AI subtasks, etc., such as perception subtasks, computing subtasks, and AI subtasks corresponding to the same subtask management function; or different management functions can be configured for different types of subtasks, such as the perception management function corresponding to the perception subtask, the computing management function corresponding to the computing subtask, and the AI ​​management function corresponding to the AI ​​subtask, and there is no restriction here.

[0120] Based on this, the technical solutions provided by the embodiments of the present application are described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0121] FIG2 is a flow chart of a task processing method 200 according to an exemplary embodiment of the present application. This method 200 may be, but is not limited to, executed by a terminal, specifically by at least one of hardware and software installed in the terminal. In this embodiment, the method 200 may include at least the following steps.

[0122] S210. The terminal sends a first message to the first network element.

[0123] The first network element is a core network internal network element, which can be understood as a network element with a task management (TM) function. For example, in this embodiment, the first network element can implement, but is not limited to, one or more of task verification, task template generation, task translation or disassembly, task identifier allocation, task slice allocation, task DNN allocation, subtask management function selection, subtask function selection, etc.

[0124] Based on this, the first network element may be but is not limited to the aforementioned TM function (or referred to as TM network element).

[0125] The first message is used to request modification of the target task or a subtask in the target task. That is, in this embodiment, when the terminal requests task modification, it can make the request at the granularity of a single task, or at the granularity of one or more subtasks included in the task, thereby ensuring the flexibility of task modification and meeting the modification requirements of different tasks.

[0126] In an optional implementation, the subtasks in the target task can be understood as subtasks obtained by translating or disassembling the target task, subtasks associated with the target task, etc. In this embodiment, there are multiple ways to classify the types of subtasks in the target task. For example, the subtasks may include but are not limited to communication subtasks, perception subtasks, computing subtasks, data subtasks, positioning subtasks, Internet Protocol Multimedia System (IMS) subtasks, AI subtasks, etc.

[0127] For another example, the subtasks may include, but are not limited to, computing subtasks, information processing subtasks, multimedia subtasks, immersive subtasks, and communication subtasks. Computing subtasks include AI computing tasks and non-AI computing tasks; information processing subtasks include positioning information processing and synaesthesia information processing; and immersive subtasks include extended reality (XR) tasks and virtual reality (VR) tasks.

[0128] It should be noted that the subtasks in the target task described in this application can be understood as one or more subtasks included in the target task, or can be understood as one or more subtasks associated with the target task, and no limitation is made here.

[0129] Based on this, in this embodiment, the terminal's request to modify the target task or the subtask in the target task can also be understood as: the terminal requests the network side to modify, update or adjust the resources (or network resources) allocated to the target task or the subtask in the target task. Thus, by modifying the resources allocated to the task, it is possible to meet the constantly updated task requirements in the communication system while improving the user experience and ensuring the rational use of network resources.

[0130] In addition, since the resource allocation of multiple subtasks included in the target task can be updated through the first message, a single signaling message, in this application, the signaling overhead during task processing can also be saved.

[0131] In a possible implementation, there may be multiple ways for the terminal to send the first message to the first network element. For example, the terminal may send the first message directly to the first network element, or forward the first message to the first network element through other network elements.

[0132] In the case where the terminal forwards the first message to the first network element through other network elements, the other network elements may be, but are not limited to, AMF, SMF, control network element, etc. The control network element may have one or more functions such as mobility management function, connection management function, and session management function.

[0133] In this embodiment, if the first network element and the SMF are co-located, the first message may be a PDU session release request message. If the first network element and the SMF are deployed independently, the first message may be, but is not limited to, a task channel modification request message, a task modification request message, a task resource modification message, etc.

[0134] Optionally, the first message can be generated by the first protocol layer of the terminal. The first protocol layer can be understood as a newly added protocol layer. For example, the first protocol layer can be responsible for task management, task signaling or task data generation and processing, etc.; the first protocol layer can also be understood as or an enhancement of an existing protocol layer, so that the existing protocol layer has functions such as task management or task signaling or task data generation and processing, such as an enhancement of the non-access stratum (NAS) or session management (SM) layer.

[0135] Then, after receiving the first message, the first network element can modify the target task or the subtask in the target task according to the first message, and send a first response to the terminal according to the modification result to indicate the modification result of the target task or the subtask in the target task, such as whether the network side accepts the task modification request or whether the task modification is successful.

[0136] Similar to the terminal side, the first network element has a peer first protocol layer for communication between the terminal and the first network element, such as the first response message can be generated or processed by the first protocol layer of the first network element.

[0137] When the first network element performs the modification operation on the target task or the subtask in the target task, there may be multiple implementations depending on the internal implementation of the first network element.

[0138] For example, the first network element can independently perform the modification operation of the target task or the subtask in the target task, or can jointly perform the modification operation of the target task or the subtask in the target task with other network elements. This embodiment does not limit this.

[0139] S220: The terminal receives a first response from the first network element.

[0140] The first response is used to indicate a modification result of the target task or a subtask in the target task.

[0141] It can be understood that, similar to the sending of the first message, there are also multiple ways for the terminal to receive the first response, such as directly receiving the first response sent by the first network element, or receiving the first response forwarded by other network elements, which is not limited here.

[0142] In this embodiment, the terminal sends a first message to the first network element to request modification of the target task or the subtask in the target task, and determines the modification result of the target task or the subtask in the target task based on the received first response. Thus, by providing a task-centric task modification process for task modification, it is possible to meet the constantly updated task requirements in the communication system while improving user experience and ensuring the rational use of network resources.

[0143] In addition, in this embodiment, the task-centric request to modify the target task or the subtasks in the target task can also enable the network to update the allocated subtask resources for one or more subtasks in the target task, thereby realizing task management in the communication network that supports services such as communication, perception and computing.

[0144] FIG3 is a flow chart of a task processing method 300 according to an exemplary embodiment of the present application. This method 300 may be, but is not limited to, executed by a terminal, specifically by at least one of hardware and software installed in the terminal. In this embodiment, the method 300 may include at least the following steps.

[0145] S310. The terminal sends a first message to a first network element.

[0146] The first message is used to request modification of a target task or a subtask in the target task.

[0147] S320: The terminal receives a first response from the first network element.

[0148] The first response is used to indicate a modification result of the target task or a subtask in the target task.

[0149] It can be understood that the implementation process of S310-S320 can refer to the relevant description in the aforementioned method embodiment 200. Of course, in addition to referring to the relevant description in the aforementioned method embodiment 200, as a possible implementation method, the first message sent by the terminal to the first network element may include but is not limited to at least one of the following 01)-06), so that the first network element can clearly understand the relevant information of the target task or the subtask in the target task that needs to be modified based on the content in the first message, so as to realize resource modification of the target task or the subtask in the target task.

[0150] 01) Terminal identification, used to identify the terminal that sends the first message, so that the first network element can determine which terminal requests task modification.

[0151] 02) A task template, which is used to indicate the task requirement information corresponding to the requested target task. It is worth noting that the task template is populated and can represent the changed or updated task requirements, so that the first network element can modify the target task or subtasks within the target task according to the task template.

[0152] Based on this, in one implementation, the task template may include but is not limited to at least one of the following 121)-124).

[0153] 021) Task description information, used to indicate the task information of the target task or application information of the task parameters, so that the first network element can modify the target task or the subtask in the target task according to the task description information.

[0154] 022) Task QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task, so that the network side (such as the first network element, subtask management function, subtask function, etc.) can modify or adjust the resources allocated to the target task according to the task QoE requirement information.

[0155] The task QoE requirement information is the user's subjective feeling about the quality and performance of the task, which can be represented by the level of user experience achieved.

[0156] 023) Task strategy or task quality information, used to indicate the service quality requirements corresponding to the requested target task, so that the network side (such as the first network element, subtask management function, subtask function, etc.) can modify or adjust the resources allocated to the target task according to the task strategy or task quality information.

[0157] 024) Subtask strategy or subtask quality information, used to indicate the service quality requirements corresponding to the subtasks in the requested target task, so that the network side (such as the first network element, subtask management function, subtask function, etc.) can modify or adjust the resources allocated to the subtasks in the target task according to the subtask strategy or subtask quality information.

[0158] 03) DNN, used to indicate the DNN corresponding to the requested target task, such as used by the first network element to determine that the task corresponding to or associated with the DNN is the target task or a subtask in the target task and modify it.

[0159] 04) S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task, such as used by the first network element to determine that the task corresponding to or associated with the S-NSSAI is the target task or a subtask in the target task and modify it.

[0160] 05) A task identifier or a task session identifier, used to identify the target task requested, such as used by the first network element to determine that the task corresponding to or associated with the task identifier or the task session identifier is the target task and to modify it.

[0161] 06) A subtask identifier or a subtask session identifier, used to identify a subtask in the requested target task, such as used by the first network element to determine that a subtask corresponding to or associated with the subtask identifier or the subtask session identifier is a subtask in the target task and to modify it.

[0162] It is worth noting that which of the above items 01)-06) are included in the first message can be determined by protocol agreement, high-level configuration or terminal implementation, and is not limited here.

[0163] In addition, in a possible implementation, there may be multiple triggering modes for the terminal to send the first message to the first network element. For example, in this embodiment, the implementation may include S311 shown in FIG3 , which is as follows.

[0164] S311: When the terminal determines that the first condition is met, the terminal sends the first message to the first network element.

[0165] The first condition may include but is not limited to at least one of the following conditions 1 to 7.

[0166] Condition 1: The task requirement information of the terminal changes.

[0167] The task requirement information may be, but is not limited to, task QoE requirement information, task strategy or task quality information, task description information, and the like.

[0168] Condition 2: The terminal desires to modify the target task or a subtask in the target task.

[0169] The terminal may expect to modify part or all of the target task. If the terminal expects to modify the entire target task, that is, to modify the complete task, then the first message may include at least one of the task identifier, task session identifier, task policy, or task quality information, so that the first network element can modify the entire target task according to the first message.

[0170] If the terminal expects to modify part of the target task, such as modifying a subtask in the target task, then the first message may include at least one of the subtask identifier, subtask session identifier, subtask policy or subtask quality information, so that the first network element can modify the subtask in the target task according to the first message.

[0171] Condition 3: The terminal has activated the power saving mode or the battery level of the terminal is lower than a first threshold.

[0172] Optionally, when the first condition includes that the terminal has turned on the power saving mode or the battery level of the terminal is lower than a first threshold, the first message may also include a first indication to indicate the battery status of the terminal, such as if the terminal is in a low battery state, so that the first network element can modify the resources allocated to the target task or the subtask in the target task with reference to the battery status to meet the terminal needs.

[0173] Condition 4: The terminal moves.

[0174] Wherein, when the first condition includes the movement of the terminal, the first message may also include the location information of the terminal after the movement, so as to indicate that the terminal location has changed, so that the first network element can adjust the resources allocated to the target task or the subtask in the target task according to the location information. Wherein, the location information may include but is not limited to one or more of Tracking Area Identity (TAI), cell information, Public Land Mobile Network Identity (PLMN ID), Stand-alone Non-Public Network (SNPN) ID, etc.

[0175] Condition 5: The task contract of the terminal changes.

[0176] For example, the terminal only signed a contract for communication services when the target task was created, but subsequently signed a contract for AI services and computing services, etc., which changed the task contract and required a request to modify the target task.

[0177] Condition 6: The terminal obtains a fourth message from the second network element, where the fourth message is used to instruct or request modification of the target task or a subtask in the target task.

[0178] The second network element may be, but is not limited to, an AF, based on which the terminal may receive the fourth message from the AF via the application layer. In this embodiment, the content of the fourth message may be the same as or different from the first content.

[0179] It is worth noting that if the fourth message is used by the second network element to request the terminal to modify the target task or a subtask within the target task, then the second network element may send the fourth message to the terminal upon determining that the second condition is satisfied. Optionally, the second condition includes at least one of a change in the task contract of the terminal and receipt by the second network element of a task modification request from the terminal, wherein the task modification request is used to request modification of the target task or a subtask within the target task.

[0180] As a possible implementation, the process of the second network element sending the fourth message to the terminal may include: the second network element first performing task translation or decomposition to obtain an updated task instance, and then sending the fourth message to the terminal based on the updated task instance. Optionally, the fourth message may include, but is not limited to, at least one of the following 11)-17).

[0181] 11) The task description information is used to indicate the task information of the target task or application information of the task parameters.

[0182] 12) DNN, used to indicate the DNN corresponding to the requested target task.

[0183] 13) S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task.

[0184] 14) Task strategy or task quality information, used to indicate the service quality requirements corresponding to the requested target task;

[0185] 15) Task ID or task session ID, used to identify the target task requested;

[0186] 16) a subtask identifier or a subtask session identifier, used to identify the subtask in the requested target task;

[0187] 17) Subtask strategy or subtask quality information, used to indicate the service quality requirements corresponding to the subtasks in the requested target task.

[0188] It is worth noting that if the terminal receives the fourth information, and the fourth information is used to request modification of the target task or a subtask within the target task, then the first message sent by the terminal to the first network element may not include the task template, but instead include the content of the fourth information as part of the first message. This allows the first network element to directly obtain an updated task instance based on the first message when modifying the task based on the received first message, without having to decompose or translate the task to obtain the updated task instance.

[0189] Condition 7: The terminal obtains a target task template, and the target task template is different from the task template used when the target task is created.

[0190] For example, if the terminal has signed up for a membership service provided by the AF, the AF will re-negotiate the task template with the first network element and provide a new task template to the terminal.

[0191] Correspondingly, after receiving the first message from the terminal, the first network element can modify the target task or the subtask in the target task according to the first message in multiple ways. For example, in this embodiment, the first network element can determine the updated task instance based on the first message, and then modify the target task or the subtask in the target task based on the task instance.

[0192] The task instance is used to indicate relevant parameters or information allocated to the target task, or in other words, the task instance is the parameters or information corresponding to the running target task.

[0193] In this embodiment, the first network element may determine the updated task instance based on the first message in various ways. For example, if the first message includes the task template, the first network element may translate, decompose, or map the first message to obtain the updated task instance.

[0194] If the first message does not include the task template, the first network element may determine the task instance according to at least one of the following 21)-25).

[0195] 21) The first message. For example, if the first message is determined by the terminal based on the received fourth message and includes an updated task instance, the first network element can directly obtain the updated task instance based on the first message without translation, decomposition, or mapping.

[0196] 22) Local configuration or local policy or operator policy of the first network element. For example, the local configuration or local policy or operator policy is configured with a method or parameters for determining the updated task instance.

[0197] 23) The first network element stores or maintains a task context associated with the target task. For example, if the first network element has generated a task instance for a similar task and the task instance can meet the business requirements of the target task requested by the terminal, the first network element can directly use the task instance.

[0198] 24) Task instance associated with the target task stored or maintained in the UDM or UDR. For example, the first network element may determine the task instance associated with the target task stored or maintained in the UDM or UDR as the updated task instance.

[0199] 25) An intelligent module inside the first network element, which can generate a corresponding task instance based on the task description information in the first message. The intelligent module is trained based on a large amount of input and output data (task description-task instance) and achieves appropriate reasoning accuracy, and can be used to generate the task instance.

[0200] Based on the updated task instance obtained above, when the first network element modifies the target task or the subtask in the target task according to the task instance, the modification method may include but is not limited to at least one of the following 31)-33).

[0201] 31) Update the resources corresponding to the subtasks in the target task. For example, when the subtask strategy or subtask quality information changes, the resources allocated to the subtasks in the target task need to be modified to correspond to the changed subtask strategy or subtask service quality information. It is worth noting that the above process may involve the selection of subtask functions. For example, if the subtask is a computing subtask and the computing power of the computing subtask increases, then the computing subtask function corresponding to the current computing subtask cannot provide the updated computing power, and the computing subtask function needs to be reselected.

[0202] 32) Add subtasks to the target task. For example, the original task is broken down into perception subtasks, and after the task is modified, it can include perception subtasks and computation subtasks.

[0203] 33) Deleting at least some of the subtasks in the target task. For example, the original task is decomposed into a perception subtask and a computation subtask, and after modification, only the perception subtask is included.

[0204] In one possible implementation, the aforementioned implementation process of the first network element modifying the target task or a subtask within the target task based on the task instance is related to the internal implementation of the first network element. For example, depending on whether the first network element and the subtask management function are co-located or integrated, the implementation process of the first network element modifying the target task or a subtask within the target task based on the task instance may include at least one of the following implementations 1 and 2.

[0205] Implementation method 1: Assuming that the first network element and the subtask management function are deployed independently, the process of the first network element modifying the target task or the subtask in the target task according to the task instance may be as follows.

[0206] First, the first network element may send a second message to the subtask management function based on the task instance, wherein the second message is used to request modification of the subtask in the target task. Optionally, in this embodiment, the second message may include but is not limited to at least one of 41)-44).

[0207] 41) The identifier or address information of the first network element, used to identify the sender of the second message.

[0208] 42) Subtask strategy or subtask quality information, so that the subtask management function selects a subtask function that meets the subtask strategy or subtask quality information, and notifies the subtask function of the subtask strategy or subtask quality information, so that the subtask function can modify the resources allocated to the subtask according to the subtask strategy or subtask quality information. For example, the computing function corresponding to the computing subtask can modify or adjust the computing power information allocated to the computing subtask according to the subtask strategy or subtask quality information.

[0209] 43) Subtask execution order, so that the subtask management function notifies the subtask execution order to the subtask function, and the subtask function modifies the execution order of each subtask in the target task with reference to the subtask execution order.

[0210] 44) Subtask identification, used to identify the subtask that needs to be modified or updated.

[0211] It is worth noting that the first network element stores the task context when the target task is established. The task context includes the association relationship between the target task and target task related information, such as the association relationship between the target task and the subtask management function, etc. Then, the first network element can determine the subtask management function based on the task context and send the second message.

[0212] Then, after receiving the second message, the subtask management function can determine the appropriate subtask function based on the subtask strategy or subtask quality information included in the second message, and send a subtask modification request to the subtask function, wherein the subtask modification request can include at least one of the subtask strategy or subtask quality information, the subtask execution order, and the subtask identifier. Then, after receiving the subtask modification request, the subtask function modifies the subtask according to the subtask modification request, and sends a subtask modification response to the subtask management function based on the modification result to indicate the modification result of the subtask, such as whether the modification is successful or failed.

[0213] Optionally, if the modification result is modification failure, the subtask modification response may further include the reason for the modification failure, such as the subtask is in progress, modification of the subtask is not allowed, the subtask is not found, etc.

[0214] Finally, after receiving the subtask modification response sent by the subtask function, the subtask management function sends a second response to the first network element to indicate the modification result of the subtask, such as whether the modification is accepted and whether the modification is successful. Correspondingly, the first network element receives the second response sent by the subtask management function. If the second response indicates that the modification result of the subtask is accepted, the second response may include but is not limited to the modified IP address of the subtask function, the ID of the subtask function, the fully qualified domain name (FQDN) of the subtask function, etc.

[0215] Optionally, if the subtask is a computing subtask, then the second response may also include computing power information of the subtask function; if the subtask is an AI subtask, then the second response may also include at least one of an AI model acquisition address and an AI model training address.

[0216] Implementation method 2: Assuming that the first network element and the subtask management function are co-installed or the subtask management function is integrated into the first network element, then the process of the first network element modifying the target task or the subtask in the target task according to the task instance can be as follows.

[0217] First, the first network element determines the subtask function that satisfies the subtask policy or subtask quality information in the task instance. In this embodiment, there may be multiple ways for the first network element to determine the subtask function. For example, the first network element may query the NRF, UDM, or UDR to obtain the subtask function that satisfies the subtask policy or subtask quality information in the task instance; or, the first network element determines the subtask function that satisfies the subtask policy or subtask quality information in the task instance based on the stored or maintained subtask capabilities.

[0218] Then, the first network element sends a third message to the determined subtask function based on the task instance, and the third message is used to request the subtask function to modify the subtask in the target task or configure the subtask information to the subtask function. Optionally, the third message may include but is not limited to at least one of 51)-54).

[0219] 51) The identifier or address information of the first network element, used to identify the sender of the second message.

[0220] 52) subtask strategy or subtask quality information, so that the subtask function can modify or adjust the resources allocated to the subtask according to the subtask strategy or subtask quality information. For example, the computing function corresponding to the computing subtask can modify or adjust the computing power information allocated to the computing subtask according to the subtask strategy or subtask quality information in the third message.

[0221] 53) Subtask execution order, whereby the subtask function executes the subtasks according to the subtask execution order, i.e., modifies or adjusts the subtask execution order. For example, if the subtask execution order indicates that the order of the computation subtasks changes from 1 to 2, the computation function corresponding to the computation subtask modifies the computation subtask execution order, such as only executing the computation subtask after receiving the execution result of the preceding subtask function.

[0222] 54) Subtask identification, used to identify the subtask that needs to be modified or updated, such as identifying the relationship between the subtask and the target task or the subtask and the terminal, which has an impact on the subtask information stored in the subtask function.

[0223] Finally, after receiving the third message, the subtask function modifies the subtask according to the third message, and sends a third response to the first network element based on the modification result to indicate the modification result of the subtask, such as whether the subtask function accepts the modification or whether the modification is successful.

[0224] Optionally, if the third response indicates that the modification result of the subtask is to accept the modification, then, if the subtask is a computing subtask, the third response may include computing power information of the subtask function, such as computing power size, computing power type, etc.; if the subtask is an AI subtask, the third response may also include at least one of the AI ​​model acquisition address and the AI ​​model training address.

[0225] Optionally, if the third response indicates that the modification result of the subtask is not accepted, then the third response may include the reason for the modification failure, such as the subtask is in progress, the subtask is not allowed to be modified, the subtask is not found, etc.

[0226] It is worth noting that, for the aforementioned implementation manner 2, if the third response indicates that the modification result of the subtask is rejection, then the first network element may again or reselect a subtask function to modify the subtask.

[0227] Of course, for the aforementioned implementation method 1 or 2, if the first network element fails to query or determine the subtask management function or subtask function, it can directly send a first response to the terminal to indicate that the modification result of the target task or the subtask in the target task is a modification failure, and the reason for the modification failure is that the subtask management function or subtask function cannot be queried or determined.

[0228] As a possible implementation, when the first network element modifies the target task or the subtask in the target task according to the task instance, in addition to executing the aforementioned implementation method 1 or implementation method 2, it can also modify the task context of the target task to record the relationship between the task requirement information of the target task and the updated task instance.

[0229] As another possible implementation, for each of the aforementioned implementations, if the first network element modifies the target task or the subtask in the target task according to the first message, a situation occurs where the task type of the target task determined according to the updated task instance is inconsistent with the task type signed by the terminal, such as the first network element determines that the task type of the target task is a combined task (or a single task) according to the updated task instance, but the task type signed by the terminal is a single task (or a combined task), resulting in the first network element being unable to determine whether the task requirement provided by the terminal is a single subtask requirement or a complete task requirement. The single task can be understood as the target task including a subtask, such as the target task including a communication subtask, and the combined subtask can be understood as the target task including two or more subtasks, such as the target task including a communication subtask, a computing subtask, and an AI subtask.

[0230] In this case, the first network element may send a fifth message to the second network element (e.g., AF) to request the second network element for the subtask requirement information corresponding to the target task, thereby dynamically determining the subtask requirement information. Optionally, the fifth message may include, but is not limited to, task description information, task QoE requirement information, subtask identifier, subtask type, etc.

[0231] Correspondingly, after receiving the fifth message, the second network element determines the task contract of the terminal and the sub-task requirement information based on the fifth message, and sends a fifth response to the first network element based on the determination result to indicate the sub-task requirement information corresponding to the target task, so that the first network element determines whether the task requirement provided by the terminal is a single task requirement or a complete task requirement based on the fifth response sent by the second network element. If the sub-task requirement information carried in the fifth response is a single task, it is determined that the task requirement provided by the terminal is a single task requirement, etc.

[0232] Optionally, the fifth response may include but is not limited to at least one of task description information, task strategy or task quality information, subtask strategy or subtask quality information.

[0233] In one possible implementation, before the first network element performs a modification operation on the target task or a subtask in the target task based on the first message, it can also verify whether the first message is allowed or authorized, thereby ensuring the legitimacy of the first message or the legitimacy of the terminal.

[0234] The first network element may perform a modification operation on the target task or a subtask in the target task according to the first message when it is determined that the first message is allowed or authorized.

[0235] Alternatively, when the first network element determines that the first message is not allowed or authorized, it sends a first response to the terminal to indicate to the terminal that the modification result of the target task or the subtask in the target task is a failure, and the reason for the release failure includes that the first message is not allowed or authorized.

[0236] Optionally, in the present application, there may be multiple ways for the first network element to verify whether the first message is allowed or authorized. For example, the first network element may verify whether the first message is allowed or authorized based on the task identifier and the terminal identifier carried in the first message. For example, the first network element may determine that the first message is allowed or authorized when it is determined that the task identifier and the terminal identifier carried by the first message are stored; and when the task identifier corresponding to the first message is not stored in the first network element and there is no task contract corresponding to the terminal, it may determine that the first message or the terminal is not allowed or authorized.

[0237] Based on this, the first network element may send a first response to the terminal according to the modification result of the aforementioned target task or the subtask in the target task, so as to indicate the modification result of the target task or the subtask in the target task. As a possible implementation method, when the first response indicates that the modification result is accepted (i.e., the modification is accepted), the first response may include at least one of the following 61)-65) to indicate the modified target task or the subtask in the target task.

[0238] 61) Task identifier, used to indicate the target task.

[0239] 62) A subtask management function identifier or a subtask function identifier, wherein the subtask function identifier is used to indicate a subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate a subtask function for executing subtasks in the target task.

[0240] The subtask management function identifier may be, but is not limited to, the ID of the subtask management function, the IP address of the subtask management function, the FQDN of the subtask management function, etc. Similarly, the subtask function identifier may also be, but is not limited to, the ID of the subtask function, the IP address of the subtask function, the FQDN of the subtask function, etc.

[0241] 63) Mission strategy or mission quality information.

[0242] 64) Subtask strategy or subtask quality information.

[0243] 65) Subtask execution order.

[0244] It is worth noting that the modified information 61)-65) can be the same or different from the information before the modification. For example, the modified task identifier can be the same or different from the one before the modification, and the execution order of the subtasks before and after the modification can be the same or different, etc., which are not limited here.

[0245] As another possible implementation, when the first response indicates that the modification result is a rejection, the first response may include a rejection reason. For example, in this application, the rejection reason may include but is not limited to at least one of the following 71)-74).

[0246] 71) Network congestion. For example, DNN congestion, S-NSSAI congestion, etc.

[0247] 71) The target task or the subtasks within the target task are not allowed to be modified;

[0248] 73) The terminal is not allowed or authorized, that is, after verification by the first network element, the first message is illegal.

[0249] 74) Insufficient subtask resources, such as insufficient computing resources, insufficient perception resources, insufficient AI resources, etc.

[0250] In this embodiment, by providing a task processing method, after the task is established, the established task can be modified at any time according to the task requirements, so that the network side can reasonably adjust the network resources for the task according to the terminal request, which can not only improve the terminal's task experience, but also ensure the rational use of network resources.

[0251] Based on the above description of method embodiments 200-300, in order to further understand the technical solution provided by this application, the task modification process provided by this application is explained below with reference to examples, as follows.

[0252] Example 1

[0253] Assuming that the first network element and the subtask management function are deployed independently, and the first network element is a TM network element and the second network element is an AF network element, then, as shown in Figure 4a, the task processing method provided in this application may include but is not limited to the following steps.

[0254] S411 : The AF sends a sixth message to the TM network element, requesting the TM network element to create or formulate a task module that meets service requirements for one or more target tasks.

[0255] Optionally, the sixth message may include but is not limited to at least one of the following 801)-808).

[0256] 801) Application Service Provider ID (ASPID), used to identify an application server, and its representation may include but is not limited to ASPID, IP address, and FQDN.

[0257] 802)Task description information.

[0258] 803) Task template identification, used to identify a task template, which can be expressed as a task template ID.

[0259] 804) DNN or S-NSSAI information. If the task template is generated for multiple task requests, the sixth message may carry multiple different DNNs or S-NSSAIs.

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

[0261] 806) Expected task template applicable area, used to indicate the geographical area or network area to which the task template is applicable. The geographical area may include but is not limited to a cell ID, TAI, geographic location, etc. The network area may include but is not limited to a PLMN ID, SNPN ID, etc.

[0262] 807) Subscribe to task template change notification, which is used to indicate that the AF needs to be notified when the task template is upgraded or changed.

[0263] 808) Task quality information, which may include a task quality reference ID (Reference ID) of the task, such as a standardized 6QI value, a task quality index (index) value, etc.

[0264] S412: The TM network element creates a new task template according to the sixth message.

[0265] The TM network element may generate or formulate a task template according to at least one of the following 901)-905).

[0266] 901) received the sixth message.

[0267] 902) Local configuration of TM network elements or local policies or operator policies.

[0268] 903) The task context associated with the target task stored or maintained by the TM network element, for example, if the first network element has generated a task template for a similar task that can meet the business requirements of the target task requested by the terminal, the first network element can directly use the task template.

[0269] 904) Task templates associated with target tasks stored / maintained in UDM or UDR.

[0270] 905) An intelligent module inside the TM network element, which can generate a corresponding task template based on the task description information in the first message. The intelligent module is trained based on a large amount of input and output data (task description-task template) and achieves appropriate reasoning accuracy, and can be used to generate task templates.

[0271] In addition, the sixth message can also be a task template modification request message or a task template generation request message, which can be sent to the TM network element via the 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.

[0272] S413: The TM network element sends a sixth response to the AF, where the sixth response includes a task template.

[0273] It's important to note that steps S411-S413 can be understood as the negotiation process for task templates, where the task templates are customized. Customization refers to the task provider and operator signing a task-level agreement, with a task template for each task in the agreement. The negotiated task template is a description of a customized task given by the network to the terminal. It can be understood as a questionnaire, where the requester "checks" certain required or unrequired parameter requirements to express their needs for the task.

[0274] S414: The terminal obtains a task module from the TM network element or the AF.

[0275] If the terminal obtains the task template from the TM network element, the terminal can obtain it through the registration process, such as the TM network element includes the task template in the registration acceptance message. In this case, the TM network element and the AMF are jointly established; or, the terminal obtains it through the connection between the terminal and the TM network element, such as the terminal obtains the address information of the TM network element (which can be obtained from the registration process), establishes a connection with the TM network element (which can be a user plane connection or a control plane connection), and obtains the task template through the connection.

[0276] If the terminal obtains the task template from the AF, then it can obtain it from the AF through the application layer. How to obtain it is not within the scope of 3GPP.

[0277] S415 , the terminal fills the acquired task template and sends the filled task template to the TM network element to allocate resources for the target task.

[0278] The terminal may fill in part or all of the content of the task template, depending on the terminal implementation.

[0279] S416: The terminal sends a first message to the TM network element, wherein the first message is used to request modification of the target task or a subtask within the target task, such as requesting modification of resources allocated by the network to the target task or a subtask within the target task.

[0280] Optionally, the terminal may send the first message to the first network element when it is determined that a first condition is met; wherein the first condition includes at least one of the following conditions 1 to 7.

[0281] Condition 1: The task requirement information of the terminal changes.

[0282] Condition 2: The terminal desires to modify the target task or a subtask in the target task.

[0283] Condition 3: The terminal has activated the power saving mode or the battery level of the terminal is lower than a first threshold.

[0284] Condition 4: The terminal moves.

[0285] Condition 5: The terminal obtains a fourth message from the second network element, where the fourth message is used to instruct modification of the target task or a subtask in the target task.

[0286] Condition 6: The task contract of the terminal changes.

[0287] Condition 7: The terminal obtains a target task template, and the target task template is different from the task template used when the target task is established.

[0288] S417 , the TM network element verifies whether the first message is authorized or allowed. If it is authorized or allowed, execute S418 ; otherwise, execute S422 .

[0289] S418: The TM network element disassembles or translates the first message to obtain an updated task instance.

[0290] S419: The TM network element sends a second message to the subtask management function according to the task instance, where the second message is used to request modification of the subtask in the target task.

[0291] It is worth noting that after receiving the second message, the subtask management function can determine the subtask function that meets the subtask policy or subtask quality information, and request the subtask function to modify the subtask, such as modifying the network resources allocated to the subtask.

[0292] For example, if the subtasks include a sensing subtask, the TM network element sends a second message to a subtask management function (or sensing management function) to request that the network modify sensing resources. The second message may include, but is not limited to, at least one of the following: a sensing subtask policy or sensing quality information, a sensing subtask execution order, and a sensing subtask identifier. The sensing management function then selects an appropriate sensing function based on the second message, such as a sensing function that meets the sensing subtask policy or sensing quality information, to request the sensing function to modify the sensing subtask. The second response, based on the modification result indicated by the sensing function, is sent to the TM network element to indicate the modification result of the sensing subtask. If the second response indicates that the modification result is acceptance, the second response may include at least one of the IP address, ID information, and FQDN of the sensing function.

[0293] For another example, if the subtask includes a computing subtask, the TM network element sends a second message to a subtask management function (or computing management function) requesting the network to modify computing resources. The second message may include, but is not limited to, at least one of the following: a computing subtask policy or computing quality information, a computing subtask execution order, and a computing subtask identifier. The computing management function then selects an appropriate computing function based on the second message, such as a computing function that meets the computing subtask policy or computing quality information, to request that the computing function be modified to perceive the computing subtask. The computing management function then sends a second response to the TM network element based on the modification result indicated by the perception function, indicating the modification result of the computing subtask. If the second response indicates that the modification result is acceptance, the second response may include at least one of the computing function's IP address, ID information, FQDN, and computing capacity information (e.g., computing capacity size and type).

[0294] For another example, if the subtask includes an AI subtask, the TM network element sends a second message to the subtask management function (or AI management function) to request the network to modify the AI ​​resources. The second message may include, but is not limited to, at least one of an AI subtask policy or AI quality information, an AI subtask execution order, and an AI subtask identifier. The AI ​​management function then selects an appropriate AI function based on the second message, such as an AI function that meets the AI ​​subtask policy or AI quality information, to request modification of the perception function to perform the AI ​​subtask, and sends a second response to the TM network element based on the modification result indicated by the AI ​​function to indicate the modification result of the AI ​​subtask. If the modification result indicated by the second response is acceptance of the modification, the second response may include at least one of the AI ​​function's IP address, AI function ID information, AI function's FQDN, AI function's AI model acquisition address, and AI function's AI model training address.

[0295] S420: The TM network element receives a second response sent by the subtask management function, where the second response is used to indicate a modification result of the subtask.

[0296] S421: The TM network element modifies at least a portion of the task context of the target task to record the relationship between the task requirement information and the updated task instance.

[0297] S422: The TM network element sends a first response to the terminal to indicate a modification result of the target task or a subtask in the target task.

[0298] It is worth noting that the implementation process of each step of the task processing method provided in Example 1 can refer to the aforementioned method

[0299] The relevant descriptions in Examples 200-300 achieve the same or corresponding technical effects and will not be repeated here to avoid repetition.

[0300] In addition, the task processing method provided in Example 1 may include more or fewer steps than the aforementioned S411 - S422 , which is not limited here.

[0301] Example 2

[0302] Assuming that the first network element and the subtask management function are jointly established, that is, the first network element has the ability to select the subtask function, the first network element is a TM network element, and the second network element is an AF network element, then, as shown in Figure 4b, the task processing method provided in this application may include the following steps.

[0303] S431 : The AF sends a sixth message to the TM network element, requesting the TM network element to create or formulate a task module that meets service requirements for one or more target tasks.

[0304] S432: The TM network element creates a new task template according to the sixth message.

[0305] S433: The TM network element sends a sixth response to the AF, where the sixth response includes a task template.

[0306] S434: The terminal obtains a task module from the TM network element or the AF.

[0307] S435 , the terminal fills the acquired task template and sends the filled task template to the TM network element to allocate resources for the target task.

[0308] S436: The terminal sends a first message to the TM network element, wherein the first message is used to request modification of the target task or a subtask in the target task.

[0309] S437, the TM network element verifies whether the first message is authorized or allowed. If it is authorized or allowed, execute S438; otherwise, execute S442.

[0310] S438: The TM network element disassembles or translates the first message to obtain an updated task instance.

[0311] It is worth noting that the implementation process of S433-S438 can refer to the aforementioned S433-S428, and will not be repeated here to avoid repetition.

[0312] S439 , the TM network element determines a subtask function that satisfies the subtask strategy or subtask quality information according to the task instance.

[0313] Optionally, the TM network element may query the NRF, UDM or UDR to determine the subtask function that meets the subtask policy or subtask quality information, or the TM network element may determine the subtask function that meets the subtask policy or subtask quality information based on stored or maintained subtask capabilities.

[0314] If no suitable subtask function is found, execute S422.

[0315] S440: The TM network element interacts with the subtask function to modify the subtask, such as modifying resources allocated to the subtask.

[0316] For example, if the TM network element determines that the subtasks include a sensing subtask, the TM network element sends a third message to the selected sensing function, instructing the sensing function to provide information required to execute the sensing subtask. Correspondingly, the sensing function modifies the subtask based on the third message and sends a third response to the TM network element based on the modification result, indicating the modification result of the sensing subtask, such as acceptance or rejection of the modification.

[0317] If the third response indicates that the modification result is rejection, the TM network element may again select a sensing function that can perform the sensing subtask.

[0318] For another example, if the TM network element determines that the subtask includes a computing subtask, the TM network element sends a third message to the selected computing function, instructing the computing function to provide information required to execute the computing subtask. Correspondingly, the computing function modifies the subtask based on the third message and, based on the modification result, sends a third response to the TM network element, indicating the modification result of the computing subtask, such as acceptance or rejection of the modification. If the third response indicates a rejection, the TM network element may select another computing function capable of executing the computing subtask.

[0319] Optionally, if the third response indicates that the modification result is accepted, the third response may also include computing power information of the computing function (such as computing power size, computing power type, etc.).

[0320] For another example, if the TM network element determines that the subtask includes an AI subtask, the TM network element sends a third message to the selected AI function, indicating the information required for the AI ​​function to execute the AI ​​subtask. Correspondingly, the AI ​​function modifies the subtask based on the third message and, based on the modification result, sends a third response to the TM network element, indicating the modification result of the AI ​​subtask, such as acceptance or rejection of the modification. If the third response indicates a rejection, the TM network element may select another AI function capable of executing the AI ​​subtask.

[0321] Optionally, if the third response indicates that the modification result is accepted, the third response may also include an AI model acquisition address, an AI model training address, etc.

[0322] S441 : The TM network element modifies at least a portion of the task context of the target task to record the relationship between the task requirement information and the updated task instance.

[0323] S442: The TM network element sends a first response to the terminal to indicate a modification result of the target task or a subtask in the target task.

[0324] It is worth noting that the implementation process of each step of the task processing method provided in Example 2 can refer to the relevant descriptions in the aforementioned method embodiments 200-300, and achieve the same or corresponding technical effects. To avoid repetition, they are not described here. In addition, the task processing method provided in Example 2 may include more or fewer steps than the aforementioned S431-S442, without limitation here.

[0325] Example 3

[0326] Assuming that the first network element and the subtask management function are deployed independently, the first network element is a TM network element and the second network element is an AF, then, as shown in FIG4c , the task processing method provided in this application may include the following steps.

[0327] S451 , when the AF determines that a modification operation needs to be performed on the target task or a subtask in the target task, the AF translates or decomposes the task to obtain an updated task instance.

[0328] Optionally, when a second condition is met, the AF determines that a modification operation needs to be performed on the target task or a subtask in the target task, wherein the second condition includes at least one of the following conditions 1-2.

[0329] Condition 1: The terminal's task contract changes.

[0330] Condition 2: The AF receives a task modification request from the terminal through the application layer, where the task modification request is used to request modification of a target task or a subtask in the target task.

[0331] S452: The AF sends a fourth message to the terminal according to the updated task instance, where the fourth message carries relevant information of the updated task instance.

[0332] S453: The terminal sends the first message to the first network element according to the fourth message, where the first message is used to request modification of the target task or a subtask in the target task.

[0333] S454, the TM network element verifies whether the first message is authorized or allowed. If it is authorized or allowed, execute S455; otherwise, execute S458.

[0334] S455: The TM network element sends a second message to the subtask management function according to the task instance, where the second message is used to request modification of the subtask in the target task.

[0335] S456: The TM network element receives a second response sent by the subtask management function, where the second response is used to indicate a modification result of the subtask.

[0336] S457 , the TM network element modifies at least a portion of the task context of the target task to record the relationship between the task requirement information and the updated task instance.

[0337] S458: The TM network element sends a first response to the terminal to indicate a modification result of the target task or a subtask in the target task.

[0338] It is worth noting that the difference between this example 3 and the aforementioned example 1 is that in this example 3, the AF performs task translation or disassembly to obtain the updated task, and then through application layer interaction, the terminal obtains the updated task instance from the AF and initiates a task modification request, that is, the first message.

[0339] Example 4

[0340] Assuming that the first network element and the subtask management function are jointly provided, the first network element is a TM network element and the second network element is an AF, then, as shown in FIG4d , the task processing method provided in the present application may include the following steps.

[0341] S461: When the AF determines that a modification operation needs to be performed on the target task or a subtask in the target task, the AF translates or decomposes the task to obtain an updated task instance.

[0342] Optionally, when a second condition is met, the AF determines that a modification operation needs to be performed on the target task or a subtask in the target task, wherein the second condition includes at least one of the following conditions 1-2.

[0343] Condition 1: The terminal's task contract changes.

[0344] Condition 2: The AF receives a task modification request from the terminal through the application layer, where the task modification request is used to request modification of a target task or a subtask in the target task.

[0345] S462: The AF sends a fourth message to the terminal according to the updated task instance, where the fourth message carries relevant information of the updated task instance.

[0346] S463: The terminal sends the first message to the first network element according to the fourth message, where the first message is used to request modification of the target task or a subtask in the target task.

[0347] S464, the TM network element verifies whether the first message is authorized or allowed. If it is authorized or allowed, execute S465; otherwise, execute S468.

[0348] S465 , the TM network element determines a subtask function that satisfies the subtask strategy or subtask quality information according to the task instance.

[0349] S466: The TM network element interacts with the subtask function to modify the subtask, such as modifying the resources allocated to the subtask.

[0350] S467 , the TM network element modifies at least a portion of the task context of the target task to record the relationship between the task requirement information and the updated task instance.

[0351] S468: The TM network element sends a first response to the terminal to indicate a modification result of the target task or a subtask in the target task.

[0352] The difference between this example 4 and the above example 2 is that in this example 4, the AF performs task translation or disassembly, and then through application layer interaction, the terminal obtains an updated task instance from the AF and initiates a task modification request, that is, the first message.

[0353] Example 5

[0354] Assume that the terminal has only signed up for communication services, but the task requested by the terminal includes both communication subtasks and computing subtasks. Then, when the TM network element receives this type of task request (ie, the first message), the TM network element needs to dynamically request the AF for the demand information of the computing subtask.

[0355] In this regard, assuming that the first network element and the subtask management function are deployed independently, and the first network element is a TM network element and the second network element is an AF network element, as shown in Figure 4e, the task processing method provided in this application may include the following steps.

[0356] S471 : The AF sends a sixth message to the TM network element, requesting the TM network element to create or formulate a task module that meets service requirements for one or more target tasks.

[0357] S472: The TM network element creates a new task template according to the sixth message.

[0358] S473: The TM network element sends a sixth response to the AF, where the sixth response includes a task template.

[0359] S474: The terminal obtains a task module from the TM network element or the AF.

[0360] S475 , the terminal fills the acquired task template and sends the filled task template to the TM network element to allocate resources for the target task.

[0361] S476: The terminal sends a first message to the TM network element, wherein the first message is used to request modification of the target task or a subtask in the target task.

[0362] S477, the TM network element verifies whether the first message is authorized or allowed. If it is authorized or allowed, execute S478; otherwise, execute S422.

[0363] S478: The TM network element disassembles or translates the first message to obtain an updated task instance.

[0364] It is worth noting that the implementation process of S471-S478 can refer to the aforementioned S417-S418, and will not be repeated here to avoid repetition.

[0365] S479: The TM network element determines, based on the updated task instance, that the task type of the target task is a combined task, but the task type contracted by the terminal is a single task, i.e., the two are inconsistent. Then, the TM network element sends a fifth message to the AF, where the fifth message is used to request subtask requirement information corresponding to the target task.

[0366] S480: The AF sends a fifth response to the TM network element according to the fifth message, where the fifth response carries the subtask requirement information.

[0367] S481: The TM network element sends a second message to the subtask management function according to the fifth response and the task instance, where the second message is used to request modification of the subtask in the target task.

[0368] S482: The TM network element receives a second response sent by the subtask management function, where the second response is used to indicate a modification result of the subtask.

[0369] S483: The TM network element modifies at least a portion of the task context of the target task to record the relationship between the task requirement information and the updated task instance.

[0370] S484: The TM network element sends a first response to the terminal to indicate a modification result of the target task or a subtask in the target task.

[0371] The difference between Example 5 and Example 1 is that in Example 5, the TM network element performs task translation or decomposition according to the task modification request (ie, the first message) sent by the terminal, and dynamically determines subtask requirement information to the AF.

[0372] It is worth noting that the implementation process of each step of the task processing method provided in Example 5 can refer to the relevant descriptions in the aforementioned method embodiments 200-300, and achieve the same or corresponding technical effects. To avoid repetition, they are not described here. In addition, the task processing method provided in Example 2 may include more or fewer steps than the aforementioned S471-S484, without limitation here.

[0373] Figure 5 is a flowchart of a task processing method 500 provided in an exemplary embodiment of the present application. This method 500 may be, but is not limited to, executed by a first network element, specifically by at least one of hardware and software installed in the first network element. In this embodiment, the method 500 may include at least the following steps.

[0374] S510: A first network element receives a first message from a terminal, wherein the first message is used to request modification of a target task or a subtask in the target task.

[0375] S520: The first network element modifies the target task or a subtask in the target task according to the first message;

[0376] S530: The first network element sends a first response to the terminal, where the first response is used to indicate a modification result of the target task or a subtask in the target task.

[0377] In one possible implementation, the first message includes at least one of the following: a terminal identifier; a task template, used to indicate the task requirements corresponding to the requested target task; a data network name DNN, used to indicate the DNN corresponding to the requested target task; single network slice selection auxiliary information S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; a task identifier or a task session identifier, used to identify the requested target task; a subtask identifier or a subtask session identifier, used to identify the subtask in the requested target task.

[0378] In one possible implementation, the task template includes at least one of the following: task description information, used to indicate the task information of the target task or application information of the task parameters; task service experience QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task; task strategy or task quality information, used to indicate the task strategy or task quality corresponding to the requested target task; subtask strategy or subtask quality information, used to indicate the service quality requirement corresponding to the subtask in the requested target task.

[0379] In one possible implementation, the first network element modifies the target task or the subtask in the target task according to the first message, including: the first network element determines an updated task instance according to the first message, and the task instance is used to indicate relevant parameters assigned to the target task; and modifies the target task or the subtask in the target task according to the task instance.

[0380] In one possible implementation, modifying the target task or the subtasks in the target task according to the task instance includes at least one of the following: updating the resources corresponding to the subtasks in the target task according to the task instance; adding subtasks in the target task according to the task instance; deleting at least some of the subtasks in the target task according to the task instance.

[0381] In one possible implementation, modifying the target task or the subtask in the target task according to the task instance includes: the first network element sends a second message to the subtask management function according to the task instance, and the second message is used to request modification of the subtask in the target task; the first network element receives a second response sent by the subtask management function, and the second response is used to indicate the modification result of the subtask.

[0382] In one possible implementation, modifying the target task or the subtask in the target task according to the task instance includes: the first network element determines a subtask function that satisfies the subtask policy or subtask quality information in the task instance; the first network element sends a third message to the subtask function according to the task instance, and the third message is used to request the subtask function to modify the subtask in the target task; the first network element receives a third response sent by the subtask function, and the third response is used to indicate the modification result of the subtask.

[0383] In a possible implementation, the second message or the third message includes at least one of the following: identification or address information of the first network element; subtask strategy or subtask quality information; subtask execution order; and identification of the subtask.

[0384] In one possible implementation, when the second response or the third response indicates that the modification result of the subtask is accepted, the second response or the third response includes at least one of the following: the Internet Protocol IP address of the subtask function; the identification ID of the subtask function; the fully qualified domain name FQDN of the subtask function.

[0385] In one possible implementation, the second response or the third response further satisfies at least one of the following: when the subtask is a computing subtask, the second response or the third response includes computing power information of the subtask function; when the subtask is an AI subtask, the second response or the third response also includes at least one of an AI model acquisition address and an AI model training address.

[0386] In a possible implementation, modifying the target task or the subtask in the target task according to the task instance also includes: the first network element modifies the task context of the target task to record the relationship between the task requirement information of the target task and the updated task instance.

[0387] In one possible implementation, the first network element modifies the target task or the subtask in the target task according to the first message, and also includes: when the first network element determines based on the updated task instance that the task type of the target task is inconsistent with the task type contracted by the terminal, the first network element sends a fifth message to the second network element, and the fifth message is used to request the subtask requirement information corresponding to the target task; the first network element receives the fifth response sent by the second network element, and the fifth response is used to indicate the subtask requirement information corresponding to the target task.

[0388] In one possible implementation, the method further includes: the first network element verifies whether the first message is allowed or authorized; if the first message is allowed or authorized, the first network element executes the step of modifying the target task or the subtask in the target task according to the first message.

[0389] In a possible implementation, the first network element verifies whether the first message is allowed or authorized, including: the first network element verifies whether the first message is allowed or authorized based on the task identifier and the terminal identifier carried in the first message.

[0390] In one possible implementation, when the first response indicates that the modification result is accepted, the first response includes at least one of the following: a task identifier, used to indicate the target task; a subtask management function identifier or a subtask function identifier, the subtask function identifier is used to indicate the subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate the subtask function for executing subtasks in the target task; task strategy or task quality information; subtask strategy or subtask quality information; subtask execution order.

[0391] In a possible implementation, when the first response indicates that the modification result is rejection, the first response includes a rejection reason.

[0392] In a possible implementation, the rejection reason includes at least one of the following: network congestion; the target task or a subtask in the target task is not allowed to be modified; the terminal is not allowed or authorized; and subtask resources are insufficient.

[0393] In one possible implementation, the subtasks include at least one of the following: a perception subtask; a computing subtask; an artificial intelligence (AI) subtask; a data subtask; a positioning subtask; an Internet Protocol Multimedia System (IMS) subtask; and a communication subtask.

[0394] It is worth noting that since each implementation method in method embodiment 500 has the same or corresponding technical features as the aforementioned method embodiment 200 or 300, the implementation process of each implementation method in method embodiment 500 can refer to the relevant description of the aforementioned method embodiment 200 or 300, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0395] Figure 6 is a flowchart of a task processing method 600 provided in an exemplary embodiment of the present application. This method 600 may be, but is not limited to, executed by a second network element, specifically by at least one of hardware and software installed in the second network element. In this embodiment, the method 600 may include at least one of the following steps S610 and S620.

[0396] S610, the second network element sends a fourth message to the terminal, where the fourth message is used to instruct or request modification of a target task or a subtask in the target task;

[0397] S620, the second network element receives the fifth message sent by the first network element, the fifth message is used to request the subtask requirement information corresponding to the target task, and sends a fifth response to the first network element, the fifth response is used to indicate the subtask requirement information corresponding to the target task.

[0398] In one possible implementation, the method further includes: when a second condition is met, the second network element executes the step of sending a fourth message to the terminal; wherein the second condition includes at least one of the following: the task contract of the terminal changes; the second network element receives a task modification request from the terminal, and the task modification request is used to request modification of the target task or a subtask in the target task.

[0399] In a possible implementation, the second network element sends the fourth message to the terminal, including: the second network element performs task translation or disassembly to obtain an updated task instance; and sends the fourth message to the terminal according to the updated task instance.

[0400] In one possible implementation, the fourth message includes at least one of the following: task description information, used to indicate the task information of the target task or application information of the task parameters; DNN, used to indicate the DNN corresponding to the requested target task; S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; task policy or task quality information, used to indicate the service quality requirements corresponding to the requested target task; task identifier or task session identifier, used to identify the requested target task; subtask identifier or subtask session identifier, used to identify the subtask in the requested target task; subtask policy or subtask quality information, used to indicate the service quality requirements corresponding to the subtask in the requested target task.

[0401] In one possible implementation, the subtasks include at least one of the following: a perception subtask; a computing subtask; an artificial intelligence (AI) subtask; a data subtask; a positioning subtask; an Internet Protocol Multimedia System (IMS) subtask; and a communication subtask.

[0402] It is worth noting that since each implementation method in method embodiment 600 has the same or corresponding technical features as the aforementioned method embodiment 200 or 300, the implementation process of each implementation method in method embodiment 600 can refer to the relevant description of the aforementioned method embodiment 200 or 300 and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0403] 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.

[0404] As shown in Figure 7, it is a structural diagram of a task processing device 700 provided in an embodiment of the present application. The device 700 includes: a sending module 710, used to send a first message to a first network element, wherein the first message is used to request modification of a target task or a subtask in the target task; and a receiving module 720, used to receive a first response from the first network element, wherein the first response is used to indicate a modification result of the target task or a subtask in the target task.

[0405] In one possible implementation, the first message includes at least one of the following: a terminal identifier; a task template, used to indicate task requirement information corresponding to the requested target task; a data network name DNN, used to indicate the DNN corresponding to the requested target task; single network slice selection auxiliary information S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; a task identifier or a task session identifier, used to identify the requested target task; a subtask identifier or a subtask session identifier, used to identify the subtask in the requested target task.

[0406] In one possible implementation, the task template includes at least one of the following: task description information, used to indicate the task information of the target task or application information of the task parameters; task service experience QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task; task strategy or task quality information, used to indicate the task strategy or task quality corresponding to the requested target task; subtask strategy or subtask quality information, used to indicate the service quality requirement corresponding to the subtask in the requested target task.

[0407] In one possible implementation, the sending of the first message to the first network element includes: sending the first message to the first network element when it is determined that a first condition is met; wherein the first condition includes at least one of the following: the task requirement information of the terminal changes; the terminal expects to modify the target task or a subtask in the target task; the terminal turns on power saving mode or the battery level of the terminal is lower than a first threshold; the terminal moves; the terminal obtains a fourth message from the second network element, and the fourth message is used to indicate or request modification of the target task or a subtask in the target task; the task contract of the terminal changes.

[0408] In one possible implementation, the first message further satisfies at least one of the following: when the first condition includes that the terminal has turned on the power saving mode or the battery level of the terminal is lower than a first threshold, the first message further includes a first indication for indicating the battery status of the terminal; when the first condition includes that the terminal has moved, the first message further includes the location information of the terminal after the movement.

[0409] In one possible implementation, when the first response indicates that the modification result is accepted, the first response includes at least one of the following: a task identifier, used to indicate the target task; a subtask management function identifier or a subtask function identifier, the subtask function identifier is used to indicate the subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate the subtask function for executing subtasks in the target task; task strategy or task quality information; subtask strategy or subtask quality information; subtask execution order.

[0410] In a possible implementation, when the first response indicates that the modification result is rejection, the first response includes a rejection reason.

[0411] In a possible implementation, the rejection reason includes at least one of the following: network congestion; the target task or a subtask in the target task is not allowed to be modified; the terminal is not allowed or authorized; and subtask resources are insufficient.

[0412] In one possible implementation, the subtasks include at least one of the following: a perception subtask; a computing subtask; an artificial intelligence (AI) subtask; a data subtask; a positioning subtask; an Internet Protocol Multimedia System (IMS) subtask; and a communication subtask.

[0413] The task processing device 700 in the embodiment 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 terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0414] The task device 700 provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 3 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0415] As shown in Figure 8, which is a structural diagram of a task processing device 800 provided in an embodiment of the present application, the device 800 includes: a receiving module 810, used to receive a first message from a terminal, wherein the first message is used to request modification of a target task or a subtask in the target task; a task modification module 820, used to modify the target task or the subtask in the target task according to the first message; and a sending module 830, used to send a first response to the terminal, wherein the first response is used to indicate a modification result of the target task or the subtask in the target task.

[0416] In one possible implementation, the first message includes at least one of the following: a terminal identifier; a task template, used to indicate the task requirements corresponding to the requested target task; a data network name DNN, used to indicate the DNN corresponding to the requested target task; single network slice selection auxiliary information S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; a task identifier or a task session identifier, used to identify the requested target task; a subtask identifier or a subtask session identifier, used to identify the subtask in the requested target task.

[0417] In one possible implementation, the task template includes at least one of the following: task description information, used to indicate the task information of the target task or application information of the task parameters; task service experience QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task; task strategy or task quality information, used to indicate the task strategy or task quality corresponding to the requested target task; subtask strategy or subtask quality information, used to indicate the service quality requirement corresponding to the subtask in the requested target task.

[0418] In one possible implementation, modifying the target task or the subtask in the target task according to the first message includes: determining an updated task instance according to the first message, the task instance being used to indicate relevant parameters assigned to the target task; and modifying the target task or the subtask in the target task according to the task instance.

[0419] In one possible implementation, modifying the target task or the subtasks in the target task according to the task instance includes at least one of the following: updating the resources corresponding to the subtasks in the target task according to the task instance; adding subtasks in the target task according to the task instance; deleting at least some of the subtasks in the target task according to the task instance.

[0420] In one possible implementation, modifying the target task or the subtask in the target task according to the task instance includes: sending a second message to the subtask management function according to the task instance, the second message being used to request modification of the subtask in the target task; and receiving a second response sent by the subtask management function, the second response being used to indicate the modification result of the subtask.

[0421] In one possible implementation, modifying the target task or the subtask in the target task according to the task instance includes: determining a subtask function that satisfies the subtask strategy or subtask quality information in the task instance; sending a third message to the subtask function according to the task instance, the third message being used to request the subtask function to modify the subtask in the target task; and receiving a third response sent by the subtask function, the third response being used to indicate the modification result of the subtask.

[0422] In a possible implementation, the second message or the third message includes at least one of the following: identification or address information of the first network element; subtask strategy or subtask quality information; subtask execution order; and identification of the subtask.

[0423] In one possible implementation, when the second response or the third response indicates that the modification result of the subtask is accepted, the second response or the third response includes at least one of the following: the Internet Protocol IP address of the subtask function; the identification ID of the subtask function; the fully qualified domain name FQDN of the subtask function.

[0424] In one possible implementation, the second response or the third response further satisfies at least one of the following: when the subtask is a computing subtask, the second response or the third response includes computing power information of the subtask function; when the subtask is an AI subtask, the second response or the third response also includes at least one of an AI model acquisition address and an AI model training address.

[0425] In a possible implementation, modifying the target task or a subtask in the target task according to the task instance further includes: modifying the task context of the target task to record the relationship between the task requirement information of the target task and the updated task instance.

[0426] In one possible implementation, modifying the target task or the subtask in the target task according to the first message also includes: when it is determined according to the updated task instance that the task type of the target task is inconsistent with the task type contracted by the terminal, sending a fifth message to the second network element, the fifth message being used to request subtask requirement information corresponding to the target task; and receiving a fifth response sent by the second network element, the fifth response being used to indicate the subtask requirement information corresponding to the target task.

[0427] In one possible implementation, the task modification module 820 is further used to: verify whether the first message is allowed or authorized; and if the first message is allowed or authorized, execute the step of modifying the target task or the subtask in the target task according to the first message.

[0428] In a possible implementation, verifying whether the first message is allowed or authorized includes: verifying whether the first message is allowed or authorized according to the task identifier and the terminal identifier carried in the first message.

[0429] In one possible implementation, when the first response indicates that the modification result is accepted, the first response includes at least one of the following: a task identifier, used to indicate the target task; a subtask management function identifier or a subtask function identifier, the subtask function identifier is used to indicate the subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate the subtask function for executing subtasks in the target task; task strategy or task quality information; subtask strategy or subtask quality information; subtask execution order.

[0430] In a possible implementation, when the first response indicates that the modification result is rejection, the first response includes a rejection reason.

[0431] In a possible implementation, the rejection reason includes at least one of the following: network congestion; the target task or a subtask in the target task is not allowed to be modified; the terminal is not allowed or authorized; and subtask resources are insufficient.

[0432] In one possible implementation, the subtasks include at least one of the following: a perception subtask; a computing subtask; an artificial intelligence (AI) subtask; a data subtask; a positioning subtask; an Internet Protocol Multimedia System (IMS) subtask; and a communication subtask.

[0433] The task processing device 800 in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a network-side device or other device other than a terminal. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above, and is not specifically limited in the embodiments of the present application.

[0434] The task processing device 800 provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0435] As shown in Figure 9, it is a structural diagram of a task processing device 900 provided in an embodiment of the present application. The device 900 includes a transmission module 910, which is used to send a fourth message to the terminal, and the fourth message is used to indicate or request modification of the target task or a subtask in the target task; or the transmission module 910 is used to receive a fifth message sent by a first network element, and the fifth message is used to request subtask requirement information corresponding to the target task, and to send a fifth response to the first network element, and the fifth response is used to indicate the subtask requirement information corresponding to the target task.

[0436] In one possible implementation, the transmission module 910 is also used to execute the step of sending a fourth message to the terminal when a second condition is met; wherein the second condition includes at least one of the following: the task contract of the terminal changes; the second network element receives a task modification request from the terminal, and the task modification request is used to request modification of the target task or a subtask in the target task.

[0437] In a possible implementation, the sending the fourth message to the terminal includes: performing task translation or decomposition to obtain an updated task instance; and sending the fourth message to the terminal according to the updated task instance.

[0438] In one possible implementation, the fourth message includes at least one of the following: task description information, used to indicate the task information of the target task or application information of the task parameters; DNN, used to indicate the DNN corresponding to the requested target task; S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; task policy or task quality information, used to indicate the service quality requirements corresponding to the requested target task; task identifier or task session identifier, used to identify the requested target task; subtask identifier or subtask session identifier, used to identify the subtask in the requested target task; subtask policy or subtask quality information, used to indicate the service quality requirements corresponding to the subtask in the requested target task.

[0439] In one possible implementation, the subtasks include at least one of the following: a perception subtask; a computing subtask; an artificial intelligence (AI) subtask; a data subtask; a positioning subtask; an Internet Protocol Multimedia System (IMS) subtask; and a communication subtask.

[0440] The task processing device 900 in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a network-side device or other device other than a terminal. For example, the network-side device can include, but is not limited to, the types of network-side devices 12 listed above, and is not specifically limited in the embodiments of the present application.

[0441] The task processing device 900 provided in the embodiment of the present application can implement each process implemented in the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0442] As shown in Figure 10, an embodiment of the present application further provides a communication device 1000, including a processor 1001 and a memory 1002. The memory 1002 stores a program or instruction that can be run on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned task processing method embodiment 200 or 300 or 500 or 600, and can achieve the same technical effect. When the communication device 1000 is a network-side device, the program or instruction is executed by the processor 1001 to implement the various steps of the above-mentioned task processing method embodiment 200 or 300 or 500 or 600, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0443] 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 of the method embodiments shown in Figures 2 and 3. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment can be applied to this terminal embodiment and achieve the same technical effects. Specifically, Figure 11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0444] The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109 and at least some of the components of the processor 1110.

[0445] Those skilled in the art will appreciate that the terminal 1100 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0446] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 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 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and at least one of other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 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.

[0447] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1101 may transmit the data to the processor 1110 for processing. Furthermore, the RF unit 1101 may send uplink data to the network-side device. Typically, the RF unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0448] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 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.). In addition, the memory 1109 may include a volatile memory or a non-volatile memory. 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 1109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0449] Processor 1110 may include one or more processing units. Optionally, processor 1110 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 1110.

[0450] Among them, the radio frequency unit 1101 is used to send a first message to the first network element, where the first message is used to request modification of the target task or a subtask in the target task; and to receive a first response from the first network element, where the first response is used to indicate the modification result of the target task or the subtask in the target task.

[0451] In one possible implementation, the first message includes at least one of the following: a terminal identifier; a task template, used to indicate task requirement information corresponding to the requested target task; a data network name DNN, used to indicate the DNN corresponding to the requested target task; single network slice selection auxiliary information S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; a task identifier or a task session identifier, used to identify the requested target task; a subtask identifier or a subtask session identifier, used to identify the subtask in the requested target task.

[0452] In one possible implementation, the task template includes at least one of the following: task description information, used to indicate the task information of the target task or application information of the task parameters; task service experience QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task; task strategy or task quality information, used to indicate the task strategy or task quality corresponding to the requested target task; subtask strategy or subtask quality information, used to indicate the service quality requirement corresponding to the subtask in the requested target task.

[0453] In one possible implementation, the sending of the first message to the first network element includes: the terminal sending the first message to the first network element when determining that a first condition is met; wherein the first condition includes at least one of the following: the task requirement information of the terminal changes; the terminal expects to modify the target task or a subtask in the target task; the terminal turns on the power saving mode or the battery level of the terminal is lower than a first threshold; the terminal moves; the terminal obtains a fourth message from the second network element, and the fourth message is used to indicate or request modification of the target task or a subtask in the target task; the task contract of the terminal changes.

[0454] In one possible implementation, the first message further satisfies at least one of the following: when the first condition includes that the terminal has turned on the power saving mode or the battery level of the terminal is lower than a first threshold, the first message further includes a first indication for indicating the battery status of the terminal; when the first condition includes that the terminal has moved, the first message further includes the location information of the terminal after the movement.

[0455] In one possible implementation, when the first response indicates that the modification result is accepted, the first response includes at least one of the following: a task identifier, used to indicate the target task; a subtask management function identifier or a subtask function identifier, the subtask function identifier is used to indicate the subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate the subtask function for executing subtasks in the target task; task strategy or task quality information; subtask strategy or subtask quality information; subtask execution order.

[0456] In a possible implementation, when the first response indicates that the modification result is rejection, the first response includes a rejection reason.

[0457] In a possible implementation, the rejection reason includes at least one of the following: network congestion; the target task or a subtask in the target task is not allowed to be modified; the terminal is not allowed or authorized; and subtask resources are insufficient.

[0458] In one possible implementation, the subtasks include at least one of the following: a perception subtask; a computing subtask; an artificial intelligence (AI) subtask; a data subtask; a positioning subtask; an Internet Protocol Multimedia System (IMS) subtask; and a communication subtask.

[0459] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiments 200-300, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0460] The present application also provides a network-side device, 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 of the method embodiment shown in Figure 5 or Figure 6. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0461] Specifically, the embodiment of the present application further provides a network side device. As shown in FIG12 , the network side device 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network interface 1202 is, for example, a common public radio interface (CPRI).

[0462] Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 1203 and executable on the processor 1201. The processor 1201 calls the instructions or programs in the memory 1203 to execute the methods executed by the modules shown in FIG. 7 or FIG. 8 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0463] 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.

[0464] 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.

[0465] 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.

[0466] 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.

[0467] 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.

[0468] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the various processes of the above task processing method embodiments 200-300, and the network-side device can be used to execute the various processes of the above task processing method embodiments 500 or 600, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0469] 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.

[0470] 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.

[0471] 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 terminal sends a first message to the first network element, where the first message is used to request modification of a target task or a subtask in the target task; The terminal receives a first response from the first network element, where the first response is used to indicate a modification result of the target task or a subtask in the target task.

2. The method according to claim 1, wherein The first message includes at least one of the following: Terminal identification; A task template, used to indicate task requirement information corresponding to the requested target task; Data network name DNN, used to indicate the DNN corresponding to the requested target task; Single network slice selection assistance information S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; A task identifier or a task session identifier, used to identify the target task requested; The subtask identifier or subtask session identifier is used to identify the subtask in the requested target task.

3. The method according to claim 2, wherein: The task template includes at least one of the following: Task description information, used to indicate the task information of the target task or application information of task parameters; Task service experience QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task; Task strategy or task quality information, used to indicate the task strategy or task quality corresponding to the requested target task; The subtask strategy or subtask quality information is used to indicate the service quality requirement corresponding to the subtask in the requested target task.

4. The method according to any one of claims 1 to 3, wherein The terminal sending a first message to the first network element includes: When the terminal determines that the first condition is met, sending the first message to the first network element; The first condition includes at least one of the following: The task requirement information of the terminal changes; The terminal desires to modify the target task or a subtask in the target task; The terminal turns on the power saving mode or the battery level of the terminal is lower than a first threshold; The terminal moves; The terminal obtains a fourth message from the second network element, where the fourth message is used to instruct or request modification of the target task or a subtask in the target task; The task contract of the terminal changes.

5. The method according to claim 4, wherein: The first message further satisfies at least one of the following: When the first condition includes that the terminal has activated a power saving mode or the battery level of the terminal is lower than a first threshold, the first message further includes a first indication for indicating the battery level of the terminal; In a case where the first condition includes movement of the terminal, the first message further includes location information of the terminal after movement.

6. The method according to any one of claims 1 to 5, wherein When the first response indicates that the modification result is accepted, the first response includes at least one of the following: A task identifier, used to indicate the target task; A subtask management function identifier or a subtask function identifier, wherein the subtask function identifier is used to indicate a subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate a subtask function for executing subtasks in the target task; mission strategy or mission quality information; Subtask strategy or subtask quality information; Subtask execution order.

7. The method according to any one of claims 1 to 5, wherein In the case where the first response indicates that the modification result is rejection, the first response includes a rejection reason.

8. The method of claim 7, wherein: The reason for rejection includes at least one of the following: Network congestion; The target task or the subtasks within the target task are not allowed to be modified; The terminal is not allowed or authorized; Insufficient resources for subtask.

9. The method according to any one of claims 1 to 8, wherein The subtasks include at least one of the following: Perception subtask; Compute subtasks; Artificial intelligence AI subtasks; Data subtask; Positioning subtasks; Internet Protocol Multimedia System IMS subtask; Communication subtask.

10. A task processing method, comprising: The first network element receives a first message from the terminal, wherein the first message is used to request modification of a target task or a subtask in the target task; The first network element modifies the target task or a subtask in the target task according to the first message; The first network element sends a first response to the terminal, where the first response is used to indicate a modification result of the target task or a subtask in the target task.

11. The method according to claim 10, wherein: The first message includes at least one of the following: Terminal identification; A task template, used to indicate the task requirements corresponding to the requested target task; Data network name DNN, used to indicate the DNN corresponding to the requested target task; Single network slice selection assistance information S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; A task identifier or a task session identifier, used to identify the target task requested; The subtask identifier or subtask session identifier is used to identify the subtask in the requested target task.

12. The method of claim 11, wherein: The task template includes at least one of the following: Task description information, used to indicate the task information of the target task or application information of task parameters; Task service experience QoE requirement information, used to indicate the QoE requirement corresponding to the requested target task; Task strategy or task quality information, used to indicate the task strategy or task quality corresponding to the requested target task; The subtask strategy or subtask quality information is used to indicate the service quality requirement corresponding to the subtask in the requested target task.

13. The method according to any one of claims 10 to 12, wherein The first network element modifies the target task or a subtask in the target task according to the first message, including: The first network element determines, according to the first message, an updated task instance, where the task instance is used to indicate relevant parameters allocated to the target task; The first network element modifies the target task or a subtask in the target task according to the task instance.

14. The method of claim 13, wherein: Modifying the target task or a subtask in the target task includes at least one of the following: Update the resources corresponding to the subtasks in the target task; Adding subtasks to the target task; Delete at least some of the subtasks in the target task.

15. The method according to any one of claims 11 to 14, wherein The first network element modifies the target task or a subtask in the target task according to the task instance, including: The first network element sends a second message to the subtask management function according to the task instance, where the second message is used to request modification of the subtask in the target task; The first network element receives a second response sent by the subtask management function, where the second response is used to indicate a modification result of the subtask.

16. The method according to any one of claims 11 to 14, wherein The first network element modifies the target task or a subtask in the target task according to the task instance, including: The first network element determines a subtask function that satisfies a subtask strategy or subtask quality information in the task instance; The first network element sends a third message to the subtask function according to the task instance, wherein the third message is used to request the subtask function to modify the subtask in the target task; The first network element receives a third response sent by the subtask function, where the third response is used to indicate a modification result of the subtask.

17. The method according to claim 15 or 16, wherein The second message or the third message includes at least one of the following: the identifier or address information of the first network element; Subtask strategy or subtask quality information; Subtask execution order; The identifier of the subtask.

18. The method of claim 15, wherein: When the second response or the third response indicates that the modification result of the subtask is accepted, the second response includes at least one of the following: The Internet Protocol (IP) address of the subtask function; The identification ID of the subtask function; The fully qualified domain name (FQDN) of the subtask function.

19. The method according to claim 16 or 18, wherein The second response or the third response satisfies at least one of the following: In the case where the subtask is a computing subtask, the second response or the third response includes computing power information of the subtask function; When the subtask is an AI subtask, the second response or the third response includes at least one of an AI model acquisition address and an AI model training address.

20. The method according to any one of claims 11 to 19, wherein The first network element modifies the target task or a subtask in the target task according to the task instance, further comprising: The first network element modifies the task context of the target task to record the relationship between the task requirement information of the target task and the updated task instance.

21. The method according to any one of claims 10 to 20, wherein The first network element modifies the target task or a subtask in the target task according to the first message, further comprising: When the first network element determines, based on the updated task instance, that the task type of the target task is inconsistent with the task type contracted by the terminal, the first network element sends a fifth message to the second network element, wherein the fifth message is used to request subtask requirement information corresponding to the target task; The first network element receives a fifth response sent by the second network element, where the fifth response is used to indicate subtask requirement information corresponding to the target task.

22. The method of any one of claims 10 to 21, wherein The method further comprises: Verifying, by the first network element, whether the first message is allowed or authorized; In a case where the first message is allowed or authorized, the first network element executes the step of modifying the target task or a subtask in the target task according to the first message.

23. The method of claim 22, wherein: The first network element verifying whether the first message is allowed or authorized includes: The first network element verifies whether the first message is allowed or authorized according to the task identifier and the terminal identifier carried in the first message.

24. The method of any one of claims 10 to 23, wherein When the first response indicates that the modification result is accepted, the first response includes at least one of the following: A task identifier, used to indicate the target task; A subtask management function identifier or a subtask function identifier, wherein the subtask function identifier is used to indicate a subtask management function for managing subtasks in the target task, and the subtask function identifier is used to indicate a subtask function for executing subtasks in the target task; mission strategy or mission quality information; Subtask strategy or subtask quality information; Subtask execution order.

25. The method of any one of claims 10 to 23, wherein In the case where the first response indicates that the modification result is rejection, the first response includes a rejection reason.

26. The method of claim 25, wherein: The reason for rejection includes at least one of the following: Network congestion; The target task or the subtasks within the target task are not allowed to be modified; The terminal is not allowed or authorized; Insufficient resources for subtask.

27. The method of any one of claims 9 to 26, wherein The subtasks include at least one of the following: Perception subtask; Compute subtasks; Artificial intelligence AI subtasks; Data subtask; Positioning subtasks; Internet Protocol Multimedia System IMS subtask; Communication subtask.

28. A task processing method comprising at least one of the following: The second network element sends a fourth message to the terminal, where the fourth message is used to instruct or request modification of the target task or a subtask in the target task; The second network element receives the fifth message sent by the first network element, where the fifth message is used to request subtask requirement information corresponding to the target task, and sends a fifth response to the first network element, where the fifth response is used to indicate the subtask requirement information corresponding to the target task.

29. The method of claim 28, wherein: The method further comprises: When the second condition is met, the second network element executes the step of sending a fourth message to the terminal; The second condition includes at least one of the following: The task contract of the terminal changes; The second network element receives a task modification request from the terminal, where the task modification request is used to request modification of the target task or a subtask in the target task.

30. The method of claim 28, wherein The second network element sending a fourth message to the terminal includes: The second network element performs task translation or decomposition to obtain an updated task instance; The fourth message is sent to the terminal according to the updated task instance.

31. The method of claim 30, wherein: The fourth message includes at least one of the following: Task description information, used to indicate the task information of the target task or application information of task parameters; DNN, used to indicate the DNN corresponding to the requested target task; S-NSSAI, used to indicate the S-NSSAI corresponding to the requested target task; Task strategy or task quality information, used to indicate the service quality requirements corresponding to the requested target task; A task identifier or a task session identifier, used to identify the target task requested; A subtask identifier or a subtask session identifier, used to identify a subtask in the target task requested; The subtask strategy or subtask quality information is used to indicate the service quality requirement corresponding to the subtask in the requested target task.

32. The method of any one of claims 28 to 31, wherein The subtasks include at least one of the following: Perception subtask; Compute subtasks; Artificial intelligence AI subtasks; Data subtask; Positioning subtasks; Internet Protocol Multimedia System IMS subtask; Communication subtask.

33. A task processing device comprising: A sending module, configured to send a first message to a first network element, wherein the first message is used to request modification of a target task or a subtask in the target task; A receiving module is used to receive a first response from the first network element, where the first response is used to indicate a modification result of the target task or a subtask in the target task.

34. The apparatus of claim 33, wherein: The sending the first message to the first network element includes: If it is determined that the first condition is met, sending the first message to the first network element; The first condition includes at least one of the following: The task requirement information of the terminal changes; The terminal desires to modify the target task or a subtask in the target task; The terminal has activated the power saving mode or the battery level of the terminal is lower than a first threshold; The terminal moves; The terminal obtains a fourth message from the second network element, where the fourth message is used to instruct or request modification of the target task or a subtask in the target task; The task contract of the terminal changes.

35. A task processing device comprising: A receiving module, configured to receive a first message from a terminal, wherein the first message is used to request modification of a target task or a subtask in the target task; A task modification module, configured to modify the target task or a subtask in the target task according to the first message; A sending module is used to send a first response to the terminal, where the first response is used to indicate a modification result of the target task or a subtask in the target task.

36. The apparatus of claim 35, wherein: The modifying the target task or a subtask in the target task according to the first message includes: Determine an updated task instance according to the first message, where the task instance is used to indicate relevant parameters assigned to the target task; The target task or a subtask in the target task is modified according to the task instance.

37. A task processing device comprising at least one of the following: a sending module, configured to send a fourth message to the terminal, wherein the fourth message is used to instruct or request modification of a target task or a subtask in the target task; A receiving module is used to receive a fifth message sent by the first network element, wherein the fifth message is used to request subtask requirement information corresponding to the target task, and to send a fifth response to the first network element, wherein the fifth response is used to indicate the subtask requirement information corresponding to the target task.

38. The apparatus of claim 37, wherein: The sending module is further configured to: when the second condition is met, execute the step of sending the fourth message to the terminal; The second condition includes at least one of the following: The task contract of the terminal changes; The second network element receives a task modification request from the terminal, where the task modification request is used to request modification of the target task or a subtask in the target task.

39. A terminal 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 according to any one of claims 1 to 9 are implemented.

40. A network side device, 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 any one of claims 10 to 27 are implemented, or the steps of the method described in any one of claims 28 to 32 are implemented.

41. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the method according to any one of claims 1 to 9, or implements the steps of the method according to any one of claims 10 to 27, or implements the steps of the method according to any one of claims 28 to 32.

Images