Data transmission method, device and communication system

Abstract

The present invention provides a data transmission method, device, and communication system, including a first processing unit configured to cause a terminal device to transmit a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) when the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority and transmissions of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain.

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE The embodiments of the present invention relate to the technical field of wireless communication. [Background technology]

[0002] In a communication system, resource pre-emption between terminal devices or between different services within a terminal device may occur.

[0003] For example, when the time-frequency domain resources of the downlink air interface of two terminals compete, the network device reserves the transmission of the high priority service in the two terminal devices preferentially, and notifies the terminal device whose resources have been preempted via special downlink control information (e.g., DCI2-1). Such a resource preemption mechanism allows the data of the high priority service to be transmitted with high priority, thereby improving the real-time property and reliability of the high priority service. As another example, the resource preemption in the terminal device may be performed based on the priority of the service.

[0004] For contention of uplink transmission in a terminal, the medium access control (MAC) layer and the physical (PHY) layer determine the preemption priority separately. For example, the MAC layer determines the preemption priority based on the logical channel priority, and the PHY layer determines the preemption priority based on the physical layer priority.

[0005] The above description of the background art is merely for the purpose of more clearly and completely explaining the configurations of the present invention and for the understanding of those skilled in the art, and should not be construed as meaning that these configurations are well known to those skilled in the art just because they are described in the background art of the present invention. Summary of the Invention [Problem to be solved by the invention]

[0006] Since the MAC layer and the PHY layer determine the preemption priority separately, it is possible that the PHY layer may determine that a transmission with a high priority determined by the MAC layer has a low priority, and the data of the uplink grant with a high priority determined by the MAC layer may be discarded by the PHY layer. In this case, data that is automatically transmitted by the terminal device using a configuration grant (CG) may not be transmitted and may be lost.

[0007] The inventors of the present invention have discovered that when two physical uplink shared channels (PUSCHs) have the same physical layer priority and the transmission of the two PUSCHs at least partially overlaps in the time domain, the prior art does not specify how a terminal device transmits data of the two PUSCHs.

[0008] The embodiments of the present invention provide a data transmission method, device and communication system, in which a terminal device transmits or does not transmit a second physical uplink shared channel (PUSCH) when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain, thereby ensuring the reliability of communication services. [Means for solving the problem]

[0009] A first aspect of an embodiment of the present invention provides a data transmission method applied to a terminal device, the method including: when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and transmission of the first physical uplink shared channel (PUSCH) and transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain, the terminal device transmits the second physical uplink shared channel (PUSCH).

[0010] A second aspect of an embodiment of the present invention provides a data transmission method applied to a terminal device, the method including: when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and transmission of the first physical uplink shared channel (PUSCH) and transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain, the terminal device not transmitting the second physical uplink shared channel (PUSCH).

[0011] A third aspect of an embodiment of the present invention provides a data transmission method applied to a terminal device, the method including: when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain, the terminal device determining whether to transmit or not transmit the second physical uplink shared channel (PUSCH) based on types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH).

[0012] In a fourth aspect of the present invention, there is provided a data transmission device to be applied to a terminal device, the data transmission device executing the data transmission method described in the first aspect, the second aspect, or the third aspect of the present invention.

[0013] In a fifth aspect of the present invention, there is provided a terminal device including the data transmission device according to the fourth aspect of the above embodiment.

[0014] In a sixth aspect of the embodiment of the present invention, there is provided a communication system including the terminal device according to the fifth aspect of the embodiment and a network device.

[0015] In a seventh aspect of the present invention, there is further provided a computer-readable program which, when executed in a data transmission device or a terminal device, causes the data transmission device or the terminal device to execute the data transmission method described in the first aspect, the second aspect, or the third aspect of the above-mentioned embodiment of the present invention.

[0016] In an eighth aspect of an embodiment of the present invention, there is further provided a storage medium having a computer-readable program stored therein, the program, when executed, causing a data transmission device or a terminal device to execute the data transmission method described in the first aspect, the second aspect or the third aspect of the embodiment of the present invention described above.

[0017] The advantageous effects of the embodiment of the present invention are as follows: When the first PUSCH and the second PUSCH have the same physical layer priority, and the transmission of the first PUSCH and the transmission of the second PUSCH at least partially overlap in the time domain, the terminal device transmits or does not transmit the second PUSCH. Thus, the medium access control layer and the physical layer of the terminal device can have a consistent process for whether to transmit a PUSCH, and the loss of data automatically transmitted by the terminal device in a configuration grant (CG) can be avoided, so that the reliability of the communication service can be ensured.

[0018] As shown in the following description and drawings, certain embodiments of the present invention are disclosed in detail to show the manner in which the principles of the present invention can be employed. However, the scope of the embodiments of the present invention is not limited to these. The embodiments of the present invention include modifications, alterations and equivalents within the spirit and scope of the appended claims.

[0019] Features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments and may be combined with or substituted for features in the other embodiments.

[0020] It should be noted that in this text, the term "including" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief description of the drawings]

[0021] Elements and features depicted in one drawing and one embodiment of the present invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may designate corresponding elements in multiple drawings and may designate corresponding elements used in more than one embodiment.

[0022] The drawings included herein are used to further understand the embodiments of the present invention, constitute a part of the specification, are used to illustrate the embodiments of the present invention, and together with the description of the words, explain the principles of the present invention. Note that the drawings described below are merely some of the embodiments of the present invention, and those skilled in the art can easily imagine other drawings based on these drawings. [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present invention; [Diagram 2] FIG. 1 is a schematic diagram of a physical layer discarding a high priority PUSCH; [Diagram 3] FIG. 2 is another schematic diagram of the physical layer discarding a high priority PUSCH; [Figure 4] FIG. 2 is a schematic diagram of a data transmission method according to the first embodiment of the present invention; [Diagram 5] FIG. 2 is a schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment of the present invention. [Figure 6] FIG. 2 is another schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment of the present invention; [Figure 7] FIG. 10 is a schematic diagram of a data transmission method according to a first example of a second embodiment of the present invention. [Figure 8] FIG. 11 is a schematic diagram of operations of a MAC layer and a physical layer according to a first example of the second embodiment of the present invention. [Figure 9] FIG. 11 is another schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment of the second embodiment of the present invention. [Figure 10] FIG. 11 is a schematic diagram of a data transmission method according to Example 2 of the second embodiment of the present invention. [Figure 11] FIG. 11 is a schematic diagram of operations of a MAC layer and a physical layer according to Example 2 of the second embodiment of the present invention. [Figure 12] FIG. 11 is another schematic diagram of the operation of the MAC layer and the physical layer according to the second embodiment of the second embodiment of the present invention. [Figure 13] FIG. 11 is a schematic diagram of a data transmission method according to a third embodiment of the present invention; [Figure 14] FIG. 11 is a schematic diagram of a data transmission device according to a fourth embodiment of the present invention. [Figure 15] FIG. 13 is a schematic block diagram of a system configuration of a terminal device according to a fifth embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Each embodiment of the present invention will be described below with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.

[0024] In embodiments of the present invention, the terms "first", "second", etc. are used in the title to distinguish different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "including", "comprising", "having", etc. refer to the presence of listed features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.

[0025] In the embodiments of the present invention, the singular forms "a", "the", etc., include the plural forms and should be understood broadly as "one kind" or "a class", and are not limited to "one". In addition, the term "said" should be understood to include both the singular and the plural forms, unless the context clearly indicates otherwise. In addition, the term "described in" should be understood to mean "described at least in part", and the term "based on" should be understood to mean "based at least in part on", unless the context clearly indicates otherwise.

[0026] In an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as, for example, Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0027] Additionally, communications between devices in a communication system may occur according to any stage of communication protocols, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), and / or other currently known or future developed communication protocols.

[0028] In the embodiment of the present invention, the term "network device" refers to a device in a communication system, for example, allowing a terminal device to access the communication system and providing a service to the terminal device. The network device may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0029] Among them, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), and a 5G base station (gNB), etc., as well as a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low power node (e.g., femto, pico, etc.). Also, the term "base station" may include some or all of the functions thereof, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area depending on the context in which the term is used.

[0030] In the embodiments of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to an apparatus that accesses a communication network and receives a network service via, for example, a network device. The terminal apparatus may be fixed or mobile, and may be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

[0031] Among them, the terminal device may include, but is not limited to, a mobile phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, and the like.

[0032] For example, in a scenario such as the Internet of Things (IoT), the user equipment may be a monitoring or measuring device or equipment, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0033] The following describes an embodiment scenario of the present invention with reference to an example, but the present invention is not limited thereto.

[0034] 1 is a schematic diagram of a communication system according to an embodiment of the present invention, and illustrates an example of a user device and a network device. As shown in FIG. 1, a communication system 100 may include a network device 101 and a terminal device 102. For convenience of explanation, FIG. 1 illustrates only one terminal device as an example.

[0035] In the embodiment of the present invention, existing services or services that can be implemented in the future can be performed between the network device 101 and the terminal device 102. For example, these services include, but are not limited to, enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC).

[0036] Here, the terminal device 102 may use, for example, a grant-free transmission method to transmit data to the network device 101. The network device 101 may receive data transmitted by one or more terminal devices 102, and feed back information (for example, acknowledgement (ACK) / non-acknowledgement (NACK)) to the terminal device 102, and the terminal device 102 may confirm the end of the transmission process according to the feedback information, or may perform new data transmission or data retransmission.

[0037] The following description will be given as an example in which a network device in a communication system is used as a receiver or a transmitter, and a terminal device is used as a transmitter or a receiver, but the present invention is not limited thereto, and the transmitter and / or the receiver may be other devices. For example, the present invention may be applied to grant-free transmission of an uplink between a network device and a terminal device, or to grant-free transmission of a sidelink between two terminal devices.

[0038] In the following embodiments of the present invention, the fact that a CG is not transmitted means that the MAC PDU data generated based on the configuration of the CG is not transmitted by the physical layer, and the MAC PDU may be referred to as an untransmitted MAC PDU.

[0039] The following describes application scenarios of the present invention.

[0040] Transmission contention in the terminal device may occur between different Physical Uplink Shared Channel (PUSCH) resource grants, for example between PUSCHs of two semi-static configuration grants (CGs), or between a configuration grant and a dynamically scheduled PUSCH. For contention between PUSCH resource grants and different scheduling request (SR) transmissions or ACK / NACK indications to downlink PUSCHs, the terminal device prioritizes the transmission of PUSCH, SR, or ACK / NACK of a physical uplink control channel (PUCCH). The medium access control (MAC) layer of the terminal device ensures the prioritized transmission of a high-priority service by determining a PUSCH grant or SR for prioritized transmission based on logical channel priority. When one PUSCH transmission block multiplexes multiple logical channel data, the priority of the PUSCH grant is determined by the logical channel with the highest priority multiplexed in the transmission block, and the priority of one SR transmission is determined by the logical channel priority corresponding to the SR. When two or more resources compete, the highest priority PUSCH grant or highest priority SR is determined as high priority and transmitted preferentially by the MAC layer, while the other grant or SR transmission is determined as low priority and preempted.

[0041] For uplink transmission contention in the terminal, the MAC layer and the PHY layer determine the transmission priority separately, the MAC layer determines the transmission priority based on the logical channel priority, and the PHY layer determines the transmission priority based on the physical layer priority. The physical layer priority (high or low) of the PUSCH of the configuration grant (CG) is indicated to the terminal device by the network device through a radio resource control (RRC) message, and the physical layer priority (high or low) of the dynamically scheduled PUSCH is indicated to the terminal device by the network device through a PDCCH signaling that schedules the PUSCH.

[0042] The network device configures a logical channel priority (1 to 16), a usable CG configuration list, and a physical layer priority (high or low) for each logical channel. An uplink PUSCH grant configured by each CG may multiplex multiple logical channel data that can be multiplexed. An uplink PUSCH grant of one dynamic scheduling may multiplex data of multiple logical channels that are the same as the physical layer priority. When one PUSCH grant can multiplex multiple logical channel data, in the MAC layer of the terminal device, the priority of the uplink grant may be determined by the logical channel with the highest priority among the logical channels that can be multiplexed, and the priority of one SR transmission may be determined by the logical channel priority corresponding to the SR. When two or more resources compete, the PUSCH grant or SR with the highest priority is preferentially transmitted by the MAC layer, and the other grants or SRs are preempted, and no uplink transmission is triggered.

[0043] In the MAC layer, if the uplink grant is a high-priority (transmitted with priority) uplink grant, the terminal device obtains the MAC PDU from the multiplexing and encapsulation entity and triggers the HARQ process associated with the grant to transmit data. If the grant is a low-priority (i.e., preempted) grant, the terminal device does not obtain the MAC PDU and does not trigger the transmission of data. In the case of a grant temporarily determined as a high-priority grant, the terminal device may have already obtained the MAC PDU and triggered the physical layer transmission of data, but may be determined again as a low-priority grant when high-priority logical channel data arrives, because the priority of the next uplink grant or SR transmission may be higher than the priority of the uplink grant of this already generated data. A high-priority grant may also generate data and trigger the transmission of the physical layer. In the PHY layer of the terminal device, the priority of the uplink transmission is determined by the physical layer priority of the PUSCH, and when the MAC layer instructs the physical layer to transmit two uplink data that overlap in resources, the physical layer transmits the uplink data with high physical layer priority with priority.

[0044] However, when two PUSCHs overlap and have the same physical layer priority, data with a higher priority at the MAC layer may be discarded at the physical layer. In this way, configuration grant (CG) data automatically transmitted by the terminal device may be lost without being transmitted. If CG data determined by the MAC layer to have a higher priority is discarded by the physical layer, the MAC side can autonomously retransmit only data determined by the MAC layer to have a lower priority, so the CG data is not automatically retransmitted by the MAC layer, and the network device does not schedule the retransmission of the CG data because the CG data has not actually been transmitted to the network device.

[0045] Figure 2 is a schematic diagram of a physical layer discarding a PUSCH with a high priority. As shown in Figure 2, the transmission of the PUSCH of the CG and the transmission of the PUSCH of the dynamic scheduling grant (DG) overlap at least partially in the time domain, and the PUSCH of the CG and the PUSCH of the DG have the same physical layer priority, and the MAC layer first generates one dynamic scheduling protocol data unit (PDU) 210, and then generates a PDU 220 of the CG with a high priority, but the physical layer preferentially transmits the PUSCH 211 of the dynamic scheduling grant, and the PUSCH 211 of the DG corresponds to the PDU 210 of the DG.

[0046] Figure 3 is another schematic diagram of the physical layer discarding a PUSCH with a high priority. As shown in Figure 3, the transmission of the PUSCH of CG1 and the transmission of the PUSCH of CG2 at least partially overlap in the time domain, and the PUSCH of CG1 and the PUSCH of CG2 have the same physical layer priority, and the MAC layer first generates a protocol data unit (PDU) 310 of CG1 and then generates a PDU 320 of CG2 with a higher priority, but the physical layer preferentially transmits the PUSCH 311 of CG1, where the PUSCH 311 of CG1 corresponds to the PDU 310 of CG1.

[0047] <First embodiment> The first embodiment of the present invention provides a data transmission method, which is applied to a terminal device, for example the terminal device 102 .

[0048] 4 is a schematic diagram of a data transmission method according to a first embodiment of the present invention. As shown in FIG. 4, the data transmission method includes the following steps:

[0049] Step 401: When a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority, and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device transmits the second physical uplink shared channel (PUSCH).

[0050] According to the first embodiment, when the first PUSCH and the second PUSCH have the same physical layer priority and the transmission of the first PUSCH and the transmission of the second PUSCH at least partially overlap in the time domain, the terminal device transmits the second PUSCH, thereby ensuring the reliability of the communication service.

[0051] In the first embodiment, the physical layer of the terminal device 102 receives data of the second physical uplink shared channel (PUSCH) from the medium access control (MAC) layer later than the data of the first physical uplink shared channel (PUSCH). That is, the second PUSCH has a higher priority than the first PUSCH. This allows the physical layer to transmit data of the second PUSCH with a higher priority.

[0052] In at least one embodiment, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by a first downlink control information (DCI), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

[0053] In another embodiment, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

[0054] Step 401 will be specifically described below.

[0055] For each PUSCH grant, the MAC layer of the terminal device 102 determines a priority based on the highest priority logical channel that can be multiplexed into the grant, and determines whether it is a high-priority uplink grant or a low-priority uplink grant based on the priority of the grant.

[0056] For a configuration grant (CG), if there is no PUSCH of another higher priority CG that overlaps with the PUSCH of the CG, there is no PUSCH of a dynamic scheduling grant with high priority or the same priority that overlaps with the PUSCH resource of the CG, and there is no PUCCH resource of a high priority SR transmission that overlaps with the PUSCH resource of the CG, then the CG grant is a high priority uplink grant and the other overlapping uplink grants are low priority uplink grants.

[0057] For a dynamic scheduling grant (DG), i.e. uplink scheduling where the physical downlink control channel (PDCCH) is addressed by the configured scheduling radio network temporary identifier (CS-RNTI) and NDI is 1, or dynamic scheduling addressed by the cell radio network temporary identifier (C-RNTI), if there is no PUSCH of a high priority CG that overlaps with the PUSCH of the dynamic scheduling grant, and there is no PUCCH resource of a high priority SR transmission that overlaps with the PUSCH resource of the dynamic scheduling grant, then the dynamic scheduling grant is determined to be a high priority grant and other overlapping uplink grants are determined to be low priority grants.

[0058] In the MAC layer, for a grant that is temporarily determined as having a high priority, the terminal device 102 may have already acquired PUSCH data and may have triggered PHY layer transmission of the data, but the priority of the next uplink grant or SR may be higher than the priority of the uplink grant of this already generated data, so the grant may be determined again as a low priority grant when high priority logical channel data arrives. The high priority grant may generate PUSCH data and transmit it to the PHY layer. In the PHY layer of the terminal device, the priority of the uplink transmission is determined by the physical layer priority of the PUSCH, and the physical layer preferentially transmits uplink data with a high physical layer priority. However, if two PUSCHs overlap and have the same physical layer priority, the data with a high priority in the MAC layer may be discarded in the physical layer.

[0059] Therefore, in the first embodiment, when the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority and the transmission of the first physical uplink shared channel (PUSCH) and the transmission of the second physical uplink shared channel (PUSCH) overlap at least partially in the time domain, when the time when the physical layer of the terminal device 102 receives data of the second physical uplink shared channel (PUSCH) from the medium access control (MAC) layer is later than the time when the data of the first physical uplink shared channel (PUSCH) is received, the terminal device 102 may transmit the second physical uplink shared channel (PUSCH) without transmitting the first PUSCH. This can avoid the problem that data with high priority in the MAC layer (i.e., data of the second PUSCH) is discarded in the PHY layer.

[0060] 5 is a schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment of the present invention. As shown in FIG. 5, the first PUSCH 510 is a PUSCH scheduled by the first downlink control information (i.e., a dynamic scheduling grant DG), the second PUSCH 520 is a PUSCH of a configuration grant (CG), the time when the second PUSCH 520 arrives at the physical layer is later than the time when the data of the first PUSCH 510 arrives at the physical layer, and the physical layer of the terminal device 102 transmits the second PUSCH 520.

[0061] 6 is another schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment of the present invention. As shown in FIG. 6, the first PUSCH 610 is a PUSCH of CG1, the second PUSCH 620 is a PUSCH of CG2, the time when the data of the second PUSCH 620 arrives at the physical layer is slower than the time when the data of the first PUSCH 610 arrives at the physical layer, and the physical layer of the terminal device 102 transmits the second PUSCH 620.

[0062] <Second embodiment> A second embodiment of the present invention provides a data transmission method, which is applied to a terminal device, for example the terminal device 102 .

[0063] In a data transmission method according to a second embodiment of the present invention, when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and transmission of the first physical uplink shared channel (PUSCH) and transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device 102 does not transmit the second physical uplink shared channel (PUSCH).

[0064] In a second embodiment of the present invention, the data transmission method may further include the terminal device 102 transmitting a first physical uplink shared channel (PUSCH).

[0065] [Example 1] 7 is a schematic diagram of a data transmission method according to Example 1 of the second embodiment of the present invention. As shown in FIG. 7, the method includes the following steps:

[0066] Step 701: When a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device 102 does not transmit the second physical uplink shared channel (PUSCH).

[0067] Step 702: The physical layer sends transmission indication information to a medium access control (MAC) layer, which is used to inform the medium access control (MAC) layer that data of the second physical uplink shared channel (PUSCH) is not being transmitted.

[0068] In the first embodiment, the physical layer of the terminal device 102 receives the data of the second physical uplink shared channel (PUSCH) from the medium access control (MAC) layer later than the data of the first physical uplink shared channel (PUSCH), i.e., the MAC layer priority of the second PUSCH is higher than the MAC layer priority of the first PUSCH.

[0069] In step 702, the physical layer can inform the MAC layer that the data of the second physical uplink shared channel (PUSCH) is not being transmitted, so that the MAC layer can perform subsequent processing on the second PUSCH, avoid data loss of the second PUSCH, and improve the reliability of communication services.

[0070] As shown in FIG. 7, the method may further include the following steps.

[0071] Step 703: A medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a low priority uplink grant.

[0072] When the MAC layer receives the transmission indication information sent by the physical layer in step 702, the MAC layer may execute step 703. Through step 703, the MAC layer can automatically start retransmitting data of the second PUSCH to avoid data loss.

[0073] As shown in FIG. 7, the method may further include the following steps.

[0074] Step 704: A medium access control (MAC) layer determines an uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high priority uplink grant.

[0075] If the MAC layer receives the transmission indication information sent by the physical layer in step 702, the MAC layer may perform step 704.

[0076] In embodiment 1, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG). Or, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

[0077] FIG. 8 is a schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment. As shown in FIG. 8, the first PUSCH 810 is a PUSCH scheduled by the first downlink control information (i.e., of a dynamic scheduling grant DG), and the second PUSCH 820 is a PUSCH of a configuration grant (CG), and the time when the data of the second PUSCH 820 arrives at the physical layer is later than the time when the data of the first PUSCH 810 arrives at the physical layer. As shown in FIG. 8, the physical layer of the terminal device 102 does not transmit the second PUSCH 820 and transmits a transmission indication to the MAC layer, and the transmission indication is used to notify the MAC layer that the data of the second PUSCH 820 is not transmitted. In addition, when the MAC layer receives the transmission indication, it may set the uplink grant (i.e., CG) corresponding to the second PUSCH 820 as a low priority grant and set the uplink grant corresponding to the first PUSCH 810 as a high priority grant.

[0078] FIG. 9 is another schematic diagram of the operation of the MAC layer and the physical layer according to the first embodiment. As shown in FIG. 9, the first PUSCH 910 is a PUSCH of a configuration grant (CG) 1, the second PUSCH 920 is a PUSCH of a CG 2, and the time when the data of the second PUSCH 920 arrives at the physical layer is slower than the time when the data of the first PUSCH 910 arrives at the physical layer. As shown in FIG. 9, the physical layer of the terminal device 102 does not transmit the second PUSCH 920 and transmits a transmission indication to the MAC layer, and the transmission indication is used to notify the MAC layer that the data of the second PUSCH 920 is not transmitted. In addition, when the MAC layer receives the transmission indication, it may set the uplink grant corresponding to the second PUSCH 920 (i.e., CG 2) as a low priority grant and set the uplink grant corresponding to the first PUSCH 910 (i.e., CG 1) as a high priority grant.

[0079] [Example 2] 10 is a schematic diagram of a data transmission method according to Example 2 of the second embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:

[0080] Step 1001: When a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device 102 does not transmit the second physical uplink shared channel (PUSCH).

[0081] In a second embodiment, step 1001 may include: if the medium access control (MAC) layer of the terminal device 102 generates data of a first physical uplink shared channel (PUSCH), the medium access control (MAC) layer does not generate data of the second physical uplink shared channel (PUSCH). Because the MAC layer does not generate data of the second PUSCH, the terminal device 102 cannot transmit data of the second PUSCH, and there is no operational inconsistency between the MAC layer and the physical layer regarding whether to transmit the second PUSCH.

[0082] Here, the fact that the Medium Access Control (MAC) layer does not generate data for the second Physical Uplink Shared Channel (PUSCH) may be realized in two ways.

[0083] In a first type of scheme, the medium access control (MAC) layer does not determine an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, and does not generate data for the second physical uplink shared channel (PUSCH).

[0084] Wherein, if there is no first physical uplink shared channel (PUSCH), the medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, and generates data of the second physical uplink shared channel (PUSCH); otherwise, the medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a low priority uplink grant, and does not generate data of the second physical uplink shared channel (PUSCH). Wherein, the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained a medium access control protocol data unit (MAC PDU).

[0085] Further, there is no physical uplink shared channel (PUSCH) of another high priority configuration grant (CG) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, there is no physical uplink shared channel (PUSCH) of high priority or the same priority scheduled by downlink control information (DCI) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, and a high priority scheduling request (SR) transmitted by the high priority scheduling request (SR) that overlaps with the second physical uplink shared channel (PUSCH) is transmitted. If there is no physical uplink control channel (PUCCH), the medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant and generates data for the second physical uplink shared channel (PUSCH); otherwise, the medium access control (MAC) layer does not determine an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant and does not generate data for the second physical uplink shared channel (PUSCH).

[0086] Therefore, in the first type of scheme, since the first physical uplink shared channel (PUSCH) already exists and the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has already acquired a medium access control protocol data unit (MAC PDU), the medium access control (MAC) layer does not determine the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as the uplink grant with higher priority, and does not generate data for the second physical uplink shared channel (PUSCH).

[0087] In a second type of scheme, the medium access control (MAC) layer directly determines not to generate data for the second physical uplink shared channel (PUSCH) for the uplink grant of the second PUSCH without determining the priority of the uplink grant corresponding to the second physical uplink shared channel (PUSCH).

[0088] For example, if there is no first physical uplink shared channel (PUSCH), generate a medium access control protocol data unit (MAC PDU) for an uplink grant corresponding to data of the second physical uplink shared channel (PUSCH); otherwise, the medium access control (MAC) layer determines the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a low-priority uplink grant, and does not generate data of the second physical uplink shared channel (PUSCH). Here, the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained a medium access control protocol data unit (MAC PDU).

[0089] Therefore, in the second type of scheme, since the first physical uplink shared channel (PUSCH) already exists and the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has acquired the medium access control protocol data unit (MAC PDU), the medium access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH), thereby avoiding operational inconsistency between the MAC layer and the physical layer regarding whether to transmit the second PUSCH.

[0090] In a second embodiment, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) (i.e., of a dynamic scheduling grant (DG)) or a physical uplink shared channel (PUSCH) of a configuration grant (CG), and the data of the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

[0091] FIG. 11 is a schematic diagram of the operation of the MAC layer and the physical layer according to the second embodiment. As shown in FIG. 11, the first PUSCH 1110 is a PUSCH scheduled by the first downlink control information (i.e., of a dynamic scheduling grant DG), the second PUSCH 1120 is a PUSCH of a configuration grant (CG), and the MAC layer has already generated data of the first PUSCH 1110 and does not generate data of the second PUSCH 1120 (shown by a dashed line in the figure). Thus, the MAC layer generates data of the first PUSCH 1110 and transmits it to the physical layer, and the physical layer transmits the data of the first PUSCH 1110, while the MAC layer does not generate data of the second PUSCH 1120, so that the physical layer does not transmit the second PUSCH 1120 data.

[0092] 12 is another schematic diagram of the operation of the MAC layer and the physical layer according to the second embodiment. As shown in FIG. 12, the first PUSCH 1210 is a PUSCH of the configuration grant (CG) 1, and the second PUSCH 1220 is a PUSCH of the configuration grant (CG) 2. The MAC layer has already generated data of the first PUSCH 1210, so it does not generate data of the second PUSCH 1220 (indicated by a dashed line in the figure). As a result, the MAC layer generates data of the first PUSCH 1210 and transmits it to the physical layer, and the physical layer transmits the data of the first PUSCH 1210, while the MAC layer does not generate data of the second PUSCH 1220, so the physical layer does not transmit the second PUSCH 1220 data.

[0093] [Example 3] The difference between the third embodiment and the second embodiment is the specific manner of realizing step 1001. In the third embodiment, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) or a physical uplink shared channel (PUSCH) of a configuration grant (CG), and data of the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

[0094] In the third embodiment, step 1001 may include that the medium access control (MAC) layer of the terminal device does not determine the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as the uplink grant with high priority and does not generate data of the second physical uplink shared channel (PUSCH). Since the MAC layer does not determine the uplink grant corresponding to the second PUSCH as the uplink grant with high priority and does not generate data of the second PUSCH, the terminal device 102 cannot transmit data of the second PUSCH. As a result, the terminal device 102 cannot transmit data of the second PUSCH, and therefore it is possible to avoid operational inconsistency between the MAC layer and the physical layer regarding whether to transmit the second PUSCH.

[0095] Here, if the first physical uplink shared channel (PUSCH) is not present, a medium access control (MAC) layer of the terminal device determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as an uplink grant with a higher priority, and generates data for the second physical uplink shared channel (PUSCH).

[0096] Furthermore, the medium access control (MAC) layer of the terminal device determines the priority of the uplink grant corresponding to the second physical uplink shared channel (PUSCH) according to the following method.

[0097] If there is no physical uplink shared channel (PUSCH) of another high priority configuration grant (CG) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, there is no physical uplink shared channel (PUSCH) of high priority or the same priority scheduled by downlink control information (DCI) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, and there is no physical uplink control channel (PUCCH) transmitted by a high priority scheduling request (SR) that overlaps with the second physical uplink shared channel (PUSCH), a medium access control (MAC) layer of the terminal device 102 determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant; otherwise, the medium access control (MAC) layer does not determine an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant.

[0098] According to the above method for determining the priority of the uplink grant corresponding to the second PUSCH, because the MAC layer has a first physical uplink shared channel (PUSCH), the physical layer priority of the first physical uplink shared channel (PUSCH) is identical to the physical layer priority of the second PUSCH, and the transmission of the first PUSCH and the transmission of the second PUSCH at least partially overlap in the time domain, the medium access control (MAC) layer does not determine the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as an uplink grant with a higher priority.

[0099] In addition, in the third embodiment, the medium access control (MAC) layer does not determine an uplink grant corresponding to a second physical uplink shared channel (PUSCH) as an uplink grant with a high priority, so that the MAC layer autonomously starts retransmission of data of the second PUSCH, thereby preventing loss of the second PUSCH data.

[0100] According to the third embodiment, when the physical layer priority of the second PUSCH and the physical layer priority of the first PUSCH are the same and at least partially overlap in the time domain, the MAC layer determines the priority of the uplink grant corresponding to the second PUSCH based on the logical channel priority and the physical layer priority. This allows the transmission priority of the MAC layer to match the transmission priority of the physical layer, thereby preventing the second PUSCH data, which is originally high priority data, from being discarded by the physical layer.

[0101] The following describes a method in embodiment 3 for MAC to determine the priorities of uplink grants corresponding to the first PUSCH and the second PUSCH, respectively.

[0102] When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI), and the data of the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), the MAC layer may respectively determine the priorities of uplink grants corresponding to the first PUSCH and the second PUSCH according to the following manner:

[0103] For a CG grant corresponding to a second PUSCH, if there is no PUSCH with high physical layer priority or the same physical layer priority scheduled by downlink control information (DCI) (i.e., dynamic scheduling grant) that at least partially overlaps in the time domain with the PUSCH of the CG, the MAC determines the CG grant corresponding to the second PUSCH as high priority, otherwise it does not determine it as high priority.

[0104] For an uplink grant corresponding to a first PUSCH, if there is no PUSCH of another high priority CG that at least partially overlaps with the first PUSCH in the time domain, the MAC layer may determine the uplink grant corresponding to the first PUSCH as high priority, otherwise, not determine it as high priority, where the physical layer priority of the PUSCH of the high priority CG is higher than the physical layer priority of the first PUSCH.

[0105] For example, for a CG grant corresponding to a second PUSCH, if there is no PUSCH of another higher priority CG that at least partially overlaps with the second PUSCH in the time domain, there is no PUSCH of a higher priority or the same priority scheduled by downlink control information (DCI) (i.e., of a dynamic scheduling grant) that at least partially overlaps with the second PUSCH in the time domain, there is no PUSCH of a higher physical layer priority or the same physical layer priority scheduled by downlink control information (DCI) (i.e., of a dynamic scheduling grant) that at least partially overlaps with the second PUSCH in the time domain, and there is no PUCCH resource transmitted by a high priority SR that at least partially overlaps with the second PUSCH in the time domain, the MAC determines the CG grant corresponding to the second PUSCH as a high priority uplink grant and determines the uplink grant corresponding to the other PUSCH that at least partially overlaps with the second PUSCH in the time domain as a low priority uplink grant.

[0106] As another example, for an uplink grant corresponding to a first PUSCH, if there is no PUSCH of another higher priority CG that at least partially overlaps with the first PUSCH in the time domain, and there is no PUCCH resource carried by a higher priority SR that at least partially overlaps with the first PUSCH in the time domain, the MAC layer determines the uplink grant corresponding to the first PUSCH as a high priority grant, and determines the uplink grant corresponding to the other PUSCH that at least partially overlaps with the first PUSCH in the time domain as a low priority uplink grant, where the physical layer priority of the PUSCH of the higher priority CG is higher than the physical layer priority of the uplink grant of the first PUSCH.

[0107] When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), the MAC layer may respectively determine the priorities of uplink grants corresponding to the first PUSCH and the second PUSCH according to the following manner:

[0108] For a CG grant corresponding to a first PUSCH or a second PUSCH, if there is no PUSCH of another CG with a higher physical layer priority or the same physical layer priority that at least partially overlaps in the time domain with the PUSCH of the CG, the MAC determines the CG grant corresponding to the first PUSCH or the second PUSCH as high priority, otherwise it does not determine it as high priority.

[0109] For example, for a CG corresponding to a first PUSCH or a second PUSCH, if there is no PUSCH of another CG of higher priority or the same priority that at least partially overlaps in the time domain with the PUSCH of the CG (the first PUSCH or the second PUSCH), there is no PUSCH of another CG of higher physical layer priority or the same physical layer priority that at least partially overlaps in the time domain with the PUSCH of the CG, there is no PUSCH of high priority or the same priority scheduled by downlink control information (DCI) (i.e., of a dynamic scheduling grant) that at least partially overlaps in the time domain with the PUSCH of the CG, and there is no PUCCH resource transmitted by a high priority SR that at least partially overlaps in the time domain with the PUSCH of the CG, the MAC determines the CG corresponding to the first PUSCH or the second PUSCH as a high priority uplink grant and determines the uplink grant corresponding to the other PUSCH that at least partially overlaps in the time domain with the first PUSCH or the second PUSCH as a low priority uplink grant.

[0110] In embodiment 3, when the MAC layer determines that the uplink grant corresponding to the first PUSCH is an uplink grant with a high priority, the MAC layer may further generate and send data of the first PUSCH to the physical layer, and the physical layer sends the data of the first PUSCH to the outside.

[0111] The above describes the first, second and third examples of the data transmission method according to the second embodiment of the present invention.

[0112] In the second embodiment of the present invention, the terminal device 102 may transmit data using the method described in any one of the first, second, and third embodiments.

[0113] <Third embodiment of the embodiment> A third embodiment of the present invention provides a data transmission method, which is applied to a terminal device, for example the terminal device 102 .

[0114] In the third embodiment of the present invention, the terminal device 102 may choose to adopt the data transmission method described in the first or second embodiment.

[0115] 13 is a schematic diagram of a data transmission method according to the third embodiment of the present invention. As shown in FIG. 13, the method includes the following steps:

[0116] Step 1301: When a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device 102 determines whether to transmit or not transmit the second physical uplink shared channel (PUSCH) based on the types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH).

[0117] In at least one embodiment, when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG) and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), the terminal device 102 determines to transmit the second physical uplink shared channel (PUSCH), i.e., adopts the first embodiment of the present invention. Also, when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), the physical layer determines not to transmit the second physical uplink shared channel (PUSCH), i.e., adopts the first embodiment of the present invention.

[0118] In another embodiment, when the first physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG) and the second physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG), the terminal device 102 determines not to transmit the second physical uplink shared channel (PUSCH), i.e. adopts the second embodiment of the present invention. Also, when the first physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) scheduled by the downlink control information (DCI) and the second physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG), the physical layer determines to transmit the second physical uplink shared channel (PUSCH), i.e. adopts the first embodiment of the present invention.

[0119] In the third embodiment of the present invention, the terminal device 102 may select example 1, example 2, or example 3 in the second embodiment of the present invention and transmit data.

[0120] For example, when the first physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG) and the second physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG), the terminal device 102 uses the method of embodiment 2 or embodiment 3. Also, when the first physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) and the second physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG), the terminal device 102 uses the method of embodiment 1.

[0121] In another example, when the first physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG) and the second physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG), the terminal device 102 uses the method of embodiment 2. Also, when the first physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) and the second physical uplink shared channel (PUSCH) is the physical uplink shared channel (PUSCH) of the configuration grant (CG), the terminal device 102 uses the method of embodiment 3.

[0122] <Fourth embodiment of the embodiment> A fourth embodiment of the present invention provides a data transmission device, which is applied to a terminal device, for example the terminal device 102.

[0123] 14 is a schematic diagram of a data transmission device according to a fourth embodiment of the present invention. As shown in FIG. 14, the data transmission device 1400 may include a first processing unit 1401, a second processing unit 1402, or a third processing unit 1403.

[0124] The first processing unit 1401 may control the terminal device so that the terminal device executes the data transmission method described in the first embodiment of the present invention. For the description of the data transmission method implemented by the first processing unit 1401, the description of the data transmission method in the first embodiment of the present invention may be referred to.

[0125] The second processing unit 1402 may control the terminal device so that the terminal device executes the data transmission method described in the second embodiment of the present invention. For the description of the data transmission method implemented by the second processing unit 1402, reference may be made to the description of the data transmission method in the second embodiment of the present invention.

[0126] The third processing unit 1403 may control the terminal device so that the terminal device executes the data transmission method described in the third embodiment of the present invention. For the description of the data transmission method implemented by the third processing unit 1403, reference may be made to the description of the data transmission method in the third embodiment of the present invention.

[0127] Fifth embodiment of the present invention The fifth embodiment of the present invention provides a terminal device, which includes the data transmitting device 1400 described in the third embodiment.

[0128] FIG 15 is a schematic block diagram of a system configuration of a terminal device 1500 according to a fifth embodiment of the present invention. As shown in FIG 15, the terminal device 1500 may include a processor 1510 and a memory 1520, and the memory 1520 is connected to the processor 1510. Note that this figure is exemplary, and other types of structures may be used to supplement or replace this structure to realize communication functions or other functions.

[0129] In one aspect, the functions of the data transmission device 1400 may be integrated into the processor 1510. Here, the processor 1510 may be configured to implement the method of the first embodiment, the second embodiment, or the third embodiment.

[0130] In another aspect, the data transmitting device 1400 may be respectively configured with the processor 1510, for example, the data transmitting device 1400 may be a chip connected to the processor 1510, and the functions of the data transmitting device 1400 may be realized under the control of the processor 1510.

[0131] As shown in Fig. 15, the terminal device 1500 may further include a communication module 1530, an input unit 1540, a display 1550, and a power source 1560. It is not necessary for the terminal device 1500 to include all the units shown in Fig. 15. The terminal device 1500 may further include units not shown in Fig. 15, and may refer to the prior art.

[0132] As shown in FIG. 15, the processor 1510, also referred to as a controller or operation control unit, may include a microprocessor or other processing device and / or logic device, and the processor 1510 accepts input and controls the operation of each part of the terminal device 1500.

[0133] Here, the memory 1520 may be, for example, one or more of a buffer, a flash memory, a hard disk, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices, and stores a program for executing various data and related information. The processor 1510 may also execute the program stored in the memory 1520 to realize information storage or processing, etc. The other components are similar to the prior art, and therefore the description thereof is omitted here. Each part of the terminal device 1500 may be realized by specific hardware, firmware, software, or a combination thereof without departing from the scope of the present invention.

[0134] Sixth embodiment of the present invention The sixth embodiment of the present invention further provides a communication system including a network device and a terminal device according to the fifth embodiment.

[0135] The above-mentioned apparatus and method of the present invention may be realized by hardware or by a combination of hardware and software.The present invention relates to a computer readable program which, when executed by a logic unit, causes the logic unit to realize the above-mentioned apparatus or components, or to realize the above-mentioned various methods or steps.The present invention relates to a storage medium for storing the above-mentioned program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0136] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module in a computer program flow, or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be realized by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0137] The software module may be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from the storage medium and writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal, or in a memory card inserted in the mobile terminal. For example, if the device (e.g., a mobile terminal) uses a MEGA-SIM card or a large capacity flash memory device with a relatively large capacity, the software module may be stored in the MEGA-SIM card or the large capacity flash memory device.

[0138] One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more of the functional blocks and / or one or more combinations of functional blocks in the functional block diagrams illustrated in the drawings may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0139] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0140] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above-mentioned examples. (Appendix 1) A data transmission method applied to a terminal device, comprising: a terminal device transmitting a second physical uplink shared channel (PUSCH) when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain. (Appendix 2) The method of claim 1, wherein the physical layer of the terminal device receives data of the second physical uplink shared channel (PUSCH) from a medium access control (MAC) layer at a time later than the time the physical layer receives data of the first physical uplink shared channel (PUSCH). (Appendix 3) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by a first downlink control information (DCI), 3. The method of claim 1 or 2, wherein the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 4) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG); 3. The method of claim 1 or 2, wherein the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 5) A data transmission method applied to a terminal device, comprising: When a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain, the terminal device does not transmit the second physical uplink shared channel (PUSCH). (Appendix 6) A time when the physical layer of the terminal device receives data of the second physical uplink shared channel (PUSCH) from a medium access control (MAC) layer is later than a time when the physical layer receives data of the first physical uplink shared channel (PUSCH); The method comprises: The physical layer further includes transmitting transmission indication information to the medium access control (MAC) layer; The method of claim 5, wherein the transmission indication information is used to notify the medium access control (MAC) layer that data on the second physical uplink shared channel (PUSCH) is not being transmitted. (Appendix 7) 7. The method of claim 6, further comprising: the medium access control (MAC) layer determining an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a low priority uplink grant. (Appendix 8) 7. The method of claim 6, further comprising: the medium access control (MAC) layer determining an uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high priority uplink grant. (Appendix 9) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI), 9. The method of claim 6, wherein the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 10) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG); 9. The method of claim 6, wherein the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 11) The terminal device does not transmit the second physical uplink shared channel (PUSCH), The method of claim 5, further comprising: when a medium access control (MAC) layer of the terminal device generates data for the first physical uplink shared channel (PUSCH), the medium access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH). (Appendix 12) The medium access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH), 12. The method of claim 11, comprising: the medium access control (MAC) layer not determining an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant and not generating data for the second physical uplink shared channel (PUSCH). (Appendix 13) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) or a physical uplink shared channel (PUSCH) of a configuration grant (CG); 13. The method of claim 12, wherein the second physical uplink shared channel (PUSCH) data is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 14) When there is no first physical uplink shared channel (PUSCH), the medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, and generates data for the second physical uplink shared channel (PUSCH); 14. The method of claim 13, wherein the uplink grant corresponding to the first physical uplink shared channel (PUSCH) is obtained as a medium access control protocol data unit (MAC PDU). (Appendix 15) The medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, 15. The method of claim 14, further comprising: when there is no physical uplink shared channel (PUSCH) of another higher priority configuration grant (CG) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, there is no physical uplink shared channel (PUSCH) of higher priority or the same priority scheduled by downlink control information (DCI) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, and there is no physical uplink control channel (PUCCH) transmitted by a scheduling request (SR) of higher priority that overlaps with the second physical uplink shared channel (PUSCH), the medium access control (MAC) layer determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, and generates data for the second physical uplink shared channel (PUSCH). (Appendix 16) generating a medium access control protocol data unit (MAC PDU) for an uplink grant corresponding to data of the second physical uplink shared channel (PUSCH) when the first physical uplink shared channel (PUSCH) is not present; 13. The method of claim 12, wherein the uplink grant corresponding to the first physical uplink shared channel (PUSCH) is obtained as a medium access control protocol data unit (MAC PDU). (Appendix 17) The terminal device does not transmit the second physical uplink shared channel (PUSCH), The method of claim 5, comprising: a medium access control (MAC) layer of the terminal device not determining an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, and not generating data for the second physical uplink shared channel (PUSCH). (Appendix 18) 18. The method of claim 17, further comprising: if there is no first physical uplink shared channel (PUSCH), a medium access control (MAC) layer of the terminal device determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant, and generates data for the second physical uplink shared channel (PUSCH). (Appendix 19) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) or a physical uplink shared channel (PUSCH) of a configuration grant (CG); 19. The method of claim 18, wherein the second physical uplink shared channel (PUSCH) data is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 20) 20. The method of claim 19, further comprising: when there is no physical uplink shared channel (PUSCH) of another higher priority configuration grant (CG) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, there is no physical uplink shared channel (PUSCH) of higher priority or the same priority scheduled by downlink control information (DCI) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, and there is no physical uplink control channel (PUCCH) transmitted by a high priority scheduling request (SR) that overlaps with the second physical uplink shared channel (PUSCH), a medium access control (MAC) layer of the terminal device determines an uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high priority uplink grant. (Appendix 21) The method of claim 5, further comprising: the terminal device transmitting the first physical uplink shared channel (PUSCH). (Appendix 22) The terminal device transmits the first physical uplink shared channel (PUSCH), 22. The method of claim 21, comprising: the medium access control (MAC) layer determining an uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high priority uplink grant; and generating data for the first physical uplink shared channel (PUSCH). (Appendix 23) The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI), 23. The method of claim 22, wherein the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG). (Appendix 24) The medium access control (MAC) layer determines an uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high priority uplink grant, When there is no physical uplink shared channel (PUSCH) of another high priority configuration grant (CG) that at least partially overlaps with the first physical uplink shared channel (PUSCH) in the time domain, and there is no physical uplink control channel (PUCCH) transmitted by a high priority scheduling request (SR) that at least partially overlaps with the first physical uplink shared channel (PUSCH) in the time domain, the medium access control (MAC) layer determines an uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high priority uplink grant; 24. The method of claim 23, wherein a physical layer priority of the configuration grant (CG) is higher than a physical layer priority of the first physical uplink shared channel (PUSCH). (Appendix 25) A data transmission method applied to a terminal device, comprising: and when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority and a transmission of the first physical uplink shared channel (PUSCH) and a transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in a time domain, the terminal device determining to transmit or not transmit the second physical uplink shared channel (PUSCH) based on types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH). (Appendix 26) The terminal device determines whether to transmit or not transmit the second physical uplink shared channel (PUSCH) based on the types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH), When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), determining that the terminal device transmits the second physical uplink shared channel (PUSCH); 26. The method of claim 25, comprising: when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), determining by the physical layer not to transmit the second physical uplink shared channel (PUSCH). (Appendix 27) The terminal device determines whether to transmit or not transmit the second physical uplink shared channel (PUSCH) based on the types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH), When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG), determining that the terminal device does not transmit the second physical uplink shared channel (PUSCH); determining, by the physical layer, to transmit the second physical uplink shared channel (PUSCH) if the first physical uplink shared channel (PUSCH) is a downlink control information (DCI) scheduled physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) is a configuration grant (CG) physical uplink shared channel (PUSCH).

Claims

1. A terminal device, A transmitter that transmits a first physical uplink shared channel (PUSCH) or a second physical uplink shared channel (PUSCH); A processing unit that cancels transmission of the second PUSCH when the first PUSCH and the second PUSCH have the same physical layer priority and the first PUSCH and the second PUSCH partially or completely overlap in a time domain, When the transmission of the second PUSH is canceled by the physical layer of the terminal device, a medium access control (MAC) layer of the terminal device does not obtain a PDU of the second PUSH, When the first PUSCH and the second PUSCH have the same physical layer priority and the first PUSCH and the second PUSCH partially or completely overlap in the time domain, the processing unit: not considering an uplink grant associated with the second physical uplink shared channel (PUSCH) as a prioritized uplink grant by the medium access control (MAC) layer so as not to obtain the PDU of the second PUSCH; A terminal device that controls the medium access control (MAC) layer to regard an uplink grant related to the first physical uplink shared channel (PUSCH) as a prioritized uplink grant, obtains a PDU of the first PUSCH, and transmits the PDU to a physical layer.

2. The terminal device according to claim 1 , wherein the physical layer of the terminal device receives the data of the second PUSH from a MAC layer later than the data of the first PUSH.

3. The first PUSCH is a physical uplink shared channel (PUSCH) scheduled by a first downlink control information (DCI); The terminal device according to claim 1 , wherein the second PUSCH is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

4. The first PUSCH is a physical uplink shared channel (PUSCH) of a configuration grant (CG); The terminal device according to claim 1 , wherein the second PUSCH is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

5. 2. The terminal device according to claim 1, wherein when the first PUSH and the second PUSH have the same physical layer priority and the first PUSH and the second PUSH partially or completely overlap in the time domain, the processing unit determines, via the MAC layer, an uplink grant corresponding to the second PUSH as an uplink grant of a lower priority, and does not generate a PDU for the second PUSH.

6. The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) or a physical uplink shared channel (PUSCH) of a configuration grant (CG); The terminal device according to claim 5 , wherein the data of the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

7. The terminal device according to claim 1 , wherein, when the first PUSH can be transmitted by the physical layer of the terminal device, the processing unit determines whether to obtain a PDU for the first PUSH by the medium access control (MAC) layer.

8. The terminal device according to claim 7, wherein if the uplink grant associated with the first PUSH is regarded as a prioritized uplink grant, the processing unit obtains a PDU for the first PUSH by the MAC layer of the terminal device.

9. The first PUSCH is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) or a physical uplink shared channel (PUSCH) of a configuration grant (CG); The terminal device according to claim 8 , wherein the second PUSCH is a physical uplink shared channel (PUSCH) of a configuration grant (CG).

10. 10. The terminal device according to claim 9, wherein when there is no physical uplink shared channel (PUSCH) of another high priority configuration grant (CG) that at least partially overlaps with the second PUSCH in the time domain, there is no physical uplink shared channel (PUSCH) of high priority or the same priority scheduled by downlink control information (DCI) that at least partially overlaps with the second physical uplink shared channel (PUSCH) in the time domain, and there is no physical uplink control channel (PUCCH) transmitted by a high priority scheduling request (SR) that at least partially overlaps with the second physical uplink shared channel (PUSCH), the processing unit determines the uplink grant corresponding to the second PUSCH as a high priority uplink grant.

11. The processing unit includes: determining an uplink grant corresponding to the first PUSCH as an uplink grant of high priority; The terminal device according to claim 1 , wherein the first PUSCH data is generated by the medium access control (MAC) layer.

12. A base station, A processing section; A receiving unit connected to the processing unit and configured to receive a first physical uplink shared channel (PUSCH) or a second physical uplink shared channel (PUSCH) from a terminal, When the first PUSCH and the second PUSCH have the same physical layer priority and the first PUSCH and the second PUSCH partially or completely overlap in the time domain, the transmission of the second PUSCH is canceled by the terminal; When the transmission of the second PUSH is canceled by the physical layer of the terminal, a medium access control (MAC) layer of the terminal does not obtain a PDU of the second PUSH; When the first PUSCH and the second PUSCH have the same physical layer priority and the first PUSCH and the second PUSCH partially or completely overlap in the time domain, the processing unit: not considering an uplink grant associated with the second physical uplink shared channel (PUSCH) as a prioritized uplink grant by the medium access control (MAC) layer so as not to obtain the PDU of the second PUSCH; A base station that controls a medium access control (MAC) layer to regard an uplink grant related to the first physical uplink shared channel (PUSCH) as a prioritized uplink grant, obtains a PDU of the first PUSCH, and transmits the PDU to a physical layer.

13. 1. A communication system comprising: A terminal transmitting a first physical uplink shared channel (PUSCH) or a second physical uplink shared channel (PUSCH); A base station that receives the first PUSCH or the second PUSCH from the terminal, When the first PUSCH and the second PUSCH have the same physical layer priority and the first PUSCH and the second PUSCH partially or completely overlap in the time domain, the terminal cancels transmission of the second PUSCH; When the transmission of the second PUSH is canceled by the physical layer of the terminal, a medium access control (MAC) layer of the terminal does not obtain a PDU of the second PUSH; When the first PUSCH and the second PUSCH have the same physical layer priority and the first PUSCH and the second PUSCH partially or completely overlap in the time domain, the terminal: not considering an uplink grant associated with the second physical uplink shared channel (PUSCH) as a prioritized uplink grant by the medium access control (MAC) layer so as not to obtain the PDU of the second PUSCH; The medium access control (MAC) layer regards an uplink grant associated with the first physical uplink shared channel (PUSCH) as a prioritized uplink grant, acquires a PDU of the first PUSCH, and controls the PDU to be transmitted to a physical layer.

Images