Task processing method, terminal and network side equipment

Abstract

The invention discloses a task processing method, a terminal and network side equipment, and belongs to the technical field of communication, and the task processing method comprises the steps that the terminal sends a first message to a first network element, and the first message is used for requesting to release a target task or a subtask in the target task; and receiving a first response from the first network element, the first response being used for indicating the target task or a release result of a sub-task in the target task.

Description

Technical Field

[0001] 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

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

[0003] However, the continuous increase of new tasks in the communication system not only puts great pressure on network resource management, but also makes the limited network resources unable to meet the network resource requirements of subsequent tasks. Summary of the Invention

[0004] The embodiments of the present application provide a task processing method, a terminal, and a network-side device, which can reduce the pressure on network resource management caused by continuously added tasks and meet the resource requirements of subsequent tasks.

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

[0006] On the second aspect, a task processing method is provided, including: a first network element receives a first message from a terminal, the first message being used to request the release of a target task or a subtask in the target task; the first network element performs a release operation on 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 release result of the target task or the subtask in the target task.

[0007] In a third 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 the release of a target task or a subtask in the target task; a receiving module for receiving a first response from the first network element, wherein the first response is used to indicate the release result of the target task or the subtask in the target task.

[0008] In a fourth 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 the release of a target task or a subtask in the target task; a task releasing module for performing a release operation on 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 release result of the target task or the subtask in the target task.

[0009] In a fifth 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.

[0010] In a sixth 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 a program or instruction to implement the steps of the method described in the first aspect.

[0011] In the seventh 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 are implemented.

[0012] In an eighth 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.

[0013] In the ninth 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.

[0014] In the tenth aspect, a wireless communication system is provided, comprising: 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.

[0015] In the eleventh aspect, a chip is provided, 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 steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0016] In the twelfth 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 to implement the steps of the method described in the second aspect.

[0017] In an embodiment of the present application, a terminal sends a first message to a first network element to request the release of a target task or a subtask within the target task, and determines the release result of the target task or the subtask within the target task based on a first response received from the first network element. Thus, by providing a task processing flow to release network resources allocated for tasks, the pressure on network resource management caused by the continuous addition of tasks to the communication system can be reduced, ensuring that the remaining network resources can meet the needs of other subsequent tasks and ensuring the performance of the communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a structural diagram of a wireless communication system provided by an exemplary embodiment of the present application.

[0019] Figure 2 This is one of the flowcharts of a task processing method provided by an exemplary embodiment of the present application.

[0020] Figure 3 This is the second flowchart of the task processing method provided by an exemplary embodiment of the present application.

[0021] Figure 4a This is one of the interactive flow diagrams of the task processing method provided by an exemplary embodiment of the present application.

[0022] Figure 4b This is the second interactive flow diagram of the task processing method provided by an exemplary embodiment of the present application.

[0023] Figure 5 This is the third flowchart of the task processing method provided by an exemplary embodiment of the present application.

[0024] Figure 6 This is one of the structural diagrams of a task processing device provided by an exemplary embodiment of the present application.

[0025] Figure 7 This is the second structural diagram of the task processing device provided by an exemplary embodiment of the present application.

[0026] Figure 8 It is a structural diagram of a communication device provided by an exemplary embodiment of the present application.

[0027] Figure 9 It is a schematic structural diagram of a terminal provided by an exemplary embodiment of the present application.

[0028] Figure 10 It is a structural diagram of a network side device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

[0033] Figure 1The block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can 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 user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc., and 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 (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (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.

[0034] 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 (TM), 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.

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

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

[0037] 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.).

[0038] 3. Task template: used to indicate the UE or network's requirements for a 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.

[0039] The task description information indicates the type of task, that is, what the task is. For example, if the task is to sense traffic congestion in the target area, the task description information would be "traffic congestion"; for another example, if the task is to park the vehicle in a suitable or designated location, the task description information would be "automatic parking."

[0040] Alternatively, the task description information is used to identify the task information of the task parameter application, which may include but is not limited to at least one of the data network name (Data Network Name, DNN), single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI), AF identifier, and application (Application, APP) identifier.

[0041] The task QoE requirement information is used to indicate the user's subjective perception of the quality and performance of the task, which refers to 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.

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

[0043] (a) Task feedback time or task latency, which indicates the time limit from when a task consumer or requester (e.g., UE, AF, etc.) initiates a task request to when it receives a task response.

[0044] (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.

[0045] (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 and / or the terminal, where the network includes but is not limited to the core network and the access network.

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

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

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

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

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

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

[0052] The perception measurement signal is used to indicate a signal for perception measurement supported by the perception device (which can be sent or received, or both sent and received). 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0066] Task description: Automatic parking.

[0067] Task type: Multi-tasking.

[0068] The task strategy or task quality information: task feedback time (such as 10s, 20s...); accuracy (such as 95%, 90%...);...

[0069] Subtask type: Perception subtask

[0070] Perception subtask configuration information: perception measurement mode (such as UE self-transmitting and 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.), perception purpose (such as surrounding environment monitoring); ...

[0071] Subtask type: Computational subtask

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

[0073] 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 combines it with the task strategy or task quality information to translate it.

[0074] Task instance: refers to an ongoing task. 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.

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

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

[0077] 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, subtask management, or subtask function.

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

[0079] The subtask functions mentioned in this application may be, but are not limited to, terminal devices, access network devices, or independently deployed execution units, etc.

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

[0081] Task verification refers to verifying whether a task is a legitimate task requested by an authorized or permitted 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 allows the task template request, whether the task request comes from an authorized or permitted UE (whether the UE has a task contract), whether the task request comes from an authorized or permitted AF (depending 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.

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

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

[0084] In this application, the task template may include at least one of a task template identifier, task description information, task QoE requirements, 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.

[0085] 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:

[0086] a) Task description information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0109] 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.).

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

[0111] like Figure 2 FIG. 2 is a flow chart of a task processing method 200 provided in an exemplary embodiment of the present application. The 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.

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

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

[0114] Optionally, the first network element may be but is not limited to the aforementioned TM function.

[0115] The first message is used to request the release of the target task or a subtask in the target task. That is, in this embodiment, when the terminal requests the release of a task, 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 release.

[0116] 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 subtask types of the 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.

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

[0118] Based on this, in this embodiment, the terminal's request to release the target task or the subtask in the target task can also be understood as: the terminal requests the network side to release or delete the resources (or network resources) allocated for the target task or the subtask in the target task. Thus, by releasing the resources allocated for the task, the pressure on network resource management caused by the continuously added tasks in the communication system can be reduced, ensuring that the remaining network resources can meet the task requirements of other subsequent tasks and ensuring the performance of the communication system.

[0119] In a possible implementation, the first message may include but is not limited to at least one of the following 001)-013).

[0120] 001) task description information, used to indicate the type of the target task (such as traffic congestion, environmental reconstruction, etc.), or to identify task information for application of task parameters, so that the first network element can determine the target task or the subtask in the target task requested to be released based on the task description information, such as releasing the target task or the subtask in the target task corresponding to the task description information, thereby realizing the release of network resources.

[0121] 002) DNN, used to indicate the DNN corresponding to the target task or the subtask in the target task requested to be released, so that the first network element determines the request to release the target task or the subtask in the target task according to the DNN, such as determining to release the target task or the subtask in the target task corresponding to or associated with the DNN, so as to realize the release of network resources.

[0122] 003) S-NSSAI, used to indicate the S-NSSAI corresponding to the target task or the subtask in the target task requested to be released, so that the first network element determines the target task or the subtask in the target task requested to be released based on the S-NSSAI, such as determining to release the target task or the subtask in the target task corresponding to or associated with the S-NSSAI to realize the release of network resources.

[0123] 004) Task strategy or task quality information, used to indicate the service quality requirements of the target task, so that the first network element determines the target task or the subtask in the target task to be requested to be released according to the task strategy or task quality information, such as determining to release the target task or the subtask in the target task corresponding to or associated with the task strategy or task quality information, so as to realize the release of network resources.

[0124] 005) A task identifier or a task session identifier is used to identify the target task, so that the first network element releases the target task corresponding to or associated with the task identifier or the task session identifier.

[0125] In this embodiment, the task identifier or task session identifier may be, but is not limited to, an ID, an IP address, a fully qualified domain name (FQDN), and the like.

[0126] 006) A subtask identifier or a subtask session identifier, used to identify a subtask in the target task, so that the first network element releases the subtask corresponding to or associated with the subtask identifier or the subtask session identifier.

[0127] 007) Subtask management function identifier or subtask function identifier. The subtask management function identifier is used to indicate the subtask management function that manages the subtask in the target task, and can be used by the network side (such as the first network element) to select the corresponding subtask management function according to the subtask function management identifier to perform a subtask release operation.

[0128] Optionally, 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.

[0129] In this embodiment, the subtask management function and the first network element can be deployed independently or combined, which is not limited here.

[0130] The subtask function identifier is used to indicate the subtask function of executing the subtask in the target task, and can be used on the network side (such as the first network element or the subtask management function) to select the corresponding subtask function according to the subtask function identifier to perform a subtask release operation.

[0131] 008) Subtask strategy or subtask quality information, used to indicate the service quality requirements of the subtasks in the target task, so that the first network element determines the subtasks that need to be released based on the subtask strategy or subtask quality information, such as determining to release the subtasks corresponding to or associated with the subtask strategy or subtask quality information to realize the release of network resources.

[0132] 009) First information indicating requirement information corresponding to the target task requested to be released. In this embodiment, the first information may be, but is not limited to, a task template or a task template identifier, etc., so that the first network element can release the target task or a subtask within the target task based on one or more of the task description information, task QoE requirement information, task policy or task quality information, task parameters, etc., included in or corresponding to the first information.

[0133] 010) A subtask execution order, which is used to indicate the timing relationship of the execution of subtasks in the target task, so that the first network element determines the subtasks or subtask resources that need to be released with reference to the subtask execution order.

[0134] 011) Release reason, used to indicate the reason why the terminal requests to release the target task or a subtask in the target task. In this embodiment, the release reason may include but is not limited to at least one of regular release, network switching, temporary release, insufficient resources, semantic error, grammatical error, etc.

[0135] The periodic release may be understood as the terminal requesting to release the target task or a subtask in the target task according to a predetermined time interval or cycle.

[0136] The network switching may be understood as the terminal requesting to release the target task or a subtask in the target task when determining to send the network switching, and the network is the network where the terminal resides or accesses.

[0137] The temporary release may be a temporary request by the terminal to release the target task or a subtask within the target task due to reasons such as insufficient battery. It is worth noting that when the temporary release is performed, in subsequent operations, after the first network element releases the corresponding resources, the task context locally stored by the first network element will be retained, so that the resource configuration can be referenced or reused when the same task is subsequently established.

[0138] For releases other than temporary releases, such as regular releases, the first network element may directly delete the locally retained task context and re-execute the entire task establishment process when subsequently establishing the same task.

[0139] The insufficient resources may be understood as insufficient task processing resources on the terminal, etc., which is not limited here.

[0140] The semantic error or grammatical error may be understood as the terminal receiving a task message that cannot be understood or parsed.

[0141] 012) Release type, which is used to indicate the type of resource requested to be released. For example, in this embodiment, the release type may include but is not limited to at least one of the following a)-c).

[0142] a) Release predefined resource combinations.

[0143] For example, assuming that three resource combinations are predefined, combination 1 includes perception resources corresponding to the perception subtask and computing resources corresponding to the computing subtask, combination 2 includes perception resources corresponding to the perception subtask and AI resources corresponding to the AI ​​subtask; combination 3 includes computing resources corresponding to the computing subtask and AI resources corresponding to the AI ​​subtask, then, if the release type is the release of the predefined resource combination, and the predefined resource combination is combination 2, it can be understood that the terminal requests to release the perception resources corresponding to the perception subtask and the AI ​​resources corresponding to the AI ​​subtask in combination 2.

[0144] b) Release the resources corresponding to the subtasks in the target task.

[0145] For example, when the release type is to release resources corresponding to a subtask in the target task, and the subtask is a perception subtask, it can be understood that the terminal requests to release only the resources corresponding to the perception subtask.

[0146] c) Release all resources corresponding to the target task.

[0147] For example, if the release type is to release all resources corresponding to the target task, then it can be understood that the terminal requests to release all resources corresponding to the target task.

[0148] It is worth noting that, in this embodiment, the three different release types provided in a) to c) above can be identified by different indication information, which is not limited here.

[0149] 013) A first instruction is used to instruct deletion of the subtask strategy or subtask quality information corresponding to the subtask in the target task.

[0150] For example, when the first indication is included in the first message, the first network element may only delete the subtask policy or subtask quality information corresponding to the subtask in the target task, but does not delete the connection or data transmission channel between the first network element and the terminal.

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

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

[0153] In this embodiment, if the first network element and the SMF are jointly established, then the first message may be a PDU session release request message.

[0154] Optionally, in this embodiment, the first message may be generated by the first protocol layer of the terminal. The first protocol layer may be understood as a newly added protocol layer, for example, responsible for task management or task signaling and / or data generation and processing, or the first protocol layer may also be understood as an enhancement to an existing protocol layer so that the existing protocol layer has the function of task management or task signaling or task data generation and processing, such as an enhancement to the non-access stratum (NAS) or session management (SM) layer.

[0155] Then, for the first network element, after receiving the first message sent by the terminal, it can perform a release operation on 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 execution result to indicate the release result of the target task or the subtask in the target task.

[0156] Corresponding to the aforementioned terminal, the first network element has a corresponding first protocol layer for communication between the terminal and the first network element, such as the first response can be generated or processed by the first protocol layer of the first network element.

[0157] In an optional implementation, when the first network element performs a release operation on the target task or a subtask within the target task, there may be multiple implementations depending on the internal implementation of the first network element. For example, the first network element may independently perform a release operation on the target task or a subtask within the target task, or may jointly perform a release operation on the target task or a subtask within the target task with other network elements, and this embodiment does not impose any restrictions thereon.

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

[0159] The first response is used to indicate the release result of the target task or the subtask in the target task, such as whether the first network element accepts the release of the target task or the subtask.

[0160] In a possible implementation, if the first response indicates that the release result of the target task or a subtask in the target task is a failure (or a release failure), the first response may include a reason for the release failure.

[0161] Optionally, in this embodiment, the reason for the release failure may include but is not limited to at least one of the following 101)-110).

[0162] 101) The target task is in progress.

[0163] 102) The target task does not exist.

[0164] 103) The target task is not allowed or authorized.

[0165] 104) The terminal does not have a task contract for the target task. For example, the first network element determines, based on the first message and by interacting with the UDM, that the task contract for the terminal does not include the target task.

[0166] 105) The subtask in the target task is in use.

[0167] 106) The subtask in the target task does not exist. For example, the first network element or the subtask management function or the subtask function does not find the subtask in the target task according to the first message.

[0168] 107) The subtask function corresponding to the subtask in the target task does not exist. For example, the first network element or subtask management function does not find the subtask function corresponding to the subtask in the target task according to the first message.

[0169] 108) The subtask resource corresponding to the subtask in the target task does not exist. For example, the first network element or subtask management function does not find the subtask resource corresponding to the subtask in the target task according to the first message.

[0170] 109) The subtask management function corresponding to the target task is not found. For example, the first network element does not find or determine the subtask management function corresponding to the target task based on the first message.

[0171] 110) The first message (or the terminal) is not permitted or authorized. For example, the first network element verifies that the first message is not permitted or authorized based on the terminal identifier, task identifier, etc. carried in the first message. This embodiment does not limit the verification method of the first message.

[0172] It is worth noting that, in this embodiment, in addition to including one or more items of the aforementioned 101)-110), the first response may also include other information, such as the target task identifier or subtask identifier.

[0173] In addition, similar to the sending of the first message, the terminal may receive the first response in multiple ways, 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.

[0174] In this embodiment, the terminal sends a first message to the first network element to request the release of the target task or a subtask within the target task, and determines the release result of the target task or the subtask within the target task based on the first response received from the first network element. Thus, by providing a task processing flow to release network resources allocated for tasks, the pressure on network resource management caused by the continuous addition of tasks in the communication system can be reduced, ensuring that the remaining network resources can meet the needs of other subsequent tasks and ensuring the performance of the communication system.

[0175] like Figure 3 FIG. 3 is a flow chart of a task processing method 300 provided in an exemplary embodiment of the present application. The 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.

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

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

[0178] It is understandable that the implementation process of S310 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, in a possible implementation, please refer to Figure 3 The process of the terminal sending the first message to the first network element described in S310 may include S311, the content of which is as follows.

[0179] S311: When a first condition is met, the terminal sends the first message to the first network element.

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

[0181] Condition 1: The terminal expects to release the target task or a subtask in the target task.

[0182] The situations in which the terminal expects to release the target task or the subtask in the target task may include but are not limited to: the terminal needs to close the APP corresponding to the target task, the terminal is shut down, the terminal has insufficient resources, etc.

[0183] Condition 2: The terminal has enabled the power saving mode or the battery level of the terminal is lower than a first threshold.

[0184] In an optional implementation, 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 further include a third indication, and the third indication is used to indicate the battery status of the terminal, such as a low battery status, so that the first network element releases the resources allocated to the target task or the subtask in the target task while clarifying the reason why the terminal requests to release the target task or the subtask in the target task.

[0185] Condition 3: The terminal receives a second indication, such as the terminal receives the second indication from an upper layer.

[0186] Among them, the second indication is used to instruct the terminal to fall back to a specific customized network, release the target task, release the task connection corresponding to the target task, and release at least one of the subtasks in the target task. The specific customized network can be but is limited to a 5G system (5G System, 5GS) or an evolved packet system (Evolved Packet System, EPS), etc.

[0187] Condition 4: The terminal receives a second message sent by a second network element, where the second message is used to request the terminal to release the target task or a subtask in the target task.

[0188] The second network element may be, but is not limited to, an AF.

[0189] Condition 5: A timer has expired, wherein the timer is started when the target task or a subtask within the target task is successfully established. That is, the terminal starts a timer when the target task or the subtask is successfully established, and when the timer expires, sends a first message to the first network element to request the release of the target task or the subtask.

[0190] It's worth noting that by setting conditions 1-5 above, the network and the terminal can have a consistent understanding of the task release conditions while also ensuring flexibility in task release, meeting user needs. Furthermore, conditions 1-5 above can be implemented through protocol agreement or network configuration, and are not limited here.

[0191] Correspondingly, for the first network element, after receiving the first message sent by the terminal, it can perform a release operation on 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 execution result.

[0192] In this embodiment, depending on whether the first network element and the subtask management function are jointly established, such as integrated or deployed on the same device, the implementation method of the first network element performing the release operation on the target task or the subtask in the target task according to the first message may be different.

[0193] For example, assuming that the first network element and the subtask management function are deployed independently, then the process of the first network element performing the release operation on the target task or the subtask in the target task according to the first message may include: the first network element may first determine the subtask management function corresponding to the subtask in the target task; then send a third message to the subtask management function according to the first message, and the third message is used to request the release of the subtask in the target task; then, the subtask management function requests the corresponding subtask function to perform the subtask release operation according to the third message, and sends a third response to the first network element to indicate whether the subtask in the target task is successfully released; finally, the first network element receives the third response from the subtask management function to determine whether the target task or the subtask in the target task is successfully released.

[0194] For another example, assuming that the first network element and the subtask management function are jointly established, such as the two are deployed together or the subtask management function is integrated into the first network element, then the process of the first network element performing the release operation on the target task or the subtask in the target task according to the first message may include: the first network element may first determine the subtask function according to the first message, and then send a third message to the subtask function, and the third message is used to request the release of the subtask in the target task; then, the subtask function performs the release operation of the subtask according to the third message, and sends a third response to the first network element according to the execution result to indicate the release result of the subtask in the target task; the first network element receives the third response from the subtask function to determine whether the target task or the subtask in the target task is successfully released.

[0195] Based on this, in one possible implementation method, there may be multiple ways for the first network element to determine the subtask management function or subtask function corresponding to the subtask in the target task. For example, the first network element may determine the subtask management function or the subtask function corresponding to the subtask in the target task based on at least one of the subtask management function identifier, subtask function identifier, subtask session identifier, subtask policy or subtask quality information contained in the first message.

[0196] Alternatively, the first network element determines the subtask management function or subtask function corresponding to the subtask in the target task based on the locally stored task context corresponding to the target task, wherein the task context includes the association relationship between the target task and the subtask management function or subtask function.

[0197] Alternatively, the first network element can determine the subtask management function or subtask function corresponding to the subtask in the target task based on at least one of the subtask management function identifier, subtask function identifier, subtask session identifier, subtask policy or subtask quality information contained in the first message and the task context corresponding to the target task stored locally by the first network element.

[0198] It is worth noting that the task context is saved by the first network element when the target task is established, wherein the association relationship between the target task and the subtask management function or the subtask function is saved.

[0199] In addition, if the first network element does not query or determine the subtask management function or subtask function, it can send a first response to the terminal and indicate that the reason for the failure to release the target task or the subtask in the target task is that the subtask management function or subtask function cannot be queried or determined.

[0200] In one implementation, when the first network element sends the third message to the determined subtask management function or subtask function, the third message may include but is not limited to at least one of the following 201)-204).

[0201] 201) The terminal identifier is used to identify the terminal requesting to release the subtask.

[0202] 202) The subtask identifier is used to identify the subtask requested to be released, so that the subtask management function determines the subtask function and releases the subtask corresponding to the subtask identifier through the subtask function, or enables the subtask function to release the subtask corresponding to the identifier.

[0203] 203) The subtask function identifier corresponding to the subtask is used to identify the subtask function that performs the subtask release operation, so that the subtask management function requests the subtask function corresponding to the subtask function identifier to perform the subtask release operation.

[0204] 204) The subtask strategy or subtask quality information is used to indicate the subtask strategy or task quality corresponding to the subtask requested to be released, thereby enabling the subtask management function or subtask function to release the subtask corresponding to the subtask strategy or subtask quality information.

[0205] In one implementation, when the third response indicates that the subtask in the target task was not successfully released, the third response may include a reason for the release failure. For example, in this embodiment, the reason for the release failure may include but is not limited to at least one of the following 301)-304).

[0206] 301) The subtask is in use.

[0207] 302) The subtask does not exist.

[0208] 303) The subtask function corresponding to the subtask does not exist.

[0209] 304) The resource corresponding to the subtask does not exist.

[0210] In one possible implementation, after the first network element performs the subtask release operation according to the first message, the connection between the first network element and the subtask management function or subtask function is disconnected, and the subtask management function or subtask function address is deleted. Furthermore, when the first network element needs to execute the target task again, it needs to reselect the subtask management function or subtask function to re-establish the target task.

[0211] Of course, if the first network element does not determine or find the subtask management function or subtask function when performing the task release operation, then the first network element may reject the task release request sent by the terminal through the first message. In this case, the first network element may also send a first response to the terminal to indicate to the terminal that the release result of the target task or the subtask in the target task is a release failure, and the reason for the release failure is that the subtask management function or subtask function was not found.

[0212] In a possible implementation, when the first network element performs a release operation according to the first message, it may also release at least part of the task context of the target task.

[0213] For example, if the terminal requests to release the target task through the first message, the first network element may delete the task context of the target task and release the connection or data transmission channel between the first network element and the terminal.

[0214] If the terminal requests to release the subtask in the target task through the first message, then the first network element deletes the task context of the subtask in the target task and releases the connection or data transmission channel between the first network element and the subtask function corresponding to the subtask.

[0215] If the terminal requests to release the task policy or task quality information of the target task through the first message, then the first network element may only delete the task policy or task quality information in the task context of the target task, but will not release the connection or data transmission channel between the first network element and the terminal.

[0216] If the terminal requests to release the subtask policy or subtask quality information of the subtask in the target task through the first message, then the first network element may only delete the subtask policy or subtask quality information in the task context of the target task, but will not release the connection or data transmission channel between the first network element and the subtask function corresponding to the subtask.

[0217] Optionally, the task context of the aforementioned target task may include but is not limited to at least one of a)-b).

[0218] a) The task context stored locally in the first network element.

[0219] b) The task context sent by the first network element to a third network element, wherein the third network element is a network element other than the first network element, such as at least one of a UDM and a UDR.

[0220] In one possible implementation, before the first network element performs a release operation on the target task or a subtask in the target task according to the first message, it may also verify whether the first message is allowed or authorized, thereby ensuring the legitimacy of the first message.

[0221] The first network element may, when determining that the first message is allowed or authorized, perform a release operation on the target task or a subtask in the target task according to the first message.

[0222] 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 release 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.

[0223] Based on this, in the present application, the first network element may verify whether the first message is allowed or authorized in various ways. For example, the first network element may determine that the first message is allowed or authorized when it determines that the task identifier carried by the first message is stored; and may determine that the first message is not allowed or authorized 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.

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

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

[0226] It is understandable that the implementation process of S320 can refer to the relevant description in the aforementioned method embodiment 200. To avoid repetition, it will not be repeated here.

[0227] In this embodiment, a task-centric task processing method is provided to achieve task release, so that the network side can dynamically reclaim resources allocated for tasks and meet the resource requirements of continuously newly added tasks in the communication system.

[0228] Based on the introduction of the task processing method in the aforementioned method embodiments 200-300, for ease of understanding, the following exemplary description of the task processing method provided in this application is provided, as follows.

[0229] Example 1

[0230] Assuming that the first network element is a TM network element, the second network element is an AF, and the TM network element and the subtask management function are deployed independently, then, if Figure 4a As shown, the task processing flow may include but is not limited to the following S411-S414.

[0231] S411: The terminal sends a first message to the TM network element to request the release of a target task or a subtask in the target task.

[0232] Optionally, the terminal may send a first message to the TM network element when determining that the first condition is met.

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

[0234] Condition 1: The terminal expects to release the target task or a subtask in the target task.

[0235] Condition 2: The terminal has enabled the power saving mode or the battery level of the terminal is lower than a first threshold.

[0236] Condition 3: The terminal receives a second indication, where the second indication is used to instruct the terminal to fall back to a specific customized network, release the target task, release the task connection corresponding to the target task, and release at least one of a subtask in the target task.

[0237] Condition 4: the terminal receives a second message sent by the AF, where the second message is used to request the terminal to release the target task or a subtask in the target task.

[0238] Condition 5: A timer times out, wherein the timer is started when the target task or a subtask within the target task is successfully established.

[0239] S412: Upon receiving the first message, the TM network element performs a task release operation.

[0240] The task release operation includes at least one of the following operations 1 and 2.

[0241] Operation 1: The TM network element verifies whether the first message is allowed or authorized. If the first message is allowed or authorized, operation 2 is performed; otherwise, operation S414 is performed.

[0242] In operation 2, the TM network element determines a subtask management function and requests the subtask management function to perform a subtask release operation. For example, the TM network element sends a third message to the subtask management function to request the subtask management function to perform the subtask release operation. The subtask management function then sends a third response to the TM network element based on the subtask release execution result, indicating the subtask release result.

[0243] For example, if the subtask includes a sensing subtask, the TM network element sends a third message to a subtask management function (or sensing management function) to request the release of all or part of the sensing resources corresponding to the sensing subtask. The third message may include, but is not limited to, at least one of a terminal identifier, a sensing subtask identifier, a sensing function address, a sensing policy, or sensing quality information.

[0244] Then, after receiving the third message, the perception management function determines the subtask function (or perception function) based on the third message, etc., and sends a subtask release request to the perception function, requesting the subtask function to perform a subtask release operation, such as requesting the release of all or part of the perception resources corresponding to the perception subtask. The subtask release request may include, but is not limited to, at least one of a terminal identifier, a perception subtask identifier, a perception policy, or perception quality information.

[0245] Then, the perception function performs a subtask release operation upon receiving the subtask release request, and sends a subtask release response to the perception management function according to the subtask release result to indicate the subtask release result.

[0246] Finally, the sensing management function sends a third response to the TM network element based on the received subtask release response, indicating whether the sensing resources associated with the sensing subtask are successfully released. If the sensing resources are not successfully released, the subtask release response or the third response may include a reason for the release failure, such as the sensing subtask being in use, the sensing subtask not existing, the sensing function not existing, or the sensing resource not existing.

[0247] For another example, if the subtask includes a computing subtask, the TM network element sends a third message to a subtask management function (or computing management function) to request the release of all or part of the computing resources corresponding to the computing subtask. The third message may include, but is not limited to, at least one of a terminal identifier, a computing subtask identifier, a computing function address, a computing policy, or computing quality information.

[0248] Then, after receiving the third message, the computing management function determines the subtask function (or computing function) based on the third message, etc., and sends a subtask release request to the computing function, requesting the subtask function to perform a subtask release operation, such as requesting the release of all or part of the computing resources corresponding to the computing subtask. The subtask release request may include, but is not limited to, at least one of a terminal identifier, a computing subtask identifier, a computing policy, or computing quality information.

[0249] Next, the computing function executes a subtask release operation upon receiving the subtask release request, and sends a subtask release response to the computing management function according to the subtask release result to indicate the subtask release result.

[0250] Finally, the computing management function sends a third response to the TM network element based on the received subtask release response, indicating whether all or part of the computing resources corresponding to the computing subtask have been successfully released. If the computing resources are not successfully released, the subtask release response or the third response may include, but is not limited to, reasons for the release failure, such as the computing subtask being in use, the computing subtask not existing, the computing function not existing, or the computing resources not existing.

[0251] For another example, if the subtask includes an AI subtask, the TM network element sends a third message to the subtask management function (or AI management function) to request the release of all or part of the AI ​​resources corresponding to the AI ​​subtask. The third message may include, but is not limited to, at least one of a terminal identifier, an AI subtask identifier, an AI function address, an AI policy, or AI quality information.

[0252] Then, after receiving the third message, the AI ​​management function determines the subtask function (or AI function) based on the third message, etc., and sends a subtask release request to the AI ​​function, requesting the subtask function to perform a subtask release operation, such as requesting the release of all or part of the AI ​​resources corresponding to the AI ​​subtask. The subtask release request may include, but is not limited to, at least one of a terminal identifier, an AI subtask identifier, an AI policy, or AI quality information.

[0253] Next, the AI ​​function performs a subtask release operation upon receiving the subtask release request, and sends a subtask release response to the AI ​​management function according to the subtask release result to indicate the subtask release result.

[0254] Finally, the AI ​​management function sends a third response to the TM network element based on the received subtask release response, indicating whether the AI ​​resource corresponding to the AI ​​subtask was successfully released. If the AI ​​resource was not successfully released, the subtask release response or the third response may include, but is not limited to, reasons for the release failure, such as the AI ​​subtask being in use, the AI ​​subtask not existing, the AI ​​function not existing, or the AI ​​resource not existing.

[0255] S413: The TM network element releases at least part of the task context of the target task.

[0256] The first network element deletes all or part of the task context of the target task.

[0257] Alternatively, the first network element deletes the task contexts of all or part of the subtasks in the target task.

[0258] S414 , the TM network element sends a first response to the terminal according to the execution result of the first operation, indicating the release result of the target task or the subtask in the target task, such as release failure or release success.

[0259] It is worth noting that the implementation process of the aforementioned S421-S424 provided in this Example 1 can refer to the relevant description in the aforementioned method embodiment 200 or 300, and to avoid repetition, it is not repeated here. In addition, the implementation process of the task processing method provided in this Example 1 may include but is not limited to the aforementioned S421-S424. That is, the task processing method provided in this Example 1 may include more or fewer steps than the aforementioned S421-S424.

[0260] Example 2

[0261] Assuming that the first network element is a TM network element, the second network element is an AF, and the TM network element is integrated with the subtask management function, such as the subtask management function is integrated into the TM network element, then the task processing process may include but is not limited to Figure 4b S421-S424 shown.

[0262] S421: The terminal sends a first message to the TM network element to request the release of a target task or a subtask in the target task.

[0263] Optionally, the terminal may send a first message to the TM network element when determining that the first condition is met.

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

[0265] Condition 1: The terminal expects to release the target task or a subtask in the target task.

[0266] Condition 2: The terminal has enabled the power saving mode or the battery level of the terminal is lower than a first threshold.

[0267] Condition 3: The terminal receives a second indication, where the second indication is used to instruct the terminal to fall back to a specific customized network, release the target task, release the task connection corresponding to the target task, and release at least one of a subtask in the target task.

[0268] Condition 4: The terminal receives a second message sent by a second network element, where the second message is used to request the terminal to release the target task or a subtask in the target task.

[0269] Condition 5: A timer times out, wherein the timer is started when the target task or a subtask within the target task is successfully established.

[0270] S422: Upon receiving the first message, the first network element performs a task release operation.

[0271] The task release operation includes at least one of the following operations 1 and 2.

[0272] Operation 1: The first network element verifies whether the first message is allowed or authorized. If it is ensured that the first message is allowed or authorized, execute operation 2; otherwise, execute S433.

[0273] Operation 2: The first network element determines a subtask function and sends a third message to the subtask function to request the subtask function to perform a subtask release operation.

[0274] For operation 2, if the subtask includes a sensing subtask, the TM network element sends a third message to the subtask function (or sensing function) to request the release of some or all sensing resources corresponding to the sensing subtask. The third message may include, but is not limited to, at least one of a terminal identifier, a sensing subtask identifier, a sensing function address, a sensing policy or sensing quality information, sensing accuracy, and a sensing area.

[0275] Correspondingly, after receiving the third message, the perception function executes a subtask release operation and, based on the execution result, sends a third response to the TM network element to indicate whether the perception resource corresponding to the perception subtask was successfully released. If the perception resource was not successfully released, the third response may include the reason for the release failure, such as the perception subtask being in use, the perception subtask not existing, the perception function not existing, or the perception resource not existing. Optionally, the third response may also include perception node information.

[0276] If the subtask includes a computing subtask, the TM network element sends a third message to the subtask function (or computing function) to request the release of some or all computing resources corresponding to the computing subtask. The third message may include, but is not limited to, at least one of a terminal identifier, a computing subtask identifier, a computing function address, a computing strategy or computing quality information, a data processing method, computing latency, and computing accuracy.

[0277] Correspondingly, after receiving the third message, the computing function executes a subtask release operation and, based on the execution result, sends a third response to the TM network element to indicate whether the computing resource corresponding to the computing subtask was successfully released. If the computing resource was not successfully released, the third response may include, but is not limited to, the reason for the release failure, such as the computing subtask being in use, the computing subtask not existing, the computing function not existing, or the computing resource not existing. Optionally, the third response may also include computing node information and the computing node's computing power.

[0278] If the subtask includes an AI subtask, the TM network element sends a third message to the subtask function (or AI function) to request the release of some or all AI resources corresponding to the AI ​​subtask. The third message may include, but is not limited to, at least one of a terminal identifier, an AI subtask identifier, an AI function address, AI policy or AI quality information, model complexity, model training time, model inference time, and model accuracy.

[0279] Correspondingly, after receiving the third message, the AI ​​function executes a subtask release operation and, based on the execution result, sends a third response to the TM network element to indicate whether the AI ​​resource corresponding to the AI ​​subtask was successfully released. If the AI ​​resource is not successfully released, the third response may include, but is not limited to, the reason for the release failure, such as the AI ​​subtask being in use, the AI ​​subtask not existing, the AI ​​function not existing, the AI ​​resource not existing, etc. Optionally, the third response may also include AI node information, model acquisition address, model training address, etc.

[0280] S423: The TM network element releases at least part of the task context of the target task.

[0281] For example, the first network element deletes the task context of the target task, or the first network element deletes the task context of a subtask in the target task.

[0282] S424 , the TM network element sends a first response to the terminal according to the execution result of the first operation, indicating the release result of the target task or the subtask in the target task, such as release failure or release success.

[0283] It is worth noting that the implementation process of the aforementioned S421-S424 provided in this Example 2 can refer to the relevant description in the aforementioned method embodiment 200 or 300, and to avoid repetition, it is not repeated here. In addition, the implementation process of the task processing method provided in this Example 2 may include but is not limited to the aforementioned S421-S424. That is, the task processing method provided in this Example 2 may include more or fewer steps than the aforementioned S421-S424.

[0284] Example 3

[0285] The difference from the aforementioned Example 1 and Example 2 is that: assuming that the first message includes a first indication for instructing deletion of the subtask policy or task quality information corresponding to the subtask in the target task, then the TM network element only deletes the corresponding task policy or task quality information, subtask policy or subtask quality information from the managed task context to release the corresponding resources. However, the connection or data transmission channel between the TM network element and the terminal still exists to facilitate the subsequent re-creation of the target task, thereby improving the efficiency of target task reconstruction and saving signaling overhead during target task reconstruction.

[0286] like Figure 5 FIG. 5 is a flow chart of a task processing method 500 provided in an exemplary embodiment of the present application. The method 500 may be, but is not limited to, executed by a first network element. Specifically, the method 500 may be executed 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.

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

[0288] S520: The first network element performs a release operation on the target task or a subtask in the target task according to the first message.

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

[0290] In an optional implementation, the first message includes at least one of the following: task description information, used to indicate the type of the target task; data network name DNN; single network slice selection auxiliary information S-NSSAI; task policy or task quality information, used to indicate the service quality requirements of the target task; task identifier or task session identifier, used to identify the target task; subtask identifier or subtask session identifier, used to identify the subtask in the target task; subtask management function identifier or subtask function identifier, used to indicate the subtask management function for managing the subtask in the target task or the subtask function for executing the subtask in the target task; subtask policy or subtask quality information, used to indicate the service quality requirements of the subtask in the target task; first information, used to indicate the demand information corresponding to the target task requested to be released; subtask execution order; release reason, used to indicate the reason for requesting to release the target task or the subtask in the target task; release type, used to indicate the type of resource requested to be released; first indication, used to indicate the deletion of the subtask policy or subtask quality information corresponding to the subtask in the target task; third indication, used to indicate the power status of the terminal.

[0291] In an optional implementation, the release reason includes at least one of the following: regular release; network switching; temporary release; insufficient resources; semantic error; or grammatical error.

[0292] In an optional implementation, the release type includes at least one of the following: releasing a predefined resource combination; releasing resources corresponding to subtasks in the target task; and releasing all resources corresponding to the target task.

[0293] In an optional implementation, the first network element performs a release operation on the target task or the subtask in the target task according to the first message, including: the first network element determines the subtask management function or subtask function corresponding to the subtask in the target task; the first network element sends a third message to the subtask management function or subtask function according to the first message, and the third message is used to request the release of the subtask in the target task; the first network element receives a third response from the subtask management function or subtask function, and the third response is used to indicate whether the subtask in the target task is successfully released.

[0294] In an optional implementation, the first network element determines the subtask management function or subtask function corresponding to the subtask in the target task, including: the first network element determines the subtask management function or subtask function corresponding to the subtask in the target task based on at least one of the following: at least one of the subtask management function identifier, subtask function identifier, subtask session identifier, subtask policy or subtask quality information contained in the first message; the task context corresponding to the target task stored in the first network element, the task context including the association relationship between the target task and the task-related information of the target task.

[0295] In an optional implementation, the third message includes at least one of the following: the terminal identifier; the subtask identifier; the subtask function identifier corresponding to the subtask; and the subtask strategy or task quality information.

[0296] In an optional implementation, when the third response indicates that the subtask in the target task is not released successfully, the third response includes a reason for the release failure.

[0297] In an optional implementation, the reason for the release failure includes at least one of the following: the subtask is in use; the subtask does not exist; the subtask function corresponding to the subtask does not exist; the resource corresponding to the subtask does not exist.

[0298] In an optional implementation, the method further includes: the first network element releasing at least part of the task context of the target task.

[0299] In an optional implementation, the first network element releases at least part of the task context of the target task, including at least one of the following: the first network element deletes the task context of the target task; the first network element deletes the task context of the subtask in the target task; the first network element deletes the task policy or task quality information in the task context of the target task; the first network element deletes the subtask policy or subtask quality information in the task context of the target task.

[0300] In an optional implementation, the task context of the target task includes at least one of the following: the task context stored locally by the first network element; the task context sent by the first network element to a third network element, where the third network element is a network element other than the first network element.

[0301] In an optional implementation, the method also includes: the first network element verifies whether the first message is allowed or authorized; and when it is determined that the first message is allowed or authorized, executes the step of releasing the target task or the subtask in the target task according to the first message.

[0302] In an optional implementation, the verification of whether the first message is allowed or authorized includes: when the task identifier carried by the first message is stored in the first network element, determining that the first message is allowed or authorized; 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, determining that the first message is not allowed or authorized.

[0303] In an optional implementation, when the first response indicates that the release result of the target task or a subtask in the target task is a failure, the first response includes a reason for the release failure.

[0304] In an optional implementation, the reasons for the release failure include at least one of the following: the target task is in progress; the target task does not exist; the release of the target task is not allowed or authorized; the terminal has no task contract for the target task; the subtask in the target task is in use; the subtask in the target task does not exist; the subtask function corresponding to the subtask in the target task does not exist; the subtask resource corresponding to the subtask in the target task does not exist; the subtask management function corresponding to the target task is not queried; the first message is not allowed or authorized.

[0305] In an optional implementation, the subtask includes at least one of the following: a communication subtask; a perception subtask; a computing subtask; a data subtask; a positioning subtask; an IMS subtask; or an AI subtask.

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

[0307] 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 performed by the task processing device as an example.

[0308] like Figure 6As shown, it is a structural diagram of a task processing device provided in an embodiment of the present application, and the device 600 includes: a sending module 610, used to send a first message to a first network element, wherein the first message is used to request the release of a target task or a subtask in the target task; a receiving module 620, used to receive a first response from the first network element, wherein the first response is used to indicate the release result of the target task or the subtask in the target task.

[0309] In an optional implementation, the first message includes at least one of the following: task description information, used to indicate the type of the target task; data network name DNN; single network slice selection auxiliary information S-NSSAI; task policy or task quality information, used to indicate the service quality requirements of the target task; task identifier or task session identifier, used to identify the target task; subtask identifier or subtask session identifier, used to identify the subtask in the target task; subtask management function identifier or subtask function identifier, used to indicate the subtask management function for managing the subtask in the target task or the subtask function for executing the subtask in the target task; subtask policy or subtask quality information, used to indicate the service quality requirements of the subtask in the target task; first information, used to indicate the demand information corresponding to the target task requested to be released; subtask execution order; release reason, used to indicate the reason for requesting to release the target task or the subtask in the target task; release type, used to indicate the type of resources requested to be released; first indication, used to indicate the deletion of the subtask policy or subtask quality information corresponding to the subtask in the target task.

[0310] In an optional implementation, the release reason includes at least one of the following: regular release; network switching; temporary release; insufficient resources; semantic error; or grammatical error.

[0311] In an optional implementation, the release type includes at least one of the following: releasing a predefined resource combination; releasing resources corresponding to subtasks in the target task; and releasing all resources corresponding to the target task.

[0312] In an optional implementation, the terminal sends a first message to a first network element, including: when a first condition is met, the terminal sends the first message to the first network element; wherein, the first condition includes at least one of the following: the terminal expects to release the target task or a subtask in the target task; the terminal has turned on power saving mode or the battery level of the terminal is lower than a first threshold; the terminal receives a second indication, and the second indication is used to instruct the terminal to fall back to a specific customized network, release the target task, release the task connection corresponding to the target task, and release at least one of the subtasks in the target task; the terminal receives a second message sent by the second network element, and the second message is used to request the terminal to release the target task or the subtask in the target task; the timer times out, wherein the timer is started when the target task or the subtask in the target task is successfully established.

[0313] In an optional implementation, 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 also includes a third indication, and the third indication is used to indicate the battery status of the terminal.

[0314] In an optional implementation, when the first response indicates that the release result of the target task or a subtask in the target task is a failure, the first response includes a reason for the release failure.

[0315] In an optional implementation, the reason for the release failure includes at least one of the following: the target task is in progress; the target task does not exist; the target task is not allowed or authorized; the terminal has no task contract for the target task; the subtask in the target task is in use; the subtask in the target task does not exist; the subtask function corresponding to the subtask in the target task does not exist; the subtask resource corresponding to the subtask in the target task does not exist; the subtask management function corresponding to the target task is not queried; the first message is not allowed or authorized.

[0316] In an optional implementation, the subtask includes at least one of the following: a communication subtask; a perception subtask; a computing subtask; a data subtask; a positioning subtask; an IMS subtask; or an AI subtask.

[0317] The task processing device 600 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.

[0318] The task processing device 600 provided in the embodiment of the present application can realize Figures 2 to 3 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0319] like Figure 7 As shown, it is a structural diagram of a task processing device 700 provided in an embodiment of the present application, and the device 700 includes: a receiving module 710, used to receive a first message from a terminal, wherein the first message is used to request the release of a target task or a subtask in the target task; a task releasing module 720, used to perform a release operation on the target task or the subtask in the target task according to the first message; and a sending module 730, used to send a first response to the terminal, wherein the first response is used to indicate the release result of the target task or the subtask in the target task.

[0320] In an optional implementation, the first message includes at least one of the following: task description information, used to indicate the type of the target task; data network name DNN; single network slice selection auxiliary information S-NSSAI; task policy or service quality task quality information, used to indicate the service quality requirements of the target task; task identifier or task session identifier, used to identify the target task; subtask identifier or subtask session identifier, used to identify the subtask in the target task; subtask management function identifier or subtask function identifier, used to indicate the subtask management function for managing the subtask in the target task or the subtask function for executing the subtask in the target task; subtask policy or subtask quality information, used to indicate the service quality requirements of the subtask in the target task; first information, used to indicate the demand information corresponding to the target task requested to be released; subtask execution order; release reason, used to indicate the reason for requesting to release the target task or the subtask in the target task; release type, used to indicate the type of resource requested to be released; first indication, used to indicate the deletion of the subtask policy or subtask quality information corresponding to the subtask in the target task; third indication, used to indicate the power status of the terminal.

[0321] In an optional implementation, the release reason includes at least one of the following: regular release; network switching; temporary release; insufficient resources; semantic error; or grammatical error.

[0322] In an optional implementation, the release type includes at least one of the following: releasing a predefined resource combination; releasing resources corresponding to subtasks in the target task; and releasing all resources corresponding to the target task.

[0323] In an optional implementation, the release operation of the target task or the subtask in the target task is performed according to the first message, including: determining the subtask management function or subtask function corresponding to the subtask in the target task; sending a third message to the subtask management function or subtask function according to the first message, and the third message is used to request the release of the subtask in the target task; receiving a third response from the subtask management function or subtask function, and the third response is used to indicate whether the subtask in the target task is successfully released.

[0324] In an optional implementation, determining the subtask management function or subtask function corresponding to the subtask in the target task includes: determining the subtask management function or subtask function corresponding to the subtask in the target task based on at least one of the following: at least one of the subtask management function identifier, subtask function identifier, subtask session identifier, subtask policy or subtask quality information contained in the first message; the task context corresponding to the target task stored in the first network element, the task context including the association relationship between the target task and the task-related information of the target task.

[0325] In an optional implementation, the third message includes at least one of the following: the terminal identifier; the subtask identifier; the subtask function identifier corresponding to the subtask; the subtask strategy or subtask quality information.

[0326] In an optional implementation, when the third response indicates that the subtask in the target task is not released successfully, the third response includes a reason for the release failure.

[0327] In an optional implementation, the reason for the release failure includes at least one of the following: the subtask is in use; the subtask does not exist; the subtask function corresponding to the subtask does not exist; the resource corresponding to the subtask does not exist.

[0328] In an optional implementation, the task releasing module 720 is further configured to release at least a portion of the task context of the target task.

[0329] In an optional implementation, releasing at least part of the task context of the target task includes at least one of the following: deleting the task context of the target task; deleting the task context of the subtask in the target task; deleting the task strategy or task quality information in the task context of the target task; deleting the subtask strategy or subtask quality information in the task context of the target task.

[0330] In an optional implementation, the task context of the target task includes at least one of the following: the task context stored locally by the first network element; the task context sent by the first network element to a third network element, where the third network element is a network element other than the first network element.

[0331] In an optional implementation, the task release module 720 is also used to: verify whether the first message is allowed or authorized; and when it is determined that the first message is allowed or authorized, execute the step of releasing the target task or the subtask in the target task according to the first message.

[0332] In an optional implementation, the verification of whether the first message is allowed or authorized includes: when the task identifier carried by the first message is stored in the first network element, determining that the first message is allowed or authorized; 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, determining that the first message is not allowed or authorized.

[0333] In an optional implementation, when the first response indicates that the release result of the target task or a subtask in the target task is a failure, the first response includes a reason for the release failure.

[0334] In an optional implementation, the reasons for the release failure include at least one of the following: the target task is in progress; the target task does not exist; the release of the target task is not allowed or authorized; the terminal has no task contract for the target task; the subtask in the target task is in use; the subtask in the target task does not exist; the subtask function corresponding to the subtask in the target task does not exist; the subtask resource corresponding to the subtask in the target task does not exist; the subtask management function corresponding to the target task is not queried; the first message is not allowed or authorized.

[0335] In an optional implementation, the subtask includes at least one of the following: a communication subtask; a perception subtask; a computing subtask; a data subtask; a positioning subtask; an IMS subtask; or an AI subtask.

[0336] In the embodiments of the present application, the task release device 700 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, but is not limited to, a network-side device. For example, the terminal can include, but is not limited to, the types of network-side devices 12 listed above, and this embodiment of the present application does not specifically limit this.

[0337] The task processing device 700 provided in the embodiment of the present application can realize Figure 5 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0338] like Figure 8 As shown, an embodiment of the present application further provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instruction that can be executed on the processor 801. For example, when the communication device 800 is a terminal, the program or instruction, when executed by the processor 801, implements the various steps of the above-mentioned task processing method embodiment 200 or 300, and can achieve the same technical effect. When the communication device 800 is a network-side device, the program or instruction, when executed by the processor 801, implements the various steps of the above-mentioned task processing method embodiment 500, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0339] The embodiment of the present application further provides a terminal, comprising 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 following Figure 2 or Figure 3 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 9 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0340] The terminal 900 includes but is not limited to: a radio frequency unit 901, a network module 902, an audio output unit 903, an input unit 904, a sensor 905, a display unit 906, a user input unit 907, an interface unit 908, a memory 909 and at least some of the components of the processor 910.

[0341] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) to power each component. The power supply can be logically connected to the processor 910 through a power management system, thereby realizing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 9The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0342] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 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 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 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.

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

[0344] The memory 909 can be used to store software programs or instructions and various data. The memory 909 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 909 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 a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

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

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

[0347] In an optional implementation, the first message includes at least one of the following: task description information, used to indicate the type of the target task; data network name DNN; single network slice selection auxiliary information S-NSSAI; task policy or service quality task quality information, used to indicate the service quality requirements of the target task; task identifier or task session identifier, used to identify the target task; subtask identifier or subtask session identifier, used to identify the subtask in the target task; subtask management function identifier or subtask function identifier, used to indicate the subtask management function for managing the subtask in the target task or the subtask function for executing the subtask in the target task; subtask policy or subtask quality information, used to indicate the service quality requirements of the subtask in the target task; first information, used to indicate the demand information corresponding to the target task requested to be released; subtask execution order; release reason, used to indicate the reason for requesting to release the target task or the subtask in the target task; release type, used to indicate the type of resources requested to be released; first indication, used to indicate the deletion of the subtask policy or subtask quality information corresponding to the subtask in the target task.

[0348] In an optional implementation, the release reason includes at least one of the following: regular release; network switching; temporary release; insufficient resources; semantic error; or grammatical error.

[0349] In an optional implementation, the release type includes at least one of the following: releasing a predefined resource combination; releasing resources corresponding to subtasks in the target task; and releasing all resources corresponding to the target task.

[0350] In an optional implementation, the terminal sends a first message to a first network element, including: when a first condition is met, the terminal sends the first message to the first network element; wherein, the first condition includes at least one of the following: the terminal expects to release the target task or a subtask in the target task; the terminal has turned on power saving mode or the battery level of the terminal is lower than a first threshold; the terminal receives a second indication, and the second indication is used to instruct the terminal to fall back to a specific customized network, release the target task, release the task connection corresponding to the target task, and release at least one of the subtasks in the target task; the terminal receives a second message sent by the second network element, and the second message is used to request the terminal to release the target task or the subtask in the target task; the timer times out, wherein the timer is started when the target task or the subtask in the target task is successfully established.

[0351] In an optional implementation, 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 also includes a third indication, and the third indication is used to indicate the battery status of the terminal.

[0352] In an optional implementation, when the first response indicates that the release result of the target task or a subtask in the target task is a failure, the first response includes a reason for the release failure.

[0353] In an optional implementation, the reasons for the release failure include at least one of the following: the target task is in progress; the target task does not exist; the release of the target task is not allowed or authorized; the terminal has no task contract for the target task; the subtask in the target task is in use; the subtask in the target task does not exist; the subtask function corresponding to the subtask in the target task does not exist; the subtask resource corresponding to the subtask in the target task does not exist; the subtask management function corresponding to the target task is not queried; the first message is not allowed or authorized.

[0354] In an optional implementation, the subtask includes at least one of the following: a communication subtask; a perception subtask; a computing subtask; a data subtask; a positioning subtask; an IMS subtask; or an AI subtask.

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

[0356] The embodiment of the present application further 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 used to run a program or instruction to implement the following Figure 5 The network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation method of the above method embodiment are applicable to the network side device embodiment and can achieve the same technical effect.

[0357] Specifically, the embodiment of the present application also provides a network side device. Figure 10 As shown, the network side device 1000 includes: a processor 1001, a network interface 1002 and a memory 1003. The network interface 1002 is, for example, a common public radio interface (CPRI).

[0358] Specifically, the network side device 1000 of the embodiment of the present application further includes: instructions or programs stored in the memory 1003 and executable on the processor 1001, and the processor 1001 calls the instructions or programs in the memory 1003 to execute Figure 5 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

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

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

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

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

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

[0364] 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 implement the various processes of the above-mentioned task processing method embodiment 200 or 300, and the network-side device can be used to implement the various processes of the above-mentioned task processing method embodiment 500, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

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

[0367] 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, characterized in that: include: The terminal sends a first message to the first network element, where the first message is used to request to release the 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 release 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: Task description information, used to indicate the type of the target task; Data network name DNN; Single Network Slice Selection Assistance Information S-NSSAI; Task strategy or task quality information, used to indicate the service quality requirements of the target task; A task identifier or a task session identifier, used to identify the target task; A subtask identifier or a subtask session identifier, used to identify a subtask in the target task; A subtask management function identifier or a subtask function identifier, used to indicate a subtask management function for managing a subtask in the target task or a subtask function for executing a subtask in the target task; Subtask strategy or subtask quality information, used to indicate the service quality requirements of the subtasks in the target task; The first information is used to indicate the requirement information corresponding to the target task requested to be released; Subtask execution order; A release reason, used to indicate the reason for requesting to release the target task or a subtask within the target task; Release type, used to indicate the type of resource requested to be released; The first instruction is used to instruct deletion of the subtask strategy or subtask quality information corresponding to the subtask in the target task.

3. The method according to claim 2, wherein The release reason includes at least one of the following: Regular release; Network switching; temporary release; Insufficient resources; Semantic errors; Syntax error.

4. The method according to claim 2, wherein The release type includes at least one of the following: Release predefined resource combinations; Release the resources corresponding to the subtasks in the target task; Release all resources corresponding to the target task.

5. The method according to any one of claims 1 to 4, wherein The terminal sending a first message to the first network element includes: When a first condition is met, the terminal sends the first message to the first network element; The first condition includes at least one of the following: The terminal expects to release 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 receives a second instruction, where the second instruction is used to instruct the terminal to fall back to a specific format network, release the target task, release a task connection corresponding to the target task, and release at least one of a subtask in the target task; The terminal receives a second message sent by a second network element, where the second message is used to request the terminal to release the target task or a subtask in the target task; The timer times out, wherein the timer is started when the target task or a subtask in the target task is successfully established.

6. The method according to claim 5, wherein In the case where the first condition includes that the terminal has activated the power saving mode or the battery level of the terminal is lower than a first threshold, the first message further includes a third indication, where the third indication is used to indicate the battery status of the terminal.

7. The method according to any one of claims 1 to 6, wherein In a case where the first response indicates that the release result of the target task or a subtask in the target task is a failure, the first response includes a reason for the release failure.

8. The method according to claim 7, wherein The reasons for the release failure include at least one of the following: The target tasks are in progress; The target task does not exist; Releasing the target task is not allowed or authorized; The terminal does not have a task contract for the target task; The subtask in the target task is in use; The subtask in the target task does not exist; The subtask function corresponding to the subtask in the target task does not exist; The subtask resource corresponding to the subtask in the target task does not exist; The subtask management function corresponding to the target task was not found; The first message is not allowed or not authorized.

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

10. A task processing method, characterized in that: include: The first network element receives a first message from the terminal, where the first message is used to request the release of a target task or a subtask in the target task; The first network element performs a release operation on 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 release 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: Task description information, used to indicate the type of the target task; Data network name DNN; Single Network Slice Selection Assistance Information S-NSSAI; Task strategy or task quality information, used to indicate the service quality requirements of the target task; A task identifier or a task session identifier, used to identify the target task; A subtask identifier or a subtask session identifier, used to identify a subtask in the target task; A subtask management function identifier or a subtask function identifier, used to indicate a subtask management function for managing a subtask in the target task or the subtask function for executing a subtask in the target task; Subtask strategy or subtask quality information, used to indicate the service quality requirements of the subtasks in the target task; The first information is used to indicate the requirement information corresponding to the target task requested to be released; Subtask execution order; A release reason, used to indicate the reason for requesting to release the target task or a subtask within the target task; Release type, used to indicate the type of resource requested to be released; A first instruction is used to instruct deletion of the subtask strategy or task quality information corresponding to the subtask in the target task; The third indication is used to indicate the battery status of the terminal.

12. The method according to claim 11, wherein The release reason includes at least one of the following: Regular release; Network switching; temporary release; Insufficient resources; Semantic errors; Syntax error.

13. The method according to claim 11, wherein The release type includes at least one of the following: Release predefined resource combinations; Release the resources corresponding to the subtasks in the target task; Release all resources corresponding to the target task.

14. The method according to any one of claims 10 to 13, wherein: The first network element performs a release operation on the target task or a subtask in the target task according to the first message, including: The first network element determines a subtask management function or a subtask function corresponding to a subtask in the target task; The first network element sends a third message to the subtask management function or the subtask function according to the first message, where the third message is used to request to release the subtask in the target task; The first network element receives a third response from the subtask management function or the subtask function, where the third response is used to indicate whether the subtask in the target task is successfully released.

15. The method according to claim 14, wherein The first network element determines a subtask management function or a subtask function corresponding to a subtask in the target task, including: The first network element determines a subtask management function or a subtask function corresponding to a subtask in the target task according to at least one of the following: at least one of a subtask management function identifier, a subtask function identifier, a subtask session identifier, a subtask strategy, or subtask quality information included in the first message; The task context corresponding to the target task stored in the first network element includes an association relationship between the target task and task-related information of the target task.

16. The method according to claim 15, wherein The third message includes at least one of the following: the terminal identification; The subtask identifier; The subtask function identifier corresponding to the subtask; The subtask strategy or subtask quality information.

17. The method according to claim 15, wherein In a case where the third response indicates that the subtask in the target task is not released successfully, the third response includes a reason for the release failure.

18. The method according to claim 17, wherein The reasons for the release failure include at least one of the following: The subtask is in use; The subtask does not exist; The subtask function corresponding to the subtask does not exist; The resource corresponding to the subtask does not exist.

19. The method according to any one of claims 14 to 18, wherein The method further comprises: The first network element releases at least part of the task context of the target task.

20. The method according to claim 19, wherein The first network element releasing at least part of the task context of the target task includes at least one of the following: Deleting, by the first network element, the task context of the target task; Deleting, by the first network element, a task context of a subtask in the target task; The first network element deletes the task policy or task quality information in the task context of the target task; The first network element deletes the subtask policy or subtask quality information in the task context of the target task.

21. The method according to claim 19 or 20, wherein: The task context of the target task includes at least one of the following: The task context stored locally by the first network element; The first network element sends a task context to a third network element, where the third network element is a network element other than the first network element.

22. The method according to any one of claims 14 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 it is determined that the first message is allowed or authorized, the step of performing a release operation on the target task or a subtask in the target task according to the first message is performed.

23. The method according to claim 22, wherein The verifying whether the first message is allowed or authorized includes: When the task identifier carried by the first message is stored in the first network element, determining whether the first message is allowed or authorized; In a case where 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 is determined that the first message is not allowed or authorized.

24. The method according to any one of claims 10 to 23, wherein In a case where the first response indicates that the release result of the target task or a subtask in the target task is a failure, the first response includes a reason for the release failure.

25. The method of claim 24, wherein: The reason for the release failure included in the first response includes at least one of the following: The target tasks are in progress; The target task does not exist; Releasing the target task is not allowed or authorized; The terminal does not have a task contract for the target task; The subtask in the target task is in use; The subtask in the target task does not exist; The subtask function corresponding to the subtask in the target task does not exist; The subtask resource corresponding to the subtask in the target task does not exist; The subtask management function corresponding to the target task was not found; The first message is not allowed or not authorized.

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

27. A task processing device, characterized in that: include: A sending module, configured to send a first message to a first network element, wherein the first message is used to request the release 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, wherein the first response is used to indicate a release result of the target task or a subtask in the target task.

28. The device according to claim 27, wherein The sending the first message to the first network element includes: When a first condition is met, sending the first message to the first network element; The first condition includes at least one of the following: The terminal expects to release 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 receives a second instruction, where the second instruction is used to instruct the terminal to fall back to a specific customized network, release the target task, release a task connection corresponding to the target task, and release at least one of a subtask in the target task; The terminal receives a second message sent by a second network element, where the second message is used to request the terminal to release the target task or a subtask in the target task; The timer times out, wherein the timer is started when the target task or a subtask in the target task is successfully established.

29. A task processing device, characterized in that: include: A receiving module, configured to receive a first message from a terminal, wherein the first message is used to request the release of a target task or a subtask in the target task; A task releasing module, configured to execute a release operation on 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, wherein the first response is used to indicate a release result of the target task or a subtask in the target task.

30. The device according to claim 29, wherein The performing a release operation on the target task or a subtask in the target task according to the first message includes: Determine the subtask management function or subtask function corresponding to the subtask in the target task; Sending a third message to the subtask management function or the subtask function according to the first message, wherein the third message is used to request to release the subtask in the target task; A third response is received from the subtask management function or the subtask function, where the third response is used to indicate whether the subtask in the target task is successfully released.

31. A terminal, characterized in that: The method comprises 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.

32. A network side device, characterized in that: The method comprises 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 10 to 26 are implemented.

33. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, 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, or the steps of the method according to any one of claims 10 to 26 are implemented.

Images