Method, device and communication system for sending data

Abstract

The present application provides a method, apparatus, and communication system for transmitting data. The apparatus for transmitting data includes a first processing unit, the first processing unit being configured to: cause a terminal device to 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 the transmission of the first physical uplink shared channel (PUSCH) and the transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of wireless communication technologies. Background Art

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

[0003] For example, when the downlink air interface time-frequency domain resources of two terminals conflict, the network device prioritizes the transmission of the service with the higher priority in the two terminal devices and notifies the terminal device whose resources have been preempted through special downlink control information (for example, DCI2-1). This resource preemption mechanism allows the data of the high-priority service to be sent with a higher priority, thereby improving the real-time performance and reliability of the high-priority service. For another example, resource preemption within the terminal device can also be based on the priority of the service.

[0004] For uplink transmission conflicts within the terminal, the media access control (MAC) layer and the physical (PHY) layer independently determine the preemption priority. 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] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art. Summary of the Invention

[0006] Since the MAC layer and the PHY layer independently determine the preemption priority, a transmission determined as high priority at the MAC layer may be determined as low priority at the PHY layer. Uplink permitted data that the MAC layer considers to be high priority may be discarded at the PHY layer. In this way, the data automatically sent by the terminal device on the configuration grant (CG) cannot be sent and is lost.

[0007] The inventors of this application discovered that when the physical layer priorities of two physical uplink shared channels (PUSCHs) are the same and the transmission of the two PUSCHs at least partially overlaps in the time domain, there is no regulation in the prior art on how the terminal device should transmit the data of the two PUSCHs.

[0008] The embodiments of the present application provide a method, apparatus, and communication system for transmitting data, wherein a terminal device transmits or does not transmit the 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 the transmission of the first physical uplink shared channel (PUSCH) and the transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain. Thus, the reliability of communication services can be ensured.

[0009] According to a first aspect of an embodiment of the present application, a method for sending data is provided, which is applied to a terminal device, and the method includes:

[0010] 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) at least partially overlap in the time domain, the terminal device sends the second physical uplink shared channel (PUSCH).

[0011] According to a second aspect of an embodiment of the present application, a method for sending data is provided, which is applied to a terminal device, and the method includes:

[0012] 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) at least partially overlap in the time domain, the terminal device does not send the second physical uplink shared channel (PUSCH).

[0013] According to a third aspect of an embodiment of the present application, a method for sending data is provided, which is applied to a terminal device, and the method includes: when a first physical uplink shared channel (PUSCH) and a second physical uplink shared channel (PUSCH) have the same physical layer priority, and the sending of the first physical uplink shared channel (PUSCH) and the sending of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device determines whether to send or not to send the second physical uplink shared channel (PUSCH) according to the types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH).

[0014] According to a fourth aspect of an embodiment of the present application, a device for sending data is provided, which is applied to a terminal device, and the device executes the method for sending data of the first aspect, the second aspect, or the third aspect of the embodiment of the present application.

[0015] According to a fifth aspect of an embodiment of the present application, a terminal device is provided, which has the device for sending data described in the fourth aspect of an embodiment of the present application.

[0016] According to a sixth aspect of an embodiment of the present application, a communication system is provided, which has the terminal device and the network device described in the fifth aspect of the embodiment of the present application.

[0017] According to the seventh aspect of the embodiments of the present application, a computer-readable program is provided, wherein when the program is executed in an apparatus or terminal device for sending data, the program causes the apparatus or terminal device for sending data to execute the method for sending data of the first aspect, the second aspect or the third aspect of the embodiments of the present application.

[0018] According to the eighth aspect of the embodiments of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables an apparatus for sending data or a terminal device to execute the method for sending data of the first aspect, the second aspect or the third aspect of the embodiments of the present application.

[0019] The beneficial effect of the embodiments of the present application is that: when the first PUSCH and the second PUSCH have the same physical layer priority, and the sending of the first PUSCH and the sending of the second PUSCH at least partially overlap in the time domain, the terminal device sends or does not send the second PUSCH. As a result, the media access control layer and the physical layer of the terminal device can have a unified processing on whether to send PUSCH, avoiding the loss of data automatically sent by the terminal device on the configuration grant (CG), thereby ensuring the reliability of the communication service.

[0020] With reference to the following description and drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope thereby. Within the scope of the terms of the appended claims, the embodiments of the present application include many variations, modifications, and equivalents.

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

[0022] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0024] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0025] Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0026] Figure 2 This is a schematic diagram of the physical layer discarding high-priority PUSCH;

[0027] Figure 3 This is another diagram of the physical layer dropping a high-priority PUSCH;

[0028] Figure 4 is a schematic diagram of a method for sending data according to the first aspect of an embodiment of the present application;

[0029] Figure 5 is a schematic diagram of the MAC layer and physical layer operations in the first aspect of the embodiment of the present application;

[0030] Figure 6 is another schematic diagram of the MAC layer and physical layer operations in the first aspect of the embodiment of the present application;

[0031] Figure 7 is a schematic diagram of a method for sending data in embodiment 1 of the second aspect of the embodiments of the present application;

[0032] Figure 8 is a schematic diagram of MAC layer and physical layer operations in embodiment 1 of the second aspect of the embodiments of the present application;

[0033] Figure 9 is another schematic diagram of the MAC layer and physical layer operations in embodiment 1 of the second aspect of the embodiments of the present application;

[0034] Figure 10 is a schematic diagram of a method for sending data in embodiment 2 of the second aspect of the embodiments of the present application;

[0035] Figure 11is a schematic diagram of MAC layer and physical layer operations in embodiment 2 of the second aspect of the embodiments of the present application;

[0036] Figure 12 is a schematic diagram of MAC layer and physical layer operations in embodiment 2 of the second aspect of the embodiments of the present application;

[0037] Figure 13 is a schematic diagram of a method for sending data according to the third aspect of an embodiment of the present application;

[0038] Figure 14 is a schematic diagram of a device for sending data according to a fourth aspect of an embodiment of the present application;

[0039] Figure 15 It is a schematic block diagram of the system structure of the terminal device of the fifth aspect of the embodiment of the present application. DETAILED DESCRIPTION

[0040] The foregoing and other features of the present application will become apparent from the following description with reference to the accompanying drawings. In the description and drawings, specific embodiments of the present application are disclosed, which illustrate some embodiments in which the principles of the present application can be employed. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations, and equivalents falling within the scope of the appended claims. Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application.

[0041] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0042] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0043] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0044] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), etc., and / or other currently known or future communication protocols to be developed.

[0045] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0046] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific 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.

[0047] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A user equipment may be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0048] Among them, user devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0049] For another example, in scenarios such as the Internet of Things (IoT), the user equipment may also be a machine or device for monitoring or measurement, such as but not limited to: machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and the like.

[0050] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0051] Figure 1 Schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation in which a terminal device and a network device are used as an example. Figure 1 As shown, the communication system 100 may include a network device 101 and a terminal device 102. For simplicity, Figure 1 Only one terminal device is used as an example for description.

[0052] In the embodiment of the present application, existing services or future services can be carried out 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), etc.

[0053] Among them, the terminal device 102 can send data to the network device 101, for example, using an unauthorized transmission mode. The network device 201 can receive data sent by one or more terminal devices 102 and feedback information (such as a correct response ACK / negative response NACK) to the terminal device 102. The terminal device 102 can confirm the end of the transmission process, or can continue to transmit new data, or can retransmit data based on the feedback information.

[0054] The following description uses the network device in the communication system as the receiving end or sending end, and the terminal device as the sending end or receiving end as an example, but the present application is not limited to this. The sending end and / or receiving end can also be other devices. For example, the present application is not only applicable to uplink unlicensed transmission between a network device and a terminal device, but also to side link unlicensed transmission between two terminal devices.

[0055] In the following embodiments of the present application, CG non-transmission means that the MAC PDU data generated according to the configuration of the CG is not sent by the physical layer, and the MAC PDU can also be called an unsent MAC PDU.

[0056] The application scenarios of this application are described below.

[0057] Transmission conflicts within the terminal device may occur between different Physical Uplink Shared Channel (PUSCH) resource grants, such as between two semi-statically configured grants (CG) of PUSCH, or between a configured grant and a dynamically scheduled PUSCH. For conflicts between PUSCH resource grants and different scheduling request (SR) transmissions or positive acknowledgment (ACK) / negative acknowledgment (NACK) indications for downlink PUSCH, the terminal device prioritizes the transmission of PUSCH, SR or physical uplink control channel (PUCCH) ACK / NACK for high-priority services. The media access control (MAC) layer of the terminal device ensures that high-priority services are transmitted first by determining the PUSCH grant or SR for priority transmission based on the logical channel priority. When multiple logical channel data are multiplexed in a PUSCH transport block, the priority of the PUSCH grant is determined by the logical channel with the highest priority multiplexed in the transport block, and the priority of an SR transmission is determined by the logical channel priority corresponding to the SR. In the event of conflict between two or more resources, the highest priority PUSCH grant or the highest priority SR is determined as high priority and transmitted by the MAC layer first, and other grants or SR transmissions are determined as low priority and preempted.

[0058] For uplink transmission conflicts within the terminal, the MAC layer and the PHY layer independently determine the transmission priority. 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 with a configuration grant (CG) is indicated to the terminal device by the network device through a radio resource control (RRC) message. The physical layer priority (high or low) of the dynamically scheduled PUSCH is indicated to the terminal device by the network device through the PDCCH signaling that schedules the PUSCH.

[0059] The network equipment configures each logical channel with a logical channel priority (1 to 16), a list of CG configurations allowed for use, and a physical layer priority (high or low). The uplink PUSCH grant configured for each CG can multiplex multiple logical channel data that are allowed to be multiplexed. A dynamically scheduled uplink PUSCH grant can multiplex data from multiple logical channels with the same physical layer priority. If a PUSCH grant can multiplex multiple logical channel data, at the MAC layer of the terminal device, the priority of the uplink grant is determined by the logical channel with the highest priority that can be multiplexed, and the priority of an SR transmission is determined by the priority of the logical channel corresponding to the SR. In the event of a conflict between two or more resources, the PUSCH grant or SR with the highest priority is transmitted by the MAC layer first, and other grants or SRs are preempted and do not trigger uplink transmission.

[0060] At the MAC layer, if the uplink grant is a high-priority (priority transmission) uplink grant, the terminal device obtains the MAC PDU from the multiplexing and encapsulation entity and causes the HARQ process associated with the grant to trigger data transmission. If it is a low-priority (i.e., preempted) grant, the terminal device does not obtain the MAC PDU and trigger the transmission of data. For a grant temporarily determined as high priority, the terminal device may have obtained the MAC PDU and triggered the physical layer transmission of the data, but it may be re-determined as a low-priority grant when higher-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 the generated data. A higher-priority grant will also generate data and trigger physical layer transmission. At the PHY layer of the terminal device, the uplink transmission priority is determined by the physical layer priority of the PUSCH. If the MAC layer instructs the physical layer to transmit two uplink data that overlap on resources, the physical layer gives priority to transmitting the uplink data with a higher physical layer priority.

[0061] However, if two PUSCHs overlap and have the same physical layer priority, data with a high priority at the MAC layer may be discarded by the physical layer. In this way, the configuration grant (CG) data automatically sent by the terminal device cannot be sent and is lost. If the CG data determined as high priority by the MAC layer is discarded by the physical layer, the CG data will not be automatically retransmitted by the MAC layer, because the MAC can only actively retransmit data determined as low priority by the MAC layer, and the network device will not schedule the retransmission of the CG data because the CG data has not actually been sent to the network device.

[0062] Figure 2 This is a schematic diagram of the physical layer discarding high-priority PUSCH. Figure 2 As shown, the transmission of CG's PUSCH and the transmission of dynamic scheduling grant (DG)'s PUSCH at least partially overlap in the time domain, and CG's PUSCH and DG's PUSCH have the same physical layer priority. The MAC layer first generates a dynamically scheduled protocol data unit (PDU) 210, and then generates a higher priority CG's PDU 220, but the physical layer gives priority to sending the dynamically scheduled grant's PUSCH 211. DG's PUSCH 211 corresponds to DG's PDU 210.

[0063] Figure 3 This is another diagram showing the physical layer discarding high priority PUSCH. Figure 3As shown, the transmission of PUSCH of CG1 and the transmission of PUSCH of CG2 at least partially overlap in the time domain, and PUSCH of CG1 and PUSCH of CG2 have the same physical layer priority. The MAC layer first generates the protocol data unit (PDU) 310 of CG1, and then generates a higher priority PDU 320 of CG2, but the physical layer gives priority to sending PUSCH 311 of CG1, where PUSCH 311 of CG1 corresponds to PDU310 of CG 1.

[0064] First aspect of the embodiment

[0065] A first aspect of an embodiment of the present application relates to a method for sending data, which is applied to a terminal device, such as the terminal device 102.

[0066] Figure 4 is a schematic diagram of a method for sending data according to the first aspect of an embodiment of the present application. Figure 4 As shown, the method for sending data may include:

[0067] Operation 401: When a first physical uplink shared channel (PUSCH) and a 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) at least partially overlap in the time domain, the terminal device transmits the second physical uplink shared channel (PUSCH).

[0068] According to the first aspect of this 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 sends the second PUSCH, thereby ensuring the reliability of the communication service.

[0069] In the first aspect of this embodiment, the physical layer of the terminal device 102 receives the data of the second physical uplink shared channel (PUSCH) from the media access control (MAC) layer later than the time when the data of the first physical uplink shared channel (PUSCH) is received, that is, the second PUSCH has a higher priority than the first PUSCH. As a result, the physical layer can send the data of the second PUSCH with a higher priority.

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

[0071] In at least another embodiment, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0072] Next, operation 401 will be described in detail.

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

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

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

[0076] At the MAC layer, for a grant that is temporarily determined to be high priority, the terminal device 102 may have obtained PUSCH data and triggered the PHY layer transmission of the data, but it may be re-determined as a low priority grant when higher priority logical channel data arrives, because the priority of the next uplink grant or SR may be higher than the priority of the uplink grant of the generated data. Therefore, the higher priority grant will also obtain PUSCH data and send it to the PHY layer. At the PHY layer of the terminal, the uplink transmission priority is determined by the physical layer priority of the PUSCH, and the physical layer gives priority to transmitting uplink data with a higher physical layer priority. However, if two PUSCHs overlap and have the same physical layer priority, the data with a higher priority at the MAC layer may be discarded by the physical layer.

[0077] Therefore, in the first aspect of this 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) at least partially overlap in the time domain, if the physical layer of the terminal device 102 receives the data of the second physical uplink shared channel (PUSCH) from the media access control (MAC) layer later than the time when the data of the first physical uplink shared channel (PUSCH) is received, the terminal device 102 can send the second physical uplink shared channel (PUSCH) instead of sending the data of the first PUSCH, thereby avoiding the problem of data with high priority at the MAC layer (i.e., the data of the second PUSCH) being discarded by the PHY layer.

[0078] Figure 5 FIG. 1 is a schematic diagram of the MAC layer and physical layer operations in the first aspect of the embodiment of the present application. Figure 5 As shown, the first PUSCH 510 is a PUSCH scheduled by the first downlink control information (i.e., dynamic scheduling permission DG), the second PUSCH 520 is a PUSCH configured with authorization (CG), the data of the second PUSCH 520 arrives at the physical layer later than the data of the first PUSCH 510 arrives at the physical layer, and the physical layer of the terminal device 102 sends the second PUSCH 520.

[0079] Figure 6 FIG. 1 is another schematic diagram of the MAC layer and physical layer operations in the first aspect of the embodiment of the present application. Figure 6 As shown, the first PUSCH 610 is the PUSCH of CG 1, and the second PUSCH 620 is the PUSCH of CG 2. The data of the second PUSCH 620 arrives at the physical layer later than the data of the first PUSCH 610. The physical layer of the terminal device 102 sends the second PUSCH 620.

[0080] Second aspect of the embodiment

[0081] A second aspect of an embodiment of the present application relates to a method for sending data, which is applied to a terminal device, such as the terminal device 102.

[0082] In the method for sending data of the second aspect of an embodiment of the present application, when the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority, and the sending of the first physical uplink shared channel (PUSCH) and the sending of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device 102 does not send the second physical uplink shared channel (PUSCH).

[0083] In a second aspect of the embodiment of the present application, the method for sending data may further include: the terminal device 102 sends a first physical uplink shared channel (PUSCH).

[0084] Example 1

[0085] Figure 7 is a schematic diagram of a method for sending data in embodiment 1 of the second aspect of the embodiment of the present application, such as Figure 7 As shown, the method includes:

[0086] Operation 701: When a first physical uplink shared channel (PUSCH) and a 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) at least partially overlap in the time domain, the terminal device 102 does not transmit the second physical uplink shared channel (PUSCH); and

[0087] Operation 702: The physical layer sends transmission indication information to the medium access control (MAC) layer, where the transmission indication information is used to notify the medium access control (MAC) layer that the second physical uplink shared channel (PUSCH) data is not sent.

[0088] In embodiment 1, the time when the physical layer of the terminal device 102 receives the data of the second physical uplink shared channel (PUSCH) from the media access control (MAC) layer is later than the time when the data of the first physical uplink shared channel (PUSCH) is received, that is, the MAC layer priority of the second PUSCH is higher than the MAC layer priority of the first PUSCH.

[0089] Through operation 702, the physical layer can notify the MAC layer that the data of the second physical uplink shared channel (PUSCH) has not been sent. As a result, the MAC layer can perform subsequent processing on the second PUSCH to avoid data loss of the second PUSCH and improve the reliability of the communication service.

[0090] like Figure 7 As shown, the method may further include:

[0091] Operation 703: 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.

[0092] The MAC layer may perform operation 703 upon receiving the transmission indication information sent by the physical layer in operation 702. Through operation 703, the MAC layer may automatically initiate retransmission of the data of the second PUSCH to avoid data loss.

[0093] like Figure 7 As shown, the method may further include:

[0094] Operation 704: The medium access control (MAC) layer determines the uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high-priority uplink grant.

[0095] The MAC layer may perform operation 704 upon receiving the transmission indication information sent by the physical layer in operation 702 .

[0096] 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) configured with a grant (CG); or, the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0097] Figure 8 FIG. 1 is a schematic diagram of the MAC layer and physical layer operations in Example 1. Figure 8 As shown, the first PUSCH 810 is a PUSCH scheduled by the first downlink control information (i.e., dynamic scheduling grant DG), the second PUSCH 820 is a PUSCH configured with a 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. Figure 8 As shown, the physical layer of the terminal device 102 does not send the second PUSCH 820, and the physical layer sends a transmission indication to the MAC layer, which is used to notify the MAC layer that the data of the second PUSCH 820 has not been sent. In addition, upon receiving the transmission indication, the MAC layer can set the uplink grant (i.e., CG) corresponding to the second PUSCH 820 to a low-priority grant and set the uplink grant corresponding to the first PUSCH 810 to a high-priority grant.

[0098] Figure 9 FIG. 1 is another schematic diagram of the MAC layer and physical layer operations in Example 1. Figure 9 As shown, the first PUSCH 910 is a PUSCH configured with grant (CG) 1, and the second PUSCH 920 is a PUSCH configured with CG 2. The time when the data of the second PUSCH 920 arrives at the physical layer is later than the time when the data of the first PUSCH 910 arrives at the physical layer. Figure 9As shown, the physical layer of the terminal device 102 does not send the second PUSCH 920, and the physical layer sends a transmission indication to the MAC layer, which is used to notify the MAC layer that the data of the second PUSCH 920 has not been sent. In addition, upon receiving the transmission indication, the MAC layer can set the uplink grant corresponding to the second PUSCH 920 (i.e., CG 2) as a low-priority grant and the uplink grant corresponding to the first PUSCH 910 (i.e., CG 1) as a high-priority grant.

[0099] Example 2

[0100] Figure 10 is a schematic diagram of a method for sending data in embodiment 2 of the second aspect of the embodiments of the present application, such as Figure 10 As shown, the method includes:

[0101] Operation 1001: 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) at least partially overlap in the time domain, the terminal device 102 does not transmit the second physical uplink shared channel (PUSCH).

[0102] In embodiment 2, operation 1001 may include: if a medium access control (MAC) layer of the terminal device 102 has generated data for the first physical uplink shared channel (PUSCH), then the medium access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH). Since the MAC layer does not generate data for the second PUSCH, the terminal device 102 cannot send data for the second PUSCH, thereby avoiding inconsistent operations between the MAC layer and the physical layer regarding whether to send the second PUSCH.

[0103] There are two ways to implement the medium access control (MAC) layer not generating data for the second physical uplink shared channel (PUSCH).

[0104] In the first manner, the medium access control (MAC) layer does not determine the 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).

[0105] Among them, if there is no first physical uplink shared channel (PUSCH), and the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained the media access control protocol data unit (MAC PDU): the media access control (MAC) layer determines that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a high-priority uplink grant, and generates data for the second physical uplink shared channel (PUSCH); otherwise, the media access control (MAC) layer determines that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a low-priority uplink grant, and does not generate data for the second physical uplink shared channel (PUSCH).

[0106] Furthermore, if no other physical uplink shared channel (PUSCH) with a higher priority configuration grant (CG) overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, no physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) with a higher priority or the same priority overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, and no physical uplink control channel (PUCCH) transmitted with a higher priority scheduling request (SR) overlaps with the second physical uplink shared channel (PUSCH), then the media access control (MAC) layer determines that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a high-priority uplink grant and generates data for the second physical uplink shared channel (PUSCH); otherwise, the media access control (MAC) layer does not determine the 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).

[0107] Therefore, in the first method, since there is already a first physical uplink shared channel (PUSCH) and the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained the media access control protocol data unit (MAC PDU), the media access control (MAC) layer does not determine the 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).

[0108] In the second method, the media access control (MAC) layer does not determine the priority of the uplink grant corresponding to the second physical uplink shared channel (PUSCH), but directly determines: for the uplink grant of the second PUSCH, no second physical uplink shared channel (PUSCH) data will be generated.

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

[0110] Therefore, in the second method, since the first physical uplink shared channel (PUSCH) already exists and the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained the media access control protocol data unit (MAC PDU), the media access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH), thereby avoiding inconsistent operations between the MAC layer and the physical layer on whether to send the second PUSCH.

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

[0112] Figure 11 FIG. 1 is a schematic diagram of the MAC layer and physical layer operations in Example 2. Figure 11 As shown, the first PUSCH 1110 is a PUSCH scheduled by the first downlink control information (i.e., a dynamic scheduling grant DG), and the second PUSCH 1120 is a PUSCH with a configuration grant (CG). The MAC layer has already generated data for the first PUSCH 1110 and no longer generates data for the second PUSCH 1120 (indicated by the dotted line in the figure). Therefore, the MAC layer generates data for the first PUSCH 1110 and sends it to the physical layer, which then sends the data for the first PUSCH 1110. The MAC layer does not generate data for the second PUSCH 1120, and therefore the physical layer does not send data for the second PUSCH 1120.

[0113] Figure 12 FIG. 1 is a schematic diagram of the MAC layer and physical layer operations in Example 2. Figure 12As shown, the first PUSCH 1210 is configured with Grant (CG) 1, and the second PUSCH 1220 is configured with Grant (CG) 2. The MAC layer has already generated data for the first PUSCH 1210 and therefore no longer generates data for the second PUSCH 1220 (indicated by the dotted line in the figure). Therefore, the MAC layer generates data for the first PUSCH 1210 and sends it to the physical layer, which then transmits the data for the first PUSCH 1210. The MAC layer does not generate data for the second PUSCH 1220, and therefore the physical layer does not transmit the data for the second PUSCH 1220.

[0114] Example 3

[0115] Embodiment 3 differs from Embodiment 2 in that a specific manner of implementing operation 1001 is different. In Embodiment 3, 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) with a configuration grant (CG), and the second physical uplink shared channel (PUSCH) data is a physical uplink shared channel (PUSCH) with a configuration grant (CG).

[0116] In embodiment 3, operation 1001 may include: a 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 a high-priority uplink grant, and does not generate data for the second physical uplink shared channel (PUSCH). Because the MAC layer does not determine the uplink grant corresponding to the second PUSCH as a high-priority uplink grant and does not generate data for the second PUSCH, the terminal device 102 cannot send data for the second PUSCH, thereby avoiding inconsistency between the MAC layer and the physical layer regarding whether to send the second PUSCH.

[0117] Among them, if there is no first PUSCH of the physical uplink shared channel, the media access control (MAC) layer of the terminal device determines the uplink permission corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink permission, and generates data for the second physical uplink shared channel (PUSCH).

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

[0119] If there is no other physical uplink shared channel (PUSCH) with a 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) scheduled by downlink control information (DCI) with a higher priority or the same priority 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 with a higher priority scheduling request (SR) that overlaps with the second physical uplink shared channel (PUSCH), then the media access control (MAC) layer of the terminal device 102 determines the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink grant; otherwise, the media access control (MAC) layer does not determine the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink grant.

[0120] According to the above-mentioned method for determining the priority of the uplink grant corresponding to the second PUSCH, there is a first physical uplink shared channel (PUSCH) at the MAC layer, and the first physical uplink shared channel (PUSCH) has the same physical layer priority as the second PUSCH, and the first PUSCH and the second PUSCH at least partially overlap in the time domain. Therefore, the media access control (MAC) layer does not determine the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink grant.

[0121] In addition, in Example 3, the media access control (MAC) layer does not determine the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink grant. In this way, the MAC layer can actively initiate retransmission of the second PUSCH data to avoid data loss of the second PUSCH.

[0122] According to Example 3, when the physical layer priorities of the second PUSCH and 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 of the PUSCH. Thus, the MAC layer transmission priority can be consistent with the physical layer transmission priority, which can avoid the data of the second PUSCH, which is originally high-priority data, from being discarded by the physical layer.

[0123] Next, a method for MAC in Embodiment 3 to determine the priority of the uplink grant corresponding to the first PUSCH and the second PUSCH will be described.

[0124] 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) data is a physical uplink shared channel (PUSCH) configured with a grant (CG), the MAC layer may determine the priority of the uplink grants corresponding to the first PUSCH and the second PUSCH respectively according to the following method:

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

[0126] For the uplink permission corresponding to the first PUSCH, if there is no other PUSCH of a higher priority CG that at least partially overlaps with the first PUSCH in the time domain, where the physical layer priority of the PUSCH of the higher priority CG is higher than the physical layer priority of the first PUSCH; then the MAC layer can determine the uplink permission corresponding to the first PUSCH as a high priority, otherwise it is not determined to be a high priority.

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

[0128] For another example, for the uplink grant corresponding to the first PUSCH: if there is no other PUSCH of a higher priority CG that at least partially overlaps with the first PUSCH in the time domain, wherein 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; and there is no PUCCH resource of a higher priority SR transmission that at least partially overlaps with the first PUSCH in the time domain, then the MAC layer determines the uplink grant corresponding to the first PUSCH as a high-priority grant, and determines the uplink grants corresponding to other PUSCHs that at least partially overlap with the first PUSCH in the time domain as low-priority uplink grants.

[0129] When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the MAC layer may determine the priority of the uplink grants corresponding to the first PUSCH and the second PUSCH respectively according to the following method:

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

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

[0132] In embodiment 4, when the MAC layer determines the uplink grant corresponding to the first PUSCH as a high-priority uplink grant, the MAC layer may further generate first PUSCH data and send it to the physical layer, and the physical layer sends the first PUSCH data outward.

[0133] Above, Embodiment 1, Embodiment 2 and Embodiment 3 of the method for sending data according to the second aspect of the embodiments of the present application are described.

[0134] In the second aspect of the embodiments of the present application, the terminal device 102 can use the method described in any one of Embodiment 1, Embodiment 2 and Embodiment 3 to send data.

[0135] The third aspect of the embodiment

[0136] A third aspect of an embodiment of the present application relates to a method for sending data, which is applied to a terminal device, such as the terminal device 102.

[0137] In the third aspect of the embodiment of the present application, the terminal device 102 can make a choice to use the method for sending data described in the first aspect or the second aspect of the embodiment.

[0138] Figure 13 This is a schematic diagram of a method for sending data according to the third aspect of an embodiment of the present application. Figure 14 As shown, the method includes:

[0139] Operation 1301: 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) at least partially overlap in the time domain, the terminal device 102 determines whether to send or not to send the second physical uplink shared channel (PUSCH) according to the types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH).

[0140] In at least one embodiment: when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and when the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the terminal device 102 determines to send the second physical uplink shared channel (PUSCH), that is, the first aspect of the embodiment of the present application; in addition, when the first physical uplink shared channel (PUSCH) is physical uplink shared channel (PUSCH) data scheduled by downlink control information (DCI), and when the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the physical layer determines not to send the second physical uplink shared channel (PUSCH), that is, the second aspect of the embodiment of the present application.

[0141] In at least another embodiment: when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and when the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the terminal device 102 determines not to send the second physical uplink shared channel (PUSCH), that is, the second aspect of the embodiment of the present application; in addition, when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI), and when the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the physical layer determines to send the second physical uplink shared channel (PUSCH), that is, the first aspect of the embodiment of the present application.

[0142] In addition, in the third aspect of the embodiment of the present application, the terminal device 102 can also select from Example 1, Example 2 and Example 3 in the second aspect of the embodiment of the present application to send data.

[0143] For example, when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the terminal device 102 uses the method of Example 2 or Example 3; in addition, 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) configured with a grant (CG), the terminal device 102 uses the method of Example 1.

[0144] For another example, when the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the terminal device 102 uses the method of Example 2; in addition, 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) configured with a grant (CG), the terminal device 102 uses the method of Example 3.

[0145] Fourth aspect of the embodiment

[0146] A fourth aspect of an embodiment of the present application provides an apparatus for sending data, which is applied to a terminal device, for example, the terminal device 102 .

[0147] Figure 14 is a schematic diagram of a device for sending data according to the fourth aspect of an embodiment of the present application, such as Figure 15 As shown, the apparatus 1400 for sending data may include a first processing unit 1401 , a second processing unit 1402 , or a third processing unit 1403 .

[0148] The first processing unit 1401 can control the terminal device so that the terminal device executes the method for sending data described in the first aspect of the embodiment of the present application. For the description of the method for sending data implemented by the first processing unit 1401, reference can be made to the description of the method for sending data in the first aspect of the embodiment of the present application.

[0149] The second processing unit 1402 can control the terminal device so that the terminal device executes the method for sending data described in the second aspect of the embodiment of the present application. For an explanation of the method for sending data implemented by the second processing unit 1402, reference can be made to the explanation of the method for sending data in the second aspect of the embodiment of the present application.

[0150] The third processing unit 1403 can control the terminal device so that the terminal device executes the method for sending data described in the third aspect of the embodiment of the present application. For an explanation of the method for sending data implemented by the third processing unit 1403, reference can be made to the explanation of the method for sending data in the third aspect of the embodiment of the present application.

[0151] Fifth aspect of the embodiment

[0152] A fifth aspect of an embodiment of the present application provides a terminal device, which includes the device 1400 for sending data as described in the third aspect of the embodiment.

[0153] Figure 15 FIG. 1 is a schematic block diagram of the system structure of the terminal device 1500 according to the fifth aspect of the embodiment of the present application. Figure 15 As shown, the terminal device 1500 may include a processor 1510 and a memory 1520; the memory 1520 is coupled to the processor 1510. It should be noted that this figure is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0154] In one embodiment, the functionality of the apparatus 1400 for sending data may be integrated into the processor 1510. The processor 1510 may be configured to implement the method of the first, second, or third aspect of the embodiment.

[0155] In another embodiment, the device 1400 for sending data can be configured separately from the processor 1510. For example, the device 1400 for sending data can be configured as a chip connected to the processor 1510, and the function of the device 1400 for sending data is realized through the control of the processor 1510.

[0156] like Figure 15 As shown, the terminal device 1500 may further include: a communication module 1530, an input unit 1540, a display 1550, and a power supply 1560. It is worth noting that the terminal device 1500 does not necessarily have to include Figure 15 In addition, the terminal device 1500 may also include Figure 15 For components not shown, reference may be made to the prior art.

[0157] like Figure 15 As shown, the processor 1510 is sometimes also referred to as a controller or operation control, and may include a microprocessor or other processor device and / or logic device. The processor 1510 receives input and controls the operation of various components of the terminal device 1500.

[0158] Memory 1520 may be, for example, one or more of a cache, flash memory, a hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store various data and may also store programs for executing related information. Processor 1510 may execute the programs stored in memory 1520 to implement information storage or processing, etc. The functions of other components are similar to those of existing devices and are not further described here. Each component of terminal device 1500 may be implemented using dedicated hardware, firmware, software, or a combination thereof without departing from the scope of this application.

[0159] Sixth aspect of the embodiment

[0160] The sixth aspect of the embodiment of the present application also provides a communication system, including a network device and a terminal device as described in the fifth aspect of the embodiment.

[0161] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0162] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0163] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part 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 that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0164] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as 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 appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0165] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0166] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0167] 1. A method for sending data, applied to a terminal device, comprising:

[0168] 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) at least partially overlap in the time domain, the terminal device sends the second physical uplink shared channel (PUSCH).

[0169] 2. The method as described in Note 1, wherein:

[0170] The time when the physical layer of the terminal device receives the data of the second physical uplink shared channel (PUSCH) from the media access control (MAC) layer is later than the time when the physical layer of the terminal device receives the data of the first physical uplink shared channel (PUSCH).

[0171] 3. The method as described in Note 1 or 2, wherein:

[0172] The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by the first downlink control information (DCI),

[0173] The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0174] 4. The method as described in Note 1 or 2, wherein:

[0175] The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG),

[0176] The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0177] 5. A method for sending data, applied to a terminal device, comprising:

[0178] The first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority.

[0179] And when the transmission of the first physical uplink shared channel (PUSCH) and the transmission of the second physical uplink shared channel (PUSCH) at least partially overlap in the time domain, the terminal device does not transmit the second physical uplink shared channel (PUSCH).

[0180] 6. The method for transmitting data as described in Supplement 5, wherein:

[0181] The physical layer of the terminal device receives the data of the second physical uplink shared channel (PUSCH) from the media access control (MAC) layer later than the time when the physical layer receives the data of the first physical uplink shared channel (PUSCH).

[0182] The method further comprises:

[0183] The physical layer sends transmission indication information to the medium access control (MAC) layer, where the transmission indication information is used to notify the medium access control (MAC) layer that data of the second physical uplink shared channel (PUSCH) is not sent.

[0184] 7. The method for sending data according to Supplementary Note 6, wherein the method further comprises:

[0185] 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.

[0186] 8. The method for sending data according to Supplementary Note 6, wherein the method further comprises:

[0187] The medium access control (MAC) layer determines the uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high-priority uplink grant.

[0188] 9. The method for transmitting data according to any one of Supplementary Notes 6 to 8, wherein:

[0189] The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI),

[0190] The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0191] 10. The method for transmitting data according to any one of Supplementary Notes 6 to 8, wherein:

[0192] The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG),

[0193] The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0194] 11. The method for transmitting data according to Note 5, wherein the terminal device does not transmit the second physical uplink shared channel (PUSCH), comprising:

[0195] If the media access control (MAC) layer of the terminal device has generated data for the first physical uplink shared channel (PUSCH), the media access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH).

[0196] 12. The method according to Note 11, wherein the medium access control (MAC) layer does not generate data for the second physical uplink shared channel (PUSCH), comprising:

[0197] The medium access control (MAC) layer does not determine the 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).

[0198] 13. The method for transmitting data according to Supplement 12, wherein:

[0199] 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) configured with a grant (CG),

[0200] The second physical uplink shared channel (PUSCH) data is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0201] 14. The method for sending data according to Supplementary Note 13, wherein the method further comprises:

[0202] If there is no first physical uplink shared channel (PUSCH), wherein the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained a media access control protocol data unit (MAC PDU),

[0203] The media access control (MAC) layer determines that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a high-priority uplink grant, and generates data for the second physical uplink shared channel (PUSCH).

[0204] 15. The method for sending data according to Note 14, wherein the medium access control (MAC) layer determines that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a high-priority uplink grant, comprising:

[0205] If no other physical uplink shared channel (PUSCH) with a higher priority configuration grant (CG) overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, no physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) with a higher priority or the same priority overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, and no physical uplink control channel (PUCCH) transmitted with a higher priority scheduling request (SR) overlaps with the second physical uplink shared channel (PUSCH),

[0206] The media access control (MAC) layer determines that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a high-priority uplink grant, and generates data for the second physical uplink shared channel (PUSCH).

[0207] 16. The method for sending data according to Supplementary Note 12, wherein the method further comprises:

[0208] If there is no first physical uplink shared channel (PUSCH), and the uplink grant corresponding to the first physical uplink shared channel (PUSCH) has obtained a media access control protocol data unit (MAC PDU),

[0209] A media access control protocol data unit (MAC PDU) is generated for an uplink grant corresponding to the second physical uplink shared channel (PUSCH) data.

[0210] 17. The method for transmitting data according to Note 5, wherein the terminal device does not transmit the second physical uplink shared channel (PUSCH), comprising:

[0211] The media access control (MAC) layer of the terminal device does not determine the 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).

[0212] 18. The method according to Note 17, further comprising:

[0213] If there is no first physical uplink shared channel (PUSCH), the media access control (MAC) layer of the terminal device determines the uplink permission corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink permission and generates data for the second physical uplink shared channel (PUSCH).

[0214] 19. The method as described in Note 18, wherein:

[0215] 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) configured with a grant (CG);

[0216] The second physical uplink shared channel (PUSCH) data is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0217] 20. The method according to Supplementary Note 19, further comprising:

[0218] If no other physical uplink shared channel (PUSCH) with a higher priority configuration grant (CG) overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, no physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) with a higher priority or the same priority overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, and no physical uplink control channel (PUCCH) transmitted with a higher priority scheduling request (SR) overlaps with the second physical uplink shared channel (PUSCH),

[0219] The media access control (MAC) layer of the terminal device determines the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a high-priority uplink grant.

[0220] 21. The method according to Supplementary Note 5, further comprising:

[0221] The terminal device sends the first physical uplink shared channel (PUSCH).

[0222] 22. The method according to Note 21, wherein the terminal device sends the first physical uplink shared channel (PUSCH), comprising:

[0223] The medium access control (MAC) layer determines the uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high-priority uplink grant, and generates data for the first physical uplink shared channel (PUSCH).

[0224] 23. The method as described in Note 22, wherein:

[0225] The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI);

[0226] The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

[0227] 24. The method according to Note 23, wherein the media access control (MAC) layer determines the uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high-priority uplink grant, comprising:

[0228] If no other physical uplink shared channel (PUSCH) with a higher priority configuration grant (CG) at least partially overlaps with the first physical uplink shared channel (PUSCH) in the time domain, wherein the physical layer priority of the configuration grant (CG) is higher than the physical layer priority of the first physical uplink shared channel (PUSCH); and no physical uplink control channel (PUCCH) with a higher priority scheduling request (SR) transmission at least partially overlaps with the first physical uplink shared channel (PUSCH) in the time domain,

[0229] The medium access control (MAC) layer determines that the uplink grant corresponding to the first physical uplink shared channel (PUSCH) is a high-priority uplink grant.

[0230] 25. A method for sending data, applied to a terminal device, comprising:

[0231] In a case where 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,

[0232] The terminal device determines whether to send or not to send the second physical uplink shared channel (PUSCH) according to types of the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH).

[0233] 26. The method for transmitting data according to Note 25, wherein the terminal device determines 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), comprising:

[0234] When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the terminal device determines to send the second physical uplink shared channel (PUSCH);

[0235] The first physical uplink shared channel (PUSCH) is physical uplink shared channel (PUSCH) data scheduled by downlink control information (DCI), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the physical layer determines not to send the second physical uplink shared channel (PUSCH).

[0236] 27. The method according to Note 25, wherein the terminal device determines whether to send or not send the second physical uplink shared channel (PUSCH) based on the first physical uplink shared channel (PUSCH) data and the type of the second physical uplink shared channel (PUSCH), comprising:

[0237] When the first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), and the second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), the terminal device determines not to send the second physical uplink shared channel (PUSCH);

[0238] 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) configured with a grant (CG), the physical layer determines to send the second physical uplink shared channel (PUSCH).

Claims

1. A terminal device, comprising: a transmitter configured to transmit a first physical uplink shared channel (PUSCH) or a second physical uplink shared channel (PUSCH); and A processor configured to: In a case where the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority, and the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) partially or completely overlap in the time domain, cancelling the transmission of the second physical uplink shared channel (PUSCH), Wherein, when the transmission of the second physical uplink shared channel is canceled by the physical layer of the terminal device, the media access control (MAC) layer of the terminal device does not use the uplink grant associated with the second physical uplink shared channel (PUSCH) as a priority uplink grant of the media access control (MAC) layer, thereby not obtaining the protocol data unit (PDU) of the second physical uplink shared channel; and The media access control (MAC) layer of the terminal device determines the uplink grant associated with the first physical uplink shared channel (PUSCH) as a high-priority uplink grant, and obtains the protocol data unit (PDU) of the first physical uplink shared channel (PUSCH).

2. The terminal device according to claim 1, wherein: The time when the physical layer of the terminal device receives the data of the second physical uplink shared channel (PUSCH) from the media access control (MAC) layer is later than the time when the physical layer of the terminal device receives the data of the first physical uplink shared channel (PUSCH).

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

4. The terminal device according to claim 1, wherein: The first physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG), The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

5. The terminal device according to claim 1, wherein: The processor is further configured to: In a case where the first physical uplink shared channel and the second physical uplink shared channel have the same physical layer priority and the first physical uplink shared channel and the second physical uplink shared channel partially or completely overlap in the time domain, the transmission of the second physical uplink shared channel is canceled, The media access control (MAC) layer determines the uplink grant corresponding to the second physical uplink shared channel (PUSCH) as a non-high priority uplink grant, and does not generate the protocol data unit (PDU) of the second physical uplink shared channel (PUSCH).

6. The terminal device according to claim 5, wherein: 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) configured with a grant (CG), The second physical uplink shared channel (PUSCH) data is a physical uplink shared channel (PUSCH) configured with a grant (CG).

7. The terminal device according to claim 1, wherein: The processor is further configured to: 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, Control is performed so that the uplink grant associated with the second physical uplink shared channel (PUSCH) is not processed, and thus a protocol data unit (PDU) of the second physical uplink shared channel is not obtained.

8. The terminal device according to claim 1, wherein: The processor is further configured to: When the first physical uplink shared channel can be sent by the physical layer of the terminal device, it is determined whether the medium access control (MAC) layer obtains a protocol data unit (PDU) of the first physical uplink shared channel.

9. The terminal device according to claim 8, wherein: The processor is further configured to: When the uplink grant associated with the first physical uplink shared channel is considered to be a priority uplink grant, the media access control (MAC) layer of the terminal device obtains a protocol data unit (PDU) of the first physical uplink shared channel.

10. The terminal device according to claim 9, wherein: 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) configured with a grant (CG); The second physical uplink shared channel (PUSCH) is a physical uplink shared channel (PUSCH) configured with a grant (CG).

11. The terminal device according to claim 10, wherein: The processor is further configured to: When no other physical uplink shared channel (PUSCH) with a higher priority configuration grant (CG) overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, no physical uplink shared channel (PUSCH) scheduled by downlink control information (DCI) with a higher priority or the same priority overlaps at least partially with the second physical uplink shared channel (PUSCH) in the time domain, and no physical uplink control channel (PUCCH) transmitted with a higher priority scheduling request (SR) overlaps with the second physical uplink shared channel (PUSCH), It is determined that the uplink grant corresponding to the second physical uplink shared channel (PUSCH) is a high-priority uplink grant.

12. The terminal device according to claim 1, wherein: The processor is further configured to: The media access control (MAC) layer of the terminal device determines the uplink grant corresponding to the first physical uplink shared channel (PUSCH) as a high-priority uplink grant, and generates data for the first physical uplink shared channel (PUSCH).

13. A base station, comprising: processor; as well as a receiver coupled to the processor and configured to receive a first physical uplink shared channel (PUSCH) or a second physical uplink shared channel (PUSCH) from a terminal device, Wherein, when the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority, and the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) partially or completely overlap in the time domain, the transmission of the second physical uplink shared channel (PUSCH) is canceled by the terminal device, When transmission of the second physical uplink shared channel is canceled by the physical layer of the terminal device, the medium access control (MAC) layer of the terminal device does not use the uplink grant associated with the second physical uplink shared channel (PUSCH) as a priority uplink grant of the medium access control (MAC) layer, and thus does not obtain a protocol data unit (PDU) of the second physical uplink shared channel; as well as The media access control (MAC) layer of the terminal device determines the uplink grant associated with the first physical uplink shared channel (PUSCH) as a high-priority uplink grant, and obtains the protocol data unit (PDU) of the first physical uplink shared channel (PUSCH).

14. A communication system comprising: A terminal device configured to transmit a first physical uplink shared channel (PUSCH) or a second physical uplink shared channel (PUSCH); and a base station configured to receive the first physical uplink shared channel (PUSCH) or the second physical uplink shared channel (PUSCH) from the terminal device, Wherein, when the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) have the same physical layer priority, and the first physical uplink shared channel (PUSCH) and the second physical uplink shared channel (PUSCH) partially or completely overlap in the time domain, the terminal device cancels the transmission of the second physical uplink shared channel (PUSCH), When transmission of the second physical uplink shared channel is canceled by the physical layer of the terminal device, the medium access control (MAC) layer of the terminal device does not use the uplink grant associated with the second physical uplink shared channel (PUSCH) as a priority uplink grant of the medium access control (MAC) layer, and thus does not obtain a protocol data unit (PDU) of the second physical uplink shared channel; and The media access control (MAC) layer of the terminal device determines the uplink grant associated with the first physical uplink shared channel (PUSCH) as a high-priority uplink grant, and obtains the protocol data unit (PDU) of the first physical uplink shared channel (PUSCH).

Images