How to configure data transmission type and terminals
By allowing the terminal to set data transmission type based on network configuration, path loss, and backoff instruction, the method aligns terminal and network understanding, improving small data transmission performance.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-09-30
- Publication Date
- 2026-03-19
AI Technical Summary
Existing technologies fail to address how a terminal sets the data transmission type, leading to inconsistencies between the terminal and the network side, which can cause transmission issues in small data communication scenarios.
The terminal sets a target transmission type based on network configuration, path loss, and backoff instruction, choosing between configuration-based, random access-based, and random access types to align understanding with the network side.
This approach improves the performance of small data transmission by ensuring consistent data transmission type setting between the terminal and network, enhancing communication efficiency.
Smart Images

Figure 0007833509000001 
Figure 0007833509000002 
Figure 0007833509000003
Abstract
Description
Technical Field
[0001] This application belongs to the field of communication technologies, and specifically relates to a method for setting a data transmission type and a terminal.
Background Art
[0002] Small data transmission is mainly for machine type communications (MTC), and is characterized by transmitting small data packets of dozens to hundreds of bits periodically or burstily. Only an uplink transmission function may be required, or only a downlink transmission function may be required. For example, sensor devices collect data, or actuator devices execute control commands, etc.
[0003] For a scenario where a non-connected terminal performs small data transmission (such as user plane data), the network side may simultaneously allocate general random access resources, small data transmission resources based on random access, and small data transmission resources based on allocation permission to the terminal. In such a case, the terminal may perform small data transmission according to the small data transmission type based on allocation permission, or may perform small data transmission according to the small data transmission type based on random access.
[0004] However, in the related art, the problem of how the terminal sets the data transmission type is not mentioned, and transmission problems are likely to occur due to the inconsistency in understanding between the terminal and the network side. Therefore, how the terminal sets the small data transmission type is an issue that needs to be resolved urgently.
Summary of the Invention
[0005] Embodiments of this application provide a method for setting a data transmission type and a terminal, which can solve the problem in the related art that the terminal cannot set the data transmission type.
[0006] According to a first aspect, a method for setting a data transmission type is provided, the method comprising a terminal setting a target transmission type based on at least one of the following: network placement, path loss, size of uplink data, and backoff instruction, wherein the target transmission type includes one of a placement-based small data transmission type, a random access-based small data transmission type, and a random access type.
[0007] According to a second aspect, a terminal is provided, the terminal including a transmission type setting module for setting a target transmission type based on at least one of network configuration, path loss, uplink data size, and backoff instruction, wherein the target transmission type includes one of a configuration-based small data transmission type, a random access-based small data transmission type, and a random access type.
[0008] According to a third aspect, a terminal is provided, the terminal including a processor, memory, and a program or instruction stored in the memory and operable on the processor, the method according to the first aspect being realized when the program or instruction is executed by the processor.
[0009] According to a fourth aspect, a readable storage medium is provided, wherein a program or instruction is stored in the readable storage medium, and when the program or instruction is executed by a processor, the method according to the first aspect is realized.
[0010] According to the fifth aspect, a computer program product is provided, the computer program product comprising a processor, memory, and a program or instruction stored in the memory and operable on the processor, wherein when the program or instruction is executed by the processor, the method according to the first aspect is realized.
[0011] According to the sixth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor being used to run a program or instructions, thereby realizing the method according to the first aspect.
[0012] In the embodiments of this application, the terminal may set the target transmission type based on at least one of the following: network configuration, path loss, uplink data size, and backoff instruction, and this target transmission type includes one of a configuration-based small data transmission type, a random access-based small data transmission type, and a random access type, solving the problem in related technologies in which the terminal cannot set the data transmission type, aligning the understanding between the terminal and the network side, and improving the performance of small data transmission. [Brief explanation of the drawing]
[0013] [Figure 1] This is a block diagram of a wireless communication system according to one embodiment of this application. [Figure 2] This is a schematic flowchart of a method for setting the data transmission type according to one embodiment of this application. [Figure 3] This is a schematic diagram of the structure of a terminal according to one embodiment of this application. [Figure 4] This is a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 5] This is a schematic diagram of the structure of a terminal according to one embodiment of this application. [Modes for carrying out the invention]
[0014] The following clearly and completely describes the technical concepts in the embodiments of this application, linking them to the drawings of the embodiments. Clearly, the embodiments described are only some, and not all, embodiments of this application. All other embodiments derived from the embodiments of this application without the creative effort of a person skilled in the art are all within the scope of protection of this application.
[0015] The terms "first," "second," etc., used in the specification and claims of this application are intended to distinguish similar subjects and not to describe a specific order or sequence. It should be understood that the data used in this manner are interchangeable where appropriate, so that the embodiments of this application can be carried out in an order other than those illustrated or described herein, and the subjects distinguished by "first" and "second" are generally of the same kind and do not limit the number of subjects; for example, the first subject may be one or more. Furthermore, "and / or" in the specification and claims indicates at least one of the connected subjects, and the letter " / " generally indicates that the preceding and succeeding related subjects are in an "or" relationship.
[0016] It should be noted that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but are also applicable 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 this application are always used interchangeably, and the technologies described may be applied to the systems and radio technologies mentioned above, or to other systems and radio technologies. However, the following description uses the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions. These technologies are not applicable to applications other than NR systems, such as sixth-generation (6) systems. th It may be applied to 6G (Generation 1) communication systems.
[0017] Figure 1 shows a block diagram of a wireless communication system to which an embodiment of this application can be applied. The wireless communication system includes a terminal 11 and network-side equipment 12. Here, terminal 11 may also be called terminal equipment or user equipment (UE), and terminal 11 may be terminal-side equipment such as a mobile phone, tablet personal computer, laptop computer (or notebook computer), personal digital assistant (PDA), palmtop computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device or in-vehicle equipment (VUE), or pedestrian terminal (PUE), and wearable devices include bracelets, earphones, glasses, etc. It should be noted that this does not limit the specific type of terminal 11 in the embodiment of this application. The network-side equipment 12 may be a base station or a core network, where a base station may also be called a node B, evolution node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), next-generation node B (gNB), home B node, home evolution B node, WLAN access point, WiFi node, transmission receiving point (TRP), or any other appropriate term in the art, as long as the same technical effect is achieved. The base station is not limited to any particular technical term, and for the purposes of this explanation, only a base station in an NR system is given as an example in the embodiments of this application, but this does not limit the specific type of base station.
[0018] In the following, with reference to the drawings, the method for setting the data transmission type according to the embodiments of the present application and the terminal will be described in detail by way of specific embodiments and their application scenarios.
[0019] As shown in FIG. 2, one embodiment of the present application provides a method 200 for setting a data transmission type, which may be executed by a terminal, or in other words, this method may be executed by software or hardware attached to the terminal, and this method includes the following steps.
[0020] In S202, the terminal sets a target transmission type based on at least one of the following, namely, network configuration, path loss, the size of uplink data, and backoff indication.
[0021] 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.
[0022] Optionally, in this embodiment, the terminal is in a disconnected state before setting the target transmission type, and this disconnected state includes an idle state (IDLE) or an inactivated state (INACTIVE).
[0023] The above network configuration may be a transmission resource of the network configuration, and this transmission resource may include at least one of a small data transmission resource based on allocation permission, a small data transmission resource based on four-step random access, a small data transmission resource based on two-step random access, a resource of four-step random access, and a resource of two-step random access.
[0024] Regarding the above path loss, the terminal may be determined by the measured value of the downlink reference signal.
[0025] The size of the uplink data may be the size of the small data packets waiting for transmission, for example, the size of the uplink user data that can be obtained, or the size of the finally generated Medium Access Control Protocol Data Unit (MAC PDU) including the uplink user data, for example, the size of the uplink user data that can be obtained, or the size obtained by adding at least one header (i.e., at least one of the Service Data Adaptation Protocol (SDAP) header, Packet Data Convergence Protocol (PDCP) header, Radio Link Control (RLC) header, and Medium Access Control (MAC) header), or the size obtained by adding at least one Medium Access Control-Control Element (MAC CE) required for at least one of the Buffer Status Report (BSR) and Power Headroom Report (PHR).
[0026] The backoff indication may be used to instruct the terminal that the uplink data transmission process of the small data transmission type based on random access has ended or been canceled.
[0027] In one example, S202 sets the target transmission type as the small data transmission type based on the allocation permission when, for example, the terminal has allocated the small data transmission resources based on the allocation permission and the small data transmission resources based on the allocation permission are valid, or sets the target transmission type as the random access type when the terminal has not allocated the small data transmission resources based on the allocation permission and has not allocated the small data transmission resources based on random access.
[0028] For example, if the measured value of the terminal downlink path loss reference is higher than the first channel quality threshold, the target transmission type is set to the placement permission-based small data transmission type, and if the measured value of the terminal downlink path loss reference is higher than the second channel quality threshold, the target transmission type is set to the random access-based small data transmission type.
[0029] In this embodiment, the measured values of the downlink path loss reference may include, but are not limited to, at least one of the following: Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), signal-to-noise ratio (SINR), channel occupancy rate (CO), received signal strength indication (RSSI), and channel busy rate (CBR).
[0030] For example, the size of the uplink data may be less than or equal to a first transport block size (TBS) threshold, and the terminal may set the target transmission type to a small data transmission type based on placement permission, or the size of the uplink data may be less than or equal to a second TBS threshold, and the terminal may set the target transmission type to a small data transmission type based on random access.
[0031] For example, the upper layer of the terminal has not received a backoff instruction from the lower layer and sets the target transmission type to the small data transmission type based on 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] In the above example, the terminal often sets the target transmission type based on one of the following: network configuration, path loss, uplink data size, and backoff instruction; in practice, the terminal can set the target transmission type based on at least both of the above.
[0034] For example, if a terminal has deployed a small data transmission resource based on deployment authorization, and the measured value of the downlink path loss reference is higher than the first channel quality threshold, the target transmission type is set to the small data transmission type based on deployment authorization.
[0035] For example, if the terminal has a small data transmission resource based on random access, and the measured value of the downlink path loss reference is higher than the second channel quality threshold, and no backoff instruction has been received, the target transmission type is set to the small data transmission type based on random access.
[0036] For example, if a terminal has deployed a small data transmission resource based on deployment permission, and the measured 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 to the small data transmission type based on deployment permission.
[0037] The placement-based small data transmission types referred to in each embodiment of this specification may specifically involve network-side equipment placing uplink permissions for a terminal by a Radio Resource Control (RRC) Release message, and include parameters such as period, time domain or frequency domain or coded domain or airspace resources, i.e., the placement-based small data transmission resources described above.
[0038] After setting the target transmission type as a small data transmission type based on the placement permission, the terminal can perform uplink data transmission by adopting the placement uplink permission, which may be terminal-specific. Specifically, the terminal sends Data Radio Bearer (DRB) data and / or Signaling Radio Bearer (SRB) request messages (e.g., RRC resume request messages) to a dedicated PUSCH resource, and after sending this PUSCH, the terminal can obtain scheduling information corresponding to the Physical Downlink Shared Channel (PDSCH) by monitoring the PDCCH, which is scrambled by a specific terminal identifier (e.g., C-RNTI) to the terminal during the corresponding Physical Downlink Control Channel (PDCCH) monitoring opportunity, and this PDSCH contains the terminal's DRB data and / or SRB response messages (e.g., RRC Release messages).
[0039] The random access-based small data transmission types referred to in each embodiment of this specification may include a two-step random access-based small data transmission type, and may further include a four-step random access-based small data transmission type.
[0040] The random access-based small data transmission types referred to in each embodiment of this specification specifically include, in which network-side equipment may arrange uplink transmission resources for terminals by broadcast messages, a parameter arrangement of MsgA Physical Random Access Channel (PRACH) resources and MsgA PUSCH resources for a small data transmission type corresponding to two-step random access, or Msg1 PRACH resources and Msg3 PUSCH resources for a small data transmission type corresponding to four-step random access, i.e., the random access-based small data transmission resources described above.
[0041] The terminal can send MsgA PRACH and MsgA PUSCH by setting the target transmission type to the small data transmission type based on two-step random access and then selecting a resource of the small data transmission type corresponding to two-step random access. Specifically, the terminal sends DRB data and / or a signaling SRB request message (e.g., an RRC resume request message) in the MsgA PUSCH, and after sending this MsgA PRACH and / or MsgA PUSCH, the terminal can obtain scheduling information corresponding to MsgB PDSCH by monitoring the PDCCH scrambled by a specific terminal identifier (e.g., MsgB-RNTI) at the corresponding PDCCH monitoring opportunity, and this MsgB PDSCH contains the terminal's DRB data and / or an SRB response message (e.g., an RRC Release message) and / or a conflict resolution identifier.
[0042] The terminal can send Msg1 PRACH by setting the target transmission type to the small data transmission type based on the four-step random access, and then selecting a resource of the small data transmission type that corresponds to the four-step random access. Specifically, after sending this Msg1 PRACH, the terminal can obtain scheduling information corresponding to Msg2 Random Access Response (RAR) by monitoring the PDCCH scrambled by a specific terminal identifier (e.g., RA-RNTI) at the corresponding PDCCH monitoring opportunity. This Msg2 RAR includes uplink permission to send Msg3 PUSCH. The terminal then sends DRB data and / or a signaling SRB request message (e.g., an RRC resume request message) in Msg3 PUSCH. After sending this Msg3 PUSCH, the terminal can obtain scheduling information corresponding to Msg4 PDSCH by monitoring the PDCCH scrambled by a specific terminal identifier (e.g., TC-RNTI) at the corresponding PDCCH monitoring opportunity. This Msg4 PDSCH includes the terminal's DRB data and / or an SRB response message (e.g., an RRC Release message) and / or a conflict resolution identifier.
[0043] The random access types referred to in each embodiment of this specification specifically allow network-side equipment to configure a parameter arrangement for a terminal via a broadcast message, which may be a two-step random access MsgA PRACH resource and a MsgA PUSCH resource, or a four-step random access Msg1 PRACH resource and a Msg3 PUSCH resource. After setting the target transmission type to the random access type, the terminal can send only SRB response messages in MsgA PUSCH or Msg3 PUSCH, but cannot carry transmitted DRB data, i.e., cannot perform uplink data transmission on the user plane.
[0044] In practice, the random access-based small data transmission type described above may perform small data transmission (e.g., DRB data transmission), but it may not perform small data transmission (e.g., not carrying transmitted DRB data). The placement permission-based small data transmission type, and the random access-based small data transmission type or random access type described above, generally perform only small data transmission.
[0045] In embodiments of this application, the terminal may set the target transmission type based on at least one of the following: network placement, path loss, uplink data size, or backoff instruction, and this target transmission type includes placement permission-based small data transmission type, random access-based small data transmission type, or random access type, solving the problem in related technologies where the terminal cannot set the data transmission type, aligning the understanding between the terminal and the network side, and improving the performance of small data transmission.
[0046] To explain in detail the method for setting the data transmission type according to the embodiments of this application, several specific embodiments will be described below in conjunction with each other.
[0047] Example 1 In this embodiment, a terminal setting a 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 placement permission based on at least one of the following:
[0048] 1) Small data transmission resources are allocated based on placement authorization. For example, the network explicitly allocates small data transmission resources based on placement authorization for the Band Width Part (BWP). These allocated small data transmission resources are related to synchronization and physical broadcast signals (Synchronization Signal and PBCH block, SSB).
[0049] 2) A small data transmission resource based on placement authorization is valid. In this example, “valid” may be understood as a small data transmission resource based on placement authorization being available, for example, if the network has placed the small data transmission resource based on placement authorization, and / or a certain timer (e.g., a time alignment timer associated with the small data transmission type based on placement authorization) is running, and / or the small data transmission resource based on placement authorization is in an uplink slot (UL slot) and is not in conflict with an SSB. Alternatively, for example, “valid” may be understood as a terminal having stored the small data transmission resource based on placement authorization and the terminal not releasing the small data transmission resource based on placement authorization.
[0050] 3) The measured value of the downlink path loss reference is higher than the first channel quality threshold. For example, the measured value of the downlink reference signal (DL RS) is higher than the first channel quality threshold.
[0051] 4) The path loss is less than the first channel quality threshold.
[0052] It should be explained that in actual applications, the first channel quality threshold mentioned in both examples 3) and 4) above is such that, generally, only one of them may hold true, or 3) and 4) are two mutually exclusive solutions and generally do not exist simultaneously, and the values of the first channel quality threshold mentioned in 3) and 4) do not necessarily have to be equal.
[0053] 5) The size of the uplink data is less than or equal to the first transmission block size (TBS) threshold. In this example, how the terminal determines the size of the uplink data may be implemented on a terminal-by-terminal basis.
[0054] Selectively, in this embodiment, setting the target transmission type as a small data transmission type based on the placement permission further includes setting variable small data transmission to true.
[0055] To explain, setting Variable Small Data Transmission to True generally means that the terminal is configured to perform uplink data transmission using either a placement permission-based small data transmission type or a random access-based small data transmission type. Setting Variable Small Data Transmission to False generally means that the terminal is not configured to perform uplink data transmission using either of the above two transmission types, but instead initiates the RRC connection recovery process using the random access type, and performs uplink data transmission after the RRC connection is recovered.
[0056] In this embodiment, when a terminal has both random access-based small data transmission resources (including 4-step random access-based small data transmission and 2-step random access-based small data transmission) and placement permission-based small data transmission resources, it is possible to prioritize the placement permission-based small data transmission type for uplink data transmission and easily make full use of the already allocated uplink resources.
[0057] Selectively, this embodiment is 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 an operation that sets variable small data transmission as in the example above, and the upper layer of the terminal (e.g., RRC layer) instructs the lower layer (e.g., MAC layer, physical layer) to perform an uplink data transmission process of the small data transmission type based on placement permission, based on at least one of the above.
[0058] Example 2 In this embodiment, 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) A small data transmission resource based on random access is deployed. For example, a small data transmission resource based on random access for BWP is deployed (for example, a small data transmission resource based on 4-step random access and / or a small data transmission resource based on 2-step random access is deployed for BWP), but the small data transmission type is set to a small data transmission type based on random access, and selectively, variable small data transmission is set to true.
[0060] 2) The measured value of the downlink path loss reference is higher than the second channel quality threshold; for example, the measured value of the downlink PL RS is higher than the second channel quality threshold.
[0061] 3) The path loss is less than the second channel quality threshold.
[0062] It should be explained that in both examples 3) and 4) above, the second channel quality threshold mentioned is that, in actual applications, only one of 3) and 4) is generally true, or 3) and 4) are two mutually exclusive solutions and generally do not exist simultaneously, and the values of the second channel quality threshold mentioned in 3) and 4) do not necessarily have to be equal.
[0063] 4) The size of the uplink data is below the second TBS threshold.
[0064] 5) The backoff instruction to indicate that the uplink data transmission process of the small data transmission type based on random access has been terminated or canceled has not been received from the lower layer.
[0065] Selectively, 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] Selectively, this embodiment further includes the step of the upper layer of the terminal instructing the lower layer to perform an uplink data transmission process of the 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, and may be specifically achieved by the operation of the example above that sets variable small data transmission to true.
[0069] Example 3 In this embodiment, the terminal sets the target transmission type based on at least one of the following: 1) Small data transmission resources based on deployment permission have not been deployed, 2) There are no small data transmission resources based on random access, 3) The small data transmission resources based on the deployment permission are not enabled, 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 the first channel quality threshold, 6) The measured value of the downlink path loss reference is not higher than the second channel quality threshold, 7) The path loss is greater than the second channel quality threshold, 8) The size of the uplink data is greater than the first TBS threshold, 9) The size of the uplink data is greater than the second TBS threshold, 10) Setting the target transmission type as a random access type based on at least one of the following: 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 being terminated or canceled.
[0070] Selectively, in this embodiment, setting the target transmission type to random access type further includes falsely setting variable small data transmission.
[0071] It should be noted that the three embodiments described above may be combined to constitute other embodiments of this application. For example, in one new combination embodiment, if all of conditions 1) to 5) listed in Embodiment 1 are met, the terminal sets the target transmission type as the small data transmission type based on the placement permission.
[0072] If at least one of conditions 1) to 5) listed in Example 1 is not met, and all of conditions 1) to 5) listed in Example 2 are met, the terminal sets the target transmission type to the random access-based small data transmission type.
[0073] If at least one of conditions 1) to 5) listed in Example 1 is not met, and at least one of conditions 1) to 5) listed in Example 2 is not met, and at least one of conditions 1) to 10) listed in Example 3 is met, the terminal sets the target transmission type to the random access type.
[0074] Selectively, the terminal described in each embodiment may, before setting the target transmission type based on at least one of the following, further include initiating a first Radio Resource Control (RRC) connection recovery process, which is used to perform uplink data transmission by the placement permission-based small data transmission type or the random access-based small data transmission type. That is, when the terminal sets the target transmission type to the placement permission-based small data transmission type, or sets the target transmission type to the random access-based small data transmission type, it can perform uplink data transmission by the first RRC connection recovery process.
[0075] Selectively, the above embodiment further includes continuing the first RRC connection recovery process or initiating the second RRC connection recovery process if a second RRC connection recovery process is requested while the first RRC connection recovery process is in progress and the target transmission type is a small data transmission type based on the placement permission. Selectively, the second RRC connection recovery process may be used to allow the terminal to recover the RRC connection and recover SRB1. Selectively, the second RRC connection recovery process may be used to allow the terminal to establish an RRC connection and transition to an RRC connection state.
[0076] When initiating the second RRC connection recovery process, the method further includes the step of performing 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 placement authorization. A detailed description of the small data transmission backoff process can be found in the embodiments described below.
[0077] Based on the descriptions of the above embodiments, when the target transmission type is set as a placement-based small data transmission type, the method further includes the step of selecting an uplink carrier to be used for uplink data transmission by the placement-based small data transmission type.
[0078] Specifically, selecting an uplink carrier to be used for uplink data transmission by the small data transmission type based on the above-mentioned deployment permission includes, in the first case, selecting a Supplementary Uplink (SUL) as the uplink carrier to be used for uplink data transmission by the small data transmission type based on the deployment permission, and in the second case, selecting a Normal Uplink (NUL) as the uplink carrier to be used for uplink data transmission by the small data transmission type based on the aforementioned deployment permission.
[0079] The first case described above includes the case where the measured value of the downlink path loss reference is lower than the third channel quality threshold, and the second case is any other case other than the first case. For example, the second case is any other case where the measured value of the downlink path loss reference is equal to or greater than the third channel quality threshold.
[0080] Based on the above-described embodiments, if the target transmission type is a small data transmission type based on the placement permission, the method further includes at least one of the following:
[0081] 1) Based on the first timer having timed out, the lower layer of the terminal transmits a failure instruction to the upper layer. Here, the first timer is used to monitor downlink control information after uplink data transmission has been performed by a small data transmission type based on placement authorization, and the failure instruction is used to indicate that the uplink data transmission process of the small data transmission type based on placement authorization was unsuccessful. This unsuccessful uplink data transmission process means, for example, that a response message from the network side (e.g., the first timer having timed out) was not received within a certain time.
[0082] 2) Based on the fact that one pending protocol data unit has not been obtained, the lower layer of the terminal transmits an uplink skip instruction to the upper layer. This uplink skip instruction is used to indicate that an uplink skip has occurred in the small data transmission type uplink data transmission process based on the placement permission.
[0083] 3) Set the value of the first transmission counter to 0. This first transmission counter is used to statistically record the number of failures in the uplink data transmission process of the small data transmission type based on the placement permission.
[0084] 4) When the upper layer of the terminal receives a failure instruction from the lower layer, 1 is added to the first transmission counter.
[0085] 5) If the value of the first transmission counter is equal to the first count threshold, execute the small data transmission backoff process.
[0086] 6) Set the value of the second transmission counter to 0. The second transmission counter is used to statistically record the number of uplink skips when performing the uplink data transmission process of the small data transmission type based on the placement permission.
[0087] 7) When the upper layer of the terminal receives an uplink skip instruction from a lower layer, 1 is added to the second transmission counter.
[0088] 8) If the value of the second transmission counter is equal to the second count threshold, execute the small data transmission backoff process.
[0089] It should be explained that items 1) through 8) listed above may be performed individually or as a set of multiple items.
[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 having timed out according to 1), the lower layer of the terminal transmits a failure instruction to the upper layer (e.g., the RRC layer), then, when the upper layer of the terminal receives a failure instruction from the lower layer according to 4), 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 executes 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 awaiting transmission has been obtained according to 2), the lower layer of the terminal transmits an uplink skip instruction to the upper layer, then, when the upper layer of the terminal receives an uplink skip instruction from the lower layer according to 7), it adds 1 to the second transmission counter, and finally, if the value of the second transmission counter is equal to the second count threshold according to 8), it executes a small data transmission backoff process.
[0092] Based on the above-described examples, if the target transmission type is the random access-based small data transmission type, the method is 1) The measured value of the downlink path loss reference is higher than the fourth channel quality threshold, 2) Small data transmission resources based on two-step random access are deployed, 3) The target transmission type is set as a small data transmission type based on two-step random access, based on at least one of the following: the size of the uplink data is less than or equal to a third TBS threshold.
[0093] Based on the above-described examples, if the target transmission type is the random access-based small data transmission type, the method is 1) The measured value of the downlink path loss reference is not higher than the fourth channel quality threshold, 2) Small data transmission resources based on 4-step random access are deployed, 3) The target transmission type is set as a small data transmission type based on 4-step random access, based on at least one of the following: the size of the uplink data is greater than a third TBS threshold.
[0094] If, selectively, 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 4-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 2-step random access, and the value of the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) is equal to the third count threshold plus 1.
[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 transmits a backoff instruction to the upper layer.
[0097] The third count threshold mentioned in the two examples above indicates the maximum number of failures the terminal will experience when performing small data transmission using a 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 transmits a backoff instruction to the upper layer.
[0099] The fourth count threshold indicates the maximum number of failures the terminal will experience when performing small data transmission using a small data transmission type based on four-step random access.
[0100] 4) Based on the fact that the upper layer of the terminal has received a backoff instruction from the lower layer, the small data transmission backoff process is executed.
[0101] Selectively performing the small data transmission backoff processes described in each of the above embodiments includes at least one of the following:
[0102] 1) Start or restart a second timer (e.g., timer 319, T319), which is used to indicate the maximum time length for the terminal to perform the RRC connection recovery process.
[0103] 2) Start sending RRC recovery request messages.
[0104] 3) Set variable small data transmission to false.
[0105] 4) Release small data transmission resources based on deployment authorization.
[0106] 5) Discard small data transmission resources based on stored placement permissions.
[0107] Initiating the transmission of the RRC recovery request message mentioned in 2) above includes, for example, the upper layer generating the RRC recovery request message and passing it to the lower layer, and if the target transmission type is the small data transmission type based on random access, the lower layer executes a random access initialization process (e.g., clearing the Msg 3 / Msg A cache) and performs the RRC recovery process through the random access process. Alternatively, for example, if the upper layer generates the RRC recovery request message and passes it to the lower layer, and the target transmission type is the small data transmission type based on placement authorization, the lower layer clears the HARQ cache associated with placement authorization, executes a random access initialization process, and performs the RRC recovery process through the random access process.
[0108] In the cases of 4) and 5) above, executing the small data transmission backoff process described above further includes releasing a small data transmission resource based on placement authorization or discarding a small data transmission resource based on stored placement authorization if the value of the first transmission counter is equal to the first count threshold, or releasing a small data transmission resource based on placement authorization and discarding a small data transmission resource based on stored placement authorization if the value of the first transmission counter is equal to the first count threshold.
[0109] In the cases of 4) and 5) above, executing the small data transmission backoff process described above further includes releasing a small data transmission resource based on placement authorization or discarding a small data transmission resource based on stored placement authorization if the value of the second transmission counter is equal to the second count threshold, or releasing a small data transmission resource based on placement authorization and discarding a small data transmission resource based on stored placement authorization if the value of the second transmission counter is equal to the second count threshold.
[0110] In each of the above embodiments, the method further includes receiving placement information for arranging at least one of the following for the terminal before the terminal sets a target transmission type based on at least one of the following.
[0111] 1) Small data transmission resources based on deployment authorization. For example, the network side deploys small data transmission resources based on deployment authorization for terminals that have been converted from CONNECTED to INACTIVE by an RRC Release message, and these resources include a terminal-specific PUSCH resource for INACTIVE terminals to send small data transmissions.
[0112] 2) Small data transmission resources based on 4-step random access. For example, the network side places small data transmission resources based on 4-step random access to an INACTIVE terminal via a system broadcast SIB1 message, and this resource includes a Physical Random Access Channel (PRACH) resource for the INACTIVE terminal to transmit small data transmissions.
[0113] 3) Small data transmission resources based on two-step random access. For example, the network side places small data transmission resources based on two-step random access to an INACTIVE terminal via a system broadcast SIB1 message, and these resources include a PRACH resource and a PUSCH resource for the INACTIVE terminal to send small data transmissions.
[0114] Selectively, the above arrangement information is further used to arrange 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 placement permission.
[0116] Based on this first channel quality threshold, the terminal can set the small data transmission type as a placement-based small data transmission type, the first channel quality threshold includes, but is not limited to, indicators that characterize channel quality such as signal-to-noise ratio (SINR), reference signal received power (RSRP), and reference signal received quality (RSRQ). Selectively, the first channel quality threshold is set only when the network side has placed a placement-based small data transmission resource for a BWP (e.g., 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 random access (4-step random access or 2-step random access).
[0118] Selectively, the second channel quality threshold is set only if the network side has deployed a small data transmission resource based on 4-step random access or a small data transmission resource based on 2-step random access for the BWP (e.g., initial BWP).
[0119] 3) A third channel quality threshold for the terminal to select SUL as the uplink carrier used to perform uplink data transmission by small data transmission type based on placement 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] Selectively, the fourth channel quality threshold is set only if the network side has allocated small data transmission resources based on the four-step random access and small data transmission resources based on the two-step random access for the BWP (e.g., initial BWP).
[0122] 5) A first TBS threshold that instructs the terminal to use the maximum TBS corresponding to performing small data transmission by the small data transmission type based on the placement 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) by a small data transmission type based on placement permission.
[0124] Selectively, this first TBS threshold is set only when the network side has allocated a small data transmission resource based on the allocation permission for a BWP (e.g., initial BWP).
[0125] 6) A second TBS threshold that instructs the terminal to use the maximum TBS corresponding to performing small data transmission by the random access-based small data transmission type.
[0126] This second 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) by a small data transmission type based on random access.
[0127] Selectively, this first TBS threshold is set only if the network side has deployed a small data transmission resource based on 4-step random access or a small data transmission resource based on 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 performing small data transmission by a small data transmission type based on two-step random access.
[0129] This third TBS threshold indicates that the terminal is suitable to use the maximum TBS corresponding to performing small data transmission (i.e., uplink data transmission) by a small data transmission type based on two-step random access.
[0130] 8) A first count threshold that instructs the terminal on the maximum number of failures required to perform the uplink data transmission process using a small data transmission type based on deployment permission.
[0131] 9) A second count threshold that instructs the terminal on the maximum number of uplink skips required to perform the uplink data transmission process using a small data transmission type based on deployment permission.
[0132] 10) A third count threshold that instructs the terminal on the maximum number of failures when performing small data transmission using a small data transmission type based on two-step random access.
[0133] 11) A fourth count threshold that instructs the terminal on the maximum number of failures when performing small data transmission using a small data transmission type based on 4-step random access.
[0134] It should be explained that in the data transmission type setting method according to the embodiment of this application, the execution body may be a terminal or a control module for executing the data transmission type setting method on this terminal. In the embodiment of this application, the terminal according to the embodiment of this application will be described using the data transmission type setting method by the terminal as an example.
[0135] Figure 3 is a schematic diagram of the structure of a terminal according to an embodiment of the present application, and as shown in Figure 3, the terminal 300 includes a transmission type setting module 302 which 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, wherein the target transmission type includes one of a configuration-based small data transmission type, a random access-based small data transmission type, and a random access type.
[0136] In embodiments of this application, the terminal may set the target transmission type based on at least one of the network configuration, path loss, uplink data size, and backoff instruction, and this 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, solving the problem in related technologies in which the terminal cannot set the data transmission type, aligning the understanding between the terminal and the network side, and improving the performance of small data transmission.
[0137] Selectively, 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 placement permission, based on at least one of the following: a small data transmission resource based on placement permission is placed; the small data transmission resource based on placement permission is enabled; the measured value of the downlink path loss reference is higher than a first channel quality threshold; the path loss is lower than a first channel quality threshold; and the size of the uplink data is less than or equal to a first TBS threshold.
[0138] Selectively, as one embodiment, the transmission type setting module 302 may also be used to truly set variable small data transmission.
[0139] Selectively, in 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 placement-authorized small data transmission type, based on at least one of the following: the target transmission type is set to a placement-authorized small data transmission type, and the value of variable small data transmission is true.
[0140] Selectively, in 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 available; the measured value of the downlink path loss reference is higher than a second channel quality threshold; the path loss is lower than a second channel quality threshold; the size of the uplink data is less than or equal to a second TBS threshold; and the uplink data transmission process for the random access-based small data transmission type has not received the backoff instruction from a lower layer to indicate that the uplink data transmission process for the random access-based small data transmission type has terminated or been canceled.
[0141] Selectively, as one embodiment, the transmission type setting module 302 may also be used to truly set variable small data transmission.
[0142] Selectively, in 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 random access-based small data transmission type, based on at least one of the following: the target transmission type is set to the random access-based small data transmission type, and the value of variable small data transmission is true.
[0143] Selectively, in 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 the following: no placement-based small data transmission resources are placed; no random access-based small data transmission resources are placed; placement-based small data transmission resources are not enabled; the 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; 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; the size of the uplink data is greater than a first TBS threshold; the size of the 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 for the random access-based small data transmission type is terminated or canceled.
[0144] Selectively, in one embodiment, the transmission type setting module 302 may also be used to falsely set variable small data transmission.
[0145] Selectively, in one embodiment, the terminal 300 further includes a startup module for initiating a first RRC connection recovery process, the first RRC connection recovery process being used to perform uplink data transmission by the placement permission-based small data transmission type or the random access-based small data transmission type.
[0146] Selectively, in one embodiment, the startup module may further be used to continue the first RRC connection recovery process or to initiate the second RRC connection recovery process if a second RRC connection recovery process is requested while the first RRC connection recovery process is in progress and the target transmission type is a small data transmission type based on the placement permission.
[0147] If, as one embodiment, the second RRC connection recovery process is initiated, 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 the uplink data transmission process of the small data transmission type based on the placement permission.
[0148] Selectively, in one embodiment, if the target transmission type is a small data transmission type based on placement permission, the transmission type setting module 302 may further be used to select an uplink carrier to be used for uplink data transmission by the small data transmission type based on placement permission.
[0149] Selectively, as one embodiment, selecting an uplink carrier to be used for uplink data transmission by the small data transmission type based on the placement permission includes, in the first case, selecting an auxiliary uplink link SUL as the uplink carrier to be used for uplink data transmission by the small data transmission type based on the placement permission, and in the second case, selecting a normal uplink link NUL as the uplink carrier to be used for uplink data transmission by the small data transmission type based on the placement permission, wherein the first case includes the case in which the measured value of the downlink path loss reference is lower than the third channel quality threshold, and the second case is any other case other than the first case.
[0150] Selectively, as one embodiment, if the target transmission type is a small data transmission type based on placement permission, the transmission type setting module 302 further: based on the first timer having timed out, the lower layer of the terminal transmits a failure instruction to the upper layer; based on the fact that one pending protocol data unit has not been obtained, the lower layer of the terminal transmits an uplink skip instruction to the upper layer; the value of the first transmission counter is set to 0; if the upper layer of the terminal receives a failure instruction from the lower layer, it adds 1 to the first transmission counter; if the value of the first transmission counter is equal to the first count threshold, it executes a small data transmission backoff process; the value of the second transmission counter is set to 0; if the upper layer of the terminal receives an uplink skip instruction from the lower layer, it adds 1 to the second transmission counter; if the value of the second transmission counter is equal to the second count threshold The first timer may be used to perform a small data transmission backoff process, wherein the first timer is used to monitor downlink control information after uplink data transmission has been performed by a placement-based small data transmission type; the failure indicator is used to indicate that the uplink data transmission process of the placement-based small data transmission type was unsuccessful; the uplink skip indicator is used to indicate that an uplink skip occurred in the uplink data transmission process of the placement-based small data transmission type; the first transmission counter is used to statistically count the number of failures in performing the uplink data transmission process of the placement-based small data transmission type; and the second transmission counter is used to statistically count the number of uplink skips in performing the uplink data transmission process of the placement-based small data transmission type.
[0151] Selectively, in one embodiment, if the target transmission type is the random access-based small data transmission type, the transmission type setting module 302 may further be used to set the target transmission type as the two-step random access-based small data transmission type based on at least one of the following: the measured value of the downlink path loss reference is higher than a fourth channel quality threshold; a two-step random access-based small data transmission resource is provided; and the size of the uplink data is less than or equal to a third TBS threshold.
[0152] Selectively, in one embodiment, if the target transmission type is the random access-based small data transmission type, the transmission type setting module 302 may further be used to set the target transmission type as the four-step random access-based small data transmission type based on at least one of the following: the measured value of the downlink path loss reference is not higher than the fourth channel quality threshold; a four-step random access-based small data transmission resource is provided; and the size of the uplink data is greater than the third TBS threshold.
[0153] Selectively, as one embodiment, if the target transmission type is the random access-based small data transmission type, the transmission type setting module 302 further: 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 the third count threshold plus one. 2) When the value of the preamble transmission counter is equal to the third count threshold plus 1, the lower layer of the terminal transmits a backoff instruction to the upper layer. 3) When the value of the preamble transmission counter is equal to the fourth count threshold plus 1, the lower layer of the terminal transmits a backoff instruction to the upper layer. 4) The upper layer of the terminal may be used to execute a small data transmission backoff process based on the reception of a backoff instruction from a lower layer, or to use at least one of the above.
[0154] Selectively, in one embodiment, performing the small data transmission backoff process described above includes at least one of: starting or restarting a second timer for indicating the maximum time length for the terminal to perform the RRC connection recovery process; initiating the transmission of an RRC recovery request message; setting variable small data transmission to false; releasing a small data transmission resource based on placement authorization; and discarding a small data transmission resource based on stored placement authorization.
[0155] Selectively, as one embodiment, performing the small data transmission backoff process described above further includes releasing a small data transmission resource based on placement permission or discarding a small data transmission resource based on stored placement permission when the value of a first transmission counter is equal to a first count threshold, or releasing a small data transmission resource based on placement permission and discarding a small data transmission resource based on stored placement permission when the value of a first transmission counter is equal to a first count threshold.
[0156] Selectively, as one embodiment, performing the small data transmission backoff process described above further includes releasing a small data transmission resource based on placement permission or discarding a small data transmission resource based on stored placement permission when the value of a second transmission counter is equal to a second count threshold, or releasing a small data transmission resource based on placement permission and discarding a small data transmission resource based on stored placement permission when the value of a second transmission counter is equal to a second count threshold.
[0157] Selectively, as one embodiment, the terminal 300 is for the terminal Small data transmission resources based on deployment permission, Small data transmission resources based on 4-step random access, The system further includes a small data transmission resource based on two-step random access, and a receiving module for receiving placement information to place at least one of these resources.
[0158] Selectively, as one embodiment, the arrangement information may further be 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 placement 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, 3) A third channel quality threshold for the terminal to select SUL as the uplink carrier used to perform uplink data transmission by small data transmission type based on placement permission, 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 the maximum TBS corresponding to performing small data transmission by the small data transmission type based on the placement permission, 6) A second TBS threshold that instructs the terminal to use the maximum TBS corresponding to performing small data transmission by the random access-based small data transmission type, 7) A third TBS threshold that instructs the terminal to use the maximum TBS corresponding to performing small data transmission by a small data transmission type based on two-step random access, 8) A first count threshold that instructs the terminal on the maximum number of failures required to perform the uplink data transmission process using a small data transmission type based on deployment permission, 9) A second count threshold that instructs the terminal on the maximum number of uplink skips required to perform the uplink data transmission process using a small data transmission type based on deployment permission, 10) A third count threshold that instructs the terminal on the maximum number of failures when performing small data transmission using a small data transmission type based on two-step random access, 11) A fourth count threshold that indicates the maximum number of failures the terminal will have when performing small data transmission by a small data transmission type based on four-step random access, is used to set up at least one of the following:
[0159] The terminal 300 according to the embodiment of this application can refer to the flow corresponding to the method 200 of the embodiment of this application, and each unit / module and the other operations and / or functions in this terminal 300 are for realizing the corresponding flow in method 200 and can achieve the same or equivalent technical effects, and for the sake of brevity, they will not be described further here.
[0160] The terminal in the embodiments of this application may be a component, integrated circuit, or chip in the terminal. This terminal may be a mobile terminal or a non-mobile terminal. Exemplary examples of mobile terminals may include, but are not limited to, the types of terminals 11 listed above. Non-mobile terminals may include servers, network-attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs or self-service machines, and the embodiments of this application are not specifically limited.
[0161] The terminal in the embodiments of this application may be a device having an operating system. This operating system may be an Android operating system, an iOS operating system, or any other possible operating system, and the embodiments of this application are not specifically limited.
[0162] The terminal according to the embodiment of this application can realize each process realized by the embodiment of the method shown in Figure 2 and achieve the same technical effects, and to avoid repetition of the explanation, it will not be explained further here.
[0163] Selectively, as shown in Figure 4, embodiments of the present application further provide 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, if the communication device 400 is a terminal, when this program or instruction is executed by the processor 401, each process of the embodiment of the data transmission type setting method described above can be realized and the same technical effects can be achieved.
[0164] Figure 5 is a schematic diagram of the hardware structure that realizes the terminal of the embodiment of this application.
[0165] This terminal 500 includes, but is not limited to, components such as 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 those skilled in the art will understand, the terminal 500 may further include a power supply (e.g., a battery) to power each component, and the power supply may be logically connected to the processor 510 by a power management system, thereby enabling functions such as charge / discharge management and power consumption management by the power management system. The terminal structure shown in Figure 5 does not constitute a limitation on terminals, and a terminal may include more or fewer components than those shown, or combinations of some components, or different arrangements of components, which will not be described further here.
[0167] It should be understood that, in the embodiments of this application, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042, the graphics processor 5041 processing still images or video image data obtained by an image capture device (e.g., a camera) in video capture mode or image capture mode. The display unit 506 may include a display panel 5061, which may be arranged in the form of a liquid crystal display, organic light-emitting diodes, etc. The user input unit 507 includes a touch panel 5071 and other input devices 5072. The touch panel 5071 is also called a touchscreen. 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, or an operating lever, and will not be described further here.
[0168] In the embodiments of this application, the radio frequency unit 501 receives downlink data from network-side equipment, processes it with the processor 510, and transmits uplink data to the network-side equipment. 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, and the like.
[0169] Memory 509 may be used to store software programs or instructions and various data. Memory 509 may mainly 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 necessary for at least one function (e.g., audio playback function, image playback function, etc.). Memory 509 may also include high-speed random access memory and non-volatile memory, where the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or flash memory. For example, it may be at least one magnetic disk memory device, a flash memory device, or other non-volatile 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 primarily handles the operating system, user interface, and application programs or instructions, while the modem processor primarily handles wireless communication, such as a baseband processor. To be clear, the modem processor does not necessarily 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 the network configuration, path loss, uplink data size, and backoff instruction, wherein the target transmission type includes one of a configuration-based small data transmission type, a random access-based small data transmission type, and a random access type.
[0172] In embodiments of this application, the terminal may set the target transmission type based on at least one of the network configuration, path loss, uplink data size, and backoff instruction, and this 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, solving the problem in related technologies in which the terminal cannot set the data transmission type, aligning the understanding between the terminal and the network side, and improving the performance of small data transmission.
[0173] The terminal according to the embodiment of this application can implement each process of the embodiment of the data transmission type setting method described above, and can achieve the same technical effects. To avoid repetition, no further explanation is provided here.
[0174] Embodiments of this application further provide a readable storage medium in which a program or instruction is stored, and when this program or instruction is executed by a processor, each process of the embodiment of the data transmission type setting method described above can be realized and the same technical effects can be achieved. To avoid repetition, no further explanation is provided here.
[0175] Here, the processor may be the processor in the terminal described in the above embodiment. The readable storage medium includes computer-readable storage media such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.
[0176] Embodiments of this application further provide a chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor being used to run a program or instructions, and which can implement each process of the embodiment of the method for setting the data transmission type described above and achieve the same technical effects. To avoid repetition, no further explanation is provided here.
[0177] It should be understood that the chips referred to in the embodiments of this application may also be called system-level chips, system chips, chip systems, or system-on-a-chip, etc.
[0178] Embodiments of this application further provide a computer program product in which the computer program product is stored in non-volatile memory and is executed by at least one processor to realize each process of the embodiment of the data transmission type setting method described above and to achieve the same technical effects. To avoid repetition, no further explanation is provided here.
[0179] Embodiments of this application further provide communication equipment configured to perform each process of the embodiment of the data transmission type setting method described above, and can achieve the same technical effects. To avoid repetition, no further explanation is provided here.
[0180] It should be noted that, in this specification, the terms “include,” “incorporate,” or any other variation thereof are intended to cover the non-exclusive “include,” thereby including not only those elements but also other elements not explicitly listed, or elements specific to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase “includes one of…” is not excluded from the existence of other identical elements in a process, method, article, or apparatus containing that element. It should also be noted that the scope of methods and apparatus in embodiments of this application is not limited to performing functions in the illustrated or discussed order, but may include performing functions in a manner that is essentially simultaneous or in reverse order based on such functions, and methods described in a different procedure than those described may be performed, and various steps may be added, omitted, or combined. Furthermore, features described by reference to some examples may be combined with other examples.
[0181] As will be readily apparent to those skilled in the art from the above description of the embodiments, the methods of the above embodiments can be implemented in the form of software and a necessary general-purpose hardware platform. Of course, they may also be implemented in hardware, but in many cases the former is a more preferred embodiment. With this understanding in mind, the technical proposal of this application may be embodied in the form of a software product, either substantially or in part with respect to the prior art. This computer software product is stored on a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and contains some instructions for causing a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to perform the methods of each embodiment of this application.
[0182] The above describes embodiments of this application, accompanied by drawings; however, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can, by the suggestion of this application, make many forms, as long as they do not deviate from the spirit and scope protected by the claims of this application, and all of these fall within the scope of protection of this application.
Claims
1. A method for setting the data transmission type, This includes the terminal setting the target transmission type based on network configuration, path loss, and the size of the uplink data. Herein, the target transmission type is a method for setting a data transmission type, which includes one of a placement permission-based small data transmission type, a random access-based small data transmission type, and a random access type.
2. The terminal sets the target transmission type based on network configuration, path loss, and the size of the uplink data. The deployment of small data transmission resources based on deployment permission, The small data transmission resources based on deployment permission are enabled, The measured downlink path loss reference is higher than the first channel quality threshold, The path loss is less than the first channel quality threshold, The process includes setting the target transmission type as a small data transmission type based on the placement permission, based on at least one of the following: the size of the uplink data is less than or equal to the first transmission block size TBS threshold, Setting the aforementioned target transmission type as a small data transmission type based on the placement permission is, The method according to claim 1, further comprising setting variable small data transmission to true.
3. The aforementioned method, The target transmission type is set as a small data transmission type based on the placement permission, The method of claim 2, further comprising instructing a lower layer to perform an uplink data transmission process of a placement permission-based small data transmission type based on at least one of the following: that the value of variable small data transmission is true.
4. The terminal sets the target transmission type based on network configuration, path loss, and the size of the uplink data. The deployment of small data transmission resources based on random access, The measured downlink path loss reference is higher than the second channel quality threshold, The path loss is less than the second channel quality threshold, The method includes setting the target transmission type as the random access-based small data transmission type based on at least one of the following: the size of the uplink data is less than or equal to a second TBS threshold, Setting the aforementioned target transmission type as the random access-based small data transmission type is, The method according to claim 1, further comprising setting variable small data transmission to true.
5. The aforementioned method, The target transmission type is set as the random access-based small data transmission type, The method of claim 4, further comprising instructing a lower layer to perform an uplink data transmission process of a random access-based small data transmission type based on at least one of the following: that the value of variable small data transmission is true.
6. The terminal sets the target transmission type based on network configuration, path loss, and the size of the uplink data. The small data transmission resources based on the deployment permission have not been deployed, The absence of small data transmission resources based on random access, and the inability to enable small data transmission resources based on placement permission, The measured downlink path loss reference is not higher than the first channel quality threshold, The path loss is greater than the first channel quality threshold, The measured downlink path loss reference is not higher than the second channel quality threshold, The path loss is greater than the second channel quality threshold, The size of the uplink data is larger than the first TBS threshold, The method includes setting the target transmission type as the random access type based on at least one of the following: the size of the uplink data is greater than a second TBS threshold, Setting the aforementioned target transmission type as the random access type means that The method according to claim 1, further comprising setting variable small data transmission to false.
7. Before the terminal sets the target transmission type based on network configuration, path loss, and the size of the uplink data, the method The method according to 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 by the placement permission-based small data transmission type or the random access-based small data transmission type.
8. If the target transmission type is a small data transmission type based on the placement permission, the method is: This further includes selecting an uplink carrier to be used for uplink data transmission by small data transmission type based on the aforementioned placement permission, Selecting an uplink carrier to be used for uplink data transmission by the small data transmission type based on the aforementioned placement permission is, In the first case, the auxiliary uplink link SUL is selected as an uplink carrier used to perform uplink data transmission by the small data transmission type based on the placement permission, In the second case, this includes selecting a normal uplink link NUL as the uplink carrier used to perform uplink data transmission by the small data transmission type based on the placement permission, The method according to claim 1, wherein the first case includes the case in which the measured value of the downlink path loss reference is lower than the third channel quality threshold, and the second case is any other case other than the first case.
9. If the target transmission type is a small data transmission type based on the placement permission, the method is: This further includes setting the value of the first transmission counter to 0, The method according to claim 1, wherein the first transmission counter is used to statistically determine the number of failures in performing the small data transmission type uplink data transmission process based on the placement permission.
10. If the target transmission type is a small data transmission type based on the placement permission, the method is: The lower layer of the terminal transmits a failure instruction to the upper layer based on the first timer having timed out, The method according to claim 9, wherein the failure instruction is used to indicate that the uplink data transmission process of the small data transmission type based on the placement permission was unsuccessful.
11. If the target transmission type is a small data transmission type based on the placement permission, the method is: When the upper layer of the terminal receives a single failure instruction from the lower layer, 1 is added to the first transmission counter. The method according to claim 10, further comprising: performing a small data transmission backoff process when the value of the first transmission counter is equal to a first count threshold.
12. If the target transmission type is a small data transmission type based on the placement permission, the method is: This further includes setting the value of the second transmission counter to 0, The method according to claim 1, wherein the second transmission counter is used to statistically determine the number of uplink skips in the uplink data transmission process of the small data transmission type based on the placement permission.
13. If the target transmission type is a small data transmission type based on the placement permission, the method is: The lower layer of the terminal transmits an uplink skip instruction to the upper layer based on the fact that one pending protocol data unit has not been obtained. The method according to claim 12, wherein the uplink skip instruction is used to indicate that an uplink skip has occurred in the small data transmission type uplink data transmission process based on the placement permission.
14. If the target transmission type is a small data transmission type based on the placement permission, the method is: When the upper layer of the terminal receives an uplink skip instruction from a lower layer, 1 is added to the second transmission counter. The method according to claim 13, further comprising: performing a small data transmission backoff process when the value of the second transmission counter is equal to a second count threshold.
15. If the target transmission type is the random access-based small data transmission type, the method is: The measured downlink path loss reference is higher than the fourth channel quality threshold, A small data transmission resource based on two-step random access will be deployed, The method according to claim 1, further comprising setting the target transmission type as a small data transmission type based on two-step random access, based on at least one of the following: the size of the uplink data is less than or equal to a third TBS threshold.
16. If the target transmission type is the random access-based small data transmission type, the method is: The measured downlink path loss reference is not higher than the fourth channel quality threshold, A small data transmission resource based on 4-step random access will be deployed, The method according to claim 1, further comprising 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 size of the uplink data is greater than a third TBS threshold.
17. If the target transmission type is the random access-based small data transmission type, the method is: Based on the fact that the upper layer of the aforementioned terminal has received a single backoff instruction from the lower layer, the small data transmission backoff process is executed. Based on the fact that the target transmission type is set as a small data transmission type based on two-step random access, and that the value of the preamble transmission counter is equal to the third count threshold plus one, the target transmission type is set as a small data transmission type based on four-step random access, If the value of the preamble transmission counter is equal to the third count threshold plus 1, the lower layer of the terminal transmits a backoff instruction to the upper layer. The method according to claim 1, further comprising at least one of the following: when the value of the preamble transmission counter is equal to a fourth count threshold plus 1, the lower layer of the terminal transmits a backoff instruction to the upper layer.
18. Executing the aforementioned small data transmission backoff process is The method according to claim 11, further comprising starting or restarting a second timer for indicating the maximum time duration for the terminal to perform the RRC connection recovery process.
19. Executing the aforementioned small data transmission backoff process is The method according to claim 11 or 18, comprising initiating the transmission of an RRC recovery request message.
20. Executing the aforementioned small data transmission backoff process is The method according to claim 11, comprising setting variable small data transmission to false.
21. Executing the aforementioned small data transmission backoff process is Releasing small data transmission resources based on deployment permission, This includes at least one of the following: discarding small data transmission resources based on stored placement permissions; Executing the aforementioned small data transmission backoff process is If the value of the first transmission counter is equal to the first count threshold, release the small data transmission resource based on placement permission, or discard the small data transmission resource based on stored placement permission, or If the value of the first transmission counter is equal to the first count threshold, the method further includes releasing the small data transmission resource based on placement permission and discarding the small data transmission resource based on stored placement permission. and / or, Executing the aforementioned small data transmission backoff process is If the value of the second transmission counter is equal to the second count threshold, release the small data transmission resource based on placement permission, or discard the small data transmission resource based on stored placement permission, or The method according to claim 11, further comprising releasing a small data transmission resource based on placement permission and discarding a small data transmission resource based on stored placement permission when the value of a second transmission counter is equal to a second count threshold.
22. Before the terminal sets the target transmission type based on network configuration, path loss, and the size of the uplink data, the method shall, for the terminal Small data transmission resources based on deployment permission, Small data transmission resources based on 4-step random access, The method according to claim 1, further comprising receiving placement information for locating at least one of a small data transmission resource based on two-step random access.
23. The aforementioned arrangement information further, for the terminal A first channel quality threshold for the terminal to set the target transmission type as a small data transmission type based on the placement 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 SUL as the uplink carrier used for uplink data transmission by small data transmission type based on placement permission, 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 the maximum TBS corresponding to performing small data transmission by the small data transmission type based on the aforementioned placement permission, A second TBS threshold that instructs the terminal to use the maximum TBS corresponding to performing small data transmission by the random access-based small data transmission type, A third TBS threshold that instructs the terminal to use the maximum TBS corresponding to performing small data transmission by a small data transmission type based on two-step random access, A first count threshold that instructs the terminal on the maximum number of failures required to perform the uplink data transmission process using a small data transmission type based on deployment permission, A second count threshold that instructs the terminal on the maximum number of uplink skips required to perform the uplink data transmission process using a small data transmission type based on placement permission, A third count threshold that instructs the terminal on the maximum number of failures when performing small data transmission using a small data transmission type based on two-step random access, The method according to claim 22, used to configure at least one of the following: a fourth count threshold that instructs the terminal on the maximum number of failures to perform small data transmission by a small data transmission type based on four-step random access.
24. A terminal comprising a processor, memory, and a program or instruction stored in the memory and operable on the processor, wherein when the program or instruction is executed by the processor, a method for setting the data transmission type described in any one of claims 1 to 18 and 20 to 23 is realized.
25. A terminal comprising a processor, memory, and a program or instruction stored in the memory and operable on the processor, wherein when the program or instruction is executed by the processor, the method for setting the data transmission type described in claim 19 is realized.
26. A readable storage medium that stores a program or instruction, and when the program or instruction is executed by a processor, enables a method for setting the data transmission type according to any one of claims 1 to 18 and 20 to 23.
Citation Information
Patent Citations
Grant free configuration
WO2018232321A2
Control channel transmission method for supporting multi-carriers in next generation communication system, and device therefor
WO2019098784A1
Method and apparatus for determining whether to perform transmission on a random access or a configured grant in wireless communication system
WO2020067790A1
Data transmission method and terminal device
WO2020078415A1