PROTOCOL DATA UNIT GENERATION METHOD, CONFIGURATION METHOD, APPARATUS, AND ELECTRONIC DEVICE

By generating MAC PDUs based on network and physical layer instructions, the method addresses the increased complexity of blind detection and multiplexing in UL skipping scenarios, enhancing communication efficiency.

JP7579359B2Active Publication Date: 2024-11-07VIVO MOBILE COMM CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2022568946
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-05-12
Filing Date
2021-05-11
Publication Date
2024-11-07
Estimated Expiration
2041-05-11

AI Technical Summary

Technical Problem

The complexity of blind detection and multiplexing of uplink control information (UCI) on uplink data channels is increased due to the UL skipping function in communication protocols, leading to increased processing complexity for both the network and terminal devices.

Method used

A method and apparatus for generating a MAC protocol data unit (PDU) in terminals, which includes receiving instruction information from the network and physical layer entities to multiplex UCI onto the uplink data channel, reducing blind detection complexity by generating MAC PDUs even in the absence of data transmission.

Benefits of technology

This approach reduces blind detection complexity on the network side and simplifies UCI multiplexing processing by ensuring MAC PDUs are generated based on clear instruction information, thereby optimizing communication efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007579359000003
    Figure 0007579359000003
  • Figure 0007579359000004
    Figure 0007579359000004
  • Figure 0007579359000005
    Figure 0007579359000005
Patent Text Reader

Abstract

This application discloses a protocol data unit generation method, a configuration method, an apparatus, and an electronic device. The protocol data unit generation method is used in a terminal, and includes: a medium access control (MAC) entity of the terminal generating a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity based on at least one of first indication information sent by a network side device, second indication information sent to the MAC entity by a physical layer entity, and the configuration of the terminal; and the MAC entity transmitting the generated MAC PDU to the physical layer entity.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to China Patent Application No. 202010399508.9, filed in China on May 12, 2020, the entire contents of which are incorporated herein by reference. The present application relates to the field of communication technology, and in particular to a protocol data unit generating method, a configuration method, an apparatus, and an electronic device. [Background technology]

[0002] When the uplink data channel (PUSCH) of the terminal enables the uplink transmission skip (UL skipping) function and there is no data transmission that needs to be transmitted in the terminal data memory, even if the base station schedules the terminal and performs data transmission, this UL skipping function allows the terminal to ignore the base station's scheduling and does not perform uplink transmission. However, in the above situation, when the uplink control channel (PUCCH) collides with the dynamically scheduled uplink data channel in resources, the terminal may select 1. not to generate a PUSCH and transmit uplink control information (UCI) on the PUCCH, or 2. to generate a PUSCH and transmit the uplink control information (UCI) multiplexed on the generated PUSCH. In this way, the blind detection complexity of the network side is increased, and the processing complexity of UCI multiplexing by the terminal is increased. Summary of the Invention [Problem to be solved by the invention]

[0003] The embodiments of the present application provide a protocol data unit generation method, configuration method, device and electronic device, which can reduce the blind detection complexity on the network side and reduce the processing complexity when the uplink control signaling of the terminal is multiplexed onto the uplink data channel. [Means for solving the problem]

[0004] According to a first aspect, an embodiment of the present application provides a protocol data unit generating method for use in a terminal, the method comprising: A medium access control (MAC) entity of the terminal generates a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity according to at least one of first indication information sent by a network side device, second indication information sent by a physical layer entity to the MAC entity, and a configuration of the terminal; The MAC entity transmits the generated MAC PDU to the physical layer entity.

[0005] According to a second aspect, an embodiment of the present application provides a configuration method for generating a protocol data unit, for use in a network side device, the method comprising: The method includes sending first instruction information to a terminal, instructing a medium access control (MAC) entity of the terminal to generate a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity.

[0006] According to a third aspect, an embodiment of the present application provides a protocol data unit generating device for use in a terminal, the device comprising: a generating module for generating a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity according to at least one of first indication information sent by a network side device, second indication information sent by a physical layer entity to the MAC entity, and a configuration of the terminal; and a transmitting module for transmitting the generated MAC PDU to the physical layer entity.

[0007] According to a fourth aspect, an embodiment of the present application provides a configuration device for generating a protocol data unit for use in a network side device, the device comprising: The terminal includes an instruction module for sending first instruction information to instruct a medium access control (MAC) entity of the terminal to generate a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity.

[0008] According to a fifth aspect, an embodiment of the present application further provides an electronic device, the electronic device including a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, realizing steps of the method described above.

[0009] According to a sixth aspect, an embodiment of the present application further provides a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implements the steps of the method described above.

[0010] According to a seventh aspect, an embodiment of the present application provides a chip, the chip comprising a processor and a communication interface, the communication interface being coupled to the processor, the processor running a program or instructions and adapted to implement the methods according to the first and second aspects.

[0011] In an embodiment of the present application, the MAC entity of the terminal can generate a MAC PDU for a currently scheduled HARQ entity based on at least one of the first indication information sent by a network side device, the second indication information sent by a physical layer entity to the MAC entity, and the configuration of the terminal, so that when the terminal has no uplink data transmission, the MAC layer can continue to generate a data PDU and pass it to the physical layer, and support that uplink control information can be multiplexed into the MAC PDU, thereby reducing the blind detection complexity on the network side and reducing the processing complexity of the terminal's uplink control signaling being multiplexed into an uplink data channel. Effect of the Invention

[0012] In order to more clearly explain the technical solutions of the embodiments of the present application, the following briefly introduces drawings that need to be used in the description of the embodiments of the present application. It is obvious that the drawings in the following description are only some embodiments of the present application, and those skilled in the art can also obtain other drawings based on these drawings without exerting creative efforts. [Brief description of the drawings]

[0013] [Figure 1] 1 illustrates a schematic diagram of a wireless communication system; [Diagram 2] 1 illustrates a schematic diagram of UCI being multiplexed onto a PUCCH. [Diagram 3] 1 shows a schematic diagram of PUSCH repetition Type A. [Figure 4] 1 shows a schematic diagram of PUSCH repetition Type B. [Diagram 5] 1 shows a schematic diagram of a UL skipping condition. [Figure 6] 1 illustrates a flow diagram of a protocol data unit generating method according to an embodiment of the present application; [Figure 7]2 illustrates a flow diagram of a configuration method for generating a protocol data unit according to an embodiment of the present application; [Figure 8] 1 illustrates a schematic diagram of a MAC entity of an embodiment of the present application generating a MAC PDU to support UCI being multiplexed into a PUSCH. [Figure 9] 1 illustrates a schematic diagram of internal signaling occurring in the physical layer of an embodiment of the present application to instruct a MAC entity to generate MAC PDUs unconditionally. [Figure 10] 1 illustrates a structural block diagram of a protocol data unit generating device according to an embodiment of the present application; [Figure 11] FIG. 2 illustrates a structural block diagram of a configuration device for generating a protocol data unit in an embodiment of the present application; [Figure 12] 1 illustrates a block diagram of a terminal according to an embodiment of the present application; [Figure 13] 1 illustrates a block diagram of a network side device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0015] The terms "first," "second," etc. in the specification and claims of this application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that the data so used may be interchanged where appropriate, such that the embodiments of this application may be performed in an order other than that shown or described herein. Note that "and / or" in the specification and claims indicates at least one of the objects connected, and the character " / " generally indicates that the related objects are in an "or" relationship.

[0016] The techniques described herein are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems and may be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are always used interchangeably. A CDMA system may implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and the like. UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. A TDMA system may implement radio technologies such as Global System for Mobile Communication (GSM). An OFDMA system may implement radio technologies such as UltraMobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and higher LTE (e.g. LTE-A) are newer versions of UMTS that use E-UTRA.UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned above or other systems and radio technologies. However, although these techniques may be used for applications other than NR system applications, the following description describes an NR system for illustration purposes, and NR terminology is used in most of the description below.

[0017] The following description provides examples, but is not intended to limit the scope, applicability, or configuration described in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the spirit and scope of the present disclosure. Various examples may omit, substitute, or add various provisions or components as appropriate. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Also, features described with reference to some examples may be combined in other examples.

[0018] Referring to Fig. 1, Fig. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a mobile internet device (Mobile Internet Device, MID), a wearable device, or an in-vehicle device, and it should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side equipment 12 may be a base station or a core network, where the base station may be a 5G or later version base station (e.g., gNB, 5G NR NB, etc.), or a base station in other communication systems (e.g., eNB, WLAN access point, or other access point), or a location server (e.g., E-SMLC or LMF (Location Manager Function)), where the base station may be called a Node B, an evolved Node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, or any other suitable term in the art, and as long as the same technical effect is achieved, the base station is not limited to a specific technical term, and it should be explained that in the embodiments of this application, only a base station in an NR system is taken as an example, but the embodiments of this application are not limited to a specific type of base station and a specific communication system.

[0019] Uplink control information (UCI) is transmitted on the uplink control channel (Physical Uplink Control Channel (PUCCH)). When a terminal transmits data on the uplink data channel (Physical Uplink Shared Channel (PUSCH), in principle, PUCCH and PUSCH can be transmitted simultaneously, i.e., UCI is reserved for PUCCH. However, this increases the cubic metric. Furthermore, if the requirement for out-of-band emission is met with higher emission power, and the spacing in the frequency domain is relatively large when PUSCH and PUCCH are transmitted simultaneously (PUCCH is generally transmitted at both ends of the frequency band), this poses a challenge for radio frequency (RF) implementation. Therefore, in general, as long as the PUCCH resource required to transmit UCI overlaps with the PUSCH resource in time and the base station ensures that the UCI multiplexing processing time condition is met when scheduling the PUSCH, the UCI is multiplexed into the data and the PUSCH as shown in FIG. 2 to avoid simultaneous transmission of the PUCCH, where DL DCI is downlink control information, PDSCH is a physical downlink shared channel, one slot is one slot, UL grant is uplink grant, Multiplex is multiplexing, UL-SCH is an uplink shared channel, DMRS is a demodulation reference signal, HARQ-ACK is hybrid automatic repeat request-acknowledgement, CSI part 1 is a first part of channel state information, and CSI part 2 is a second part of channel state information.

[0020] In related communication protocols, repetitive transmission is based on slots, K repetitive transmissions need to occupy K slots, and the time resources (transmission start positions) occupied by data transmissions in each slot are the same. This mechanism of repetitive transmission is called PUSCH repetition Type A, as shown in Figure 3, where slot boundary is a slot boundary.

[0021] In some communication protocols, sub-slot-based repetition transmission is introduced, and K nominal repetition transmissions can be "back-to-back" continuous transmissions in one slot. If the time domain resource of one nominal transmission straddles the slot boundary or there are invalid or unavailable resources or symbols, e.g., downlink symbols, in this time domain resource, the nominal transmission is symbol-split into multiple actual repetition transmissions by slot or invalid resources. This repetition transmission mechanism is called PUSCH repetition Type B, as shown in Figure 4.

[0022] The Media Access Control (MAC) layer defines a process in which a terminal performs uplink transmission skipping (UL skipping) in some communication protocols, and FIG. 5 shows a schematic diagram of a UL skipping condition.

[0023] (1) the MAC entity is configured with a parameter skipUplinkTxDynamic, and the value of this parameter is set to true, and the MAC is positioned at the HARQ entity indicated in the uplink grant; (2) This UL grant does not require aperiodic CSI for this PUSCH transmission as specified in the relevant communication protocol; and (3) the MAC PDU contains zero MAC Service Data Units (SDUs); and (4) If the MAC PDU contains only a periodic Buffer Status Report (BSR) and there is no data applicable to any Logical Channel Group (LCG) or the MAC PDU contains only a filling BSR, the MAC entity does not generate a MAC Protocol Data Unit (PDU) for the HARQ entity.

[0024] When the uplink data channel (PUSCH) of the terminal enables the uplink transmission skip (UL skipping) function and there is no data transmission that needs to be transmitted in the terminal data memory, even if the base station schedules the user and performs data transmission, the UL skipping function allows the user to ignore the base station's scheduling and does not perform uplink transmission. However, in the above situation, when the uplink control channel (PUCCH) conflicts with the dynamically scheduled uplink data channel in resources, the terminal: 1. No PUSCH is generated, and uplink control information (UCI) is transmitted on PUCCH; 2. There is a possibility of selecting to generate a PUSCH and multiplex uplink control information (UCI) into the generated PUSCH for transmission.

[0025] Supporting UCI multiplexing on PUSCH without generating MAC PDUs will bring the following problems: (1) increasing the blind detection complexity on the network side, because the network side needs to blindly detect whether UCI is transmitted on PUCCH or PUSCH, and the probability of transmitting UCI on PUCCH due to UL skipping is much higher than the situation when UL grant is missed; (2) increasing the complexity of the terminal processing UCI multiplexing, because according to the conventional communication protocol, the condition for the terminal multiplexing UCI on PUSCH is that the resources between PUCCH and PUSCH overlap, and does not consider the situation when UL skipping is enabled, and adding a judgment of whether the terminal generates a MAC PDU means that the terminal needs to check another condition in addition to the resource overlap, which introduces a new behavior and increases the complexity of the user processing UCI multiplexing.

[0026] In addition, in the conventional MAC layer protocol, the resource overlap between the physical layer PUCCH and PUSCH is not visible to the MAC layer, so the MAC layer cannot determine whether a MAC PDU needs to be generated when there is no data in the data memory of the terminal and UL skipping is enabled.

[0027] The embodiments of the present application provide a protocol data unit generating method, a configuration method, an apparatus, and an electronic device, which support a MAC entity generating a MAC PDU and passing the generated MAC PDU to a physical layer entity (wherein the MAC PDU becomes a PUSCH) to multiplex UCI onto the PUSCH.

[0028] The embodiment of the present application provides a method for generating a protocol data unit for use in a terminal. As shown in FIG. 6, the method includes the following steps:

[0029] In step 101, the medium access control (MAC) entity of the terminal generates a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity based on at least one of first indication information sent by a network side device, second indication information sent by a physical layer entity to the MAC entity, and a configuration of the terminal.

[0030] In step 102, the MAC entity transmits the generated MAC PDU to the physical layer entity.

[0031] In an embodiment of the present application, the MAC entity of the terminal can generate a MAC PDU for a currently scheduled HARQ entity based on at least one of the first indication information sent by a network side device, the second indication information sent by a physical layer entity to the MAC entity, and the configuration of the terminal; in this way, the terminal can support that when there is no uplink data transmission, the MAC layer continues to generate a data PDU and passes it to the physical layer, and uplink control information can be multiplexed into this MAC PDU, thereby reducing the blind detection complexity of the network side and reducing the processing complexity of the uplink control signaling of the terminal being multiplexed into the uplink data channel.

[0032] Here, the first instruction information sent by the network side device is dynamic scheduling information, which can clearly indicate under what conditions the UL-SCH is to be generated, or indicate whether the UL-SCH is to be generated, or can indicate to generate uplink data regardless of whether the terminal has data or not, where the generation of the UL-SCH means that the MAC entity generates a MAC PDU.

[0033] In some embodiments, the first indication information may be carried in an uplink grant message transmitted by the network side device. For example, DCI format(s), i.e., UL grant, includes x bit(s) (x is a natural number and may be equal to 1) for indicating whether or not a UL-SCH (data) is generated for this PUSCH transmission.

[0034] In some embodiments, the first indication information occupies a separate first indication field in the uplink grant message; or The first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; or The first indication information multiplexes a third indication field for indicating other information in the uplink grant message.

[0035] That is, the x bit(s) may occupy an independent field in the UL grant, or may be jointly coded with or multiplexed with a conventional field.

[0036] In one specific embodiment, the first indication information occupies a separate first indication field in the uplink grant message; Instructing the MAC entity to always generate MAC PDUs if the value of the first indication field is a first value; and / or When the value of the first indication field is a second value, the MAC entity is instructed not to generate a MAC PDU when the value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true and the terminal meets the condition of skipping uplink transmission.

[0037] This separate first indication field may be a UCI Multiplexing field, the size of which is 1 bit.

[0038] In one specific example, when the value of the UCI Multiplexing field is 1, it indicates that the terminal always transmits the UL-SCH on the PUSCH regardless of the conditions and circumstances, and when the value of the UCI Multiplexing field is 0, it is a reserved value.

[0039] In another specific example, when the value of the UCI Multiplexing field is 1, the UE is instructed to always transmit the UL-SCH on the PUSCH regardless of the conditions and circumstances, but when the value of the UCI Multiplexing field is 0, the UE is instructed not to generate the UL-SCH when the skipUplinkTxDynamic is set to true and the UE meets the conditions to perform uplink transmission skip (UL skipping).

[0040] Here, the condition for the terminal to execute uplink transmission skip is as follows: a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); The MAC PDU includes only a periodic buffer status report BSR and no data for a logical channel group, or the MAC PDU includes only a fill BSR.

[0041] In another specific embodiment, the first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; if the value of the second indication field is a third value, instructing the MAC entity to generate a MAC PDU when the channel state information (CSI request) is not set to all zeros; If the value of the second indication field is a fourth value, instruct the MAC entity to always generate a MAC PDU; When the value of the second indication field is a fifth value, the value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and when the terminal meets a condition for skipping uplink transmission, the MAC entity is instructed not to generate a MAC PDU.

[0042] For example, this x bit (where x is a natural number and may be equal to 1) is jointly coded with a conventional 1-bit UL-SCH indicator field to become an (x+1)-bit UCI Multiplexing field, and the code-point and meaning of this jointly coded field are defined in the table below.

[0043] [Table 1]

[0044] In another specific embodiment, when the first indication information multiplexes a third indication field in the uplink grant message, If the value of the third indication field is a sixth value, instructing the MAC entity to always generate MAC PDUs; and / or When the value of the third indication field is a seventh value, the MAC entity is instructed not to generate a MAC PDU when skipUplinkTxDynamic is set to true and the terminal meets the condition to perform an uplink transmission skip.

[0045] For example, a new meaning is given to the conventional UL-SCH indicator field, so that when the value of the UL-SCH indicator field is 0, the UL-SCH should always be transmitted on the PUSCH unconditionally (UL-SCH shall always be transmitted on the PUSCH without conditions), and when the value of the UL-SCH indicator field is 1, when skipUplinkTxDynamic is set to true and the terminal satisfies the conditions for skipping uplink transmission, the UL-SCH should not be transmitted on the PUSCH (UL-SCH shall not be transmitted on the PUSCH when skipUplinkTxDynamic is set to true).

[0046] Here, the condition for skipping uplink transmission is: a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); The MAC PDU includes only a periodic buffer status report BSR and no data for a logical channel group, or the MAC PDU includes only a fill BSR.

[0047] It should be noted that the uplink grant message is demodulated by the physical layer entity before being sent to the MAC entity.

[0048] Furthermore, when the MAC entity generates a MAC PDU, if the scheduled PUSCH is configured to repeat transmission K times or is instructed by the uplink grant message to repeat transmission K times, the MAC entity generates a number of repeated MAC PDUs accordingly, where K is an integer greater than or equal to 1.

[0049] In some embodiments, inter-layer signaling from a physical layer to a MAC layer within the terminal, i.e., the second indication information, is defined, and when the physical layer entity determines that resources of the scheduled physical uplink shared channel PUSCH and the physical uplink control channel PUCCH overlap in the time domain, the physical layer entity transmits the second indication information to a MAC entity.

[0050] In one specific embodiment, the second indication information may instruct the MAC entity to always generate a MAC PDU when a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true.

[0051] In another specific embodiment, the second instruction information further comprises: the MAC entity is configured with skipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and There is no aperiodic CSI requested for this PUSCH transmission; and if the notification of 'UCI multiplexing' (or 'UL-SCH generation') 'UCI multiplexing' (or 'UL-SCH') has not been received from lower layers, the MAC PDU includes zero MAC SDUs; If all of the following conditions are met: the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR, the MAC entity can be instructed not to generate a MAC PDU for the HARQ entity.

[0052] When the MAC entity generates the MAC PDU, if the scheduled PUSCH is configured to repeat transmission K times or is instructed by the uplink grant message to repeat transmission K times, the internal signaling passed by the physical layer entity to the MAC entity is: unconditionally generating K identical MAC PDUs, or Generate M out of K MAC PDUs unconditionally, where 1≦M≦K, M is the number of overlapping PUCCH resources with PUSCH resources, K is an integer greater than or equal to 1, and M may be an integer greater than or equal to 1 and less than or equal to K.

[0053] The MAC entity may generate K or M repeated MAC PDUs based on the second indication.

[0054] Also, if the repeated transmission type is B, the repeated MAC PDU is a nominal repeated transmission or the first or last actual repeated transmission that overlaps with a PUCCH resource.

[0055] In some embodiments, the overlap of PUCCH and PUSCH transmission resources of the physical layer is seen in the MAC layer by directly defining the relevant MAC PDU generation conditions in the MAC layer without the need to define any air interface or terminal internal signaling, for example, the terminal is configured such that the MAC entity generates a MAC PDU if any one of the uplink transmission skip conditions is not met.

[0056] In one specific embodiment, the condition for skipping uplink transmission is: a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); The MAC PDU includes only a periodic buffer status report BSR and no data for a logical channel group, or the MAC PDU includes only a filling BSR.

[0057] If all of the above conditions are met, the MAC entity does not generate a MAC PDU for the HARQ entity. If any one of the above conditions is not met, the MAC entity generates a MAC PDU.

[0058] Furthermore, when the MAC entity generates a MAC PDU, if the scheduled PUSCH is configured to repeat transmission K times or is instructed by the uplink grant message to repeat transmission K times, the MAC entity generates multiple repeated MAC PDUs, where K is an integer greater than or equal to 1.

[0059] An embodiment of the present application provides a configuration method for generating a protocol data unit, used in a network side device, and as shown in FIG. 7, the method includes the following steps:

[0060] In step 201, send first instruction information to a terminal, instructing a media access control (MAC) entity of the terminal to generate a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity.

[0061] Here, the first instruction information sent by the network side device is dynamic scheduling information, which can clearly indicate based on what conditions whether a UL-SCH is generated, or indicate whether a UL-SCH is generated, or can instruct the terminal to generate uplink data regardless of whether the terminal has data or not, where the generation of a UL-SCH means that the MAC entity generates a MAC PDU.

[0062] In some embodiments, the first indication information may be carried in an uplink grant message transmitted by the network side device. For example, DCI format(s), i.e., UL grant, includes x bit(s) (x is a natural number and may be equal to 1) for indicating whether or not a UL-SCH (data) is generated for this PUSCH transmission.

[0063] In some embodiments, the first indication information occupies a separate first indication field in the uplink grant message; or The first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; or The first indication information multiplexes a third indication field for indicating other information in the uplink grant message.

[0064] That is, the x bit(s) may occupy an independent field in the UL grant, or may be jointly coded with or multiplexed with a conventional field.

[0065] In one specific embodiment, the first indication information occupies a separate first indication field in the uplink grant message; Instructing the MAC entity to always generate MAC PDUs if the value of the first indication field is a first value; and / or When the value of the first indication field is a second value, the MAC entity is instructed not to generate a MAC PDU when the value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true and the terminal satisfies the condition for skipping uplink transmission.

[0066] This separate first indication field may be a UCI Multiplexing field, the size of which is 1 bit.

[0067] In one specific example, when the value of the UCI Multiplexing field is 1, it indicates that the terminal always transmits the UL-SCH on the PUSCH regardless of the conditions and circumstances, and when the value of the UCI Multiplexing field is 0, it is a reserved value.

[0068] In another specific example, when the value of the UCI Multiplexing field is 1, the UE is instructed to always transmit the UL-SCH on the PUSCH regardless of the conditions and circumstances, but when the value of the UCI Multiplexing field is 0, the UE is instructed not to generate the UL-SCH when the skipUplinkTxDynamic is set to true and the UE meets the conditions to perform uplink transmission skip (UL skipping).

[0069] Here, the condition for the terminal to execute uplink transmission skip is as follows: a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); The MAC PDU includes only a periodic buffer status report BSR and no data for a logical channel group, or the MAC PDU includes only a fill BSR.

[0070] In another specific embodiment, the first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; if the value of the second indication field is a third value, instructing the MAC entity to generate a MAC PDU when the channel state information (CSI request) is not set to all zeros; If the value of the second indication field is a fourth value, instruct the MAC entity to always generate a MAC PDU; When the value of the second indication field is a fifth value, the value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and when the terminal meets a condition for skipping uplink transmission, the MAC entity is instructed not to generate a MAC PDU.

[0071] For example, this x bit (where x is a natural number and may be equal to 1) is jointly coded with a conventional 1-bit UL-SCH indicator field to become an (x+1)-bit UCI Multiplexing field, and the code-point and meaning of this jointly coded field are defined in the table below.

[0072] [Table 2]

[0073] In another specific embodiment, when the first indication information multiplexes a third indication field in the uplink grant message, If the value of the third indication field is a sixth value, instructing the MAC entity to always generate MAC PDUs; and / or When the value of the third indication field is a seventh value, the MAC entity is instructed not to generate a MAC PDU when the condition that skipUplinkTxDynamic is set to true and the terminal meets the condition to perform an uplink transmission skip is met.

[0074] For example, a new meaning is given to the conventional UL-SCH indicator field, so that when the value of the UL-SCH indicator field is 0, the UL-SCH should always be transmitted on the PUSCH unconditionally (UL-SCH shall always be transmitted on the PUSCH without conditions), and when the value of the UL-SCH indicator field is 1, when skipUplinkTxDynamic is set to true and the terminal satisfies the conditions for skipping uplink transmission, the UL-SCH should not be transmitted on the PUSCH (UL-SCH shall not be transmitted on the PUSCH when skipUplinkTxDynamic is set to true).

[0075] Here, the condition for skipping uplink transmission is: a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); The MAC PDU includes only a periodic buffer status report BSR and no data for a logical channel group, or the MAC PDU includes only a fill BSR.

[0076] It should be noted that the uplink grant message is demodulated by the physical layer entity before being sent to the MAC entity.

[0077] Furthermore, when the MAC entity generates a MAC PDU, if the scheduled PUSCH is configured to repeat transmission K times or is instructed by the uplink grant message to repeat transmission K times, the MAC entity generates a number of repeated MAC PDUs accordingly, where K is an integer greater than or equal to 1.

[0078] The following further introduces the technical solution of this application in conjunction with drawings and specific embodiments.

[0079] Example 1 In this embodiment, as shown in FIG. 8, in the base station and / or network side, when the skipUplinkTxDynamic with a value of true is configured and the scheduled PUSCH resource overlaps with the PUCCH resource in time, in order to reduce the blind detection complexity (i.e., when determining whether UCI is transmitted on the PUCCH or on the PUSCH), the network side instructs in the UL grant in the relevant fields defined as above that the UL-SCH is always transmitted on the PUSCH regardless of the conditions or circumstances.

[0080] At the terminal and / or user side, the physical layer entity of the terminal demodulates the UL grant and passes the information received in the UL grant to the MAC entity, which determines whether to generate a MAC PDU based on the above-defined fields in the UL grant, i.e. the MAC entity is configured with skipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and There is no aperiodic CSI requested for this PUSCH transmission; and There is no 'UCI multiplexing' (or 'UL-SCH') requested for this PUSCH transmission; and the MAC PDU includes zero MAC SDUs; If all of the following conditions are met: the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR, then the MAC entity does not generate a MAC PDU for the HARQ entity.

[0081] Example 2 In this embodiment, as shown in FIG. 9, inter-layer signaling from the physical layer to the MAC layer inside the terminal is defined. When the physical layer of the terminal recognizes that the resources of the scheduled PUSCH and PUCCH overlap in the time domain, optionally, the terminal is configured with skipUplinkTxDynamic with a value of true, and the physical layer of the terminal notifies the MAC layer to unconditionally generate a MAC PDU for the currently scheduled HARQ entity.

[0082] It should be noted that in the protocol data unit generating method according to the embodiment of the present application, the execution body may be a protocol data unit generating device or a module for executing the loading of the protocol data unit generating method in the protocol data unit generating device. In the embodiment of the present application, the protocol data unit generating method according to the embodiment of the present application is described by taking the loading and execution of the protocol data unit generating method by the protocol data unit generating device as an example.

[0083] The protocol data unit generating device of the embodiment of the present application is used in a terminal 300, as shown in FIG. 10, the device comprises: a generating module 310 for generating a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity according to at least one of: first indication information sent by a network side device, second indication information sent by a physical layer entity to the MAC entity, and a configuration of the terminal; and a transmitting module 320 for transmitting the generated MAC PDU to the physical layer entity.

[0084] In some embodiments, the first indication information occupies a separate first indication field in the uplink grant message; or The first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; or The first indication information multiplexes a third indication field for indicating other information in the uplink grant message.

[0085] In some embodiments, the terminal is configured such that the MAC entity generates a MAC PDU if any one of the conditions for skipping uplink transmission is not met.

[0086] In some embodiments, the second indication is transmitted when the physical layer entity determines that scheduled resources of a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH) overlap in the time domain.

[0087] The protocol data unit generating device in the embodiment of the present application may be a device, or may be a component, integrated circuit, or chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), and the non-mobile electronic device may be a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit machine, or a self-service machine, and the embodiment of the present application is not specifically limited thereto.

[0088] The protocol data unit generating device in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited thereto.

[0089] The protocol data unit generating apparatus according to the embodiment of the present application can realize each process realized by the protocol data unit generating method in the method embodiment of FIG. 6, and will not be described further here to avoid repetition of description.

[0090] It should be noted that in the configuration method for generating a protocol data unit according to the embodiment of the present application, the execution body may be a configuration device for generating a protocol data unit, or a module for executing the loading of the configuration method for generating a protocol data unit in the configuration device for generating a protocol data unit. In the embodiment of the present application, the configuration method for generating a protocol data unit according to the embodiment of the present application is described by taking the loading and execution of the configuration method for generating a protocol data unit by the configuration device for generating a protocol data unit as an example.

[0091] The configuration device for generating a protocol data unit in the embodiment of the present application is used in a network side device 400, as shown in FIG. 11, the device includes: The method includes an instruction module 410 for sending first instruction information to a terminal, instructing a media access control (MAC) entity of the terminal to generate a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity.

[0092] In some embodiments, the first indication information occupies a separate first indication field in the uplink grant message; or The first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; or The first indication information multiplexes a third indication field for indicating other information in the uplink grant message.

[0093] The component device for generating the protocol data unit in the embodiment of the present application may be a device, a component in a terminal, an integrated circuit, or a chip. The device may be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), and the non-mobile electronic device may be a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit machine, or a self-service machine, and the embodiment of the present application is not specifically limited thereto.

[0094] The component device generating the protocol data unit in the embodiment of the present application may be a device having an operating system, which may be an Android operating system, an ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited thereto.

[0095] The configuration device for generating a protocol data unit according to an embodiment of the present application can realize each process realized by the configuration method for generating a protocol data unit in the method embodiment of FIG. 7, and will not be described further here to avoid repetition of description.

[0096] Optionally, the embodiments of the present application further provide an electronic device, which includes a processor, a memory, and a program or instruction stored on the memory and operable on the processor, and when the program or instruction is executed by the processor, each process of the embodiments of the configuration method for generating a protocol data unit and the protocol data unit generating method can be realized and the same technical effect can be achieved. In order to avoid repetition of the description, no further description will be given here.

[0097] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices described above.

[0098] The electronic device of this embodiment may be a terminal. FIG. 12 is a hardware structure schematic diagram of a terminal for implementing each embodiment of the present application, and the terminal 50 includes, but is not limited to, components such as a radio frequency unit 51, a network module 52, an audio output unit 53, an input unit 54, a sensor 55, a display unit 56, a user input unit 57, an interface unit 58, a memory 59, a processor 510, and a power supply 511. As can be understood by those skilled in the art, the terminal structure shown in FIG. 12 does not constitute a limitation on the terminal, and the terminal may include more or less components than the number of components shown, or a combination of some components, or a configuration of different components. In the embodiments of the present application, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, and a pedometer.

[0099] It should be understood that in the embodiment of the present application, the radio frequency unit 51 may be used to transmit and receive information or transmit and receive signals during a call. Specifically, it receives downlink data from a base station, and then processes the data through the processor 510, and transmits uplink data to the base station. In general, the radio frequency unit 51 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. It should be noted that the radio frequency unit 51 can also communicate with other devices through a wireless communication system or network.

[0100] The memory 59 may be used to store software programs and various data. The memory 59 may mainly include a program storage area and a data storage area. Here, the program storage area can store an operating system, an application program required for at least one function (e.g., a voice playback function, an image playback function, etc.), and the data storage area can store data generated by using the mobile phone (e.g., audio data, a phone book, etc.). The memory 59 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk memory device, a flash memory device, or other volatile solid-state memory device.

[0101] The processor 510 is the control center of the terminal, and is connected to various parts of the entire terminal by various interfaces and lines, and monitors the entire terminal by executing or running software programs and / or modules stored in the memory 59, and by accessing data stored in the memory 59, performing various functions of the terminal, and processing data. The processor 510 may include one or more processing units. Preferably, the processor 510 may integrate an application processor and a modem processor. Here, the application processor is mainly for processing the operating system, user interface, and application programs, and the like, and the modem processor is mainly for processing wireless communication. As can be understood, the modem processor may not be integrated into the processor 510.

[0102] The terminal 50 may further include a power source 511 (e.g., a battery) for powering each component, and preferably, the power source 511 may be logically connected to the processor 510 by a power management system, so that the power management system can realize functions such as charge / discharge management and power consumption management.

[0103] The terminal 50 also includes several functional modules not shown, which will not be further described here.

[0104] The electronic device of this embodiment may be a network side device. As shown in Fig. 13, this network side device 600 includes an antenna 61, a radio frequency device 62, and a baseband device 63. The antenna 61 is connected to the radio frequency device 62. In the uplink direction, the radio frequency device 62 receives information through the antenna 61, and transmits the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be transmitted and transmits it to the radio frequency device 62, and the radio frequency device 62 transmits the received information through the antenna 61 after processing it.

[0105] The above frequency band processing device may be located in a baseband device 63, and the method performed by the network side equipment in the above embodiments may be realized in the baseband device 63, which includes a processor 64 and a memory 65.

[0106] The baseband device 63 may include, for example, at least one baseband board, on which multiple chips are configured, as shown in FIG. 13, where one chip is, for example, a processor 64, connected to a memory 65, and calls the program in the memory 65 to perform the network side equipment operations shown in the above method embodiments.

[0107] The baseband unit 63 may further include a network interface 66 for interacting with the radio frequency unit 62, the interface being, for example, a common public radio interface (CPRI).

[0108] The processor here may be one processor or a collective term for multiple processing elements, for example, the processor may be a CPU, an ASIC, or one or more integrated circuits configured to implement the method performed by the network side device, such as one or more microprocessors DSP, or one or more field programmable gate arrays FPGA, etc. The storage element may be one memory or a collective term for multiple storage elements.

[0109] Memory 65 may be volatile or nonvolatile memory, or may include both volatile and nonvolatile memory. Here, the nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be random access memory (RAM), which is used as an external cache. By way of example and not of limitation, many types of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (DRAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM), and direct Rambus random access memory (Direct Rambus RAM, DRRAM). Memory 65 as described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0110] The embodiments of the present application further provide a readable storage medium, in which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the configuration method for generating a protocol data unit or the protocol data unit generating method can be realized and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0111] Here, the processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0112] The embodiments of the present application further provide a chip, the chip including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction, so as to realize each process of the embodiments of the configuration method for generating a protocol data unit or the protocol data unit generating method, and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

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

[0114] It should be explained that in this specification, the terms "comprise", "include", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also includes other elements not specifically listed or inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element. It should be pointed out that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions essentially simultaneously or in the reverse order based on such functions, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

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

[0116] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take the suggestions of this application and make many forms without departing from the spirit and scope of protection of the claims, all of which belong to the protection scope of this application.

Claims

1. A method for generating a protocol data unit for use in a terminal, comprising: A medium access control (MAC) entity of the terminal generates a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity according to first indication information sent by a network side device; the MAC entity transmitting the generated MAC PDU to a physical layer entity; The first indication information is carried in an uplink grant message transmitted by the network side device, the first indication information occupies a separate first indication field in the uplink grant message; or The first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; or the first indication information is multiplexed with a third indication field for indicating other information in the uplink grant message; the first indication information occupies a separate first indication field in the uplink grant message; Instructing the MAC entity to always generate a MAC PDU if the value of the first indication field is a first value; and / or When the value of the first indication field is a second value, instruct the MAC entity not to generate a MAC PDU when a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true and the terminal satisfies a condition of skipping uplink transmission; Or, the first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; If the value of the second indication field is a third value, when the channel state information (CSI) request is not set to all zeros, instruct the MAC entity to generate a MAC PDU; If the value of the second indication field is a fourth value, instruct the MAC entity to always generate a MAC PDU; If the value of the second indication field is a fifth value, when a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true and the terminal satisfies a condition for skipping uplink transmission, instruct the MAC entity not to generate a MAC PDU; Or, The first indication information is obtained by multiplexing a third indication field in the uplink grant message. If the value of the third indication field is a sixth value, instructing the MAC entity to always generate a MAC PDU; and / or and when a value of the third indication field is a seventh value, the MAC entity instructs the terminal not to generate a MAC PDU when skipUplinkTxDynamic is set to true and the terminal satisfies a condition for performing an uplink transmission skip.

2. A method for generating a protocol data unit for use in a terminal, comprising: generating a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity based on a configuration of the terminal; the MAC entity transmitting the generated MAC PDU to a physical layer entity; The terminal is configured such that, when any one of the conditions for skipping uplink transmission is not satisfied, the MAC entity generates a MAC PDU; The condition for skipping uplink transmission is A value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); The method of generating a protocol data unit, comprising: the MAC PDU including only a periodic buffer status report (BSR) and no data for a logical channel group; or the MAC PDU including only a filler BSR.

3. the parameter skipUplinkTxDynamic of the MAC entity is configured as true and the grant indicated to the HARQ entity is an uplink grant addressed to the C-RNTI or the grant indicated to the HARQ entity is configured; PUSCH transmission does not require aperiodic CSI; and Not requiring "UCI multiplexing" or "UL-SCH" for the PUSCH transmission; The MAC PDU includes 0 MAC service data units (SDUs); 3. The method of claim 2, wherein if the MAC PDU satisfies all of the following conditions: the MAC PDU contains only a Periodic Buffer Status Report (BSR) and does not contain data for any logical channel group; or the MAC PDU contains only a Filling BSR, the MAC entity does not generate a MAC PDU for a HARQ entity.

4. A method for generating a protocol data unit for use in a terminal, comprising: generating a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity according to second indication information sent by a physical layer entity to the MAC entity; the MAC entity transmitting the generated MAC PDU to the physical layer entity; the second indication information is inter-layer signaling transmitted from the physical layer entity when the physical layer entity determines that resources of the scheduled physical uplink shared channel (PUSCH) and the scheduled physical uplink control channel (PUCCH) overlap in the time domain.

5. A configuration method for generating a protocol data unit for use in a network side device, comprising: sending first instruction information to a terminal to instruct a medium access control (MAC) entity of the terminal to generate a MAC protocol data unit (PDU) for a currently scheduled hybrid automatic repeat request (HARQ) entity; The first indication information is carried in an uplink grant message transmitted by the network side device, the first indication information occupies a separate first indication field in the uplink grant message; or The first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; or the first indication information is multiplexed with a third indication field for indicating other information in the uplink grant message; the first indication information occupies a separate first indication field in the uplink grant message; Instructing the MAC entity to always generate a MAC PDU if the value of the first indication field is a first value; and / or When the value of the first indication field is a second value, the MAC entity instructs the terminal not to generate a MAC PDU when a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true and the terminal satisfies a condition for skipping uplink transmission; Or, the first indication information is jointly encoded with other indication information to occupy a second indication field in the uplink grant message; If the value of the second indication field is a third value, when the channel state information (CSI) request is not set to all zeros, instruct the MAC entity to generate a MAC PDU; If the value of the second indication field is a fourth value, instruct the MAC entity to always generate a MAC PDU; If the value of the second indication field is a fifth value, when a value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true and the terminal satisfies a condition for skipping uplink transmission, instruct the MAC entity not to generate a MAC PDU; Or, The first indication information is obtained by multiplexing a third indication field in the uplink grant message. If the value of the third indication field is a sixth value, instructing the MAC entity to always generate a MAC PDU; and / or When the value of the third indication field is a seventh value, the MAC entity instructs the terminal not to generate a MAC PDU when skipUplinkTxDynamic is set to true and the terminal satisfies a condition to perform an uplink transmission skip.

6. The condition for skipping uplink transmission is A value of a parameter skipUplinkTxDynamic configured by the MAC entity is set to true, and the MAC entity is positioned to a HARQ entity indicated in the uplink grant message; the uplink grant message does not trigger an aperiodic CSI report; and The resources allocated by the uplink grant message do not overlap in a time domain with uplink control signaling to be transmitted; and The MAC PDU includes 0 MAC service data units (SDUs); 6. The method of claim 5, wherein the MAC PDU includes only a Periodic Buffer Status Report (BSR) and does not include data for a logical channel group, or the MAC PDU includes only a Filling BSR.

7. 7. An electronic device comprising a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions implementing the method of any one of claims 1 to 6 when executed by the processor.

Citation Information

Patent Citations

  • Base station

    WO2020026292A1

  • Terminal and wireless communication method

    WO2020040179A1