Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a terminal device sends first information to a network device, the first information being used for requesting establishment of a data radio bearer, and the first information comprising one or more of the following: first indication information, used for indicating a task type that triggers the terminal device to request establishment of the data radio bearer; second indication information, used for indicating a QoS flow requirement that the data radio bearer requested to be established by the terminal device needs to satisfy; third indication information, used for indicating an RLC mode requirement that the data radio bearer requested to be established by the terminal device needs to satisfy; and fourth indication information, used for indicating a data amount corresponding to data that the terminal device expects to send. In embodiments of the present application, the terminal device sends the first information to the network device for requesting establishment of the data radio bearer, and the first information carries part or all of information such as the task type that triggers the terminal device to request establishment of the data radio bearer, the QoS flow requirement that the data radio bearer requested to be established by the terminal device needs to satisfy, the RLC mode requirement that the data radio bearer requested to be established by the terminal device needs to satisfy, and the data amount corresponding to the data that the terminal device expects to send, thereby assisting the network device in establishing a suitable data radio bearer for the terminal device, expanding service types capable of being transmitted by means of the data radio bearer, and enabling the terminal device to transmit a corresponding type of data service by means of the suitable data radio bearer.

Description

Wireless communication methods, terminal devices, and network devices Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal device, and network device. Background Technology

[0002] Typically, data radio bearers are established by access network devices in response to requests from core network devices, primarily for application-layer service transmission. However, with the gradual application of artificial intelligence (AI) technology in communication systems, the types of data transmission services in communication systems are undergoing significant changes, expanding from single application-layer data transmission services to data transmission services within the communication system itself, such as model transmission tasks and model training dataset transmission tasks. How to transmit this data via data radio bearers has become a problem that needs to be solved. Summary of the Invention

[0003] This application provides a wireless communication method, terminal device, and network device. The various aspects covered by this application are described below.

[0004] In a first aspect, a wireless communication method is provided, comprising: a terminal device sending first information to a network device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: first indication information, used to indicate the task type that triggers the terminal device to request the establishment of the data radio bearer; second indication information, used to indicate the quality of service (QoS) flow requirements that the data radio bearer requested by the terminal device needs to meet; third indication information, used to indicate the radio link control (RLC) mode requirements that the data radio bearer requested by the terminal device needs to meet; and fourth indication information, used to indicate the amount of data corresponding to the data that the terminal device expects to send.

[0005] In a second aspect, a wireless communication method is provided, comprising: a network device receiving first information sent by a terminal device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: first indication information, used to indicate the task type that triggers the terminal device to request the establishment of the data radio bearer; second indication information, used to indicate the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet; third indication information, used to indicate the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet; and fourth indication information, used to indicate the amount of data corresponding to the data that the terminal device expects to send.

[0006] Thirdly, a terminal device is provided, comprising: a transceiver unit, configured to send first information to a network device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: first indication information, used to indicate the task type that triggers the terminal device to request the establishment of the data radio bearer; second indication information, used to indicate the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet; third indication information, used to indicate the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet; and fourth indication information, used to indicate the amount of data corresponding to the data that the terminal device expects to send.

[0007] Fourthly, a network device is provided, comprising: a transceiver unit, configured to receive first information sent by a terminal device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: first indication information, used to indicate the task type that triggers the terminal device to request the establishment of the data radio bearer; second indication information, used to indicate the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet; third indication information, used to indicate the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet; and fourth indication information, used to indicate the amount of data corresponding to the data that the terminal device expects to send.

[0008] Fifthly, a terminal device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, and the processor is used to invoke the program in the memory and control the transceiver to receive or send signals so that the terminal device performs the method as described in the first aspect.

[0009] In a sixth aspect, a network device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, and the processor is used to invoke the program in the memory and control the transceiver to receive or transmit signals so that the network device performs the method as described in the second aspect.

[0010] A seventh aspect provides an apparatus including a processor for calling a program from a memory to cause the apparatus to perform the method as described in any one of the first or second aspects.

[0011] Eighthly, a chip is provided, including a processor for calling a program from memory to cause a device having the chip mounted to perform the method as described in the first or second aspect.

[0012] Ninth aspect, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

[0013] A tenth aspect provides a computer program product, including a program that causes a computer to perform the method as described in the first or second aspect.

[0014] Eleventhly, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0015] In this embodiment, the terminal device sends first information to the network device to request the establishment of a data radio bearer. The first information carries part or all of the following information: the task type that triggered the terminal device to request the establishment of the data radio bearer, the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet, the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet, and the amount of data that the terminal device expects to send. This assists the network device in establishing a suitable data radio bearer for the terminal device, expands the types of services that can be transmitted through the data radio bearer, and enables the terminal device to transmit corresponding types of data services through a suitable data radio bearer. Attached Figure Description

[0016] Figure 1 is a system architecture example diagram of a wireless communication system applicable to embodiments of this application.

[0017] Figure 2 is a flowchart illustrating the wireless communication method according to an embodiment of this application.

[0018] Figure 3 is a schematic diagram of the structure of the terminal device according to an embodiment of this application.

[0019] Figure 4 is a schematic diagram of the structure of a network device according to an embodiment of this application.

[0020] Figure 5 is a schematic diagram of a communication apparatus according to an embodiment of this application. Detailed Implementation

[0021] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0022] Wireless communication system

[0023] Figure 1 is an example diagram of the system architecture of a wireless communication system 100 to which embodiments of this application can be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network, such as a wireless network, through the network device 110. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity; this embodiment of the application does not limit this.

[0024] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5G) systems, new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as sixth generation mobile communication systems, satellite communication systems, etc.

[0025] In this application embodiment, the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user apparatus. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, in-vehicle equipment, etc. Terminal devices can also be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes. Optionally, terminal devices can act as base stations. For example, a terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) systems. For instance, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0026] In this embodiment, the network device can be a device used for communicating with a terminal device. The network device can be an access network device or a wireless access network device. For example, the network device can be a base station. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), femtocell, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), centralized unit-control plane (CU-CP), centralized unit-user plane (CU-UP), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or device. A base station can also be a mobile switching center, or a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device performing base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0027] Furthermore, base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0028] Network equipment may also include core network equipment. Core network equipment includes, but is not limited to, location management function (LMF) network elements, network slice selection function (NSSF) network elements, authentication server function (AUSF) network elements, unified data management (UDM) network elements, access and mobility management function (AMF) network elements, session management function (SMF) network elements, policy control function (PCF) network elements, user plane function (UPF) network elements, sensing function (SF) network elements, network data analytics function (NWDAF) network elements, and AI function management entities.

[0029] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0030] It should be understood that all or part of the functions of the communication device in the embodiments of this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform such as a cloud platform.

[0031] With the gradual application of AI technology in communication systems, the types of data transmission services in these systems are undergoing significant changes. This has expanded from single application-layer data transmission services to include both application-layer data transmission services and data transmission services within the communication system itself, such as AI model transmission tasks and model training dataset transmission tasks. The starting and ending points of these data transmission services are highly flexible. For example, it could be from the access stratum (AS) layer of the terminal device to the access network device, from the AS layer of the terminal device to the core network device, or from the non-access stratum (NAS) layer of the terminal device to the core network device. If air interface resources can only be established by the core network device triggering the access network device to establish a data radio bearer, the air interface resource establishment latency is significant (for example, data transmission services from the AS layer of the terminal device to the access network device need to first bypass the core network device to establish a session before informing the access network device to establish air interface radio resources). On the other hand, relying solely on the core network device to provide resource establishment requests to the access network device cannot flexibly meet the actual resource establishment needs of the terminal device. On the other hand, from the perspective of upgrading the service requirements of terminal devices, relying entirely on core network equipment to provide resources to access network equipment to establish service requirements is not conducive to the expansion of new data transmission services by terminal devices. This is because terminal devices cannot guarantee that the core network equipment has made corresponding technical upgrades to support each new data transmission service. The way the core network equipment triggers resource establishment will greatly limit the realization of new data transmission services by terminal devices. Therefore, in this embodiment, the establishment of data radio bearers is allowed to be triggered by the terminal device.

[0032] In this embodiment, the terminal device sends first information to the network device to request the establishment of a data radio bearer. The first information carries part or all of the following information: the task type that triggered the terminal device to request the establishment of the data radio bearer, the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet, the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet, and the amount of data that the terminal device expects to send. This assists the network device in establishing a suitable data radio bearer for the terminal device, expands the types of services that can be transmitted through the data radio bearer, and enables the terminal device to transmit corresponding types of data services through a suitable data radio bearer.

[0033] The models mentioned below include, for example, AI models or machine learning (ML) models.

[0034] The embodiments of this application will be described in detail below with reference to Figure 2.

[0035] Figure 2 is a schematic flowchart of a wireless communication method provided in an embodiment of this application. The method 200 shown in Figure 2 can be executed by a terminal device and a network device. The terminal device can be, for example, the terminal device 120 shown in Figure 1, and the network device can be, for example, the network device 110 shown in Figure 1.

[0036] Referring to Figure 2, in step 210, the terminal device sends the first information to the network device.

[0037] Accordingly, in step 220, the network device receives the first information sent by the terminal device.

[0038] The first information is used to request the establishment of a radio bearer, such as a data radio bearer. Since the first information is used to request resources for establishing the radio bearer, it will be referred to hereinafter as a radio bearer resource establishment request. In some implementations, the first information may include one or more of a first indication information, a second indication information, a third indication information, and a fourth indication information. The first indication information indicates the task type that triggers the terminal device to request the establishment of a data radio bearer; the second indication information indicates the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet; the third indication information indicates the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet; and the fourth indication information indicates the amount of data that the terminal device expects to send.

[0039] As an example, the first information may include first instruction information, second instruction information, third instruction information, or fourth instruction information. Where the first information includes only the first instruction information, it can also be referred to as the first instruction information; where the first information includes only the second instruction information, it can also be referred to as the second instruction information; where the first information includes only the third instruction information, it can also be referred to as the third instruction information; and where the first information includes only the fourth instruction information, it can also be referred to as the fourth instruction information. For example, the first information may include first instruction information and second instruction information, or it may include first instruction information and third instruction information, or it may include first instruction information and fourth instruction information, or it may include second instruction information and third instruction information, or it may include second instruction information and fourth instruction information, or it may include second instruction information, third instruction information, and fourth instruction information. For example, the first information may include first instruction information, second instruction information, and third instruction information, or it may include first instruction information, second instruction information, and fourth instruction information, or it may include first instruction information, third instruction information, and fourth instruction information, or it may include second instruction information, third instruction information, and fourth instruction information. For example, the first information may include first instruction information, second instruction information, third instruction information, and fourth instruction information.

[0040] In some implementations, the first information may further include fifth and / or sixth indication information. The fifth indication information indicates the encryption level or encryption algorithm that the terminal device expects to use in establishing the data radio bearer; the sixth indication information indicates the number or minimum number of data radio bearers that the terminal device expects to establish.

[0041] As an example, the first information may include first instruction information and fifth instruction information, or second instruction information and fifth instruction information, or third instruction information and fifth instruction information, or fourth instruction information and fifth instruction information; for example, the first information may include first instruction information, second instruction information and fifth instruction information, or first instruction information, third instruction information and fifth instruction information, or first instruction information, fourth instruction information and fifth instruction information, or second instruction information, third instruction information and fifth instruction information, or second instruction information, fourth instruction information and fifth instruction information, or third instruction information, fourth instruction information and fifth instruction information; for example, the first information may include first instruction information, second instruction information, third instruction information and fifth instruction information, or first instruction information, second instruction information, fourth instruction information and fifth instruction information, or first instruction information, third instruction information, fourth instruction information and fifth instruction information, or second instruction information, third instruction information, fourth instruction information and fifth instruction information; for example, the first information may include first instruction information, second instruction information, third instruction information, fourth instruction information and fifth instruction information.

[0042] For example, the first information may include first instruction information and sixth instruction information, or second instruction information and sixth instruction information, or third instruction information and sixth instruction information, or fourth instruction information and sixth instruction information; for example, the first information may include first instruction information, second instruction information and sixth instruction information, or first instruction information, third instruction information and sixth instruction information, or first instruction information, fourth instruction information and sixth instruction information, or second instruction information, third instruction information and sixth instruction information, or second instruction information, fourth instruction information and sixth instruction information, or third instruction information, fourth instruction information and sixth instruction information; for example, the first information may include first instruction information, second instruction information, third instruction information and sixth instruction information, or first instruction information, second instruction information, fourth instruction information and sixth instruction information, or first instruction information, third instruction information, fourth instruction information and sixth instruction information, or second instruction information, third instruction information, fourth instruction information and sixth instruction information; for example, the first information includes first instruction information, second instruction information, third instruction information, fourth instruction information and sixth instruction information.

[0043] For example, the first information may include first instruction information, fifth instruction information, and sixth instruction information, or it may include second instruction information, fifth instruction information, and sixth instruction information, or it may include third instruction information, fifth instruction information, and sixth instruction information, or it may include fourth instruction information, fifth instruction information, and sixth instruction information; or it may include first instruction information, second instruction information, fifth instruction information, and sixth instruction information, or it may include first instruction information, third instruction information, fifth instruction information, and sixth instruction information, or it may include second instruction information, fourth instruction information, fifth instruction information, and sixth instruction information, or it may include second instruction information, fourth instruction information, and sixth instruction information. The fifth and sixth instruction information may include the third, fourth, fifth, and sixth instruction information; for example, the first information may include the first, second, third, fifth, and sixth instruction information, or may include the first, second, fourth, fifth, and sixth instruction information, or may include the first, third, fourth, fifth, and sixth instruction information, or may include the second, third, fourth, fifth, and sixth instruction information; for example, the first information may include the first, second, third, fourth, fifth, and sixth instruction information.

[0044] The first information includes the first instruction information, which has the following beneficial effects: The first instruction information can help the network device clarify the reason why the terminal device requests to establish a data radio bearer, that is, what kind of task triggered the terminal device's radio bearer establishment request. The network device can decide whether to grant the terminal device's request based on the task type indicated by the first instruction information, and, on the premise of granting the terminal device's request, associate the configured data radio bearer with the specific task type, so that the terminal device can clarify which task type-related data is transmitted through which data radio bearers.

[0045] The first information includes the second instruction information, which has the following beneficial effects: The second instruction information can help network devices clarify the QoS requirements of the data that the terminal device is preparing to transmit. On the one hand, it can let network devices know which types of QoS flows to configure; on the other hand, the QoS requirements can guide network devices to configure appropriate Layer 2 parameters. For example, the QoS requirements can guide network devices to configure parameters such as the data drop duration used by the PDCP protocol layer, the data transmission mode used by the RLC protocol layer, and the reassembly timer duration used by the RLC protocol layer, so that the Layer 2 parameter settings corresponding to the data radio bearer match the QoS requirements of the terminal device.

[0046] The first information includes the third instruction information, which has the following beneficial effects: The third instruction information can help network devices clarify the RLC transmission mode corresponding to the data radio bearer required by the terminal device, and avoid the scenario where the RLC transmission mode corresponding to the data radio bearer configured by the network device is different from the RLC transmission mode actually required by the terminal device, resulting in a decrease in data transmission quality.

[0047] The first information includes the fourth instruction information, which has the following beneficial effects: The fourth instruction information can help network devices determine the amount of data that the terminal device intends to transmit. On the one hand, based on the fourth instruction information and the current resource congestion status of the network device, the network device can decide whether to accept the resource establishment request from the terminal device; on the other hand, based on the fourth instruction information, the network device can also determine how many data radio bearers need to be configured to transmit data in parallel to meet the QoS requirements of the terminal device.

[0048] The first information, including the fifth instruction information, has the following beneficial effects: The fifth instruction information can assist network devices in clarifying the encryption level or encryption algorithm that the terminal device expects to use when requesting to establish a data radio bearer, thereby considering the personalized needs of the terminal device when configuring the data radio bearer. On the one hand, the fifth instruction information increases the terminal device's initiative in establishing radio resources; on the other hand, the personalized encryption level or encryption algorithm requirements further strengthen the confidentiality of transmitted data, because the key at the granularity of data transmission tasks will not lead to security threats to other data transmission tasks due to the cracking of the key for one data transmission task, and the confidentiality between different data transmission tasks is relatively independent.

[0049] The first information includes the sixth instruction information, which has the following beneficial effects: the sixth instruction information can help network devices clarify how much data wireless bearer the terminal device expects to establish, and the sixth instruction information can simplify the implementation of network devices.

[0050] The beneficial effects of the different implementation methods of the first information described above are a combination of the beneficial effects of the aforementioned instruction information, and will not be elaborated on one by one here.

[0051] The first, second, third, fourth, fifth, and sixth instruction messages are described in detail below.

[0052] First instruction information

[0053] The first indication information is used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer. In one implementation, the first indication information is identification information (e.g., an ID identifier) ​​associated with the task type. For example, identifier '0000' is associated with a model training dataset transmission task, '0001' is associated with a model transmission task, etc. By using the value of the first indication information, the access network device can confirm the task type involved in this request, which has good scalability. In another implementation, the first indication information is implemented through a selection function (choice{} function), where each value of the choice{} function corresponds to a different task type. In yet another implementation, the first indication information is implemented through enumerated parameters, where each element of the enumerated parameters corresponds to a different task type. In yet another implementation, the task type indicated by the first indication information is implicitly indicated by the predefined position of the parameter carrying the first information in the protocol. For example, the parameter carrying the first information is specifically defined for model transmission tasks; if the parameter carrying the first information appears in the agreed position, the access network device can confirm that the task type involved in this request is a model transmission task, which is more cost-effective.

[0054] In some implementations, the task type indicated by the first indication information may include a model training dataset transfer task and / or a measurement-related data transfer task.

[0055] Model training datasets are used to train AI models. For example, for beam management functions, terminal devices can collect beam-related measurement results over a period of time (e.g., beam-related measurement results include cell identification information, beam identification information, and one or more of the beam measurement results). The beam measurement results over a period of time can be called model training datasets, which are used to train AI models for beam management functions.

[0056] Measurement-related data typically refers to measurement data acquired by terminal devices through measurement reference signals configured on network devices. Common types of measurement reference signals include synchronization signal block / physical broadcast channel block (SS / PBCH block, SSB), channel state information reference signal (CSI-RS), phase reference symbol (PRS), sensing reference signals, and reference signals for ambient IoT devices. Measurement-related data includes cell-level measurement-related data and / or beam-level measurement-related data. Cell-level measurement-related data includes cell identification information and / or cell measurement results, while beam-level measurement-related data includes one or more of the following: cell identification information, beam identification information, and beam measurement results.

[0057] The measurement quantities corresponding to the above measurement results include one or more of the following: reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), received signal strength indication (RSSI), and channel impulse response (CIR).

[0058] The benefits of transmitting model training datasets wirelessly are twofold: First, model training datasets typically record raw sample data, whose characteristics are closer to the actual communication environments experienced by terminal devices. Therefore, transmitting model training datasets allows terminal devices to train models that are closer to reality using raw sample data, and the performance of the models is more likely to meet the needs of actual communication environments. Second, most data types involved in model training datasets (e.g., RSRP measurements) do not have high privacy protection requirements (except for information such as the location of the terminal device). Directly transmitting model training datasets is less likely to leak the trade secrets of the data sender.

[0059] The advantages of transmitting measurement-related data over wireless bearers are twofold: First, the measurement data obtained by a single device (e.g., a terminal device or a network device) through the measurement process is very limited, but the optimization of measurement-related algorithms or the training of measurement-related models generally require a large amount of measurement data. Transmitting measurement-related data over wireless bearers enables measurement data sharing among multiple devices, improving the efficiency of a single device in acquiring measurement-related data. Second, because the data source is relatively random, the generalization of measurement-related data is better (or, in other words, the quality of measurement-related data is higher), making it easier to obtain high-quality optimization algorithms or high-performance models using such data.

[0060] In some other implementations, the task type indicated by the first instruction information may also include one or more of the following: model transmission task; model parameter transmission task; terminal device capability information transmission task.

[0061] The benefits of transmitting models wirelessly are as follows: If the data receiver uses the received model to perform model training tasks, transmitting the model wirelessly allows the model trainer to train the required model more quickly; if the data receiver uses the received model to perform specific communication functions, it saves the data receiver the work of training that type of model itself. Especially for terminal devices with limited computing power, obtaining the model from the network device is more in line with business reality than training the model itself.

[0062] The beneficial effects of transmitting model parameters over wireless bearers are as follows: If the data receiver of the model parameters uses the received model parameters to perform model training tasks, transmitting model parameters over wireless bearers allows the model trainer to train the required model more quickly; if the data receiver of the model parameters uses the received model parameters to replace existing model parameters, transmitting model parameters over wireless bearers allows the data receiver to quickly update its deployed relevant models, thereby regaining communication gains through the model in a shorter time.

[0063] The beneficial effect of transmitting terminal equipment capability information via data wireless bearer is that it can avoid congestion of signaling wireless bearer when the amount of data contained in the capability information is large.

[0064] As examples, task types include model training dataset transfer tasks; task types include measurement-related data transfer tasks; task types include model transfer tasks; task types include model parameter transfer tasks; task types include terminal device capability information transfer tasks; task types include both model training dataset transfer tasks and measurement-related data transfer tasks; task types include both model training dataset transfer tasks and model transfer tasks; task types include both model training dataset transfer tasks and model parameter transfer tasks; task types include both model training dataset transfer tasks and terminal device capability information transfer tasks; task types include measurement-related data transfer tasks. Data transmission tasks and model transmission tasks; for example, task types include measurement-related data transmission tasks and model parameter transmission tasks; for example, task types include measurement-related data transmission tasks and terminal device capability information transmission tasks; for example, task types include model transmission tasks and model parameter transmission tasks; for example, task types include model transmission tasks and terminal device capability information transmission tasks; for example, task types include model parameter transmission tasks and terminal device capability information transmission tasks; for example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, and model transmission tasks; for example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, and model parameter transmission tasks. For example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, and terminal device capability information transmission tasks; for example, task types include model training dataset transmission tasks, model transmission tasks, and model parameter transmission tasks; for example, task types include model training dataset transmission tasks, model transmission tasks, and terminal device capability information transmission tasks; for example, task types include model training dataset transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks; for example, task types include measurement-related data transmission tasks, model transmission tasks, and model parameter transmission tasks; for example, task types include measurement-related data transmission tasks, model transmission tasks, and terminal device capability information transmission tasks. Information transmission tasks; for example, task types include measurement-related data transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks; for example, task types include model transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks; for example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, model transmission tasks, and model parameter transmission tasks; for example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, model transmission tasks, and terminal device capability information transmission tasks; for example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks.For example, task types include model training dataset transmission tasks, model transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks; for example, task types include measurement-related data transmission tasks, model transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks; for example, task types include model training dataset transmission tasks, measurement-related data transmission tasks, model transmission tasks, model parameter transmission tasks, and terminal device capability information transmission tasks.

[0065] In some implementations, the task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type being transmitted. Here, the data type refers to the category of data. However, data category alone cannot effectively distinguish the associated functional characteristics of the data. For example, the data category could be model training dataset, measurement-related data, model-related data, model parameter-related data, or terminal device capability information, etc. Different functional characteristics all contain data of the above categories, making this implementation more versatile. In other implementations, the task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to both the data type being transmitted and the associated functional characteristics. This method indicates both the data category and the specific functional characteristics associated with the data, providing greater specificity and more comprehensive information for the network device, thus facilitating its decision-making.

[0066] This functional feature may include one or more of the following: channel state information (CSI) compression feedback function; beam management function; positioning function; radio resource management (RRM) measurement function; CSI prediction function; RRM event prediction function; sensing function; beam failure detection (BFD) function; radio link failure (RLF) function; channel estimation function; environmental IoT function; and low-layer / L2-triggered mobility (LTM) function.

[0067] As an example, in the first definition method, the task type indicated by the first indication information is defined according to the data type being transmitted. In this case, the task type indicated by the first indication information does not distinguish the functional characteristics associated with the data type being transmitted. For example, the range of values ​​for the task type that triggers the terminal device to request the establishment of a data wireless bearer may include one or more of the following tasks: model training dataset transmission task, model transmission task, model parameter transmission task, terminal device capability information transmission task, and measurement-related data transmission task.

[0068] As an example, in the second definition method, the task type is defined according to the data type being transmitted and the functional characteristics associated with that data type. In this case, the task type definition already considers the functional characteristics associated with the data type being transmitted. The data types and functional characteristics associated with different task types are agreed upon in the protocol, i.e., agreed upon through the protocol's default method. For example, the range of values ​​for the task type that triggers the terminal device to request the establishment of a data radio bearer can include one or more of the following tasks: Model training dataset transmission task for CSI compressed feedback function; Model transmission task for CSI compressed feedback function; Model parameter transmission task for CSI compressed feedback function; Model training dataset transmission task for beam management function; Model transmission task for beam management function; Model parameter transmission task for beam management function; Model training dataset transmission task for positioning function; Model transmission task for positioning function; Model parameter transmission task for positioning function; Model training dataset transmission task for RRM measurement function; Model transmission task for RRM measurement function; Model parameter transmission task for RRM measurement function; Model training dataset transmission task for CSI prediction function; Model transmission task for CSI prediction function; Model training dataset transmission task for CSI prediction function; Model transmission task for CSI... The tasks include: transmitting model parameters for prediction functions; transmitting model training datasets for RRM event prediction functions; transmitting model parameters for RRM event prediction functions; transmitting model training datasets for sensing functions; transmitting model parameters for sensing functions; transmitting model training datasets for BFD functions; transmitting model parameters for beam failure detection functions; transmitting model training datasets for RLF functions; transmitting model parameters for wireless link failure functions; transmitting model training datasets for channel estimation functions; transmitting model parameters for channel estimation functions; or transmitting capability information for terminal devices.

[0069] When a terminal device requests the establishment of a data radio bearer from a network device, the first indication information can help the network device determine the type and urgency of the data transmission demand, thereby deciding whether to accept the terminal device's resource establishment request, and if so, what kind of data radio resources to establish for the terminal device.

[0070] Second instruction information

[0071] The second instruction information is used to indicate the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet.

[0072] Because the importance of the transmitted data types varies, network devices may use the QoS requirements provided by the terminal devices as the basis for configuring different modes of data radio bearers. For example, if the terminal device expects the transmitted data type to be of low importance, the network device may configure the terminal device in unacknowledged mode (UM) for the data radio bearer (i.e., the RLC protocol layer corresponding to the established data radio bearer uses unacknowledged mode for communication); if the terminal device expects the transmitted data type to be of high importance, the network device may configure the terminal device in acknowledged mode (AM) for the data radio bearer (i.e., the RLC protocol layer corresponding to the established data radio bearer uses acknowledged mode for communication).

[0073] The second indication information may indicate one or more QoS flow requirements. For example, the QoS flow requirements indicated by the second indication information may include multiple QoS flows that are related, and these related QoS flows expect to be associated with the same data radio bearer. Another example is that the QoS flow requirements indicated by the second indication information may include multiple QoS flows, and these multiple QoS flows are not associated with each other.

[0074] As an example, in the first scenario, where the QoS flows indicated by the second indication information are not further classified or associated, the network device can autonomously decide which QoS flows are associated with the same data radio bearer based on one or more QoS flow requirements provided by the terminal device through the second indication information. That is, the further classification or association between the QoS flows required by the terminal device is determined by the implementation of the network device. Therefore, the implementation is simpler for the terminal device, while the implementation of the network device offers greater flexibility. For instance, suppose the second indication information provided by the terminal device includes QoS flows 1, 2, 3, 4, and 5. The network device, based on its own implementation, determines to establish two data radio bearers for the terminal device: data radio bearer 1 and data radio bearer 2. Data radio bearer 1 is associated with QoS flows 1, 2, and 3, while data radio bearer 2 is associated with QoS flows 4 and 5.

[0075] As an example, in the second case, the QoS flows indicated by the second indication information are further classified or associated. In this case, the terminal device can use the second indication information to indicate which QoS flows need to be classified into the same category or which QoS flows need to be associated together. QoS flows classified into the same category or associated together need to be associated with the same data radio bearer. Therefore, the terminal device has a high degree of autonomy and can customize the data radio bearer establishment requirements according to the needs of the terminal device. This effectively avoids the scenario of establishing a data radio bearer that does not meet the needs of the terminal device due to the incorrect implementation of the network device, while retaining a certain degree of flexibility in the implementation of the network device. Suppose that the second indication information provided by the terminal device includes QoS flow 1, QoS flow 2, QoS flow 3, QoS flow 4, QoS flow 5, and QoS flow 6. The terminal device further indicates that QoS flow 1 and QoS flow 2 are associated together, QoS flow 3 and QoS flow 4 are associated together, and QoS flow 5 and QoS flow 6 are associated together. Based on the terminal device's requirements and its own implementation, the network device determines to establish two data radio bearers for the terminal device, namely data radio bearer 1 and data radio bearer 2. Data radio bearer 1 is associated with QoS flow 1, QoS flow 2, QoS flow 3, and QoS flow 4, and data radio bearer 2 is associated with QoS flow 5 and QoS flow 6. In this way, the requirements of the terminal device are met, while retaining a certain degree of flexibility in the implementation of the network device.

[0076] Third instruction information

[0077] The third indication information is used to indicate the RLC mode requirements that the data radio bearer requested by the terminal device must meet. Each value of the third indication information can be associated with a specific RLC mode. An established data radio bearer typically corresponds to one RLC mode. When configuring a data radio bearer, the network device informs the terminal device of the RLC mode to use during the configuration process. Generally, there are three RLC modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). In some communication systems, if the functions of the PDCP protocol layer and the RLC protocol layer are merged (for example, the merged protocol layer is called the first protocol layer), the third indication information is used to indicate the RLC mode requirements of the first protocol layer that the requested data radio bearer must meet.

[0078] As an example, the third indication information includes 1 bit. In this case, the value of the third indication information is the first value (e.g., the first value is '1') to indicate AM mode; the value of the third indication information is the second value (e.g., the second value is '0') to indicate UM mode or non-AM mode. As another example, the third indication information includes 2 bits. In this case, the value of the third indication information is the first value (e.g., the first value is '11') to indicate AM mode; the value of the third indication information is the second value (e.g., the second value is '10') to indicate UM mode; the value of the third indication information is the third value (e.g., the third value is '01') to indicate TM mode; and the value of the third indication information is the fourth value (e.g., the fourth value is '00') and is temporarily reserved.

[0079] When a terminal device requests the establishment of a data radio bearer from a network device, it can send a third instruction message to the network device to provide information on the required RLC mode. This can help the network device to accurately configure the data radio bearer and avoid scenarios where the network device establishes a data radio bearer that does not meet the requirements of the terminal device due to incorrect implementation.

[0080] Fourth instruction information

[0081] The fourth indication information is used to indicate the amount of data that the terminal device expects to send.

[0082] In one implementation, the fourth indication information can indicate the number of bytes of data that the terminal device expects to send, thus making the data volume information indicated by the fourth indication information more accurate. In another implementation, the fourth indication information can indicate the quantity level corresponding to the data that the terminal device expects to send. For example, each quantity level can correspond to a byte number range, that is, one value of the fourth indication information is associated with a byte number range, and the protocol can specify which byte number range each value of the fourth indication information is associated with. As an example, the fourth indication information occupies 2 bits, where the value '00' indicates a byte number range of less than 10M bytes, the value '01' indicates a byte number range of greater than 10M bytes and less than 100M bytes, the value '10' indicates a byte number range of greater than 100M bytes and less than 1G bytes, and the value '11' indicates a byte number range of greater than 1G bytes.

[0083] When a terminal device requests the establishment of a data radio bearer from a network device, it can send a fourth instruction message to the network device to provide information on the amount of data to be transmitted. This can help the network device to reasonably configure the number of data radio bearers and ensure the throughput and latency requirements of data transmission.

[0084] Fifth instruction information

[0085] The fifth instruction information is used to indicate the encryption level and / or encryption algorithm that the terminal device expects to use for the data radio bearer it requests to establish.

[0086] An established data radio bearer typically involves a PDCP protocol layer configuration. Encryption and integrity protection are among the main functions of the PDCP protocol layer. To further enhance the confidentiality of data transmission, the terminal device can further specify the encryption level or algorithm to be used by the requested data radio bearer through the fifth indication information during the request process. In one implementation, the fifth indication information indicates the encryption level required for the data radio bearer. Different encryption levels correspond to different encryption algorithms, and the network device can select an appropriate PDCP protocol layer encryption algorithm based on the encryption level information provided by the terminal device. This implementation provides some flexibility for the network device. In another implementation, the fifth indication information indicates the encryption algorithm to be used by the data radio bearer. This implementation better meets the needs of the terminal device.

[0087] Sixth instruction information

[0088] The sixth instruction information is used to indicate the number or minimum number of data radio bearers that the terminal device expects to establish. When the terminal device requests the establishment of data radio bearers from the network device, sending the sixth instruction information to indicate the number or minimum number of data radio bearers expected to be established helps the network device to clearly understand the resource establishment requirements of the terminal device.

[0089] The above describes the possible content carried in the first message sent by the terminal device when requesting the establishment of a data radio bearer. The following describes in detail the timing of the terminal device sending the first message.

[0090] Timing of sending the first message

[0091] In some implementations, the terminal device determines when to send the first information based on the implementation. This approach offers the greatest flexibility to the terminal device and is conducive to the flexible development of terminal device products.

[0092] In some implementations, in step 210, in response to the fulfillment of the first event, the terminal device triggers the action of sending the first information to the network device. That is, the first information is event-triggered. Introducing the first event can avoid scenarios where the terminal device frequently triggers the action of sending the first information, resulting in high air interface resource overhead.

[0093] In some implementations, the first event may include one or more of the following: the task type that triggers the sending of the first information belongs to the range of the first task type; the amount of data corresponding to the data that the terminal device expects to send is greater than the first threshold; the terminal device determines that it is not in a low power state.

[0094] The value of the first threshold is either predefined in the protocol or configured by the network device for the terminal device. The terminal device determines that it is not in a low-power state to ensure it has sufficient power to transmit data, avoiding requests to establish a data wireless bearer in low-power scenarios, where data transmission might be interrupted due to the terminal device running out of power midway through the transmission. The first task type range is either predefined in the protocol or configured by the network device for the terminal device.

[0095] In one implementation, the task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type being transmitted. In this case, the task type may not distinguish between the functional characteristics associated with the data type being transmitted. For example, the first task type may include one or more of the following: model training dataset transmission task, model transmission task, model parameter transmission task, terminal device capability information transmission task, or measurement-related data transmission task.

[0096] In another implementation, the task type that triggers the terminal device to request the establishment of a data radio bearer is defined according to the data type being transmitted and the functional characteristics associated with that data type. That is, the task type distinguishes between the data type and the corresponding functional characteristics. In this case, the first task type range may include one or more of the following: a model training dataset transmission task for CSI compressed feedback function, a model transmission task for CSI compressed feedback function, a model parameter transmission task for CSI compressed feedback function, a model training dataset transmission task for beam management function, a model transmission task for beam management function, a model parameter transmission task for beam management function, a model training dataset transmission task for positioning function, a model transmission task for positioning function, a model parameter transmission task for positioning function, a model training dataset transmission task for RRM measurement function, a model transmission task for RRM measurement function, a model parameter transmission task for RRM measurement function, a model training dataset transmission task for CSI prediction function, a model transmission task for CSI prediction function, and a model transmission task for CSI prediction function. The tasks include: transmitting model parameters for the measurement function; transmitting model training datasets for the RRM event prediction function; transmitting model training datasets for the sensing function; transmitting model parameters for the sensing function; transmitting model training datasets for the BFD function; transmitting model training datasets for the BFD function; transmitting model parameters for the BFD function; transmitting model training datasets for the RLF function; transmitting model parameters for the RLF function; transmitting model training datasets for the channel estimation function; transmitting model parameters for the channel estimation function; and transmitting capability information for the terminal device.

[0097] Furthermore, the terminal device may trigger the transmission of the first information for one or more reasons. In one implementation, the first event can be a single event, meaning the reason for triggering the transmission of the first information is a specific cause. For example, the first event could be that the task type triggering the transmission of the first information belongs to a first task type range, or the first event could be that the amount of data corresponding to the data the terminal device expects to send is greater than a first threshold, or the first event could be that the terminal device determines it is not in a low-battery state. In another implementation, the first event can be a composite event, meaning the reason for triggering the transmission of the first information is a combination of multiple reasons. For example, the first event could be that the task type triggering the transmission of the first information belongs to a first task type range and the amount of data corresponding to the data the terminal device expects to send is greater than a first threshold; or the first event could be that the task type triggering the transmission of the first information belongs to a first task type range and the terminal device determines it is not in a low-battery state; or the first event could be that the amount of data corresponding to the data the terminal device expects to send is greater than a first threshold and the terminal device determines it is not in a low-battery state; or the first event could be that the task type triggering the transmission of the first information belongs to a first task type range and the amount of data corresponding to the data the terminal device expects to send is greater than a first threshold and the terminal device determines it is not in a low-battery state.

[0098] The first event being the task type that triggers the sending of the first information has the following benefits: This type of first event can effectively prevent the terminal device from triggering the establishment of a data radio bearer due to a task type that the network device does not care about, thus avoiding the waste of air interface signaling. Generally speaking, requests to establish a data radio bearer triggered by a task type that the network device does not care about will always be rejected by the network device. Providing the first task type range can avoid invalid requests from the terminal device.

[0099] The first event is when the amount of data the terminal device expects to send exceeds a first threshold. The beneficial effect of this type of first event is that the terminal device can effectively avoid frequently triggering requests to establish a data radio bearer. The terminal device will not trigger a resource establishment request because of a small amount of data. This is because the terminal device will always trigger the request after the amount of data to be transmitted has accumulated to a certain level, which helps to reduce the air interface overhead caused by the resource establishment request triggered by the terminal device.

[0100] The first benefit of the terminal device determining that it is not in a low-battery state is that it ensures that the terminal device has enough power to transmit data, avoiding the need to request the establishment of a data wireless bearer in scenarios with low power, which may cause the transmission to be interrupted in the middle of the data transmission due to the terminal device running out of power.

[0101] The beneficial effects of the different implementation methods of the composite events described above are combinations of the beneficial effects of the individual events mentioned above, and will not be elaborated on one by one here.

[0102] In some implementations, the terminal device determines not to send the first information during the first timer's execution. That is, during the first timer's execution, the terminal device is not allowed to trigger a request to establish a data radio bearer, i.e., it is not allowed to send the first information. The starting condition for the first timer is, for example, triggering the transmission of the first information; the stopping condition for the first timer is, for example, a change in the value of the parameter used to configure the timing duration of the first timer or receiving a reconfiguration message from the network device, such as the network device reconfiguring the timing duration of the first timer for the terminal device. As an example, the terminal device starts the first timer when sending the first information and will not request to establish a data radio bearer again during the first timer's execution (i.e., before the first timer expires) (i.e., it will not send the first information again). Another example is that the terminal device starts the first timer when sending the first information and stops the first timer's execution when the network device reconfigures the timing duration of the first timer. After the first timer stops running, the timer restriction condition is lifted, and the terminal device can request to establish a data radio bearer again (i.e., send the first information again) when other conditions are met (e.g., the aforementioned first event is met).

[0103] The duration of the first timer can be determined based on a default method (or a method agreed upon by the protocol); or the duration of the first timer can be configured by the network device for the terminal device.

[0104] The first timer and the first event can also be implemented in combination. For example, if a mechanism involving both the first event and the first timer is introduced, the terminal device will not trigger a request to establish a data radio bearer, i.e., it will not send the first information, even if the first event is satisfied during the execution of the first timer. In other words, the terminal device can only trigger a request to establish a data radio bearer, i.e., send the first information, when the first timer is not running and the first event is satisfied. This approach can further prevent the terminal device from frequently triggering requests to establish a data radio bearer.

[0105] Rejection of resource creation request

[0106] In some implementations, method 200 may further include the terminal device receiving second information sent by the network device; correspondingly, the network device sends the second information to the terminal device. The second information is used to reject the request to establish a data radio bearer triggered by the first information.

[0107] In some implementations, the second information includes one or more of the seventh, eighth, and ninth indication information. The seventh indication information indicates the type of task being rejected; the eighth indication information indicates the reason for rejection; and the ninth indication information indicates the duration of rejection, which is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer. As an example, the second information may include the seventh, eighth, or ninth indication information; or, for example, the second information may include the seventh and eighth indication information, or the seventh and ninth indication information, or the eighth and ninth indication information; or, for example, the second information may include the seventh, eighth, and ninth indication information.

[0108] The reasons for rejection may include one or more of the following: the network device is in a congested state; the network device does not need the data corresponding to the task type that triggered the terminal device to request the establishment of a data radio bearer; the network device cannot meet the requirements of the data radio bearer requested in the first information. Specifically, if the network device is currently in a congested state, it may reject the resource establishment request initiated by the terminal device through the first information. Alternatively, if the data corresponding to the task type that triggered the terminal device to request the establishment of a data radio bearer (i.e., the task type indicated in the first information) is not required by the current network device, the network device may also reject the resource establishment request initiated by the terminal device. In addition, if the first information indicates multiple resource establishment-related requirements, and the network device may not be able to meet all the requirements in the first information, the network device may reject the resource establishment request initiated by the terminal device.

[0109] As an example, the rejection reason may include the network device being in a congested state, the network device not needing the data corresponding to the task type for which the terminal device requests the establishment of a data radio bearer, or the network device being unable to meet the requirements of the first information request to establish a data radio bearer; for example, the rejection reason may include the network device being in a congested state and the network device not needing the data corresponding to the task type for which the terminal device requests the establishment of a data radio bearer; for example, the rejection reason may include the network device being in a congested state and the network device being unable to meet the requirements of the first information request to establish a data radio bearer; for example, the rejection reason may include the network device not needing the data corresponding to the task type for which the terminal device requests the establishment of a data radio bearer, and the network device being unable to meet the requirements of the first information request to establish a data radio bearer; for example, the rejection reason may include the network device being in a congested state, the network device not needing the data corresponding to the task type for which the terminal device requests the establishment of a data radio bearer, and the network device being unable to meet the requirements of the first information request to establish a data radio bearer.

[0110] The seventh indication information is used to indicate the type of task to be rejected. In one implementation, the seventh indication information is an identifier (e.g., an ID) associated with the task type. For example, '0000' is associated with a model training dataset transmission task, '0001' with a model transmission task, etc. By determining the value of the seventh indication information, the terminal device can confirm the task type involved in the rejection process, offering good scalability. In another implementation, the seventh indication information is implemented using the `choice{}` function, where each value corresponds to a different task type. In yet another implementation, the seventh indication information is implemented using enumerated parameters, where each element corresponds to a different task type. In yet another implementation, the task type indicated by the seventh indication information is implicitly indicated by the predefined position of the parameter carrying the second information in the protocol. For example, the parameter carrying the second information is specifically defined for model transmission tasks; if the parameter carrying the second information appears in the agreed-upon position, the terminal device can confirm that the task type involved in the rejection process is a model transmission task, making this implementation more cost-effective.

[0111] In one implementation, the eighth indication information may not distinguish between task types, meaning it is not associated with any task type. Regardless of how many task types the information in the first indication requests for data radio bearers, if the network device intends to reject resource establishment requests initiated by a terminal device, it must reject all resource establishment requests for data radio bearers requiring these task types. This eliminates the possibility of rejecting resource establishment requests for only some task types, simplifying the complexity of network device management. In another implementation, the eighth indication information is distinct from the task type, meaning it is associated with the task type. This allows the network device to provide rejection reasons to the terminal device at the granularity of task type or task type group. The network device can reject resource establishment requests for data bearers from some task types or task type groups out of all task types initiated by the terminal device. This implementation allows the network device to partially reject resource establishment requests initiated by the terminal device, offering greater flexibility and reflecting the management independence of different task types. If the eighth indication information is associated with a task type, the associated task type is indicated by the seventh indication information.

[0112] In some scenarios, such as when the network device is congested, the network device can reject resource establishment requests initiated by the terminal device and provide the terminal device with rejection duration information (or waiting duration information) through the ninth indication information. After receiving the ninth indication information, the terminal device's behavior may include not triggering resource establishment requests for task types subject to rejection duration constraints for a first time length starting from the receipt of the ninth indication information (or the second information). The value of the first time length is indicated by the ninth indication information, and the first time length is the duration of the rejection.

[0113] In some implementations, the ninth instruction can directly indicate the value of the rejection duration; in other implementations, the ninth instruction is used to indicate the value of the intermediate parameters used to calculate the rejection duration. For example, the rejection duration is equal to a + (b * c), where parameters a and b are default values ​​agreed upon by the protocol, and the value of parameter c is indicated by the ninth instruction.

[0114] In some implementations, the ninth indication information may not be distinguished by task type, i.e., it is not associated with task type. Regardless of how many types of data radio bearer resource establishment requests the network device rejects through the second information, these rejected task types are subject to the same rejection duration constraint. That is, within the time range of the rejection duration constraint, the terminal device is not allowed to trigger resource establishment requests for task types subject to the rejection duration constraint. In this case, the value of the rejection duration is indicated by the ninth indication information or confirmed by a protocol predefined method. In this way, the implementation is simpler, and the terminal device does not need to maintain the timer corresponding to the rejection duration according to the granularity of task type or task type group. In other implementations, the ninth indication information is distinguished from the task type, that is, the ninth indication information is associated with the task type. This allows network devices to provide rejection duration information to terminal devices at the task type granularity or at the task type group granularity. In this implementation, network devices can configure different rejection durations for different task types. Within the time limit of the rejection duration associated with any task type or any task type group, the terminal device is not allowed to trigger a resource establishment request for the task type subject to the rejection duration constraint. This makes the implementation more flexible and reflects the management independence of different task types. If the ninth indication information is associated with a task type, the task type associated with the ninth indication information is indicated by the seventh indication information.

[0115] In some implementations, method 200 may further include the terminal device determining whether it can request the establishment of a data radio bearer. The terminal device will only send the aforementioned first information to the network device if it determines that it can request the establishment of a data radio bearer. For example, in one implementation, the terminal device receives a tenth indication information sent by the network device, which indicates whether the network device allows the terminal device to send the first information. The terminal device can determine whether it can request the establishment of a data radio bearer based on the value of the tenth indication information. As an example, a fifth value (e.g., a value of '1') indicates that the network device allows the terminal device to trigger the action of sending the first information; a sixth value (e.g., a value of '0') indicates that the network device does not allow the terminal device to trigger the action of sending the first information. The tenth indication information can be configured to be sent to the terminal device, for example, through a system broadcast message or dedicated signaling.

[0116] As another implementation, the terminal device can also determine whether it can request to establish a data radio bearer based on its capability information. For example, when the first capability information is the seventh value (e.g., the seventh value is '1'), it means that the terminal device has the capability to trigger the action of sending the first information; when the first capability information is the eighth value (e.g., the eighth value is '0'), it means that the terminal device does not have the capability to trigger the action of sending the first information.

[0117] In another implementation, the terminal device receives the tenth indication information sent by the network device and determines whether it can request to establish a data radio bearer based on the value of the tenth indication information and the terminal device's capability information. In this case, the terminal device can trigger the action of sending the first information only if the value of the tenth indication information indicates that the terminal device is allowed to send the first information, and the value of the terminal device's capability information also indicates that the terminal device is allowed to send the first information; otherwise, if either of these conditions is not met, the terminal device is considered not allowed to trigger the action of sending the first information.

[0118] Typically, the establishment of data radio bearers is usually for data transmission services between the application layer of a terminal device and a server. However, with the continuous expansion of data transmission services within the communication system (e.g., model transmission tasks, model training dataset transmission tasks, etc.), based on the embodiments of this application described above, the terminal device requesting the establishment of a data radio bearer can effectively expand the service applicability of air interface data radio bearers. Furthermore, the method of the terminal device requesting the establishment of a data radio bearer can assist network devices in configuring data radio bearer resources that better meet the actual needs of the terminal device, avoiding blind implementation by network devices. Simultaneously, for data transmission services between the terminal device and access network devices, the method of the terminal device requesting the establishment of a data radio bearer has lower latency.

[0119] The method embodiments of this application have been described in detail above with reference to Figures 1 and 2. The apparatus embodiments of this application will be described in detail below with reference to Figures 3 to 5. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0120] Figure 3 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The terminal device 300 shown in Figure 3 may include a transceiver unit 310. The transceiver unit 310 is used to send first information to a network device. The first information is used to request the establishment of a data radio bearer. The first information includes one or more of the following: first indication information, used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer; second indication information, used to indicate the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet; third indication information, used to indicate the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet; and fourth indication information, used to indicate the amount of data corresponding to the data that the terminal device expects to send.

[0121] In some implementations, the first information further includes: fifth indication information, used to indicate the encryption level or encryption algorithm that the terminal device expects to use for the data radio bearer it requests to establish; and / or, sixth indication information, used to indicate the number or minimum number of data radio bearers that the terminal device expects to establish.

[0122] In some implementations, the task type includes model training dataset transfer tasks and / or measurement-related data transfer tasks.

[0123] In some implementations, the task type includes one or more of the following: model transmission task; model parameter transmission task; terminal device capability information transmission task.

[0124] In some implementations, the task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type of the transmitted data, or according to the data type of the transmitted data and the functional characteristics associated with the data type of the transmitted data.

[0125] In some implementations, the functional characteristics include one or more of the following: Channel State Information (CSI) compression feedback function; beam management function; positioning function; RRM measurement function; CSI prediction function; RRM event prediction function; sensing function; BFD function; RLF function; channel estimation function; environmental IoT function; LTM function.

[0126] In some implementations, the QoS flow requirements indicated by the second indication information include multiple QoS flows that are related, and the multiple QoS flows that are related are expected to be associated with the same data radio bearer.

[0127] In some implementations, the transceiver unit 310 is specifically used to: trigger the action of sending the first information to the network device in response to the fulfillment of a first event.

[0128] In some implementations, the first event includes one or more of the following: the task type that triggers the sending of the first information belongs to the range of the first task type; the amount of data corresponding to the data that the terminal device expects to send is greater than the first threshold; the terminal device determines that it is not in a low battery state.

[0129] In some implementations, the transceiver unit 310 is further configured to: determine not to send the first information during the operation of the first timer.

[0130] In some implementations, the first timer is started when the first information is sent; and / or the first timer is stopped when the value of the parameter used to configure the timing duration of the first timer changes.

[0131] In some implementations, the duration of the first timer is determined based on a default method; or, the duration of the first timer is configured by the network device to the terminal device.

[0132] In some implementations, the transceiver unit 310 is further configured to: receive second information sent by the network device, the second information being used to reject the request to establish a data radio bearer triggered by the first information.

[0133] In some implementations, the second information includes one or more of the following: a seventh indication information for indicating the type of task rejected; an eighth indication information for indicating the reason for rejection; and a ninth indication information for indicating the duration of rejection, wherein the duration is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer.

[0134] In some implementations, the rejection reason includes one or more of the following: the network device is in a congested state; the network device does not need to trigger the terminal device to request data corresponding to the task type of the data radio bearer; the network device cannot meet the data radio bearer requirement of the first information request.

[0135] In some implementations, the transceiver unit 310 is further configured to: determine whether it is possible to request the establishment of a data radio bearer.

[0136] In some implementations, the transceiver unit 310 is specifically used to: receive a tenth indication information sent by the network device, the tenth indication information being used to indicate whether the network device allows the terminal device to send the first information; and the terminal device, based on the value of the tenth indication information, determines whether it can request to establish a data radio bearer.

[0137] In some implementations, the transceiver unit 310 is specifically used to: determine whether a data radio bearer can be requested to be established based on capability information.

[0138] In some implementations, the transceiver unit 310 is specifically used to: receive a tenth indication information sent by the network device, the tenth indication information being used to indicate whether the network device allows the terminal device to send the first information; and determine whether a data radio bearer can be requested to be established based on the value of the tenth indication information and the capability information of the terminal device.

[0139] It is understood that the transceiver unit 310 may be, for example, a transceiver 530. Additionally, the terminal device 300 may optionally include a processor 510 and a memory 520, as shown in Figure 5.

[0140] Figure 4 is a schematic diagram of the network device provided in an embodiment of this application. The network device 400 shown in Figure 4 may include a transceiver unit 410. The transceiver unit 410 is used to receive first information sent by a terminal device. The first information is used to request the establishment of a data radio bearer. The first information includes one or more of the following: first indication information, used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer; second indication information, used to indicate the QoS flow requirements that the data radio bearer requested by the terminal device needs to meet; third indication information, used to indicate the RLC mode requirements that the data radio bearer requested by the terminal device needs to meet; and fourth indication information, used to indicate the amount of data corresponding to the data that the terminal device expects to send.

[0141] In some implementations, the first information further includes: fifth indication information, used to indicate the encryption level or encryption algorithm that the terminal device expects to use for the data radio bearer it requests to establish; and / or, sixth indication information, used to indicate the number or minimum number of data radio bearers that the terminal device expects to establish.

[0142] In some implementations, the task type includes model training dataset transfer tasks and / or measurement-related data transfer tasks.

[0143] In some implementations, the task type includes one or more of the following: model transmission task; model parameter transmission task; terminal device capability information transmission task.

[0144] In some implementations, the task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type of the transmitted data, or according to the data type of the transmitted data and the functional characteristics associated with the data type of the transmitted data.

[0145] In some implementations, the functional characteristics include one or more of the following: CSI compression feedback function; beam management function; positioning function; RRM measurement function; CSI prediction function; RRM event prediction function; sensing function; BFD function; RLF function; channel estimation function; environmental IoT function; LTM function.

[0146] In some implementations, the QoS flow requirements indicated by the second indication information include multiple QoS flows that are related, and the multiple QoS flows that are related are expected to be associated with the same data radio bearer.

[0147] In some implementations, the transceiver unit 410 is further configured to: send a second message to the terminal device, the second message being used to reject the request to establish a data radio bearer triggered by the first message.

[0148] In some implementations, the second information includes one or more of the following: a seventh indication information for indicating the type of task rejected; an eighth indication information for indicating the reason for rejection; and a ninth indication information for indicating the duration of rejection, wherein the duration is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer.

[0149] In some implementations, the rejection reason includes one or more of the following: the network device is in a congested state; the network device does not need to trigger the terminal device to request data corresponding to the task type of the data radio bearer; the network device cannot meet the data radio bearer requirement of the first information request.

[0150] In some implementations, the transceiver unit 410 is further configured to: send a tenth indication information to the terminal device, the tenth indication information being used to indicate whether the network device allows the terminal device to send the first information.

[0151] It is understood that the transceiver unit 410 may be, for example, a transceiver 530. Additionally, the network device 400 may optionally include a processor 510 and a memory 520, as shown in Figure 5.

[0152] Figure 5 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 5 indicate that the unit or module is optional. The apparatus 500 can be used to implement the methods described in the above method embodiments. The apparatus 500 may be, for example, a chip, a terminal device, or a network device.

[0153] The apparatus 500 may include one or more processors 510. The processors 510 may support the apparatus 500 in implementing the methods described in the foregoing method embodiments. The processor 510 may be a general-purpose processor or a special-purpose processor. For example, the processor 510 may be a central processing unit (CPU). Alternatively, the processor 510 may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0154] The apparatus 500 may also include one or more memories 520. The memories 520 store programs that can be executed by the processor 510, causing the processor 510 to perform the methods described in the above method embodiments. The memories 520 may be independent of the processor 510, or they may be integrated into the processor 510.

[0155] The device 500 may also include a transceiver 530. The processor 510 can communicate with other devices or chips via the transceiver 530. For example, the processor 510 can send and receive data with other devices or chips via the transceiver 530.

[0156] This application also provides a communication system. The communication system includes the terminal device and network device described above. In some implementations, the system further includes other devices that interact with the terminal device and network device.

[0157] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal device or network device in various embodiments of this application.

[0158] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal device or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0159] This application also provides a computer program. This computer program can be applied to the terminal device or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal device or network device in the various embodiments of this application.

[0160] It should be understood that the terms "system" and "network" in the embodiments of this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of this application and is not intended to limit this application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0161] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0162] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0163] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0164] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0165] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0166] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0167] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0168] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0169] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0170] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0171] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0172] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication, characterized in that, include: The terminal device sends first information to the network device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: The first indication information is used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer; The second instruction information is used to indicate the Quality of Service (QoS) flow requirements that the data radio bearer requested by the terminal device needs to meet. The third instruction information is used to indicate the Radio Link Control (RLC) mode requirements that the data radio bearer requested by the terminal device needs to meet. The fourth indication information is used to indicate the amount of data that the terminal device expects to send.

2. The method according to claim 1, characterized in that, The first information also includes: The fifth instruction information is used to indicate the encryption level or encryption algorithm that the terminal device expects to use in the data radio bearer it requests to establish; and / or, The sixth indication information is used to indicate the number or minimum number of data wireless bearers that the terminal device expects to establish.

3. The method according to claim 1 or 2, characterized in that, The task types include: Model training dataset transfer task; and / or, Measurement-related data transmission tasks.

4. The method according to any one of claims 1 to 3, characterized in that, The task type includes one or more of the following: Model transfer task; Model parameter transfer task; The task of transmitting capability information of terminal equipment.

5. The method according to any one of claims 1 to 4, characterized in that, The task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type of the transmitted data, or according to the data type of the transmitted data and the functional characteristics associated with the data type of the transmitted data.

6. The method according to claim 5, characterized in that, The functional characteristics include one or more of the following: Channel State Information (CSI) compression feedback function; beam management function; positioning function; Radio Resource Management (RRM) measurement function; CSI prediction function; RRM event prediction function; sensing function; Beam Failure Detection (BFD) function; Radio Link Failure (RLF) function; channel estimation function; environmental IoT function; and Low Layer Mobility Detection (LTM) function.

7. The method according to any one of claims 1 to 6, characterized in that, The QoS flow requirements indicated by the second indication information include multiple QoS flows that are related, and the multiple QoS flows that are related are expected to be associated with the same data radio bearer.

8. The method according to any one of claims 1 to 7, characterized in that, The terminal device sends first information to the network device, including: In response to the fulfillment of the first event, the terminal device triggers the action of sending the first information to the network device.

9. The method according to claim 8, characterized in that, The first event includes one or more of the following: The task type that triggered the sending of the first information belongs to the first task type range; The amount of data that the terminal device expects to send is greater than the first threshold. The terminal device determines that it is not in a low battery state.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: During the first timer operation, the terminal device determines not to send the first information.

11. The method according to claim 10, characterized in that, The first timer is activated when the first message is sent; and / or, The stopping condition for the first timer is that the value of the parameter used to configure the timing duration of the first timer changes.

12. The method according to claim 10 or 11, characterized in that, The timing duration of the first timer is determined based on a default method; or, The duration of the first timer is configured by the network device to the terminal device.

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: The terminal device receives a second message sent by the network device, the second message being used to reject the request to establish a data radio bearer triggered by the first message.

14. The method according to claim 13, characterized in that, The second information includes one or more of the following: The seventh instruction message indicates the type of task to be rejected; The eighth instruction message is used to indicate the reason for rejection; The ninth indication information is used to indicate the rejection duration, which is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer.

15. The method according to claim 14, characterized in that, The reasons for rejection include one or more of the following: The network device is in a congested state; The network device does not need to trigger the terminal device to request data corresponding to the task type of establishing a data wireless bearer; The network device cannot meet the data wireless bearer requirements established by the first information request.

16. The method according to any one of claims 1 to 15, characterized in that, The method further includes: The terminal device determines whether it can request the establishment of a data wireless bearer.

17. The method according to claim 16, characterized in that, The method further includes: The terminal device receives a tenth indication information sent by the network device, the tenth indication information being used to indicate whether the network device allows the terminal device to send the first information; The process of determining whether a data radio bearer can be established by the terminal device includes: Based on the value of the tenth indication information, the terminal device determines whether it can request to establish a data radio bearer.

18. The method according to claim 16, characterized in that, The terminal device determines whether it can request the establishment of a data radio bearer, including: The terminal device determines whether it can request to establish a data wireless bearer based on capability information.

19. The method according to claim 16, characterized in that, The method further includes: The terminal device receives a tenth indication information sent by the network device, the tenth indication information being used to indicate whether the network device allows the terminal device to send the first information; The process of determining whether a data radio bearer can be established by the terminal device includes: Based on the value of the tenth indication information and the capability information of the terminal device, the terminal device determines whether it can request to establish a data radio bearer.

20. A method for wireless communication, characterized in that, include: The network device receives first information sent by the terminal device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: The first indication information is used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer; The second instruction information is used to indicate the Quality of Service (QoS) flow requirements that the data radio bearer requested by the terminal device needs to meet. The third instruction information is used to indicate the Radio Link Control (RLC) mode requirements that the data radio bearer requested by the terminal device needs to meet. The fourth indication information is used to indicate the amount of data that the terminal device expects to send.

21. The method according to claim 20, characterized in that, The first information also includes: The fifth instruction information is used to indicate the encryption level or encryption algorithm that the terminal device expects to use in the data radio bearer it requests to establish; and / or, The sixth indication information is used to indicate the number or minimum number of data wireless bearers that the terminal device expects to establish.

22. The method according to claim 20 or 21, characterized in that, The task types include: Model training dataset transfer task; and / or, Measurement-related data transmission tasks.

23. The method according to any one of claims 20 to 22, characterized in that, The task type includes one or more of the following: Model transfer task; Model parameter transfer task; The task of transmitting capability information of terminal equipment.

24. The method according to any one of claims 20 to 23, characterized in that, The task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type of the transmitted data, or according to the data type of the transmitted data and the functional characteristics associated with the data type of the transmitted data.

25. The method according to claim 24, characterized in that, The functional characteristics include one or more of the following: Channel State Information (CSI) compression feedback function; beam management function; positioning function; Radio Resource Management (RRM) measurement function; CSI prediction function; RRM event prediction function; sensing function; Beam Failure Detection (BFD) function; Radio Link Failure (RLF) function; channel estimation function; environmental IoT function; and Low Layer Mobility Detection (LTM) function.

26. The method according to any one of claims 20 to 25, characterized in that, The QoS flow requirements indicated by the second indication information include multiple QoS flows that are related, and the multiple QoS flows that are related are expected to be associated with the same data radio bearer.

27. The method according to any one of claims 20 to 26, characterized in that, The method further includes: The network device sends a second message to the terminal device, the second message being used to reject the request to establish a data radio bearer triggered by the first message.

28. The method according to claim 27, characterized in that, The second information includes one or more of the following: The seventh instruction message indicates the type of task to be rejected; The eighth instruction message is used to indicate the reason for rejection; The ninth indication information is used to indicate the rejection duration, which is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer.

29. The method according to claim 28, characterized in that, The reasons for rejection include one or more of the following: The network device is in a congested state; The network device does not need to trigger the terminal device to request data corresponding to the task type of establishing a data wireless bearer; The network device cannot meet the data wireless bearer requirements established by the first information request.

30. The method according to any one of claims 20 to 29, characterized in that, The method further includes: The network device sends a tenth instruction message to the terminal device, the tenth instruction message being used to indicate whether the network device allows the terminal device to send the first message.

31. A terminal device, characterized in that, include: The transceiver unit is configured to send first information to the network device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: The first indication information is used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer; The second instruction information is used to indicate the Quality of Service (QoS) flow requirements that the data radio bearer requested by the terminal device needs to meet. The third instruction information is used to indicate the Radio Link Control (RLC) mode requirements that the data radio bearer requested by the terminal device needs to meet. The fourth indication information is used to indicate the amount of data that the terminal device expects to send.

32. The terminal device according to claim 31, characterized in that, The first information also includes: The fifth instruction information is used to indicate the encryption level or encryption algorithm that the terminal device expects to use in the data radio bearer it requests to establish; and / or, The sixth indication information is used to indicate the number or minimum number of data wireless bearers that the terminal device expects to establish.

33. The terminal device according to claim 31 or 32, characterized in that, The task types include: Model training dataset transfer task; and / or, Measurement-related data transmission tasks.

34. The terminal device according to any one of claims 31 to 33, characterized in that, The task type includes one or more of the following: Model transfer task; Model parameter transfer task; The task of transmitting capability information of terminal equipment.

35. The terminal device according to any one of claims 31 to 34, characterized in that, The task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type of the transmitted data, or according to the data type of the transmitted data and the functional characteristics associated with the data type of the transmitted data.

36. The terminal device according to claim 35, characterized in that, The functional characteristics include one or more of the following: Channel State Information (CSI) compression feedback function; beam management function; positioning function; Radio Resource Management (RRM) measurement function; CSI prediction function; RRM event prediction function; sensing function; Beam Failure Detection (BFD) function; Radio Link Failure (RLF) function; channel estimation function; environmental IoT function; and Low Layer Mobility Detection (LTM) function.

37. The terminal device according to any one of claims 31 to 36, characterized in that, The QoS flow requirements indicated by the second indication information include multiple QoS flows that are related, and the multiple QoS flows that are related are expected to be associated with the same data radio bearer.

38. The terminal device according to any one of claims 31 to 37, characterized in that, The transceiver unit is specifically used for: In response to the fulfillment of the first event, the action of sending the first information to the network device is triggered.

39. The terminal device according to claim 38, characterized in that, The first event includes one or more of the following: The task type that triggered the sending of the first information belongs to the first task type range; The amount of data that the terminal device expects to send is greater than the first threshold. The terminal device determines that it is not in a low battery state.

40. The terminal device according to any one of claims 31 to 39, characterized in that, The transceiver unit is also used for: During the first timer's operation, it is determined that the first information will not be sent.

41. The terminal device according to claim 40, characterized in that, The first timer is activated when the first message is sent; and / or, The stopping condition for the first timer is that the value of the parameter used to configure the timing duration of the first timer changes.

42. The terminal device according to claim 40 or 41, characterized in that, The timing duration of the first timer is determined based on a default method; or, The duration of the first timer is configured by the network device to the terminal device.

43. The terminal device according to any one of claims 31 to 42, characterized in that, The transceiver unit is also used for: The network device receives a second message, which is used to reject the request to establish a data radio bearer triggered by the first message.

44. The terminal device according to claim 43, characterized in that, The second information includes one or more of the following: The seventh instruction message indicates the type of task to be rejected; The eighth instruction message is used to indicate the reason for rejection; The ninth indication information is used to indicate the rejection duration, which is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer.

45. The terminal device according to claim 44, characterized in that, The reasons for rejection include one or more of the following: The network device is in a congested state; The network device does not need to trigger the terminal device to request data corresponding to the task type of establishing a data wireless bearer; The network device cannot meet the data wireless bearer requirements established by the first information request.

46. ​​The terminal device according to any one of claims 31 to 45, characterized in that, The transceiver unit is also used for: Determine whether it is possible to request the establishment of a data radio bearer.

47. The terminal device according to claim 46, characterized in that, The transceiver unit is specifically used for: The network device receives a tenth indication message, which indicates whether the network device allows the terminal device to send the first information. Based on the value of the tenth indication information, it is determined whether a request can be made to establish a data radio bearer.

48. The terminal device according to claim 46, characterized in that, The transceiver unit is specifically used for: Based on capability information, it is determined whether a request can be made to establish a data radio bearer.

49. The terminal device according to claim 46, characterized in that, The transceiver unit is specifically used for: The network device receives a tenth indication message, which indicates whether the network device allows the terminal device to send the first information. Based on the value of the tenth instruction information and the capability information of the terminal device, it is determined whether a request can be made to establish a data radio bearer.

50. A network device, characterized in that, include: The transceiver unit is configured to receive first information sent by the terminal device, the first information being used to request the establishment of a data radio bearer, the first information including one or more of the following: The first indication information is used to indicate the task type that triggers the terminal device to request the establishment of a data radio bearer; The second instruction information is used to indicate the Quality of Service (QoS) flow requirements that the data radio bearer requested by the terminal device needs to meet. The third instruction information is used to indicate the Radio Link Control (RLC) mode requirements that the data radio bearer requested by the terminal device needs to meet. The fourth indication information is used to indicate the amount of data that the terminal device expects to send.

51. The network device according to claim 50, characterized in that, The first information also includes: The fifth instruction information is used to indicate the encryption level or encryption algorithm that the terminal device expects to use in the data radio bearer it requests to establish; and / or, The sixth indication information is used to indicate the number or minimum number of data wireless bearers that the terminal device expects to establish.

52. The network device according to claim 50 or 51, characterized in that, The task types include: Model training dataset transfer task; and / or, Measurement-related data transmission tasks.

53. The network device according to any one of claims 50 to 52, characterized in that, The task type includes one or more of the following: Model transfer task; Model parameter transfer task; The task of transmitting capability information of terminal equipment.

54. The network device according to any one of claims 50 to 53, characterized in that, The task type that triggers the terminal device to request the establishment of a data wireless bearer is defined according to the data type of the transmitted data, or according to the data type of the transmitted data and the functional characteristics associated with the data type of the transmitted data.

55. The network device according to claim 54, characterized in that, The functional characteristics include one or more of the following: Channel State Information (CSI) compression feedback function; beam management function; positioning function; Radio Resource Management (RRM) measurement function; CSI prediction function; RRM event prediction function; sensing function; Beam Failure Detection (BFD) function; Radio Link Failure (RLF) function; channel estimation function; environmental IoT function; and Low Layer Mobility Detection (LTM) function.

56. The network device according to any one of claims 50 to 55, characterized in that, The QoS flow requirements indicated by the second indication information include multiple QoS flows that are related, and the multiple QoS flows that are related are expected to be associated with the same data radio bearer.

57. The network device according to any one of claims 50 to 56, characterized in that, The transceiver unit is also used for: A second message is sent to the terminal device, the second message being used to reject the request to establish a data radio bearer triggered by the first message.

58. The network device according to claim 57, characterized in that, The second information includes one or more of the following: The seventh instruction message indicates the type of task to be rejected; The eighth instruction message is used to indicate the reason for rejection; The ninth indication information is used to indicate the rejection duration, which is the duration during which the terminal device is not allowed to trigger a request to establish a data radio bearer.

59. The network device according to claim 58, characterized in that, The reasons for rejection include one or more of the following: The network device is in a congested state; The network device does not need to trigger the terminal device to request data corresponding to the task type of establishing a data wireless bearer; The network device cannot meet the data wireless bearer requirements established by the first information request.

60. The network device according to any one of claims 50 to 59, characterized in that, The transceiver unit is also used for: The tenth instruction information is sent to the terminal device, which is used to indicate whether the network device allows the terminal device to send the first information.

61. A terminal device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or send signals so that the terminal device performs the method according to any one of claims 1 to 19.

62. A network device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the network device performs the method according to any one of claims 20 to 30.

63. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform the method according to any one of claims 1 to 30.

64. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method according to any one of claims 1 to 30.

65. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method according to any one of claims 1 to 30.

66. A computer program product, characterized in that, Includes a program that causes a computer to perform the method according to any one of claims 1 to 30.

67. A computer program, characterized in that, The computer program causes the computer to perform the method according to any one of claims 1 to 30.

Images