Task processing method and apparatus, and related device

Abstract

The present application belongs to the technical field of communications. Disclosed are a task processing method and apparatus, and a related device. The task processing method in the embodiments of the present application comprises: a first network element receiving a first message sent by a second network element, wherein the first message is used for requesting the release of a target task or sub-tasks of the target task; and the first network element executing a release operation for the target task or the sub-tasks of the target task, wherein the sub-tasks of the target task comprise at least one of the following: a sensing sub-task, a computing sub-task, an artificial intelligence (AI) sub-task, a data sub-task, a positioning sub-task, a communication sub-task, an IP multimedia subsystem (IMS) sub-task, an information processing sub-task and an immersive sub-task.

Description

Task processing method, device and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

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

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

[0004] Traditional communication systems are connection-oriented. Typical applications involve providing connections between specific terminals or between terminals and application servers. The network architecture provides a complete lifecycle management mechanism and Quality of Service (QoS) guarantees for sessions. Release operations in traditional communication systems are always performed on a connection-by-connection basis. If a new service is triggered, the connection must be re-established and the corresponding resources must be requested, resulting in lengthy service processing times. Summary of the Invention

[0005] The embodiments of the present application provide a task processing method, apparatus, and related equipment, which can solve the problem of long service processing time in traditional communication systems.

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

[0007] The first network element receives a first message sent by the second network element, where the first message is used to request the release of a target task or a subtask of the target task;

[0008] The first network element performs a release operation on the target task or a subtask of the target task according to the first message;

[0009] Among them, the target task includes at least one subtask, and the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

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

[0011] The second network element sends a first message to the first network element, where the first message is used to request the release of the target task or a subtask of the target task;

[0012] Among them, the target task includes at least one subtask, and the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

[0013] In a third aspect, a task processing device is provided, comprising:

[0014] A receiving module, configured to receive a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of the target task;

[0015] An execution module, configured to execute a release operation on the target task or a subtask of the target task;

[0016] Among them, the target task includes at least one subtask, and the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

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

[0018] 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 of the target task;

[0019] Among them, the target task includes at least one subtask, and the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

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

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

[0022] receiving a first message sent by a second network element, where the first message is used to request the release of a target task or a subtask of the target task;

[0023] The processor is configured to: perform a release operation on the target task or a subtask of the target task;

[0024] Among them, the target task includes at least one subtask, and the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

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

[0026] Sending a first message to a first network element, where the first message is used to request the release of a target task or a subtask of the target task;

[0027] Among them, the target task includes at least one subtask, and the subtasks of the target task include at least one of the following: perception subtask, computing subtask, artificial intelligence AI subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem IMS subtask, information processing subtask, and immersive subtask.

[0028] In an eighth 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 or the steps of the method described in the second aspect are implemented.

[0029] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

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

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

[0032] In an embodiment of the present application, a first network element receives a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of a target task; the first network element performs a release operation on the target task or a subtask of the target task; wherein the subtask of the target task includes at least one of the following: a perception subtask, a computing subtask, an artificial intelligence AI subtask, a data subtask, a positioning subtask, a communication subtask, an IP multimedia subsystem IMS subtask, an information processing subtask, and an immersive subtask. In this way, by performing a release operation on the target task or a subtask of the target task, release based on tasks or subtasks can be achieved, so that when a new service is triggered, the resources corresponding to the service can be directly requested, which can reduce the processing time of the service; further, the embodiment of the present application can also support the release of multiple subtasks of the target task through one signaling message. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

[0038] FIG6 is a fifth flow chart of a task processing method provided in an embodiment of the present application;

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

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

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

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

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

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

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

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

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

[0048] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer, a 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, 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), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

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

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

[0051] Communication, perception, and computing are the three most important foundational capabilities for building a freely connected physical and digital world. 6G will natively support communication, perception, and computing services, which means 6G networks will need to introduce a new resource dimension. Unlike existing connection-oriented designs, 6G systems will adopt a task-oriented design.

[0052] Unlike traditional communications services, artificial intelligence (AI) is a data- and compute-intensive service. To enable 6G networks to have native AI capabilities, 6G networks need to introduce new resource dimensions, including heterogeneous computing and storage resources, new computing subtasks (such as AI-related computing), and new data types (such as AI computing input and output data). Corresponding management and control mechanisms need to be designed. On the other hand, 6G networks will have more comprehensive perception capabilities, including target detection, positioning (distance and angle), speed measurement, and three-dimensional (3D) imaging, and will introduce solutions based on radar echoes. These new network capabilities, such as AI or perception capabilities, will involve the coordination and deployment of computing power, connectivity, algorithms, and data resources in multi-node scenarios to jointly achieve a specific goal.

[0053] The existing 5G system can only provide a pipeline for data transmission. The corresponding deletion of the end-to-end communication tunnel only targets communication resources, and cannot support the release of communication, perception, and computing resources required for the execution of 6G network tasks.

[0054] Since network resources are limited, if resources are not released in a timely and reasonable manner after the task is completed, it will put great pressure on network resource management and may not be able to meet the needs of subsequent tasks.

[0055] To facilitate understanding of the technical solutions provided by this application, the relevant technical features involved in this application are explained below. The content is as follows.

[0056] 1. Mission: A comprehensive set of services including communication, information, synaesthesia, and computing that the 6G system provides on-demand based on external service requests. These external service requests can come from user equipment (UE) or over-the-top (OTT) services.

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

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

[0059] 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086] Task description: Automatic parking.

[0087] Task type: Multi-tasking.

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

[0089] Subtask type: perception subtask.

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

[0091] Subtask type: Computational subtask

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

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

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

[0095] Task session: refers to the process of communication between a UE and a TM, or 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 a 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 task bearer. A task session or subtask session can sometimes also be implemented by a Protocol Data Unit (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 use some non-standard methods to transfer it to the perception execution node.

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

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

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

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

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

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

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

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

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

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

[0106] a) Task description information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0132] Step 101: A first network element receives a first message sent by a second network element, where the first message is used to request the release of a target task or a subtask of the target task.

[0133] Step 102: The first network element performs a release operation on the target task or a subtask of the target task according to the first message;

[0134] The target task includes at least one subtask, and the subtask of the target task includes at least one of the following:

[0135] Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, Internet Protocol (IP) multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

[0136] The first message may be used to request the release of a target task, or the first message may be used to request the release of a subtask of the target task. The first network element may perform a release operation on the target task, or the first network element may perform a release operation on a subtask of the target task.

[0137] In one implementation, the first message is used to request the release of a target task, and the first network element may perform a release operation on the target task or a subtask of the target task.

[0138] In one embodiment, the first message may be used to request the release of a subtask of the target task, and the first network element may perform a release operation on the subtask of the target task. For example, the subtask of the target task may include a perception subtask, the first message may be used to request the release of the perception subtask, and the first network element may perform a release operation on the perception subtask; or, the subtask of the target task may include a computing subtask, the first message may be used to request the release of the computing subtask, and the first network element may perform a release operation on the computing subtask; or, the subtask of the target task may include an artificial intelligence (AI) task, the first message may be used to request the release of the AI ​​subtask, and the first network element may perform a release operation on the AI ​​subtask.

[0139] It should be noted that a task can refer to an integrated service, including communication, information, interpersonal communication, and computing, or a collection of integrated services, provided on-demand by a network system (such as a 6G network system) based on external service requests (including services requested by UEs, over-the-top (OTT) services, or services requested by AFs). A task is composed of subtasks, which can also be described as a service, business, or event. A subtask of a task can be described as a task within a service, business, or event. For example, a subtask can be a service or task within an integrated service including communication, information, interpersonal communication, and computing.

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

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

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

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

[0144] It should be noted that the target task may be an established task that meets at least one of the following conditions: a subtask management function or a subtask execution function corresponding to the task has allocated corresponding resources to the task; and a task context for the task has been established.

[0145] In addition, the release operation may include: deleting the task; releasing the allocated task resources; deleting the subtasks of the target task; deleting the task context; deleting the subtask management function corresponding to the target task; or deleting the address of the subtask execution node corresponding to the target task, etc.

[0146] In one embodiment, the release operation can be used to release the resource occupation related to the task or subtask, so that other tasks or subtasks can use the released resources, which include: communication resources, computing resources or data resources, etc.; or, the release operation can be used to delete information related to the task strategy in the task or subtask.

[0147] In one implementation, the first message may be a task release request message, a task resource release request message, a service release request message, or a business release request message, etc., which is not limited in this embodiment.

[0148] It should be noted that the release request and release execution in the related art are only for communication resources or a single type of network resources. The embodiment of the present application can realize the release of multiple subtasks of the target task through a signaling message (such as the first message).

[0149] The embodiments of the present application can solve the problem of how the network releases the network resources allocated for a task when a second network element (such as AF or OTT) initiates a release request, aiming to rationally utilize resources and provide the possibility of meeting the task requirements of a large number of second network elements. The embodiments of the present application can support the release of resources allocated to the task by performing a release operation on the target task or a subtask of the target task, thereby increasing the availability of network resources.

[0150] Taking the first network element as TM and the second network element as AF as an example, the AF initiates a task release request and indicates the release reason and release type.

[0151] TM performs task release operations, including at least one of the following: releasing task resources (such as one or more of perception, computing, and AI resources), deleting subtasks, and deleting task contexts.

[0152] It should be noted that in the embodiment of the present application, the first network element is a TM and the second network element is an AF. The TM can be a newly added TM network element, or network elements in the core network (such as AMF, SMF, PCF, NEF) can be enhanced to implement the functions of the TM. For example, the PCF and TM are not limited to being co-located. In this case, the AF initiates a task request to the PCF, and the PCF is responsible for all or part of the functions of the TM.

[0153] In the embodiment of the present application, only the case of direct interaction between the AF and the TM is described, but it is not limited to whether there is a transit node, for example, it is not limited to the presence of an NEF or other control node. In this case, the messages between the AF and the TM can be transmitted through the NEF or other control nodes.

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

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

[0156] In an embodiment of the present application, a first network element receives a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of a target task; the first network element performs a release operation on the target task or a subtask of the target task; wherein the subtask of the target task includes at least one of the following: a perception subtask, a computing subtask, an artificial intelligence AI subtask, a data subtask, a positioning subtask, a communication subtask, an IP multimedia subsystem IMS subtask, an information processing subtask, and an immersive subtask. In this way, by performing a release operation on the target task or a subtask of the target task, release based on tasks or subtasks can be achieved, so that when a new service is triggered, the resources corresponding to the service can be directly requested, which can reduce the processing time of the service; further, the embodiment of the present application can also support the release of multiple subtasks of the target task through one signaling message.

[0157] Optionally, the release operation includes at least one of the following:

[0158] Release the resources corresponding to the target task or the subtask of the target task;

[0159] Delete the task context corresponding to the target task or a subtask of the target task.

[0160] The task context corresponding to the target task or the subtask of the target task may include the address of the subtask management function or the address of the subtask execution function corresponding to the target task.

[0161] In addition, the resource corresponding to the target task or the subtask of the target task may refer to a network resource established based on the target task or the subtask of the target task.

[0162] In one embodiment, releasing the resources corresponding to the target task or the subtask of the target task may include sending a task release request to the subtask management function or subtask execution function corresponding to the target task, requesting the subtask management function or subtask execution function to release the resources allocated to the subtask of the target task.

[0163] In one embodiment, deleting the task context corresponding to the target task or the subtask of the target task may include deleting the stored task context of the target task or the subtask of the target task. The stored task context includes a task context stored locally by the first network element or a task context stored on another network element. The first network element may directly delete the locally stored task context, or the first network element may send a deletion request to the network element storing the task context to delete the task context stored on the other network element.

[0164] In this implementation, by releasing the resources corresponding to the target task or the subtask of the target task, the resources can be reasonably released after the task is completed. The released task resources can be used for the needs of subsequent tasks, which is beneficial to network resource management; or, deleting the task context corresponding to the target task or the subtask of the target task can avoid the subtask occupying resources.

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

[0166] Task description information, used to indicate the type of the target task;

[0167] Data network name DNN information;

[0168] Slice information;

[0169] Mission strategy information;

[0170] Task quality information QoT, used to indicate the service quality requirement of the target task;

[0171] A task identifier, or task session identifier, is used to identify the target task;

[0172] An identifier of a subtask management function, used to indicate a subtask management function for managing subtasks in the target task or a subtask function for executing subtasks in the target task;

[0173] Identification of the subtask execution function;

[0174] Subtask strategy information;

[0175] Subtask requirement information, used to indicate the service quality requirements of the subtasks in the target task;

[0176] A subtask identifier, or subtask session identifier, is used to identify a subtask in the target task;

[0177] The identity of the task template;

[0178] First instruction information for indicating the execution order of subtasks;

[0179] second indication information used to indicate the reason for requesting to release resources;

[0180] third indication information for indicating a resource release type;

[0181] The task template is used to represent task requirement information. The identifier of the task template may implicitly indicate the resource type included, and the resource type included may include at least one of communication resources, perception resources, computing resources, and AI resources.

[0182] In addition, the indication information for indicating the reason for requesting to release resources may indicate: regular release, normal release, temporary release, network switching, insufficient resources, semantic error or grammatical error, etc.

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

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

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

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

[0187] A task template can be a description of a customized task, which can be understood as a questionnaire. The requester "checks" certain required or optional parameters on the questionnaire to express their requirements for the task. The task template can include at least one of the following: a task template identifier, used to identify the task template; task description information; task quality information; task strategy information; and task parameters. Task parameters: These are parameters used to indicate the task, and may include subtask configuration information. For example, if the target task includes both a perception task and a computation task, the task parameters include both the perception task configuration information and the computation task configuration information.

[0188] The subtask execution function may also be described as a subtask function or a subtask execution node. The identifier of the task template may be simply described as a task template indication. The indication information for indicating the subtask execution order may be simply described as a subtask execution order indication. The task description information may also be simply described as a task description; the task strategy information may also be simply described as a task strategy; the subtask strategy information may also be simply described as a subtask strategy; and the DNN information may also be simply described as a DNN. The slice information may include S-NSSAI.

[0189] In addition, the identifier of the subtask management function may include but is not limited to an identifier (ID), an Internet Protocol (IP) address, and a fully qualified domain name (FQDN). The identifier of the subtask execution function may include but is not limited to an ID, an IP address, and an FQDN.

[0190] It should be noted that when the first network element establishes a target task, the second network element can obtain from the first network element the subtasks included in the target task and the corresponding subtask execution functions. For example, the second network element may receive an execution result from the corresponding subtask execution function, for example, the execution result indicates that the subtask function has insufficient resources and cannot meet the subtask quality. The second network element can send a first message to the first network element to request the release of the corresponding subtask. The first message can carry an identifier of the subtask execution function to request the release of the corresponding subtask.

[0191] In one embodiment, the first network element can determine the target task or the subtask of the target task through one or more of the task description information, DNN information, slicing information, task strategy information, QoT, task identifier, task template identifier, subtask identifier, subtask management function identifier, subtask execution function identifier, subtask requirement information and subtask strategy information carried by the first message, and then perform a release operation on the target task or the subtask of the target task.

[0192] For example, the first network element can determine the target task through one or more of the task description information, DNN information, slicing information, task strategy information, QoT, task identifier, and task template identifier carried by the first message, and then perform a release operation on the target task or a subtask of the target task.

[0193] For example, the first network element can determine the target task through one or more of the task description information, DNN information, slicing information, task strategy information, QoT, task identifier, and task template identifier carried by the first message, and determine one or more subtasks of the target task through one or more of the subtask management function identifier, subtask execution function identifier, subtask identifier, subtask requirement information, and subtask strategy information carried by the first message, and then perform a release operation on the one or more subtasks.

[0194] For example, the first network element may determine one or more subtasks of the target task through the identifier of the task template or the subtask requirement information or the subtask strategy information carried in the first message, and then perform a release operation on the one or more subtasks.

[0195] In one implementation, the first network element may determine the resource type through the identifier of the task template carried in the first message, and further determine the type of released resources.

[0196] In one implementation, the first network element may release the resources of the subtasks in the order in which the subtasks are executed, using the indication information for indicating the order in which the subtasks are executed carried in the first message.

[0197] In one implementation, the first network element may learn the reason why the second network element requests to release resources through indication information carried in the first message and used to indicate the reason for requesting to release resources.

[0198] In one implementation, the first network element may determine the type of released resources through indication information carried in the first message for indicating the type of resource release.

[0199] Optionally, the third indication information indicates at least one of the following:

[0200] Release perception resources; release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.

[0201] Among them, the predefined resource combination may include a resource combination consisting of at least one of communication resources, perception resources, computing resources and AI resources.

[0202] In one implementation, the indication information for indicating the resource release type may indicate at least one of the following:

[0203] Release one or more resources, such as instructing to release at least one of perception resources, computing resources, and AI resources;

[0204] Releasing a predefined resource combination, such as indicating to release a certain predefined resource combination. For example, the predefined resource combination may be sensing resources + computing resources;

[0205] Release all resources, such as indicating to release all resources. For example, all resources include perception resources+computing resources+AI resources+data storage resources.

[0206] Optionally, the first message further includes fourth indication information used to instruct the second network element to trigger sending the first message based on at least one of the following:

[0207] The second network element expects to release the target task or a subtask of the target task;

[0208] The second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;

[0209] The timer corresponding to the target task times out.

[0210] Among them, the reason why the second network element expects to release the target task or the subtask of the target task may include at least one of the following: the second network element closes the application associated with the target task; the available resources of the second network element are less than a preset threshold; the second network element cannot provide relevant data of the target task.

[0211] In one implementation, after the target task is established, the second network element may start a timer, and when the timer times out, the second network element may send a first message to the first network element.

[0212] For example, if the first network element is a TM and the second network element is an AF, the conditions for the AF to send a task release request include at least one of the following:

[0213] AF expects to release tasks, including at least one of the following: AF closes the application (Application, APP), AF resources are insufficient, and AF privacy is restricted.

[0214] The AF receives a task release request from the UE through the application layer. The task information included in the task release request is consistent with the task information carried in the first message. For example, the task information included in the task release request and the task information carried in the first message are information about the same task.

[0215] The timer maintained by AF times out. AF will start a timer after the task is successfully established. When the timer times out, AF will initiate a task release request.

[0216] In this embodiment, when the second network element expects to release the target task or the subtask of the target task, the second network element sends a first message to the first network element, so that the second network element can actively request to release the target task or the subtask of the target task; or, when the second network element receives a request message sent by the terminal to request the release of the target task or the subtask of the target task, the second network element sends a first message to the first network element, so that the second network element can send a request to release the target task or the subtask of the target task based on the request of the terminal; or, when the timer corresponding to the target task times out, the second network element sends a first message to the first network element, so that the second network element can request to release the target task or the subtask of the target task based on the timeout of the timer corresponding to the target task.

[0217] Optionally, when the second network element meets the first condition, the second network element expects to release the target task or a subtask of the target task:

[0218] The first condition includes at least one of the following:

[0219] The second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.

[0220] The second network element cannot provide relevant data of the target task, which may indicate that the privacy of the second network element is limited.

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

[0222] The first network element sends a second message corresponding to the first message to the second network element;

[0223] The second message is used to indicate whether the release operation is executed successfully or fails.

[0224] Taking the first message as a task release request message as an example, the second message can be a task release response message; taking the first message as a task resource release request message as an example, the second message can be a task resource release response message; taking the first message as a service release request message as an example, the second message can be a service release response message; taking the first message as a business release request message as an example, the second message can be a business release response message.

[0225] In this embodiment, the first network element sends a second message corresponding to the first message to the second network element; the second message is used to indicate that the release operation is executed successfully or the release operation fails, so that the second network element can obtain the release result of the target task or the subtask of the target task through the second message.

[0226] Optionally, when the release operation fails, the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:

[0227] The target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

[0228] The non-existence of the target task can be understood as the target task requested to be released by the second network element has not been established or the first network element has already released the target task locally. The first network element can determine that the target task does not exist when it is determined that the network has not allocated network resources for the target task. The non-existence of a subtask of the target task can be understood as the subtask of the target task requested to be released by the second network element has not been established or the first network element has already released the subtask of the target task locally. The first network element can determine that the target task does not exist when it is determined that the network has not allocated network resources for the subtask of the target task.

[0229] In addition, the target task is not authorized, which can be understood as no service level agreement on the target task is signed between the first network element and the second network element, or no service level agreement is signed between the second network element and the first network element.

[0230] In one embodiment, the first message can be used to request the release of the target task, and the first indication information is used to indicate at least one of the following: the target task is in an execution state; the target task does not exist; the target task is not authorized; the target task has no task contract; the subtask of the target task is in an execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

[0231] In one embodiment, the first message can be used to request the release of a subtask of the target task, and the first indication information is used to indicate at least one of the following: the target task is in an execution state; the target task does not exist; the target task is not authorized; the target task has no task contract; the subtask of the target task is in an execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

[0232] Optionally, the first network element performs a release operation on the target task or a subtask of the target task, including the first network element determining a subtask management function or a subtask execution function corresponding to the target task;

[0233] The first network element sends a third message to the subtask management function or the subtask execution function, where the third message is used to request the release of the subtask of the target task.

[0234] The first network element may determine the subtask management function or subtask execution function corresponding to the target task according to at least one of the following:

[0235] an identifier of the subtask management function or the subtask execution function carried by the second network element in the first message;

[0236] The subtask management function or subtask execution function identifier stored in the task context of the target task. The first network element stores the task context when the task is established. The task context includes the association relationship between the target task and the subtask management function or subtask execution function.

[0237] Obtain the identifier of the subtask management function or the subtask execution function through query.

[0238] For example, the first network element can query the NRF, UDM or UDR to determine the appropriate subtask management function or subtask function, or the first network element can determine the appropriate subtask management function or subtask function based on stored or maintained information (such as whether the task is supported, the size of computing power, etc.).

[0239] It should be noted that, if the first network element cannot find the associated subtask management function or subtask execution function, the first network element may reject the request of the second network element and indicate that the release operation has failed.

[0240] In one embodiment, the first message can be used to request the release of the target task, and the first network element can determine the management function or execution function of all or part of the subtasks of the target task, and send a third message to the determined subtask management function or subtask execution function.

[0241] In one embodiment, the first message can be used to request the release of one or more subtasks of the target task, and the first network element can determine the management function or execution function of the one or more subtasks, and send a third message to the determined subtask management function or subtask execution function.

[0242] In addition, the third message may be generated by triggering the first message. After receiving the first message, the first network element triggers the generation of the third message and sends the third message to the subtask management function or the subtask execution function.

[0243] It should be noted that in the embodiment of the present application, the subtask management function corresponding to the target task can also be described as the management function or control function of the subtask of the target task; the subtask execution function corresponding to the target task can also be described as the execution function or execution node of the subtask of the target task.

[0244] In this embodiment, the first network element determines the subtask management function or subtask execution function corresponding to the target task; the first network element sends a third message to the subtask management function or subtask execution function, and the third message is used to request the release of the subtask of the target task, so that the first network element can release the subtask of the target task through the subtask management function or subtask execution function corresponding to the target task.

[0245] Optionally, in the case where the subtasks of the target task include a perception subtask, the third message includes at least one of the following: an identifier of the second network element; a perception subtask identifier; a perception execution function address; perception strategy information; perception requirement information; or

[0246] In the case where the subtasks of the target task include a computing subtask, the third message includes at least one of the following: an identifier of the second network element; an identifier of the computing subtask; an address of a computing execution function; computing strategy information; computing requirement information; or

[0247] In the case where the subtasks of the target task include an AI subtask, the third message includes at least one of the following: an identifier of the second network element; an AI subtask identifier; an AI resource node address; AI strategy information; and AI requirement information.

[0248] It should be noted that the network system may include a first network element, a second network element, a third network element, a fourth network element, and a fifth network element. The first network element in the embodiment of the present application may be used for task management. For example, the first network element may include a newly added network element TM, or may be co-located with an existing network element (e.g., AMF, SMF, PCF).

[0249] The second network element may be a third-party server whose content or services are built on top of the basic telecommunications service, for example, an OTT server; or it may be an application function, such as an application function (AF). OTT refers to providing various application services to users via the Internet.

[0250] The third network element can be located between the 6G core network and external third-party application functions (possibly also some internal AFs), responsible for opening up network capabilities and internal network information; all external applications that want to access internal data of the 6G core network need to go through the third network element. The third network element provides corresponding security guarantees to ensure the security of external applications to the 3rd Generation Partnership Project (3GPP) network, and provides functions such as opening up external application requirements or target customization capabilities, subscription to mobility status events, and distribution of AF requests. The third network element can include network opening functions, such as NEF.

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

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

[0253] In addition, the first network element (such as TM) may be a 3GPP internal network element, and may be used to implement one or more of the following functions:

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

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

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

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

[0258] Task description;

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

[0260] Task strategy or QoS description;

[0261] Task parameters.

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

[0263] (1) Task description;

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

[0265] (3) Task strategy or QoS;

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

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

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

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

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

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

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

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

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

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

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

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

[0278] Random establishment;

[0279] concurrent builds;

[0280] Establish by priority.

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

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

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

[0284] Obtained from PCF or policy charging function;

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

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

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

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

[0289] It should be noted that in the embodiments of the present application, a task may refer to a comprehensive service, or a collection of comprehensive services, including communication, information, interawareness, and computing, provided on demand by a network system (such as a 6G network system) based on external service requests (including UE, OTT, or AF). Task management refers to the management process of providing communication functions and other additional network system functions (such as positioning, interawareness, computing, etc.) with the goal of responding to external service requests.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0317] {

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

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

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

[0321] }

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

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

[0324] Alternatively, a task session can refer to the communication process between a UE and a TM, along with related subtask functions. A task session can correspond to one or more subtask sessions (a subtask session refers to the communication process between the TM and a subtask function). Establishing a task session establishes 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, the TM, and related subtask execution functions in the operator's network. A task session is sometimes also referred to as a task connection or task bearer.

[0325] The task session identifier can be used to identify the task session, which is allocated by the UE and sent to the network or allocated by the TM. 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).

[0326] 3 , which is a flow chart of a task processing method provided in an embodiment of the present application. As shown in FIG3 , the task processing method includes the following steps:

[0327] Step 201: A second network element sends a first message to a first network element, where the first message is used to request the release of a target task or a subtask of the target task.

[0328] The subtasks of the target task include at least one of the following:

[0329] Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

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

[0331] Task description information; data network name (DNN) information; slicing information; task strategy information; task quality information (QoT); task identifier; identifier of the subtask management function; identifier of the subtask execution function; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; first indication information for indicating the subtask execution order; second indication information for indicating the reason for requesting resource release; third indication information for indicating the resource release type;

[0332] The task template is used to represent task requirement information.

[0333] Optionally, the third indication information indicates at least one of the following:

[0334] Release perception resources; release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.

[0335] Optionally, the second network element sending the first message to the first network element includes:

[0336] Determining, by the second network element, whether a first condition is met;

[0337] When it is determined that the first condition is met, the second network element sends a first message to the first network element;

[0338] The first condition includes at least one of the following:

[0339] The second network element expects to release the target task or a subtask of the target task;

[0340] The second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;

[0341] The timer corresponding to the target task times out.

[0342] Optionally, when the second network element satisfies the second condition, the second network element expects to release the target task or a subtask of the target task:

[0343] The second condition includes at least one of the following:

[0344] The second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.

[0345] Optionally, after the second network element sends the first message to the first network element, the method further includes:

[0346] The second network element receives a second message corresponding to the first message sent by the first network element;

[0347] The second message is used to indicate whether the release operation is executed successfully or fails.

[0348] Optionally, when the release operation fails, the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:

[0349] The target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

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

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

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

[0353] Example 1:

[0354] As shown in Figure 4, the task processing method includes the following steps:

[0355] Step (1): TM receives the first message;

[0356] Taking the first message as a task release request message as an example, the AF sends a task release request message to the TM, which is used to request the network to release the resources allocated for the task. The task release request message includes at least one of the following:

[0357] Task description information (e.g., “traffic congestion,” “environment reconstruction”);

[0358] DNN or S-NSSAI information;

[0359] mission strategies or requirements;

[0360] Task ID or task session ID;

[0361] The identifier of the subtask management function or the subtask execution function (in the form of representation including but not limited to ID, IP address, FQDN);

[0362] Subtask strategies or requirements;

[0363] Subtask execution order;

[0364] Release reason, used to indicate the reason for releasing the task, including at least one of the following: normal release, temporary release, insufficient resources, semantic error, syntax error;

[0365] Release type, including at least one of the following: release only perception resources, release only computing resources, release only AI resources; release all resources.

[0366] Among them, in case of temporary release, in subsequent operations, after the network element releases the response resources, the locally stored context will be retained, and the resource configuration can be referenced or reused when the same task is established subsequently; if it is other release (including normal release, etc.), the locally retained context will be directly deleted, and it will need to be reconsidered when the same task is established subsequently.

[0367] It should be noted that the AF can request the network to release resources allocated for the task, or request the network to release resources allocated for a subtask, for example, requesting to release only the sensing resources.

[0368] In addition, the first message can be forwarded to the TM by a third network element. The third network element is located between the 6G core network and external third-party application functions (possibly also some internal AFs), and is responsible for opening network capabilities and internal network information. All external applications that want to access internal data of the 6G core network must go through the third network element. The third network element provides corresponding security guarantees to ensure the security of external applications accessing the 3GPP network, and provides functions such as external application demand or target customization capability opening, mobility status event subscription, and AF request distribution. The third network element is a network opening function, such as NEF.

[0369] The conditions for the AF to send a task release request message include at least one of the following:

[0370] AF expects to release tasks, including at least one of the following: AF closes the APP, AF resources are insufficient, and AF privacy is restricted.

[0371] The AF receives a task release request from the UE through the application layer. The task information included in the task release request is consistent with the task information carried in the first message. For example, the task information included in the task release request and the task information carried in the first message are information about the same task.

[0372] The timer maintained by AF times out. AF will start a timer after the task is successfully established. When the timer times out, AF will initiate a task release request.

[0373] Step (2): TM performs the first operation;

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

[0375] a. The TM verifies whether the task release request is a legal request. Specifically, if the TM stores the task identifier, the TM determines that the task release request is legal; if the TM does not store the task identifier and the AF does not have the task contract, the TM determines that the task release request is illegal. The TM may directly reject the task modification request and directly execute step (5).

[0376] b. The TM sends a subtask release request to the subtask management function or the subtask execution function.

[0377] The TM determines the subtask management function or the subtask execution function according to at least one of the following:

[0378] The subtask management function or subtask execution function identifier included by the AF in the task release request;

[0379] The subtask management function or subtask execution function identifier stored in the task context. The TM stores the task context when the task is established. The task context includes the association between the task and the subtask management function and / or subtask execution function.

[0380] If the TM cannot find the associated subtask management function or subtask execution function, the TM directly executes step (5), rejects the AF's request, and indicates that the resources associated with the requested task cannot be released.

[0381] Step (3): Subtask release;

[0382] 3-1a: If the subtasks include a sensing subtask, the TM sends a sensing subtask release request to the sensing management function or the sensing execution function, requesting the release of sensing resources, including at least one of the following: AF identifier, sensing subtask identifier, sensing execution function address, sensing policy, or QoS.

[0383] 3-1b: The perception management function or the perception execution function sends a perception subtask release response to the TM, indicating whether the perception resources associated with the task are successfully released.

[0384] If the perception resource is not released successfully, optionally, the perception subtask release response includes a failure reason, including at least one of: the perception subtask is in use, the perception subtask does not exist, the perception execution function does not exist, and the perception resource does not exist.

[0385] 3-2a: If the subtask includes a computing subtask, the TM sends a computing subtask release request to the computing management function or the computing execution function to request the network to release computing resources, including at least one of the following: AF identifier, computing subtask identifier, computing execution function address, computing policy or QoS.

[0386] 3-2b: The computing management function or computing execution function sends a computing subtask release response to the TM, indicating whether the computing resources associated with the task are successfully released.

[0387] If the computing resource is not released successfully, optionally, the computing subtask release response includes a failure reason, including at least one of: the computing subtask is in use, the computing subtask does not exist, the computing execution function does not exist, and the computing resource does not exist.

[0388] 3-3a: If the subtask includes an AI subtask, the TM sends an AI subtask release request to the AI ​​management function (e.g., AI service management function, AI resource management function) or AI resource node to request the network to release the AI ​​resource, including at least one of the following: AF identifier, AI subtask identifier, AI resource node address, AI policy, or QoS.

[0389] 3-3b: The AI ​​management function (eg, AI service management function, AI resource management function) or the AI ​​resource node sends an AI subtask release response to the TM, indicating whether the AI ​​resources associated with the task are successfully released.

[0390] If the AI ​​resource is not released successfully, the AI ​​subtask release response may optionally include a failure reason, including at least one of: the AI ​​subtask is in use, the AI ​​subtask does not exist, the AI ​​resource node does not exist, or the AI ​​resource does not exist.

[0391] After the TM releases the subtask, the connection between the TM and the subtask management function or subtask execution function is disconnected, and the TM deletes the subtask management function or subtask execution function address. When the TM executes the task again, it needs to select the subtask management function or subtask execution function again.

[0392] Step (4): TM releases the task context;

[0393] TM releases the task context, including at least one of:

[0394] If the AF requests to release the task, the TM deletes the saved complete task context.

[0395] If the AF requests to release the subtask, the TM deletes the saved subtask context.

[0396] It should be noted that the saved task context includes at least one of: the task context stored locally in the TM, and the task context stored in the UDM or UDR.

[0397] Step (5): TM sends a second message;

[0398] The TM sends a second message to the AF in response to the first message, notifying the AF of the result of the task release.

[0399] If a task release fails, the message optionally carries a failure reason value, indicating at least one of the following: task in progress, task does not exist, task is illegal, task is not signed, subtask is in use, subtask does not exist, subtask execution function does not exist, or subtask resource does not exist. The subtask indicated by the reason value can be one or more of the perception, computing, and AI subtasks.

[0400] Example 2:

[0401] In this embodiment, the AF requests to release the task or subtask. As shown in FIG5 , the task processing method includes the following process:

[0402] Step (1): TM receives the first message;

[0403] Step (2): TM performs the first operation;

[0404] Step (3): Subtask release;

[0405] Step (4): TM releases the task context;

[0406] Step (5): TM sends the second message.

[0407] FIG5 expands step (3) in detail based on FIG4.

[0408] Example 3:

[0409] In this embodiment, the AF requests to release the context. As shown in FIG6 , the task processing method includes the following steps:

[0410] Step (1): same as step (1) in Example 1;

[0411] Step (2): Same as step (4) in Example 1;

[0412] Step (3): Same as step (5) in Example 1;

[0413] The difference from the first embodiment is that here the AF requests the release of the task context, and the TM releases the task context, but the data transmission channel between the TM and the AF remains. The task context includes the association between the task policy or task requirement and the subtask management function or subtask execution function, or the association between the subtask policy or subtask requirement and the subtask management function or subtask execution function.

[0414] The embodiments of the present application provide a feasible AF-triggered task release process and method, which enables the network to dynamically reclaim resources and can meet the resource requests of a large number of tasks.

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

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

[0417] The receiving module 301 is configured to receive a first message sent by a second network element, where the first message is used to request the release of a target task or a subtask of the target task;

[0418] An execution module 302 is configured to execute a release operation on the target task or a subtask of the target task according to the first message;

[0419] The target task includes at least one subtask, and the subtask of the target task includes at least one of the following:

[0420] Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

[0421] Optionally, the release operation includes at least one of the following:

[0422] Release the resources corresponding to the target task or the subtask of the target task;

[0423] Delete the task context corresponding to the target task or a subtask of the target task.

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

[0425] Task description information; data network name (DNN) information; slicing information; task strategy information; task quality information (QoT); task identifier; identifier of the subtask management function; identifier of the subtask execution function; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; first indication information for indicating the subtask execution order; second indication information for indicating the reason for requesting resource release; third indication information for indicating the resource release type;

[0426] The task template is used to represent task requirement information.

[0427] Optionally, the third indication information indicates at least one of the following:

[0428] Release perception resources; release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.

[0429] Optionally, the first message further includes fourth indication information used to instruct the second network element to trigger sending the first message based on at least one of the following:

[0430] The second network element expects to release the target task or a subtask of the target task;

[0431] The second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;

[0432] The timer corresponding to the target task times out.

[0433] Optionally, the device further comprises:

[0434] a sending module, configured to send a second message corresponding to the first message to the second network element;

[0435] The second message is used to indicate whether the release operation is executed successfully or fails.

[0436] Optionally, when the release operation fails, the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:

[0437] The target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

[0438] Optionally, the execution module is specifically configured to:

[0439] Determine a subtask management function or a subtask execution function corresponding to the target task;

[0440] A third message is sent to the subtask management function or the subtask execution function, where the third message is used to request the release of the subtask of the target task.

[0441] Optionally, in the case where the subtasks of the target task include a perception subtask, the third message includes at least one of the following: an identifier of the second network element; a perception subtask identifier; a perception execution function address; perception strategy information; perception requirement information; or

[0442] In the case where the subtasks of the target task include a computing subtask, the third message includes at least one of the following: an identifier of the second network element; an identifier of the computing subtask; an address of a computing execution function; computing strategy information; computing requirement information; or

[0443] In the case where the subtasks of the target task include an AI subtask, the third message includes at least one of the following: an identifier of the second network element; an AI subtask identifier; an AI resource node address; AI strategy information; and AI requirement information.

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

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

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

[0447] A sending module 401 is configured to send a first message to a first network element, where the first message is used to request the release of a target task or a subtask of the target task;

[0448] The target task includes at least one subtask, and the subtask of the target task includes at least one of the following:

[0449] Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

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

[0451] Task description information; data network name (DNN) information; slicing information; task strategy information; task quality information (QoT); task identifier; identifier of the subtask management function; identifier of the subtask execution function; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; first indication information for indicating the subtask execution order; second indication information for indicating the reason for requesting resource release; third indication information for indicating the resource release type;

[0452] The task template is used to represent task requirement information.

[0453] Optionally, the third indication information indicates at least one of the following:

[0454] Release perception resources; release computing resources; release artificial intelligence (AI) resources; release predefined resource combinations; release all resources.

[0455] Optionally, the sending module is specifically configured to:

[0456] determining whether the first condition is satisfied;

[0457] When it is determined that the first condition is met, the second network element sends a first message to the first network element;

[0458] The first condition includes at least one of the following:

[0459] The second network element expects to release the target task or a subtask of the target task;

[0460] The second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task;

[0461] The timer corresponding to the target task times out.

[0462] Optionally, when the second network element satisfies the second condition, the second network element expects to release the target task or a subtask of the target task:

[0463] The second condition includes at least one of the following:

[0464] The second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.

[0465] Optionally, the device further comprises:

[0466] a receiving module, configured to receive a second message corresponding to the first message sent by the first network element;

[0467] The second message is used to indicate whether the release operation is executed successfully or fails.

[0468] Optionally, when the release operation fails, the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following:

[0469] The target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

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

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

[0472] Optionally, as shown in FIG9 , an embodiment of the present application further provides a communication device 500, comprising a processor 501 and a memory 502, wherein the memory 502 stores a program or instruction that can be run on the processor 501. For example, when the communication device 500 is a first network element, the program or instruction, when executed by the processor 501, implements the various steps of the embodiment of the task processing method applied to the first network element, and can achieve the same technical effect. To avoid repetition, it is not described here. When the communication device 500 is a second network element, the program or instruction, when executed by the processor 501, implements the various steps of the embodiment of the task processing method applied to the second network element, and can achieve the same technical effect. To avoid repetition, it is not described here.

[0473] The present application also provides a network-side device, which is a first network element or a second network element and includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 2 or Figure 3. This network-side device embodiment corresponds to the above-mentioned method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network-side device embodiment and can achieve the same technical effects.

[0474] Specifically, an embodiment of the present application further provides a network-side device. The network-side device can be a first network element or a second network element. As shown in Figure 10, the network-side device 600 includes: an antenna 601, a radio frequency device 602, a baseband device 603, a processor 604, and a memory 605. The antenna 601 is connected to the radio frequency device 602. In the uplink direction, the radio frequency device 602 receives information via the antenna 601 and sends the received information to the baseband device 603 for processing. In the downlink direction, the baseband device 603 processes the information to be transmitted and sends it to the radio frequency device 602. The radio frequency device 602 processes the received information and then sends it through the antenna 601.

[0475] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 603 , which includes a baseband processor.

[0476] The baseband device 603 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 10, one of which is, for example, a baseband processor, which is connected to the memory 605 through a bus interface to call the program in the memory 605 and execute the network device operations shown in the above method embodiment.

[0477] The network side device may further include a network interface 606, which is, for example, a Common Public Radio Interface (CPRI).

[0478] Specifically, the network side device 600 of the embodiment of the present application also includes: instructions or programs stored in the memory 605 and can be run on the processor 604. The processor 604 calls the instructions or programs in the memory 605 to execute the method executed by each module shown in Figure 7 or Figure 8, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0479] Specifically, an embodiment of the present application further provides a network-side device. The network-side device may be a first network element or a second network element. As shown in FIG11 , the network-side device 700 includes a processor 701, a network interface 702, and a memory 703. The network interface 702 may be, for example, a common public radio interface (CPRI).

[0480] Specifically, the network side device 700 of the embodiment of the present application also includes: instructions or programs stored in the memory 703 and can be run on the processor 701. The processor 701 calls the instructions or programs in the memory 703 to execute the methods executed by each module shown in Figure 7 or Figure 8, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

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

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

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

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

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

[0486] An embodiment of the present application also provides a task processing system, including: a first network element and a second network element, wherein the first network element can be used to execute the steps of the task processing method applied to the first network element as described above, and the second network element can be used to execute the steps of the task processing method applied to the second network element as described above.

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

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

[0489] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A task processing method, comprising: The first network element receives a first message sent by the second network element, where the first message is used to request the release of a target task or a subtask of the target task; The first network element performs a release operation on the target task or a subtask of the target task according to the first message; The target task includes at least one subtask, and the subtask of the target task includes at least one of the following: Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

2. The method according to claim 1, wherein The release operation includes at least one of the following: Release the resources corresponding to the target task or the subtask of the target task; Delete the task context corresponding to the target task or a subtask of the target task.

3. The method according to claim 1 or 2, wherein: The first message carries at least one of the following: Task description information; data network name DNN information; slicing information; task strategy information; task quality information QoT; task identifier; subtask management function identifier; subtask execution function identifier; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; First instruction information for indicating the execution order of subtasks; Second indication information for indicating the reason for requesting to release the resource; third indication information for indicating the type of resource requested to be released; The task template is used to represent task requirement information.

4. The method according to claim 3, wherein: The third indication information indicates at least one of the following: Request to release perception resources; request to release computing resources; request to release artificial intelligence (AI) resources; request to release a predefined resource combination; request to release all resources.

5. The method according to any one of claims 1 to 4, wherein The first message further includes fourth indication information for indicating a triggering cause of the first message, where the triggering cause includes at least one of the following: The second network element expects to release the target task or a subtask of the target task; The second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task; The timer corresponding to the target task times out.

6. The method according to any one of claims 1 to 5, wherein After the first network element receives the first message sent by the second network element, the method further includes: The first network element sends a second message corresponding to the first message to the second network element; The second message is used to indicate whether the release operation is executed successfully or fails.

7. The method according to claim 6, wherein: If the release operation fails, the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following: The target task is in the execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; the subtask of the target task is in the execution state; the subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

8. The method according to any one of claims 1 to 7, wherein The first network element performs a release operation on the target task or a subtask of the target task, including The first network element determines a subtask management function or a subtask execution function corresponding to the target task; The first network element sends a third message to the subtask management function or the subtask execution function, where the third message is used to request the release of the subtask of the target task.

9. The method according to claim 8, wherein In the case where the subtasks of the target task include a perception subtask, the third message includes at least one of the following: an identifier of the second network element; an identifier of the perception subtask; an address of a perception execution function; perception strategy information; perception requirement information; or In the case where the subtasks of the target task include a computing subtask, the third message includes at least one of the following: an identifier of the second network element; an identifier of the computing subtask; an address of a computing execution function; computing strategy information; computing requirement information; or In the case where the subtasks of the target task include an AI subtask, the third message includes at least one of the following: an identifier of the second network element; an AI subtask identifier; an AI resource node address; AI strategy information; and AI requirement information.

10. A task processing method, comprising: The second network element sends a first message to the first network element, where the first message is used to request the release of the target task or a subtask of the target task; The target task includes at least one subtask, and the subtask of the target task includes at least one of the following: Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

11. The method according to claim 10, wherein: The first message carries at least one of the following: Task description information; data network name DNN information; slicing information; task strategy information; task quality information QoT; task identifier; subtask management function identifier; subtask execution function identifier; subtask strategy information; subtask requirement information; subtask identifier; task template identifier; First instruction information for indicating the execution order of subtasks; Second indication information for indicating the reason for requesting to release the resource; third indication information for indicating the type of resource requested to be released; The task template is used to represent task requirement information.

12. The method according to claim 11, wherein The third indication information indicates at least one of the following: Request to release perception resources; request to release computing resources; request to release artificial intelligence (AI) resources; request to release a predefined resource combination; request to release all resources.

13. The method according to any one of claims 10 to 12, wherein: The second network element sending a first message to the first network element includes: When it is determined that the first condition is met, the second network element sends a first message to the first network element; The first condition includes at least one of the following: The second network element expects to release the target task or a subtask of the target task; The second network element receives a request message sent by the terminal for requesting to release the target task or a subtask of the target task; The timer corresponding to the target task times out.

14. The method according to claim 13, wherein: When the second network element satisfies the second condition, the second network element expects to release the target task or a subtask of the target task: The second condition includes at least one of the following: The second network element closes an application associated with the target task; available resources of the second network element are less than a preset threshold; and the second network element cannot provide relevant data of the target task.

15. The method according to any one of claims 10 to 14, wherein: After the second network element sends the first message to the first network element, the method further includes: The second network element receives a second message corresponding to the first message; The second message is used to indicate whether the release operation is executed successfully or fails.

16. The method according to claim 15, wherein If the release operation fails, the second message carries fifth indication information, where the fifth indication information is used to indicate at least one of the following: The target task is in execution state; the target task does not exist; the target task is not authorized; there is no task contract for the target task; The subtasks of the target task are in execution state; The subtask of the target task does not exist; the subtask execution function corresponding to the target task does not exist; the resource of the subtask of the target task does not exist.

17. A task processing device comprising: A receiving module, configured to receive a first message sent by a second network element, wherein the first message is used to request the release of a target task or a subtask of the target task; an execution module, configured to execute a release operation on the target task or a subtask of the target task according to the first message; The target task includes at least one subtask, and the subtask of the target task includes at least one of the following: Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

18. The device according to claim 17, wherein The release operation includes at least one of the following: Release the resources corresponding to the target task or the subtask of the target task; Delete the task context corresponding to the target task or a subtask of the target task.

19. The apparatus according to claim 17, further comprising: a sending module, configured to send a second message corresponding to the first message to the second network element; The second message is used to indicate whether the release operation is executed successfully or fails.

20. A task processing device comprising: A sending module, configured to send a first message to a first network element, wherein the first message is used to request the release of a target task or a subtask of the target task; The subtasks of the target task include at least one of the following: Perception subtask, computing subtask, artificial intelligence (AI) subtask, data subtask, positioning subtask, communication subtask, IP multimedia subsystem (IMS) subtask, information processing subtask, and immersive subtask.

21. A communication device comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the task processing method according to any one of claims 1 to 9 are implemented, or the steps of the task processing method according to any one of claims 10 to 16 are implemented.

22. A chip, wherein: The chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the task processing method according to any one of claims 1 to 9, or to implement the steps of the task processing method according to any one of claims 10 to 16.

23. A readable storage medium, wherein: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the task processing method according to any one of claims 1 to 9 are implemented, or the steps of the task processing method according to any one of claims 10 to 16 are implemented.

24. A computer program / program product, wherein: When the computer program / program product is executed by at least one processor, the computer program / program product implements the steps of the task processing method according to any one of claims 1 to 9, or implements the steps of the task processing method according to any one of claims 10 to 16.

Images