Task processing method and device

Abstract

The invention discloses a task processing method and device, belongs to the technical field of communication, and aims to support a terminal device to perform task processing in an inactive state, reduce time delay, signaling overhead and energy consumption when the terminal device performs task processing, enable the device in the inactive state to still participate in task processing, and assist in implementation of an everything-intellectual property scene. The method comprises the steps that a first communication device receives a task, and the task is a non-session task; the first communication device obtains first task data obtained by executing the task; and when the sending of the first task data meets a first condition, the first communication device sends the first task data to the second communication device based on a small-amount data transmission mechanism. Wherein the first communication device is terminal equipment, the second communication device is network equipment, or the first communication device is network equipment, the second communication device is terminal equipment, and the terminal equipment is in an inactive state.

Description

Task processing method and device Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a task processing method and device. Background Art

[0002] In the new radio (NR), terminal devices have three different radio resource control (RRC) states: idle, inactive, and connected. In the future-oriented intelligent inclusive scenario, the network's cloud (such as the central node of cloud computing), edge (such as the edge device of cloud computing), and end (such as terminal devices, etc.) need to work together to perform task processing. However, existing task processing generally requires the terminal device to be in a connected state. Therefore, for terminal devices in an inactive state, it is necessary to switch to a connected state to complete task processing. Frequent state switching will bring about problems such as longer delays, higher signaling overhead, and higher energy consumption. Therefore, how to reduce the delay, signaling overhead, and energy consumption of terminal devices when performing task processing is a problem that needs to be considered.

[0003] Summary of the Invention

[0004] The present application provides a task processing method and apparatus to support terminal devices in performing task processing in an inactive state, thereby reducing the time delay, signaling overhead, and energy consumption of the terminal devices during task processing.

[0005] In a first aspect, an embodiment of the present application provides a task processing method, the method comprising: a first communication device receives a task, wherein the task is a non-conversational task, and the first communication device or the second communication device participating in the task is in an inactive state; the first communication device obtains first task data obtained by executing the task; when the sending of the first task data meets a first condition, the first communication device sends the first task data to the second communication device based on a small amount of data transmission mechanism.

[0006] In the above-mentioned task processing method, the first communication device can be a terminal device, a component of a terminal device (such as a processor, chip, or chip system, etc.), or a device used in conjunction with the terminal device; the second communication device can be a network device, a component of a network device (such as a processor, chip, or chip system, etc.), or a device used in conjunction with the network device; or, the first communication device can be a network device, a component of a network device (such as a processor, chip, or chip system, etc.), or a device used in conjunction with the network device, and the second communication device can be a terminal device, a component of a terminal device (such as a processor, chip, or chip system, etc.), or a device used in conjunction with the terminal device, etc. The communication device corresponding to the terminal device, the component of the terminal device (such as a processor, chip, or chip system, etc.), or the device used in conjunction with the terminal device is in an inactive state.

[0007] Through the above method, terminal devices in an inactive state are enabled to complete tasks based on a small amount of data transmission mechanism. Compared with the situation where the terminal device needs to switch to a connected state to process tasks, the number of times the terminal device switches between the inactive state and the connected state can be effectively reduced, thereby reducing the delay, signaling overhead, and energy consumption of the terminal device when processing tasks.

[0008] In one possible design, the sending of the first task data satisfies a first condition, including: the data volume of the first task data is less than or equal to a first threshold value.

[0009] It can be understood that when the first communication device receives multiple tasks and the first communication device performs multiple tasks to obtain multiple first task data, if the first communication device sends the multiple first task data together based on a small amount of data transmission mechanism, the total data volume of the multiple first task data should be less than or equal to the first threshold value; if the first communication device sends the multiple first task data separately based on a small amount of data transmission mechanism, the data volume of each first task in the multiple first task data should be less than or equal to the first threshold value.

[0010] Through the above design, it can be ensured that the task data sent based on the small amount of data transmission mechanism meets the transmission data volume threshold of the small amount of data transmission mechanism, thereby ensuring the reliability of task data transmission.

[0011] In one possible design, the first threshold value includes a token number threshold value and / or an embedding vector dimension threshold value, and the data volume of the first task data is less than or equal to the first threshold value, including: the number of tokens corresponding to the first task data is less than or equal to the token number threshold value; or, the embedding vector dimension corresponding to the first task data is less than or equal to the embedding dimension threshold value.

[0012] In AI-related tasks such as AI training and AI reasoning, the data that needs to be transmitted over the air interface between the terminal device and the network device is a token or embedding vector. Among them, embedding in AI refers to the process of mapping high-dimensional data (such as text, pictures, audio) to a low-dimensional space. An embedding vector is usually a vector composed of real numbers. It represents the input data as a point in a continuous numerical space and can be used to represent almost anything, such as text, pictures, audio, etc. A token can be called an identifier, a tag, etc. In AI, a token usually refers to the smallest unit in the text processing process. A token can be a word, a phrase, a sentence, or other smaller text units. One or more tokens can be included in an embedding vector. Through the above design, it supports setting the transmission data volume threshold of the small-scale data transmission mechanism according to the transmission unit of the specific task, which is conducive to quickly judging whether the transmission of task data meets the conditions for transmission based on the small-scale data transmission mechanism, thereby improving task processing efficiency.

[0013] In one possible design, the sending of the first task data satisfies the first condition and further includes: the channel quality between the first communication device and the second communication device is greater than or equal to the channel quality threshold value of the small amount of data transmission mechanism.

[0014] Through the above design, the channel quality between the first communication device and the second communication device is further constrained, which is conducive to improving the reliability of the transmission of task data between the first communication device and the second communication device.

[0015] In one possible design, before the first communication device sends the first task data to the second communication device based on the small amount of data transmission mechanism, the method also includes: the first communication device sends a task initiation request to the second communication device based on the small amount of data transmission mechanism, and the task initiation request includes the task identifier of the task; the first communication device receives a task confirmation response sent by the second communication device based on the small amount of data transmission mechanism, and the task confirmation response includes the task identifier of the task.

[0016] Through the above design, the first communication device and the second communication device are supported to request and confirm tasks before sending task data, which is beneficial for the second communication device to know the tasks that need to transmit task data and improve the reliability of task data transmission between the first communication device and the second communication device.

[0017] In one possible design, the method further includes: the first communication device sending a task identifier corresponding to the first task data to the second communication device based on a small amount of data transmission mechanism.

[0018] Through the above design, the task identifier corresponding to the task data is notified to the second communication device receiving the task data, which is conducive to the second communication device quickly learning the task to which the task data belongs and processing the task data.

[0019] In one possible design, the first communication device is a terminal device and the second communication device is a network device. The first communication device sends the first task data to the second communication device based on a small amount of data transmission mechanism, including: the first communication device sends the first task data to the second communication device through a random access request in a two-step random access process; or, the first communication device sends the first task data to the second communication device through an RRC recovery request in a four-step random access process; or, the first communication device sends the first task data to the second communication device through an RRC recovery request sent to the second communication device on configured authorized resources.

[0020] Through the above design, terminal devices and network devices in an inactive state are supported to transmit task data using random access (RA), a small amount of data transmission mechanism, a configured grant (CG) small amount of data transmission mechanism, etc., among which the random access small amount of data transmission mechanism can include a two-step random access small amount of data transmission mechanism and a four-step random access small amount of data transmission mechanism.

[0021] In one possible design, the first communication device is a terminal device, the second communication device is a network device, and the first communication device is in an inactive state. The method also includes: when the sending of the first task data does not meet the first condition, the first communication device switches to a connected state; the first communication device sends the first task data to the second communication device based on a non-small amount of data transmission mechanism.

[0022] Through the above design, when the task data does not meet the sending conditions of the small amount of data transmission mechanism, the terminal device switches to the connected state to send the task data, which can improve the reliability of the transmission of the task data between the terminal device and the network device.

[0023] In one possible design, the first communication device is a terminal device, the second communication device is a network device, the first communication device is in an inactive state, the first task data is the Nth round of task data obtained by the first communication device performing the task, and N is an integer greater than or equal to 1. The method also includes: when the sending of the second task data does not meet the first condition, the first communication device switches to a connected state, wherein the second task data is the Kth round of task data obtained by the first communication device performing the task, and K is an integer greater than N; the first communication device sends the second task data to the second communication device based on a non-small amount of data transmission mechanism.

[0024] Through the above design, when a round of task data does not meet the sending conditions of the small amount of data transmission mechanism, the terminal device is supported to switch to the connected state to send the task data, which can improve the reliability of the task data transmission between the terminal device and the network device.

[0025] In one possible design, the first communication device is a network device and the second communication device is a terminal device. The first communication device sends first task data to the second communication device based on a small amount of data transmission mechanism, including: the first communication device sends the first task data to the second communication device through an RRC temporary release indication, wherein the RRC temporary release indication is used to respond to an RRC recovery request sent by the second communication device.

[0026] Through the above design, the network device is supported to send task data to the terminal device in the inactive state, and instruct the terminal device to remain in the inactive state through the RRC temporary release indication. Compared with the situation where the terminal device needs to switch to the connected state to perform task processing, the number of switchings of the terminal device between the inactive state and the connected state can be effectively reduced, thereby reducing the delay, signaling overhead, and energy consumption of the terminal device when performing task processing.

[0027] In one possible design, the first communication device is a network device, the second communication device is a terminal device, and the second communication device is in an inactive state. The method also includes: when the sending of the first task data does not meet the first condition, the first communication device sends a paging message to the second communication device, and the paging message is used to trigger the second communication device to switch to a connected state; after the second communication device switches to the connected state, the first communication device sends the first task data to the second communication device based on a non-small amount of data transmission mechanism.

[0028] Through the above design, when the task data does not meet the sending conditions of the small amount of data transmission mechanism, the network device is supported to instruct the terminal device to switch to the connected state before transmitting the task data, which can improve the reliability of the transmission of task data between the terminal device and the network device.

[0029] In one possible design, the first communication device is a network device, the second communication device is a terminal device, the second communication device is in an inactive state, the first task data is the Nth round of task data obtained by the first communication device performing the task, and N is an integer greater than or equal to 1. The method also includes: when the sending of the second task data does not meet the first condition, the first communication device sends a paging message to the second communication device, and the paging message is used to trigger the second communication device to switch to a connected state, wherein the second task data is the Kth round of task data obtained by the first communication device performing the task, and K is an integer greater than N; after the second communication device switches to the connected state, the first communication device sends the second task data to the second communication device based on a non-small amount of data transmission mechanism.

[0030] Through the above design, when a round of task data does not meet the sending conditions of the small amount of data transmission mechanism, the network device supports instructing the terminal device to switch to the connected state before transmitting the task data, which can improve the reliability of the transmission of task data between the terminal device and the network device.

[0031] In a second aspect, embodiments of the present application provide a communication device having the functionality to implement the method of the first aspect described above. The functionality may be implemented through hardware or through hardware executing corresponding software. The hardware or software may include one or more modules corresponding to the functionality, such as an interface unit and a processing unit.

[0032] In one possible design, the device may be a chip or an integrated circuit.

[0033] In one possible design, the device includes a memory and a processor, the memory is used to store instructions executed by the processor, and when the instructions are executed by the processor, the device can perform the method of the first aspect.

[0034] In a third aspect, an embodiment of the present application provides a communication device, comprising an interface circuit and a processor, wherein the processor and the interface circuit are coupled to each other. The processor implements the method of the first aspect described above through a logic circuit or executing instructions. The interface circuit is configured to receive signals from other communication devices outside the communication device and transmit them to the processor, or to transmit signals from the processor to other communication devices outside the communication device. It will be understood that the interface circuit may be a transceiver, a transceiver, a transceiver, or an input / output interface.

[0035] Optionally, the communication device may further include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute instructions, or storing data generated after the processor executes instructions. The memory may be a physically independent unit, or may be coupled to the processor, or the processor may include the memory (i.e., the processor and memory are integrated together).

[0036] In a possible implementation, the communication device is a chip.

[0037] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the method of the above-mentioned first aspect can be implemented.

[0038] In a fifth aspect, an embodiment of the present application further provides a computer program product, comprising a computer program or instructions, which, when executed by a processor, can implement the method of the first aspect described above.

[0039] In the sixth aspect, an embodiment of the present application also provides a chip system, which includes a processor, the processor is used to couple with a memory, and the memory is used to store programs or instructions. When the program or instruction is executed by the processor, the method of the above-mentioned first aspect can be implemented.

[0040] The technical effects that can be achieved in the second to sixth aspects mentioned above can be referred to the technical effects that can be achieved in the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0042] FIG2 is a schematic diagram of RRC state transition provided in an embodiment of the present application;

[0043] FIG3 is a schematic diagram of a two-step RA-SDT process provided in an embodiment of the present application;

[0044] FIG4 is a schematic diagram of a four-step RA-SDT process according to an embodiment of the present application;

[0045] FIG5 is a schematic diagram of the CG-SDT process provided in an embodiment of the present application;

[0046] FIG6 is a schematic diagram of a task processing method according to an embodiment of the present application;

[0047] FIG7 is a second schematic diagram of a task processing method provided in an embodiment of the present application;

[0048] FIG8 is a third schematic diagram of a task processing method provided in an embodiment of the present application;

[0049] FIG9 is a fourth schematic diagram of a task processing method provided in an embodiment of the present application;

[0050] 10A and 10B are schematic diagrams of a task processing mechanism provided in an embodiment of the present application;

[0051] FIG11 is a fifth schematic diagram of a task processing method provided in an embodiment of the present application;

[0052] FIG12 is a sixth schematic diagram of a task processing method provided in an embodiment of the present application;

[0053] FIG13 is a schematic diagram of a structure of a communication device according to an embodiment of the present application;

[0054] FIG14 is a second schematic diagram of the structure of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, evolved LTE (LTE-advanced, LTE-A) system, universal mobile telecommunications system (UMTS), and fifth generation (5G) mobile communication systems such as NR, beyond 5G (B5G) mobile communication systems, or sixth generation (6G) and other communication systems evolved after 5G. The communication system can also be a device-to-device (D2D) network, a machine-to-machine (M2M) network, an Internet of Things (IoT) network, or other networks.

[0056] The architecture of the communication system used in the embodiments of the present application can be shown in Figure 1. Communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, communication system 1000 may also include the Internet 300. RAN 100 includes at least one network device (such as 110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal device (such as 120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal device 120 is wirelessly connected to network device 110. Network device 110 is wirelessly or wiredly connected to core network 200. The core network devices in core network 200 and network device 110 in RAN 100 may be different physical devices, or they may be the same physical device that integrates core network logical functions and radio access network logical functions.

[0057] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G, 5G, or an evolved system beyond 5G (e.g., a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN) or a cloud radio access network (CRAN). The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0058] The apparatus provided in the embodiment of the present application can be applied to the network device 110 or to the terminal device 120. It is understood that FIG1 only shows a possible communication system architecture to which the embodiment of the present application can be applied, and in other possible scenarios, the communication system architecture may also include other devices.

[0059] The network device 110 is a node in the radio access network (RAN), which can also be called an access network device or a RAN node (or device). The network device 110 is used to help terminal devices achieve wireless access. The multiple network devices 110 in the communication system 1000 can be nodes of the same type or different types. In some scenarios, the roles of the network device 110 and the terminal device 120 are relative. For example, the network element 120i in Figure 1 can be a helicopter or a drone, which can be configured as a mobile base station. For terminal devices 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal device. The network device 110 and the terminal device 120 are sometimes referred to as communication devices. For example, the network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and the network elements 120a-120j can be understood as communication devices with terminal device functions.

[0060] In one possible scenario, a network device can be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next-generation NodeB (gNB), a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, a satellite, an integrated access and backhaul (IAB) node, a mobile switching center, or a network device in a non-terrestrial network (NTN) communication system, i.e., it can be deployed on a high-altitude platform or satellite. The network device can be a macro base station (such as 110a in Figure 1), a micro base station or an indoor station (such as 110b in Figure 1), a relay node or a donor node, or a wireless controller in a CRAN scenario. The network device can also be a device that functions as a base station in device-to-device (D2D) communication, Internet of Vehicles (IoV) communication, drone communication, or machine communication. Optionally, the network device can also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle to everything (V2X) technology may be a road side unit (RSU).

[0061] In another possible scenario, multiple network devices collaborate to assist the terminal device in achieving wireless access, and different network devices respectively implement part of the functions of the base station. For example, the network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It can be understood that the network device can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into a network device in the access network RAN, or the CU can be divided into a network device in the core network CN, which is not limited here.

[0062] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0063] In the embodiments of the present application, the form of the network device is not limited. The device used to implement the function of the network device can be a network device; it can also be a device that can support the network device to implement the function, such as a chip system. The device can be installed in the network device or used in conjunction with the network device.

[0064] The terminal device 120, which may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a device used to provide voice or data connectivity to users, or an IoT device. For example, the terminal device includes a handheld device with wireless connection capabilities, an in-vehicle device, etc. Currently, terminal devices can include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), vehicle-mounted devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and flying devices (such as intelligent robots, hot air balloons, drones, airplanes). Terminal devices can also be other devices with terminal functions, for example, terminal devices can also be devices that function as terminals in D2D communication.

[0065] The embodiments of this application do not limit the device form factor of the terminal device. The device used to implement the functions of the terminal device can be the terminal device; it can also be a device that supports the terminal device to implement the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of a chip or include a chip and other discrete components.

[0066] To facilitate understanding by those skilled in the art, some terms in this application are explained below.

[0067] 1) Radio resource control (RRC) state. There are three different RRC states for terminal devices, namely RRC idle state (RRC_idle), RRC inactive state (RRC_inactive) and RRC connected state (RRC_connected). As shown in Figure 2, the RRC connected state can be converted to the RRC idle state and RRC inactive state. For example: a terminal device in the RRC idle state can request to switch to the RRC connected state by sending an RRC establishment request to the network device; a terminal device in the RRC connected state can switch to the RRC idle state according to an RRC release message from the network device, or can switch to the RRC inactive state according to an RRC temporary release indication (release with suspend) from the network device; a terminal device in the RRC inactive state can request to switch to the RRC connected state by sending an RRC resume request to the network device, or can switch to the RRC idle state according to an RRC release message from the network device.

[0068] In addition, it should be understood that in the embodiments of the present application, the RRC connected state can be referred to as the "connected state", the RRC idle state can be referred to as the "idle state", and the RRC inactive state can be referred to as the "inactive state".

[0069] NR specifies a small data transmission (SDT) mechanism to support small data transmissions from inactive devices. The SDT mechanism enables inactive devices (such as IoT devices) to complete data transmission without switching to an RRC state, significantly reducing signaling overhead and achieving more energy-efficient and faster data transmission.

[0070] There are two types of SDT mechanisms: one is based on random access SDT (RA-SDT), and the other is based on configured grant SDT (CG-SDT).

[0071] The first SDT mechanism, RA-SDT, refers to a situation where the terminal device does not have dedicated wireless resources and the random access message may collide with the random access message sent by other RA-SDT devices. RA-SDT devices also obtain the wireless resources for the random access process from the system information message, similar to non-RA-SDT devices. However, the random access wireless resources of RA-SDT devices and non-RA-SDT devices are separate, that is, RA-SDT devices and non-RA-SDT devices will not interfere with each other during random access. The RA-SDT process can be a two-step or four-step random access process. In the two-step random access process, the payload data to be transmitted is sent together with the initial random access request; in the four-step random access process, the terminal device first resolves the contention conflict through the random access request and random access response, and then uses the RRC recovery request to send the payload data.

[0072] As shown in Figure 3, in the two-step random access process, the terminal device sends a random access request (random access request) to the network device, that is, message A (MsgA), where sending message A can also be called sending a physical random access channel (PRACH) preamble (preable) to the network device, and message A can also include an RRC resume request (RRC resume request) and payload data (payload data); the terminal device receives a random access response (random access response, RAR) from the network device, that is, message B (MsgB), and message B can include an RRC release with suspend indication (RRC release with suspend), instructing the terminal device to remain in an inactive state. As shown in Figure 4, in the four-step random access process, the terminal device sends a random access request to the network device, that is, message 1 (Msg1), which may include a random access preamble; the terminal device receives a random access response from the network device, that is, message 2 (Msg2), which may include a random access preamble, resources for sending data, etc.; the terminal device sends an RRC resume request (RRC resume request) to the network device, that is, message 3 (Msg3), which may include payload data, or payload data and message 3 are sent together (such as in parallel); the terminal device receives an RRC temporary release indication (RRC release with suspend) from the network device, that is, message 4 (Msg4), which indicates that the terminal device remains in an inactive state. As shown in Figures 3 and 4 above, the terminal device maintains an RRC inactive state throughout the entire process, and the random access process will not cause the RRC state of the terminal device to switch.

[0073] The second SDT mechanism, the CG-SDT mechanism, means that wireless resources are allocated periodically based on an estimate of the traffic demand of the terminal device. This uplink scheduling method is called configuration authorization. When using CG-SDT, there will be no message conflicts with other terminal devices because the wireless resources are dedicated to each device. When the terminal device leaves the RRC connected state, the network device sends a resource allocation signal to the terminal device. As shown in Figure 5, the terminal device in the RRC connected state sends assistance information (assistance information) to the network device, which may include a CG request (request); the network device sends an RRC temporary release indication to the terminal device, and the RRC temporary release indication may include a CG configuration (includes CG configuration) for configuring CG resources. After receiving the RRC temporary release indication, the terminal device switches from the RRC connected state to the RRC inactive state. When the data of the terminal device arrives at the transmit buffer (data in the tx buffer), that is, when the terminal device has data to be transmitted, the terminal device can send an RRC recovery request to the network device on the CG resource. The RRC recovery request may include payload data, or the payload data and the RRC recovery request may be sent together; the terminal device receives the RRC temporary release indication from the network device and remains in the RRC inactive state.

[0074] Currently, in future-oriented intelligent and inclusive scenarios, the network's cloud (such as the central node of cloud computing), edge (such as edge devices of cloud computing), and end (such as terminal devices, etc.) need to work together to perform task processing. However, existing task processing requires the terminal device to be in a connected state. Therefore, for terminal devices in an inactive state, they need to switch to a connected state to complete task processing. Frequent state switching will bring about problems such as longer latency, higher signaling overhead, and higher energy consumption. Therefore, how to reduce the latency, signaling overhead, and energy consumption of terminal devices during task processing is an issue that needs to be considered.

[0075] Based on this, the present application provides a task processing method and apparatus to support terminal devices in performing task processing in an inactive state, thereby reducing the time delay, signaling overhead, and energy consumption of the terminal devices during task processing. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0076] Furthermore, it should be understood that ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish between multiple objects and are not used to define the size, content, order, timing, priority, or importance of the multiple objects. For example, the references to first task data and second task data do not indicate a difference in priority or importance between the two task data.

[0077] In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, c can be single or multiple.

[0078] The task processing method provided in the embodiment of the present application can be executed by a first communication device and a second communication device, where the first communication device can be a terminal device, a component of a terminal device (such as a processor, a chip, or a chip system, etc.), or a device used in conjunction with a terminal device; the second communication device can be a network device, a component of a network device (such as a processor, a chip, or a chip system, etc.), or a device used in conjunction with a network device; or, the first communication device can be a network device, a component of a network device (such as a processor, a chip, or a chip system, etc.), or a device used in conjunction with a network device, and the second communication device can be a terminal device, a component of a terminal device (such as a processor, a chip, or a chip system, etc.), or a device used in conjunction with a terminal device, etc.

[0079] The following first describes the access method provided by the present application, taking the first communication device and the second communication device as an example, respectively, to describe a terminal device and a network device. It should be understood that the terminal device may also be a component of the terminal device (such as a processor, chip, or chip system, etc.) or a device used in conjunction with the terminal device, and the network device may also be a component of the network device (such as a processor, chip, or chip system, etc.) or a device used in conjunction with the network device.

[0080] FIG6 is a schematic diagram of a task processing method according to an embodiment of the present application, wherein the method includes:

[0081] S601: The terminal device receives the task.

[0082] Among them, the terminal device is in an inactive state and the task is a non-session task.

[0083] S602: The terminal device obtains first task data obtained by executing the task.

[0084] In the embodiments of the present application, the tasks involved are non-session tasks, that is, non-traditional data transmission tasks (or services), such as data transmission tasks such as non-audio data transmission and video data transmission. The tasks involved may refer to new computing services such as artificial intelligence (AI) and perception. At the network level, they may refer to the process of achieving a specific goal through the collaboration of multi-dimensional resources, for example, the process of jointly achieving a specific goal through the collaboration and deployment of connection, computing, data and algorithm resources in a multi-node scenario. Depending on the different goals, tasks can be divided into task types such as AI training, AI reasoning, computing, and data processing.

[0085] Tasks can be triggered by internal events of the terminal device or by external events. Taking internal event-triggered tasks as an example, when the terminal device collects a certain type of data, or when the collection time of data from one or more sensors reaches a set time threshold, the terminal device can be triggered to process the collected data and report the processing results to the network device. Taking external event-triggered tasks as an example, the network device can issue one or more tasks (such as AI reasoning tasks, AI training tasks, etc.) to the terminal device through non-access stratum (NAS) signaling or RRC signaling. A third party (such as an application server, etc.) can also issue one or more tasks to the terminal device's application, etc.

[0086] After receiving the task, the terminal device may execute the task and obtain first task data obtained by executing the task.

[0087] Taking the AI ​​training task as an example, the terminal device can extract the weights, biases and other parameters in the AI ​​model obtained by the AI ​​training task as task data; or extract the changes in the weights, biases and other parameters in the trained AI model after the AI ​​training task is performed, compared with before the AI ​​training task is performed, as task data, etc. Taking the AI ​​reasoning task as an example, the terminal device can extract the reasoning result of the AI ​​reasoning task as task data. Similarly, if the task is a data processing task, the terminal device can extract the data processing result of the data processing task as task data; if the task is a computing task, the terminal device can extract the computing result as task data.

[0088] In addition, in order to further reduce the transmission overhead of the task data, the first communication device may also perform compression and / or pruning on the acquired first task data.

[0089] As an example: the terminal device can obtain the first task data obtained by executing the task through AI-based semantic extraction technology, and can further compress and / or filter the data volume of the obtained first task data through AI compression and / or AI pruning technologies.

[0090] It should be understood that, in the embodiment of the present application, the tasks received by the terminal device may be one or more. When the terminal device receives multiple tasks, the terminal device may obtain the first task data obtained by executing each task separately.

[0091] S603: When the sending of the first task data meets the first condition, the terminal device sends the first task data to the network device based on a small amount of data transmission mechanism, and accordingly, the network device receives the first task data.

[0092] In an embodiment of the present application, the first condition may also be referred to as a decision condition for starting a small amount of data transmission mechanism. When the task data to be sent meets the first condition, the terminal device may send the task data based on the small amount of data transmission mechanism.

[0093] In one possible implementation, the first condition may include that the amount of data to be transmitted (e.g., the amount of task data to be sent) is less than or equal to a first threshold. The first threshold may be determined based on a transmission data volume threshold (sdt-DataVolumeThreshold) of a small amount of data transmission mechanism, and the first threshold may be less than or equal to the transmission data volume threshold of the small amount of data transmission mechanism.

[0094] Taking the example of a terminal device sending first task data to a network device based on a small amount of data transmission mechanism, the data volume of the first task data should be less than or equal to the first threshold value.

[0095] It can be understood that the terminal device may receive one or more tasks. When the terminal device receives multiple tasks, if the multiple task data corresponding to the multiple tasks are sent together based on a small amount of data transmission mechanism, then the total data volume of the multiple task data corresponding to the multiple tasks should be less than or equal to the first threshold value; if the multiple task data corresponding to the multiple tasks are sent based on a small amount of data transmission respectively, then the data volume of the task data corresponding to each task in the multiple tasks should be less than or equal to the first threshold value.

[0096] When a terminal device receives multiple tasks, whether the multiple task data corresponding to the multiple tasks are sent together based on the small amount of data transmission mechanism or separately based on the small amount of data transmission mechanism can be determined by the terminal device according to the instructions of the network device, the provisions of the protocol, or the configured sending strategy, etc. For example: the configured sending strategy can stipulate that when the terminal device receives multiple tasks, the multiple task data corresponding to the multiple tasks are sent together based on the small amount of data transmission mechanism; or it can stipulate that when the terminal device receives multiple tasks, the multiple task data corresponding to the multiple tasks are sent separately based on the small amount of data transmission mechanism; or it can also stipulate that when the terminal device receives multiple tasks, if the total data volume of the multiple task data corresponding to the multiple tasks is less than or equal to the first threshold value, the multiple task data corresponding to the multiple tasks are sent together based on the small amount of data transmission mechanism; if the total data volume of the multiple task data corresponding to the multiple tasks is greater than the first threshold value, but the data volume of the task data corresponding to each task is less than the first threshold value, the multiple task data of the multiple tasks are sent separately based on the small amount of data transmission mechanism, and so on.

[0097] Taking the example of a terminal device sending multiple first task data corresponding to multiple tasks to a network device based on a small amount of data transmission mechanism, when the multiple first task data are sent together based on the small amount of data transmission mechanism, the total data volume of the multiple first task data should be less than or equal to the first threshold value; when the multiple first task data are sent separately based on the small amount of data transmission mechanism, the data volume of each first task data in the multiple first task data should be less than or equal to the first threshold value.

[0098] In the embodiment of the present application, the amount of data to be transmitted and the first threshold value can also be set according to the specific task.

[0099] For example, in AI-related tasks such as AI training and AI reasoning, the task data (i.e., model data) transmitted over the air interface between the terminal device and the network device can be an identifier (token) or an embedding (embedding) vector. In AI, embedding refers to the process of mapping high-dimensional data (such as text, images, audio, etc.) into a low-dimensional space. An embedding vector is typically a vector composed of real numbers that represents the input data as a point in a continuous numerical space and can be used to represent almost anything, such as text, images, audio, etc. A token can be called an identifier or a tag. In AI, a token generally refers to the smallest unit in the text processing process. A token can be a word, phrase, sentence, or other smaller text unit. An embedding vector can include one or more tokens. Therefore, for AI-related tasks such as AI training and AI reasoning, the amount of data to be transmitted (i.e., the amount of task data) can be the number of tokens or the dimension of the embedding vector, and the corresponding first threshold value can also be the token number threshold value or the embedding vector dimension threshold value. For AI-related tasks such as AI training and AI reasoning, the data volume of the first task data is less than or equal to the first threshold value, which can also be expressed as the number of tokens corresponding to the first task data is less than or equal to the token number threshold value, or the embedding vector dimension corresponding to the first task data is less than or equal to the embedding vector dimension threshold value.

[0100] In some embodiments, the first condition may also include that the channel quality between the terminal device and the network device is greater than or equal to the channel quality threshold value of the small amount of data transmission mechanism to ensure that the channel quality meets the requirements for sending task data based on the small amount of data transmission mechanism.

[0101] Among them, the channel quality can be one or more of the reference signal receiving power (reference signal receiving power, RSRP) and reference signal receiving quality (reference signal receiving quality, RSRQ) of the reference signal received by the terminal device from the network device, and the channel quality threshold value of the small amount of data transmission mechanism can be one or more of the RSRP threshold and the RSRQ threshold.

[0102] When the sending of the first task data corresponding to the task meets the first condition, the terminal device can send the first task data to the network device based on a small amount of data transmission mechanism.

[0103] In an embodiment of the present application, a small amount of data transmission mechanism may be a RA-SDT mechanism, a CG-SDT mechanism, etc., wherein the RA-SDT mechanism may include a two-step RA-SDT mechanism and a four-step RA-SDT mechanism.

[0104] Taking the example of a terminal device sending first task data to a network device based on a two-step RA-SDT mechanism, the terminal device can initiate a two-step random access procedure and send the first task data to the network device via a random access request in the two-step random access procedure (i.e., message A in the two-step random access procedure). The specific implementation can refer to the introduction of the two-step random access procedure in Figure 3 above and will not be repeated here.

[0105] Taking the example of a terminal device sending first task data to a network device based on a four-step RA-SDT mechanism, the terminal device can initiate a four-step random access process and send the first task data to the network device via an RRC recovery request in the four-step random access process (i.e., message 3 in the four-step random access process). The specific implementation can refer to the introduction of the four-step random access process in Figure 4 above and will not be repeated here.

[0106] Taking the example of a terminal device sending first task data to a network device based on the CG-SDT mechanism, the terminal device can initiate an RRC connection establishment / activation process and send the first task data to the network device by sending an RRC recovery request (i.e., message 3 in the CG-SDT mechanism) to the network device on the configuration authorization resource. The specific implementation can refer to the introduction of the RA-SDT mechanism in Figure 5 above and will not be repeated here.

[0107] In some implementations, after receiving the first task data from the terminal device, the network device may further send a receipt confirmation message to the terminal device based on a small amount of data transmission mechanism, indicating that the network device has received the task data. The receipt confirmation message may be sent via message B in the two-step random access process, message 4 in the four-step random access process, or message 4 in the CG-SDT mechanism.

[0108] In some implementations, after receiving a task, the terminal device may also send a task initiation request to the network device based on a small amount of data transmission mechanism before sending the first task data corresponding to the task to the network device, and carry the task identifier of the task in the task initiation request; and receive a task confirmation response including the task identifier of the task sent by the network device based on the small amount of data transmission mechanism to determine that the network device has learned about the task performed by the terminal device.

[0109] Among them, the terminal device can send a task initiation request to the network device through message A in the two-step random access process, message 1 or message 3 in the four-step random access process, or message 3 in the CG-SDT mechanism, and receive a task confirmation response sent by the network device through message B in the two-step random access process, message 2 or message 4 in the four-step random access process, or message 4 in the CG-SDT mechanism. In addition, the task identifier of the task (such as task ID) can be an index, number, indicator, etc. of the task, and the task type identifier of the task can also be included in the task identifier. For example, the task identifier of the task can be composed of the task type index of the task and the index of the task under the task type.

[0110] S604: When the sending of the first task data does not meet the first condition, the terminal device switches to the connected state.

[0111] S605: The terminal device sends the first task data to the network device based on the non-small amount of data transmission mechanism. Correspondingly, the network device receives the first task data.

[0112] As an example: when the transmission of the first task data does not meet the first condition, the terminal device in an inactive state can send an RRC recovery request to the network device. After the network device receives the RRC recovery request from the terminal device, it can determine whether the RRC recovery request is a message sent by the terminal device based on a small amount of data transmission mechanism (such as message A in the two-step random access process in Figure 3, message 3 in the four-step random access process in Figure 4, message 3 in the CG-SDT mechanism in Figure 5, etc.) based on whether the RRC recovery request is sent together with the task data (i.e., payload data). When the RRC recovery request is not sent together with the task data (i.e., payload data), the network device can determine that the RRC recovery request is not a message sent by the terminal device based on a small amount of data transmission mechanism, and the network device can send an RRC recovery response to the terminal device. After the terminal device receives the RRC recovery response from the network device, it can restore the RRC connection with the network device and switch from the inactive state to the connected state. After the terminal device switches from the inactive state to the connected state, the terminal device can send the first task data to the terminal device through the RRC link established between the terminal device and the network device to ensure reliable transmission of the task data.

[0113] It is understandable that the task processing method of the present application can be applied to single-task, multi-task and other scenarios. The task processing method of the present application is explained below in combination with different scenarios.

[0114] Scenario 1: Taking a single task initiated by a terminal device as an example, FIG7 is a second schematic diagram of a task processing method provided by an embodiment of the present application, which includes:

[0115] S701: The terminal device receives the task.

[0116] The terminal device is in an inactive state and the task is a non-session task.

[0117] S702: The terminal device obtains first task data obtained by executing the task.

[0118] The implementation of S701-S702 can refer to the implementation of S601-S602 above and will not be described in detail.

[0119] S703: When the sending of the first task data meets the first condition, the terminal device sends a task initiation request to the network device based on a small amount of data transmission mechanism, and accordingly, the network device receives the task initiation request.

[0120] The task initiation request carries the task identifier of the task. In FIG7 , the task identifier of the task received by the terminal device is taken as task ID1 as an example.

[0121] S704: The network device sends a task confirmation response to the terminal device based on a small amount of data transmission mechanism. Correspondingly, the terminal device receives the task confirmation response.

[0122] The task confirmation response carries the task identifier of the task. In FIG7 , the task identifier of the task received by the terminal device is taken as task ID1 as an example.

[0123] In one possible implementation, the terminal device can send a task initiation request to the network device through message A in the two-step random access process, message 1 or message 3 in the four-step random access process, or message 3 in the CG-SDT mechanism, and receive a task confirmation response sent by the network device through message B in the two-step random access process, message 2 or message 4 in the four-step random access process, or message 4 in the CG-SDT mechanism.

[0124] It should be understood that when the sending of the first task data meets the first condition, the terminal device may also directly execute S705 to send the first task data, that is, the terminal device may not execute S703 and S704.

[0125] S705: The terminal device sends the first task data to the network device based on a small amount of data transmission mechanism. Correspondingly, the network device receives the first task data.

[0126] Optionally, after receiving the first task data from the terminal device, the network device may further send a reception confirmation message to the terminal device based on a small amount of data transmission mechanism, indicating that the first task data has been received.

[0127] In some implementations, when a terminal device sends first task data to a network device based on a small amount of data transmission mechanism, the first task data can be sent together with a task identifier (such as task ID1) corresponding to the first task data, so that the network device can quickly know the task to which the first task data belongs and process the first task data; the reception confirmation information sent by the network device to the terminal device may also include the task identifier (such as task ID1) corresponding to the received first task data, so that the terminal device can quickly know whether the first task data has been sent successfully.

[0128] S706: When the sending of the first task data does not meet the first condition, the terminal device sends an RRC recovery request to the network device, and accordingly, the network device receives the RRC recovery request.

[0129] S707: The network device sends an RRC recovery response to the terminal device, and accordingly, the terminal device receives the RRC recovery response.

[0130] S708: The terminal device sends the first task data to the network device based on the non-small amount of data transmission mechanism.

[0131] When the transmission of the first task data does not meet the first condition, the terminal device in the inactive state can send an RRC recovery request to the network device. After the network device receives the RRC recovery request from the terminal device, it can determine whether the RRC recovery request is a message sent by the terminal device based on a small amount of data transmission mechanism (such as message A in the two-step random access process in Figure 3, message 3 in the four-step random access process in Figure 4, message 3 in the CG-SDT mechanism in Figure 5, etc.) based on whether the RRC recovery request is sent together with the task data (i.e., payload data). When the RRC recovery request is not sent together with the task data (i.e., payload data), the network device can determine that the RRC recovery request is not a message sent by the terminal device based on a small amount of data transmission mechanism, and the network device can send an RRC recovery response to the terminal device. After the terminal device receives the RRC recovery response from the network device, it can restore the RRC connection with the network device and switch from the inactive state to the connected state. After the terminal device switches from the inactive state to the connected state, the terminal device can send the first task data through the RRC link established between it and the network device to ensure reliable transmission of the task data.

[0132] It is understandable that when the terminal device sends the first task data to the network device through the RRC link established between the terminal device and the network device, it can also carry the task identifier corresponding to the first task data (such as task ID1) so that the network device can quickly learn the task to which the task data belongs and process the task data.

[0133] Scenario 2: Taking multiple tasks initiated by the terminal device as an example, FIG8 is a schematic diagram of the third task processing method provided by an embodiment of the present application. This method includes:

[0134] S801: The terminal device receives multiple tasks.

[0135] Among them, the terminal device is in an inactive state, and multiple tasks are non-session tasks.

[0136] S802: The terminal device obtains a plurality of first task data obtained by executing a plurality of tasks.

[0137] When the sending of the plurality of first task data satisfies the first condition, S803 - 805 are executed; when the sending of the plurality of first task data does not satisfy the first condition, S806 - S808 are executed.

[0138] Among them, the implementation of S801-S802 can refer to the implementation of S601-S602 above and will not be described in detail.

[0139] S803: When the sending of the plurality of first task data satisfies the first condition, the terminal device sends a task initiation request to the network device based on a small amount of data transmission mechanism, and accordingly, the network device receives the task initiation request.

[0140] The task initiation request carries the task identifiers of multiple tasks. In FIG8 , it is taken as an example that the terminal device receives two tasks, and the task identifiers of the two tasks are task ID1 and task ID2 respectively.

[0141] S804: The network device sends a task confirmation response to the terminal device based on a small amount of data transmission mechanism. Correspondingly, the terminal device receives the task confirmation response.

[0142] The task confirmation response carries the task identifiers of multiple tasks. In FIG8 , it is taken as an example that the terminal device receives two tasks, and the task identifiers of the two tasks are task ID1 and task ID2 respectively.

[0143] In one possible implementation, the terminal device can send a task initiation request to the network device through message A in the two-step random access process, message 1 or message 3 in the four-step random access process, or message 3 in the CG-SDT mechanism, and receive a task confirmation response sent by the network device through message B in the two-step random access process, message 2 or message 4 in the four-step random access process, or message 4 in the CG-SDT mechanism.

[0144] It should be understood that when the sending of multiple first task data meets the first condition, the terminal device may also directly execute S805 to send multiple first task data, that is, the terminal device may not execute S803 and S804.

[0145] S805: The terminal device sends a plurality of first task data to the network device based on a small amount of data transmission mechanism. Correspondingly, the network device receives the plurality of first task data.

[0146] Optionally, after receiving the multiple first task data from the terminal device, the network device may further send a reception confirmation message to the terminal device based on a small amount of data transmission mechanism, indicating that the multiple first task data have been received.

[0147] In some implementations, when a terminal device sends multiple first task data to a network device based on a small amount of data transmission mechanism, each first task data can be sent together with the task identifier corresponding to the first task data, so that the network device can quickly know the task to which each first task data belongs and process the first task data; the reception confirmation information sent by the network device to the terminal device can also include the task identifier corresponding to each received first task data, so that the terminal device can quickly know whether each first task data is sent successfully.

[0148] As an example: a terminal device receives two tasks, whose task identifiers are task ID1 and task ID2 respectively. The first task data corresponding to the task with task ID1 of the terminal device is first task data 1, and the first task data corresponding to the task with task ID2 is first task data 2. The terminal device can send the first task data 1 + task ID1, and the first task data 2 + task ID2 to the network device based on a small amount of data transmission mechanism. After the network device receives the first task data 1 + task ID1, and the first task data 2 + task ID2 from the terminal device, it can also send a receipt confirmation message including task ID1 and task ID2 to the terminal device based on the small amount of data transmission mechanism, indicating that the first task data 1 and the first task data 2 have been received.

[0149] S806: When the transmission of the plurality of first task data does not satisfy the first condition, the terminal device sends an RRC recovery request to the network device, and accordingly, the network device receives the RRC recovery request.

[0150] S807: The network device sends an RRC recovery response to the terminal device, and accordingly, the terminal device receives the RRC recovery response.

[0151] S808: The terminal device sends a plurality of first task data to the network device based on a non-small amount of data transmission mechanism. Correspondingly, the network device receives at least one first task data.

[0152] When the transmission of multiple first task data does not meet the first condition, the terminal device in the inactive state can send an RRC recovery request to the network device. After the network device receives the RRC recovery request from the terminal device, it can determine whether the RRC recovery request is a message sent by the terminal device based on a small amount of data transmission mechanism (such as message A in the two-step random access process in Figure 3, message 3 in the four-step random access process in Figure 4, message 3 in the CG-SDT mechanism in Figure 5, etc.) based on whether the RRC recovery request is sent together with the task data (i.e., payload data). When the RRC recovery request is not sent together with the task data (i.e., payload data), the network device can determine that the RRC recovery request is not a message sent by the terminal device based on a small amount of data transmission mechanism, and the network device can send an RRC recovery response to the terminal device. After the terminal device receives the RRC recovery response from the network device, it can restore the RRC connection with the network device and switch from the inactive state to the connected state. After the terminal device switches from the inactive state to the connected state, the terminal device can send multiple first task data through the RRC link established between it and the network device to ensure reliable transmission of the task data.

[0153] It can be understood that when the terminal device sends multiple first task data to the network device through the RRC link established between the terminal device and the network device, it can also carry multiple task identifiers corresponding to the first task data (such as task ID1 corresponding to the first task data 1, and task ID2 corresponding to the second task data), so that the network device can quickly learn about the task to which the task data belongs and process the task data.

[0154] In some implementations, a task may be executed in multiple rounds, and there may be multiple rounds of task data that need to be sent. Since the sending of a certain round of task data does not meet the first condition, the terminal device may also switch from the inactive state to the connected state, and then continue to execute the task and send the task data.

[0155] Scenario 3: In the case where a task is initiated by a terminal device and task data is sent, because a certain round of task data transmission does not meet the first condition, the terminal device switches from an inactive state to a connected state and then continues to execute the task and send task data. FIG9 is a fourth schematic diagram of a task processing method provided in an embodiment of the present application, which includes:

[0156] S901: The terminal device receives the task.

[0157] Among them, the terminal device is in an inactive state and the task is a non-session task.

[0158] S902: The terminal device obtains first task data obtained by executing the task.

[0159] S903: The transmission of the first task data satisfies the first condition, and the terminal device sends a task initiation request to the network device based on a small amount of data transmission mechanism. Accordingly, the network device receives the task initiation request, wherein the task initiation request carries a task identifier (such as a task ID).

[0160] S904: The network device sends a task confirmation response to the terminal device based on a small amount of data transmission mechanism, and the terminal device receives the task confirmation response, wherein the task confirmation response carries a task identifier (such as a task ID) of the task.

[0161] The implementation of S901-S904 may refer to the implementation of S701-S704 or S801-S804 described above, and will not be described in detail.

[0162] S905: The terminal device sends the first task data to the network device based on a small amount of data transmission mechanism, and accordingly, the network device receives the task data.

[0163] Optionally, after receiving the first task data from the terminal device, the network device may further send a reception confirmation message to the terminal device based on a small amount of data transmission mechanism, indicating that the first task data has been received.

[0164] In some implementations, when a terminal device sends first task data to a network device based on a small amount of data transmission mechanism, the first task data can be sent together with a task identifier (such as a task ID) corresponding to the first task data, so that the network device can quickly know the task to which the first task data belongs and process the first task data; the reception confirmation information sent by the network device to the terminal device may also include the task identifier corresponding to the received first task data, so that the terminal device can quickly know whether the first task data is sent successfully.

[0165] When a task is executed in multiple rounds and there are multiple rounds of task data being sent, the first task data may be the Nth round of task data obtained by the terminal device when executing the task, where N is an integer greater than or equal to 1, for example, N may be 1 or 2, etc., wherein the sending of each round of task data in the first N rounds of task data obtained by the terminal device when executing the task satisfies the first condition.

[0166] S906: The sending of the second task data does not meet the first condition, the terminal device sends an RRC recovery request to the network device, and accordingly, the network device receives the RRC recovery request.

[0167] S907: The network device sends an RRC recovery response to the terminal device, and accordingly, the terminal device receives the RRC recovery response.

[0168] S908: The terminal device sends the second task data to the network device based on the non-small amount of data transmission mechanism, and accordingly, the network device receives the second task data.

[0169] In an embodiment of the present application, when a task is executed in multiple rounds and there are multiple rounds of task data transmission, the terminal device can judge whether the transmission of each round of task data meets the first condition, or it can judge whether the transmission of task data meets the first condition according to a set interval period, etc. When there is task data (such as second task data) that does not meet the first condition, the terminal device in an inactive state can send an RRC recovery request to the network device. After the network device receives the RRC recovery request from the terminal device, it can determine whether the RRC recovery request is a message sent by the terminal device based on a small amount of data transmission mechanism (such as message A in the two-step random access process in Figure 3, message 3 in the four-step random access process in Figure 4, message 3 in the CG-SDT mechanism in Figure 5, etc.) based on whether the RRC recovery request is sent together with the task data (i.e., payload data). When the RRC recovery request is not sent together with the task data (i.e., payload data), the network device can determine that the RRC recovery request is not a message sent by the terminal device based on the small amount of data transmission mechanism, and the network device can send an RRC recovery response to the terminal device. After receiving the RRC recovery response from the network device, the terminal device can restore the RRC connection with the network device and switch from the inactive state to the connected state. After the terminal device switches from the inactive state to the connected state, the terminal device can send the second task data through the RRC link established between the terminal device and the network device to ensure the reliable transmission of the task data.

[0170] The second task data may be the Kth round of task data obtained when the terminal device executes the task and does not satisfy the first condition, where K is an integer greater than N.

[0171] Referring to the task processing mechanism shown in Figure 10A, the task processing method provided by the embodiment of the present application is that when the terminal device participating in the task is in an inactive state, the terminal device obtains the task data obtained by executing the task after receiving the task, and determines whether the sending of the task data meets the first condition. If the first condition is met, the terminal device can send the task data to the network device participating in the task based on a small amount of data transmission mechanism (taking the SDT mechanism as an example in Figure 10A); if the sending of the task data does not meet the first condition, the terminal device can send an RRC recovery request to the network device, requesting to restore the RRC connection, and then send the task data after switching to the connected state. In addition, referring to the task processing mechanism shown in Figure 10B, based on Figure 10A, if the task is executed for multiple rounds and there are multiple rounds of task data transmission, if the terminal device is still in an inactive state after a round of task data transmission, the terminal device can also judge whether the transmission of task data meets the first condition before each subsequent round of task data transmission or before the subsequent task data transmission according to the set period. If the first condition is met, the task data is sent to the network devices participating in the task based on a small amount of data transmission mechanism; if the transmission of task data does not meet the first condition; the terminal device can send an RRC recovery request to the network device, requesting to restore the RRC connection, switch to the connected state, and then send the task data.

[0172] The above Figures 6 to 10B mainly take the task initiated on the terminal device side as an example to introduce the task processing method of the present application. It can be understood that the task can also be initiated on the network device side. The following takes the first communication device and the second communication device as an example of a network device and a terminal device respectively to introduce the task processing method provided by the present application. It should be understood that the network device can also be a component of the network device (such as a processor, chip, or chip system, etc.) or a device used in conjunction with the network device; the terminal device can also be a component of the terminal device (such as a processor, chip, or chip system, etc.) or a device used in conjunction with the terminal device.

[0173] FIG11 is a fifth schematic diagram of a task processing method provided in an embodiment of the present application, the method comprising:

[0174] S1101: The network device receives the task.

[0175] The task is a non-session task, the participants of the task involve network devices and terminal devices, and the terminal devices are in an inactive state.

[0176] In the embodiments of the present application, tasks can be triggered by internal events of the network device or by external events. Taking internal event-triggered tasks as an example, the network device can trigger an AI inference task for adjusting the channel state when the duration of collecting channel data between the network device and the terminal device reaches a set duration threshold.

[0177] S1102: The network device obtains first task data obtained by executing the task.

[0178] In the embodiment of the present application, the network device may receive one or more tasks. When the network device receives multiple tasks, the network device may obtain the first task data obtained by executing each task respectively. The implementation of the network device obtaining the first task data obtained by executing the task can refer to the implementation of the terminal device obtaining the first task data obtained by executing the task at S602, and will not be further described.

[0179] S1103: When the sending of the first task data meets the first condition, the network device sends the first task data to the terminal device based on a small amount of data transmission mechanism, and accordingly, the terminal device receives the first task data.

[0180] In the embodiment of the present application, the network device determines whether the sending of the first task data satisfies the implementation of the first condition. The determination of whether the sending of the first task data satisfies the implementation of the first condition by the terminal device at S603 may be referred to and will not be repeated.

[0181] As an example: the network device can trigger the terminal device to switch from an inactive state to a connected state by sending a signaling or message such as a paging message to the terminal device. After the terminal device receives the paging message from the network device, it can send an RRC recovery request to the network device (such as sending an RRC recovery request to the network device on the CG resource, message 3 in the CG-SDT mechanism). After the network device receives the RRC recovery request from the terminal device, if the sending of the first task data meets the first condition, the network device can send the first task data to the terminal device by responding to the RRC temporary release indication of the RRC recovery request (such as message 4 in the CG-SDT mechanism). After receiving the RRC temporary release indication, the terminal remains in the inactive state and will not switch to the connected state.

[0182] In some implementations, after receiving the first task data from the network device, the terminal device may also send a receipt confirmation message to the network device based on a small amount of data transmission mechanism, indicating that the terminal device has received the task data. The receipt confirmation message may be sent via Message 3 of the CG-SDT mechanism, for example.

[0183] In some implementations, after receiving a task and before sending the first task data corresponding to the task to the terminal device, the network device may also send a task initiation request to the terminal device based on a small amount of data transmission mechanism, and carry the task identifier of the task (such as a task ID) in the task initiation request; and receive a task confirmation response including the task identifier of the task sent from the terminal device based on the small amount of data transmission mechanism to determine that the terminal device has learned about the task performed by the network device.

[0184] Among them, the network device can send a task initiation request through an RRC temporary release indication (such as message 4 in the CG-SDT mechanism, etc.), and the terminal device can send a task confirmation response to the network device through an RRC recovery request (such as message 3 in the CG-SDT mechanism, etc.).

[0185] S1104: When the transmission of the first task data does not meet the first condition, the network device sends a paging message to the terminal device, and the terminal device receives the paging message accordingly. The paging message is used to trigger the terminal device to switch to a connected state.

[0186] S1105: After the terminal device switches to the connected state, the network device sends the first task data to the terminal device based on a non-small amount of data transmission mechanism, and accordingly, the terminal device receives the first task data.

[0187] As an example: when the sending of the first task data does not meet the first condition, the network device may send a paging message to the terminal device, triggering the terminal device to switch to a connected state. The terminal device that receives the paging message may send an RRC recovery request to the network device. When the sending of the first task data does not meet the first condition, the network device may reply with an RRC recovery response to the terminal device. After receiving the RRC recovery response from the network device, the terminal device may restore the RRC connection with the network device and switch from an inactive state to a connected state. After the terminal device switches from an inactive state to a connected state, the network device may send the first task data to the terminal device through the RRC link established between the network device and the terminal device to ensure reliable transmission of the task data.

[0188] In some implementations, a task may be executed in multiple rounds, and there may be multiple rounds of task data transmission. Since a certain round of task data transmission does not meet the first condition, the network device may also instruct the terminal device to switch from an inactive state to a connected state before continuing to execute the task and sending task data.

[0189] FIG12 is a sixth schematic diagram of a task processing method provided in an embodiment of the present application, the method comprising:

[0190] S1201: The network device receives the task.

[0191] The task is a non-session task, the participants of the task involve network devices and terminal devices, and the terminal devices are in an inactive state.

[0192] S1202: The network device obtains first task data obtained by executing the task.

[0193] S1203: The transmission of the first task data satisfies the first condition. The network device sends a task initiation request to the terminal device based on a small amount of data transmission mechanism. In response, the terminal device receives the task initiation request. The task initiation request carries a task identifier (such as a task ID).

[0194] S1204: The terminal device sends a task confirmation response to the network device based on a small amount of data transmission mechanism, and the network device receives the task confirmation response, wherein the task confirmation response carries a task identifier (such as a task ID) of the task.

[0195] It should be understood that when the sending of the first task data meets the first condition, the network device may directly execute S1205 to send the first task data, that is, the network device may not execute S1203 and S1204.

[0196] S1205: The network device sends the first task data to the terminal device based on a small amount of data transmission mechanism, and accordingly, the terminal device receives the task data.

[0197] Optionally, after receiving the first task data from the network device, the terminal device may further send a reception confirmation message to the network device based on a small amount of data transmission mechanism to indicate that the task data has been received.

[0198] In some implementations, when a network device sends first task data to a terminal device based on a small amount of data transmission mechanism, the first task data can be sent together with a task identifier (such as a task ID) corresponding to the first task data, so that the terminal device can quickly know the task to which the first task data belongs and process the first task data; the reception confirmation information sent by the terminal device to the network device can also include the task identifier (such as a task ID) corresponding to the received first task data, so that the network device can quickly know whether the first task data has been sent successfully.

[0199] When a task is executed in multiple rounds and there are multiple rounds of task data being sent, the first task data can be the Nth round of task data obtained by the network device when executing the task, where N is an integer greater than or equal to 1, for example, N can be 1 or 2, etc., among which the first N rounds of task data obtained by the terminal device when executing the task, the sending of each round of task data meets the first condition.

[0200] S1206: The sending of the second task data does not satisfy the first condition, the network device sends a paging message to the terminal device, and accordingly, the terminal device receives the paging message.

[0201] S1207: The terminal device sends an RRC recovery request to the network device, and accordingly, the network device receives the RRC recovery request.

[0202] S1208: The network device sends an RRC recovery response to the terminal device, and accordingly, the terminal device receives the RRC recovery response.

[0203] S1209: The network device sends the second task data to the terminal device based on the non-small amount of data transmission mechanism, and accordingly, the terminal device receives the second task data.

[0204] In an embodiment of the present application, when a task is executed in multiple rounds and there are multiple rounds of task data transmission, the network device can judge whether the transmission of each round of task data meets the first condition, or it can judge whether the transmission of task data meets the first condition according to a set interval period, etc. When there is task data (such as second task data) that does not meet the first condition, the network device can send a paging message to the terminal device, triggering the terminal device to switch to a connected state. The terminal device that receives the paging message can send an RRC recovery request to the network device. When the transmission of the second task data does not meet the first condition, the network device can reply an RRC recovery response to the terminal device. After the terminal device receives the RRC recovery response from the network device, it can restore the RRC connection with the network device and switch from an inactive state to a connected state. After the terminal device switches from an inactive state to a connected state, the network device can send the second task data to the terminal device through the RRC link established between the network device and the terminal device to ensure reliable transmission of the task data.

[0205] The second task data may be the Kth round of task data sent when the network device executes the task and does not meet the first condition, where K is an integer greater than N.

[0206] The following describes the communication device provided in an embodiment of the present application. Please refer to Figure 13, which is a schematic diagram of the structure of the communication device in an embodiment of the present application. The communication device may include units or modules corresponding to all or part of the steps in the above-mentioned method embodiment, and may be used to execute the steps performed by the first communication device or the second communication device in the above-mentioned method embodiment. For details, please refer to the relevant description in the above-mentioned method embodiment.

[0207] As shown in Figure 13, communication device 1300 includes a processing unit 1310 and an interface unit 1320. Processing unit 1310 may be a processor or processing circuit, and interface unit 1320 may be a transceiver unit or an input / output interface. Communication device 1300 may be used to implement the steps performed by the first communication device or the second communication device in the above embodiments.

[0208] When the communication device 1300 is used to implement the steps performed by the first communication device in the above embodiment:

[0209] The processing unit 1310 is configured to receive a task, wherein the task is a non-session task and the first communication device or the second communication device participating in the task is in an inactive state; and obtain first task data obtained by executing the task;

[0210] The interface unit 1320 is configured to send the first task data to the second communication device based on a small amount of data transmission mechanism when the sending of the first task data meets a first condition.

[0211] For other implementations, please refer to the relevant introduction of the first communication device or the second communication device in the aforementioned embodiments, which will not be repeated here.

[0212] As shown in Figure 14, the present application also provides a communication device 1400, which includes a processor 1410 and may also include a communication interface 1420. The processor 1410 and the communication interface 1420 are coupled to each other. It is understandable that the communication interface 1420 can be a transceiver, an input / output interface, an input interface, an output interface, an interface circuit, etc. Optionally, the communication device 1400 may further include a memory 1430 for storing instructions executed by the processor 1410 or storing input data required by the processor 1410 to execute instructions or storing data generated after the processor 1410 executes instructions. The memory 1430 may be a physically independent unit, or may be coupled to the processor 1410, or the processor 1410 may include the memory 1430.

[0213] When the communication device 1400 is used to implement the steps performed by the first communication device and the second communication device in the above embodiments, the processor 1410 can be used to implement the functions of the above processing unit 1310, and the communication interface 1420 can be used to implement the functions of the above interface unit 1320.

[0214] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), logic circuits, field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0215] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal device. Of course, the processor and the storage medium can also be present in a network device or a terminal device as discrete components.

[0216] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions can be transmitted from one network device, terminal, computer, server, or data center to another network device, terminal, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disk; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0217] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0218] Furthermore, it should be understood that in the embodiments of this application, the word "exemplary" is used to indicate an example, illustration, or description. Any embodiment or design described in this application as "exemplary" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word "exemplary" is intended to present concepts in a concrete manner.

[0219] It is understood that the various numbers used in the embodiments of this application are merely for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the sequence numbers of the above-mentioned processes does not necessarily imply a specific order of execution; the order of execution of the processes should be determined by their functions and inherent logic.

Claims

1. A task processing method, characterized in that: include: The first communication device receives a task, wherein the task is a non-session task, and the first communication device or the second communication device participating in the task is in an inactive state; The first communication device acquires first task data obtained by executing the task; When the sending of the first task data satisfies a first condition, the first communication device sends the first task data to the second communication device based on a small amount of data transmission mechanism.

2. The method according to claim 1, characterized in that The sending of the first task data satisfies a first condition, including: The data volume of the first task data is less than or equal to a first threshold value.

3. The method according to claim 2, characterized in that The first threshold value includes an identifier token number threshold value and / or an embedding vector dimension threshold value, and the data volume of the first task data is less than or equal to the first threshold value, including: The number of tokens corresponding to the first task data is less than or equal to the token number threshold; or, The embedding vector dimension corresponding to the first task data is less than or equal to the embedding vector dimension threshold value.

4. The method according to claim 2 or 3, characterized in that The sending of the first task data satisfies the first condition, further comprising: The channel quality between the first communication device and the second communication device is greater than or equal to a channel quality threshold value of a small amount of data transmission mechanism.

5. The method according to any one of claims 1 to 4, characterized in that Before the first communication device sends the first task data to the second communication device based on a small amount of data transmission mechanism, the method further includes: The first communication device sends a task initiation request to the second communication device based on a small amount of data transmission mechanism, wherein the task initiation request includes a task identifier of the task; The first communication device receives a task confirmation response sent by the second communication device based on a small amount of data transmission mechanism, where the task confirmation response includes a task identifier of the task.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first communication device sends a task identifier corresponding to the first task data to the second communication device based on a small amount of data transmission mechanism.

7. The method according to any one of claims 1 to 6, characterized in that The first communication device is a terminal device, the second communication device is a network device, and the first communication device sends the first task data to the second communication device based on a small amount of data transmission mechanism, including: The first communication device sends the first task data to the second communication device through a random access request in a two-step random access process; or, The first communication device sends the first task data to the second communication device through a radio resource control RRC recovery request in a four-step random access process; or, The first communication device sends the first task data to the second communication device by sending an RRC recovery request to the second communication device on the configuration authorization resource.

8. The method according to any one of claims 1 to 7, characterized in that The first communication device is a terminal device, the second communication device is a network device, and the first communication device is in an inactive state, and the method further includes: When the sending of the first task data does not satisfy a first condition, the first communication device switches to a connected state; The first communication device sends the first task data to the second communication device based on a non-small amount of data transmission mechanism.

9. The method according to any one of claims 1 to 7, characterized in that The first communication device is a terminal device, the second communication device is a network device, the first communication device is in an inactive state, the first task data is the Nth round of task data obtained by the first communication device performing the task, N is an integer greater than or equal to 1, and the method further includes: If the sending of the second task data does not meet the first condition, the first communication device switches to a connected state, wherein the second task data is the Kth round of task data obtained by the first communication device executing the task, and K is an integer greater than N; The first communication device sends the second task data to the second communication device based on a non-small amount of data transmission mechanism.

10. The method according to any one of claims 1 to 6, characterized in that The first communication device is a network device, the second communication device is a terminal device, and the first communication device sends the first task data to the second communication device based on a small amount of data transmission mechanism, including: The first communication device sends the first task data to the second communication device through an RRC temporary release indication, wherein the RRC temporary release indication is used to respond to an RRC recovery request sent by the second communication device.

11. The method according to any one of claims 1 to 6 and 10, characterized in that: The first communication device is a network device, the second communication device is a terminal device, and the second communication device is in an inactive state, and the method further includes: When the sending of the first task data does not satisfy a first condition, the first communication device sends a paging message to the second communication device, wherein the paging message is used to trigger the second communication device to switch to a connected state; After the second communication device switches to the connected state, the first communication device sends the first task data to the second communication device based on a non-small amount of data transmission mechanism.

12. The method according to any one of claims 1 to 6 and 10, characterized in that: The first communication device is a network device, the second communication device is a terminal device, the second communication device is in an inactive state, the first task data is the Nth round of task data obtained by the first communication device performing the task, N is an integer greater than or equal to 1, and the method further includes: When the sending of the second task data does not meet the first condition, the first communication device sends a paging message to the second communication device, the paging message is used to trigger the second communication device to switch to a connected state, wherein the second task data is the Kth round of task data obtained by the first communication device performing the task, and K is an integer greater than N; After the second communication device switches to the connected state, the first communication device sends the second task data to the second communication device based on a non-small amount of data transmission mechanism.

13. The method according to any one of claims 1 to 12, characterized in that The small amount of data transmission mechanism includes: A random access small amount of data transmission mechanism and / or a configuration authorized small amount of data transmission mechanism.

14. A communication device, characterized in that: The method comprises a module or a unit for executing the method according to any one of claims 1 to 13.

15. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 1-13 through a logic circuit or execution instructions.

16. A computer program product, characterized in that The method comprises a computer program or an instruction, and when the computer program or the instruction is executed by a processor, the method according to any one of claims 1 to 13 is implemented.

17. A chip system, characterized in that: The chip system includes a processor, the processor is coupled to a memory, the memory is used to store computer programs or instructions, and when the computer program or instructions are executed by the processor, the method as described in any one of claims 1-13 is implemented.

18. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a processor, the method according to any one of claims 1 to 13 is implemented.

Images