CN115669192A

CN115669192A - Data transmission method, device, terminal equipment and storage medium

Info

Publication number: CN115669192A
Application number: CN202080101129.5A
Authority: CN
Inventors: 林雪; 石聪; 李海涛
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-07-10
Filing date: 2020-07-10
Publication date: 2023-01-31
Also published as: WO2022006911A1

Abstract

The application discloses a data transmission method, a data transmission device, terminal equipment and a storage medium, and relates to the field of wireless communication. The method is applied to the terminal equipment and comprises the following steps: triggering one of an IDT flow and a connection establishment recovery flow according to the type and/or the data volume of the service data; transmitting the service data by using the IDT process; or, after recovering the radio resource control RRC connection according to the connection establishment recovery flow, transmitting the service data; wherein the service data includes: at least one of a first type of data including data from a logical channel that supports triggering of the IDT flow and a second type of data including data from a logical channel that does not support triggering of the IDT flow.

Description

Data transmission method, device, terminal equipment and storage medium

Technical Field

The present application relates to the field of wireless communications, and in particular, to a data transmission method, apparatus, terminal device, and storage medium.

Background

The RRC _ INACTIVE state (i.e., RRC INACTIVE state) is a New state introduced by a New Radio (NR) system from the viewpoint of power saving.

For the terminal device in the RRC _ INACTIVE state, the Radio bearer and all Radio resources are released, but the UE access context is reserved on the terminal device side and the network device side, so as to quickly recover Radio Resource Control (RRC) connection.

In the related art, in the RRC _ INACTIVE state, if a terminal device wants to perform data transmission, it needs to trigger a connection establishment recovery procedure to recover the RRC connection, and enter a connected state to perform data transmission, which results in large power consumption.

Disclosure of Invention

The embodiment of the application provides a data transmission method and device, terminal equipment and a storage medium, wherein the terminal equipment can reasonably trigger an IDT (IDT) flow according to the type of service data, so that data transmission can be performed without recovering RRC (radio resource control) connection, and power consumption is reduced. The technical scheme is as follows.

According to an aspect of the present application, a data transmission method is provided, which is applied in a terminal device, and the method includes:

triggering one of an IDT flow and a connection establishment recovery flow according to the type and/or the data volume of the service data;

transmitting the service data by using the IDT flow; or, after recovering the radio resource control RRC connection according to the connection establishment recovery flow, transmitting the service data;

wherein the service data includes: at least one of a first type of data including data from a logical channel that supports triggering of the IDT flow and a second type of data including data from a logical channel that does not support triggering of the IDT flow.

According to an aspect of the present application, there is provided a data transmission apparatus, the apparatus including: the device comprises a trigger module and a transmission module;

the triggering module is used for triggering one of an IDT (IDT) flow and a connection establishment recovery flow according to the type of the service data and/or the size of the data volume;

the transmission module is configured to transmit the service data by using the IDT process; or, after recovering the radio resource control RRC connection according to the connection establishment recovery flow, transmitting the service data;

According to an aspect of the present application, there is provided a terminal device including: a processor; a transceiver coupled to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the data transmission method as described in the above aspect.

According to an aspect of the present application, there is provided a computer-readable storage medium having stored therein executable instructions that are loaded and executed by a processor to implement the data transmission method according to the above aspect.

According to an aspect of the present application, there is provided a computer program product or a computer program comprising computer instructions stored in a computer-readable storage medium, the computer instructions being read by a processor of a computer device from the computer-readable storage medium, the computer instructions being executed by the processor to cause the computer device to perform the data transmission method of the above aspect.

The technical scheme provided by the embodiment of the application at least comprises the following beneficial effects:

under the condition that the terminal equipment is in an inactive state, one of the IDT triggering process and the connection establishment recovery process can be selected according to the type and/or the data volume of the service data so as to realize data transmission, and the terminal equipment can reasonably trigger the IDT process according to the type and/or the data volume of the service data, so that the data transmission can be carried out without recovering RRC connection, and the power consumption is reduced.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

FIG. 1 is a block diagram of a communication system provided in an exemplary embodiment of the present application;

FIG. 2 is a flow chart of a method for data transmission provided by an exemplary embodiment of the present application;

FIG. 3 is a flow chart of a method of data transmission provided by an exemplary embodiment of the present application;

FIG. 4 is a flow chart of a method of data transmission provided by an exemplary embodiment of the present application;

FIG. 5 is a flow chart of a method of data transmission provided by an exemplary embodiment of the present application;

FIG. 6 is a flow chart of a method of data transmission provided by an exemplary embodiment of the present application;

FIG. 7 is a flow chart of a method for data transmission provided by an exemplary embodiment of the present application;

FIG. 8 is a flow chart of a method for data transmission provided by an exemplary embodiment of the present application;

FIG. 9 is a flow chart of a method of data transmission provided by an exemplary embodiment of the present application;

fig. 10 is a block diagram of a data transmission apparatus according to an exemplary embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an exemplary embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, the following detailed description of the embodiments of the present application will be made with reference to the accompanying drawings.

First, terms referred to in the embodiments of the present application are briefly described:

RRC state:

in a 5G network environment, a new RRC state, that is, an RRC _ INACTIVE state, is defined for the purpose of reducing air interface signaling, quickly recovering wireless connection, and quickly recovering data service.

RRC _ IDLE state (i.e., RRC IDLE state): the mobility is cell selection and reselection based on terminal equipment, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The network equipment side does not have the UE access context. There is no RRC connection.

RRC _ CONNECTED state (i.e., RRC CONNECTED state): the RRC connection exists, and the network equipment and the terminal equipment have UE access context. The network equipment side knows that the position of the terminal equipment is at a specific cell level. Mobility is network device side controlled mobility. Unicast data may be transmitted between the terminal device and the network device.

RRC _ INACTIVE state (i.e., RRC INACTIVE state): mobility is cell selection and reselection based on terminal equipment, connection between CN-NR exists, UE Access context exists on certain Network equipment, paging is triggered by a Radio Access Network (RAN), a paging area based on the RAN is managed by the RAN, and the Network equipment side knows that the position of the terminal equipment is based on the paging area level of the RAN.

Fig. 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application, which may include: access network 12 and terminal equipment 14.

Several network devices 120 are included in access network 12. Network device 120 may be a base station, which is a device deployed in an access network to provide wireless communication functionality for terminals. The base stations may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different radio access technologies, the names of devices with base station functionality may differ, for example in LTE systems, called eNodeB or eNB; in a 5G NR-U system, it is called gNodeB or gNB. The description of "base station" may change as communication technology evolves. For convenience of this embodiment, the above-mentioned apparatuses providing wireless communication function for the terminal device 14 are collectively referred to as a network device.

Terminal devices 14 may include a variety of handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of user equipment, mobile Stations (MSs), terminals (terminal devices), and so forth. For convenience of description, the above-mentioned devices are collectively referred to as a terminal. The network device 120 and the terminal device 14 communicate with each other through some air interface technology, for example, a Uu interface. Optionally, the terminal device is in RRC _ INACTIVE state.

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: global System for Mobile communications (GSM) System, code Division Multiple Access (CDMA) System, wideband Code Division Multiple Access (WCDMA) System, general Packet Radio Service (GPRS), long Term Evolution (Long Term Evolution, LTE) System, LTE Frequency Division Duplex (FDD) System, LTE Time Division Duplex (TDD) System, advanced Long Term Evolution (Advanced Long Term Evolution), an LTE-a) System, a New Radio (NR) System, an Evolution System of the NR System, an LTE (LTE-based Access to Unlicensed spectrum) System on an Unlicensed Frequency band, an NR-U System, a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) Communication System, a Wireless Local Area Network (WLAN), a Wireless Fidelity (WiFi), a next generation Communication System, or other Communication systems.

Generally, the conventional Communication system supports a limited number of connections and is easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-Machine (M2M) Communication, machine Type Communication (MTC), vehicle-to-Vehicle (V2V) Communication, and Vehicle networking (V2X) system, etc. The embodiments of the present application can also be applied to these communication systems.

Fig. 2 is a flowchart illustrating a data transmission method according to an exemplary embodiment of the present application. The method can be applied to the terminal device and the network device shown in fig. 1, and comprises the following steps:

step 210, the terminal device triggers one of the IDT flow and the connection establishment recovery flow according to the type of the service data and/or the size of the data volume.

Wherein, the terminal device is in RRC _ INACTIVE state.

When the terminal device needs to transmit the service Data, one of an Inactive Data Transmission (IDT) triggering process and a connection establishment recovery process is selected according to the type of the service Data, or according to the Data volume of the service Data, or according to the type and the Data volume of the service Data, and part or all of the service Data is transmitted through the triggered IDT process or the connection establishment recovery process.

In a possible implementation manner, the terminal device establishes a recovery flow through the connection, enters an RRC connected state, and transmits all service data; in another possible implementation manner, the terminal device transmits all service data by triggering the IDT flow; in another possible implementation manner, by triggering the IDT procedure, part of the service data is transmitted through one transmission, and then the connection establishment recovery procedure needs to be triggered, and the remaining service data is continuously transmitted in the RRC connected state.

The IDT procedure is a procedure in which the terminal device performs data transmission in an INACTIVE state (i.e., RRC _ INACTIVE state). The IDT procedure does not require an RRC connection to be established between the terminal device and the network device. The embodiment of the present application does not limit the specific process of the IDT flow. The connection establishment recovery procedure is a procedure in which the terminal device recovers the RRC connection with the network device.

If the terminal device in the RRC _ INACTIVE state can only establish the recovery procedure through the connection, the RRC connection with the network device is recovered to perform data transmission, and the terminal device needs to return to the RRC _ INACTIVE state after the data transmission is completed. For a terminal device with a small data amount and a low transmission frequency, power consumption is large. Through the IDT flow, the conversion of the connection state is avoided, and the power consumption can be reduced.

The traffic data is data to be transmitted that is present at the terminal device. The service data comprises: at least one of a first type data including data from a logical channel supporting the triggered IDT flow and a second type data including data from a logical channel not supporting the triggered IDT flow.

Optionally, the Service quality (QoS) requirements of the services corresponding to the first type data and the second type data are different, and the first type data and the second type data are mapped to different logical channels, and the network device configures whether the logical channels support triggering the IDT process.

The International Telecommunications Union (ITU) has classified the traffic in 5G networks into 3 major classes. The first type is Mobile Broadband enhanced (eMBB), which is a 5G service class that is dedicated to Mobile devices such as Mobile phones. The second category is Ultra-Reliable and Ultra-Low Latency Communication (URLLC), which is mainly used in industrial applications and autonomous vehicles. The third Type is a large-scale internet of things (mtc), the mtc is a service Type to be used in the "internet of things" and "everything interconnection" scenarios, and the advantage of the mtc is that a large number of neighboring devices can simultaneously enjoy smooth Communication connection. The service data may comprise service data of the same or different service classes. Such as: including eMBB data and URLLC data; or, including eMBB data, URLLC data, and mMTC data; or, only URLLC data.

Alternatively, the service data of different service classes may correspond to one of the first type data and the second type data. Such as: since URLLC service will usually require very high reliability and very low latency URLLC data may correspond to the first type of data, so as to facilitate fast transmission of URLLC data through IDT procedure; since eMBB services typically require higher rates but do not require very low latency and very low error rates, eMBB data may correspond to the second type of data. That is, URLLC data is transmitted on a logical channel supporting the triggered IDT procedure, and eMBB data is transmitted on a logical channel not supporting the triggered IDT procedure.

After the service data arrives, if the logic channel mapped by the service data is the logic channel supporting triggering the IDT process, the service data is the first type data; if the logical channel to which the service data is mapped is a logical channel that does not support the triggered IDT procedure, the service data is the second type data. And the terminal equipment selects one of the IDT triggering process and the connection establishment recovery process according to the type of the service data and/or the data volume. The types of the service data may include the following three types:

1) Including a first type of data.

2) Including the second type of data.

3) Including a first type of data and a second type of data.

Exemplarily, the service data is URLLC data, the logical channel to which the URLLC data is mapped is a logical channel supporting the triggered IDT flow, and then the URLLC data corresponds to the first type of data, and then the type of the service data is 1) includes the first type of data; the service data is eMB data, the logical channel to which the eMB data is mapped is a logical channel which does not support triggering the IDT process, and if the eMB data corresponds to the second type data, the type of the service data is 2) including the second type data; the service data is eMMC data and URLLC data, the logical channel to which the URLLC data is mapped is a logical channel supporting triggering IDT flow, the URLLC data corresponds to first type data, the logical channel to which the eMMC data is mapped is a logical channel not supporting triggering IDT flow, the eMMC data corresponds to second type data, and the type of the service data is 3) including the first type data and the second type data.

It can be understood that, the above description only exemplifies the first type data and the second type data, and it can also be determined in other ways whether the service data belongs to the first type data or the second type data, which is not limited in this embodiment of the application.

After performing step 210, the terminal device performs one of step 220 and step 230. Specifically, in the case that the terminal device triggers the IDT procedure, step 220 is executed; in case the terminal device triggers the connection establishment recovery procedure, step 230 is executed.

Step 220, the terminal device transmits the service data by using the IDT flow.

And if the terminal equipment triggers the IDT flow according to the type of the service data, the triggered IDT flow is used for transmitting the service data.

In one possible implementation, the terminal device transmits the first type data using an IDT procedure; in another possible implementation manner, the terminal device transmits the second type data by using an IDT flow; in another possible implementation, the terminal device uses an IDT flow to transmit the first type of data and the second type of data.

Step 230, the terminal device transmits the service data after recovering the RRC connection according to the connection establishment recovery procedure.

If the terminal equipment triggers the connection establishment recovery process according to the type of the service data, the service data is transmitted by the terminal equipment in the RRC connection state after the RRC connection is recovered.

In one possible implementation, the terminal device in the RRC connected state transmits the first type of data; in another possible implementation manner, the terminal device in the RRC connected state transmits the second type data; in another possible implementation, the terminal device in the RRC connected state transmits the first type of data and the second type of data.

In summary, according to the method provided in this embodiment, when the terminal device is in the inactive state, one of the IDT triggering procedure and the connection establishment recovery procedure may be selected according to the type and/or the data size of the service data, so as to implement data transmission.

In an alternative embodiment based on fig. 2, the types of the service data may include the following three types:

1) The traffic data includes a first type of data.

The first type of data may also be referred to as IDT data.

2) The service data includes a second type of data.

The second type of data may also be referred to as Non-IDT data.

3) The service data includes a first type of data and a second type of data.

The terminal device may select one of the trigger IDT procedure and the connection setup recovery procedure according to the determined type (1) or 2) or 3) of the service data and/or the data volume size. This is further exemplified below.

Type 1) traffic data includes a first type of data.

Fig. 3 is a flowchart illustrating a data transmission method according to an exemplary embodiment of the present application. The method can be applied to a terminal device and a network device as shown in fig. 1. In this embodiment, step 210 is alternatively implemented as step 211:

step 211: the terminal device triggers one of an IDT flow and a connection establishment recovery flow according to the data volume of the first type data.

Optionally, the IDT flow is triggered in case the data amount of the first type of data is smaller than the first threshold.

After the terminal device triggers the IDT procedure, step 220 is executed to transmit the first type of data using the IDT procedure.

Optionally, in a case that the data amount of the first type of data is not less than the first threshold, the connection establishment recovery procedure is triggered.

After the terminal device triggers the connection establishment recovery procedure, step 230 is executed, that is, the connection establishment recovery procedure is triggered, and after the RRC connection is recovered, the first type data is transmitted in the RRC connected state.

Wherein the first threshold is a maximum Transport Block Size (TBS) corresponding to the first type of data. The first threshold is used for the terminal device to determine whether the first type data can trigger the IDT flow. The first threshold is predefined or the first threshold is configured by the network device.

For example, assuming that logical channel #1 and logical channel #2 are logical channels that can trigger the IDT procedure, the maximum TBS threshold 1 (i.e., the first threshold) supported by the IDT procedure is assumed to be 2000bits.

If the service data to be transmitted by the terminal device comes from the logical channel #1, or the logical channel #2, or the logical channel #1+ the logical channel #2, and the data volume of the IDT data (i.e., the first type data) is 1800bits, the data volume of the IDT data is less than the TBS threshold 1, and the terminal device triggers the IDT procedure.

If the service data to be transmitted by the terminal device comes from the logical channel #1, or the logical channel #2, or the logical channel #1+ the logical channel #2, and the data volume of the IDT data (i.e., the first type data) is 2500bits, the data volume of the IDT data does not meet the requirement that the data volume of the IDT data is less than the TBS threshold 1, and the terminal device triggers a connection establishment recovery procedure.

Type 2) traffic data includes second type data.

Fig. 4 is a flowchart illustrating a data transmission method according to an exemplary embodiment of the present application. The method can be applied to a terminal device and a network device as shown in fig. 1. In the present embodiment, step 210 is alternatively implemented as step 212-1:

step 212-1: the terminal equipment triggers a connection establishment recovery process.

When Non-IDT data (i.e., second-type data) is present, the IDT procedure is not allowed to be triggered, and the terminal device triggers the connection establishment recovery procedure.

In step 230, the terminal device recovers the RRC connection according to the connection establishment recovery procedure, and then transmits the service data.

And the terminal equipment directly triggers the connection establishment recovery process because the service data only comprise the second type data, and transmits the second type data in the RRC connected state after the RRC connection is recovered.

For example, it is assumed that logical channel #1 and logical channel #2 are logical channels that can trigger the IDT flow.

If the service data to be transmitted by the terminal equipment comes from the logical channel #4, and the data volume of non-IDT data (i.e. second type data) is 1000bits, the logical channel from the non-triggerable IDT flow is not allowed to trigger the IDT flow, so that the connection establishment recovery flow is triggered.

Fig. 5 is a flowchart illustrating a data transmission method according to an exemplary embodiment of the present application. The method can be applied to the terminal device and the network device as shown in fig. 1. In the present embodiment, step 210 is alternatively implemented as step 212-2:

step 212-2: the terminal device triggers one of the IDT flow and the connection establishment recovery flow according to the data volume of the second type data.

When the Non-IDT data (second type data) is present, the IDT flow is allowed to be triggered, and the terminal device can trigger one of the IDT flow and the connection establishment recovery flow according to the data amount of the second type data.

Optionally, the IDT flow is triggered in case the data amount of the second type of data is smaller than a second threshold.

After the terminal device triggers the IDT procedure, step 220 is executed to transmit the second type data using the IDT procedure.

Optionally, in a case that the data amount of the second type of data is not less than the second threshold, the connection establishment recovery procedure is triggered.

After the terminal device triggers the connection establishment recovery procedure, step 230 is executed, that is, the connection establishment recovery procedure is triggered, and after the RRC connection is recovered, the second type data is transmitted in the RRC connected state.

Wherein the second threshold is a maximum TBS corresponding to the second type of data. The second threshold is used for the terminal device to determine whether the IDT flow can be triggered by the second type of data. The second threshold is predefined or the second threshold is configured by the network device.

It is to be understood that the second threshold and the first threshold are independent of each other, that is, the first threshold and the second threshold are the same or different, and the embodiment of the present application does not limit this.

For example, assuming that logical channel #1 and logical channel #2 are logical channels that can trigger IDT procedure, the maximum TBS threshold 2 (i.e., the second threshold) supported by Non-IDT is assumed to be 1500bits.

If the service data to be transmitted by the terminal equipment comes from the logic channel #4, the data volume of the Non-IDT data (namely the second type data) is 1000bits, the data volume of the Non-IDT data is less than the TBS threshold 2, and the terminal equipment triggers the IDT flow.

If the service data to be transmitted by the terminal equipment comes from a logical channel #4, the data volume of Non-IDT data (namely second type data) is 2000bits and the data volume of the Non-IDT data is not satisfied to be less than the TBS threshold value 2, the terminal equipment triggers the connection and establishes a recovery process.

Type 3) service data includes first type data and second type data.

Fig. 6 shows a flowchart of a data transmission method according to an example embodiment of the present application. The method can be applied to the terminal device and the network device as shown in fig. 1. In the present embodiment, step 210 is alternatively implemented as step 213-1:

step 213-1: the terminal equipment triggers a connection establishment recovery process.

Because the service data includes the second type data in addition to the first type data, the terminal device directly triggers the connection establishment recovery process, and transmits the first type data and the second type data in the RRC connected state after the RRC connection is recovered.

If the service data to be transmitted by the terminal device comes from the logical channel #1+ logical channel #4, or the logical channel #2+ logical channel #4, or the logical channel #1+ logical channel #2+ logical channel #4, the logical channel from the non-triggerable IDT flow is not allowed to trigger the IDT flow, so that the connection establishment recovery flow is triggered.

Fig. 7 is a flowchart illustrating a data transmission method according to an exemplary embodiment of the present application. The method can be applied to a terminal device and a network device as shown in fig. 1. In the present embodiment, step 210 is alternatively implemented as step 213-2:

step 213-2: the terminal device triggers one of the IDT flow and the connection establishment recovery flow according to the data amount of the first type data.

When Non-IDT data (second type data) is present, the IDT flow is allowed to be triggered, and the terminal device can trigger one of the IDT flow and the connection establishment recovery flow according to the data amount of the first type data.

After the terminal device triggers the IDT procedure, step 220 is executed, i.e. the first type of data is transmitted using the IDT procedure. Optionally, after triggering the IDT procedure, the terminal device Reports a current Buffer Status Reports (BSR) and informs the network device of the Buffer Status. The network device may determine, according to the BSR, whether to revert the terminal device to the connected state or continue to schedule data transmission in the RRC inactive state.

After the terminal device triggers the connection establishment recovery procedure, step 230 is executed, that is, the connection establishment recovery procedure is triggered, and after the RRC connection is recovered, the first type data and the second type data are transmitted in the RRC connected state.

Wherein the first threshold is a maximum TBS corresponding to the first type of data. The first threshold is used for the terminal device to determine whether to trigger the IDT process when the service data includes the first type of data. The first threshold is predefined or the first threshold is configured by the network device.

For example, assuming that logical channel #1 and logical channel #2 are logical channels that can trigger the IDT flow, the maximum TBS threshold 1 (i.e., the first threshold) supported by the IDT flow is assumed to be 2000bits.

If the service data to be transmitted by the terminal device comes from the logical channel #1+ logical channel #4, or the logical channel #2+ logical channel #4, or the logical channel #1+ logical channel #2+ logical channel #4, wherein the data volume of the IDT data (i.e., the first type data) is 1800bits, the data volume of the non-IDT data (i.e., the second type data) is 1000bits, and the data volume of the IDT data is less than the TBS threshold 1, the terminal device triggers the IDT flow.

If the service data to be transmitted by the terminal device comes from the logical channel #1+ logical channel #4, or the logical channel #2+ logical channel #4, or the logical channel #1+ logical channel #2+ logical channel #4, wherein the data volume of the IDT data (i.e., the first type data) is 2500bits, the data volume of the non-IDT data (i.e., the second type data) is 1000bits, and the data volume of the IDT data is not satisfied to be less than the TBS threshold 1, the terminal device triggers a connection establishment recovery procedure.

Fig. 8 is a flowchart illustrating a data transmission method according to an exemplary embodiment of the present application. The method can be applied to a terminal device and a network device as shown in fig. 1. In the present embodiment, step 210 is alternatively implemented as step 213-3:

step 213-3: the terminal device triggers one of the IDT flow and the connection establishment recovery flow according to the data volume of the first type data and the data volume of the second type data.

When Non-IDT data (second type data) is present, the IDT flow is allowed to be triggered, and the terminal device may trigger one of the IDT flow and the connection establishment recovery flow according to the data amount of the second type data and the data amount of the first type data.

The terminal equipment firstly preliminarily judges whether to trigger the connection establishment recovery flow according to the data volume of the second type of data, and if the judgment result obtained according to the data volume of the second type of data is that the connection establishment recovery flow is not triggered, the terminal equipment further judges whether to trigger the connection establishment recovery flow according to the data volume of the first type of data.

Optionally, the IDT flow is triggered when the data amount of the second type of data is smaller than the second threshold and the data amount of the first type of data is smaller than the first threshold.

After the terminal device triggers the IDT procedure, step 220 is executed to transmit the first type of data using the IDT procedure. Optionally, after triggering the IDT procedure, the terminal device reports the current BSR to notify the network device of the buffer status. The network device may determine, according to the BSR, whether to restore the terminal device to the connected state or continue to schedule data transmission in the RRC inactive state.

Optionally, the connection establishment recovery procedure is triggered when the data amount of the second type of data is smaller than a second threshold and the data amount of the first type of data is not smaller than a first threshold.

Wherein the first threshold is a maximum TBS corresponding to the first type of data. The first threshold is used for the terminal device to determine whether to trigger the IDT flow when the service data includes the first type of data. The first threshold is predefined or the first threshold is configured by the network device. The second threshold is the maximum TBS for the second type of data. The second threshold is used for the terminal device to determine whether to trigger the IDT process when the service data includes the second type of data. The second threshold is predefined or the second threshold is configured by the network device. It is to be understood that the second threshold and the first threshold are independent of each other, that is, the first threshold and the second threshold are the same or different, and this is not limited by the embodiment of the present application.

For example, assuming that logical channel #1 and logical channel #2 are logical channels that can trigger the IDT flow, the maximum TBS threshold 1 (i.e., the first threshold) supported by the IDT flow is assumed to be 2000bits. The maximum TBS threshold 2 (i.e., the second threshold) supported by IDT procedure is assumed to be 1500bits.

If the terminal device wants to transmit the service data logical channel #1+ logical channel #4, or the logical channel #2+ logical channel #4, or the logical channel #1+ logical channel #2+ logical channel #4, wherein the data amount of the IDT data (i.e., the first type data) is 2500bits, the data amount of the Non-IDT data (i.e., the second type data) is 2000bits, and the data amount of the Non-IDT data is not satisfied < TBS threshold 2, the terminal device triggers a connection establishment recovery procedure.

If the service data to be transmitted by the terminal device comes from the logical channel #1+ logical channel #4, or the logical channel #2+ logical channel #4, or the logical channel #1+ logical channel #2+ logical channel #4, wherein the data amount of the IDT data (i.e., the first type data) is 1800bits, the data amount of the Non-IDT data (i.e., the second type data) is 1000bits, the data amount of the Non-IDT data < TBS threshold 2 and the data amount of the IDT data < TBS threshold 1 are satisfied, and the terminal device triggers the IDT procedure.

If the service data to be transmitted by the terminal device comes from the logical channel #1+ logical channel #4, or the logical channel #2+ logical channel #4, or the logical channel #1+ logical channel #2+ logical channel #4, wherein the data volume of the IDT data (i.e., the first type data) is 2500bits, the data volume of the Non-IDT data (i.e., the second type data) is 1000bits, the data volume of the Non-IDT data is less than the TBS threshold 2, but the data volume of the IDT data is not less than the TBS threshold 1, and the terminal device triggers a connection establishment recovery procedure.

In summary, the terminal device may determine one of the IDT triggering procedure and the connection establishment recovery procedure according to different types of service data and by using any one of a plurality of determination criteria, so as to improve the flexibility of the data transmission method.

For the above method embodiments, the following can also be understood:

1. in case the service data contains or is entirely of the second type of data, the IDT flow is not allowed to be triggered.

For example, corresponding to the embodiment shown in fig. 3, the IDT process is triggered only when all the service data are the first type data and the data amount of the first type data is smaller than the first threshold.

For example, corresponding to the embodiment shown in fig. 4, if all the service data is the second type data, the IDT flow is not allowed to be triggered, and the connection establishment recovery flow is directly triggered.

Illustratively, corresponding to the embodiment shown in fig. 6, if the service data includes the first type data and the second type data, the IDT flow is not allowed to be triggered, and the connection establishment recovery flow is directly triggered.

Because the IDT flow is not allowed to be triggered under the condition that the service data contains or is totally the second type data, the IDT flow can be triggered only when the service data is totally from the logic channel which allows the IDT flow to be triggered, and the abuse of the IDT flow to influence the normal connection establishment and data transmission flow is avoided.

2. And determining whether to trigger the IDT flow according to the data volume of the first type data under the condition that the service data contains the second type data.

Illustratively, corresponding to the embodiment shown in fig. 7, the service data includes the first type data and the second type data, and the IDT flow is triggered when the data amount of the first type data is smaller than the first threshold.

When the first type data and the second type data arrive at the same time, the terminal device may execute the IDT flow according to the condition of the first type data, so that the data satisfying the IDT condition may be delivered to the network more quickly.

3. And under the condition that the service data contains the second type data, determining whether to trigger the IDT flow according to the data volume of the first type data and the data volume of the second type data.

Illustratively, corresponding to the embodiment shown in fig. 8, the service data includes the first type data and the second type data, and the IDT procedure is triggered when the data amount of the second type data is smaller than the second threshold and the data amount of the first type data is smaller than the first threshold.

When the first type data and the second type data arrive at the same time, the terminal device may determine whether to directly recover to the connection state according to the data volume of the second type data, if the data volume of the second type data is large, the connection state needs to be entered for transmission, the connection establishment recovery process may be directly triggered, and if the data volume of the second type data is small, the IDT process may still be triggered.

4. And in the case that all the service data are the second type data, triggering the IDT flow is allowed.

Exemplarily, corresponding to the embodiment shown in fig. 5 described above, the IDT flow is allowed to be triggered when all the service data are the second type data and the data amount of the second type data is smaller than the second threshold.

When all the service data to be transmitted by the terminal device is the second type data and the data volume of the second type data is small, for example, the data volume is smaller than the threshold value configured by the network device, the terminal device can avoid the time delay and signaling overhead brought by triggering the connection establishment flow, and directly and quickly deliver the data to the network through the IDT flow.

In an alternative embodiment based on fig. 2, fig. 9 shows a flowchart of a data transmission method provided in an exemplary embodiment of the present application. The method can be applied to a terminal device and a network device as shown in fig. 1. In this embodiment, the method further includes the following steps:

in step 240, the network device sends the data transmission parameters to the terminal device.

In step 250, the terminal device receives the data transmission parameters.

The data transmission parameters include, but are not limited to: at least one of a logical channel, a first threshold value, and a second threshold value that triggers the IDT flow is supported. The first threshold corresponds to a first type of data and the second threshold corresponds to a second type of data.

It should be noted that, the data transmission parameters may be configured by the network device, and may also be predefined in the protocol standard, which is not limited in the embodiment of the present application.

In summary, in the method provided in this embodiment, since the service data is transmitted on a certain logical channel, the logical channel supporting triggering the IDT procedure may be configured by the data transmission parameter, so as to define a specific service triggering IDT procedure.

It should be noted that the above method embodiments may be implemented individually or in combination, and the present application is not limited thereto.

In the above embodiments, the steps executed by the terminal device may be implemented separately as a method for processing a handover failure on the terminal device side, and the steps executed by the network device may be implemented separately as a method for transmitting data on the network device side.

Fig. 10 shows a block diagram of a data transmission apparatus according to an exemplary embodiment of the present application, where the apparatus may be implemented as a terminal device or as a part of a terminal device, and the apparatus includes: a triggering module 1001 and a transmission module 1002;

a triggering module 1001, configured to trigger one of an IDT (active digital media transport) procedure and a connection establishment recovery procedure according to a type and/or a data size of service data;

a transmission module 1002, configured to transmit service data using an IDT flow; or, after the radio resource control RRC connection is recovered according to the connection establishment recovery flow, transmitting service data;

the service data comprises: at least one of a first type data including data from a logical channel supporting the triggered IDT flow and a second type data including data from a logical channel not supporting the triggered IDT flow.

In an alternative embodiment, the service data includes: a first type of data; a triggering module 1001, configured to trigger one of an IDT procedure and a connection establishment recovery procedure according to the data amount of the first type of data.

In an optional embodiment, the triggering module 1001 is configured to trigger the IDT process if the data amount of the first type of data is smaller than a first threshold; the triggering module 1001 is configured to trigger a connection establishment recovery procedure when the data amount of the first type data is not less than a first threshold.

In an alternative embodiment, the service data includes: a second type of data; a triggering module 1001, configured to trigger a connection establishment recovery procedure; or, the triggering module 1001 is configured to trigger one of the IDT procedure and the connection establishment recovery procedure according to the data amount of the second type of data.

In an optional embodiment, the triggering module 1001 is configured to trigger the IDT flow if the data amount of the second type of data is smaller than a second threshold; the triggering module 1001 is configured to trigger a connection establishment recovery procedure when the data amount of the second type of data is not less than a second threshold.

In an optional embodiment, the service data includes: a first type of data and a second type of data; a triggering module 1001, configured to trigger a connection establishment recovery procedure; or, the triggering module 1001 is configured to trigger one of an IDT procedure and a connection establishment recovery procedure according to the data amount of the first type of data; or, the triggering module 1001 is configured to trigger one of the IDT procedure and the connection establishment recovery procedure according to the first type data and the data volume of the second type data.

In an optional embodiment, the triggering module 1001 is configured to trigger the connection establishment recovery procedure when the data amount of the second type of data is not less than a second threshold; a triggering module 1001, configured to trigger the IDT process when a data amount of the second type of data is smaller than a second threshold and a data amount of the first type of data is smaller than a first threshold; the triggering module 1001 is configured to trigger a connection establishment recovery procedure when the data amount of the second type of data is smaller than a second threshold and the data amount of the first type of data is not smaller than a first threshold.

In an optional embodiment, the apparatus further comprises: a receiving module 1003; a receiving module 1003, configured to receive data transmission parameters configured by the network device; wherein, the data transmission parameters include: at least one of a logical channel triggering the IDT flow, a first threshold value corresponding to a first type of data, and a second threshold value corresponding to a second type of data is supported.

Fig. 11 shows a schematic structural diagram of a communication device (terminal device or network device) according to an exemplary embodiment of the present application, where the communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104, and a bus 105.

The processor 101 includes one or more processing cores, and the processor 101 executes various functional applications and information processing by running software programs and modules.

The receiver 102 and the transmitter 103 may be implemented as one communication component, which may be a communication chip.

The memory 104 is connected to the processor 101 through a bus 105.

The memory 104 may be configured to store at least one instruction for execution by the processor 101 to implement the various steps in the above-described method embodiments.

Further, the memory 104 may be implemented by any type or combination of volatile or non-volatile storage devices, including, but not limited to: magnetic or optical disk, electrically Erasable Programmable Read-Only Memory (EEPROM), erasable Programmable Read-Only Memory (EPROM), static Random Access Memory (SRAM), read-Only Memory (ROM), magnetic Memory, flash Memory, programmable Read-Only Memory (PROM).

In an exemplary embodiment, a computer readable storage medium is also provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, and the at least one instruction, the at least one program, the set of codes, or the set of instructions is loaded and executed by a processor to implement the data transmission method performed by the communication device provided by the above-mentioned various method embodiments.

In an exemplary embodiment, there is also provided a computer program product or a computer program comprising computer instructions stored in a computer readable storage medium, the computer instructions being read by a processor of a computer device from the computer readable storage medium, the computer instructions being executed by the processor to cause the computer device to perform the data transmission method of the above aspect.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

A data transmission method is applied to a terminal device, and the method comprises the following steps:

triggering one of an IDT flow and a connection establishment recovery flow according to the type and/or the data volume of the service data;

transmitting the service data by using the IDT flow; or, after recovering the radio resource control RRC connection according to the connection establishment recovery flow, transmitting the service data;

wherein the service data includes: at least one of a first type of data including data from a logical channel that supports triggering of the IDT flow and a second type of data including data from a logical channel that does not support triggering of the IDT flow.
The method of claim 1, wherein the traffic data comprises: the first type of data;

the triggering one of the IDT procedure and the connection establishment recovery procedure according to the type and/or the data volume of the service data includes:

triggering one of the IDT flow and the connection establishment recovery flow according to the data amount of the first type data.
The method of claim 2, wherein triggering one of the IDT procedure and the connection establishment recovery procedure according to the data amount of the first type of data comprises:

triggering the IDT flow when the data quantity of the first type of data is smaller than a first threshold value;

and triggering the connection establishment recovery process under the condition that the data volume of the first type of data is not less than the first threshold value.
The method of claim 1, wherein the traffic data comprises: the second type of data;

the triggering at least one of the IDT procedure and the connection establishment recovery procedure according to the type and/or the data volume of the service data includes:

triggering the connection establishment recovery process;

or, triggering one of the IDT procedure and the connection establishment recovery procedure according to the data amount of the second type data.
The method of claim 4, wherein triggering one of the IDT procedure and the connection establishment recovery procedure according to the amount of the second type of data comprises:

triggering the IDT flow when the data quantity of the second type of data is smaller than a second threshold value;

and triggering the connection establishment recovery process under the condition that the data volume of the second type of data is not less than the second threshold.
The method of claim 1, wherein the traffic data comprises: the first type of data and the second type of data;

the triggering one of the IDT procedure and the connection establishment recovery procedure according to the type and/or the data volume of the service data includes:

triggering the connection establishment recovery process;

or, according to the data volume of the first type data, triggering one of the IDT flow and the connection establishment recovery flow;

or, triggering one of the IDT flow and the connection establishment recovery flow according to the data volume of the first type data and the data volume of the second type data.
The method of claim 6, wherein triggering one of the IDT procedure and the connection establishment recovery procedure according to the amount of data of the first type of data comprises:

triggering the IDT flow when the data quantity of the first type of data is smaller than a first threshold value;

and triggering the connection establishment recovery process under the condition that the data volume of the first type of data is not less than a first threshold value.
The method of claim 6, wherein triggering one of the IDT procedure and the connection establishment recovery procedure according to the amount of the first type of data and the second type of data comprises:

under the condition that the data volume of the second type data is not smaller than a second threshold value, triggering the connection establishment recovery process;

triggering the IDT flow when the data volume of the second type data is smaller than the second threshold and the data volume of the first type data is smaller than a first threshold;

and triggering the connection establishment recovery process under the condition that the data volume of the second type of data is smaller than the second threshold and the data volume of the first type of data is not smaller than the first threshold.
The method according to any one of claims 1 to 8, further comprising:

receiving data transmission parameters configured by network equipment;

wherein the data transmission parameters include: supporting at least one of a logical channel triggering the IDT flow, a first threshold corresponding to the first type of data, and a second threshold corresponding to the second type of data.
A data transmission apparatus, applied to a terminal device, the apparatus comprising: the device comprises a triggering module and a transmission module;

the triggering module is used for triggering one of an IDT (IDT) flow and a connection establishment recovery flow according to the type of the service data and/or the size of the data volume;

the transmission module is configured to transmit the service data by using the IDT process; or, after recovering the radio resource control RRC connection according to the connection establishment recovery flow, transmitting the service data;

wherein the service data includes: at least one of a first type of data including data from a logical channel that supports triggering of the IDT flow and a second type of data including data from a logical channel that does not support triggering of the IDT flow.
The apparatus of claim 10, wherein the traffic data comprises: the first type of data;

the triggering module is configured to trigger one of the IDT procedure and the connection establishment recovery procedure according to the data volume of the first type of data.
The apparatus of claim 10,

the triggering module is used for triggering the IDT process under the condition that the data volume of the first type of data is smaller than a first threshold;

the triggering module is configured to trigger the connection establishment recovery procedure when the data amount of the first type of data is not less than the first threshold.
The apparatus of claim 12, wherein the traffic data comprises: the second type of data;

the triggering module is used for triggering the connection establishment recovery process;

or, the triggering module is configured to trigger one of the IDT procedure and the connection establishment recovery procedure according to the data volume of the second type of data.
The apparatus of claim 13,

the triggering module is used for triggering the IDT flow under the condition that the data volume of the second type data is smaller than a second threshold value;

the triggering module is configured to trigger the connection establishment recovery procedure when the data amount of the second type of data is not less than the second threshold.
The apparatus of claim 10, wherein the traffic data comprises: the first type of data and the second type of data;

the triggering module is used for triggering the connection establishment recovery process;

or, the triggering module is configured to trigger one of the IDT procedure and the connection establishment recovery procedure according to the data volume of the first type of data;

or, the triggering module is configured to trigger one of the IDT procedure and the connection establishment recovery procedure according to the data volume of the first type data and the data volume of the second type data.
The apparatus of claim 15,

the triggering module is used for triggering the IDT process under the condition that the data volume of the first type of data is smaller than a first threshold;

the triggering module is configured to trigger the connection establishment recovery procedure when the data amount of the first type of data is not less than a first threshold.
The apparatus of claim 15,

the triggering module is used for triggering the connection establishment recovery process under the condition that the data volume of the second type data is not less than a second threshold value;

the triggering module is used for triggering the IDT flow under the condition that the data volume of the second type of data is smaller than the second threshold and the data volume of the first type of data is smaller than a first threshold;

the triggering module is configured to trigger the connection establishment recovery procedure when the data amount of the second type of data is smaller than the second threshold and the data amount of the first type of data is not smaller than the first threshold.
The apparatus of any one of claims 10 to 17, further comprising: a receiving module;

the receiving module is used for receiving the data transmission parameters configured by the network equipment;

wherein the data transmission parameters include: supporting at least one of a logical channel triggering the IDT flow, a first threshold corresponding to the first type of data, and a second threshold corresponding to the second type of data.
A terminal device, characterized in that the terminal device comprises:

a processor;

a transceiver coupled to the processor;

a memory for storing executable instructions of the processor;

wherein the processor is configured to load and execute the executable instructions to implement the data transmission method of any of claims 1 to 9.
A computer-readable storage medium having stored thereon executable instructions that are loaded and executed by a processor to implement a data transmission method as claimed in any one of claims 1 to 9.