Wireless communication method, terminal, and network-side device

Abstract

The present application belongs to the field of communications. Disclosed are a wireless communication method, a terminal, and a network-side device. The wireless communication method in the embodiments of the present application comprises: a terminal sending a first request to a first network-side device, wherein the first request is used for requesting the first network-side device to establish a first task; and the terminal receiving a first response from the first network-side device. The first response comprises at least one of the following: first information, which is used for identifying the first task; second information, which is used for indicating a message type of the first response; third information, which is used for instructing the terminal to send task data to the first network-side device, or is used for instructing the terminal to send the task data to one or more second network-side devices; fourth information, which is used for indicating address information of the one or more second network-side devices; and fifth information, which comprises information used for the one or more second network-side devices to verify an identity of the terminal.

Description

Wireless communication methods, terminals and network-side equipment

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411628567.3, filed on November 14, 2024, entitled "Wireless Communication Method, Terminal and Network Side Device", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of communication technology, specifically relating to a wireless communication method, terminal, and network-side equipment. Background Technology

[0004] In related technologies, task data is typically transmitted between the terminal and the network via signaling on the control plane. This task data includes, but is not limited to, perception data, artificial intelligence (AI) data, and computational data.

[0005] However, as the frequency and amount of data increase, transmitting task data via control plane signaling cannot guarantee data transmission efficiency. Summary of the Invention

[0006] This application provides a wireless communication method, terminal, and network-side device that can improve data transmission efficiency.

[0007] In a first aspect, a wireless communication method is provided, executed by a terminal, the method comprising:

[0008] The terminal sends a first request to the first network-side device, the first request being used to request the first network-side device to establish a first task;

[0009] The terminal receives a first response from the first network-side device;

[0010] The first response includes at least one of the following:

[0011] The first piece of information is used to identify the first task;

[0012] The second piece of information is used to indicate the message type of the first response;

[0013] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices;

[0014] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0015] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0016] Secondly, a wireless communication method is provided, executed by a first network-side device, the method comprising:

[0017] The first network-side device receives a first request from the terminal, the first request being used to request the first network-side device to establish a first task;

[0018] The first network-side device sends a first response to the terminal;

[0019] The first response includes at least one of the following:

[0020] The first piece of information is used to identify the first task;

[0021] The second piece of information is used to indicate the message type of the first response;

[0022] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices;

[0023] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0024] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0025] Thirdly, a wireless communication method is provided, executed by a second network-side device, the method comprising:

[0026] The second network-side device receives the first message from the terminal, or the second network-side device receives the fourth message from the first network-side device;

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

[0028] The first piece of information is used to identify the first task;

[0029] The ninth piece of information is information used to indicate the notification address of the terminal;

[0030] The tenth piece of information is used to indicate the message type of the first message;

[0031] The eleventh piece of information includes task data for the subtasks of the first task;

[0032] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0033] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal;

[0034] The fourth message includes at least one of the following:

[0035] The first piece of information is used to identify the first task;

[0036] The ninth piece of information is information used to indicate the terminal's notification address;

[0037] The eleventh piece of information includes task data for the subtasks of the first task;

[0038] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0039] Fourthly, a wireless communication device is provided, comprising:

[0040] The sending module is used to send a first request to a first network-side device, the first request being used to request the first network-side device to establish a first task;

[0041] The receiving module is configured to receive a first response from the first network-side device;

[0042] The first response includes at least one of the following:

[0043] The first piece of information is used to identify the first task;

[0044] The second piece of information is used to indicate the message type of the first response;

[0045] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices.

[0046] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0047] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0048] Fifthly, a wireless communication device is provided, comprising:

[0049] The receiving module is configured to receive a first request from the terminal, wherein the first request is used to request the first network-side device to establish a first task;

[0050] The sending module is used to send a first response to the terminal;

[0051] The first response includes at least one of the following:

[0052] The first piece of information is used to identify the first task;

[0053] The second piece of information is used to indicate the message type of the first response;

[0054] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices;

[0055] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0056] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0057] Sixthly, a wireless communication device is provided, comprising:

[0058] The receiving module is used to receive a first message from the terminal, or for the second network-side device to receive a fourth message from the first network-side device;

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

[0060] The first piece of information is used to identify the first task;

[0061] The ninth piece of information is information used to indicate the notification address of the terminal;

[0062] The tenth piece of information is used to indicate the message type of the first message;

[0063] The eleventh piece of information includes task data for the subtasks of the first task;

[0064] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0065] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal;

[0066] The fourth message includes at least one of the following:

[0067] The first piece of information is used to identify the first task;

[0068] The ninth piece of information is information used to indicate the terminal's notification address;

[0069] The eleventh piece of information includes task data for the subtasks of the first task;

[0070] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0071] In a seventh aspect, a wireless communication device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0072] In an eighth aspect, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect.

[0073] Ninthly, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0074] Send a first request to the first network-side device, the first request being used to request the first network-side device to establish a first task;

[0075] Receive a first response from the first network-side device;

[0076] The first response includes at least one of the following:

[0077] The first piece of information is used to identify the first task;

[0078] The second piece of information is used to indicate the message type of the first response;

[0079] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices.

[0080] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0081] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0082] In a tenth aspect, a first network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0083] Eleventhly, a first network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0084] Receive a first request from the terminal, the first request being used to request the first network-side device to establish a first task;

[0085] Send a first response to the terminal;

[0086] The first response includes at least one of the following:

[0087] The first piece of information is used to identify the first task;

[0088] The second piece of information is used to indicate the message type of the first response;

[0089] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices;

[0090] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0091] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0092] In a twelfth aspect, a second network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the third aspect.

[0093] In a thirteenth aspect, a second network-side device is provided, including a processor and a communication interface, wherein the communication interface is used for:

[0094] Receive the first message from the terminal, or receive the fourth message from the first network-side device;

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

[0096] The first piece of information is used to identify the first task;

[0097] The ninth piece of information is information used to indicate the notification address of the terminal;

[0098] The tenth piece of information is used to indicate the message type of the first message;

[0099] The eleventh piece of information includes task data for the subtasks of the first task;

[0100] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0101] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal;

[0102] The fourth message includes at least one of the following:

[0103] The first piece of information is used to identify the first task;

[0104] The ninth piece of information is information used to indicate the terminal's notification address;

[0105] The eleventh piece of information includes task data for the subtasks of the first task;

[0106] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0107] In a fourteenth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0108] In a fifteenth aspect, a wireless communication system is provided, comprising: a terminal, a first network-side device, and a second network-side device, wherein the terminal is configured to perform the steps of the method described in the first aspect, the first network-side device is configured to perform the steps of the method described in the second aspect, and the second network-side device is configured to perform the steps of the method described in the third aspect.

[0109] In a sixteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the steps of the method as described in the third aspect.

[0110] In a seventeenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the wireless communication method as described in the first aspect, or the steps of the wireless communication method as described in the second aspect, or the steps of the method as described in the third aspect.

[0111] In this embodiment, the terminal sends a first request to the first network-side device and receives a first response from the first network-side device, thereby enabling the first network-side device to establish a first task. This allows the terminal to support high-frequency, large-volume data transmission, thereby improving data transmission efficiency.

[0112] Furthermore, when the first response includes the first information, it enables the terminal to transmit and process signaling and / or data related to the first task, thereby accurately associating it with the first task and improving transmission and processing efficiency. When the first response includes the second information, it clearly indicates whether the received message is for task control and management or for task data transmission, helping the terminal directly execute operations matching the first response and enabling rapid signaling interaction, thus improving the transmission efficiency of the first task's task data. When the first response includes the third information, it helps the terminal directly send the task data of the first task to the first network-side device or the second network-side device based on the third information, thereby improving the transmission efficiency of the first task's task data. When the first response includes the fourth or fifth information, it helps the terminal directly send the task data to the second network-side device, reducing the number of relay nodes and thus improving the transmission efficiency of the first task's task data. Attached Figure Description

[0113] Figure 1 is a schematic diagram of a communication system architecture provided in an embodiment of this application.

[0114] Figure 2 is a schematic diagram of a user plane positioning process provided in an embodiment of this application.

[0115] Figures 3 to 6 are schematic flowcharts of the wireless communication method provided in the embodiments of this application.

[0116] Figures 7 to 9 are schematic block diagrams of the wireless communication device provided in the embodiments of this application.

[0117] Figure 10 is a schematic block diagram of a communication device provided in an embodiment of this application.

[0118] Figure 11 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application.

[0119] Figure 12 is a schematic block diagram of a first network-side device provided in an embodiment of this application.

[0120] Figure 13 is a schematic block diagram of a second network-side device provided in an embodiment of this application. Detailed Implementation

[0121] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0122] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0123] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0124] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0125] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (AS), or Wireless Fidelity (WiFi) nodes, etc.The term "base station" can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), or any other suitable term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical terminology. It should be noted that this application embodiment only uses a base station in an NR system as an example for description and does not limit the specific type of base station.

[0126] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), and Binding Support. The core network functions include: BSF (Block Network Function), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), and Network Data Analytics Function (NWDAF). It should be noted that this application embodiment only uses core network equipment in the NR system as an example and does not limit the specific type of core network equipment. If the name of the core network equipment mentioned in this application embodiment changes in subsequent protocol versions (e.g., 6G), it will still be within the scope of protection of this application.

[0127] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0128] To facilitate a better understanding of the embodiments of this application, the related technologies are described.

[0129] Traditional communication systems are designed around connection / session. Their typical application is to provide connections and sessions between specific terminals or between terminals and application servers. The network architecture provides a complete lifecycle management mechanism for sessions (such as the generation, modification, and deletion of end-to-end communication tunnels, anchor migration, etc.) and Quality of Service (QoS) guarantees. Its main purpose is to provide connectivity for data transmission, support user mobility, and ensure a good user experience.

[0130] Unlike traditional communication services, Artificial Intelligence (AI) is a data- and computationally intensive service. To enable 6G networks to possess native AI capabilities, new resource dimensions need to be introduced, including heterogeneous computing and storage resources, new computing tasks (AI-related computations), and new data types (AI computation input and output data). Corresponding management mechanisms need to be designed. On the other hand, 6G networks will have more comprehensive sensing capabilities, including target detection, localization (distance and angle), speed measurement, and 3D imaging, and will introduce radar echo-based solutions. These new network capabilities, such as AI and sensing capabilities, will involve the coordination and allocation of computing power, connectivity, algorithms, and data resources in multi-node scenarios to jointly achieve a specific goal.

[0131] In the future, 6G may introduce a task-centric management mechanism, enabling management at the task level rather than the session level.

[0132] Furthermore, user plane positioning is a positioning technology in which the UE and LMF use the user plane to transmit positioning signaling and measurement data. Figure 2 shows a schematic diagram of a user plane positioning process 200. As shown in Figure 2, this process 200 may include:

[0133] S201. The UE sends a User Plane (UP) positioning to the AMF.

[0134] S202.AMF performs LMF selection.

[0135] S203.AMF sends an UP positioning configuration request to LMF.

[0136] S204.LMF sends UP information to AMF.

[0137] S205.AMF sends UP information to UE.

[0138] S206.UE establishes a secure UP connection.

[0139] S207. The UE sends an UP location confirmation to the AMF.

[0140] S208.AMF sends an UP location confirmation to LMF.

[0141] S209.LMF sends a location UP configuration response to AMF.

[0142] S210.AMF stores the LCS-UP connection context.

[0143] S211. The UE transmits location and supplementary service messages via the UP.

[0144] As shown above, the UP connection establishment process initiated by the UE involves the UE requesting a UP connection, followed by the AMF selecting a suitable LMF. Upon receiving the UP positioning configuration request, the LMF sends UP information to the UE, including the LMF address and connection ID. After receiving the UP information, the UE first establishes a PDU session, and then uses the LMF address and connection ID to establish a secure UP connection between the UE and the LMF. After the connection is established, the UE sends a reply to the LMF to acknowledge the connection. At this point, the UE and LMF can transmit positioning and supplementary service messages via the UP connection.

[0145] The wireless communication method provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0146] It should be understood that the wireless communication method provided in this application involves interaction between at least two of the following: a terminal, a first network-side device, and a second network-side device. The terminal may include, but is not limited to, the type of terminal 11 listed above. The first network-side device or the second network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not specifically limit the types of devices. For example, the first network-side device may be a task management point / function (TMP / TMF), which is abbreviated as TM in this application. As another example, the second network-side device may be a server for a sub-task node, such as, but not limited to, AI servers, computing power servers, sensor servers, and communication access management nodes.

[0147] Figure 3 is a schematic flowchart of a wireless communication method 300 according to an embodiment of this application.

[0148] As shown in Figure 3, the wireless communication method 300 may include at least some of the following:

[0149] S301, the terminal sends a first request to the first network-side device, the first request being used to request the first network-side device to establish a first task.

[0150] For example, after receiving the first request, the first network-side device establishes the first task. Establishing the first task by the first network-side device can be understood as the first network-side device creating, but not limited to, communication session resources, computing power resources, AI resources, data resources, storage resources, spectrum resources, etc., for the first task to complete a task that requires coordination of resources across multiple dimensions. For example, an autonomous driving navigation task requires guaranteed communication resources, data resources, and AI resources for model inference, etc.

[0151] S302, the terminal receives a first response from the first network-side device;

[0152] The first response includes at least one of the following:

[0153] The first piece of information is used to identify the first task;

[0154] The second piece of information is used to indicate the message type of the first response;

[0155] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices;

[0156] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0157] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0158] For example, the first response is used to respond to the first request. The first information may be the task ID of the first task. The task ID may also be referred to as task identification information. The second information is used to indicate that the message type of the first response is the signaling type. As one implementation, the second information may indicate that the message type of the first response is the signaling type by using a bearer, session, or QoS stream used to transmit the first response. For example, if bearer 1 or session 1 is used to transmit task-related control plane signaling, and bearer 2 or session 2 is used to transmit task-related user plane data messages, then the first response is transmitted through bearer 1 or session 1 to indicate that the message type of the first response is the signaling type. Alternatively, a session can be established to distinguish between different QoS streams, i.e., using different filters to distinguish different types of messages at the sending and receiving ends; for example, if on the same PDU session, QoS stream 1 is dedicated to transmitting task-related control plane signaling, and QoS stream 2 is dedicated to transmitting task-related user plane data messages, then the first response is transmitted through QoS stream 1 to indicate that the message type of the first response is the signaling type. In another implementation, the second information can be a value in a bit field. For example, a newly added bit field dedicated to carrying the second information can be used to indicate that the message type of the first response is the signaling type. For example, when the value of the bit field is a specific value, it indicates that the message type of the first response is a signaling type. It should be understood that the message type can include one of task-related signaling types and task-related data types. The signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, task modification messages, etc. The data types include, but are not limited to: task initial data messages, task intermediate processing data messages, task data processing result messages, etc. For example, the second information is used to indicate that the message type of the first response is a task management message or a task connection message. When the value of the third information is a first value, it is used to instruct the terminal to send task data to the first network-side device; when the value of the third information is a second value, it is used to instruct the terminal to send task data to one or more second network-side devices. For example, the first value is 0 and the second value is 1, or the first value is 1 and the second value is 0. The address information of the second network-side device indicated by the fourth information includes, but is not limited to: Fully Qualified Domain Name (FQDN), Internet Protocol (IP) address, and port information.The fifth piece of information used by one or more second network-side devices to verify the identity of the terminal may be security data such as token sets, token lists, and permission profiles.

[0159] For example, the first response may further include a request result, which is used to instruct the first network-side device to accept or reject the first request.

[0160] For example, after receiving the first request or before sending the first response, the first network-side device breaks down the first task into one or more sub-tasks and establishes the one or more sub-tasks with one or more second network-side devices. The first or more second network-side devices are paired with the one or more sub-tasks in a one-to-one or many-to-one manner. For instance, after breaking down the first task into one or more sub-tasks, the first network-side device sends a second request to the one or more second network-side devices and receives a second response from the one or more second network-side devices. The second request is used to request the establishment of sub-tasks, and the second response is used to respond to the second request.

[0161] In this embodiment, the terminal sends a first request to the first network-side device and receives a first response from the first network-side device, thereby enabling the first network-side device to establish a first task. This allows the terminal to support high-frequency, large-volume data transmission, thereby improving data transmission efficiency.

[0162] Furthermore, when the first response includes the first information, it enables the terminal to transmit and process signaling and / or data related to the first task, thereby accurately associating it with the first task and improving transmission and processing efficiency. When the first response includes the second information, it clearly indicates whether the received message is for task control and management or for task data transmission, helping the terminal directly execute operations matching the first response and enabling rapid signaling interaction, thus improving the transmission efficiency of the first task's task data. When the first response includes the third information, it helps the terminal directly send the task data of the first task to the first network-side device or the second network-side device based on the third information, thereby improving the transmission efficiency of the first task's task data. When the first response includes the fourth or fifth information, it helps the terminal directly send the task data to the second network-side device, reducing the number of relay nodes and thus improving the transmission efficiency of the first task's task data.

[0163] In some embodiments, S301 includes:

[0164] The terminal sends the first request to the first network-side device through a user plane connection with the first network-side device.

[0165] For example, when a user plane connection is established between the terminal and the first network-side device, the terminal sends the first request to the first network-side device through the user plane connection with the first network-side device.

[0166] In some embodiments, S302 includes:

[0167] The terminal receives the first response from the first network-side device through a user plane connection with the first network-side device.

[0168] For example, when a user plane connection is established between the terminal and the first network-side device, the terminal receives the first response from the first network-side device through the user plane connection with the first network-side device.

[0169] In some embodiments, prior to S301, the method 300 further includes:

[0170] The terminal establishes a user plane connection with the first network-side device.

[0171] For example, if no user plane connection is established between the terminal and the first network-side device, the terminal first establishes a user plane connection with the first network-side device, and then sends the first request to the first network-side device through the user plane connection with the first network-side device, and / or receives the first response from the first network-side device through the user plane connection with the first network-side device.

[0172] In some embodiments, the first request includes at least one of the following:

[0173] The sixth piece of information is used to identify the session of the first task;

[0174] The seventh piece of information is used to indicate the message type of the first request;

[0175] The eighth piece of information is used to indicate the address information of the first network-side device.

[0176] For example, the sixth information can be understood as information used to identify a session or a connection, such as a connection ID or session ID. The terminal can interact with network-side devices (including a first network-side device or a second network-side device) on a session or a connection to exchange signaling or data related to the first task. It should be noted that the sixth information is different from the first information; the first information identifies a task, specifically a task ID (e.g., 0001 or 0002). One or more task-related information may be exchanged simultaneously on a session or connection. The seventh information is used to indicate that the message type of the first request is the signaling type. As one implementation, the seventh information can indicate that the message type of the first request is the signaling type by using a bearer, session, or QoS stream used to transmit the first request. For example, if bearer 1 or session 1 is used to transmit task-related control plane signaling, and bearer 2 or session 2 is used to transmit task-related user plane data messages, then the first request is transmitted through bearer 1 or session 1 to indicate that the message type of the first request is the signaling type. For example, a session can be established to distinguish different QoS flows, i.e., different filters can be used to differentiate different types of messages at the sending and receiving ends. For instance, if QoS flow 1 is dedicated to transmitting task-related control plane signaling and QoS flow 2 is dedicated to transmitting task-related user plane data messages on the same PDU session, then the first request is transmitted through QoS flow 1 to indicate that the message type of the first response is the signaling type. In another implementation, the seventh information can be a value in a bit field. For example, the value of a newly added bit field dedicated to carrying the seventh information can indicate that the message type of the first request is the signaling type. For example, when the value of the bit field is a specific value, it indicates that the message type of the first request is a signaling type. It should be understood that the message type can include either task-related signaling types or task-related data types. The signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, task modification messages, etc. The data types include, but are not limited to: task initial data messages, task intermediate processing data messages, task data processing result messages, etc. For example, the seventh piece of information is used to indicate that the message type of the first request is a task management message or a task connection establishment message. The address information of the first network-side device indicated by the eighth piece of information may include at least one of the following: FQDN information, IP address, and port information.

[0177] For example, the first request may also include descriptive information such as the template of the first task and the type of the first task.

[0178] In some embodiments, the method 300 further includes:

[0179] The terminal sends a first message to the second network-side device via a user plane connection with the second network-side device, the first message including at least one of the following:

[0180] The first piece of information is used to identify the first task;

[0181] The ninth piece of information is information used to indicate the notification address of the terminal;

[0182] The tenth piece of information is used to indicate the message type of the first message;

[0183] The eleventh piece of information includes task data for the subtasks of the first task;

[0184] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0185] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal.

[0186] For example, the first information may be the task ID of the first task. The task ID may also be referred to as task identification information. The terminal notification address information indicated by the ninth information can be used by the second network-side device to send the execution result of the first task or the execution result of a subtask of the first task to the terminal. The terminal notification address information may be the IP address of the terminal. The tenth information is used to indicate that the message type of the first message is a task-related data type. As one implementation, the tenth information can indicate that the message type of the first message is the data type by using a bearer, session, or QoS stream used to transmit the first message. For example, if bearer 1 or session 1 is used to transmit task-related control plane signaling, and bearer 2 or session 2 is used to transmit task-related user plane data messages, then the first message is transmitted through bearer 2 or session 2 to indicate that the message type of the first message is the data type. For example, a session can be established to distinguish different QoS flows, i.e., different filters can be used to differentiate different types of messages at the sending and receiving ends. For instance, if QoS flow 1 is dedicated to transmitting task-related control plane signaling and QoS flow 2 is dedicated to transmitting task-related user plane data messages on the same PDU session, then the first message is transmitted through QoS flow 2 to indicate that the message type of the first message is the data type mentioned above. In another implementation, the tenth information can be a value in a bit field. For example, the message type of the first message can be indicated by the value of a newly added bit field dedicated to carrying the tenth information. For example, when the value of the bit field is a specific value, it indicates that the message type of the first message is the data type mentioned above. It should be understood that the message type can include either task-related signaling types or task-related data types. The signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, task modification messages, etc. The data types include, but are not limited to: task initial data messages, task intermediate processing data messages, task data processing result messages, etc. For example, the tenth information is used to indicate that the message type of the first message is an initial data message for a task. The task data of the sub-tasks of the first task in the eleventh information can be understood as the raw data of the sub-tasks of the first task. The raw data of the sub-tasks of the first task can be understood as the data used when executing the sub-tasks. For example, the raw data includes, but is not limited to: communication data, image data, GPS location data, audio data, video data, etc.The address information of the second network-side device indicated in the twelfth information includes, but is not limited to: Fully Qualified Domain Name (FQDN), Internet Protocol (IP) address, and port information. The information in the thirteenth information used by the second network-side device to verify the identity of the terminal may be security data such as token sets, token lists, and permission profiles.

[0187] For example, the terminal sends the first message to the second network-side device used to process the first subtask via a user plane connection with one or more second network-side devices used to process the first subtask. The first subtask may be the first subtask in any sequence of one or more subtask sequences processed in parallel. For example, the first subtask may be the first subtask in each of the one or more subtask sequences processed in parallel.

[0188] For example, if the first response includes at least one of the following: the fourth information, the fifth information, or if the first response includes the third information, and the third information is used to instruct the terminal to send task data to the one or more second network-side devices, then the terminal sends the first message to the second network-side device through the user plane connection with the second network-side device.

[0189] In some embodiments, before the terminal sends a first message to the second network-side device via a user plane connection with the second network-side device, the method 300 further includes:

[0190] The terminal establishes a user plane connection with the second network-side device.

[0191] For example, if no user plane connection is established between the terminal and the second network-side device, the terminal first establishes a user plane connection with the second network-side device, and then sends the first message to the first network-side device through the user plane connection with the second network-side device.

[0192] In some embodiments, the method 300 further includes:

[0193] The terminal receives the execution result of the first task or the execution result of a subtask of the first task from the second network-side device via a user plane connection with the second network-side device.

[0194] For example, the terminal receives the execution result of the first task or the execution result of a subtask of the first task from one or more second network-side devices that are used to process the last subtask, via a user plane connection with the second network-side device. The last subtask can be the last subtask in any subtask sequence of one or more subtask sequences processed in parallel. For example, the last subtask can be the last subtask in each of the one or more subtask sequences processed in parallel.

[0195] For example, based on the terminal's notification address information, the terminal receives the execution result of the first task or the execution result of a subtask of the first task from the second network-side device via a user plane connection. The execution result of the first task or the execution result of a subtask of the first task includes, but is not limited to, communication data, sensing data, AI data, and computational data. For instance, when the first task or a subtask of the first task is a sensing task, the second network-side device is a sensing server, and the execution result of the first task or the execution result of a subtask of the first task includes sensing data.

[0196] Of course, the terminal can also receive the execution result of the first task or the execution result of a subtask of the first task from the second network-side device via the UPF. For example, the terminal can receive the execution result of the first task or the execution result of a subtask of the first task from the second network-side device via the UPF based on the terminal's notification address information.

[0197] In some embodiments, the method 300 further includes:

[0198] The terminal sends a second message to the first network-side device via a user plane connection with the first network-side device, the second message including at least one of the following:

[0199] The first piece of information is used to identify the first task;

[0200] The ninth piece of information is information used to indicate the notification address of the terminal;

[0201] The fourteenth piece of information is used to indicate the message type of the second message;

[0202] The fifteenth piece of information includes the task data for the first task;

[0203] The sixteenth piece of information is used to indicate the address information of the first network-side device.

[0204] For example, the first information may be the task ID of the first task. The task ID may also be referred to as task identification information. The terminal notification address information indicated by the ninth information can be used by the second network-side device to send the execution result of the first task or the execution result of a subtask of the first task to the terminal. The terminal notification address information may be the IP address of the terminal. The fourteenth information is used to indicate that the message type of the second message is a task-related data type. As one implementation, the fourteenth information can indicate that the message type of the second message is the data type by using a bearer, session, or QoS stream used to transmit the second message. For example, if bearer 1 or session 1 is used to transmit task-related control plane signaling, and bearer 2 or session 2 is used to transmit task-related user plane data messages, then the second message is transmitted through bearer 2 or session 2 to indicate that the message type of the second message is the data type. For example, a session can be established to distinguish different QoS flows, i.e., different filters can be used to differentiate different types of messages at the sending and receiving ends. For instance, if QoS flow 1 is dedicated to transmitting task-related control plane signaling and QoS flow 2 is dedicated to transmitting task-related user plane data messages on the same PDU session, then the second message is transmitted through QoS flow 2 to indicate that the message type of the second message is the data type mentioned above. In another implementation, the fourteenth information can be a value in a bit field. For example, the message type of the second message can be indicated by the value of a newly added bit field dedicated to carrying the fourteenth information. For example, when the value of the bit field is a specific value, it indicates that the message type of the second message is the data type mentioned above. It should be understood that the message type can include either task-related signaling types or task-related data types. The signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, task modification messages, etc. The data types include, but are not limited to: task initial data messages, task intermediate processing data messages, task data processing result messages, etc. For example, the fourteenth piece of information indicates that the message type of the second message is an initial data message for a task. The task data of the first task in the fifteenth piece of information can be understood as the raw data of the first task. The raw data of the first task can be understood as the data used when executing the first task. For example, the raw data includes, but is not limited to: communication data, image data, GPS location data, audio data, video data, etc.The address information of the first network-side device in the sixteenth information may include at least one of the following: FQDN information, IP address, and port information.

[0205] For example, if the first response includes at least one of the following: the first information, the second information, or if the first response includes the third information, and the third information is used to instruct the terminal to send task data to the first network-side device, then the terminal sends the second message to the first network-side device through the user plane connection with the first network-side device.

[0206] In some embodiments, the method 300 further includes:

[0207] The first network-side device obtains the context of the first task;

[0208] Based on the context of the first task, the first network-side device sends a fourth message to the second network-side device, the fourth message including at least one of the following:

[0209] The first piece of information is used to identify the first task;

[0210] The ninth piece of information is information used to indicate the notification address of the terminal;

[0211] The eleventh piece of information includes task data for the subtasks of the first task;

[0212] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0213] For example, the context of the first task may include at least one of the following: the task context of the terminal (e.g., the processing strategy of the first task, the address of the sub-task node, the processing order of the sub-tasks), the task context corresponding to the port number associated with the first task, the task context corresponding to the IP address associated with the first task, and the task context corresponding to the task identifier of the first task.

[0214] For example, the first information may be the task ID of the first task. The task ID may also be referred to as task identification information. The terminal notification address information indicated by the ninth information may be used by the second network-side device to send the execution result of the first task or the execution result of a subtask of the first task to the terminal. The terminal notification address information may be the IP address of the terminal. The task data of the subtask of the first task in the eleventh information can be understood as the raw data of the subtask of the first task. The raw data of the subtask of the first task can be understood as the data used when executing the subtask. For example, the raw data includes, but is not limited to: communication data, image data, location GPS data, audio data, video data, etc. The address information of the second network-side device indicated by the twelfth information includes, but is not limited to: fully qualified domain name (FQDN), Internet Protocol (IP) address, and port information.

[0215] For example, the first network-side device may send the fourth message to one or more second network-side devices that are used to process the first subtask, based on the context of the first task. The first subtask may be the first subtask in any subtask sequence of one or more subtask sequences processed in parallel. For example, the first subtask may be the first subtask in each subtask sequence of one or more subtask sequences processed in parallel.

[0216] In some embodiments, the method 300 further includes:

[0217] The terminal receives the execution result of the first task or the execution result of a subtask of the first task from the first network-side device through a user plane connection with the first network-side device.

[0218] For example, the first network-side device receives the execution result of the first task or the execution result of a subtask of the first task from the second network-side device, and forwards the execution result of the first task or the execution result of a subtask of the first task to the terminal through a user plane connection with the terminal. For instance, the first network-side device receives the execution result of the first task or the execution result of a subtask of the first task from one or more second network-side devices used to process the last subtask, and forwards the execution result of the first task or the execution result of a subtask of the first task to the terminal through a user plane connection with the terminal. The last subtask can be the last subtask in any subtask sequence of one or more subtask sequences processed in parallel. For example, the last subtask can be the last subtask in each subtask sequence of one or more subtask sequences processed in parallel.

[0219] In some embodiments, prior to S301, the method 300 further includes:

[0220] The terminal receives a third message from the first network-side device, the third message including at least one of the following:

[0221] The sixth piece of information is used to identify the session of the first task;

[0222] The eighth piece of information is used to indicate the address information of the first network-side device;

[0223] The seventeenth piece of information is used to indicate the message type of the third message.

[0224] For example, the sixth information can be understood as information used to identify a session or a connection, such as a connection ID or session ID. The terminal can interact with network-side devices (including the first or second network-side device) on a session or connection to exchange signaling or data related to the first task. It should be noted that the sixth information is different from the first information; the first information identifies a task, specifically a task ID (e.g., 0001 or 0002). One or more task-related information may be exchanged simultaneously on a session or connection. The address information of the first network-side device indicated by the eighth information may include at least one of the following: FQDN information, IP address, and port information. The seventeenth information is used to indicate that the message type of the third message is a task-related signaling type. As one implementation, the seventeenth information can indicate that the message type of the third message is the signaling type through the bearer, session, or QoS stream used to transmit the third message. For example, if bearer 1 or session 1 is used to transmit task-related control plane signaling, and bearer 2 or session 2 is used to transmit task-related user plane data messages, then the third message is transmitted through bearer 1 or session 1 to indicate that the message type of the third message is the signaling type. Alternatively, a session can be established to distinguish between different QoS flows, i.e., using different filters to differentiate different types of messages at the sending and receiving ends; for example, if on the same PDU session, QoS flow 1 is dedicated to transmitting task-related control plane signaling, and QoS flow 2 is dedicated to transmitting task-related user plane data messages, then the third message is transmitted through QoS flow 1 to indicate that the message type of the third message is the signaling type. In another implementation, the seventeenth information can be a value in a bit field. For example, the message type of the third message can be indicated by the value of a newly added bit field dedicated to carrying the seventeenth information. For example, when the value of the bit field is a specific value, it indicates that the message type of the third message is the signaling type. It should be understood that the message type can include either task-related signaling types or task-related data types. The signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, and task modification messages. The data types include, but are not limited to: initial data messages for a task, intermediate processing data messages for a task, and data processing result messages for a task. For example, the seventeenth message indicates that the message type of the third message is a task management message.

[0225] In some embodiments, the message type includes one of task-related signaling types and task-related data types.

[0226] For example, the signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, task modification messages, etc. The data types include, but are not limited to: task initial data messages, task intermediate processing data messages, task data processing result messages, etc.

[0227] It should be understood that the interaction between the terminal and the first network-side device in this application can be relayed or implemented through a UPF. For example, sending information from the terminal to the first network-side device includes: the terminal sending information to the first network-side device through a UPF; or receiving information from the first network-side device includes: the terminal receiving information from the first network-side device through a UPF. This application does not impose specific limitations on this.

[0228] Figure 4 is a schematic flowchart of a wireless communication method 400 according to an embodiment of this application.

[0229] As shown in Figure 4, the wireless communication method 400 may include at least some of the following:

[0230] S401a, the second network-side device receives the first message from the terminal, or

[0231] S401b, the second network-side device receives the fourth message from the first network-side device;

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

[0233] The first piece of information is used to identify the first task;

[0234] The ninth piece of information is information used to indicate the notification address of the terminal;

[0235] The tenth piece of information is used to indicate the message type of the first message;

[0236] The eleventh piece of information includes task data for the subtasks of the first task;

[0237] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0238] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal;

[0239] The fourth message includes at least one of the following:

[0240] The first piece of information is used to identify the first task;

[0241] The ninth piece of information is information used to indicate the terminal's notification address;

[0242] The eleventh piece of information includes task data for the subtasks of the first task;

[0243] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0244] In some embodiments, S401a includes:

[0245] The second network-side device receives the first message from the terminal through a user plane connection with the terminal.

[0246] In some embodiments, before the second network-side device receives the first message from the terminal via a user plane connection with the terminal, the method 400 further includes:

[0247] The second network-side device establishes a user plane connection with the terminal.

[0248] In some embodiments, the method 400 further includes:

[0249] The second network-side device sends the execution result of the first task or the execution result of a subtask of the first task to the terminal through a user plane connection with the terminal.

[0250] In some embodiments, the method 400 further includes:

[0251] The second network-side device sends the execution result of the first task or the execution result of a subtask of the first task to the first network-side device.

[0252] In some embodiments, the message type includes one of task-related signaling types and task-related data types.

[0253] It should be understood that the wireless communication method 400 involves the relevant processes of the second network-side device, which are similar to the interaction between the terminal and the first network-side device, as well as the related terminology and methods 300. Therefore, for a detailed description, please refer to the relevant description in method 300. To avoid repetition, it will not be repeated here.

[0254] This application proposes a method for transmitting task-centric signaling and data between a terminal and a network-side device (including a first network-side device or a second network-side device) based on a secure user plane connection. In one implementation, the terminal sends data of a sub-task of a first task to the second network-side device via the first network-side device, and the second network-side device executes the corresponding sub-task. In another implementation, the terminal directly sends data of the sub-task of the first task to the second network-side device, and the second network-side device executes the corresponding sub-task.

[0255] In this application, mission-centric signaling and data may be transmitted in the following manner:

[0256] For the task-centric signaling in this application, the terminal and the first network-side device transmit the signaling via UPF.

[0257] For task-centric data in this application, one implementation involves the first network-side device not participating in data relay at all; that is, the first network-side device assists the terminal in establishing a user plane connection with the second network-side device, and data flows directly from the terminal to the second network-side device. Another implementation involves the first network-side device acting as a relay station in data transmission: the destination address of the terminal's data is the first network-side device, and the first network-side device distributes relevant information to the second network-side device based on the task context.

[0258] The following description uses TM as the first network-side device and the sub-task node as the second network-side device as an example to illustrate the solution of this application in conjunction with specific embodiments.

[0259] Example 1: TM only participates in the signaling transmission process, not the data transmission process.

[0260] The main idea of ​​this embodiment is:

[0261] The control plane between the UE and TM transmits the information required to establish the user plane connection between the UE and TM. After the user plane connection between the UE and TM is established, the destination address of the task-related data sent by the UE is the subtask node, without needing to go through the TM. This reduces the number of data transmission nodes and improves data processing efficiency. Furthermore, the user plane enables the rapid transmission of large amounts of task data.

[0262] Figure 5 is a schematic flowchart of the wireless communication method 500 provided in an embodiment of this application.

[0263] As shown in Figure 5, the method 500 may include at least some of the following:

[0264] S501.TM receives a task session establishment request from the UE / AF via the CP.

[0265] The TM is responsible for task management, including the context of the task session (such as the type of the task session), UE identity, and task resource management. The TM receives a task session establishment request from the UE / AF (or intranet element (NF)), which is used to request the establishment of a task session connection with the UE.

[0266] S502.TM sends a third message to the UE via CP.

[0267] The third message includes at least one of the following:

[0268] The sixth information is used to identify the session of the first task, and may include at least one of the following: task session ID, task connection ID. The sixth information belongs to the identifier information and is used to distinguish different task sessions / connections. The UE may maintain multiple task sessions with the network, or the TM may maintain task sessions with multiple UEs. Thus, for the UE or TM, it is necessary to distinguish the different UEs or TMs corresponding to different sessions.

[0269] The eighth piece of information is used to indicate the address information of the TM, which includes at least one of the following: FQDN information, TM IP address, and TM port information.

[0270] The seventeenth piece of information indicates the message type of the third message. The message type includes either a task-related signaling type or a task-related data type. In this step, the seventeenth piece of information indicates that the message type of the third message is a signaling type. The implementation of the seventeenth indication can be found in the description of "Adding a Field" below, and will not be repeated here.

[0271] It should be noted that a task session or task connection can be understood as a dedicated bearer or a PDU session. For example, it can be understood as a PDU session established between the UE and the TM. It can also be understood as a relationship based on the PDU session, that is, a PDU session between the UE and the UPF, while the connection from the UE to the TM is a concept that spans from the UE to the UPF and then to the TM. In other words, the underlying layer is the PDU session, and the next layer is the task session / connection. Alternatively, the PDU session can be understood as a subset of the task session / connection, because a task includes multiple functions such as communication, AI, sensing, and computing, and the PDU session that implements the communication function is a part of it, so it can be understood as a subset relationship.

[0272] It should be noted that the TM can include the TM-Control plane (TM-CP) and the TM-User plane (TM-UP), that is, it includes a control plane processing module and a user plane processing module. The control plane processing module can handle the task session establishment request in S501, and can use control signaling to complete the user plane establishment process between the UE and the TM. It also supports maintaining the UE's task context, including the UE identifier, task session identifier, connection port, and UE IP address. The control plane processing module can process the TM address information mentioned in S502, which can be the overall address of the TM or the IP address of the TM-UP. Further explanation: the IP address or port number of the TM-CP and TM-UP can be the same or different. If the IP address / port number is the same, the entire TM can use a single IP address / port number, and subsequent destination addresses and port numbers will be the same. If the IP address / port number is different, using different addresses / port numbers helps the UE or TM distinguish whether the received message is control plane signaling or a message carrying user plane data.

[0273] It should also be noted that, in order to support the UE or TM in distinguishing whether a received message is control plane signaling of signaling type or user plane data of data type, different bearers or different sessions can be established. For example, one bearer or session can be used to transmit task-related control plane signaling, and another bearer or session can be used to transmit task-related user plane data messages. Alternatively, a session can be established with different QoS flows to distinguish between different types of messages, i.e., different filters can be used to distinguish between different types of messages at the sending and receiving ends (for example, on the same PDU session, QoS flow 1 is dedicated to transmitting task-related control plane signaling, and QoS flow 2 is dedicated to transmitting task-related user plane data messages).

[0274] It should also be noted that, to support the UE or TM in distinguishing between received messages that are control plane signaling and messages carrying user plane data, a new bit field can be added to the messages exchanged between the UE and TM. This new bit field can be used to indicate the message type. Signaling types include, but are not limited to: task management messages, task connection establishment messages, task connection release messages, task connection modification messages, task request messages, task release messages, and task modification messages. Data types include, but are not limited to: initial data messages for a task, intermediate processing messages for a task, and data processing result messages for a task. One implementation method includes adding a field to indicate two types: signaling type and data type. Thus, the sender (UE or TM) carries this bit field in the message it sends, and the receiver (UE or TM), after receiving the message, can easily determine whether it is a task-related control plane signaling message or a task-related user plane data message by simply judging the value of the bit field.

[0275] The message type can be indicated by carrying / session / QoS streams or by adding a new bit field; either one or both can be used. This embodiment does not make a specific limitation.

[0276] S503.UE establishes a UP connection with TM.

[0277] The UE uses the sixth information (such as the task session identifier) ​​and the eighth information (the TM's address information) to establish a user plane connection between the UE and the TM. This can be based on a direct connection between the UE and the TM. One implementation is based on a TCP or IP connection, where a socket session is established between the UE and the TM. Alternatively, it can be based on a PDU session, where a new PDU session is created and a dedicated QoS flow for the task is established on the PDU session.

[0278] It should be noted that during the message exchange process of establishing a UP connection between the UE and the TM, the UE may carry first indication information of the message type. The message type includes either a task-related signaling type or a task-related data type. In this step, the first indication information is used to indicate that the relevant message is a task management message. The implementation method of the first indication information can be referred to the previous explanation of "Adding a Field," and will not be repeated here.

[0279] It's also important to note that this step occurs in the user plane, not the control plane signaling. In this step, the TM and UE establish a connection, and either the TM or UE binds the destination to the connection. For example, the TM maintains task connections with multiple UEs. When a UE suddenly sends signaling from the user plane to establish a connection, the TM doesn't know who sent the request. Therefore, the UE might include identification / identity information in its user plane request message to allow the TM to bind the UE to that user plane connection. This allows the TM to subsequently identify who is using the connection.

[0280] S504.UE sends a task connection confirmation via CP to TM.

[0281] After the user plane connection is successfully established, the UE sends a control plane signaling message to the TM, namely the task connection confirmation, which is used to confirm whether the user plane connection was successfully established or not.

[0282] It should be noted that this step is optional.

[0283] It should also be noted that the task connection confirmation may carry second indication information regarding the message type. The message type includes either a task-related signaling type or a task-related data type. In this step, the second indication information is used to indicate that the relevant message is a task management message. The implementation of the second indication information can be found in the previous description of "Adding a Field," and will not be repeated here.

[0284] S505.UE sends the first request to TM.

[0285] The first request is used to request the establishment of a first task. The first request includes at least one of the following:

[0286] The sixth piece of information is used to identify the session of the first task;

[0287] The seventh piece of information is used to indicate the message type of the first request;

[0288] The eighth piece of information is used to indicate the address information of the TM;

[0289] Description information of the first task.

[0290] The description information of the first task includes, but is not limited to: the first request also includes the template of the first task, the type of the first task, and other descriptive information.

[0291] It should be noted that the message type includes either task-related signaling type or task-related data type. In this step, the seventh information is used to indicate that the relevant message is a task management message. The implementation of the seventh information can be referred to the previous description of "Adding a Field," and will not be repeated here.

[0292] S506.TM translates / decomposes the first task into one or more sub-tasks.

[0293] Specifically, TM understands the task and breaks it down into one or more subtasks.

[0294] S507.TM establishes subtasks with multiple subtask nodes.

[0295] Specifically, the TM uses information such as task session identifier and task identifier to interact with subtask nodes, aiming to establish subtasks with them. The subtask nodes reserve relevant resources (communication, AI, computing, perception, etc.). If the UE interacts directly with the subtask node later, the TM may need to obtain the token or profile issued by the subtask node on behalf of the UE. Therefore, the TM sends the token / profile to the UE in subsequent messages, allowing the UE to quickly establish a connection with the subtask node for rapid task data processing.

[0296] It should be noted that subtask nodes include, but are not limited to, AI nodes, communication nodes, computing nodes, and sensory nodes. The AI ​​nodes and computing nodes in the diagram are merely examples of subtask nodes. After task decomposition, tasks can be processed serially among multiple subtask nodes, or they can be processed in multiple overlapping ways: that is, a task can be processed by a simple computing node and then handed over to an AI node, or it can be processed by both a sensory node and a communication node before being handed over to an AI node, or it can be processed by a computing node, then handed over to an AI node, and then processed by a communication node. In short, there are many ways to execute tasks, and this embodiment does not impose specific limitations.

[0297] S508.TM sends the first response to the UE.

[0298] The first response includes at least one of the following:

[0299] The first information is used to identify the first task; for example, the task identifier (Task ID) is used to identify a task. It should be noted that this is different from the task session identifier (such as task session identifier or task connection identifier) ​​in S502. This is specific to a certain task. Multiple tasks can be performed on a session or connection, which means that multiple task identifiers are supported. In other words, the UE can establish / request multiple tasks simultaneously on the same session / connection.

[0300] The second information indicates the message type of the first response; the message type includes either a task-related signaling type or a task-related data type. In this step, the second information indicates that the relevant message is a task management message. The implementation of the second information can be found in the previous description of "Adding a Field," and will not be repeated here.

[0301] The third piece of information is used to instruct the terminal to send task data to one or more sub-task nodes;

[0302] The fourth piece of information is used to indicate the address information of one or more subtask nodes; for example, a list of IP addresses of subtask nodes, which contains the IP addresses of one or more subtask nodes, and optionally includes the execution order of the subtask nodes; another example is the FQDN information or port information of the subtask nodes.

[0303] The fifth piece of information includes information used by one or more sub-task nodes to verify the identity of the terminal; for example: a token list, a permission profile. For sub-task servers that require tokens, the TM obtains the tokens from the sub-task nodes and forwards them to the UE, with each token corresponding to one of the IP addresses of the sub-task nodes.

[0304] The request result is used to instruct TM to accept or reject the first request.

[0305] S509.UE establishes a UP connection with the AI ​​node.

[0306] The UE uses the received IP address of the AI ​​node to establish a user plane connection with the AI ​​node. For example, the UE uses the IP address of the AI ​​node and at least one of the following to establish a user plane connection with the AI ​​node: task session identifier, task identifier, and token / permission information.

[0307] S510. Establish a UP connection with the compute node.

[0308] The UE uses the received IP address of the computing node to establish a user plane connection with the computing node. For example, the UE uses the IP address of the computing node and at least one of the following to establish a user plane connection with the computing node: task session identifier, task identifier, and token / permission information.

[0309] It should be noted that S509 and S510 can be referenced from S503, as the principles are similar. In one implementation, the PDU session of S509 and S510 can be the same as the PDU session in S503, only the QoS flow may be different. For example, the AI ​​subtask and the computation subtask may have different QoS flows.

[0310] It should also be noted that if a task is broken down into multiple subtasks in S506 and the subtasks are sequential, then the UE only needs to establish a user plane connection from the UE to the first subtask node, and user plane connections to other subtask nodes can be established optionally. If a task is broken down into multiple subtasks in S506 and the subtasks are parallel, then the UE can establish a user plane connection from the UE to each subtask node simultaneously and process task data at the same time to speed up task execution.

[0311] S511.UE sends the first message to TM.

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

[0313] The first piece of information is used to identify the first task; for example, the task identifier (Task ID) is used to identify a task. It should be noted that this is different from the task session identifier (such as task session identifier or task connection identifier) ​​in S502. This is specific to a certain task. Multiple tasks can be performed on a session or connection, which means that multiple task identifiers are supported. In other words, the UE can establish / request multiple tasks simultaneously on the same session / connection.

[0314] The ninth piece of information is information indicating the notification address of the terminal, which is used by the subtask node to send the execution result of the subtask to the terminal.

[0315] The tenth piece of information indicates the message type of the first message. The message type includes either a task-related signaling type or a task-related data type. In this step, the tenth piece of information indicates that the relevant message is a data type. The implementation of the tenth piece of information can be found in the previous description of "Adding a Field," and will not be repeated here.

[0316] The eleventh piece of information includes task data for subtasks of the first task; such as communication data, image data, GPS location data, audio data, video data, etc.

[0317] The twelfth piece of information is used to indicate the address information of the subtask node; for example, the FQDN information, IP address, or port information of the subtask node.

[0318] The thirteenth piece of information includes information used by the sub-task nodes to verify the identity of the terminal. For example, a token, a permission profile; for sub-task servers that require a token, the TM obtains it from the sub-task node and forwards it to the UE, with each token corresponding one-to-one with the IP address of the sub-task node.

[0319] S512. AI node executes subtask 1.

[0320] Specifically, the AI ​​node executes subtask 1 based on the first message and obtains the execution result of subtask 1.

[0321] S513. The AI ​​node sends a data transfer message to the computing node.

[0322] The data transfer message may include the execution result of subtask 1, which may be referred to as intermediate data. The data transfer message may also include at least one of the following:

[0323] The first piece of information is used to identify the first task; for example, the task identifier (Task ID) is used to identify a task. It should be noted that this is different from the task session identifier (such as task session identifier or task connection identifier) ​​in S502. This is specific to a certain task. Multiple tasks can be performed on a session or connection, which means that multiple task identifiers are supported. In other words, the UE can establish / request multiple tasks simultaneously on the same session / connection.

[0324] The ninth piece of information is information indicating the notification address of the terminal, which is used by the subtask node to send the execution result of the subtask to the terminal.

[0325] S514. The compute node executes subtask 2.

[0326] Specifically, the calculation remembers to execute subtask 2 based on the received data forwarding message, and obtain the execution result of the first task or the execution result of subtask 2.

[0327] S515. The computing node sends the execution result of the first task or the execution result of subtask 2 to the UE.

[0328] It should be noted that, based on the parameter information carried in the first response issued by S508, if the subtask is executed serially, the UE sends data to the sub-AI node. After the AI ​​node finishes processing, it sends data to the computing node. The computing node, acting as the task endpoint (the last subtask node or the final task processing node), replies to the UE with the execution result of the first task or the execution result of subtask 2 after finishing processing. If the subtask is executed in parallel, the UE sends the task data of the subtask to both the AI ​​node and the computing node. Both the AI ​​node and the computing node, acting as task endpoints (the last subtask node or the final task processing node), reply to the UE with the execution result of the subtask after finishing processing. The attached diagram illustrates the serial execution of subtasks, but this application is not limited to this.

[0329] It should also be noted that in one implementation, the UE has already established a user plane connection to the task endpoint when executing S510, so the task endpoint can directly send the final task result to the UE through the user plane connection; in another implementation, if the user plane connection between the UE and the task endpoint is not established, the task endpoint can send the final task result to the UPF according to the terminal notification address information indicated by the ninth information in S513, and the UPF will forward it to the UE.

[0330] It should also be noted that the execution order and logic of each subtask node can be determined by the TM in S506, and the TM can notify each participating subtask node in S507. This application does not impose specific limitations on this.

[0331] Example 2: TM participates in both the signaling and data transmission processes.

[0332] The main idea of ​​this embodiment is:

[0333] The control plane between the UE and TM transmits the information required to establish a user plane connection between them. After the user plane connection is established, the destination address of task-related data sent by the UE is always the TM, which acts as an intermediary. Therefore, the UE does not need to know how the task is executed on the network side (e.g., the processing logic between sub-task nodes). The UE is completely unaware of the task data processing; it only reports the task data to the TM. The TM processes the task data according to the task breakdown and planning, distributing the data to sub-task nodes for processing. The UE is unaware of which server performs the sub-task. This scheme reduces the user plane connection between the UE and sub-task nodes, avoiding complexity in the UE-to-network interface / connection.

[0334] Figure 6 is a schematic flowchart of the wireless communication method 600 provided in an embodiment of this application.

[0335] As shown in Figure 6, the method 600 may include at least some of the following:

[0336] S601~S607.

[0337] It should be understood that S601 to S607 are the same as S501 to S507. For the specific solutions of S601 to S608, please refer to the relevant descriptions of S501 to S508. To avoid repetition, they will not be repeated here.

[0338] S608.TM sends the first response to the UE.

[0339] The first response includes at least one of the following:

[0340] The first information is used to identify the first task; for example, the task identifier (Task ID) is used to identify a task. It should be noted that this is different from the task session identifier (such as task session identifier or task connection identifier) ​​in S502. This is specific to a certain task. Multiple tasks can be performed on a session or connection, which means that multiple task identifiers are supported. In other words, the UE can establish / request multiple tasks simultaneously on the same session / connection.

[0341] The second information indicates the message type of the first response; the message type includes either a task-related signaling type or a task-related data type. In this step, the second information indicates that the relevant message is a task management message. The implementation of the second information can be found in the previous description of "Adding a Field," and will not be repeated here.

[0342] The third piece of information is used to instruct the terminal to send task data to TM;

[0343] The request result is used to instruct TM to accept or reject the first request.

[0344] S609.UE sends a second message to TM.

[0345] The second message includes at least one of the following:

[0346] The first information is used to identify the first task; for example, the task identifier (Task ID) is used to identify a task. It should be noted that this is different from the task session identifier (such as task session identifier or task connection identifier) ​​in S502. This is specific to a certain task. Multiple tasks can be performed on a session or connection, which means that multiple task identifiers are supported. In other words, the UE can establish / request multiple tasks simultaneously on the same session / connection.

[0347] The ninth piece of information is information indicating the notification address of the terminal, which is used by the subtask node to send the execution result of the subtask to the terminal.

[0348] The fourteenth piece of information indicates the message type of the second message. The message type includes either a task-related signaling type or a task-related data type. In this step, the fourteenth piece of information indicates that the message type of the second message is a data type. The implementation of the second piece of information can be found in the previous explanation of "Adding a Field," and will not be repeated here.

[0349] The fifteenth piece of information includes the task data of the first task; such as communication data, image data, GPS location data, audio data, video data, etc.

[0350] The sixteenth piece of information is used to indicate the TM's address information, such as FQDN information, IP address, or port information.

[0351] In this embodiment, the UE does not need to establish a user plane connection to each subtask node; the UE only needs to send the task data to the TM.

[0352] S610.TM obtains the context of the first task.

[0353] Specifically, after receiving the second message, TM obtains the context of the first task. The context of the first task may include at least one of the following: the UE's task context (e.g., the processing strategy of the first task, the address of the sub-task node, the processing order of the sub-tasks), the task context corresponding to the port number associated with the first task, the task context corresponding to the IP address associated with the first task, and the task context corresponding to the task identifier of the first task.

[0354] S611.TM sends a fourth message to the AI ​​node.

[0355] Specifically, based on the context of the first task, TM sends a fourth message to the AI ​​node, the fourth message including at least one of the following:

[0356] The first information is used to identify the first task; the task ID is used to identify a task. It should be noted that this is different from the task session ID in S502 (such as the task session ID or task connection ID). This is specific to a certain task; multiple tasks can be performed on a session or connection, which means that multiple task IDs are supported. In other words, the UE can establish / request multiple tasks simultaneously on the same session / connection.

[0357] The ninth piece of information is the notification address of the terminal, which is used by the subtask node to send the execution results of the subtask to the terminal.

[0358] The eleventh piece of information includes task data for subtasks of the first task; such as communication data, image data, GPS location data, audio data, video data, etc.

[0359] The twelfth piece of information is used to indicate the address information of the AI ​​node, such as FQDN information, IP address, or port information.

[0360] S612. AI node executes subtask 1.

[0361] Specifically, the AI ​​node executes subtask 1 based on the second message and obtains the execution result of subtask 1.

[0362] S613~S615.

[0363] It should be understood that S613~S615 are the same as S513~S515. For the specific schemes of S612~S615, please refer to the relevant descriptions of S513~S515. To avoid repetition, they will not be repeated here.

[0364] It should also be noted that after executing subtask 2, the task endpoint (e.g., the computing node) sends the execution result of the first task or the execution result of subtask 2 to the UE according to the notification address information of the terminal indicated by the ninth information. Alternatively, the task endpoint (e.g., the computing node) sends the execution result of the first task or the execution result of subtask 2 to the TM, which then sends it to the UE. In this implementation, S611 and S6113 do not need to transmit the ninth information.

[0365] It should also be noted that the execution order and logic of each subtask node can be determined by the TM in S506, and the TM can notify each participating subtask node in S507. This application does not impose specific limitations on this.

[0366] It should also be noted that the message sent by the task endpoint or TM to the UE may optionally carry message type indication information. The message type includes either a task-related signaling type or a task-related data type. For example, in S615, the message type is indicated as a data type. The implementation of this indication information can be found in the previous explanation of "Adding a Field," and will not be repeated here.

[0367] The wireless communication method provided in this application can be executed by a wireless communication device. This application uses an example of a wireless communication device executing the wireless communication method to illustrate the wireless communication device provided in this application.

[0368] This application provides a wireless communication device. As an example, the wireless communication device may be a communication device or a component within a communication device, such as a chip. The communication device may be a terminal, a first network-side device, or a second network-side device, etc. Exemplarily, the terminal may include, but is not limited to, the type of terminal 11 listed above, and the first network-side device or the second network-side device may include, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0369] The wireless communication device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, such as a Central Processing Unit (CPU), microprocessor, Digital Signal Processor (DSP), Artificial Intelligence (AI) processor, Graphics Processing Unit (GPU), Application Specific Integrated Circuit (ASIC), Network Processor (NP), Field Programmable Gate Array (FPGA), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceiver, pins, circuits, bus, radio frequency unit, etc.

[0370] Specifically, referring to Figure 7, when the wireless communication device is a terminal or a component within a terminal, the wireless communication device 710 includes:

[0371] Sending module 711 is used to send a first request to a first network-side device, the first request being used to request the first network-side device to establish a first task;

[0372] The receiving module 712 is configured to receive a first response from the first network-side device;

[0373] The first response includes at least one of the following:

[0374] The first piece of information is used to identify the first task;

[0375] The second piece of information is used to indicate the message type of the first response;

[0376] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices.

[0377] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0378] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0379] In some embodiments, the sending module 711 is specifically used for:

[0380] The first request is sent to the first network-side device via the user plane connection with the first network-side device.

[0381] In some embodiments, the receiving module 712 is specifically used for:

[0382] The first response is received from the first network-side device via a user plane connection with the first network-side device.

[0383] In some embodiments, before the sending module 711 sends the first request to the first network-side device, it is further configured to:

[0384] Establish a user plane connection with the first network-side device.

[0385] In some embodiments, the first request includes at least one of the following:

[0386] The sixth piece of information is used to identify the session of the first task;

[0387] The seventh piece of information is used to indicate the message type of the first request;

[0388] The eighth piece of information is used to indicate the address information of the first network-side device.

[0389] In some embodiments, the sending module 711 is further configured to:

[0390] A first message is sent to the second network-side device via a user plane connection with the second network-side device, the first message including at least one of the following:

[0391] The first piece of information is used to identify the first task;

[0392] The ninth piece of information is information used to indicate the notification address of the terminal;

[0393] The tenth piece of information is used to indicate the message type of the first message;

[0394] The eleventh piece of information includes task data for the subtasks of the first task;

[0395] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0396] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal.

[0397] In some embodiments, before sending the first message to the second network-side device via a user plane connection with the second network-side device, the sending module 711 is further configured to:

[0398] Establish a user plane connection with the second network-side device.

[0399] In some embodiments, the receiving module 712 is further configured to:

[0400] Through the user plane connection with the second network-side device, the execution result of the first task or the execution result of a subtask of the first task is received from the second network-side device.

[0401] In some embodiments, the sending module 711 is further configured to:

[0402] A second message is sent to the first network-side device via a user plane connection with the first network-side device, the second message including at least one of the following:

[0403] The first piece of information is used to identify the first task;

[0404] The ninth piece of information is information used to indicate the notification address of the terminal;

[0405] The fourteenth piece of information is used to indicate the message type of the second message;

[0406] The fifteenth piece of information includes the task data for the first task;

[0407] The sixteenth piece of information is used to indicate the address information of the first network-side device.

[0408] In some embodiments, the receiving module 712 is further configured to:

[0409] Through the user plane connection with the first network-side device, the execution result of the first task or the execution result of a subtask of the first task is received from the first network-side device.

[0410] In some embodiments, before the sending module 711 sends the first request to the first network-side device, the receiving module 712 is further configured to:

[0411] A third message is received from the first network-side device, the third message including at least one of the following:

[0412] The sixth piece of information is used to identify the session of the first task;

[0413] The eighth piece of information is used to indicate the address information of the first network-side device;

[0414] The seventeenth piece of information is used to indicate the message type of the third message.

[0415] In some embodiments, the message type includes one of task-related signaling types and task-related data types.

[0416] Referring to Figure 8, when the wireless communication device is a first network-side device or a component of the first network-side device, the wireless communication device 720 includes:

[0417] The receiving module 721 is used to receive a first request from the terminal, wherein the first request is used to request the first network-side device to establish a first task;

[0418] Sending module 722 is used to send a first response to the terminal;

[0419] The first response includes at least one of the following:

[0420] The first piece of information is used to identify the first task;

[0421] The second piece of information is used to indicate the message type of the first response;

[0422] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices;

[0423] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0424] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0425] In some embodiments, the receiving module 721 is specifically used for:

[0426] The first request is received from the terminal via a user plane connection with the terminal.

[0427] In some embodiments, the sending module 722 is specifically used for:

[0428] The first response is sent to the terminal via a user plane connection with the terminal.

[0429] In some embodiments, before the receiving module 721 receives the first request from the terminal, it is further configured to:

[0430] Establish a user plane connection with the terminal.

[0431] In some embodiments, the first request includes at least one of the following:

[0432] The sixth piece of information is used to identify the session of the first task;

[0433] The seventh piece of information is used to indicate the message type of the first request;

[0434] The eighth piece of information is used to indicate the address information of the first network-side device.

[0435] In some embodiments, the receiving module 721 is further configured to:

[0436] A second message is received from the terminal via a user plane connection with the terminal, the second message including at least one of the following:

[0437] The first piece of information is used to identify the first task;

[0438] The ninth piece of information is information used to indicate the notification address of the terminal;

[0439] The fourteenth piece of information is used to indicate the message type of the second message;

[0440] The fifteenth piece of information includes the task data for the first task;

[0441] The sixteenth piece of information is used to indicate the address information of the first network-side device.

[0442] In some embodiments, the sending module 722 is further configured to:

[0443] Obtain the context of the first task;

[0444] Based on the context of the first task, a fourth message is sent to the second network-side device, the fourth message including at least one of the following:

[0445] The first piece of information is used to identify the first task;

[0446] The ninth piece of information is information used to indicate the notification address of the terminal;

[0447] The eleventh piece of information includes task data for the subtasks of the first task;

[0448] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0449] In some embodiments, the receiving module 721 is further configured to receive the execution result of the first task or the execution result of a subtask of the first task from the second network-side device, and the sending module 722 is further configured to forward the execution result of the first task or the execution result of a subtask of the first task to the terminal through a user plane connection with the terminal.

[0450] In some embodiments, before the receiving module 721 receives the first request from the terminal, the sending module 722 is further configured to:

[0451] A third message is sent to the terminal, the third message including at least one of the following:

[0452] The sixth piece of information is used to identify the session of the first task;

[0453] The eighth piece of information is used to indicate the address information of the first network-side device;

[0454] The seventeenth piece of information is used to indicate the message type of the third message.

[0455] In some embodiments, the message type includes one of task-related signaling types and task-related data types.

[0456] Referring to Figure 9, when the wireless communication device is a second network-side device or a component within a second network-side device, the wireless communication device 730 includes:

[0457] The receiving module 731 is used to receive a first message from the terminal, or for the second network-side device to receive a fourth message from the first network-side device;

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

[0459] The first piece of information is used to identify the first task;

[0460] The ninth piece of information is information used to indicate the notification address of the terminal;

[0461] The tenth piece of information is used to indicate the message type of the first message;

[0462] The eleventh piece of information includes task data for the subtasks of the first task;

[0463] The twelfth piece of information is used to indicate the address information of the second network-side device;

[0464] The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal;

[0465] The fourth message includes at least one of the following:

[0466] The first piece of information is used to identify the first task;

[0467] The ninth piece of information is information used to indicate the terminal's notification address;

[0468] The eleventh piece of information includes task data for the subtasks of the first task;

[0469] The twelfth piece of information is used to indicate the address information of the second network-side device.

[0470] In some embodiments, the receiving module 731 is specifically used for:

[0471] The first message is received from the terminal via a user plane connection with the terminal.

[0472] In some embodiments, before receiving the first message from the terminal via a user plane connection with the terminal, the receiving module 731 is further configured to:

[0473] Establish a user plane connection with the terminal.

[0474] In some embodiments, the device 730 further includes a first transmitting module, configured to:

[0475] The execution result of the first task or the execution result of a subtask of the first task is sent to the terminal via a user plane connection with the terminal.

[0476] In some embodiments, the device 730 further includes a second transmitting module, configured to:

[0477] Send the execution result of the first task or the execution result of a subtask of the first task to the first network-side device.

[0478] In some embodiments, the message type includes one of task-related signaling types and task-related data types.

[0479] The apparatus provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 3 to 6 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0480] As shown in Figure 10, this application embodiment also provides a communication device 800, including a processor 801 and a memory 802. The memory 802 stores programs or instructions that can run on the processor 801. For example, when the communication device 800 is a terminal, the program or instructions executed by the processor 801 implement the various steps executed by the terminal in the above-described wireless communication method embodiment, and achieve the same technical effect. When the communication device 800 is a first network-side device, the program or instructions executed by the processor 801 implement the various steps executed by the first network-side device in the above-described wireless communication method embodiment, and achieve the same technical effect. When the communication device 800 is a second network-side device, the program or instructions executed by the processor 801 implement the various steps executed by the second network-side device in the above-described wireless communication method embodiment, and achieve the same technical effect. To avoid repetition, further details are omitted here.

[0481] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiments shown in Figures 3 to 6. This terminal embodiment corresponds to the above-described terminal-side method embodiments, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal can be the wireless communication device shown in Figure 7. Specifically, Figure 11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

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

[0483] Those skilled in the art will understand that the terminal 900 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to the processor 910 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 11 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0484] It should be understood that, in this embodiment, the input unit 904 may include a graphics processor 9041 and a microphone 9042. The graphics processor 9041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 906 may include a display panel 9061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 907 includes at least one of a touch panel 9071 and other input devices 9072. The touch panel 9071 is also called a touch screen. The touch panel 9071 may include a touch detection device and a touch controller. Other input devices 9072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0485] In this embodiment, after receiving downlink data from the first network-side device or the second network-side device, the radio frequency unit 901 can transmit it to the processor 910 for processing; in addition, the radio frequency unit 901 can send uplink data to the first network-side device or the second network-side device. Typically, the radio frequency unit 901 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

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

[0487] Processor 910 may include one or more processing units; optionally, processor 910 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 910.

[0488] The radio frequency unit 901 is used for:

[0489] Send a first request to the first network-side device, the first request being used to request the first network-side device to establish a first task;

[0490] Receive a first response from the first network-side device;

[0491] The first response includes at least one of the following:

[0492] The first piece of information is used to identify the first task;

[0493] The second piece of information is used to indicate the message type of the first response;

[0494] The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices.

[0495] The fourth piece of information is used to indicate the address information of one or more second network-side devices;

[0496] The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

[0497] In this embodiment, the terminal sends a first request to the first network-side device and receives a first response from the first network-side device, thereby enabling the first network-side device to establish a first task. This allows the terminal to support high-frequency, large-volume data transmission, thereby improving data transmission efficiency.

[0498] Furthermore, when the first response includes the first information, it enables the terminal to transmit and process signaling and / or data related to the first task, thereby accurately associating it with the first task and improving transmission and processing efficiency. When the first response includes the second information, it clearly indicates whether the received message is for task control and management or for task data transmission, helping the terminal directly execute operations matching the first response and enabling rapid signaling interaction, thus improving the transmission efficiency of the first task's task data. When the first response includes the third information, it helps the terminal directly send the task data of the first task to the first network-side device or the second network-side device based on the third information, thereby improving the transmission efficiency of the first task's task data. When the first response includes the fourth or fifth information, it helps the terminal directly send the task data to the second network-side device, reducing the number of relay nodes and thus improving the transmission efficiency of the first task's task data.

[0499] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above wireless communication method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0500] This application also provides a first network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps executed by the first network-side device in the method embodiments shown in Figures 3 to 6. This first network-side device embodiment corresponds to the above-described first network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this first network-side device embodiment and can achieve the same technical effect.

[0501] Specifically, this application embodiment also provides a first network-side device, which may be the wireless communication device shown in FIG8. As shown in FIG12, the first network-side device 1000 includes: an antenna 101, a radio frequency device 102, a baseband device 103, a processor 104, and a memory 105. The antenna 101 is connected to the radio frequency device 102. In the uplink direction, the radio frequency device 102 receives information through the antenna 101 and sends the received information to the baseband device 103 for processing. In the downlink direction, the baseband device 103 processes the information to be transmitted and sends it to the radio frequency device 102. The radio frequency device 102 processes the received information and transmits it through the antenna 101.

[0502] The method executed by the first network-side device in the above embodiments can be implemented in the baseband device 103, which includes a baseband processor.

[0503] The baseband device 103 may include at least one baseband board, on which multiple chips are disposed, one of which is, for example, a baseband processor, as shown in FIG12. The baseband device 103 is connected to the memory 105 through a bus interface to call the program in the memory 105 and execute the network device operation shown in the above method embodiment.

[0504] The first network-side device may also include a network interface 106, such as a Common Public Radio Interface (CPRI).

[0505] Specifically, the first network-side device 1000 in this application embodiment further includes: instructions or programs stored in memory 105 and executable on processor 104. Processor 104 calls the instructions or programs in memory 105 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0506] This application also provides a second network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps executed by the second network-side device in the method embodiments shown in Figures 3 to 6. This second network-side device embodiment corresponds to the above-described second network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this second network-side device embodiment and can achieve the same technical effect.

[0507] Specifically, this application embodiment also provides a second network-side device, which may be the wireless communication device shown in FIG9. Specifically, this application embodiment also provides a second network-side device. As shown in FIG13, the second network-side device 1100 includes: a processor 1101, a network interface 1102, and a memory 1103. The second network-side device may be the wireless communication device shown in FIG8. The network interface 1102 is, for example, a common public radio interface (CPRI).

[0508] Specifically, the second network-side device 1100 in this application embodiment further includes: instructions or programs stored in memory 1103 and executable on processor 1101. Processor 1101 calls the instructions or programs in memory 1103 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0509] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described wireless communication method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0510] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0511] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described wireless communication method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0512] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0513] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described wireless communication method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0514] This application also provides a communication system, including: a terminal, a first network-side device, and a second network-side device. The terminal can be used to perform the steps executed by the terminal in the wireless communication method described above. The first network-side device can be used to perform the steps executed by the first network-side device in the wireless communication method described above. The second network-side device can be used to perform the steps executed by the second network-side device in the wireless communication method described above.

[0515] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0516] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions to cause the terminal, the first network-side device, or the second network-side device to execute the methods described in the various embodiments of this application.

[0517] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A wireless communication method, wherein, include: The terminal sends a first request to the first network-side device, the first request being used to request the first network-side device to establish a first task; The terminal receives a first response from the first network-side device; The first response includes at least one of the following: The first piece of information is used to identify the first task; The second piece of information is used to indicate the message type of the first response; The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices; The fourth piece of information is used to indicate the address information of one or more second network-side devices; The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

2. The method according to claim 1, wherein, The terminal sends a first request to the first network-side device, including: The terminal sends the first request to the first network-side device through a user plane connection with the first network-side device.

3. The method according to claim 1 or 2, wherein, The terminal receives a first response from the first network-side device, including: The terminal receives the first response from the first network-side device through a user plane connection with the first network-side device.

4. The method according to any one of claims 1 to 3, wherein, Before the terminal sends the first request to the first network-side device, the method further includes: The terminal establishes a user plane connection with the first network-side device.

5. The method according to any one of claims 1 to 4, wherein, The first request includes at least one of the following: The sixth piece of information is used to identify the session of the first task; The seventh piece of information is used to indicate the message type of the first request; The eighth piece of information is used to indicate the address information of the first network-side device.

6. The method according to any one of claims 1 to 5, wherein, The method further includes: The terminal sends a first message to the second network-side device via a user plane connection with the second network-side device, the first message including at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the notification address of the terminal; The tenth piece of information is used to indicate the message type of the first message; The eleventh piece of information includes task data for the subtasks of the first task; The twelfth piece of information is used to indicate the address information of the second network-side device; The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal.

7. The method according to claim 6, wherein, Before the terminal sends the first message to the second network-side device via a user plane connection with the second network-side device, the method further includes: The terminal establishes a user plane connection with the second network-side device.

8. The method according to claim 6 or 7, wherein, The method further includes: The terminal receives the execution result of the first task or the execution result of a subtask of the first task from the second network-side device via a user plane connection with the second network-side device.

9. The method according to any one of claims 1 to 5, wherein, The method further includes: The terminal sends a second message to the first network-side device via a user plane connection with the first network-side device, the second message including at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the notification address of the terminal; The fourteenth piece of information is used to indicate the message type of the second message; The fifteenth piece of information includes the task data for the first task; The sixteenth piece of information is used to indicate the address information of the first network-side device.

10. The method according to claim 9, wherein, The method further includes: The terminal receives the execution result of the first task or the execution result of a subtask of the first task from the first network-side device through a user plane connection with the first network-side device.

11. The method according to any one of claims 1 to 10, wherein, Before the terminal sends the first request to the first network-side device, the method further includes: The terminal receives a third message from the first network-side device, the third message including at least one of the following: The sixth piece of information is used to identify the session of the first task; The eighth piece of information is used to indicate the address information of the first network-side device; The seventeenth piece of information is used to indicate the message type of the third message.

12. The method according to any one of claims 1 to 11, wherein, The message type includes one of the following: task-related signaling type and task-related data type.

13. A wireless communication method, wherein, include: The first network-side device receives a first request from the terminal, the first request being used to request the first network-side device to establish a first task; The first network-side device sends a first response to the terminal; The first response includes at least one of the following: The first piece of information is used to identify the first task; The second piece of information is used to indicate the message type of the first response; The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices; The fourth piece of information is used to indicate the address information of one or more second network-side devices; The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

14. The method according to claim 13, wherein, The first network-side device receives a first request from the terminal, including: The first network-side device receives the first request from the terminal through a user plane connection with the terminal.

15. The method according to claim 13 or 14, wherein, The first network-side device sends a first response to the terminal, including: The first network-side device sends the first response to the terminal through a user plane connection with the terminal.

16. The method according to any one of claims 13 to 15, wherein, Before the first network-side device receives the first request from the terminal, the method further includes: The first network-side device establishes a user plane connection with the terminal.

17. The method according to any one of claims 13 to 16, wherein, The first request includes at least one of the following: The sixth piece of information is used to identify the session of the first task; The seventh piece of information is used to indicate the message type of the first request; The eighth piece of information is used to indicate the address information of the first network-side device.

18. The method according to any one of claims 13 to 17, wherein, The method further includes: The first network-side device receives a second message from the terminal via a user plane connection with the terminal, the second message including at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the notification address of the terminal; The fourteenth piece of information is used to indicate the message type of the second message; The fifteenth piece of information includes the task data for the first task; The sixteenth piece of information is used to indicate the address information of the first network-side device.

19. The method according to claim 18, wherein, The method further includes: The first network-side device obtains the context of the first task; Based on the context of the first task, the first network-side device sends a fourth message to the second network-side device, the fourth message including at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the notification address of the terminal; The eleventh piece of information includes task data for the subtasks of the first task; The twelfth piece of information is used to indicate the address information of the second network-side device.

20. The method according to claim 18 or 19, wherein, The method further includes: The first network-side device receives the execution result of the first task or the execution result of a subtask of the first task from the second network-side device, and forwards the execution result of the first task or the execution result of a subtask of the first task to the terminal through the user plane connection with the terminal.

21. The method according to any one of claims 13 to 20, wherein, Before the first network-side device receives the first request from the terminal, the method further includes: The first network-side device sends a third message to the terminal, the third message including at least one of the following: The sixth piece of information is used to identify the session of the first task; The eighth piece of information is used to indicate the address information of the first network-side device; The seventeenth piece of information is used to indicate the message type of the third message.

22. The method according to any one of claims 13 to 21, wherein, The message type includes one of the following: task-related signaling type and task-related data type.

23. A wireless communication method, wherein, include: The second network-side device receives the first message from the terminal, or the second network-side device receives the fourth message from the first network-side device; The first message includes at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the notification address of the terminal; The tenth piece of information is used to indicate the message type of the first message; The eleventh piece of information includes task data for the subtasks of the first task; The twelfth piece of information is used to indicate the address information of the second network-side device; The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal; The fourth message includes at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the terminal's notification address; The eleventh piece of information includes task data for the subtasks of the first task; The twelfth piece of information is used to indicate the address information of the second network-side device.

24. The method according to claim 23, wherein, The second network-side device receives a first message from the terminal, including: The second network-side device receives the first message from the terminal through a user plane connection with the terminal.

25. The method according to claim 24, wherein, Before the second network-side device receives the first message from the terminal via a user plane connection with the terminal, the method further includes: The second network-side device establishes a user plane connection with the terminal.

26. The method according to any one of claims 23 to 25, wherein, The method further includes: The second network-side device sends the execution result of the first task or the execution result of a subtask of the first task to the terminal through a user plane connection with the terminal.

27. The method according to any one of claims 23 to 25, wherein, The method further includes: The second network-side device sends the execution result of the first task or the execution result of a subtask of the first task to the first network-side device.

28. The method according to any one of claims 23 to 27, wherein, The message type includes one of the following: task-related signaling type and task-related data type.

29. A wireless communication device, wherein, include: The sending module is used to send a first request to a first network-side device, the first request being used to request the first network-side device to establish a first task; The receiving module is configured to receive a first response from the first network-side device; The first response includes at least one of the following: The first piece of information is used to identify the first task; The second piece of information is used to indicate the message type of the first response; The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices. The fourth piece of information is used to indicate the address information of one or more second network-side devices; The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

30. The apparatus according to claim 29, wherein, The sending module is specifically used for: The first request is sent to the first network-side device via the user plane connection with the first network-side device.

31. The apparatus according to claim 29 or 30, wherein, The receiving module is specifically used for: The first response is received from the first network-side device via a user plane connection with the first network-side device.

32. A wireless communication device, wherein, include: The receiving module is configured to receive a first request from the terminal, wherein the first request is used to request the first network-side device to establish a first task; The sending module is used to send a first response to the terminal; The first response includes at least one of the following: The first piece of information is used to identify the first task; The second piece of information is used to indicate the message type of the first response; The third piece of information is used to instruct the terminal to send task data to the first network-side device, or to instruct the terminal to send task data to one or more second network-side devices; The fourth piece of information is used to indicate the address information of one or more second network-side devices; The fifth piece of information includes information used by one or more second network-side devices to verify the identity of the terminal.

33. The apparatus according to claim 32, wherein, The receiving module is specifically used for: The first request is received from the terminal via a user plane connection with the terminal.

34. The apparatus according to claim 32 or 33, wherein, The sending module is specifically used for: The first response is sent to the terminal via a user plane connection with the terminal.

35. A wireless communication device, wherein, include: The receiving module is used to receive a first message from the terminal, or for the second network-side device to receive a fourth message from the first network-side device; The first message includes at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the notification address of the terminal; The tenth piece of information is used to indicate the message type of the first message; The eleventh piece of information includes task data for the subtasks of the first task; The twelfth piece of information is used to indicate the address information of the second network-side device; The thirteenth piece of information includes information used by the second network-side device to verify the identity of the terminal; The fourth message includes at least one of the following: The first piece of information is used to identify the first task; The ninth piece of information is information used to indicate the terminal's notification address; The eleventh piece of information includes task data for the subtasks of the first task; The twelfth piece of information is used to indicate the address information of the second network-side device.

36. The apparatus according to claim 35, wherein, The second network-side device receives a first message from the terminal, including: The second network-side device receives the first message from the terminal through a user plane connection with the terminal.

37. A terminal, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the wireless communication method according to any one of claims 1 to 12.

38. A network-side device, wherein, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the wireless communication method according to any one of claims 13 to 22, or to implement the steps of the wireless communication method according to any one of claims 23 to 28.

39. A readable storage medium, wherein, The readable storage medium stores a program or instructions that, when executed by a processor, implement the wireless communication method according to any one of claims 1 to 12, or implement the steps of the wireless communication method according to any one of claims 13 to 22, or implement the steps of the wireless communication method according to any one of claims 23 to 28.

Images