Transmission processing method and apparatus, terminal, and network side device

Abstract

The present application relates to the technical field of communications, and discloses a transmission processing method and apparatus, a terminal, and a network side device. The transmission processing method in embodiments of the present application comprises: a first network side device receives a first message from a terminal, the first message being used for establishing a target task; the first network side device sends a first response message to the terminal on the basis of the first message, the first response message being used for indicating a request result of the target task, wherein the first response message satisfies at least one of the following: when the first network side device accepts the target task, the first response message comprises at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name (DNN), and information of a sub-task, and the sub-task is associated with the target task; and when the first network side device rejects the target task, the first response message is a rejection message.

Description

Transmission processing method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

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

[0003] The present application belongs to the field of communication technology, and specifically relates to a transmission processing method, apparatus, terminal and network-side equipment. Background Art

[0004] Communication, perception and computing are three important basic capabilities for building a freely connected physical and digital world. th 5G networks typically only provide a single channel for data transmission, such as through protocol data unit (PDU) sessions, which establish communication resources between terminals and the data network. However, in future communication networks (such as 6G), task management based on PDU sessions cannot meet the needs of future communication networks due to the need to support services such as communication, perception, and computing. Therefore, for networks that support services such as communication, perception, and computing, how to implement task management has become an urgent problem that needs to be solved. Summary of the Invention

[0005] The embodiments of the present application provide a transmission processing method, apparatus, terminal, and network-side equipment, which can solve the problem of how to implement task management for a network that supports services such as communication, perception, and computing.

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

[0007] The first network-side device receives a first message from the terminal, where the first message is used to establish a target task;

[0008] The first network-side device sends a first response message to the terminal based on the first message, where the first response message is used to indicate the request result of the target task;

[0009] The first response message satisfies at least one of the following conditions:

[0010] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name DNN, and subtask information, where the subtask is associated with the target task;

[0011] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

[0012] In a second aspect, a transmission processing method is provided, including:

[0013] The terminal sends a first message to the first network side device, where the first message is used to establish a target task;

[0014] The terminal receives a first response message from the first network-side device, where the first response message is used to indicate a request result of the target task;

[0015] Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; target task quality of experience QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; target task identifier; target task session identifier.

[0016] In a third aspect, a transmission processing device is provided, including:

[0017] A first receiving module is used to receive a first message from a terminal, where the first message is used to establish a target task;

[0018] A first sending module, configured to send a first response message to the terminal based on the first message, wherein the first response message is used to indicate the request result of the target task;

[0019] The first response message satisfies at least one of the following conditions:

[0020] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name DNN, and information about a subtask, where the subtask is associated with the target task;

[0021] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

[0022] In a fourth aspect, a transmission processing device is provided, including:

[0023] A second sending module is used to send a first message to the first network side device, where the first message is used to establish a target task;

[0024] A second receiving module is configured to receive a first response message from the first network-side device, where the first response message is used to indicate a request result of the target task;

[0025] Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; target task quality of experience QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; target task identifier; target task session identifier.

[0026] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0027] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is configured to send a first message to a first network-side device, the first message being configured to establish a target task; and receive a first response message from the first network-side device, the first response message being configured to indicate a request result for the target task.

[0028] Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; task experience quality target task QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; target task identifier; target task session identifier.

[0029] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0030] In an eighth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive a first message from a terminal, the first message being configured to establish a target task; and send a first response message to the terminal based on the first message, the first response message being configured to indicate a request result for the target task;

[0031] The first response message satisfies at least one of the following conditions:

[0032] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name DNN, and information about a subtask, where the subtask is associated with the target task;

[0033] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

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

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

[0036] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0037] In the twelfth aspect, a computer program / program product is provided, wherein the computer program / program product includes computer instructions, and the computer program / program product is executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0038] In an embodiment of the present application, a first message is received from a terminal through a first network-side device, and the first message is used to establish a target task; the first network-side device sends a first response message to the terminal based on the first message, and the first response message is used to indicate the request result of the target task. In this way, a task-centric request is made to establish a target task, so that the network can allocate task resources for one or more subtasks associated with the target task, thereby realizing task management in a network that supports services such as communication, perception, and computing. At the same time, since resource allocation for multiple subtasks associated with the target task can be achieved through one signaling message, signaling overhead can be saved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0040] FIG2 is a flow chart of a transmission processing method according to an embodiment of the present application;

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

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

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

[0044] FIG6 is a schematic structural diagram of a transmission processing device provided in an embodiment of the present application;

[0045] FIG7 is a schematic structural diagram of another transmission processing device provided in an embodiment of the present application;

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

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

[0048] FIG10 is a schematic structural diagram of a network-side device provided in an embodiment of the present application;

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

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

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

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

[0053] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) 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.

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

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

[0056] 1. PDU session

[0057] A PDU session is the process of communication between a user terminal (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, if a UE wants to transmit data to an application, it must first establish a PDU session. In other words, a PDU session is the communication resource established between the UE and the data network in a 5G network.

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

[0059] 2. Task session: refers to the process of communication between a UE and Task Management (TM), or the process of communication between the UE, 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 task bearer. A task session or subtask session can sometimes also be implemented by a PDU session. The task session in this application is different from the PDU session (data channel between the UE and the UPF) in the prior art. For example, in the prior art, if the UE wants to use the perception service, the UE will establish a PDU session (data channel between the UE and the UPF). When the data reaches the UPF, the UPF may use some non-standard methods to transfer it to the perception execution node.

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

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

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

[0063] 3. Synaesthesia integration.

[0064] 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 Quality of Service (QoS) guarantees. Its primary purpose is to provide connectivity for data transmission, support user mobility, and guarantee a reliable user experience.

[0065] In terms of resource types, non-cloud-based devices typically utilize dedicated computing resources, with low demands for both computing and storage resources. Unlike traditional communications services, artificial intelligence (AI) is data- and compute-intensive. To enable 6G networks to have native AI capabilities, new resource dimensions must be introduced, including heterogeneous computing and storage resources, new computing tasks (AI-related computing), and new data types (AI computing input and output data), requiring the design of corresponding management and control mechanisms. Furthermore, 6G networks will possess more comprehensive perception capabilities, including target detection, positioning (distance and angle), speed measurement, and three-dimensional (3D) imaging, and will introduce solutions based on radar echoes. These new network capabilities, including AI and perception, will involve the coordination and deployment of computing power, connectivity, algorithms, and data resources in multi-node scenarios to achieve specific goals.

[0066] Currently, the 5G system can only provide a pipeline for data transmission, which is insufficient to support the goal of 6G network to achieve the integration of telecom and computing. The impact of achieving telecom and computing integration on network architecture needs to be studied. To this end, the transmission processing method of this application is proposed.

[0067] The transmission processing method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0068] 2 , an embodiment of the present application provides a transmission processing method. As shown in FIG2 , the transmission processing method includes:

[0069] Step 201: A first network-side device receives a first message from a terminal, where the first message is used to establish a target task.

[0070] Step 202: The first network-side device sends a first response message to the terminal based on the first message, where the first response message is used to indicate the request result of the target task;

[0071] The first response message satisfies at least one of the following conditions:

[0072] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name (DNN), and subtask information, where the subtask is associated with the target task;

[0073] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

[0074] In an embodiment of the present application, the first message used to establish the target task can be understood as the first message being used to request the allocation of network resources for the target task or a subtask associated with the target task. Allocating network resources can be understood as establishing network resources, such as establishing a task session, establishing a subtask session. The above-mentioned target task can be understood as a specific business task, such as a 6G system that provides comprehensive services including communication, information, synaesthesia, and computing on demand based on external business requests. In an optional implementation method, there can be multiple classification methods for the subtask types in the target task. In an optional implementation method, one or more subtasks obtained by disassembling the target task can be understood as subtasks associated with the target task.

[0075] For example, the subtasks may include but are not limited to communication subtasks, perception subtasks, computing subtasks, data subtasks, positioning subtasks, Internet Protocol Multimedia System (IMS) subtasks, AI subtasks, and the like.

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

[0077] Optionally, in some embodiments, the first network side device can be understood as a newly added network function (for example, a network side device with a task management (TM) function) or an enhancement of an existing network function so that the existing network function has all or part of the functions of the first network side device. For example, an enhancement of AMF, SMF or PCF. Optionally, task management can be understood as a management process that provides communication functions and other 6G additional functions (such as positioning, synaesthesia, computing, etc.) with the goal of responding to external business requests.

[0078] It should be noted that the above-mentioned first response message can be understood as the response message corresponding to the target task, that is, the information included in the first response message is the information associated with the target task. For example, the above-mentioned target task identifier can be understood or replaced by the target task's task identifier; the above-mentioned target task session identifier can be understood or replaced by the target task's task session identifier; the above-mentioned target task strategy can be understood or replaced by the target task's task strategy; the above-mentioned target task slice can be understood or replaced by the target task's task slice or the slice that identifies the data network in the target task's task session; the above-mentioned target task DNN can be understood or replaced by the target task's task DNN or the DNN that identifies the data network in the target task's task session.

[0079] It should be understood that a task session is a channel for the interaction of data units between a terminal and a data network. At least one of a DNN and a slice can be used to identify the data network in the task session. In some embodiments, a target task session has one DNN or slice. Another implementation method is that a subtask session has one DNN or slice.

[0080] In an optional implementation, the target task session can be understood as a task session used to transmit the target task or a task session corresponding to the target task. The target task session can also be understood as a channel for the terminal and the data network (identified by the target task DNN) to interact with data or signaling.

[0081] In an embodiment of the present application, a first message is received from a terminal through a first network-side device, and the first message is used to establish a target task; the first network-side device sends a first response message to the terminal based on the first message, and the first response message is used to indicate the request result of the target task. In this way, a task-centric request is made to establish a target task, so that task resources can be allocated to one or more subtasks associated with the target task, thereby realizing task management in a network that supports services such as communication, perception, and computing. At the same time, since resource allocation for multiple subtasks associated with the target task can be achieved through one signaling message, signaling overhead can be saved.

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

[0083] Correspondingly, the first network side device has a peer first protocol layer for communication between the terminal and the first network side device, and the first response message can be generated or processed by the first protocol layer of the first network side device.

[0084] Optionally, in some embodiments, the first message includes at least one of the following:

[0085] First information of the request, where the first information is used to indicate requirement information corresponding to the target task;

[0086] Target task description information;

[0087] Target task quality of experience (QoE);

[0088] Target task DNN;

[0089] Single Network Slice Selection Assistance Information (S-NSSAI) associated with the target task;

[0090] Target mission strategy;

[0091] Target task quality information;

[0092] Target task identification;

[0093] Target task session ID.

[0094] In the embodiment of the present application, the target task quality information may be understood or replaced by target task QoS; the first information may be understood or replaced by a task template. Optionally, the requirement information may include at least one of the following:

[0095] Target task description information: used to indicate the target type of the task, that is, to indicate what the task is. For example, if the task is to perceive traffic congestion in the target area, the target task description information is "traffic congestion"; if the task is to park the vehicle at a suitable or specified location, the target task description information is "automatic parking"; or task information used to identify the application of task parameters, including at least one of the following: target task DNN, S-NSSAI associated with the target task, AF identifier, and APP identifier;

[0096] Target Task Quality of Experience (QoE): This indicates the user's subjective perception of the quality and performance of a task. It refers to the user's perceived ease or difficulty in completing the entire task. This can be characterized by the level of user experience achieved.

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

[0098] Task parameters: parameters used to indicate the target task, which may include subtask configuration information. For example, if the target task includes a perception task and a computing task, the task parameters include the perception task configuration information and the computing task configuration information.

[0099] Optionally, if the subtask type is a perception subtask, the perception subtask configuration information includes at least one of the following:

[0100] The sensing measurement method may include at least one of the following methods: 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, base station transmitting and base station receiving. "Transmitting" refers to sending measurement signals, and "receiving" refers to receiving measurement signals and performing measurements.

[0101] The sensing service may include at least one of the following: a wide sensing range and high real-time requirement, a wide sensing range and low real-time requirement, a small sensing range and high real-time requirement, or a small sensing range and low real-time requirement. Optionally, in some embodiments, specific sensing services may be represented by numbers, letters, or other character strings indicating these services.

[0102] The sensing purpose may include one or more applications that require sensing services supported by the sensing device, such as respiratory monitoring and surrounding traffic environment monitoring;

[0103] A sensing measurement signal indicates a signal supported by the sensing device (which can be sent or received, or both sent and received) for sensing 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;

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

[0105] Perception resolution refers to the ability to distinguish multiple perceived targets from different dimensions, including distance resolution, velocity resolution, and angle resolution.

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

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

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

[0109] Optionally, if the subtask type is a computing subtask, the computing subtask configuration information includes at least one of the following:

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

[0111] Data processing delay, which indicates the overall delay between data collection and data calculation;

[0112] Calculation accuracy, which is used to indicate the accuracy of data collection and the overall accuracy of data calculation;

[0113] Computing power information, including at least one of the following: computing power size and computing power type.

[0114] Optionally, if the subtask type is an AI subtask, the computing subtask configuration includes at least one of the following: model complexity, which refers to the representation capability of the model, that is, the complexity of the data that the model can fit; model training time; model inference time; model identification; model download address; data source information (such as data source address); computing power; and calculation type.

[0115] Optionally, in some embodiments, taking automatic parking as an example, the framework of the automatic parking task template includes general parameters, perception task parameters, and calculation task parameters, wherein:

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

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

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

[0119] It should be understood that the above task template is a framework description (without specific numerical description), and the task instance is obtained after the terminal fills (or sets) or the first network side device combines the target task strategy or target task quality information to translate it.

[0120] Task instance: An ongoing task may have a corresponding task context. Different network elements may store different task contexts for the same task instance. Optionally, in some embodiments, the task instance includes at least one of the following:

[0121] Task description information;

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

[0123] Mission strategy;

[0124] Task quality information;

[0125] Security-related parameters, information used to encrypt transmitted signaling or data;

[0126] Subtask type, used to indicate the type of subtask, including at least one of the following: perception, computing, AI.

[0127] Optionally, a task session refers to a process of communication between a UE and a first network side device or a UE and a first network side device and related subtask functions. A task session may correspond to one or more subtask sessions (a subtask session refers to a process of communication between a first network side device and a subtask function). Establishing a task session is to establish a data transmission channel between the UE and the first network side device and related subtasks, that is, a task session is a network resource established between the UE and the first network side device and related subtask functions in the operator network. A task session may also be referred to as a task connection or a task bearer. A task session or a subtask session may sometimes also be implemented by a PDU session.

[0128] Optionally, the target task session identifier is used to identify the task session, and is allocated by the UE and sent to the network or allocated by the first network-side device. The subtask session identifier is used to identify the subtask session, and the subtask session identifier can be allocated by the UE and sent to the network, or allocated by the TM, or allocated by the subtask management, or allocated by the subtask function. The target task session identifier and the subtask identifier have a one-to-one mapping relationship or a one-to-many mapping relationship (i.e., one task is a combined task).

[0129] It should be noted that, in some embodiments, the first network-side device may be a network device that implements at least one of the following functions:

[0130] (1) Task Verification: Verify whether a task is a reasonable task requested by a legitimate task consumer or requester (including but not limited to UE or second network-side device). This includes at least one of the following: verify whether the second network-side device allows the request for a task template, whether the task request comes from a legitimate UE (whether the UE has a task contract), whether the task request comes from a legitimate second network-side device (based on whether there is a task agreement between the first network-side device and the second network-side device), and whether the task exceeds the upper limit of the number of tasks associated with the UE or the second network-side device.

[0131] Optionally, if the task request comes from the second network-side device, the task verification function may be implemented by the NEF.

[0132] (2) Task Template Generation: A task template is determined through negotiation with the second network-side device. The task template is a description of a customized task given by the network to the UE. Different task types may have one or more task templates. Optionally, the task template can be requested in the form of a questionnaire. That is, the task template includes multiple options or multiple parameter requirements. The terminal (i.e., the requester) can fill in the task template (i.e., "check" some parameter requirements in the task template) to express its requirements for the task.

[0133] Optionally, the task template includes at least one of the following:

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

[0135] Target task description information;

[0136] Target task QoE;

[0137] Target mission strategy;

[0138] Target task quality information;

[0139] Task parameters;

[0140] (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:

[0141] Target task description information;

[0142] The task type is 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.

[0143] Target mission strategy;

[0144] Target task quality information;

[0145] Security-related parameters, information used to encrypt transmitted signaling or data;

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

[0147] The subtask policy or subtask quality information is used to indicate the service quality requirement of the subtask.

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

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

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

[0151] The temporal relationship of subtasks includes at least one of the following:

[0152] The subtask execution order is used to indicate the temporal relationship of the subtask execution, including at least one of the following implementation methods: the first network side device informs the subsequent subtask execution node of the information of the preceding subtask execution node; the first network side device acts as the central control node for task execution, the preceding subtask execution node informs the first network side device of the result of the preceding subtask, and the first network side device informs the subsequent subtask execution node of the result of the preceding subtask; for example, the task includes a perception subtask and a computing subtask, and the first network side device determines that the perception subtask is the preceding subtask, then the first network side device informs the computing function of the perception function address, then after the computing function receives data from the perception function, the computing function can start executing the computing subtask;

[0153] The subtask bearer establishment order is used to indicate the temporal relationship of the subtask bearer establishment, including at least one of: random establishment; concurrent establishment; establishment according to priority.

[0154] Optionally, the subtask temporal relationship may be a part of the subtask strategy or subtask quality information.

[0155] 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: target task description information, task type, target task strategy, target task quality information, and security-related parameters. Specific parameters describe the QoS requirements for specific subtasks and include at least one of the following: subtask type, subtask strategy or subtask quality information, and subtask execution order.

[0156] It should be noted that when the first network side device determines the target task strategy, target task quality information, sub-task strategy or sub-task quality information, it can also be implemented in the following ways: obtaining from PCF or the function responsible for policy billing; determining the target task strategy, target task quality information, sub-task strategy or sub-task quality information based on the information obtained from PCF or the function responsible for policy billing.

[0157] (4) allocating at least one of a target task identifier and a target task session identifier, and optionally, allocating at least one of a subtask identifier and a subtask session identifier;

[0158] (5) allocating at least one of a target task slice and a target task DNN, and optionally, allocating at least one of a subtask slice and a subtask DNN;

[0159] (6) Selecting a subtask management function or subtask function: The first network-side device selects a subtask management function or subtask function that can meet the subtask quality information. Specifically, the first network-side device may query the NRF, UDM, or UDR to determine a suitable subtask management function or subtask function, or the first network-side device may determine a suitable subtask management function or subtask function based on stored or maintained information (e.g., whether the task is supported, computing power size, etc.).

[0160] Optionally, the above-mentioned second network side device can be understood or replaced by AF.

[0161] Optionally, in some embodiments, before the first network-side device receives the first message from the terminal, the method further includes:

[0162] The first network-side device receives a second message from the second network-side device, where the second message is used to request generation of first information that meets task requirements for a target task;

[0163] The first network-side device generates first information for the target task.

[0164] In an embodiment of the present application, the second message may request generation of first information that meets task requirements for one or more target tasks.

[0165] Optionally, in some embodiments, the second message includes at least one of the following:

[0166] Target identification information, the target identification information is used to indicate the application server corresponding to the task provider;

[0167] Task description information;

[0168] identification information of the first information;

[0169] Task DNN;

[0170] Task-related S-NSSAI;

[0171] a time window of the expected first information, where the time window of the first information is used to indicate a time when the first information is applicable;

[0172] an applicable area of ​​the desired first information, where the applicable area of ​​the first information is used to indicate a geographical area or network to which the first information is applicable;

[0173] Subscribe to notifications of changes to the first information, for instructing the second network side device to be notified when the first information is updated;

[0174] Task quality information.

[0175] In this embodiment of the present application, the first network-side device and the second network-side device may negotiate first information of one or more tasks based on the second message. That is, the generated first information may include at least one of the following:

[0176] one or more target identification information in the second message;

[0177] identification information of one or more first information in the second message;

[0178] One or more task DNNs in the second message;

[0179] The S-NSSAI associated with one or more tasks in the second message;

[0180] One or more task quality information in the second message.

[0181] Optionally, the time window of the above-mentioned first information can be understood as the effective time of the first information. For example, if the task consumer requests to use the first information outside the time window of the first information, the first network side device can reject the request; similarly, the applicable area of ​​the above-mentioned first information can be understood as the effective area of ​​the first information. If the task consumer requests to use the first information outside the applicable area of ​​the first information, the first network side device can reject the request.

[0182] Optionally, in some embodiments, the target identification information may include but is not limited to: Application Service Provider ID (ASPID), Identity (IP) address, Fully Qualified Domain Name (FQDN), and the identifier of the second network side device.

[0183] The identification information of the first information can be used to indicate the first information, and can be expressed in the form of the identification of the first information.

[0184] When the second message is a multi-task request message (i.e., a request to generate first information for multiple target tasks, or a request to generate first information for one target task, and the target task includes multiple subtasks), it can carry at least one of multiple different DNNs and multiple different S-NSSAIs.

[0185] The time window of the desired first information may be a continuous time or a set of several intervals of time.

[0186] Optionally, the geographic area to which the first information applies may be represented by a cell identifier, a tracking area identity (TAI), or a geographic location. The network to which the first information applies may be represented by a public land mobile network (PLMN) ID or a stand-alone non-public network (SNPN) ID.

[0187] Optionally, the target task quality information (Quality of Task, QoT) may include at least one of the following: a QoT reference (QoT Reference) and an individual QoT parameter (individual QoT parameter).

[0188] Optionally, in some embodiments, the second message may be understood as a first information negotiation request message or a first information generation request message. The second message may be sent to the first network side device via the NEF or directly from the second network side device to the first network side device.

[0189] Optionally, in some embodiments, the first network-side device generating the first information for the target task includes:

[0190] The first network-side device generates first information for the target task based on at least one of the following:

[0191] the second message;

[0192] local configuration of the first network-side device;

[0193] first information associated with the target task stored by the first network-side device;

[0194] first information associated with the target task stored in the third network-side device;

[0195] The intelligent function in the first network side device is used to generate first information according to the requirement information corresponding to the target task.

[0196] In the embodiment of the present application, the above-mentioned local configuration can be understood or replaced by a local policy or an operator policy.

[0197] Optionally, the first information associated with the target task stored by the first network side device can be understood or replaced by the first information associated with the target task maintained by the first network side device. For example, the first network side device has generated or formulated similar first information that can meet the task requirements requested by the second network side device, then the first network side device can directly use the first information.

[0198] Optionally, the third network side device may be understood as a UDM or a UDR. The first information associated with the target task stored in the third network side device may be understood as or replaced by the first information associated with the target task maintained in the third network side device.

[0199] Optionally, the intelligent function can be trained based on a large amount of input and output data, and after reaching a suitable accuracy, it can be used to generate the first information.

[0200] Optionally, in some embodiments, the method further comprises:

[0201] The first network-side device sends a second response message to the second network-side device, where the second response message is used to indicate a request result for the first information of the target task.

[0202] For example, in some embodiments, the second response message may carry indication information, where the indication information is used to indicate whether the first information that meets the task requirement is generated for the target task.

[0203] Optionally, in some embodiments, the method further comprises:

[0204] The first network-side device performs a target operation;

[0205] The first network-side device generates the first response message based on the execution result of the target operation;

[0206] The target operation includes at least one of the following:

[0207] Verify whether the target task is an authorized or permitted task;

[0208] Determine a task instance of the target task;

[0209] assigning at least one of a target task identifier and a target task session identifier;

[0210] Allocate at least one of a target task slice and a target task DNN;

[0211] Select a target subtask management function that satisfies the subtask quality information or subtask policy, or select a target subtask function that satisfies the subtask quality information or subtask policy.

[0212] Optionally, verifying whether the target task is an authorized or permitted task can be understood as verifying whether the target task or the request for the target task is legal, authorized or permitted. For example, if the terminal has a contract for the target task, the first network side device determines that the target task or the request for the target task is legal; if the terminal does not have a contract for the target task, the first network side device determines that the target task or the request for the target task is illegal, and the first network side device can directly reject the request for the target task.

[0213] Optionally, determining the task instance of the target task can be understood as replacing the first network-side device translating or decomposing the first message into a task instance. In some embodiments, determining the task instance of the target task includes at least one of the following:

[0214] In a case where the first message includes first requested information, mapping the first requested information into a task instance;

[0215] In a case where the first message does not include the requested first information, generating a task instance of the target task according to the second information;

[0216] The second information includes at least one of the following:

[0217] information carried by the first message;

[0218] a local configuration of the first network-side device, the local configuration comprising at least one of subtask quality information and a subtask strategy;

[0219] first information associated with the target task stored by the first network-side device;

[0220] first information associated with the target task stored in the third network-side device;

[0221] The intelligent function in the first network side device.

[0222] In an embodiment of the present application, the first message does not include the requested first information, which can be understood as the first message does not include the requested first information, but includes at least one of the following target task description information; target task quality of experience QoE; target task DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task policy; target task quality information; target task identifier; target task session identifier.

[0223] Optionally, the information carried by the above-mentioned first message can be understood as the content carried in the above-mentioned first message, that is, including at least one of the following: the first information of the request; the target task quality of experience QoE; the target task DNN; the single network slice selection auxiliary information S-NSSAI associated with the target task; the target task strategy; the target task quality information; the target task identifier; the target task session identifier.

[0224] Optionally, if the first message includes a target task identifier or a target task session identifier, the first network-side device may use it as a reference to allocate the target task identifier or the target task session identifier. The task session is used to exchange task-related information (including signaling and data) between the UE and the first network-side device and related subtask functions.

[0225] Optionally, the first network-side device may query the third network-side device to determine an appropriate subtask management function, or the first network-side device may determine an appropriate subtask management function according to stored or maintained subtask capabilities.

[0226] Optionally, in some embodiments, when the task signed by the terminal is a single task, the method further includes:

[0227] The first network side device sends a target request message to the second network side device, where the target request message is used to request to obtain subtask information of the subtask associated with the target task;

[0228] The first network side device receives the subtask information from the second network side device;

[0229] The subtask information includes at least one of subtask strategy and subtask quality information.

[0230] In an embodiment of the present application, when performing task translation or decomposition, the first network-side device determines that the task type is a combined task. However, the UE's contract determines that the UE is only contracted for a single subtask. The first network-side device cannot determine whether the task requirement provided by the UE is a communication subtask requirement or a complete task requirement. In this case, the first network-side device can perform at least one of the following to obtain the task requirement:

[0231] Get the subtask information stored locally;

[0232] The second network side device sends third request information.

[0233] Optionally, in some embodiments, the third request information may include at least one of the following: target task description information, target task QoE, target task identifier, target task session identifier, subtask identifier, subtask session identifier, and subtask type. Optionally, the first network device may determine the second network device by using the identifier of the second network device obtained during the previous task negotiation process. When the second network device receives the target request message, it may send subtask information of the subtask associated with the target task to the first network device via a response message.

[0234] Optionally, in some embodiments, after determining the task instance of the target task, the method further includes:

[0235] The first network side device sends a third message to the target subtask management function, where the third message is used to request to establish the subtask;

[0236] The first network-side device receives a third response message from the target subtask management function, where the third response message is used to indicate an establishment result of the subtask;

[0237] The target subtask management function is a subtask management function for executing the subtask management.

[0238] In an embodiment of the present application, the target subtask management function corresponds to the subtask associated with the above-mentioned target task. For example, when the subtask includes a perception task, the corresponding target subtask management function can be understood as the target perception task management function; when the subtask includes a computing task, the corresponding target subtask management function can be understood as the target computing task management function; when the subtask includes an AI task, the corresponding target subtask management function can be understood as the target AI task management function.

[0239] Optionally, if the first network-side device determines the order in which the subtask bearers are established, the first network-side device may interact with the subtask management function in accordance with the order in which the subtask bearers are established (including sending a third message and receiving a third response message). For example, the target task includes a perception task and a computing task, and the first network-side device determines to first establish the perception task bearer and then establish the computing task bearer. In this case, the first network-side device first interacts with the perception management function to establish the perception task bearer and then interacts with the computing management function to establish the computing task bearer.

[0240] Optionally, in some embodiments, when the subtask includes a perception task, the interaction process includes:

[0241] The first network-side device sends a sensing task request message (i.e., a third message) to the target sensing management function, where the sensing task request message is used to request allocation of sensing resources;

[0242] The first network side device receives a third response message from the target perception management function, where the third response message carries perception function information;

[0243] The perception function information includes at least one of the following: address information of the target perception function, identification information of the target perception function, fully qualified domain name of the target perception function, perception subtask identification information (or perception task identification information), perception subtask session identification information (or perception task session identification information), perception subtask slice (or perception task slice), and perception subtask DNN (or perception task DNN).

[0244] Among them, the target perception function is a perception function used to perform the perception task.

[0245] In an embodiment of the present application, the target perception management function may select an appropriate perception function based on the received perception task request message and assign at least one of a subtask identifier and a subtask session identifier, and optionally at least one of a subtask slice and a subtask DNN. Subsequently, the target perception management function sends the perception function information to the first network-side device via a third response message.

[0246] Optionally, the perception task request message includes at least one of the following: perception subtask strategy, perception subtask quality information, temporal relationship of subtasks, perception subtask slices and perception subtask DNN.

[0247] Optionally, in some embodiments, when the subtask includes a computing task, the interaction process includes:

[0248] The first network-side device sends a computing task request message (i.e., a third message) to the target computing management function, where the computing task request message is used to request allocation of computing resources;

[0249] The first network-side device receives a third response message from the computing management function, where the third response message carries computing function information;

[0250] The computing function information includes at least one of the following: address information of the target computing function, identification information of the target computing function, fully qualified domain name of the target computing function, computing subtask identification information (or computing task identification information), computing subtask session identification information (or computing subtask session identification information), computing subtask slice, and computing subtask DNN (or computing task DNN);

[0251] The target computing function is a computing function used to execute the computing task.

[0252] Optionally, the computing task request message includes at least one of the following: computing subtask strategy, computing subtask quality information, subtask timing relationship, computing subtask slices, and computing subtask DNN.

[0253] In an embodiment of the present application, the target computing management function may select an appropriate computing function based on the received computing task request message and assign at least one of a subtask identifier and a subtask session identifier, and optionally, at least one of a subtask slice and a subtask DNN. Subsequently, the target computing management function sends the computing function information to the first network-side device via a third response message.

[0254] Optionally, in some embodiments, when the subtask includes an AI task, the interaction process includes:

[0255] The first network-side device sends an AI task request message (i.e., a third message) to the AI ​​management function, where the AI ​​task request message is used to request allocation of AI resources;

[0256] The first network-side device receives a third response message from the AI ​​management function, where the third response message carries AI function information;

[0257] The AI ​​function information includes at least one of the following: address information of the target AI function, identification information of the target AI function, fully qualified domain name of the target AI function, model acquisition address, model training address, AI subtask identification information (or referred to as AI task identification information), AI subtask session identification information (or referred to as AI task session identification information), AI subtask slice (or referred to as AI task slice), and AI subtask DNN (or referred to as AI task DNN);

[0258] The target AI function is an AI function used to execute the AI ​​task.

[0259] Optionally, the AI ​​task request message includes at least one of the following: AI subtask strategy, AI subtask quality information, subtask timing relationship, AI subtask slicing, AI subtask DNN, model complexity, model training time, model inference time, model identification, model download address, data source information, computing power and calculation type.

[0260] In this embodiment of the present application, the target AI management function may select an appropriate AI function based on the received AI task request message and assign at least one of a subtask identifier and a subtask session identifier, and optionally at least one of a subtask slice and a subtask DNN. Subsequently, the target AI management function sends the AI ​​function information to the first network-side device via a third response message.

[0261] Optionally, in some embodiments, after selecting a subtask that satisfies the subtask quality information or the target subtask function of the subtask, the method further includes:

[0262] The first network-side device sends a fourth message to the target subtask function, where the fourth message is used to indicate information required for the target subtask function to execute the subtask;

[0263] The first network-side device receives a fourth response message from the target subtask function, where the fourth response message is used to indicate to the target subtask function whether to accept or refuse to execute the subtask.

[0264] In this embodiment of the present application, the first network-side device selects a target subtask function that satisfies the subtask quality information or the subtask, and the target subtask function is responsible for performing at least one of the perception task, the computing task, and the AI ​​task. Specifically, the target subtask function may include a target perception task function for performing the perception task, a target computing task function for performing the computing task, and a target AI task function for performing the AI ​​task.

[0265] Optionally, if the subtasks associated with the target task include a perception task, the first network-side device may send a fourth message associated with the perception task to the target perception task function to configure the target perception task function with information required for the perception task, and then receive a fourth response message sent by the target perception task function, which may be an acceptance or rejection message. If the fourth response message is a rejection message, the first network-side device may reselect a target perception task function that can perform the perception task.

[0266] Optionally, if the subtasks associated with the target task include computing tasks, the first network-side device may send a fourth message associated with the computing task to the target computing task function to configure the target computing task function with the information required for the computing task, and then receive a fourth response message sent by the target computing function, which may be an acceptance or rejection message. If the fourth response message is a rejection message, the first network-side device may reselect a target computing task function that can perform the computing task. Optionally, the fourth response message may also include computing power information of the computing function, such as computing power size and computing power type.

[0267] Optionally, if the subtasks associated with the target task include AI tasks, the first network-side device may send a fourth message associated with the AI ​​task to the target AI task function to configure the target AI task function with the information required for the AI ​​task, and then receive a fourth response message sent by the target AI function, which may be an acceptance or rejection message. If the fourth response message is a rejection message, the first network-side device may reselect a target AI task function that can perform the AI ​​task. Optionally, the fourth response message may also include at least one of a model acquisition address and a model training address.

[0268] For better understanding of this application, the following takes the first network side device as TM and the second network side device as AF as an example, and provides detailed explanation through some examples.

[0269] Example 1: TM performs task translation and determines subtask management functions. Referring to Figure 3, the process includes the following:

[0270] Step 301: The AF sends a second message to the TM to request the 3rd Generation Partnership Project (3GPP) network to formulate a task template that meets task requirements for the target task.

[0271] Optionally, the second message may be a task template negotiation request message or a task template generation request message. The second message may be sent to the TM via the NEF or directly by the AF.

[0272] In step 302, the TM generates or formulates a task template for the target task based on at least one of the following:

[0273] the second message;

[0274] local configuration of the first network-side device;

[0275] a task template associated with the target task and stored by the first network-side device;

[0276] a task template associated with the target task stored in a third network-side device;

[0277] The intelligent function in the first network-side device is used to generate a task template according to the requirement information corresponding to the target task.

[0278] Optionally, the task template generated through negotiation is a description of a customized task given by the network to the UE. It can be understood as a questionnaire, where the requester "checks" some required or optional parameter requirements in the questionnaire to express their requirements for the task.

[0279] Step 303: The TM sends a second response message to the AF to indicate that a task template that meets the task requirements is prepared for the target task.

[0280] It should be understood that steps 301 to 303 are the negotiation process for the task template. In this application, the task template is customized. Customization refers to the task provider and the operator signing a task level agreement, and there is a task template for each task or each type of task in the agreement. Therefore, steps 301 to 303 are optional.

[0281] Step 304: The terminal obtains a task template, which may include any of the following:

[0282] 304a. The UE obtains the task template from the TM. Specifically, the task template may be obtained in at least one of the following ways:

[0283] Through the registration process, specifically, the TM includes the task template in a registration accept message, in which case the TM is co-located with the AMF. Optionally, the UE includes a first capability in the registration request, the first capability being used to indicate that the UE supports at least one of establishing tasks, task modes, or tasks.

[0284] Through the connection between the UE and the TM, specifically, the UE obtains the TM address information (which can be obtained from the registration or PDU session establishment / modification process), establishes a connection with the TM (which can be a user plane connection or a control plane connection), and obtains the task template through the connection.

[0285] 304b. The UE obtains the task template from the AF. Specifically, the UE may obtain the task template from the AF through the application layer. How to obtain the task template is not within the scope of 3GPP.

[0286] Step 305: The terminal fills in the task template, including at least one of the following:

[0287] The terminal sets the task description information in the task template as the task type of the target task; the task type of the target task may be a task type received from an upper layer or a task type generated by the terminal;

[0288] The terminal sets the task QoE in the task template as the QoE of the target task; the QoE of the target task may be the QoE received from the upper layer or the QoE generated by the terminal;

[0289] The terminal sets the task policy in the task template as a target task policy; the target task policy may be a task policy received from an upper layer, a task policy received from a network, a task policy pre-configured in the terminal or a task policy generated by the terminal; optionally, the target task policy may be understood or replaced by the task policy of the target task;

[0290] The terminal sets the task quality information in the task template as the target task quality information; the target task quality information can be the task quality information received from the upper layer, the task quality information received from the network, the task quality information pre-configured in the terminal or generated by the terminal; optionally, the target task quality information can be understood or replaced by the task quality information of the target task.

[0291] The terminal sets the task parameters in the task template as the task parameters of the target task, and the task parameters include configuration information of the perception subtask, configuration information of the computing subtask, configuration information of the artificial intelligence AI subtask, data subtask information, positioning subtask information, and at least one of the Internet Protocol Multimedia System IMS subtask; the task parameters of the target task can be task parameters received from an upper layer, a target task strategy received from a network, or task parameters pre-configured in the terminal or generated by the terminal.

[0292] Optionally, the terminal may fill in part or all of the contents of the task template, depending on the terminal implementation.

[0293] Step 306: The terminal sends a first message to the TM, where the first message is used to request allocation of network resources for the target task.

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

[0295] It should be noted that the first message can be forwarded to the TM by the target network element, and the target network element is at least one of the following: AMF, SMF, and control network element (the control network element has at least one of the following functions: mobility management function, connection management function, and session management function). If the TM and SMF are co-located, the second message is a PDU session establishment request message.

[0296] Step 307: The TM performs a target operation, which includes at least one of the following:

[0297] Verify whether the target task is an authorized or permitted task;

[0298] Determine a task instance of the target task;

[0299] assigning at least one of a target task identifier and a target task session identifier;

[0300] Allocate at least one of a target task slice and a target task DNN;

[0301] Select the target subtask management function that meets the subtask quality information or subtask strategy.

[0302] Step 308: The TM sends a third message to the target subtask management function, where the third message is used to request to establish the subtask, wherein the target subtask management function is a subtask management function used to perform subtask management.

[0303] Step 309: The first network-side device receives a third response message from the target subtask management function, where the third response message is used to indicate the establishment result of the subtask.

[0304] In this embodiment, the TM interacts with the identified target subtask management function based on the third message and the third response message to determine the node information for subtask execution. The target subtask management function selects a target subtask function that meets the task requirements based on the subtask strategy and subtask quality information. The target subtask function is used to execute the corresponding subtask. The target subtask management function may include at least one of a target perception management function, a target calculation management function, and a target AI management function.

[0305] Optionally, if the TM determines the order in which the subtask bearers are established, the TM may interact with the corresponding task management functions in that order. For example, if the task includes a perception task and a computation task, and the TM determines to establish the perception task bearer first, followed by the computation task bearer, the TM may first interact with the target perception management function to establish the perception task bearer, and then interact with the target computation management function to establish the computation task bearer.

[0306] Step 310: The TM creates a task context based on the received subtask function information (ie, the content included in the fourth response message) to record the relationship between the task requirement and the task instance.

[0307] Optionally, when receiving a similar task requirement, the TM may determine a task instance that can be used for the task based on the stored task context.

[0308] Optionally, the TM associates at least one of the target task identifier and the target task session identifier with at least one of the subtask identifier and the subtask session identifier.

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

[0310] Step 311: The TM sends a first response message to the UE to indicate the result of the task request.

[0311] Optionally, when the first response message is a rejection message, it may also carry at least one of the rejection reason and the rejection message, wherein the rejection reason may include but is not limited to at least one of the following: the number of task requests exceeds the maximum value, the task request is not allowed, and the terminal is illegal.

[0312] Example 2: TM performs task translation and determines subtask functions.

[0313] The difference between the second embodiment of the present application and the first embodiment is that the second embodiment does not have a subtask management function, and the TM performs the operation of the subtask management function, that is, the TM directly determines the subtask function. The specific process is shown in Figure 4:

[0314] Steps 401 to 406 are the same as steps 301 to 306.

[0315] Step 407: The TM performs a target operation, which includes at least one of the following:

[0316] Verify whether the target task is an authorized or permitted task;

[0317] Determine a task instance of the target task;

[0318] assigning at least one of a target task identifier and a target task session identifier;

[0319] Allocate at least one of a target task slice and a target task DNN;

[0320] Select target subtask functions that satisfy subtask quality information or subtask policies.

[0321] Step 408: The TM sends a fourth message to the target subtask function, where the fourth message is used to indicate information required by the target subtask function to execute the subtask.

[0322] Step 409: The TM receives a fourth response message from the target subtask function. The fourth response message is used to indicate whether the target subtask function accepts or refuses to execute the subtask.

[0323] In this embodiment, the TM exchanges information with the determined target subtask function based on the third message and the third response message, and assigns the responded subtask function to the subtask to execute the subtask associated with the target task. Specifically, the TM may query the NRF, UDM, or UDR to determine the appropriate subtask function, or the TM may determine the appropriate subtask function based on stored or maintained subtask capabilities. The subtask function may include a terminal device, an access network device, or an independently deployed execution unit.

[0324] Steps 410 to 411 are the same as steps 310 to 311 .

[0325] Example 3: AF performs task translation, UE obtains task instance from AF and initiates task request, and network selects subtask function as needed. The specific process is as follows:

[0326] Step 51: AF performs task translation or decomposition to determine the task instance.

[0327] In step 52, the UE and the AF interact through the application layer, and the UE obtains the task instance.

[0328] Optionally, the AF may send a target task policy or target task quality information update request to the TM to request the network to update resources reserved for the target task. The update request includes at least one of the following: AF ID, target task quality information, and target task quality information priority.

[0329] Step 53: The terminal sends a first message to the TM, where the first message is used to request allocation of network resources for the target task.

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

[0331] Target task description information;

[0332] Target task DNN;

[0333] Single network slice selection auxiliary information S-NSSAI associated with the target task;

[0334] Target mission strategy;

[0335] Target task quality information;

[0336] Instruction information for indicating the execution order of subtasks;

[0337] Target task identification;

[0338] Target task session ID.

[0339] Step 54: The TM receives the first message and performs a target operation, including at least one of the following:

[0340] Verify whether the target task is an authorized or permitted task;

[0341] Determine a task instance of the target task;

[0342] assigning at least one of a target task identifier and a target task session identifier;

[0343] Allocate at least one of a target task slice and a target task DNN;

[0344] Select a target subtask management function that satisfies subtask quality information or subtask policies, or select a target subtask function that satisfies subtask quality information or subtask policies.

[0345] Steps 55 to 58 are the same as steps 308 to 311 , or the same as steps 408 to 411 .

[0346] Embodiment 4: TM performs task translation and dynamically determines subtask information to AF.

[0347] In this application, the terminal has only signed up for a single service, such as communication service, but the task requested by the terminal includes two sub-tasks: communication and computing. When the TM receives such a task request, the TM needs to dynamically request the computing task requirement information from the AF.

[0348] The difference between this embodiment and the above-mentioned embodiments 1, 2 and 3 is that:

[0349] 1. Since the terminal has only a single task contract, the task template obtained by the terminal only has information of a single task, and the terminal can only fill in the task template of the single task.

[0350] 2. When performing task translation or decomposition, the TM determines that the task type is a combined task. However, the UE's contract determines that the UE is only sub-task-subscribed. Therefore, the TM cannot determine whether the task requirement provided by the UE is a communication sub-task requirement or a complete task requirement. In this case, the TM determines the sub-task information (including at least one of the sub-task strategy and sub-task quality information) based on at least one of the following:

[0351] Obtained from AF;

[0352] Obtained from the local configuration.

[0353] Optionally, the TM requests the AF for requirement information corresponding to the subtask, including at least one of the following: target task description information; target task quality of experience (QoE); target task identifier; target task session identifier; subtask identifier; subtask session identifier; and subtask type.

[0354] Optionally, the TM may determine the AF through an AF identifier obtained in a previous task negotiation process.

[0355] 5 , an embodiment of the present application further provides a transmission processing method. As shown in FIG5 , the transmission processing method includes:

[0356] Step 501: The terminal sends a first message to a first network-side device, where the first message is used to establish a target task.

[0357] Step 502: The terminal receives a first response message from the first network-side device, where the first response message indicates a request result of the target task.

[0358] Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; target task quality of experience QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; task identifier; target task session identifier.

[0359] Optionally, the first response message satisfies at least one of the following:

[0360] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task DNN, and information of a subtask, where the subtask is associated with the target task;

[0361] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

[0362] Optionally, the subtask information includes at least one of the following: subtask identification, subtask session identification, identification information of subtask management function, subtask strategy, subtask quality information, indication information for indicating the subtask execution order, subtask slice and subtask DNN.

[0363] Optionally, before the terminal sends the first message to the first network-side device, the method further includes:

[0364] The terminal obtains the first information;

[0365] The terminal sets at least part of the content of the first information.

[0366] Optionally, the terminal acquiring the first information includes any one of the following:

[0367] The terminal obtains first information from the first network side device in a target manner, wherein the target manner includes performing at least one of the following: a registration process; a connection between the terminal and the first network side device;

[0368] The terminal obtains first information from the second network side device.

[0369] Optionally, the terminal sets at least part of the first information to include at least one of the following:

[0370] The terminal sets the task description information in the first information as the task type of the target task;

[0371] The terminal sets the task QoE in the first information as the QoE of the target task;

[0372] The terminal sets the task strategy in the first information as the target task strategy;

[0373] The terminal sets the task quality information in the first information as target task quality information;

[0374] The terminal sets the task parameters in the first information as the task parameters of the target task, where the task parameters include configuration information of the perception subtask, configuration information of the computing subtask, configuration information of the artificial intelligence AI subtask, data subtask information, positioning subtask information, and at least one of the Internet Protocol Multimedia System IMS subtask.

[0375] In the embodiment of the present application, the configuration information of the above-mentioned perception subtask, the configuration information of the calculation subtask, and the configuration information of the artificial intelligence AI subtask can be understood as the preference information of the terminal.

[0376] Optionally, the method further includes:

[0377] The terminal receives a task instance from a second network-side device, where the task instance is used to indicate parameter information allocated by the network to the target task.

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

[0379] 6 , an embodiment of the present application further provides a transmission processing device 600. As shown in FIG6 , the transmission processing device 600 includes:

[0380] A first receiving module 601 is configured to receive a first message from a terminal, where the first message is used to establish a target task;

[0381] A first sending module 602 is configured to send a first response message to the terminal based on the first message, where the first response message is used to indicate the request result of the target task;

[0382] The first response message satisfies at least one of the following conditions:

[0383] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name DNN, and information about a subtask, where the subtask is associated with the target task;

[0384] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

[0385] Optionally, the subtask information includes at least one of the following: subtask identification, subtask session identification, identification information of subtask management function, subtask strategy, subtask quality information, indication information for indicating the subtask execution order, subtask slicing information and subtask DNN.

[0386] Optionally, the first message includes at least one of the following:

[0387] First information of the request, where the first information is used to indicate requirement information corresponding to the target task;

[0388] Target task description information;

[0389] Target task quality of experience (QoE);

[0390] Target task DNN;

[0391] Single network slice selection auxiliary information S-NSSAI associated with the target task;

[0392] Target mission strategy;

[0393] Target task quality information;

[0394] Target task identification;

[0395] Target task session ID.

[0396] Optionally, the transmission processing device 600 further includes a generation module, wherein:

[0397] The first receiving module 601 is further configured to receive a second message from a second network-side device, where the second message is configured to request generation of first information that meets task requirements for a target task;

[0398] The generating module is used to generate first information for the target task.

[0399] Optionally, the second message includes at least one of the following:

[0400] Target identification information, the target identification information is used to indicate the application server corresponding to the task provider;

[0401] Task description information;

[0402] identification information of the first information;

[0403] Task DNN;

[0404] Task-related S-NSSAI;

[0405] a time window of the expected first information, where the time window of the first information is used to indicate a time when the first information is applicable;

[0406] an applicable area of ​​the desired first information, where the applicable area of ​​the first information is used to indicate a geographical area or network to which the first information is applicable;

[0407] Subscribe to notifications of changes to the first information, for instructing the second network side device to be notified when the first information is updated;

[0408] Task quality information.

[0409] Optionally, the generating module is specifically configured to generate the first information for the target task based on at least one of the following:

[0410] the second message;

[0411] local configuration of the first network-side device;

[0412] first information associated with the target task stored by the first network-side device;

[0413] first information associated with the target task stored in the third network-side device;

[0414] The intelligent function in the first network side device is used to generate first information according to the requirement information corresponding to the target task.

[0415] Optionally, the first sending module 602 is further used to: send a second response message to the second network-side device, where the second response message is used to indicate the request result of the first information of the target task.

[0416] Optionally, the first sending module 602 is further configured to send first information of the target task to a terminal.

[0417] Optionally, the transmission processing device 600 further includes:

[0418] Execution module, used to execute target operations;

[0419] A generating module, configured to generate the first response message based on the execution result of the target operation;

[0420] The target operation includes at least one of the following:

[0421] Verify whether the target task is an authorized or permitted task;

[0422] Determine a task instance of the target task;

[0423] assigning at least one of a target task identifier and a target task session identifier;

[0424] Allocate at least one of a target task slice and a target task DNN;

[0425] Select a target subtask management function that satisfies the subtask quality information or subtask policy, or select a target subtask function that satisfies the subtask quality information or subtask policy.

[0426] Optionally, determining the task instance of the target task includes at least one of the following:

[0427] In a case where the first message includes first requested information, mapping the first requested information into a task instance;

[0428] In a case where the first message does not include the requested first information, generating a task instance of the target task according to the second information;

[0429] The second information includes at least one of the following:

[0430] information carried by the first message;

[0431] a local configuration of the first network-side device, the local configuration comprising at least one of subtask quality information and a subtask strategy;

[0432] first information associated with the target task stored by the first network-side device;

[0433] first information associated with the target task stored in the third network-side device;

[0434] The intelligent function in the first network side device.

[0435] In the case where the task contracted by the terminal is a single task, the first receiving module 601 is further configured to send a target request message to the second network-side device, wherein the target request message is configured to request obtaining subtask information of subtasks associated with the target task;

[0436] The first receiving module 601 is further configured to receive the subtask information from the second network side device;

[0437] The subtask information includes at least one of subtask strategy and subtask quality information.

[0438] Optionally, the first receiving module 601 is further configured to send a third message to the target subtask management function, where the third message is used to request to establish the subtask;

[0439] The first receiving module 601 is further configured to receive a third response message from the target subtask management function, where the third response message is used to indicate a result of establishing the subtask;

[0440] The target subtask management function is a subtask management function for executing the subtask management.

[0441] Optionally, the first receiving module 601 is further configured to send a fourth message to the target subtask function, where the fourth message is used to indicate information required for the target subtask function to execute the subtask;

[0442] The first receiving module 601 is further configured to receive a fourth response message from the target subtask function, where the fourth response message is used to indicate whether the target subtask function accepts or refuses to execute the subtask.

[0443] 7 , an embodiment of the present application further provides a transmission processing device 700. As shown in FIG7 , the transmission processing device 700 includes:

[0444] The second sending module 701 is configured to send a first message to the first network-side device, where the first message is used to establish a target task;

[0445] A second receiving module 702 is configured to receive a first response message from the first network-side device, where the first response message is used to indicate a request result of the target task;

[0446] Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; target task quality of experience QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; target task identifier; target task session identifier.

[0447] Optionally, the first response message satisfies at least one of the following:

[0448] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task DNN, and information of a subtask, where the subtask is associated with the target task;

[0449] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

[0450] Optionally, the subtask information includes at least one of the following: subtask identification, subtask session identification, identification information of subtask management function, subtask strategy, subtask quality information, indication information for indicating the subtask execution order, subtask slice and subtask DNN.

[0451] Optionally, the transmission processing device 700 further includes a setting module, wherein:

[0452] The second receiving module 702 is further configured to obtain the first information;

[0453] The setting module is used to set at least part of the content of the first information.

[0454] Optionally, the second receiving module 702 is specifically configured to perform any one of the following:

[0455] Acquiring first information from the first network side device in a target manner, the target manner comprising performing at least one of the following: a registration process; a connection between the terminal and the first network side device;

[0456] Acquire first information from the second network-side device.

[0457] Optionally, the setting module is specifically configured to perform at least one of the following:

[0458] Setting the task description information in the first information as the task type of the target task;

[0459] Setting the task QoE in the first information as the target task QoE;

[0460] Setting the task strategy in the first information as the target task strategy;

[0461] Setting the task quality information in the first information as target task quality information;

[0462] The task parameters in the first information are set as the task parameters of the target task, and the task parameters include configuration information of the perception subtask, configuration information of the computing subtask, configuration information of the artificial intelligence AI subtask, data subtask information, positioning subtask information, and at least one of the Internet Protocol Multimedia System IMS subtask.

[0463] Optionally, the second receiving module 702 is further configured to receive a task instance from a second network-side device, where the task instance is used to indicate parameter information allocated by the network to the target task.

[0464] Optionally, the second receiving module 702 is further configured to receive a task instance from a second network-side device, where the task instance is used to indicate parameter information allocated by the network to the target task.

[0465] In an embodiment of the present application, the above-mentioned parameter information may include at least one of the following: target task description information, task type, target task strategy, task requirement information, safety-related parameters, subtask type, subtask strategy, subtask requirement information and the timing relationship of subtasks.

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

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

[0468] As shown in Figure 8, an embodiment of the present application also provides a communication device 800, including a processor 801 and a memory 802, and the memory 802 stores a program or instruction that can be run on the processor 801. When the program or instruction is executed by the processor 801, the various steps of the above-mentioned transmission processing method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0469] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG5 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG9 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

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

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

[0472] It should be understood that in an embodiment of the present application, the input unit 904 may include a graphics processing unit (GPU) 9041 and a microphone 9042, and the graphics processor 9041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 906 may include a display panel 9061, and the display panel 9061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 907 includes a touch panel 9071 and at least one of other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include two parts: a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

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

[0474] The memory 909 can be used to store software programs or instructions and various data. The memory 909 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 909 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 909 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0475] Processor 910 may include one or more processing units. Optionally, processor 910 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 910.

[0476] The radio frequency unit 901 is configured to receive a first message from a terminal, the first message being used to establish a target task; and send a first response message to the terminal based on the first message, the first response message being used to indicate a request result of the target task;

[0477] The first response message satisfies at least one of the following conditions:

[0478] When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name DNN, and information about a subtask, where the subtask is associated with the target task;

[0479] In the case that the first network-side device rejects the target task, the first response message is a rejection message.

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

[0481] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG2 . This network-side device embodiment corresponds to the first network-side device method embodiment described above, and each implementation process and implementation method of the above method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0482] Specifically, an embodiment of the present application also provides a network-side device. As shown in Figure 10, the network-side device 1000 includes: an antenna 1001, a radio frequency device 1002, a baseband device 1003, a processor 1004, and a memory 1005. Antenna 1001 is connected to radio frequency device 1002. In the uplink direction, radio frequency device 1002 receives information via antenna 1001 and sends the received information to baseband device 1003 for processing. In the downlink direction, baseband device 1003 processes the information to be transmitted and sends it to radio frequency device 1002. Radio frequency device 1002 processes the received information and sends it through antenna 1001.

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

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

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

[0486] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 1005 and executable on the processor 1004. The processor 1004 calls the instructions or programs in the memory 1005 to execute the method of execution of each module shown in Figure 7 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0487] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG11 , the network-side device 1100 includes a processor 1101, a network interface 1102, and a memory 1103. The network interface 1102 is, for example, a common public radio interface (CPRI).

[0488] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 1103 and executable on the processor 1101. The processor 1101 calls the instructions or programs in the memory 1103 to execute the method of execution of each module shown in Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0489] 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 transmission processing method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0491] 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 transmission processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0493] An embodiment of the present application further provides a computer program / program product, which includes computer instructions. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned transmission processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0494] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the transmission processing method of the terminal side as described above, and the network side device can be used to execute the steps of the transmission processing method of the first network side device as described above.

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

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

[0497] 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 transmission processing method, comprising: The first network-side device receives a first message from the terminal, where the first message is used to establish a target task; The first network-side device sends a first response message to the terminal based on the first message, where the first response message is used to indicate the request result of the target task; The first response message satisfies at least one of the following conditions: When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task data network name DNN, and subtask information, where the subtask is associated with the target task; In the case that the first network-side device rejects the target task, the first response message is a rejection message.

2. The method according to claim 1, wherein The subtask information includes at least one of the following: subtask identification, subtask session identification, identification information of subtask management function, subtask strategy, subtask quality information, indication information for indicating the subtask execution order, subtask slicing information and subtask DNN.

3. The method according to claim 1 or 2, wherein The first message includes at least one of the following: First information of the request, where the first information is used to indicate requirement information corresponding to the target task; Target task description information; Target task quality of experience (QoE); Target task DNN; Single network slice selection auxiliary information S-NSSAI associated with the target task; Target mission strategy; Target task quality information; Target task identification; Target task session ID.

4. The method according to claim 1, wherein Before the first network-side device receives the first message from the terminal, the method further includes: The first network-side device receives a second message from the second network-side device, where the second message is used to request generation of first information that meets task requirements for a target task; The first network-side device generates first information for the target task.

5. The method according to claim 4, wherein The second message includes at least one of the following: Target identification information, the target identification information is used to indicate the application server corresponding to the task provider; Task description information; identification information of the first information; Task DNN; Task-related S-NSSAI; a time window of the expected first information, where the time window of the first information is used to indicate a time when the first information is applicable; an applicable area of ​​the desired first information, where the applicable area of ​​the first information is used to indicate a geographical area or network to which the first information is applicable; Subscribe to notifications of changes to the first information, for instructing the second network side device to be notified when the first information is updated; Task quality information.

6. The method according to claim 4, wherein: The first network-side device generating first information for the target task includes: The first network-side device generates first information for the target task based on at least one of the following: the second message; local configuration of the first network-side device; first information associated with the target task stored by the first network-side device; first information associated with the target task stored in the third network-side device; The intelligent function in the first network side device is used to generate first information according to the requirement information corresponding to the target task.

7. The method according to claim 4, further comprising: The first network-side device sends a second response message to the second network-side device, where the second response message is used to indicate a request result for the first information of the target task.

8. The method according to claim 4, further comprising: The first network-side device sends first information of the target task to the terminal.

9. The method according to any one of claims 1 to 8, further comprising: The first network-side device performs a target operation; The first network-side device generates the first response message based on the execution result of the target operation; The target operation includes at least one of the following: Verify whether the target task is an authorized or permitted task; Determine a task instance of the target task; assigning at least one of a target task identifier and a target task session identifier; Allocate at least one of a target task slice and a target task DNN; Select a target subtask management function that satisfies the subtask quality information or subtask policy, or select a target subtask function that satisfies the subtask quality information or subtask policy.

10. The method according to claim 9, wherein: The task instance of determining the target task includes at least one of the following: In a case where the first message includes first requested information, mapping the first requested information into a task instance; In a case where the first message does not include the requested first information, generating a task instance of the target task according to the second information; The second information includes at least one of the following: information carried by the first message; a local configuration of the first network-side device, the local configuration comprising at least one of subtask quality information and a subtask strategy; first information associated with the target task stored by the first network-side device; first information associated with the target task stored in the third network-side device; The intelligent function in the first network side device.

11. The method according to claim 10, wherein: In the case where the task signed by the terminal is a single task, the method further includes: The first network side device sends a target request message to the second network side device, where the target request message is used to request to obtain subtask information of the subtask associated with the target task; The first network side device receives the subtask information from the second network side device; The subtask information includes at least one of subtask strategy and subtask quality information.

12. The method according to claim 9, wherein After determining the task instance of the target task, the method further includes: The first network side device sends a third message to the target subtask management function, where the third message is used to request to establish the subtask; The first network-side device receives a third response message from the target subtask management function, where the third response message is used to indicate an establishment result of the subtask; The target subtask management function is a subtask management function for executing the subtask management.

13. The method according to claim 9, wherein: After selecting the subtask function that satisfies the subtask quality information or the target subtask function, the method further includes: The first network-side device sends a fourth message to the target subtask function, where the fourth message is used to indicate information required for the target subtask function to execute the subtask; The first network-side device receives a fourth response message from the target subtask function, where the fourth response message is used to indicate to the target subtask function whether to accept or refuse to execute the subtask.

14. A transmission processing method, comprising: The terminal sends a first message to the first network side device, where the first message is used to establish a target task; The terminal receives a first response message from the first network-side device, where the first response message is used to indicate a request result of the target task; Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; target task quality of experience QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; target task identifier; target task session identifier.

15. The method according to claim 14, wherein The first response message satisfies at least one of the following: When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a target task DNN, and information of a subtask, where the subtask is associated with the target task; In the case that the first network-side device rejects the target task, the first response message is a rejection message.

16. The method according to claim 15, wherein The subtask information includes at least one of the following: subtask identification, subtask session identification, identification information of subtask management function, subtask strategy, subtask quality information, indication information for indicating the subtask execution order, subtask slice and subtask DNN.

17. The method according to any one of claims 14 to 16, wherein: Before the terminal sends the first message to the first network side device, the method further includes: The terminal obtains the first information; The terminal sets at least part of the content of the first information.

18. The method according to claim 17, wherein The terminal acquiring the first information includes any one of the following: The terminal obtains first information from the first network side device in a target manner, wherein the target manner includes performing at least one of the following: a registration process; a connection between the terminal and the first network side device; The terminal obtains first information from the second network side device.

19. The method according to claim 17, wherein The terminal sets at least part of the first information to include at least one of the following: The terminal sets the task description information in the first information as the task type of the target task; The terminal sets the task QoE in the first information as the target task QoE; The terminal sets the task strategy in the first information as the target task strategy; The terminal sets the task quality information in the first information as target task quality information; The terminal sets the task parameters in the first information as the task parameters of the target task, where the task parameters include configuration information of the perception subtask, configuration information of the computing subtask, configuration information of the artificial intelligence AI subtask, data subtask information, positioning subtask information, and at least one of the Internet Protocol Multimedia System IMS subtask.

20. The method according to any one of claims 14 to 16, further comprising: The terminal receives a task instance from a second network-side device, where the task instance is used to indicate parameter information allocated by the network to the target task.

21. A transmission processing device, comprising: A first receiving module is used to receive a first message from a terminal, where the first message is used to establish a target task; A first sending module, configured to send a first response message to the terminal based on the first message, wherein the first response message is used to indicate the request result of the target task; The first response message satisfies at least one of the following conditions: When the first network-side device accepts the target task, the first response message includes at least one of the following: a target task identifier, a target task session identifier, a target task policy, target task quality information, a target task slice, a data network name DNN, and information about a subtask, where the subtask is associated with the target task; In the case that the first network-side device rejects the target task, the first response message is a rejection message.

22. The apparatus according to claim 21, further comprising a generating module, wherein: The first receiving module is further configured to receive a second message from a second network-side device, wherein the second message is configured to request generation of first information that meets task requirements for a target task; The generating module is used to generate first information for the target task.

23. The device according to claim 22, wherein The first sending module is further used to send a second response message to the second network-side device, where the second response message is used to indicate a request result for the first information of the target task.

24. The apparatus according to claim 22, wherein The first sending module is further used to send the first information of the target task to the terminal.

25. The apparatus according to any one of claims 21 to 24, further comprising: Execution module, used to execute target operations; A generating module, configured to generate the first response message based on the execution result of the target operation; The target operation includes at least one of the following: Verify whether the target task is an authorized or permitted task; Determine a task instance of the target task; assigning at least one of a target task identifier and a target task session identifier; Allocate at least one of a target task slice and a target task DNN; Select a target subtask management function that satisfies the subtask quality information or subtask policy, or select a target subtask function that satisfies the subtask quality information or subtask policy.

26. A transmission processing device, comprising: A second sending module is used to send a first message to the first network side device, where the first message is used to establish a target task; A second receiving module is configured to receive a first response message from the first network-side device, where the first response message is used to indicate a request result of the target task; Among them, the first message includes at least one of the following: the first information set, the first information is used to indicate the demand information corresponding to the target task; target task description information; target task quality of experience QoE; target task data network name DNN; single network slice selection auxiliary information S-NSSAI associated with the target task; target task strategy; target task quality information; target task identifier; target task session identifier.

27. The apparatus according to claim 26, further comprising a setting module, wherein: The second receiving module is further configured to obtain the first information; The setting module is used to set at least part of the content of the first information.

28. The apparatus according to claim 27, wherein The setting module is specifically configured to perform at least one of the following: Setting the task description information in the first information as the task type of the target task; Setting the task QoE in the first information as the target task QoE; Setting the task strategy in the first information as the target task strategy; Setting the task quality information in the first information as target task quality information; The task parameters in the first information are set as the task parameters of the target task, and the task parameters include configuration information of the perception subtask, configuration information of the computing subtask, configuration information of the artificial intelligence AI subtask, data subtask information, positioning subtask information, and at least one of the Internet Protocol Multimedia System IMS subtask.

29. The apparatus according to claim 26, wherein The second receiving module is further configured to receive a task instance from a second network-side device, where the task instance is configured to indicate parameter information allocated by the network to the target task.

30. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the transmission processing method according to any one of claims 14 to 20 are implemented.

31. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the transmission processing method according to any one of claims 1 to 13 are implemented.

32. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the transmission processing method according to any one of claims 1 to 20.

33. A computer program product comprising computer instructions, wherein when the computer instructions are executed by a processor, the steps of the transmission processing method according to any one of claims 1 to 20 are implemented.

Images