Task processing method and device and related equipment

Abstract

The invention discloses a task processing method and device and related equipment, and belongs to the technical field of communication, and the task processing method comprises the steps that a first network element receives a first message sent by a second network element, and the first message is used for requesting to establish a target task; the first network element establishes the target task; wherein the first message carries at least one of the following items: a target task template; task description information; task quality information QoT of the task; task data network name DNN information; task slice information; task strategy information; task identification; the target task template is used for representing task demand information; wherein the sub-tasks of the target task comprise at least one of the following sub-tasks: 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

Technical Field

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

[0002] Traditional communication systems are connection-oriented. Typical applications involve providing connections between specific terminals or between terminals and application servers. The network architecture provides complete session lifecycle management mechanisms and Quality of Service (QoS) guarantees. However, in future communication networks (such as 6G), which will need to support services such as communication, perception, and computing, connection-based designs cannot meet the task processing requirements of future communication networks. Therefore, implementing task processing in networks supporting communication, perception, and computing services has become a pressing issue. Summary of the Invention

[0003] The embodiments of the present application provide a task processing method, apparatus, and related equipment that can solve the problem of how to implement task processing for a network that supports services such as communication, perception, and computing.

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

[0005] The first network element receives a first message sent by the second network element, where the first message is used to request to establish a target task;

[0006] The first network element establishes the target task;

[0007] The first message carries at least one of the following:

[0008] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0009] The target task template is used to represent task requirement information;

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

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

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

[0013] The second network element sends a first message to the first network element, where the first message is used to request to establish a target task;

[0014] The first message carries at least one of the following:

[0015] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0016] The target task template is used to represent task requirement information;

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

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

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

[0020] A first receiving module is configured to receive a first message sent by a second network element, where the first message is used to request establishment of a target task;

[0021] An establishment module, used for establishing the target task;

[0022] The first message carries at least one of the following:

[0023] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0024] The target task template is used to represent task requirement information;

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

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

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

[0028] A first sending module is used to send a first message to a first network element, where the first message is used to request to establish a target task;

[0029] The first message carries at least one of the following:

[0030] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0031] The target task template is used to represent task requirement information;

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

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

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

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

[0036] receiving a first message sent by a second network element, where the first message is used to request establishment of a target task;

[0037] The processor is used to: establish the target task;

[0038] The first message carries at least one of the following:

[0039] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0040] The target task template is used to represent task requirement information;

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

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

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

[0044] Sending a first message to a first network element, where the first message is used to request establishment of a target task;

[0045] The first message carries at least one of the following:

[0046] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0047] The target task template is used to represent task requirement information;

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

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

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

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

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

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

[0054] 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 establishment of a target task; the first network element establishes the target task; wherein the first message carries at least one of the following: a target task template; task description information; task quality information QoT of the task; task data network name DNN information; task slicing information; task strategy information; task identifier; the target task template is used to characterize task requirement information; wherein the subtasks of the target task include 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, the target task establishment is requested with the task as the center, so that the first network element can allocate task resources for one or more subtasks of the target task, thereby realizing task processing in a network that supports services such as communication, perception, and computing; in addition, since the task establishment of multiple subtasks of the target task can be realized through one signaling message, the signaling overhead can be saved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0056] Figure 2 This is one of the flowcharts of a task processing method provided in an embodiment of the present application;

[0057] Figure 3 This is a second flowchart of a task processing method provided in an embodiment of the present application;

[0058] Figure 4 This is a third flowchart of a task processing method provided in an embodiment of the present application;

[0059] Figure 5 This is a fourth flowchart of a task processing method provided in an embodiment of the present application;

[0060] Figure 6 This is a fifth flowchart of a task processing method provided in an embodiment of the present application;

[0061] Figure 7 This is the sixth flowchart of a task processing method provided in an embodiment of the present application;

[0062] Figure 8 This is the seventh flowchart of a task processing method provided in an embodiment of the present application;

[0063] Figure 9 This is the eighth flowchart of a task processing method provided in an embodiment of the present application;

[0064] Figure 10 This is one of the structural diagrams of a task processing device provided in an embodiment of the present application;

[0065] Figure 11 This is the second structural diagram of a task processing device provided in an embodiment of the present application;

[0066] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0067] Figure 13 This is one of the structural diagrams of a network side device provided in an embodiment of the present application;

[0068] Figure 14 This is the second structural diagram of a network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

[0074] 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 server discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), etc. 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.

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

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

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

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

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

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

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

[0082] 2. Synaesthesia and computing integration

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

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

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

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

[0087] See also Figure 2 , Figure 2 This is a flowchart of a task processing method provided by an embodiment of the present application. Figure 2 As shown, the task processing method includes the following steps:

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

[0089] Step 102: The first network element establishes the target task;

[0090] The first message carries at least one of the following:

[0091] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0092] The target task template is used to represent task requirement information;

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

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

[0095] A task can refer to a comprehensive service, or a collection of comprehensive services, including communication, information, interpersonal communication, and computing, provided on-demand by a network system (such as a 6G network system) based on external service requests (including services requested by UEs, over-the-top (OTT) services, or services requested by AFs). OTT refers to the provision of various application services to users via the internet.

[0096] Task management refers to the management process that aims to respond to external business requests and provide communication functions and other additional network system functions (such as positioning, synaesthesia, computing, etc.).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0125] Task description: Automatic parking.

[0126] Task type: Multi-tasking.

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

[0128] Subtask type: Perception subtask

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

[0130] Subtask type: Computational subtask

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0145] a) Task description information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0184] 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;

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

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

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

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

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

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

[0191] Sensing services: These services may include at least one of the following: long sensing range with high real-time requirements (DelayCritical LSS); long sensing range with low real-time requirements (LSS); short sensing range with low real-time requirements (DelayCritical SSS); and short sensing range with low real-time requirements (SSS). These services may also be represented by numbers, letters, or other character strings.

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

[0193] 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 arrival angle, multipath departure angle, multipath delay, and Doppler frequency.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0207] {

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

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

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

[0211] }

[0212] 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 task QoS description information to obtain a task instance.

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

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

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

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

[0217] In addition, QoT can be understood or replaced by QoS.

[0218] In one embodiment, if the first network element agrees with the request corresponding to the first message, the first network element establishes the target task; if the first network element does not agree with the request corresponding to the first message, the first network element does not establish the target task.

[0219] It should be noted that the first network element can establish the target task based on the first message. The first network element can determine the subtask management function or subtask execution function based on the target task template, task description information, task QoT, task data network name DNN information, task slicing information, task strategy information or task identifier carried by the first message, and request the subtask management function to allocate subtask resources or configure subtask configuration-related information for the subtask execution function.

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

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

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

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

[0224] It should be noted that task description information can also be briefly described as task description; task strategy information can also be briefly described as task strategy; task slice information can also be briefly described as task slice; DNN information can also be briefly described as DNN.

[0225] Taking the second network element as AF as an example, the AF sends a first message to the first network element (network side device), wherein the first message is used to request the first network element to allocate network resources for the task. The first message includes at least one of the following:

[0226] Filled task template; task description (for example, "traffic congestion", "environment reconstruction"); task QoE requirements (the case where the second network element sends subtask requirements on behalf of the UE); DNN or S-NSSAI information; task strategy or requirements; task identifier.

[0227] 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 establishment of a target task; the first network element establishes the target task; wherein the first message carries at least one of the following: a target task template; task description information; task quality information QoT of the task; task data network name DNN information; task slicing information; task strategy information; task identifier; the target task template is used to characterize task requirement information; wherein the subtasks of the target task include 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, the target task establishment is requested with the task as the center, so that the first network element can allocate task resources for one or more subtasks of the target task, thereby realizing task processing in a network that supports services such as communication, perception, and computing; in addition, since the task establishment of multiple subtasks of the target task can be realized through one signaling message, the signaling overhead can be saved.

[0228] Optionally, the method further includes:

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

[0230] When the second message is used to indicate approval of the request corresponding to the first message, the second message carries at least one of the following:

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

[0232] Optionally, the method further includes:

[0233] The first network element sends a third message to the second network element;

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

[0235] The task identifier, subtask identifier, and task request quantity exceed the maximum value; requesting the target task is not allowed; the second network element is not authorized.

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

[0237] It should be noted that when the first message and the second message or the third message all carry task identification, task strategy information, task slicing information or task DNN information, the task identification, task strategy information, task slicing information or task DNN information in the second message or the third message are the same as those in the first message.

[0238] The second network element is not authorized, which may indicate that the second network element is illegal. The second network element is not authorized, which may be understood as the first network element and the second network element not signing a service level agreement for the target task or the second network element and the first network element not signing a service level agreement.

[0239] Taking the second network element as AF as an example, the AF receives a second message returned by the first network element, including at least one of the following: task identifier, subtask execution function identifier (expression includes but is not limited to identifier (Identifier, ID), Internet Protocol (Internet Protocol, IP) address, fully qualified domain name (Fully Qualified Domain Name, FQDN)), subtask management function identifier (expression includes but is not limited to ID, IP address, FQDN), task strategy, subtask strategy, subtask execution order.

[0240] In one embodiment, the third message may be a rejection message, which may optionally carry a rejection reason, including but not limited to: the number of task requests exceeds the maximum value; the task request is not allowed; the AF is illegal.

[0241] In this implementation, the first network element sends a second message or a third message to the second network element, so that the second network element can learn through the second message or the third message whether the first network element agrees with or rejects the request corresponding to the first message.

[0242] Optionally, the method further includes:

[0243] The first network element receives a fourth message sent by the second network element, where the fourth message is used to request: updating a task policy corresponding to the target task or a reserved resource corresponding to the target task.

[0244] Before the first network element receives the first message sent by the second network element, the second network element receives a fourth message sent by the second network element. The second network element may perform task translation or decomposition of the target task to determine a task instance; based on the determined task instance, the second network element sends a fourth message to the first network element, requesting: updating a task policy corresponding to the target task or updating reserved resources corresponding to the target task.

[0245] For example, the fourth message may carry task policy information corresponding to the target task, and the first network element may update the reserved resources corresponding to the target task for the second network element based on the task policy information in the fourth message.

[0246] In this embodiment, the first network element receives the fourth message sent by the second network element. The first network element can update the task policy corresponding to the target task or the reserved resources corresponding to the target task based on the request of the fourth message, thereby realizing the update of the task policy or task reserved resources when the second network element performs task translation or task decomposition.

[0247] Optionally, the fourth message carries at least one of the following:

[0248] The identifier of the second network element; task strategy information; subtask strategy information; instruction information for indicating the execution order of subtasks; QoT of the task; task QoT priority; QoT of the subtask.

[0249] The task quality information, task QoT priority, and subtask QoT carried in the fourth message may be task-related information on the terminal side. For example, the target task may be composed of a task on the terminal side and a task on the second network element side, and the relevant information of the task on the terminal side may be sent by the second network element to the first network element.

[0250] In one embodiment, the first network element can update the task policy corresponding to the target task or the reserved resources corresponding to the target task based on the task policy information, subtask policy information, indication information for indicating the execution order of subtasks, task quality information, task QoS priority or subtask quality information carried by the fourth message.

[0251] In one implementation, the first network element may determine the target task corresponding to the identifier of the second network element based on the identifier of the second network element carried in the fourth message.

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

[0253] The first network element receives a fifth message sent by the second network element, where the fifth message is used to request creation of a task template;

[0254] The first network element creates a task template based on the fifth message;

[0255] The first network element sends a sixth message to the second network element, where the sixth message carries task template information.

[0256] Among them, the fifth message may include at least one of the following: Application Service Provider ID (ASPID) information; task description information; task template identifier; DNN or S-NSSAI; expected task template time window, used to indicate the time when the task template is applicable, which can be continuous time or a set of time intervals; expected task template applicable area, used to indicate the geographical area (such as cell ID, tracking area identity (TAI), geographical location) or network area (such as public land mobile network (PLMN) ID, stand-alone non-public network (SNPN) ID) to which the task template is applicable; subscription task template change notification, used to notify the AF when the task template is upgraded or changed; task quality information.

[0257] In addition, the first network element creating a task template based on the fifth message may mean that the first network element creates a task template based on a request of the fifth message.

[0258] In one embodiment, the first network element may further create a task template based on at least one of the following:

[0259] Information carried in the fifth message;

[0260] First network element local configuration or local policy or operator policy;

[0261] A task template associated with the target task stored or maintained by the first network element, for example, if the first network element has generated or formulated a similar task template that can meet the service requirements of the task requested by the second network element, the first network element can directly use the task template;

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

[0263] The intelligent function inside the first network element can generate or formulate a corresponding task template based on the task description. The intelligent function is trained based on a large amount of input and output data (task description-task template) and achieves an accuracy that meets the preset threshold, and can be used to generate a task template.

[0264] It should be noted that the task template information may represent the task template created by the first network element. The second network element may set the task template created by the first network element to obtain a target task template.

[0265] In this embodiment, the first network element receives the fifth message sent by the second network element, and the fifth message is used to request the creation of a task template; the first network element creates the task template based on the fifth message; the first network element sends a sixth message to the second network element, and the sixth message carries task template information, so that the task template can be generated. The second network element can indicate the task requirements to the first network element according to the task template corresponding to the task template information, so that the first network element can interpret the task requirements of the second network element.

[0266] Optionally, the first network element establishing the target task includes:

[0267] The first network element obtains first information;

[0268] The first network element determines subtask strategy information or subtask QoT of the target task based on the first information;

[0269] The first network element allocates resources to the target task based on subtask strategy information or QoT of the subtask of the target task;

[0270] The first information includes at least one of the following:

[0271] Task quality information from the terminal; locally configured task quality information.

[0272] Among them, when the target task includes a subtask required by the terminal, the first network element determines the subtask policy information or subtask QoT of the target task based on the first information. For example, the first network element determines the subtask policy information or subtask QoT of the target task based on the first information, including: when the subtask of the target task includes a subtask required by the terminal, the first network element determines the subtask policy information or subtask QoT of the target task based on the first information.

[0273] It should be noted that the first message may only carry part of the requirement information of the target task. The first network element can obtain the first information, and combine the requirement information of the target task carried by the first message and the first information to obtain the QoT of the complete task. The QoT of the complete task may include the requirement information corresponding to all subtasks contained in the target task.

[0274] In one embodiment, the first network element may determine subtask policy information or subtask QoT of the target task based on task quality information from the terminal. For example, the subtasks of the target task may include subtasks contracted by the terminal. The first network element may request the task quality information of the terminal from the terminal, and determine the subtask policy information or subtask QoT of the subtask contracted by the terminal based on the task quality information of the terminal.

[0275] In one embodiment, the first network element may determine the subtask policy information or subtask QoT of the target task based on the locally configured task quality information. For example, the subtask of the target task may include a subtask contracted by the terminal, and the first network element may determine the subtask policy information or subtask QoT of the subtask contracted by the terminal based on the locally configured task quality information.

[0276] It should be noted that the first network element can determine the parameter information for allocating network resources to the task based on the subtask policy information or the subtask QoT, and allocate network resources to the task based on the parameter information; or, the first network element can send the parameter information to the subtask management function, and the subtask management function will allocate network resources to the task based on the parameter information; or, the first network element can generate a subtask configuration based on the parameter information, and configure the subtask configuration for the subtask execution function.

[0277] In this embodiment, the first network element obtains first information; the first network element determines the subtask strategy information or subtask QoT of the target task based on the first information; in this way, it is possible to translate or disassemble all subtasks included in the target task to obtain the subtask strategy information or subtask QoT of the target task; and then determine the task instance based on the obtained subtask strategy information or subtask QoT to establish the target task.

[0278] Optionally, before the first network element obtains the first information, the method further includes:

[0279] The first network element sends a seventh message to the terminal, where the seventh message is used to request the QoT of the subtask;

[0280] The first network element receives the eighth message sent by the terminal, and the eighth message carries at least one of the following: a task template of the subtask; subtask description information; QoT of the subtask; subtask DNN information; subtask slicing information; subtask strategy information; and subtask identifier.

[0281] It should be noted that the first network element may send the seventh message to the terminal to dynamically determine subtask requirements from the terminal. When the target task that the second network element requests the first network element to establish includes multiple subtasks, and the second network element has only signed up for some of the multiple subtasks, the first network element may send the seventh message to the terminal to dynamically request the terminal to determine the requirements of the subtasks for which the terminal has signed up.

[0282] In one implementation, the terminal may set a task template for the subtask according to at least one of the following, and carry the set task template for the subtask in the eighth message:

[0283] The terminal sets the task description information in the task template of the subtask as the task type of the subtask;

[0284] The terminal sets the task QoE in the task template of the subtask as the QoE of the subtask;

[0285] The terminal sets the task strategy information in the task template of the subtask as the task strategy information of the subtask;

[0286] The terminal sets the task quality information in the task template of the subtask as the task quality information of the subtask;

[0287] The terminal sets the task parameters in the task template of the subtask as the task parameters of the subtask.

[0288] In one embodiment, the eighth message carries at least one of the following items of the subtasks contracted by the terminal: a populated subtask template; subtask description information; subtask QoT; subtask DNN information; subtask slicing information; subtask strategy information; and subtask identifier. The subtasks contracted by the terminal are at least some subtasks of the target task.

[0289] In this embodiment, the first network element sends a seventh message to the terminal, and the seventh message is used to request the QoT of the subtask; the first network element receives the eighth message sent by the terminal; in this way, the first network element can obtain the QoT of the terminal's subtask based on the content of the eighth message, and then can determine the subtask policy information or subtask QoT of the target task according to the QoT of the terminal's subtask.

[0290] Optionally, the seventh message carries at least one of the following:

[0291] Task description information; task QoE description information; task ID; task session ID; subtask ID; subtask session ID; subtask type information; subtask QoE description information.

[0292] In this embodiment, the terminal can determine the target task or a subtask of the target task through the task description information, task QoE description information, task identifier, task session identifier, subtask identifier, subtask session identifier, subtask type information or subtask QoE description information carried by the seventh message, and feedback the relevant information of the subtask signed by the terminal in the target task to the first network element.

[0293] Optionally, before the first network element sends the seventh message to the terminal, the method further includes:

[0294] The first network element determines the terminal based on at least one of the following:

[0295] Terminal ID; task template ID; task strategy ID; task ID.

[0296] In one implementation, the first network element may obtain the terminal identifier through a task negotiation process with the second network element, and determine the terminal through the terminal identifier.

[0297] In one embodiment, the first network element may store the correspondence between the task template identifier, the task policy identifier or the task identifier and the terminal; the first network element may obtain the task template identifier, the task policy identifier or the task identifier through the first message, and then determine the corresponding terminal through the task template identifier, the task policy identifier or the task identifier.

[0298] Optionally, the first network element establishes the target task, including at least one of the following:

[0299] The first network element determines the subtask management function corresponding to the target task, and sends a ninth message to the subtask management function, wherein the ninth message is used to request the subtask management function to allocate subtask resources;

[0300] The first network element determines a subtask execution function corresponding to the target task, and sends a tenth message to the subtask execution function, where the tenth message is used to indicate information related to subtask configuration;

[0301] determining, by the first network element, whether the second network element is authorized;

[0302] The first network element determines a task instance corresponding to the target task;

[0303] The first network element allocates at least one of a task identifier, a task slice, and a task DNN to the target task.

[0304] The subtask management function may include a perception management function, a computing management function, or an AI management function, etc. The subtask execution function may include a perception execution function (or described as a perception function), a computing execution function (or described as a computing function), or an AI execution function (or described as an AI resource node, or an AI function), etc.

[0305] In one embodiment, the subtask management function includes a perception management function, and the first network element sends a ninth message to the perception management function to request the network to allocate perception resources, including at least one of the following: perception subtask strategy or QoS, perception subtask execution order, and perception subtask identifier.

[0306] The perception management function may select an appropriate perception execution function and assign a subtask identifier according to the ninth message, and optionally assign a subtask slice or a subtask DNN;

[0307] The perception management function sends perception execution function information to the first network element, including at least one of the following: perception execution function IP address, ID information, FQDN, subtask identifier, allocated subtask slice or subtask DNN.

[0308] In one embodiment, the subtask management function includes a computing management function, and the first network element sends a ninth message to the computing management function to request the network to allocate computing resources, including at least one of the following: computing subtask strategy or QoS, computing subtask execution order, and computing subtask identification.

[0309] The computing management function selects an appropriate computing execution function according to the ninth message and assigns a subtask identifier, and optionally assigns a subtask slice or a subtask DNN;

[0310] The computing management function sends computing execution function information to the first network element, including at least one of the following: computing execution function IP address, ID information, FQDN, computing power information of the computing execution function (computing power size, type), subtask identifier, allocated subtask slice or subtask DNN.

[0311] In one embodiment, the subtask management function includes an AI management function, and the first network element sends a ninth message to the AI ​​management function to request the network to allocate AI resources, including at least one of the following: AI subtask policy or QoS, AI subtask execution order, and AI subtask identifier.

[0312] The AI ​​management function selects a suitable AI execution function (or AI resource node) according to the ninth message, assigns a subtask identifier, and optionally assigns a subtask slice or a subtask DNN;

[0313] The AI ​​management function sends AI execution function (or AI resource node) information to the first network element, including at least one of the following: AI execution function IP address, ID information, FQDN, model acquisition address, model training address, AI resource address, subtask identifier, allocated subtask slice or subtask DNN.

[0314] In one embodiment, the subtask execution function includes a perception execution function, and the first network element sends a tenth message to the selected perception execution function to configure perception subtask information, where the perception subtask information is used to indicate the information required for the perception execution function to execute the perception subtask.

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

[0316] In one embodiment, the subtask execution function includes a computing execution function, and the first network element sends a tenth message to the selected computing execution function to configure computing subtask information, where the computing subtask information is used to indicate the information required for the computing execution function to execute the computing subtask.

[0317] The computing execution function sends a computing subtask response to the first network element. The response can be an acceptance or rejection. If the response is a rejection, the first network element needs to select another computing execution function that can execute the computing subtask. Optionally, the computing subtask response may also include computing power information (such as computing power size and type) of the computing execution function.

[0318] In one embodiment, the subtask execution function includes an AI execution function, and the first network element sends a tenth message to the selected AI execution function to configure AI subtask information, where the AI ​​subtask information is used to indicate information required for the AI ​​execution function to execute the AI ​​subtask.

[0319] The AI ​​execution function sends an AI subtask response to the first network element. The response can be an acceptance or rejection. If the response is a rejection, the first network element needs to select another AI execution function that can execute the AI ​​subtask. Optionally, the AI ​​subtask response may also include at least one of the following: a model acquisition address, a model training address, supported AI frameworks (e.g., TensorFlow, PyTorch, etc.), and supported AI libraries and versions.

[0320] In this embodiment, the first network element determines the subtask management function corresponding to the target task and sends a ninth message to the subtask management function, wherein the ninth message is used to request the subtask management function to allocate subtask resources, thereby enabling resource allocation of subtasks of the target task.

[0321] In this embodiment, the first network element determines the subtask execution function corresponding to the target task and sends a tenth message to the subtask execution function. The tenth message is used to indicate information related to the subtask configuration, so that the subtask execution function can execute the configuration of the subtask of the target task.

[0322] In one embodiment, determining whether the second network element is authorized can verify whether the second network element is legitimate, and thus can verify whether the target task is a reasonable task requested by the legitimate second network element. If the second network element has signed the task contract, the first network element determines that the first message is legitimate; if the second network element does not have the task contract, the first network element determines that the first message is illegal, and the first network element can directly reject the first message.

[0323] In one implementation, the first network element may translate or decompose the first message into task instances.

[0324] The subtasks of the target task may include at least one of the following: perception subtask, computing subtask, AI subtask, and communication subtask.

[0325] If the first message includes a populated task template, the first network element may map the task template to the task instance; if the first message does not include a populated task template, the first network element may generate a task instance for the target task according to at least one of the following:

[0326] a first message received;

[0327] First network element local configuration or local policy or operator policy;

[0328] The task context associated with the target task stored or maintained by the first network element, for example, if the first network element has generated a task instance for a similar task that can meet the service requirements of the task requested by the second network element, the first network element can directly use the task instance;

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

[0330] The intelligent module inside the first network element can generate corresponding task instances based on the task description. The intelligent function is trained based on a large amount of input and output data (task description-task instance) and achieves an accuracy that meets the preset threshold, and can be used to generate task instances.

[0331] It should be noted that communication, perception, and computing are the three most important basic capabilities for building a freely connected physical and digital world. 6G will natively support communication, perception, and computing services, which means that 6G networks need to introduce new resource dimensions and provide on-demand comprehensive services including communication, information, synaesthesia, and computing, or a collection of comprehensive services, based on external business requests (including UE and OTT). The embodiments of the present application can solve the problems of how OTT or AF initiates task requests to the network, how the network allocates multiple resources (such as perception, computing resources, and communication) based on the task requests of OTT or AF, and how to ensure coordination between the allocated resources to ensure that the service quality requirements corresponding to the task are met as a whole.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0346] Task description;

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

[0348] Task strategy or QoS description;

[0349] Task parameters.

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

[0351] (1) Task description;

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

[0353] (3) Task strategy or QoS;

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

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

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

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

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

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

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

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

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

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

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

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

[0366] Random establishment;

[0367] concurrent builds;

[0368] Establish by priority.

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

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

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

[0372] Obtained from PCF or policy charging function;

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

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

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

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

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

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

[0379] 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 (Radio Resource Control, RRC) (can also be sub-task-related radio resource control RRC), task-related non-access stratum (Non-Access Stratum, NAS) signaling (can also be sub-task-related non-access stratum NAS signaling), or task-related radio signaling bearer (Signalling Radio Bearer, SRB) (can also be sub-task-related radio signaling bearer SRB).

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

[0381] See also Figure 3 , Figure 3 This is a flowchart of a task processing method provided by an embodiment of the present application. Figure 3 As shown, the task processing method includes the following steps:

[0382] Step 201: The second network element sends a first message to the first network element, where the first message is used to request to establish a target task.

[0383] The first message carries at least one of the following:

[0384] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0385] The target task template is used to represent task requirement information;

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

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

[0388] Optionally, the method further includes:

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

[0390] When the second message is used to indicate approval of the request corresponding to the first message, the second message carries at least one of the following:

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

[0392] Optionally, the method further includes:

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

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

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

[0396] Optionally, the first message is a task establishment request message, a task resource request message, a service establishment request message or a business establishment request message.

[0397] Optionally, the method further includes:

[0398] The second network element determines a task instance corresponding to the target task;

[0399] The second network element sends a fourth message to the first network element based on the task instance, where the fourth message is used to request: updating a task policy corresponding to the target task or a reserved resource corresponding to the target task.

[0400] Optionally, the fourth message carries at least one of the following:

[0401] The identifier of the second network element; task strategy information; subtask strategy information; instruction information for indicating the execution order of subtasks; QoT of the task; task QoT priority; QoT of the subtask.

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

[0403] The second network element sends a fifth message to the first network element, where the fifth message is used to request creation of a task template;

[0404] The second network element receives a sixth message sent by the first network element, where the sixth message carries task template information;

[0405] The second network element determines a target task template based on the task template information, wherein the first message carries the target task template.

[0406] It should be noted that this embodiment is Figure 2 The implementation method of the corresponding second network element in the embodiment shown in the figure can be found in the specific implementation method. Figure 2 To avoid duplication, the relevant descriptions of the embodiment shown will not be repeated in this embodiment.

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

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

[0409] Example 1:

[0410] This embodiment includes two parts: a strategy (pre-) negotiation process and a task establishment process.

[0411] like Figure 4 As shown, the task creation process includes the following steps:

[0412] Step (1) AF sends a first message to TM, where the first message is used to request the network to allocate network resources for the task.

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

[0414] Filled task templates;

[0415] Task description (e.g., “traffic jam situation,” “environment reconstruction”);

[0416] Description of task requirements;

[0417] Task QoE description (proxy UE forwarding);

[0418] DNN or S-NSSAI information;

[0419] Task strategy or QoS description;

[0420] The task ID or task session ID.

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

[0422] It should be noted that: 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 the external third-party application function body (possibly also some internal AF), and is responsible for opening network capabilities and internal network information; all external applications that want to access the internal data of the 6G core network need to go through the third network element. The third network element provides corresponding security guarantees to ensure the security of external applications to the 3gpp network, and provides functions such as external application requirements or target customization capability opening, mobility status event subscription, AF request distribution, etc. The third network element can be a network opening function, such as NEF.

[0423] Step (2) TM performs a first operation, including at least one of the following:

[0424] a. The TM verifies whether the task is a reasonable task requested by a legitimate AF. Specifically, if the AF has signed a contract for the task, the TM determines that the task request is legitimate; if the AF has not signed a contract for the task, the TM determines that the task request is illegitimate. The TM may directly reject the task request and directly execute step (5).

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

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

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

[0428] a first message received;

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

[0430] The task context associated with the target task stored or maintained by the TM. For example, if the TM has already generated a task instance for a similar task that meets the business requirements of the task requested by the AF, the TM can directly use the task instance;

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

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

[0433] c. The TM assigns a task identifier, and optionally, a subtask identifier;

[0434] If the first message contains a task identifier, the TM may use it as a reference.

[0435] The task session is used to exchange task related information (including signaling and data) between the UE and the TM and related subtask execution functions. If the target task is related to the UE, the TM and the UE need to establish a connection.

[0436] d. The TM allocates a task slice or a task DNN, and optionally allocates a subtask slice or a subtask DNN;

[0437] e. The TM selects a subtask management function that can meet the subtask requirements or subtask QoT.

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

[0439] Step (3). TM determines the subtask execution nodes and resources.

[0440] The TM determines the subtask execution nodes and resources using method 1 or method 2.

[0441] Method 1:

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

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

[0444] It should be noted that if Figure 5 As shown, steps 3-1 to 3-3 below are performed on demand. If the TM determines the order in which subtasks are established, the TM can interact with the subtask management function according to the order in which the subtasks are established. For example, if the task includes a perception task and a computation task, and the TM determines to establish the perception task first, followed by the computation task, the TM will first interact with the perception management function to establish the perception task, and then with the computation management function to establish the computation task.

[0445] If the TM determines that the subtask includes a perception task, it executes steps 3-1a and 3-1b:

[0446] 3-1a: If the TM determines that the subtask includes a sensing task, the TM sends a sensing task request message to the sensing management function, requesting the network to allocate sensing resources, including at least one of the following: sensing subtask policy or QoS, sensing subtask execution order, and sensing subtask identification.

[0447] 3-1b: The perception management function selects an appropriate perception execution function according to the perception task request information and assigns a subtask identifier, and optionally assigns a subtask slice or a subtask DNN;

[0448] The perception management function sends perception execution function information to TM, including at least one of the following: perception execution function IP address, ID information, FQDN, subtask identifier, allocated subtask slice or subtask DNN.

[0449] If the TM determines that the subtask includes a computing task, it executes steps 3-2a and 3-2b:

[0450] 3-2a: If the TM determines that the subtask includes a computing task, the TM sends a computing task request message to the computing management function, requesting the network to allocate computing resources, including at least one of the following: computing subtask policy or QoS, computing subtask execution order, and computing subtask identification.

[0451] 3-2b: The computing management function selects an appropriate computing execution function according to the computing task request information and allocates a subtask identifier, and optionally allocates a subtask slice or a subtask DNN;

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

[0453] If the TM determines that the subtask includes an AI task, it executes steps 3-3a and 3-3b:

[0454] 3-3a: If the TM determines that the subtask includes an AI task, the TM sends an AI task request message to the AI ​​management function, requesting the network to allocate AI resources, including at least one of the following:

[0455] AI subtask strategy or QoS;

[0456] The order in which AI subtasks are executed;

[0457] AI subtask identification;

[0458] Model complexity refers to the computational complexity of the model, such as the number of floating point operations (FLOPs) or multiplication and addition required;

[0459] Model training latency;

[0460] Model inference latency;

[0461] Model identification;

[0462] Model download address;

[0463] Data source information (data source address);

[0464] Hashrate size;

[0465] Calculation type.

[0466] 3-3b: The AI ​​management function selects an appropriate AI execution function (or AI resource node) based on the AI ​​task request information, assigns a subtask identifier, and optionally, assigns a subtask slice or subtask DNN;

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

[0468] It should be noted that the interaction between the TM and the subtask management function is on-demand. The subtask management function can dynamically notify the TM of the collected dynamic information of the subtask execution function, such as notifying the TM of the remaining computing power information of the calculation execution function (for example, notifying the TM through step 3-2b or other processes).

[0469] Method 2:

[0470] The TM selects a subtask execution function that can satisfy the subtask requirement or subtask QoT.

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

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

[0473] If the TM determines that the subtask includes a perception task, it executes steps 3-1a and 3-1b:

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

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

[0476] If the TM determines that the subtask includes a computing task, it executes steps 3-2a and 3-2b:

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

[0478] 3-2b: The computation execution function sends a computation subtask response to the TM. The response can be either acceptance or rejection. If the response is rejection, the TM needs to select another computation execution function that can execute the computation subtask. Optionally, the computation subtask response may also include computing power information (e.g., computing power size, computing power type, etc.) of the computation execution function.

[0479] If the TM determines that the subtask includes an AI task, it executes steps 3-3a and 3-3b:

[0480] 3-3a: If the TM determines that the subtask includes an AI subtask, the TM configures the AI ​​subtask information to the selected AI execution function, which is used to instruct the AI ​​execution function on the information required to execute the AI ​​subtask.

[0481] 3-3b: The AI ​​execution function sends an AI subtask response to the TM. The response can be either acceptance or rejection. If the response is rejection, the TM needs to select another AI execution function capable of executing the AI ​​subtask. Optionally, the AI ​​subtask response may also include at least one of the following: model acquisition address, model training address, supported AI frameworks (e.g., TensorFlow, PyTorch, etc.), and supported AI libraries and versions.

[0482] Step (4): The TM creates a task context based on the received subtask information, which is used to record the relationship between the QoT of the task and the task instance.

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

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

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

[0486] Step (5): The TM sends a response message to the AF (eg, a task establishment response message) to indicate the result of the task request.

[0487] The response message of the first message is an acceptance message, including at least one of the following: task identifier, subtask identifier, subtask execution function identifier (expression includes but is not limited to ID, IP address, FQDN), subtask management function identifier (expression includes but is not limited to ID, IP address, FQDN), task policy or QoS, subtask policy or QoS, subtask execution order, task slice or task DNN, subtask slice or subtask DNN.

[0488] or

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

[0490] The policy (pre) negotiation process includes the following steps:

[0491] Before step (1), a policy (pre) negotiation process may also be included; the policy (pre) negotiation process may be implemented by the following first or second method.

[0492] First way:

[0493] Step (0) (including steps 0~1-0~3) is the negotiation process of the task template. The task template here is customized. The customization here means that the task provider and the operator have signed a task level agreement, such as Figure 7 As shown, there is a task template for each task in the protocol. Steps 0 to 1-0 to 3 are optional.

[0494] Step 0-1. The AF sends a fifth message to the TM, requesting the 3GPP network to formulate a task template that meets the service requirements for one or more tasks. The fifth message includes at least one of the following:

[0495] ASP identification (Application Service Provider ID) information, used to identify an application server, including but not limited to ASPID, IP address, FQDN, and AF ID;

[0496] Task description;

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

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

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

[0500] The expected task template applicable area is used to indicate the geographical area (such as cell ID, TAI, geographical location) or network area (such as PLMN ID, SNPN ID) to which the task template is applicable;

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

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

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

[0504] Step 0-2. The TM generates or formulates a task template for one or more tasks based on at least one of the following:

[0505] The fifth message received;

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

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

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

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

[0510] The negotiated task template is a description of a customized task given by the network to the AF. It can be understood as a questionnaire, where the requester "checks" some required or optional parameters to express their requirements for the task. The content of the task template is described in step 0-1.

[0511] Step 0-3. The TM sends a sixth message to the AF, which is used to instruct the AF to formulate a task template that meets the task requirements for one or more tasks.

[0512] Second way:

[0513] Step (0) (including steps 0-1-0-2) is the negotiation process of the task template. Steps 0-1-0-2 are optional.

[0514] 0-1. AF performs task translation or decomposition to determine the task instance.

[0515] 0-2a. The UE and AF interact through the application layer, and the UE obtains the task instance.

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

[0517] Example 2:

[0518] like Figure 5 As shown, in this embodiment, the TM performs task translation and determines subtask management functions.

[0519] Step (0) is as follows: Figure 4 The first method in step (0) is shown.

[0520] Steps (1) to (2) are the same as steps (1) to (2) in Example 1.

[0521] Step (3) adopts method 1 in step (3) of embodiment 1.

[0522] Steps (4) to (5) are the same as steps (4) to (5) in Example 1.

[0523] Example 3:

[0524] like Figure 6 As shown, in this embodiment, the TM performs task translation and determines subtask execution functions.

[0525] Step (0) is as follows: Figure 4 The first method in step (0) is shown.

[0526] Steps (1) to (2) are the same as steps (1) to (2) in Example 1.

[0527] Step (3) adopts the method 2 in step (3) of embodiment 1. In this step, instead of determining the subtask management function, the subtask configuration information is directly determined.

[0528] Steps (4) to (5) are the same as steps (4) to (5) in Example 1.

[0529] Example 4:

[0530] like Figure 8 As shown, in this embodiment, the AF performs task translation, the UE obtains the task instance from the AF and initiates a task request, and the network selects a subtask execution function as needed.

[0531] Step (0) is as follows: Figure 4 The second method in step (0) is shown.

[0532] Step 0-1. AF performs task translation or decomposition and determines the task instance. The specific implementation of AF performing task translation or decomposition is similar to the process of TM performing task translation or decomposition, which will not be repeated here.

[0533] Step 0-2a. The UE and the AF interact through the application layer, and the UE obtains the task instance.

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

[0535] Step (1). AF sends a first message to TM, where the first message is used to request the network to allocate network resources for the task.

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

[0537] Task description (e.g., “traffic jam situation,” “environment reconstruction”);

[0538] DNN or S-NSSAI information;

[0539] Task policy or QoS;

[0540] Subtask policy or QoS;

[0541] Subtask execution order

[0542] The task ID or task session ID.

[0543] Step (2): The TM receives the first message and performs a first operation, including at least one of the following:

[0544] The TM verifies whether the task is a reasonable task requested by a legitimate AF. Specifically, if the AF has signed a contract for the task, the TM determines that the task request is legitimate; if the AF has not signed a contract for the task, the TM determines that the task request is illegitimate.

[0545] The TM assigns a task identifier;

[0546] The TM allocates task slices or task DNNs.

[0547] The TM selects a subtask management function or a subtask execution function that can satisfy the subtask strategy or requirement obtained from the AF.

[0548] Step (3) adopts method 1 in step (3) of embodiment 1.

[0549] Steps (4) to (5) are the same as those in Example 1.

[0550] In this embodiment, step (0) adopts the second method in step (0) of embodiment 1. In step (1), the first message carries the translated policy information, including task policy, subtask policy, and subtask execution order.

[0551] Embodiment 5:

[0552] like Figure 9 As shown, in this embodiment, the TM performs task translation and dynamically determines subtask information to the UE.

[0553] This embodiment is applicable to a scenario where the AF has only signed up for computing services, but the task requested by the AF includes two subtasks: communication and computing. When the TM receives such a task request, the TM needs to dynamically request the UE for the demand information of the communication subtask.

[0554] This embodiment differs from the first embodiment in that:

[0555] 1. In step (2), the TM determines that the task type is a composite task when performing task translation or decomposition, but the AF contract determines that the AF has only a single subtask contract. In this case, the TM cannot determine whether the task requirement provided by the AF is a computational subtask requirement or a complete task requirement. Alternatively, the TM can determine whether the requirement provided by the AF is a partial or complete task requirement based on the task template ID.

[0556] The TM determines the subtask strategy or QoS according to at least one of the following:

[0557] The task QoS description obtained from the UE. Before obtaining the task QoS description, the TM needs to perform step 2A-a or 2A-b;

[0558] Locally configured task QoS description.

[0559] Step 2A-a. Optionally, the TM requests the QoT of the subtask from the UE, including at least one of the following: task description, task QoE description, task identifier or task session identifier, subtask identifier or subtask session identifier, subtask type.

[0560] The TM may determine the UE through the UE identifier obtained in the previous task negotiation process, or determine the UE through the task template identifier or the task identifier;

[0561] Step 2A-b. The UE sends the task QoS description to the TM.

[0562] After executing step 2A-a or 2A-b, the TM can complete the task translation or decomposition process and determine the execution information of each subtask.

[0563] 2. In step (5), the TM not only sends a task establishment response message to the AF, but also sends a subtask establishment response message to the UE to inform the UE of the result of the subtask establishment.

[0564] The embodiment of the present application is based on TM and designs a service establishment and response process when AF or OTT initiates hybrid service requirements such as telecommuting, so that the network can respond to the telecommuting hybrid service requirements initiated by AF or OTT.

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

[0566] See Figure 10 , Figure 10 is a structural diagram of a task processing device provided in an embodiment of the present application, wherein the first network element includes the task processing device, such as Figure 10 As shown, the task processing device 300 includes:

[0567] A first receiving module 301 is configured to receive a first message sent by a second network element, where the first message is used to request establishment of a target task;

[0568] Establishing module 302, for establishing the target task;

[0569] The first message carries at least one of the following:

[0570] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0571] The target task template is used to represent task requirement information;

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

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

[0574] Optionally, the device further comprises:

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

[0576] When the second message is used to indicate approval of the request corresponding to the first message, the second message carries at least one of the following:

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

[0578] Optionally, the device further comprises:

[0579] A second sending module, configured to send a third message to the second network element;

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

[0581] The task identifier, subtask identifier, and task request quantity exceed the maximum value; requesting the target task is not allowed; the second network element is not authorized.

[0582] Optionally, the device further comprises:

[0583] The second receiving module is used to receive a fourth message sent by the second network element, where the fourth message is used to request: updating the task policy corresponding to the target task or the reserved resources corresponding to the target task.

[0584] Optionally, the fourth message carries at least one of the following:

[0585] The identifier of the second network element; task strategy information; subtask strategy information; instruction information for indicating the execution order of subtasks; QoT of the task; task QoT priority; QoT of the subtask.

[0586] Optionally, the device further comprises:

[0587] A third receiving module, configured to receive a fifth message sent by the second network element, where the fifth message is used to request creation of a task template;

[0588] A creation module, configured to create a task template based on the fifth message;

[0589] The second sending module is used to send a sixth message to the second network element, where the sixth message carries task template information.

[0590] Optionally, the establishing module is specifically configured to:

[0591] Obtaining first information;

[0592] Determine subtask strategy information or subtask QoT of the target task based on the first information;

[0593] The first network element allocates resources to the target task based on subtask strategy information or QoT of the subtask of the target task;

[0594] The first information includes at least one of the following:

[0595] Task quality information from the terminal; locally configured task quality information.

[0596] Optionally, the device further comprises:

[0597] A third sending module is used to send a seventh message to the terminal, where the seventh message is used to request the QoT of the subtask;

[0598] The fourth receiving module is used to receive the eighth message sent by the terminal, and the eighth message carries at least one of the following: task template of subtask; subtask description information; QoT of subtask; subtask DNN information; subtask slicing information; subtask strategy information; subtask identifier.

[0599] Optionally, the seventh message carries at least one of the following:

[0600] Task description information; task QoE description information; task ID; task session ID; subtask ID; subtask session ID; subtask type information; subtask QoE description information.

[0601] Optionally, the device further comprises:

[0602] A determination module, configured to determine the terminal based on at least one of the following:

[0603] Terminal ID; task template ID; task strategy ID; task ID.

[0604] Optionally, the establishment module is specifically used for at least one of the following:

[0605] The first network element determines the subtask management function corresponding to the target task, and sends a ninth message to the subtask management function, wherein the ninth message is used to request the subtask management function to allocate subtask resources;

[0606] The first network element determines a subtask execution function corresponding to the target task, and sends a tenth message to the subtask execution function, where the tenth message is used to indicate information related to subtask configuration;

[0607] determining, by the first network element, whether the second network element is authorized;

[0608] The first network element determines a task instance corresponding to the target task;

[0609] The first network element allocates at least one of a task identifier, a task slice, and a task DNN to the target task.

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

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

[0612] See Figure 11 , Figure 11 is a structural diagram of a task processing device provided in an embodiment of the present application, wherein the first network element includes the task processing device, such as Figure 11 As shown, the task processing device 400 includes:

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

[0614] The first message carries at least one of the following:

[0615] Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification;

[0616] The target task template is used to represent task requirement information;

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

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

[0619] Optionally, the device further comprises:

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

[0621] When the second message is used to indicate approval of the request corresponding to the first message, the second message carries at least one of the following:

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

[0623] Optionally, the device further comprises:

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

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

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

[0627] Optionally, the first message is a task establishment request message, a task resource request message, a service establishment request message or a business establishment request message.

[0628] Optionally, the device further comprises:

[0629] A determination module, configured to determine a task instance corresponding to the target task;

[0630] The second sending module is used to send a fourth message to the first network element based on the task instance, where the fourth message is used to request: updating the task policy corresponding to the target task or the reserved resources corresponding to the target task.

[0631] Optionally, the fourth message carries at least one of the following:

[0632] The identifier of the second network element; task strategy information; subtask strategy information; instruction information for indicating the execution order of subtasks; QoT of the task; task QoT priority; QoT of the subtask.

[0633] Optionally, the device further comprises:

[0634] A third sending module is used to send a fifth message to the first network element, where the fifth message is used to request to create a task template;

[0635] A second receiving module is configured to receive a sixth message sent by the first network element, where the sixth message carries task template information;

[0636] A determination module is configured to determine a target task template based on the task template information, wherein the first message carries the target task template.

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

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

[0639] Alternatively, as Figure 12 As shown, an embodiment of the present application further provides a communication device 500, including 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 is executed by the processor 501 to implement 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 repeated here. When the communication device 500 is a second network element, the program or instruction is executed by the processor 501 to implement 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 repeated here.

[0640] The embodiment of the present application further provides a network side device, which is a first network element or a second network element, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 2 or Figure 3 The network side device embodiment corresponds to the above method embodiment, and each implementation process and implementation method of the above method embodiment are applicable to the network side device embodiment and can achieve the same technical effect.

[0641] Specifically, the 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. Figure 13As shown, 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. Antenna 601 is connected to radio frequency device 602. In the uplink direction, radio frequency device 602 receives information via antenna 601 and sends the received information to baseband device 603 for processing. In the downlink direction, baseband device 603 processes the information to be transmitted and sends it to radio frequency device 602. Radio frequency device 602 processes the received information and then sends it through antenna 601.

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

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

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

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

[0646] Specifically, the 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. Figure 14 As shown, the network side device 700 includes: a processor 701, a network interface 702 and a memory 703. The network interface 702 is, for example, a common public radio interface (CPRI).

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

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

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

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

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

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

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

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

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

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

Claims

1. A task processing method, characterized in that: include: The first network element receives a first message sent by the second network element, where the first message is used to request to establish a target task; The first network element establishes the target task; The first message carries at least one of the following: Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification; The target task template is used to represent task requirement information; 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, characterized in that The method further comprises: The first network element sends a second message to the second network element; When the second message is used to indicate approval of the request corresponding to the first message, the second message carries at least one of the following: Task identification; subtask identification; identification of the subtask management function; identification of the subtask execution function; task strategy information; QoT of the task; subtask strategy information; QoT of the subtask; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

3. The method according to claim 1, characterized in that The method further comprises: The first network element sends a third message to the second network element; In a case where the third message is used to indicate rejection of the request corresponding to the first message, the third message carries first indication information, where the first indication information is used to indicate at least one of the following: The task identifier, subtask identifier, and task request quantity exceed the maximum value; requesting the target task is not allowed; the second network element is not authorized.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first network element receives a fourth message sent by the second network element, where the fourth message is used to request: updating a task policy corresponding to the target task or a reserved resource corresponding to the target task.

5. The method according to claim 4, characterized in that The fourth message carries at least one of the following: The identifier of the second network element; task strategy information; subtask strategy information; instruction information for indicating the execution order of subtasks; QoT of the task; task QoT priority; QoT of the subtask.

6. The method according to any one of claims 1 to 5, characterized in that Before the first network element receives the first message sent by the second network element, the method further includes: The first network element receives a fifth message sent by the second network element, where the fifth message is used to request creation of a task template; The first network element creates a task template based on the fifth message; The first network element sends a sixth message to the second network element, where the sixth message carries task template information.

7. The method according to any one of claims 1 to 6, characterized in that The first network element establishing the target task includes: The first network element obtains first information; The first network element determines subtask strategy information or subtask QoT of the target task based on the first information; The first network element allocates resources to the target task based on subtask strategy information or QoT of the subtask of the target task; The first information includes at least one of the following: Task quality information from the terminal; locally configured task quality information.

8. The method according to claim 7, characterized in that Before the first network element obtains the first information, the method further includes: The first network element sends a seventh message to the terminal, where the seventh message is used to request the QoT of the subtask; The first network element receives the eighth message sent by the terminal, and the eighth message carries at least one of the following: a task template of the subtask; subtask description information; QoT of the subtask; subtask DNN information; subtask slicing information; subtask strategy information; and subtask identifier.

9. The method according to claim 8, characterized in that The seventh message carries at least one of the following: Task description information; task QoE description information; task ID; task session ID; subtask ID; subtask session ID; subtask type information; subtask QoE description information.

10. The method according to claim 8 or 9, characterized in that Before the first network element sends the seventh message to the terminal, the method further includes: The first network element determines the terminal based on at least one of the following: Terminal ID; task template ID; task strategy ID; task ID.

11. The method according to any one of claims 1 to 10, characterized in that The first network element establishing the target task includes at least one of the following: The first network element determines the subtask management function corresponding to the target task, and sends a ninth message to the subtask management function, wherein the ninth message is used to request the subtask management function to allocate subtask resources; The first network element determines a subtask execution function corresponding to the target task, and sends a tenth message to the subtask execution function, where the tenth message is used to indicate information related to subtask configuration; determining, by the first network element, whether the second network element is authorized; The first network element determines a task instance corresponding to the target task; The first network element allocates at least one of a task identifier, a task slice, and a task DNN to the target task.

12. A task processing method, characterized in that: include: The second network element sends a first message to the first network element, where the first message is used to request to establish a target task; The first message carries at least one of the following: Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification; The target task template is used to represent task requirement information; 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.

13. The method according to claim 12, characterized in that The method further comprises: The second network element receives a second message sent by the first network element; When the second message is used to indicate approval of the request corresponding to the first message, the second message carries at least one of the following: Task identification; subtask identification; identification of the subtask management function; identification of the subtask execution function; task strategy information; QoT of the task; subtask strategy information; QoT of the subtask; indication information for indicating the execution order of subtasks; task slicing information; task DNN information; subtask slicing information; subtask DNN information.

14. The method according to claim 12, characterized in that The method further comprises: The second network element receives a third message sent by the first network element; In a case where the third message is used to indicate rejection of the request corresponding to the first message, the third message carries first indication information, where the first indication information is used to indicate at least one of the following: The number of task requests exceeds the maximum value; requesting the target task is not allowed; the second network element is not authorized.

15. The method according to any one of claims 12 to 14, characterized in that The first message is a task establishment request message, a task resource request message, a service establishment request message or a business establishment request message.

16. The method according to any one of claims 12 to 15, characterized in that The method further comprises: The second network element determines a task instance corresponding to the target task; The second network element sends a fourth message to the first network element based on the task instance, where the fourth message is used to request: updating a task policy corresponding to the target task or a reserved resource corresponding to the target task.

17. The method according to claim 16, characterized in that The fourth message carries at least one of the following: The identifier of the second network element; task strategy information; subtask strategy information; instruction information for indicating the execution order of subtasks; QoT of the task; task QoT priority; QoT of the subtask.

18. The method according to any one of claims 12 to 17, characterized in that Before the second network element sends the first message to the first network element, the method further includes: The second network element sends a fifth message to the first network element, where the fifth message is used to request creation of a task template; The second network element receives a sixth message sent by the first network element, where the sixth message carries task template information; The second network element determines a target task template based on the task template information, wherein the first message carries the target task template.

19. A task processing device, characterized in that: include: A first receiving module is configured to receive a first message sent by a second network element, where the first message is used to request establishment of a target task; An establishment module, used for establishing the target task; The first message carries at least one of the following: Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification; The target task template is used to represent task requirement information; 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.

20. A task processing device, characterized in that: include: A first sending module is used to send a first message to a first network element, where the first message is used to request to establish a target task; The first message carries at least one of the following: Target task template; task description information; task quality information QoT; task data network name DNN information; task slicing information; task strategy information; task identification; The target task template is used to represent task requirement information; 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.

21. A communication device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the task processing method according to any one of claims 1 to 11 are implemented, or the steps of the task processing method according to any one of claims 12 to 18 are implemented.

22. A chip, characterized in that: 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 described in any one of claims 1-11, or to implement the steps of the task processing method described in any one of claims 12-18.

23. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the task processing method according to any one of claims 1 to 11 are implemented, or the steps of the task processing method according to any one of claims 12 to 18 are implemented.

24. A computer program / program product, characterized in that 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 11, or implements the steps of the task processing method according to any one of claims 12 to 18.

Images