How to set the data transmission type and the device

Abstract

To provide a method for setting data transmission types and a terminal that allow the terminal to set data transmission types.SOLUTION: A method for setting data transmission types includes in a wireless communication system, a terminal setting a target transmission type based on at least one of the following: network placement, path loss, uplink data size, and back-off indication. The target transmission type includes one of the following: a small data transmission type based on placement permission, a small data transmission type based on random access, and a random access type.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present application relates to the field of communication technology, and particularly to a method and terminal for setting a data transmission type. [Background technology]

[0002] Small data transmission is mainly for machine type communications (MTC) and is characterized by transmitting small data packets of tens to hundreds of bits periodically or in bursts. It may require only uplink transmission function or only downlink transmission function, for example, sensor-type devices collect data, or actuator-type devices execute control commands, etc.

[0003] In a scenario in which a terminal in an unconnected state performs small data transmission (e.g., user plane data), the network side may simultaneously configure general random access resources, small data transmission resources based on random access, and small data transmission resources based on configuration permission to the terminal. In such a case, the terminal may perform small data transmission according to the small data transmission type based on configuration permission, or may perform small data transmission according to the small data transmission type based on random access.

[0004] However, the related art does not address the issue of how a terminal sets the data transmission type, which can easily lead to transmission problems due to misunderstandings between the terminal and the network side. Therefore, how a terminal sets the small data transmission type is an issue that needs to be resolved as soon as possible. Summary of the Invention

[0005] The embodiments of the present application provide a method and a terminal for setting a data transmission type, which can solve the problem in the related art that a terminal cannot set a data transmission type.

[0006] According to a first aspect, a method for setting a data transmission type is provided, the method including a terminal setting a target transmission type based on at least one of the following: network configuration, path loss, uplink data size, and backoff instruction, wherein the target transmission type includes one of a small data transmission type based on configuration permission, a small data transmission type based on random access, and a random access type.

[0007] According to a second aspect, there is provided a terminal, the terminal including: a transmission type setting module for setting a target transmission type based on at least one of a network configuration, a path loss, an uplink data size, and a backoff instruction, wherein the target transmission type includes one of a small data transmission type based on a configuration permission, a small data transmission type based on random access, and a random access type.

[0008] According to a third aspect, there is provided a terminal including a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, implementing a method according to the first aspect.

[0009] According to a fourth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implements the method of the first aspect.

[0010] According to a fifth aspect, there is provided a computer program product, the computer program product comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, implementing a method according to the first aspect.

[0011] According to a sixth aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface coupled to the processor, the processor being used to run a program or instructions to implement the method of the first aspect.

[0012] In an embodiment of the present application, the terminal may set a target transmission type based on at least one of the following: network configuration, path loss, uplink data size, and backoff instruction. The target transmission type includes one of a small data transmission type based on configuration permission, a small data transmission type based on random access, and a random access type, which solves the problem in the related art that the terminal cannot set the data transmission type, aligns the understanding between the terminal and the network side, and improves the performance of small data transmission. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram of a wireless communication system according to one embodiment of the present application; [Figure 2] 1 is a schematic flowchart of a method for setting a data transmission type according to one embodiment of the present application; [Figure 3] 1 is a structural schematic diagram of a terminal according to one embodiment of the present application; [Figure 4] 1 is a structural schematic diagram of a communication device according to one embodiment of the present application; [Figure 5] 1 is a structural schematic diagram of a terminal according to one embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0014] The following clearly and completely describes the technical solutions in the embodiments of the present application, in conjunction with the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without any creative efforts fall within the scope of protection of the present application.

[0015] The terms "first," "second," etc., used in the specification and claims of this application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It should be understood that such terms are interchangeable where appropriate, so that embodiments of this application may be performed in orders other than those illustrated or described herein, and that objects distinguished by "first" and "second" generally are of the same type and do not limit the number of objects; for example, a first object may be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected objects, and the character " / " generally indicates an "or" relationship between the related objects.

[0016] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the described techniques may be used in the above-mentioned systems and radio technologies as well as other systems and radio technologies. However, the following description describes New Radio (NR) systems for illustrative purposes, and uses NR terminology in most of the following description, and these technologies may be used in applications other than NR system applications, such as sixth generation (6G) systems. th This may be applied to 6G (6th Generation) communication systems.

[0017] 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be referred to as a terminal device or user equipment (UE), and may be a terminal side device such as a mobile phone, a tablet personal computer (PDA), a laptop computer (also called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), a wearable device, a vehicle-mounted equipment (VUE), a pedestrian-mounted equipment (PUE), etc., and wearable devices include a bracelet, an earphone, glasses, etc. It should be noted that the specific type of the terminal 11 in the embodiments of the present application is not limited. The network side equipment 12 may be a base station or a core network, where the base station may be called a Node B, an evolved Node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a next generation Node B (gNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or any other suitable term in the art, as long as the same technical effect is achieved, and the base station is not limited to a specific technical term. For illustrative purposes, in the embodiments of this application, only base stations in an NR system are taken as examples, but the specific type of base station is not limited.

[0018] Hereinafter, the method and terminal for setting a data transmission type according to the embodiments of the present application will be described in detail with reference to specific embodiments and application scenarios in conjunction with the drawings.

[0019] As shown in FIG. 2 , one embodiment of the present application provides a data transmission type setting method 200, which may be performed by a terminal, in other words, the method may be performed by software or hardware installed in the terminal, and the method includes the following steps:

[0020] In S202, the terminal sets a target transmission type based on at least one of the following: network configuration, path loss, uplink data size, and backoff indication.

[0021] Here, the target transmission type includes one of a configuration permission-based small data transmission type, a random access-based small data transmission type, and a random access type.

[0022] Optionally, in this embodiment, the terminal is in a non-connected state before setting the target transmission type, and the non-connected state includes an idle state (IDLE) or an inactive state (INACTIVE).

[0023] The above network configuration may be a network configuration transmission resource, and the transmission resource may include at least one of a small data transmission resource based on a configuration permission, a small data transmission resource based on four-step random access, a small data transmission resource based on two-step random access, a four-step random access resource, and a two-step random access resource.

[0024] The path loss may be determined by a terminal based on measurements of downlink reference signals.

[0025] The size of the uplink data may be the size of a small data packet waiting for transmission, for example, the size of available uplink user data, or the size of a finally generated Medium Access Control Protocol Data Unit (MAC PDU) containing the uplink user data, for example, the available uplink user data size, or a size including at least one header (i.e., at least one header selected from a Service Data Adaptation Protocol (SDAP) header, a Packet Data Convergence Protocol (PDCP) header, a Radio Link Control (RLC) header, and a Medium Access Control (MAC) header), or a size including a Medium Access Control Unit (MAC CE) required for at least one of a Buffer Status Report (BSR) and a Power Headroom Report (PHR).

[0026] The backoff instruction may be used to instruct the terminal that the uplink data transmission process of the small data transmission type based on random access is terminated or canceled.

[0027] In one example, S202 sets the target transmission type as the small data transmission type based on the configuration permission, for example, if the terminal has configured a small data transmission resource based on the configuration permission and the small data transmission resource based on the configuration permission is valid, or sets the target transmission type as the random access type if the terminal has not configured a small data transmission resource based on the configuration permission and has not configured a small data transmission resource based on random access.

[0028] For example, if the measurement value of the terminal downlink path loss reference is higher than a first channel quality threshold, the target transmission type is set as a small data transmission type based on the placement permission, and if the measurement value of the terminal downlink path loss reference is higher than a second channel quality threshold, the target transmission type is set as a small data transmission type based on the random access.

[0029] In this embodiment, the measurement value of the downlink path loss reference may include, but is not limited to, at least one of Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Noise Ratio (SINR), Channel Occupancy Rate (CO), Received Signal Strength Indication (RSSI), Channel Busy Rate (CBR), etc.

[0030] For example, the size of the uplink data is equal to or less than a first transport block size (TBS) threshold, and the terminal sets the target transmission type as a small data transmission type based on the configuration permission, or the size of the uplink data is equal to or less than a second TBS threshold, and the terminal sets the target transmission type as a small data transmission type based on the random access.

[0031] Alternatively, for example, the upper layer of the terminal does not receive a backoff instruction from the lower layer and sets the target transmission type as the small data transmission type based on the random access.

[0032] It should be noted that the lower layers referred to in each embodiment of this specification may be a Medium Access Control (MAC) layer or a physical layer, and the higher layer / upper layer referred to in each embodiment of this specification may be a Radio Resource Control (RRC) layer or an RRC sublayer.

[0033] The above example shows that the terminal often sets the target transmission type based on one of the following: network configuration, path loss, uplink data size, and backoff indication; in practice, the terminal can set the target transmission type based on at least both of the above.

[0034] For example, if the terminal configures small data transmission resources based on the configuration permission and the measurement value of the downlink path loss reference is higher than a first channel quality threshold, the target transmission type is set as the small data transmission type based on the configuration permission.

[0035] For example, if the terminal configures small data transmission resources based on random access, and the measurement value of the downlink path loss reference is higher than a second channel quality threshold, and no backoff instruction has been received, the target transmission type is set as the small data transmission type based on random access.

[0036] For example, if the terminal allocates small data transmission resources based on the allocation permission, and the measurement value of the downlink path loss reference is higher than the first channel quality threshold, and the size of the uplink data is less than or equal to the first TBS threshold, the target transmission type is set as the small data transmission type based on the allocation permission.

[0037] The small data transmission type based on the configuration permission mentioned in each embodiment of this specification may specifically be configured by a network side device through a Radio Resource Control (RRC) release message (RRC Release message) to configure an uplink permission for a terminal, and includes parameters such as a periodicity, a time domain or frequency domain or code domain or airspace resource of a Physical Uplink Shared Channel (PUSCH), i.e., the small data transmission resource based on the above-mentioned configuration permission.

[0038] After setting the target transmission type as a small data transmission type based on the configuration grant, the terminal can perform uplink data transmission by adopting the configured uplink grant, where the uplink grant may be UE-specific. Specifically, the terminal transmits Data Radio Bearer (DRB) data and / or a Signaling Radio Bearer (SRB) request message (e.g., an RRC resume request message) on a dedicated PUSCH resource. After transmitting the PUSCH, the terminal can obtain scheduling information corresponding to a Physical Downlink Shared Channel (PDSCH) by monitoring a PDCCH scrambled by a terminal identifier (e.g., a C-RNTI) specific to the terminal in a corresponding Physical Downlink Control Channel (PDCCH) monitoring opportunity, where the PDSCH includes DRB data and / or an SRB response message (e.g., an RRC Release message) of the terminal.

[0039] The small data transmission type based on random access mentioned in each embodiment of this specification may include a small data transmission type based on two-step random access, and may further include a small data transmission type based on four-step random access.

[0040] The small data transmission type based on random access referred to in each embodiment of this specification specifically includes a network side device configuring uplink transmission resources for a terminal by a broadcast message, which includes MsgA Physical Random Access Channel (PRACH) resources and MsgA PUSCH resources for a small data transmission type corresponding to two-step random access, or parameter configuration of Msg1 PRACH resources and Msg3 PUSCH for a small data transmission type corresponding to four-step random access, i.e., the small data transmission resources based on random access mentioned above.

[0041] After setting the target transmission type as the small data transmission type based on the two-step random access, the terminal can transmit an MsgA PRACH and an MsgA PUSCH by selecting resources of the small data transmission type corresponding to the two-step random access. Specifically, the terminal transmits DRB data and / or a signaling SRB request message (e.g., an RRC resume request message) in the MsgA PUSCH. After transmitting the MsgA PRACH and / or the MsgA PUSCH, the terminal can obtain scheduling information corresponding to the MsgB PDSCH by monitoring a PDCCH scrambled with a specific terminal identifier (e.g., an MsgB-RNTI) in a corresponding PDCCH monitoring occasion, where the MsgB PDSCH includes the DRB data and / or an SRB response message (e.g., an RRC Release message) and / or a contention resolution identifier of the terminal.

[0042] After setting the target transmission type as the small data transmission type based on the 4-step random access, the terminal can transmit Msg1 PRACH by selecting a resource of the small data transmission type corresponding to the 4-step random access. Specifically, after transmitting this Msg1 PRACH, the terminal can obtain scheduling information corresponding to a Msg2 Random Access Response (RAR) by monitoring a PDCCH scrambled with a specific terminal identifier (e.g., RA-RNTI) in a corresponding PDCCH monitoring occasion, where the Msg2 RAR includes an uplink grant for transmitting a Msg3 PUSCH. The terminal then transmits DRB data and / or a signaling SRB request message (e.g., an RRC resume request message) in the Msg3 PUSCH. After transmitting this Msg3 PUSCH, the terminal can obtain scheduling information corresponding to a Msg4 PDSCH by monitoring a PDCCH scrambled with a specific terminal identifier (e.g., TC-RNTI) in a corresponding PDCCH monitoring occasion, where the Msg4 PDSCH includes the DRB data and / or an SRB response message (e.g., an RRC Release message) and / or a contention resolution identifier of the terminal.

[0043] The random access types mentioned in the embodiments of this specification specifically allow a network side device to configure parameter configuration of MsgA PRACH resources and MsgA PUSCH resources for two-step random access or parameter configuration of Msg1 PRACH resources and Msg3 PUSCH for four-step random access for a terminal through a broadcast message. After setting the target transmission type as the random access type, the terminal can only transmit an SRB response message in MsgA PUSCH or Msg3 PUSCH, but cannot carry transmitted DRB data, i.e., cannot perform uplink data transmission in the user plane.

[0044] In practice, the small data transmission type based on the random access may perform small data transmission (e.g., DRB data transmission), but may not perform small data transmission (e.g., not carrying transmitted DRB data). The small data transmission type based on the allocation permission and the small data transmission type or random access type based on the random access generally perform only small data transmission.

[0045] In an embodiment of the present application, the terminal may set a target transmission type based on at least one of the following: network configuration, path loss, uplink data size, and backoff instruction, and the target transmission type includes a small data transmission type based on configuration permission, a small data transmission type based on random access, or a random access type, which solves the problem in the related art that the terminal cannot set the data transmission type, aligns the understanding between the terminal and the network side, and improves the performance of small data transmission.

[0046] To explain in detail the method for setting a data transmission type according to the embodiment of the present application, the following description will be given in conjunction with several specific embodiments.

[0047] Example 1 In this embodiment, the terminal setting the target transmission type based on at least one of the following includes setting the target transmission type as a small data transmission type based on a configuration permission based on at least one of the following:

[0048] 1) The small data transmission resource based on the allocation permission is allocated. For example, the network side explicitly allocates the small data transmission resource based on the allocation permission for the bandwidth part (BWP). The small data transmission resource based on the allocation permission is related to the synchronization signal and the physical broadcast signal (SSB).

[0049] 2) The small data transmission resource based on the configuration grant is valid. The term "valid" in this example may be understood as meaning that the small data transmission resource based on the configuration grant to be configured is available for use, and may be considered valid, for example, when the network side configures the small data transmission resource based on the configuration grant, and / or when a specific timer (e.g., a time alignment timer associated with the small data transmission type based on the configuration grant) is running, and / or when the small data transmission resource based on the configuration grant is within an uplink slot (UL slot) and does not collide with an SSB. Also, for example, the term "valid" above may be understood as meaning that the terminal has reserved the small data transmission resource based on the configuration grant and has not released the small data transmission resource based on the configuration grant.

[0050] 3) The measured value of the downlink path loss reference is higher than a first channel quality threshold, for example, the measured value of the downlink reference signal (DL RS) is higher than a first channel quality threshold.

[0051] 4) The path loss is less than a first channel quality threshold.

[0052] It should be noted that, in actual applications, the first channel quality thresholds mentioned in the above two examples 3) and 4) generally only hold true, or the above 3) and 4) are two mutually exclusive solutions, and generally, both do not exist at the same time, and the values ​​of the first channel quality thresholds mentioned in 3) and 4) may not be equal.

[0053] 5) The size of the uplink data is less than or equal to a first transport block size (TBS) threshold. In this example, how the terminal determines the size of the uplink data may be implemented depending on the terminal.

[0054] Optionally, in this embodiment, setting the target transmission type as the placement permission-based small data transmission type further includes setting variable small data transmission to true.

[0055] It should be noted that setting variable small data transmission to true generally means that the terminal is configured to perform uplink data transmission according to the small data transmission type based on configuration permission or according to the small data transmission type based on random access. Setting variable small data transmission to false generally means that the terminal is not configured to perform uplink data transmission according to the above two transmission types, but initiates an RRC connection recovery process according to the random access type, and performs uplink data transmission after the RRC connection is recovered.

[0056] According to this embodiment, when small data transmission resources based on random access (including small data transmission based on 4-step random access and small data transmission based on 2-step random access) and small data transmission resources based on configuration permission are simultaneously configured in a terminal, the small data transmission type based on configuration permission is preferentially selected to perform uplink data transmission, thereby facilitating full utilization of the already allocated uplink resources.

[0057] Optionally, this embodiment includes: 1) the target transmission type is set as a small data transmission type based on the placement permission; 2) The value of variable small data transmission is true, which may be specifically achieved by setting variable small data transmission to true in the above example, based on at least one of the steps, an upper layer (e.g., RRC layer) of the terminal instructs a lower layer (e.g., MAC layer, physical layer) to perform an uplink data transmission process of small data transmission type based on the configuration permission.

[0058] Example 2 In this embodiment, the terminal setting the target transmission type based on at least one of the following includes setting the target transmission type as a random access-based small data transmission type based on at least one of the following:

[0059] 1) Configuring small data transmission resources based on random access. For example, small data transmission resources based on random access for BWP are configured (e.g., configuring small data transmission resources based on four-step random access and / or small data transmission resources based on two-step random access for BWP), but setting the small data transmission type as the small data transmission type based on random access, and optionally setting variable small data transmission as true.

[0060] 2) The measurement value of the downlink path loss reference is higher than the second channel quality threshold, for example, the measurement value of the downlink PL RS is higher than the second channel quality threshold.

[0061] 3) The path loss is less than a second channel quality threshold.

[0062] It should be noted that, in actual applications, the second channel quality thresholds mentioned in the above two examples 3) and 4) generally only hold true, or the above 3) and 4) are two mutually exclusive solutions, and generally, both do not exist at the same time, and the values ​​of the second channel quality thresholds mentioned in 3) and 4) may not be equal.

[0063] 4) The size of the uplink data is equal to or less than the second TBS threshold.

[0064] 5) The backoff indication to indicate that the uplink data transmission process of the random access-based small data transmission type is terminated or canceled has not been received from the lower layer.

[0065] Optionally, in this embodiment, setting the target transmission type as the random access based small data transmission type further includes setting variable small data transmission to true.

[0066] Optionally, this embodiment further includes the step of: an upper layer of the terminal instructing a lower layer to perform an uplink data transmission process of a small data transmission type based on random access based on at least one of the following:

[0067] 1) The target transmission type is set as the random access-based small data transmission type.

[0068] 2) The value of variable small data transmission is true, which may be specifically realized by the above example operation of setting variable small data transmission to true.

[0069] Example 3 In this embodiment, the terminal setting the target transmission type based on at least one of the following: 1) Small data transmission resources based on the allocation permission have not been allocated; and 2) Small data transmission resources based on random access are not allocated; and 3) The small data transmission resource based on the allocation permission is not available; and 4) the measured value of the downlink path loss reference is not higher than the first channel quality threshold; 5) the path loss is greater than a first channel quality threshold; and 6) the measured value of the downlink path loss reference is not higher than a second channel quality threshold; 7) the path loss is greater than a second channel quality threshold; and 8) The size of the uplink data is greater than a first TBS threshold; and 9) The size of the uplink data is greater than a second TBS threshold; and 10) receiving the backoff instruction from a lower layer, the backoff instruction being used to indicate that the uplink data transmission process of the random access-based small data transmission type is terminated or canceled, and setting the target transmission type as a random access type based on at least one of the above.

[0070] Optionally, in this embodiment, setting the target transmission type as a random access type further includes setting variable small data transmission to false.

[0071] It should be noted that the three embodiments introduced above may be combined to form other embodiments of the present application. For example, in one new combined embodiment, if all of the conditions 1) to 5) listed in embodiment 1 are satisfied, the terminal sets the target transmission type as a small data transmission type based on the configuration permission.

[0072] If at least one of the conditions 1) to 5) listed in Example 1 is not met and all of the conditions 1) to 5) listed in Example 2 are met, the terminal sets the target transmission type as the small data transmission type based on the random access.

[0073] If at least one of the conditions 1) to 5) listed in Example 1 is not met, and at least one of the conditions 1) to 5) listed in Example 2 is not met, and at least one of the conditions 1) to 10) listed in Example 3 is met, the terminal sets the target transmission type as the random access type.

[0074] Optionally, before the terminal in each of the embodiments sets the target transmission type based on at least one of the following, the method further includes initiating a first Radio Resource Control (RRC) connection recovery process, where the first RRC connection recovery process is used to perform uplink data transmission according to the configuration grant-based small data transmission type or the random access-based small data transmission type. That is, when the terminal sets the target transmission type as the configuration grant-based small data transmission type or the random access-based small data transmission type, the terminal can perform uplink data transmission according to the first RRC connection recovery process.

[0075] Optionally, the above embodiment further includes, when a second RRC connection recovery process is requested during the progress of the first RRC connection recovery process and the target transmission type is a small data transmission type based on the configuration grant, continuing to perform the first RRC connection recovery process or starting the second RRC connection recovery process. Optionally, the second RRC connection recovery process may be used by the terminal to recover the RRC connection and recover SRB1. Optionally, the second RRC connection recovery process may be used by the terminal to establish an RRC connection and transition to an RRC connected state.

[0076] When the second RRC connection recovery process is initiated, the method further includes performing a small data transmission backoff process, which is used to terminate, cancel, or suspend an uplink data transmission process of a small data transmission type based on the configuration grant. For a detailed introduction to the small data transmission backoff process, please refer to the following examples.

[0077] Based on the introduction of the above several embodiments, when the target transmission type is set as a small data transmission type based on configuration permission, the method further includes a step of selecting an uplink carrier to be used for uplink data transmission according to the small data transmission type based on configuration permission.

[0078] Specifically, selecting an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission includes, in a first case, selecting a supplementary uplink (SUL) as an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission, and, in a second case, selecting a normal uplink (NUL) as an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission.

[0079] The first case includes a case where the measured downlink path loss reference is lower than a third channel quality threshold, and the second case is a case other than the first case, for example, the second case is a case where the measured downlink path loss reference is equal to or greater than a third channel quality threshold, or other cases.

[0080] Based on the introduction of the above several embodiments, if the target transmission type is a small data transmission type based on the configuration permission, the method further includes at least one of the following:

[0081] 1) When a first timer expires, a lower layer of the terminal sends a failure indication to a higher layer. Here, the first timer is used to monitor downlink control information after performing uplink data transmission according to a small data transmission type based on a configuration permission, and the failure indication is used to indicate that the uplink data transmission process of the small data transmission type based on the configuration permission is unsuccessful. The unsuccessful uplink data transmission process may be, for example, that a network-side response message (e.g., the first timer expires) is not received within a certain period of time.

[0082] 2) If a protocol data unit waiting for transmission is not available, the lower layer of the terminal sends an uplink skip indication to the upper layer, which is used to indicate that an uplink skip has occurred in the uplink data transmission process of the small data transmission type based on the configuration permission.

[0083] 3) Setting the value of a first transmission counter to 0. The first transmission counter is used to count the number of failures in performing an uplink data transmission process of the small data transmission type based on the configuration grant.

[0084] 4) When the upper layer of the terminal receives a failure indication from the lower layer, it increments a first transmission counter by one.

[0085] 5) If the value of the first transmission counter is equal to the first count threshold, perform a small data transmission backoff process.

[0086] 6) Setting the value of a second transmission counter to 0. The second transmission counter is used to count the number of uplink skips performed for performing an uplink data transmission process of a small data transmission type based on the configuration permission.

[0087] 7) When the upper layer of the terminal receives an uplink skip instruction from the lower layer, it increments the second transmission counter by one.

[0088] 8) If the value of the second transmission counter is equal to the second count threshold, perform a small data transmission backoff process.

[0089] It should be noted that only one of the above listed items 1) to 8) may be performed, or multiple items may be performed.

[0090] For example, the terminal first sets the value of the first transmission counter to 0 according to 3), then based on the first timer timing out according to 1), the lower layer of the terminal transmits a failure indication to the upper layer (e.g., the RRC layer), then according to 4), if the upper layer of the terminal receives a failure indication from the lower layer, it adds 1 to the first transmission counter, and finally according to 5), if the value of the first transmission counter is equal to the first count threshold, it performs a small data transmission backoff process.

[0091] For example, the terminal first sets the value of the second transmission counter to 0 according to 6), then based on the fact that no protocol data unit is waiting for transmission according to 2), the lower layer of the terminal transmits an uplink skip instruction to the upper layer, then according to 7), if the upper layer of the terminal receives an uplink skip instruction from the lower layer, it adds 1 to the second transmission counter, and finally according to 8), if the value of the second transmission counter is equal to the second count threshold, it performs a small data transmission backoff process.

[0092] Based on the introduction of the above several embodiments, when the target transmission type is the random access-based small data transmission type, the method includes: 1) the measured downlink path loss reference is higher than a fourth channel quality threshold; and 2) Small data transmission resources are allocated based on two-step random access; 3) the size of the uplink data is less than or equal to a third TBS threshold, and setting the target transmission type as a small data transmission type based on two-step random access based on at least one of the above.

[0093] Based on the introduction of the above several embodiments, when the target transmission type is the random access-based small data transmission type, the method includes: 1) the measured value of the downlink path loss reference is not higher than a fourth channel quality threshold; 2) Small data transmission resources are allocated based on four-step random access; 3) the size of the uplink data is greater than a third TBS threshold, and setting the target transmission type as a small data transmission type based on four-step random access based on at least one of the above.

[0094] Optionally, if the target transmission type is the random access-based small data transmission type, the method further includes at least one of the following:

[0095] 1) The target transmission type is set as a small data transmission type based on 2-step random access, and the value of the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) is equal to a third count threshold plus 1, based on at least one of the following:

[0096] 2) If the value of the preamble transmission counter is equal to the third count threshold plus 1, the lower layer of the terminal sends a backoff instruction to the upper layer.

[0097] The third count threshold mentioned in the above two examples indicates the maximum number of failures that the terminal will encounter in small data transmission according to the small data transmission type based on two-step random access.

[0098] 3) If the value of the preamble transmission counter is equal to the fourth count threshold plus 1, the lower layer of the terminal sends a backoff instruction to the upper layer.

[0099] The fourth count threshold indicates the maximum number of failures that the terminal will attempt to transmit small data using the small data transmission type based on four-step random access.

[0100] 4) The upper layer of the terminal executes a small data transmission backoff process based on receiving a backoff instruction from the lower layer.

[0101] Optionally, performing the small data transmission backoff process introduced in each of the above embodiments includes at least one of the following:

[0102] 1) Starting or restarting a second timer (eg, timer 319, T319), which is used to indicate the maximum length of time the terminal will perform an RRC connection recovery process.

[0103] 2) Start sending RRC recovery request messages.

[0104] 3) Set Transmit Variable Small Data to false.

[0105] 4) Release small data transmission resources based on allocation permission.

[0106] 5) Discarding small data transmission resources based on the stored allocation permission.

[0107] Initiating the transmission of the RRC recovery request message referred to in 2) above includes, for example, an upper layer generating an RRC recovery request message and passing it to a lower layer, and if the target transmission type is the random access-based small data transmission type, the lower layer performs a random access initialization process (for example, clearing the Msg 3 / Msg A cache) and performs the RRC recovery process through the random access process. Also, for example, if the upper layer generates an RRC recovery request message and passes it to a lower layer, and if the target transmission type is the configuration grant-based small data transmission type, the lower layer clears the HARQ cache related to the configuration grant, performs a random access initialization process, and performs the RRC recovery process through the random access process.

[0108] In the above cases 4) and 5), performing the small data transmission backoff process further includes releasing small data transmission resources based on the placement authorization or discarding small data transmission resources based on the stored placement authorization when the value of the first transmission counter is equal to the first count threshold, or releasing small data transmission resources based on the placement authorization and discarding small data transmission resources based on the stored placement authorization when the value of the first transmission counter is equal to the first count threshold.

[0109] In the above cases 4) and 5), performing the small data transmission backoff process further includes releasing small data transmission resources based on the placement authorization or discarding small data transmission resources based on the stored placement authorization when the value of the second transmission counter is equal to the second count threshold, or releasing small data transmission resources based on the placement authorization and discarding small data transmission resources based on the stored placement authorization when the value of the second transmission counter is equal to the second count threshold.

[0110] In each of the above embodiments, before the terminal sets a target transmission type based on at least one of the following, the method further includes receiving configuration information for the terminal to configure at least one of the following:

[0111] 1) Small data transmission resource based on configuration permission. For example, the network side configures a small data transmission resource based on configuration permission for a terminal that has been converted from a connected state to an inactive state by an RRC release message, and this resource includes a PUSCH resource dedicated to the terminal for transmitting small data transmission by the inactive terminal.

[0112] 2) Small data transmission resources based on 4-step random access. For example, the network side configures small data transmission resources based on 4-step random access to INACTIVE terminals via a system broadcast SIB1 message, and these resources include Physical Random Access Channel (PRACH) resources for INACTIVE terminals to transmit small data transmissions.

[0113] 3) Small data transmission resources based on two-step random access. For example, the network side configures small data transmission resources based on two-step random access for inactive terminals through a system broadcast SIB1 message, and the resources include PRACH resources and PUSCH resources for the inactive terminals to transmit small data transmissions.

[0114] Optionally, the configuration information is further used to configure at least one of the following for the terminal:

[0115] 1) A first channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on the configuration permission.

[0116] Based on this first channel quality threshold, the terminal can set the small data transmission type as a small data transmission type based on a configuration grant, where the first channel quality threshold includes, but is not limited to, an indicator characterizing channel quality, such as a signal-to-noise ratio (SINR), a reference signal received power (RSRP), a reference signal received quality (RSRQ), etc. Optionally, the first channel quality threshold is configured only when the network side configures small data transmission resources based on the configuration grant for a BWP (e.g., an initial BWP).

[0117] 2) A second channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on the random access (four-step random access or two-step random access).

[0118] Optionally, the second channel quality threshold is configured only when the network side configures the small data transmission resource based on the 4-step random access or the small data transmission resource based on the 2-step random access for the BWP (e.g., the initial BWP).

[0119] 3) A third channel quality threshold for the terminal to select the SUL as an uplink carrier to be used for uplink data transmission by a small data transmission type based on a configuration permission.

[0120] 4) A fourth channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on two-step random access.

[0121] Optionally, the fourth channel quality threshold is configured only when the network side configures the small data transmission resource based on the 4-step random access and the small data transmission resource based on the 2-step random access for the BWP (e.g., initial BWP).

[0122] 5) A first TBS threshold that instructs the terminal to use a maximum TBS corresponding to performing small data transmission according to the small data transmission type based on the allocation permission.

[0123] This first TBS threshold may indicate that the terminal is suitable to use the maximum TBS corresponding to performing small data transmission (i.e., uplink data transmission) according to the small data transmission type based on the configuration permission.

[0124] Optionally, the first TBS threshold is configured only when the network side allocates small data transmission resources based on the allocation grant for a BWP (eg, initial BWP).

[0125] 6) A second TBS threshold that instructs the terminal to use a maximum TBS corresponding to small data transmission using the random access-based small data transmission type.

[0126] This second TBS threshold may indicate that the terminal is suitable for using the largest TBS corresponding to performing small data transmission (i.e., uplink data transmission) using a small data transmission type based on random access.

[0127] Optionally, this first TBS threshold is configured only when the network side configures the small data transmission resource based on the 4-step random access or the small data transmission resource based on the 2-step random access for the BWP (e.g., initial BWP).

[0128] 7) A third TBS threshold that instructs the terminal to use a maximum TBS corresponding to small data transmission using a small data transmission type based on two-step random access.

[0129] This third TBS threshold indicates that the terminal is suitable for using the largest TBS corresponding to performing small data transmission (i.e., uplink data transmission) using the small data transmission type based on two-step random access.

[0130] 8) A first count threshold that indicates to the terminal the maximum number of failures in performing an uplink data transmission process using a small data transmission type based on a configuration permission.

[0131] 9) A second count threshold that indicates to the terminal the maximum number of uplink skips when performing an uplink data transmission process using a small data transmission type based on the configuration permission.

[0132] 10) A third count threshold that indicates to the terminal the maximum number of failures in performing small data transmission using a small data transmission type based on two-step random access.

[0133] 11) A fourth count threshold that indicates to the terminal the maximum number of failures in performing small data transmission according to the small data transmission type based on four-step random access.

[0134] It should be noted that in the method for setting a data transmission type according to the embodiment of the present application, the execution body may be a terminal or a control module for executing the method for setting a data transmission type in the terminal. In the embodiment of the present application, the method for setting a data transmission type by a terminal is taken as an example to describe the terminal according to the embodiment of the present application.

[0135] FIG. 3 is a structural schematic diagram of a terminal according to an embodiment of the present application. As shown in FIG. 3, the terminal 300 includes a transmission type setting module 302 that may be used to set a target transmission type based on at least one of network configuration, path loss, uplink data size, and backoff instruction, where the target transmission type includes one of a small data transmission type based on configuration permission, a small data transmission type based on random access, and a random access type.

[0136] In an embodiment of the present application, the terminal may set a target transmission type based on at least one of network configuration, path loss, uplink data size, and backoff instruction, and the target transmission type may include a small data transmission type based on configuration permission, a small data transmission type based on random access, or a random access type, which solves the problem in the related art that the terminal cannot set the data transmission type, aligns the understanding between the terminal and the network side, and improves the performance of small data transmission.

[0137] Optionally, in one embodiment, the transmission type setting module 302 may be used to set the target transmission type as the small data transmission type based on the configuration permission based on at least one of: a small data transmission resource based on the configuration permission is configured; a small data transmission resource based on the configuration permission is valid; a measurement value of a downlink path loss reference is higher than a first channel quality threshold; the path loss is smaller than a first channel quality threshold; and the size of the uplink data is less than a first TBS threshold.

[0138] Optionally, in one embodiment, the transmission type setting module 302 may further be used to set variable small data transmission to true.

[0139] Optionally, as one embodiment, the transmission type setting module 302 may further be used to instruct a lower layer to perform an uplink data transmission process of a small data transmission type based on the configuration permission based on at least one of the target transmission type being set as a small data transmission type based on the configuration permission and the value of the variable small data transmission being true.

[0140] Optionally, as one embodiment, the transmission type setting module 302 may be used to set the target transmission type as the random access-based small data transmission type based on at least one of the following: a random access-based small data transmission resource is allocated; a measured value of a downlink path loss reference is higher than a second channel quality threshold; the path loss is smaller than a second channel quality threshold; the size of uplink data is less than a second TBS threshold; and the backoff indication to indicate that the uplink data transmission process of the random access-based small data transmission type is terminated or canceled has not been received from a lower layer.

[0141] Optionally, in one embodiment, the transmission type setting module 302 may further be used to set variable small data transmission to true.

[0142] Optionally, as one embodiment, the transmission type setting module 302 may further be used to instruct a lower layer to perform an uplink data transmission process of a small data transmission type based on random access based on at least one of the target transmission type being set as the small data transmission type based on random access and the value of variable small data transmission being true.

[0143] Optionally, as one embodiment, the transmission type setting module 302 may be used to set the target transmission type as the random access type based on at least one of: a small data transmission resource based on a configuration permission is not configured; a small data transmission resource based on random access is not configured; a small data transmission resource based on a configuration permission is not valid; a measured value of a downlink path loss reference is not higher than a first channel quality threshold; the path loss is greater than a first channel quality threshold; a measured value of a downlink path loss reference is not higher than a second channel quality threshold; the path loss is greater than a second channel quality threshold; the size of uplink data is greater than a first TBS threshold; the size of uplink data is greater than a second TBS threshold; and receiving the backoff instruction from a lower layer, wherein the backoff instruction is used to indicate that the uplink data transmission process of the small data transmission type based on random access is terminated or canceled.

[0144] Optionally, in one embodiment, the transmission type setting module 302 may further be used to set variable small data transmission to false.

[0145] Optionally, in one embodiment, the terminal 300 further includes an initiation module for initiating a first RRC connection recovery process, and the first RRC connection recovery process is used to perform uplink data transmission according to the small data transmission type based on the configuration permission or the small data transmission type based on the random access.

[0146] Optionally, as one embodiment, the activation module may be further used to continue performing the first RRC connection recovery process or initiate the second RRC connection recovery process when a second RRC connection recovery process is requested during the progress of the first RRC connection recovery process and the target transmission type is a small data transmission type based on the configuration permission.

[0147] Optionally, as one embodiment, when initiating the second RRC connection recovery process, the transmission type setting module 302 may further be used to perform a small data transmission backoff process, which is used to terminate, cancel, or suspend an uplink data transmission process of the small data transmission type based on the configuration permission.

[0148] Optionally, as one embodiment, when the target transmission type is a small data transmission type based on the configuration permission, the transmission type setting module 302 may further be used to select an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission.

[0149] Optionally, as one embodiment, selecting an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission includes, in a first case, selecting a supplemental uplink SUL as the uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission, and in a second case, selecting a normal uplink NUL as the uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration permission, wherein the first case includes a case where the measurement value of the downlink path loss reference is lower than a third channel quality threshold, and the second case is a case other than the first case.

[0150] Optionally, in one embodiment, if the target transmission type is a small data transmission type based on the configuration permission, the transmission type setting module 302 further includes: a lower layer of the terminal sending a failure indication to an upper layer based on a first timer timing out; a lower layer of the terminal sending an uplink skip indication to an upper layer based on a protocol data unit awaiting transmission not being obtained; setting a value of a first transmission counter to 0; when the upper layer of the terminal receives a failure indication from the lower layer, incrementing the first transmission counter by 1; and when the value of the first transmission counter is equal to a first count threshold, performing a small data transmission backoff process; setting a value of a second transmission counter to 0; when the upper layer of the terminal receives an uplink skip indication from the lower layer, incrementing the second transmission counter by 1; and when the value of the second transmission counter is equal to a second count threshold. , performing a small data transmission backoff process, wherein the first timer is used to monitor downlink control information after performing uplink data transmission according to a small data transmission type based on the configuration permission, the failure indication is used to indicate that the uplink data transmission process of the small data transmission type based on the configuration permission is unsuccessful, the uplink skip indication is used to indicate that an uplink skip has occurred in the uplink data transmission process of the small data transmission type based on the configuration permission, the first transmission counter is used to count the number of failures in performing the uplink data transmission process of the small data transmission type based on the configuration permission, and the second transmission counter is used to count the number of uplink skips in performing the uplink data transmission process of the small data transmission type based on the configuration permission.

[0151] Optionally, as one embodiment, when the target transmission type is the small data transmission type based on random access, the transmission type setting module 302 may be further used to set the target transmission type as the small data transmission type based on two-step random access based on at least one of: the measurement value of the downlink path loss reference is higher than a fourth channel quality threshold; a small data transmission resource based on two-step random access is allocated; and the size of the uplink data is less than or equal to a third TBS threshold.

[0152] Optionally, as one embodiment, if the target transmission type is the small data transmission type based on random access, the transmission type setting module 302 may be further used to set the target transmission type as the small data transmission type based on 4-step random access based on at least one of: the measurement value of the downlink path loss reference is not higher than a fourth channel quality threshold; a small data transmission resource based on 4-step random access is allocated; and the size of the uplink data is greater than a third TBS threshold.

[0153] Optionally, in one embodiment, if the target transmission type is the random access-based small data transmission type, the transmission type setting module 302 further comprises: 1) setting the target transmission type as a small data transmission type based on four-step random access based on at least one of the following: the target transmission type is set as a small data transmission type based on two-step random access; and the value of the preamble transmission counter is equal to a third count threshold plus one; 2) when the value of the preamble transmission counter is equal to a third count threshold plus one, the lower layer of the terminal sends a backoff instruction to the upper layer; 3) when the value of the preamble transmission counter is equal to a fourth count threshold plus one, the lower layer of the terminal sends a backoff instruction to the upper layer; 4) The upper layer of the terminal performs a small data transmission backoff process based on receiving a backoff instruction from a lower layer.

[0154] Optionally, as one embodiment, performing the small data transmission backoff process includes at least one of starting or restarting a second timer to indicate the maximum length of time for the terminal to perform an RRC connection recovery process, starting to transmit an RRC recovery request message, setting variable small data transmission to false, releasing small data transmission resources based on the configuration permission, and discarding small data transmission resources based on the stored configuration permission.

[0155] Optionally, as one embodiment, performing the small data transmission backoff process further includes releasing small data transmission resources based on the placement authorization or discarding small data transmission resources based on the stored placement authorization when the value of the first transmission counter is equal to the first count threshold, or releasing small data transmission resources based on the placement authorization and discarding small data transmission resources based on the stored placement authorization when the value of the first transmission counter is equal to the first count threshold.

[0156] Optionally, as one embodiment, performing the small data transmission backoff process further includes releasing small data transmission resources based on the placement authorization or discarding small data transmission resources based on the stored placement authorization when the value of the second transmission counter is equal to the second count threshold, or releasing small data transmission resources based on the placement authorization and discarding small data transmission resources based on the stored placement authorization when the value of the second transmission counter is equal to the second count threshold.

[0157] Optionally, in one embodiment, the terminal 300 may small data transmission resources based on allocation permission; Small data transmission resources based on four-step random access; and a small data transmission resource based on two-step random access.

[0158] Optionally, in one embodiment, the configuration information further comprises for the terminal: 1) a first channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on the configuration permission; 2) a second channel quality threshold for the terminal to set the target transmission type as the random access-based small data transmission type; and 3) a third channel quality threshold for the terminal to select the SUL as an uplink carrier to be used for uplink data transmission according to a small data transmission type based on the configuration permission; and 4) a fourth channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on two-step random access; 5) a first TBS threshold that instructs the terminal to use a maximum TBS corresponding to performing small data transmission according to the small data transmission type based on the allocation permission; and 6) a second TBS threshold that instructs the terminal to use a maximum TBS corresponding to small data transmission using the small data transmission type based on the random access; and 7) a third TBS threshold that instructs the terminal to use a maximum TBS corresponding to small data transmission using a small data transmission type based on two-step random access; 8) a first count threshold indicating the maximum number of failures that the terminal may encounter when performing an uplink data transmission process using a small data transmission type based on the configuration permission; 9) a second count threshold indicating the maximum number of uplink skips for the terminal to perform an uplink data transmission process according to the small data transmission type based on the configuration permission; 10) a third count threshold indicating to the terminal the maximum number of failures in small data transmission according to a small data transmission type based on two-step random access; 11) a fourth count threshold indicating the maximum number of failures for the terminal to perform small data transmission using the small data transmission type based on four-step random access.

[0159] The terminal 300 according to the embodiment of the present application can refer to the flow corresponding to the method 200 according to the embodiment of the present application, and each unit / module and the above-mentioned other operations and / or functions in the terminal 300 are for realizing the corresponding flow in the method 200, respectively, and can achieve the same or equivalent technical effects, and for the sake of brevity, they will not be further described here.

[0160] The terminal in the embodiment of the present application may be a component, an integrated circuit, or a chip in the terminal. The terminal may be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal may include, but is not limited to, the types of terminals 11 listed above. The non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, a self-service machine, etc., and the embodiment of the present application is not specifically limited thereto.

[0161] The terminal in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an iOS operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited.

[0162] The terminal according to the embodiment of the present application can implement each process implemented by the embodiment of the method of FIG. 2 and achieve the same technical effect, and will not be further described here to avoid repetition.

[0163] Optionally, as shown in FIG. 4, an embodiment of the present application further provides a communication device 400, including a processor 401, a memory 402, and a program or instruction stored in the memory 402 and operable on the processor 401. For example, when the communication device 400 is a terminal, when the program or instruction is executed by the processor 401, each process of the embodiment of the data transmission type setting method can be realized and the same technical effect can be achieved.

[0164] FIG. 5 is a schematic diagram of the hardware structure of the terminal of the embodiment of the present application.

[0165] The terminal 500 includes components such as, but not limited to, a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, and a processor 510.

[0166] As will be understood by those skilled in the art, the terminal 500 may further include a power source (e.g., a battery) for powering each component, and the power source may be logically connected to the processor 510 by a power management system, thereby enabling the power management system to realize functions such as charge / discharge management and power consumption management. The terminal structure shown in Figure 5 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than those shown, or a combination of some components, or a different arrangement of components, which will not be further described here.

[0167] It should be understood that in the embodiment of the present application, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042, and the graphics processor 5041 processes image data of still or video images captured by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be arranged in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 507 includes a touch panel 5071 and other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts: a touch detection device and a touch controller. The other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, and a control lever, which will not be further described herein.

[0168] In the embodiment of the present application, the radio frequency unit 501 receives downlink data from the network side device, then processes the data in the processor 510, and transmits uplink data to the network side device. Generally, the radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0169] The memory 509 may be used to store software programs or instructions and various data. The memory 509 may primarily include a program or instruction storage area and a data storage area, where the program or instruction storage area can store an operating system, an application program or instructions required for at least one function (e.g., audio playback function, image playback function, etc.), etc. The memory 509 may include high-speed random access memory or nonvolatile memory, where the nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. For example, the memory 509 may be at least one magnetic disk memory device, flash memory device, or other nonvolatile solid-state memory device.

[0170] The processor 510 may include one or more processing units. Optionally, the processor 510 may integrate an application processor and a modem processor. Here, the application processor mainly processes an operating system, a user interface, and application programs or instructions, and the modem processor mainly processes wireless communication, such as a baseband processor. As can be appreciated, the modem processor does not have to be integrated into the processor 510.

[0171] Here, the processor 510 is used to set a target transmission type based on at least one of network configuration, path loss, uplink data size, and backoff instruction, where the target transmission type includes one of a small data transmission type based on configuration permission, a small data transmission type based on random access, and a random access type.

[0172] In an embodiment of the present application, the terminal may set a target transmission type based on at least one of network configuration, path loss, uplink data size, and backoff instruction, and the target transmission type may include a small data transmission type based on configuration permission, a small data transmission type based on random access, or a random access type, which solves the problem in the related art that the terminal cannot set the data transmission type, aligns the understanding between the terminal and the network side, and improves the performance of small data transmission.

[0173] The terminal according to the embodiment of the present application can also implement each process of the embodiment of the data transmission type setting method described above, and can achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0174] The embodiments of the present application further provide a readable storage medium, which stores a program or instruction, and when the program or instruction is executed by a processor, it can realize each process of the above-mentioned data transmission type setting method embodiment and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0175] The processor may be the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0176] The embodiments of the present application further provide a chip, the chip including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to realize each process of the embodiments of the data transmission type setting method and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0177] It should be understood that the chips referred to in the embodiments of this application may be referred to as system level chips, system chips, chip systems, or system-on-chips.

[0178] The embodiments of the present application further provide a computer program product, which is stored in a non-volatile memory, and which can be executed by at least one processor to realize each process of the above-mentioned data transmission type setting method embodiment and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0179] The embodiments of the present application further provide a communication device, which is configured to perform each process of the embodiments of the data transmission type setting method described above, and can achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0180] It should be noted that, in this specification, the terms "comprise," "include," "includes," or any other variations thereof are intended to cover the non-exclusive "comprise," whereby a process, method, article, or apparatus comprising a set of elements not only includes those elements, but also other elements not expressly listed or inherent in such process, method, article, or apparatus. Absent further limitations, an element defined by the phrase "comprises one of" does not preclude the presence of other identical elements in the process, method, article, or apparatus comprising that element. It should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions essentially simultaneously or in the reverse order based on such functions. For example, the described method may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to some examples may be combined in other examples.

[0181] As will be apparent to those skilled in the art from the above description of the embodiments, the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of the present application, in substance or in part contributing to the prior art, may be embodied in the form of a software product. This computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a terminal (which may be a mobile phone, computer, server, air conditioner, network device, etc.) to execute the methods described in each embodiment of the present application.

[0182] Although the embodiments of the present application have been described above in conjunction with the drawings, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can implement many forms under the guidance of the present application as long as they do not deviate from the spirit and scope of protection of the claims, and all of them fall within the scope of protection of the present application.

Claims

1. A method for setting a data transmission type, comprising: The terminal sets a target transmission type based on one of the following: Network placement and path loss, Path loss and uplink data size, Path loss and backoff indication, Network configuration, path loss and backoff indication, Path loss, uplink data size and backoff indication, network configuration, path loss, uplink data size and backoff indication; Here, the target transmission type includes one of a small data transmission type based on allocation permission, a small data transmission type based on random access, and a random access type.

2. The terminal setting a target transmission type based on at least one of the following: Allocating small data transmission resources based on the allocation permission; The small data transmission resource based on the allocation permission is valid; and a measured downlink path loss reference is greater than a first channel quality threshold; the path loss is less than a first channel quality threshold; and a size of uplink data is less than or equal to a first transport block size (TBS) threshold. setting the target transmission type as a small data transmission type based on the placement permission, The method of claim 1 , further comprising setting variable small data transmission to true.

3. The method comprises: The target transmission type is set as a small data transmission type based on the placement permission; 3. The method of claim 2, further comprising instructing a lower layer to perform an uplink data transmission process of a small data transmission type based on a configuration permission based on at least one of: the value of the variable small data transmission being true; and

4. The terminal setting a target transmission type based on at least one of the following: A small data transmission resource based on random access is allocated; the measured downlink path loss reference is greater than a second channel quality threshold; and the path loss is less than a second channel quality threshold; and The size of the uplink data is equal to or less than a second TBS threshold; and and setting the target transmission type as the random access-based small data transmission type based on at least one of the following: a backoff indication has not been received from a lower layer to indicate that the uplink data transmission process of the random access-based small data transmission type is terminated or canceled; setting the target transmission type as the random access-based small data transmission type; The method of claim 1 , further comprising setting variable small data transmission to true.

5. The method comprises: The target transmission type is set as the random access-based small data transmission type; and the value of the variable small data transmission is true.

6. The terminal setting a target transmission type based on at least one of the following: The small data transmission resource based on the allocation permission is not allocated; and No random access-based small data transmission resources are allocated; and The small data transmission resource based on the allocation permission is not valid; and a measured downlink path loss reference is not higher than a first channel quality threshold; the path loss is greater than a first channel quality threshold; and the measured downlink path loss reference is not higher than a second channel quality threshold; the path loss is greater than a second channel quality threshold; and The size of the uplink data is greater than a first TBS threshold; and The size of the uplink data is greater than a second TBS threshold; and receiving the backoff instruction from a lower layer, the backoff instruction being used to indicate that the uplink data transmission process of the random access-based small data transmission type is terminated or canceled; and setting the target transmission type as the random access type based on at least one of the following: setting the target transmission type as the random access type includes: The method of claim 1 , further comprising setting Transmit Variable Small Data to false.

7. Before the terminal sets a target transmission type based on at least one of the following, the method includes:

2. The method of claim 1, further comprising: initiating a first radio resource control (RRC) connection recovery process, wherein the first RRC connection recovery process is used to perform uplink data transmission according to the configuration grant-based small data transmission type or the random access-based small data transmission type.

8. The method comprises: If a second RRC connection recovery process is requested during the first RRC connection recovery process, and the target transmission type is a small data transmission type based on the configuration grant, continuing to perform the first RRC connection recovery process; or and initiating the second RRC connection recovery process. When initiating the second RRC connection recovery process, the method further comprises:

8. The method of claim 7, further comprising: performing a small data transmission backoff process, wherein the small data transmission backoff process is used to terminate, cancel, or suspend an uplink data transmission process of a small data transmission type based on the configuration grant.

9. If the target transmission type is a small data transmission type based on the placement permission, the method includes: selecting an uplink carrier to be used for performing uplink data transmission according to the small data transmission type based on the configuration grant; selecting an uplink carrier to be used for performing uplink data transmission according to the small data transmission type based on the configuration grant, In a first case, selecting a supplemental uplink link (SUL) as an uplink carrier to be used for uplink data transmission according to a small data transmission type based on the configuration grant; In a second case, selecting a normal uplink carrier NUL as an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration grant; 2. The method of claim 1, wherein the first case includes a case where the measured value of the downlink path loss reference is lower than a third channel quality threshold, and the second case is a case other than the first case.

10. The method according to claim 1, wherein the target transmission type is a small data transmission type based on the placement permission. further comprising setting the value of a first transmission counter to zero; The method according to claim 1 , wherein the first transmission counter is used to count the number of failures in performing an uplink data transmission process of a small data transmission type based on the configuration grant.

11. When the target transmission type is a small data transmission type based on the placement permission, the method further comprises: The method further includes: a lower layer of the terminal transmitting a failure indication to an upper layer based on the first timer expiring; The method of claim 10 , wherein the failure indication is used to indicate that an uplink data transmission process of a small data transmission type based on the configuration grant has not been successful.

12. The method according to claim 1, wherein the target transmission type is a small data transmission type based on the placement permission. When the upper layer of the terminal receives a failure indication from the lower layer, incrementing the first transmission counter by one; 12. The method of claim 11, further comprising: performing a small data transmission backoff process if the value of the first transmission counter is equal to a first count threshold.

13. The method according to claim 1, wherein the target transmission type is a small data transmission type based on the placement permission. setting the value of a second transmission counter to zero; The method according to claim 1 , wherein the second transmission counter is used to count the number of uplink skips performed in an uplink data transmission process of a small data transmission type based on the configuration grant.

14. The method according to claim 1, wherein the target transmission type is a small data transmission type based on the placement permission. The method further includes a lower layer of the terminal sending an uplink skip indication to an upper layer based on the fact that a protocol data unit waiting for transmission has not been obtained; The method of claim 13 , wherein the uplink skip indication is used to indicate that an uplink skip has occurred in an uplink data transmission process of a small data transmission type based on the configuration grant.

15. The method according to claim 1, wherein the target transmission type is a small data transmission type based on the placement permission. When an upper layer of the terminal receives an uplink skip instruction from a lower layer, adding 1 to the second transmission counter; and performing a small data transmission backoff process if the value of the second transmission counter is equal to a second count threshold.

16. When the target transmission type is the random access-based small data transmission type, the method includes: the measured downlink path loss reference is greater than a fourth channel quality threshold; and Arranging small data transmission resources based on two-step random access; and a size of uplink data being less than or equal to a third TBS threshold.

17. When the target transmission type is the random access-based small data transmission type, the method includes: the measured downlink path loss reference is not higher than a fourth channel quality threshold; and The small data transmission resource is arranged based on four-step random access; and a size of uplink data is greater than a third TBS threshold.

18. When the target transmission type is the random access-based small data transmission type, the method includes: The upper layer of the terminal performs a small data transmission backoff process based on receiving a backoff instruction from the lower layer; setting the target transmission type as a small data transmission type based on two-step random access and based on the value of the preamble transmission counter being equal to a third count threshold plus one, setting the target transmission type as a small data transmission type based on four-step random access; When the value of the preamble transmission counter is equal to a third count threshold plus one, the lower layer of the terminal sends a backoff instruction to the upper layer; 2. The method of claim 1, further comprising at least one of: when the value of the preamble transmission counter is equal to a fourth count threshold plus one, the lower layer of the terminal conveying a backoff indication to the upper layer.

19. The method of claim 18, wherein the small data transmission backoff process is performed by:

9. The method of claim 8, further comprising starting or restarting a second timer for indicating a maximum length of time for the terminal to perform the RRC connection recovery process.

20. The performing of the small data transmission backoff process includes: The method of claim 8 , comprising initiating transmission of an RRC Recovery Request message.

21. Executing the small data transmission backoff process includes: The method of claim 8 , comprising setting Transmit Variable Small Data to false.

22. The method of claim 21, wherein the small data transmission backoff process is performed by: Releasing small data transmission resources based on the allocation authorization; and discarding small data transmission resources based on the stored placement grant; The performing of the small data transmission backoff process includes: Releasing the small data transmission resource based on the allocation grant or discarding the stored small data transmission resource based on the allocation grant when the value of the first transmission counter is equal to a first count threshold; or When the value of the first transmission counter is equal to the first count threshold, releasing the small data transmission resource based on the placement grant and discarding the stored small data transmission resource based on the placement grant is further included; The performing of the small data transmission backoff process includes: Releasing the small data transmission resource based on the allocation grant or discarding the stored small data transmission resource based on the allocation grant when the value of the second transmission counter is equal to a second count threshold; or 9. The method of claim 8, further comprising: releasing small data transmission resources based on the placement grant when the value of the second transmission counter is equal to a second count threshold; and discarding the stored small data transmission resources based on the placement grant.

23. Before the terminal sets a target transmission type based on at least one of the following, the method small data transmission resources based on allocation permission; A small data transmission resource based on four-step random access; The method of claim 1 , further comprising receiving configuration information for configuring at least one of: a small data transmission resource based on two-step random access; and a small data transmission resource based on two-step random access.

24. The configuration information further comprises: a first channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on the configuration permission; a second channel quality threshold for the terminal to set the target transmission type as the random access-based small data transmission type; a third channel quality threshold for the terminal to select the SUL as an uplink carrier to be used for uplink data transmission according to the small data transmission type based on the configuration grant; and a fourth channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on two-step random access; a first TBS threshold that instructs the terminal to use a maximum TBS corresponding to performing small data transmission according to the small data transmission type based on the allocation permission; a second TBS threshold that instructs the terminal to use a maximum TBS corresponding to small data transmission performed by the random access-based small data transmission type; a third TBS threshold instructing the terminal to use a maximum TBS corresponding to small data transmission according to a small data transmission type based on two-step random access; a first count threshold indicating to the terminal a maximum number of failures in performing an uplink data transmission process according to a small data transmission type based on a configuration permission; a second count threshold indicating a maximum number of uplink skips for the terminal to perform an uplink data transmission process according to the small data transmission type based on the configuration permission; a third count threshold indicating to the terminal the maximum number of failures in performing small data transmission according to a small data transmission type based on two-step random access; and a fourth count threshold that indicates to the terminal the maximum number of failures to perform small data transmission according to a small data transmission type based on four-step random access.

25. A terminal comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions implementing the method for setting a data transmission type according to any one of claims 1 to 24 when executed by the processor.

26. A readable storage medium having stored thereon a program or instructions which, when executed by a processor, implements the method for setting a data transmission type according to any one of claims 1 to 24.

Images