Apparatus, method, apparatus and computer readable medium for media access control control unit transmission
By configuring terminal devices and network devices, managing the number of MAC-CE transmissions and timer retriggering events, the problem of insure in decoding in HARQ mode B is solved, and the transmission delay reduction and system performance improvement in HARQ mode A is achieved. .
Patent Information
- Application Number
- CN202280094567.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-08
- Publication Date
- 2024-11-15
AI Technical Summary
In non-terrestrial networks, when MAC-CE is multiplexed in HARQ mode B, it cannot ensure correct decoding, resulting in a degradation of system performance; while when multiplexed in HARQ mode A, the transmission delay increases.
Through the configuration of the terminal device and the network device, the number of transmissions configured by the network device for sending the uplink medium access control control unit is obtained, and in response to the trigger event, the MAC-CE is sent or cancelled in the hybrid automatic retransmission request process. Retrieve the event with a timer to ensure the reliability of decoding.
It realizes that the transmission delay is avoided in any HARQ mode while ensuring the correct decoding of MAC-CE, improving system performance.
Smart Images

Figure CN118975377A_ABST
Abstract
Description
Technical Field
[0001] Various embodiments are directed to devices, methods, apparatus, and computer-readable media for medium access control element (MAC-CE) transmissions. Background Art
[0002] In a non-terrestrial network (NTN), for the uplink (UL), two UL hybrid automatic repeat request (HARQ) retransmission states / modes are defined: HARQ mode A and HARQ mode B. The UE behavior in HARQ mode A preferably supports the reception of UL retransmission grants based on UL decoding results. For example, in HARQ mode A, HARQ retransmissions can be scheduled by the network side based on the HARQ transmission decoding results. The UE behavior in HARQ mode B preferably does not support UL retransmissions and / or blind UL retransmissions. For example, in HARQ mode B, HARQ retransmissions can be scheduled before the HARQ transmission decoding results are reached on the network side. When MAC-CE is multiplexed / transmitted, the triggering event for MAC-CE will be cancelled. If MAC-CE is multiplexed in HARQ mode B, UL retransmissions and / or blind UL retransmissions cannot ensure that the MAC-CE can be correctly decoded. If the MAC-CE is critical and cannot be successfully decoded by the base station (BS), the system performance will be affected. On the other hand, if MAC-CE is restricted to be multiplexed in HARQ mode A, MAC-CE transmission opportunities are also restricted, which may cause transmission delay. Summary of the invention
[0003] The following provides a brief summary of exemplary embodiments to provide a basic understanding of some aspects of various embodiments. It should be noted that this summary is not intended to identify the key features of the basic elements or define the scope of the embodiments, and its only purpose is to introduce some concepts in a simplified form as a preface to the more detailed description provided below.
[0004] In a first aspect, a terminal device is disclosed. The terminal device may include at least one processor and at least one memory. The at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to, together with the at least one processor, cause the terminal device to execute: obtaining a transmission number configured by a network device for sending an uplink medium access control control element; and in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, sending an uplink medium access control control element to the network device in a hybrid automatic repeat request process.
[0005] In some exemplary embodiments, at least one memory and the computer program code may also be configured to, together with at least one processor, cause the terminal device to further execute: if an uplink medium access control control unit is sent in a hybrid automatic repeat request process in mode A, cancel the triggering event; and avoid further sending of an uplink medium access control control unit.
[0006] In some example embodiments, the at least one memory and the computer program code may also be configured to, together with the at least one processor, cause the terminal device to further perform: canceling the triggering event if a downlink medium access control control unit is received from the network device confirming the decoding of the uplink medium access control control unit; and avoiding further sending of the uplink medium access control control unit.
[0007] In some example embodiments, the acknowledgment of the downlink medium access control control element has a logical channel identifier or an extended logical channel identifier specific to the decoded acknowledgment of the uplink medium access control control element.
[0008] In some example embodiments, the logical channel identifier or the extended logical channel identifier is in a subheader of an acknowledgment downlink medium access control control element, and the acknowledgment downlink medium access control control element has no payload.
[0009] In some example embodiments, the downlink medium access control control element has a reserved bit that is specific to the acknowledgement of the decoding of the uplink medium access control control element.
[0010] In some example embodiments, the acknowledgment downlink medium access control control element has a payload indicating an acknowledgment of decoding the uplink medium access control control element via a bitmap.
[0011] In some example embodiments, the at least one memory and the computer program code may be further configured to, together with the at least one processor, cause the terminal device to further execute: if the number of transmissions reaches a configured number of transmissions, canceling the triggering event.
[0012] In some example embodiments, the number of transmissions is counted based on the number of initial transmissions and retransmissions of at least one transport block carrying the uplink medium access control control element.
[0013] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions of at least one transport block carrying an uplink medium access control control element.
[0014] In some example embodiments, the at least one memory and the computer program code may also be configured to, together with the at least one processor, cause the terminal device to further execute: starting a timer configured by the network device for re-triggering the triggering event, and if the number of transmissions reaches the configured number of transmissions and no downlink medium access control control unit confirming the decoding of the uplink medium access control control unit is received from the network device before the timer expires, re-triggering the triggering event when the timer expires.
[0015] In some example embodiments, the timer may be started at the last retransmission of the uplink medium access control control element.
[0016] In some example embodiments, a timer may be started upon initial transmission of an uplink medium access control control element.
[0017] In some example embodiments, the uplink MAC control element may be sent in a Mode B HARQ process.
[0018] In some example embodiments, the transmission number may be common to multiple uplink medium access control control elements.
[0019] In some example embodiments, the transmission number may be uplink medium access control control element specific.
[0020] In a second aspect, a network device is disclosed. The network device may include at least one processor and at least one memory. The at least one memory may include computer program code, and the at least one memory and the computer program code may be configured to, together with the at least one processor, cause the network device to execute: configuring a transmission number for sending an uplink medium access control control element for a terminal device, wherein in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
[0021] In some example embodiments, the at least one memory and the computer program code may also be configured to, together with the at least one processor, cause the network device to further execute: if the uplink medium access control control unit is successfully decoded, transmitting a downlink medium access control control unit to the terminal device for confirming the decoding of the uplink medium access control control unit.
[0022] In some example embodiments, the at least one memory and the computer program code may also be configured to, with the at least one processor, cause the network device to further perform: configuring a downlink medium access control control unit.
[0023] In some example embodiments, at least one memory and the computer program code may also be configured to, together with at least one processor, cause the network device to further perform: configuring a timer for the terminal device to re-trigger the triggering event; if the number of transmissions reaches the number of transmissions and the terminal device does not receive a downlink medium access control control unit confirming the decoding of the uplink medium access control control unit from the network device before the timer expires, the triggering event is re-triggered when the timer expires.
[0024] In a third aspect, a method performed by a terminal device is disclosed. The method may include: obtaining a transmission number configured by a network device for sending an uplink medium access control control element; and in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, sending the uplink medium access control control element to the network device in a hybrid automatic repeat request process.
[0025] In some example embodiments, the method may further include: canceling the triggering event if the uplink medium access control control element is sent in a hybrid automatic repeat request process in mode A; and avoiding further sending of the uplink medium access control control element.
[0026] In some example embodiments, the method may further include: canceling the triggering event if a downlink medium access control control element confirming the decoding of the uplink medium access control control element is received from the network device; and refraining from further sending of the uplink medium access control control element.
[0027] In some example embodiments, the acknowledging downlink medium access control control element may have a logical channel identifier or an extended logical channel identifier that is specific to the decoded acknowledgment of the uplink medium access control control element.
[0028] In some example embodiments, the logical channel identifier or the extended logical channel identifier may be in a subheader of an acknowledgment downlink medium access control control element, and the acknowledgment downlink medium access control control element may have no payload.
[0029] In some example embodiments, a downlink medium access control control element may have a reserved bit specific to an acknowledgement of a decode of an uplink medium access control control element.
[0030] In some example embodiments, the acknowledging downlink MAC control element may have a payload indicating the acknowledgment of decoding the uplink MAC control element via a bitmap.
[0031] In some example embodiments, the method may further include cancelling the triggering event if the number of transmissions reaches a configured number of transmissions.
[0032] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions and retransmissions of at least one transport block carrying the uplink medium access control control element.
[0033] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions of at least one transport block carrying an uplink medium access control control element.
[0034] In some example embodiments, the method may further include starting a timer configured by the network device for re-triggering the triggering event, and if the number of transmissions reaches the configured number of transmissions and a downlink medium access control control element confirming the decoding of the uplink medium access control element is not received from the network device before the timer expires, re-triggering the triggering event when the timer expires.
[0035] In some example embodiments, the timer may be started at the last retransmission of the uplink medium access control control element.
[0036] In some example embodiments, a timer may be started upon initial transmission of an uplink medium access control control element.
[0037] In some example embodiments, the uplink MAC control element may be sent in a Mode B HARQ process.
[0038] In some example embodiments, the transmission number may be common to multiple uplink medium access control control elements.
[0039] In some example embodiments, the transmission number may be uplink medium access control control element specific.
[0040] In a fourth aspect, a method performed by a network device is disclosed. The method may include: configuring a transmission number for a terminal device to send an uplink medium access control control element, wherein in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
[0041] In some example embodiments, the method may further include: if the uplink medium access control control element is successfully decoded, transmitting a downlink medium access control control element confirming the decoding of the uplink medium access control control element to the terminal device.
[0042] In some example embodiments, the method may further include configuring a downlink medium access control control unit.
[0043] In some example embodiments, the method may further include configuring a timer for the terminal device to re-trigger the trigger event, and if the number of transmissions reaches the transmission number and the terminal device does not receive a downlink medium access control control unit confirming the decoding of the uplink medium access control control unit from the network device before the timer expires, the trigger event is re-triggered when the timer expires.
[0044] In a fifth aspect, an apparatus is disclosed. The apparatus as a terminal device may include: a component for obtaining a transmission number configured by a network device for sending an uplink medium access control control element; and a component for sending an uplink medium access control control element to the network device in a hybrid automatic repeat request process in response to a trigger event for the uplink medium access control control element if the number of transmissions is less than the configured number of transmissions.
[0045] In some example embodiments, the apparatus may further include: means for cancelling the triggering event if an uplink medium access control control element is sent during a hybrid automatic repeat request process in mode A; and means for avoiding further sending of the uplink medium access control control element.
[0046] In some example embodiments, the apparatus may further include: a component for canceling the triggering event if a downlink medium access control control element is received from the network device confirming the decoding of the uplink medium access control control element; and a component for avoiding further sending of uplink medium access control control elements.
[0047] In some example embodiments, the acknowledging downlink medium access control control element may have a logical channel identifier or an extended logical channel identifier that is specific to the decoded acknowledgment of the uplink medium access control control element.
[0048] In some example embodiments, the logical channel identifier or the extended logical channel identifier may be in a subheader of an acknowledgment downlink medium access control control element, and the acknowledgment downlink medium access control control element may have no payload.
[0049] In some example embodiments, a downlink medium access control control element may have a reserved bit specific to an acknowledgement of a decode of an uplink medium access control control element.
[0050] In some example embodiments, the acknowledging downlink MAC control element may have a payload indicating the acknowledgment of decoding the uplink MAC control element via a bitmap.
[0051] In some example embodiments, the apparatus may further comprise means for cancelling the triggering event if the number of transmissions reaches a configured number of transmissions.
[0052] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions and retransmissions of at least one transport block carrying the uplink medium access control control element.
[0053] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions of at least one transport block carrying an uplink medium access control control element.
[0054] In some example embodiments, the apparatus may further include: a component for starting a timer configured by the network device for re-triggering a triggering event; and a component for re-triggering the triggering event when the timer expires if the number of transmissions reaches the configured number of transmissions and a downlink medium access control control unit confirming the decoding of the uplink medium access control control unit is not received from the network device before the timer expires.
[0055] In some example embodiments, the timer may be started at the last retransmission of the uplink medium access control control element.
[0056] In some example embodiments, a timer may be started upon initial transmission of an uplink medium access control control element.
[0057] In some example embodiments, the uplink MAC control element may be sent in a Mode B HARQ process.
[0058] In some example embodiments, the transmission number may be common to multiple uplink medium access control control elements.
[0059] In some example embodiments, the transmission number may be uplink medium access control control element specific.
[0060] In a sixth aspect, an apparatus is disclosed. The apparatus as a network device may include: a component for configuring a transmission number for sending an uplink medium access control control element for a terminal device, wherein in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element may be sent to the network device in a hybrid automatic repeat request process.
[0061] In some example embodiments, the apparatus may further include means for transmitting to the terminal device a downlink medium access control control element confirming decoding of the uplink medium access control control element if the uplink medium access control control element is successfully decoded.
[0062] In some example embodiments, the apparatus may further include means for configuring a downlink medium access control control unit.
[0063] In some example embodiments, the apparatus may further include: a component for configuring a timer for a terminal device for re-triggering a triggering event, wherein if the number of transmissions reaches the number of transmissions and the terminal device does not receive a downlink medium access control control unit confirming the decoding of the uplink medium access control control unit from the network device before the timer expires, the triggering event is re-triggered when the timer expires.
[0064] In a seventh aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon, configured to cause a terminal device to execute: obtaining a transmission number configured by a network device for sending an uplink medium access control control element; and in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, sending the uplink medium access control control element to the network device in a hybrid automatic repeat request process.
[0065] In some example embodiments, the computer-readable medium may also include instructions stored thereon for causing the terminal device to further perform: canceling the triggering event if an uplink medium access control control unit is sent in a hybrid automatic repeat request process in mode A; and avoiding further sending of an uplink medium access control control unit.
[0066] In some example embodiments, the computer-readable medium may also include instructions stored thereon for causing the terminal device to further perform: canceling the triggering event if a downlink medium access control control unit is received from the network device confirming the decoding of the uplink medium access control control unit; and avoiding further sending of the uplink medium access control control unit.
[0067] In some example embodiments, the acknowledging downlink medium access control control element may have a logical channel identifier or an extended logical channel identifier that is specific to the decoded acknowledgment of the uplink medium access control control element.
[0068] In some example embodiments, the logical channel identifier or the extended logical channel identifier may be in a subheader of an acknowledgment downlink medium access control control element, and the acknowledgment downlink medium access control control element may have no payload.
[0069] In some example embodiments, a downlink medium access control control element may have a reserved bit specific to an acknowledgement of a decode of an uplink medium access control control element.
[0070] In some example embodiments, the acknowledging downlink MAC control element may have a payload indicating the acknowledgment of decoding the uplink MAC control element via a bitmap.
[0071] In some example embodiments, the computer-readable medium may further include instructions stored thereon for causing the terminal device to further execute: if the number of transmissions reaches a configured number of transmissions, canceling the triggering event.
[0072] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions and retransmissions of at least one transport block carrying the uplink medium access control control element.
[0073] In some example embodiments, the number of transmissions may be counted based on the number of initial transmissions of at least one transport block carrying an uplink medium access control control element.
[0074] In some example embodiments, the computer-readable medium may also include instructions stored thereon for causing the terminal device to further execute: starting a timer configured by the network device for re-triggering the triggering event, and if the number of transmissions reaches the configured number of transmissions and no downlink medium access control control unit confirming the decoding of the uplink medium access control control unit is received from the network device before the timer expires, re-triggering the triggering event when the timer expires.
[0075] In some example embodiments, the timer may be started at the last retransmission of the uplink medium access control control element.
[0076] In some example embodiments, a timer may be started upon initial transmission of an uplink medium access control control element.
[0077] In some example embodiments, the uplink MAC control element may be sent in a Mode B HARQ process.
[0078] In some example embodiments, the transmission number may be common to multiple uplink medium access control control elements.
[0079] In some example embodiments, the transmission number is specific to an uplink medium access control control element.
[0080] In an eighth aspect, a computer-readable medium is disclosed. The computer-readable medium may include instructions stored thereon, causing a network device to execute: configuring a transmission number for a terminal device to send an uplink medium access control control element, wherein in response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
[0081] In some example embodiments, the computer-readable medium may further include instructions stored thereon, causing the network device to further execute: if the uplink medium access control control element is successfully decoded, transmitting a downlink medium access control control element to the terminal device for confirming the decoding of the uplink medium access control control element.
[0082] In some example embodiments, the computer readable medium may further include instructions stored thereon to cause the network device to further perform: configuring a downlink medium access control control unit.
[0083] In some example embodiments, the computer-readable medium may also include instructions stored thereon to cause the network device to further perform: configuring a timer for the terminal device to re-trigger the triggering event, if the number of transmissions reaches the transmission number, and the terminal device does not receive a downlink medium access control control unit confirming the decoding of the uplink medium access control control unit from the network device before the timer expires, then the triggering event is re-triggered when the timer expires.
[0084] Other features and advantages of example embodiments of the present disclosure will become apparent from the following description of the detailed description when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of example embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0085] Some example embodiments will now be described, by way of non-limiting examples, with reference to the accompanying drawings.
[0086] Figure 1 An exemplary sequence diagram for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0087] Figure 2 An exemplary flow chart for MAC-CE transmission according to an exemplary embodiment of the present disclosure is shown.
[0088] Figure 3A flow chart of an example method 300 for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0089] Figure 4 A flow chart of an example method 400 for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0090] Figure 5 A block diagram of an example device 400 for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0091] Figure 6 A block diagram of an example device 600 for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0092] Figure 7 A block diagram of an example apparatus 700 for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0093] Figure 8 A block diagram of an example apparatus 800 for MAC-CE transmission according to an example embodiment of the present disclosure is shown.
[0094] In all drawings, the same or similar reference numerals represent the same or similar elements, and repeated description of the same elements will be omitted. DETAILED DESCRIPTION
[0095] Hereinafter, some example embodiments are described in detail with reference to the accompanying drawings. In order to provide a thorough understanding of various concepts, the following description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known circuits, techniques, and components are shown in block diagram form to avoid obscuring the concepts and features described.
[0096] The exemplary embodiments of the present disclosure provide a solution for transmitting a MAC-CE on any UL resource that is independent of the HARQ mode, thereby avoiding transmission delays and ensuring the reliability of correctly decoding a critical MAC-CE.
[0097] Figure 1 An exemplary sequence diagram for MAC-CE transmission according to an exemplary embodiment of the present disclosure is shown. Figure 1 , UE 110 may represent any terminal device in a wireless communication network. Network device 120 may serve as a BS in the wireless communication network and serve UE 110. The wireless communication network may be, for example, an NTN, and network device 120 may be located, for example, in a geosynchronous orbit (GEO) satellite or a non-GEO satellite, such as a medium earth orbit (MEO) satellite or a low earth orbit (LEO) satellite.
[0098] In operation 125, the network device 120 may configure a transmission number 130 for the UE 110 to send a UL MAC-CE. The transmission number 130 may be common to a plurality of UL MAC-CEs. Alternatively, the transmission number 130 may be specific to a group of UL MAC-CEs. Alternatively, the transmission number 130 may be specific to one UL MAC-CE, such as UL MAC-CE 135. The transmission number 130 may be the maximum number of transmissions for the UE 110 to send the UL MAC-CE 135, which may represent any UL MAC-CE. If the number of transmissions is less than the configured transmission number 130, the UE 110 may send the UL MAC-CE 135 to the network device 120 in a HARQ process.
[0099] The network device 120 may transmit the number 130 to the UE 110. The configured number of transmissions 130 is obtained, and if a trigger event for the UL MAC-CE 135 occurs, then in response to the trigger event, the UE 110 may trigger the corresponding UL MAC-CE 135 in operation 132, and if the number of transmissions is less than the configured number of transmissions 130, the UE 110 sends the UL MAC-CE 135 to the network device 120 in the HARQ process. The transmission may be an initial transmission of a transport block (TB) carrying the UL MAC-CE 135 or a retransmission of a TB carrying the UL MAC-CE 135. The UL MAC-CE 135 may be multiplexed / transmitted in a HARQ process scheduled by a UL grant of a HARQ of a mode A or a HARQ of a mode B.
[0100] In an embodiment, as an option, if the UL MAC-CE 135 is transmitted in the HARQ process of mode A, the UE 110 may cancel the triggering event, for example, after the first transmission of the UL MAC-CE 135 in operation 170, and if the triggering event is canceled, avoid further transmission of the UL MAC-CE 135. Since mode A can support reception of a UL retransmission grant based on a UL decoding result, the reliability of correctly decoding the MAC-CE 135 can be guaranteed to a certain extent.
[0101] Alternatively, UE 110 may avoid canceling the triggering event even if UL MAC-CE 135 is multiplexed / transmitted in the HARQ process of Mode A. For example, UE 110 may perform the following operations and / or cancel the triggering event based on other (multiple) conditions regardless of HARQ Mode A or HARQ Mode B.
[0102] Alternatively, in some embodiments, if UL MAC-CE 135 is sent in a HARQ process of Mode B, UE 110 may perform the following operations and / or cancel the triggering event based on other condition(s). HARQ Mode B may support no UL retransmission and / or blind UL retransmission.
[0103] On the network side, if the UL MAC-CE 135 is received, the network device 120 may decode the UL MAC-CE 135 in operation 145. If the network device 120 successfully decodes the UL MAC-CE 135, the network device 120 may transmit a downlink (DL) MAC-CE 155 to the UE 110 to confirm the decoding of the UL MAC-CE 135. The DL MAC-CE 155 may be used as an acknowledgement (ACK) feedback of the UL MAC-CE 135.
[0104] If the DL MAC-CE 155 is received, then in operation 170, if the triggering event is canceled, the UE 110 may cancel the triggering event and avoid further sending of the UL MAC-CE 135. In an embodiment, the ACK DL MAC-CE 155 may have a logical channel identifier (LCID) or an extended logical channel identifier (eLCID) of the decoded ACK specific to the UL MAC-CE 135. The LCID or eLCID may be reserved for the UL MAC-CE 135. In an option, the LCID or eLCID may be in a subheader of the ACK DL MAC-CE 155, and the ACK DL MAC-CE 155 may have no payload.
[0105] Alternatively, in an embodiment, the DL MAC-CE 155 may have a reserved bit specific to the decoded ACK of the UL MAC-CE 135. For example, the DL MAC-CE 155 may be an existing MAC-CE having at least one reserved bit, and one reserved bit may be used for the decoded ACK of the UL MAC-CE 135.
[0106] Alternatively or additionally, the ACK DL MAC-CE 155 may have a payload indicating the decoded ACK of the UL MAC-CE 135 through a bitmap. For example, the ACK DL MAC-CE 155 may have different bits for confirming the decoding of different UL MAC-CEs. For example, the third bit may be used for the decoded ACK of the UL MAC-CE 135, and the fifth bit may be used for the decoded ACK of another UL MAC-CE 135.
[0107] The mapping between ACK DL MAC-CE 155 and UL MAC-CE 135 and the bitmap of ACK DL MAC-CE 155 may be configured by network device 120 in operation 150 and transmitted to UE 110 via radio resource control (RRC) signaling, and may alternatively or additionally be pre-specified in a specification / standard.
[0108] Alternatively or additionally, after the first transmission of the UL MAC-CE 135 , in operation 140 , the UE 110 may count the number of transmissions of the UL MAC-CE 135 , and if the number of transmissions reaches the configured number of transmissions 130 , the triggering event may be canceled.
[0109] In an embodiment, the UE 110 may count the number of transmissions based on the number of initial transmissions and retransmissions of at least one TB carrying the UL MAC-CE 135. For example, whether the UL MAC-CE 135 is initially transmitted on a TB, retransmitted on a TB, or initially transmitted and retransmitted on another TB, the UE 110 will count as an increment of the number of transmissions.
[0110] Alternatively, in an embodiment, the UE 110 may count the number of transmissions based on the number of initial transmissions of at least one TB carrying the UL MAC-CE 135. For example, after the initial transmission on a TB, retransmissions on the TB will not be counted. If the UL MAC-CE 135 was initially transmitted on another TB, the UE 110 will count as an increment of the number of transmissions. In this case, the number of transmissions may be the number of transmitted TBs carrying the UL MAC-CE 135.
[0111] On the network side, in operation 125, UE 110 may also configure a timer 160 for UE 110 to re-trigger the triggering event. Timer 160 may be related to the duration for allowing network device 120 to confirm the decoding of UL MAC-CE 135. The configuration of timer 160 may include the length of the timer. As an option, the configuration of timer 160 may also include the timing of starting timer 160. Alternatively, the start timing of timer 160 may be pre-specified in a specification or standard. Upon receiving the configuration of timer 160, if the number of transmissions reaches the number of transmissions 130 and UE 110 does not receive ACK DL MAC-CE 155 before timer 160 expires, UE 110 may use timer 160 to re-trigger the triggering event.
[0112] With the timer 160 configured, in operation 165, the UE 110 may start the timer 160. In an embodiment, the UE 110 may start the timer 160 at the last retransmission of the UL MAC-CE 135. In this case, the length of the timer 160 may be at least one round trip time (RTT) between the UE 110 and the network device 120. Alternatively, in an embodiment, the UE 110 may start the timer 160 at the initial transmission of the UL MAC-CE 135. In this case, the length of the timer 160 may be at least one RTT between the UE 110 and the network device 120 plus the estimated duration of the retransmission(s) of the UL MAC-CE 135.
[0113] In operation 175, if the number of transmissions reaches the configured number of transmissions 130, and an ACK DL MAC-CE 155 confirming the decoding of the UL MAC-CE 135 is not received from the network device 120 before the timer 160 expires, the UE 110 may re-trigger the triggering event when the timer 160 expires. By re-triggering the triggering event, the UE 110 may repeat the transmission of the UL MAC-CE 135 so that the reliability of successfully decoding the UL MAC-CE 135 may be ensured.
[0114] Figure 2 An exemplary flow chart for MAC-CE transmission according to an exemplary embodiment of the present disclosure is shown. Figure 1 The corresponding operations shown in the Figure 2 Operations in .
[0115] After the start of the process, the network device 120 may configure a maximum number of transmissions, denoted as Nmax, for the UL MAC-CE in operation 210. Nmax may be, for example, the number of transmissions 130, and the UL MAC-CE may be, for example, UL MAC-CE 135.
[0116] In operation 215, in response to a triggering event for the UL MAC-CE 135, the UE 110 may trigger the corresponding UL MAC-CE 135 and set the number of transmissions (denoted as Ntx) to 0 and start transmission of the UL MAC-CE 135 in the HARQ process.
[0117] As an option, in operation 220, if the UL MAC-CE 135 is multiplexed / transmitted in the HARQ process of mode A (the "Yes" branch of operation 220), then in operation 225, if the triggering event is canceled, the UE 110 may cancel the triggering event and avoid further sending the UL MAC-CE 135. If the UL MAC-CE 135 is multiplexed / transmitted in the HARQ process of mode B (the "No" branch of operation 220), the UE 110 may continue with the following operations.
[0118] Alternatively, operation 220 may be omitted, and in this case, UE 110 may perform the flow regardless of the HARQ mode.
[0119] In operation 230, the UE 110 may count Ntx. In an embodiment, if a TB carrying the UL MAC-CE 135 is transmitted, the UE 110 may count Ntx regardless of whether the UL MAC-CE 135 is initially transmitted on the TB, retransmitted on the TB, or transmitted on other (multiple) TBs. If the HARQ process is set with a number of transmissions (denoted as M), where the UL MAC-CE 135 will be transmitted M times, Ntx may increase by M. For example, in the case where the UL MAC-CE 135 is multiplexed / transmitted in a HARQ process of mode B, if mode B supports blind retransmission, M may be equal to the number of initial transmissions and subsequent blind retransmissions, and if mode B does not support UL retransmission, M will be 1.
[0120] Alternatively, in an embodiment, the UE 110 may count Ntx as the number of initial transmissions of different TBs carrying the UL MAC-CE 135. In this case, Ntx will be increased by 1 regardless of whether retransmissions are supported by the HARQ mode.
[0121] In operation 235, in the case where Ntx has not reached Nmax (the "yes" branch of operation 235), if the UE 110 receives a DL ACK MAC-CE, for example, ACK DL MAC-CE 155 confirms the decoding of the UL MAC-CE 135 in operation 245 (the "yes" branch of operation 245), in operation 250, if the triggering event is canceled, the UE 110 may cancel the triggering event and avoid further sending of the UL MAC-CE 135. If the UE 110 does not receive the ACK DL MAC-CE 155 in operation 245 (the "no" branch of operation 245), the UE 110 may continue the process from operation 220.
[0122] In operation 235, if Ntx reaches Nmax (the "No" branch of operation 235), the UE 110 may cancel the triggering event in operation 240. After operation 240 in which Ntx reaches Nmax, if the UE 110 does not receive the ACK DL MAC-CE 155 before, for example, the timer 160 expires, the UE 110 may re-trigger the triggering event when the timer 160 expires. In this case, the flow may be repeated from operation 215.
[0123] It can be understood that the above embodiments can be applied to any UL MAC-CE. Since there is no restriction on the logical channel priority (LCP) on the UL MAC-CE, the UL MAC-CE can be transmitted on any UL resource regardless of the HARQ mode, so that the UL MAC-CE transmission opportunity can be fully utilized and the transmission delay can be avoided. At the same time, the reliability of successfully decoding the UL MAC-CE can be guaranteed. According to the embodiments of the present disclosure, a more favorable effect can be produced on the key UL MAC-CE.
[0124] For example, reporting timing advance (TA) for UL MAC-CE can assist UL scheduling in NTN and can be called TA reporting MAC-CE. If the TA reporting MAC-CE cannot be successfully decoded by the network side, the system performance will be seriously affected. According to the embodiment of the present disclosure, the HARQ process of UL grant scheduling can be adaptive regardless of the HARQ mode, and thus the reliability of successfully decoding UL MAC-CE (such as TA reporting MAC-CE) can be achieved.
[0125] Figure 3 A flow chart of an example method 300 for MAC-CE transmission according to an example embodiment of the present disclosure is shown. The example method 300 may be performed, for example, at a terminal device (such as UE 110).
[0126] refer to Figure 3 , the example method 200 may include operation 310: obtaining the number of transmissions configured by the network device for sending UL MAC-CE; and operation 320: in response to a trigger event for UL MAC-CE, if the number of transmissions is less than the configured number of transmissions, sending UL MAC-CE to the network device in a HARQ process.
[0127] The details of operation 310 have been described in the above description at least with respect to the number of transmissions 130 and Nmax, and a repeated description thereof is omitted here.
[0128] The details of operation 320 have been described above at least with respect to the UL MAC-CE 135, and a repeated description thereof is omitted here.
[0129] In an embodiment, the example method 300 may further include an operation of canceling the triggering event and avoiding further transmission of the UL MAC-CE if the UL MAC-CE is transmitted in the HARQ process of mode A. More details have been described in the above description at least with respect to operation 170 and operations 220 and 225, and their repeated description is omitted here.
[0130] In an embodiment, the example method 300 may further include the following operations: if a decoded DL MAC-CE confirmation for the UL MAC-CE is received from the network device, the triggering event is canceled and further transmission of the UL MAC-CE is avoided. More details have been described above at least with respect to the description of the DL MAC-CE 155, operation 170, and operations 245 and 250, and their repeated description is omitted here.
[0131] In an embodiment, the ACK DL MAC-CE may have an LCID or eLCID specific to the decoded ACK of the UL MAC-CE.More details have been described above at least with respect to the DL MAC-CE 155, and a repeated description thereof is omitted here.
[0132] In an embodiment, the LCID or eLCID may be in the subheader of the ACK DL MAC-CE, and the ACK DL MAC-CE may have no payload.More details have been described above at least with respect to the DL MAC-CE 155, and a repeated description thereof is omitted here.
[0133] In an embodiment, the DL MAC-CE may have a reserved bit specific to the decoded ACK of the UL MAC-CE.More details have been described above at least in the description about the DL MAC-CE 155, and a repeated description thereof is omitted here.
[0134] In an embodiment, the confirmation DL MAC-CE may have a payload indicating an ACK of the decoded UL MAC-CE through a bitmap.More details have been described above at least in the description about the DL MAC-CE 155, and a repeated description thereof is omitted here.
[0135] In an embodiment, the example method 300 may further include an operation of canceling the trigger event if the number of transmissions reaches the configured number of transmissions.More details have been described in the above description at least with respect to operation 170 and operations 235 and 240, and their repeated description is omitted here.
[0136] In an embodiment, the number of transmissions may be counted based on the number of initial transmissions and retransmissions of at least one TB carrying UL MAC-CE.More details have been described in the above description at least about operation 140 and operation 230, and repeated description thereof is omitted here.
[0137] In an embodiment, the number of transmissions may be counted based on the number of initial transmissions of at least one TB carrying UL MAC-CE.More details have been described in the above description at least with respect to operation 140 and operation 230, and repeated description thereof is omitted here.
[0138] In an embodiment, the example method 300 also includes: starting an operation of a timer configured by the network device for re-triggering the triggering event, more details of which are described in the above description at least with respect to operation 165, and its repeated description is omitted here; and if the number of transmissions reaches the configured number of transmissions and no DL MAC-CE confirming the decoding of the UL MAC-CE is received from the network device before the timer expires, re-triggering the triggering event when the timer expires, more details of which have been described in the above description at least with respect to operation 175 and operation 255, and its repeated description is omitted here.
[0139] In an embodiment, the timer may be started at the last retransmission of the UL MAC-CE.More details have been described in the above description at least with respect to operation 165, and a repeated description thereof is omitted here.
[0140] In an embodiment, the timer may be started at the initial transmission of the UL MAC-CE.More details have been described in the above description at least with respect to operation 165, and a repeated description thereof is omitted here.
[0141] In an embodiment, the UL MAC-CE may be transmitted in a HARQ process of mode B. More details have been described in the above description at least with respect to operation 220, and a repeated description thereof is omitted here.
[0142] In an embodiment, the transmission number may be common to a plurality of UL MAC-CEs.More details are described in the above description at least with respect to the transmission number 130, and a repeated description thereof is omitted here.
[0143] In an embodiment, the transmission number may be specific to the UL MAC-CE.More details are described in the above description at least with respect to the transmission number 130, and a repeated description thereof is omitted here.
[0144] Figure 4A flow chart of an example method 400 for MAC-CE transmission according to an example embodiment of the present disclosure is shown. The example method 400 may be performed at a network device (such as network device 120), for example.
[0145] Reference Figure 4 , the example method 400 may include operation 410: configuring a transmission number for the terminal device to send a UL MAC-CE, wherein if the number of transmissions is less than the configured number of transmissions, then in response to a trigger event for the UL MAC-CE, the UL MAC-CE may be sent to the network device in a HARQ process.
[0146] The details of operation 410 have been described above at least in the description about operation 125, the number of transmissions 130, operation 210, and Nmax, and a repeated description thereof is omitted here.
[0147] In an embodiment, the example method 400 may further include an operation of transmitting a DL MAC-CE for confirming the decoding of the UL MAC-CE to the terminal device if the UL MAC-CE is successfully decoded. More details have been described above at least with respect to the DL MAC-CE 155, and their repeated description is omitted here.
[0148] In an embodiment, the example method 400 may further include an operation of configuring a DL MAC-CE.More details have been described in the above description at least with respect to operation 150, and a repeated description thereof is omitted here.
[0149] In an embodiment, the example method 400 may further include an operation of configuring a timer for the terminal device to re-trigger the trigger event, and if the number of transmissions reaches the number of transmissions, and the terminal device does not receive a DL MAC-CE confirming the decoding of the UL MAC-CE from the network device before the timer expires, the trigger event is re-triggered when the timer expires. More details have been described in the above description of at least the timer 160 and the operation 170, and the operation 255, and their repeated description is omitted here.
[0150] Figure 5 A block diagram of an example device 400 for MAC-CE transmission according to an example embodiment of the present disclosure is shown. The device may be, for example, at least a part of a terminal device such as the UE 110 in the above example.
[0151] like Figure 5As shown, the example device 500 may include at least one processor 510 and at least one memory 520 that may include computer program code 530. The at least one memory 520 and the computer program code 530 may be configured to, together with the at least one processor 510, cause the device 500 to at least perform the above-described example method 300.
[0152] In various example embodiments, at least one processor 510 in the example device 500 may include, but is not limited to, at least one hardware processor, including at least one microprocessor such as a central processing unit (CPU), a portion of at least one hardware processor, and any other suitable special-purpose processor, such as those developed based on, for example, a field programmable gate array (FPGA) and an application-specific integrated circuit (ASIC). In addition, the at least one processor 510 may also include Figure 5 At least one other circuit system or component not shown.
[0153] In various example embodiments, at least one memory 520 in the example device 500 may include at least one storage medium in different forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least memory 520 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any combination of the above.
[0154] Furthermore, in various example embodiments, the example device 500 may further include at least one other circuit system, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.
[0155] In various example embodiments, the circuit systems, parts, elements, and interfaces in the example device 500 including at least one processor 510 and at least one memory 520 may be coupled together in any suitable manner (e.g., electrically, magnetically, optically, electromagnetically, etc.) via any suitable connection (including but not limited to buses, beams, wires, and / or wireless lines).
[0156] It can be understood that the structure of the device on the UE 110 side is not limited to the above example device 500.
[0157] Figure 6 A block diagram of an example device 600 for MAC-CE transmission according to an example embodiment of the present disclosure is shown. The device may be, for example, at least a part of a network device (such as the network device 120 in the above example).
[0158] like Figure 6 As shown, the example device 600 may include at least one processor 610 and at least one memory 620 that may include computer program code 630. The at least one memory 620 and the computer program code 630 may be configured to, together with the at least one processor 610, cause the device 600 to at least perform the above-described example method 400.
[0159] In various example embodiments, at least one processor 610 in the example device 600 may include, but is not limited to, at least one hardware processor including at least one microprocessor such as a central processing unit (CPU), a portion of at least one hardware processor, and any other suitable dedicated processor (such as those developed based on, for example, a field programmable gate array (FPGA) and an application specific integrated circuit (ASIC)). In addition, the at least one processor 610 may also include Figure 6 At least one other circuit system or component not shown.
[0160] In various example embodiments, at least one memory 620 in the example device 600 may include at least one storage medium in different forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, random access memory (RAM), cache, etc. Non-volatile memory may include, but is not limited to, for example, read-only memory (ROM), hard disk, flash memory, etc. In addition, at least memory 620 may include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any combination thereof.
[0161] Further, in various example embodiments, the example device 600 may also include at least one other circuit system, element, and interface, such as at least one I / O interface, at least one antenna element, and the like.
[0162] In various example embodiments, the circuit systems, parts, elements, and interfaces in the example device 600 including at least one processor 610 and at least one memory 620 may be coupled together in any suitable manner (e.g., electrically, magnetically, optically, electromagnetically, etc.) via any suitable connection (including but not limited to buses, beams, wires, and / or wireless lines).
[0163] It can be understood that the structure of the device on the network device 120 side is not limited to the above-mentioned example device 600.
[0164] Figure 7 A block diagram of an example apparatus 700 for MAC-CE transmission according to an example embodiment of the present disclosure is shown. The apparatus may be, for example, at least a part of a terminal device such as the UE 110 in the above example.
[0165] like Figure 7 As shown, the example apparatus 700 may include a component 710 for performing operation 310 of the example method 300 and a component 720 for performing operation 320 of the example method 400. In one or more other example embodiments, at least one I / O interface, at least one antenna element, etc. may also be included in the example apparatus 700.
[0166] In some example embodiments, examples of components in example apparatus 700 may include circuitry. For example, examples of components 710 may include circuitry configured to perform operation 310 of example method 300, and examples of components 720 may include circuitry configured to perform operation 320 of example method 300. In some example embodiments, examples of components may also include software modules and any other suitable functional entities.
[0167] Figure 8 A block diagram of an example apparatus 800 for MAC-CE transmission according to an example embodiment of the present disclosure is shown. The apparatus may be, for example, at least a portion of a network device such as the network device 120 in the above example.
[0168] like Figure 8 As shown, the example apparatus 800 may include means 810 for performing operation 410 of the example method 400. In one or more other example embodiments, at least one I / O interface, at least one antenna element, etc. may also be included in the example apparatus 800.
[0169] In some example embodiments, examples of components in the example apparatus 800 may include circuitry. For example, examples of components 810 may include circuitry configured to perform operation 410 of the example method 400. In some example embodiments, examples of components may also include software modules and any other suitable functional entities.
[0170] The term "circuitry" throughout this disclosure may refer to one or more or all of the following: (a) a hardware-only implementation of a circuit (e.g., an implementation in analog and / or digital circuitry only); (b) a combination of hardware circuitry and software, such as (if applicable) (i) a combination of analog and / or digital hardware circuitry with software / firmware and (ii) a hardware processor (including a digital signal processor) with software, any portion of software and memory that work together to enable a device such as a mobile phone or server to perform various functions); and (c) a hardware circuit and / or processor that requires software (e.g., firmware) for operation, such as a microprocessor or a portion of a microprocessor, but the software may not be present when not required for operation. This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also encompasses an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to a particular claim element, a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or networking equipment.
[0171] Another example embodiment may involve computer program code or instructions that may cause an apparatus to at least perform the above-described corresponding method. Another example embodiment may involve a computer-readable medium having such computer program code or instructions stored thereon. In some embodiments, such a computer-readable medium may include at least one storage medium in different forms, such as volatile memory and / or non-volatile memory. Volatile memory may include, but is not limited to, for example, RAM, cache, etc. Non-volatile memory may include, but is not limited to: ROM, hard disk, flash memory, etc. Non-volatile memory may also include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any combination of the above.
[0172] Unless the context clearly requires otherwise, throughout the specification and claims, the words "include", "comprises", etc. should be interpreted as inclusive meanings, contrary to exclusive or exhaustive meanings; that is, interpreted as "including but not limited to". As commonly used herein, the word "coupled" means that two or more elements can be directly connected or connected through one or more intermediate elements. Similarly, as commonly used herein, the word "connected" means that two or more elements can be directly connected or connected through one or more intermediate elements. Additionally, when used in this application, the words "herein", "above", "below" and words of similar meanings should refer to the application as a whole and do not refer to any specific part of the application. Where the context permits, the words in the description using the singular or plural may also include the plural or singular, respectively. The word "or" about a list of two or more items covers all the following interpretations of the word: any item in the list, all items in the list, and any combination of items in the list.
[0173] Furthermore, conditional language such as "may," "could," "might," "for example," "such as," and the like, as used herein, unless otherwise explicitly stated or otherwise understood in the context in which it is used, is generally intended to convey that certain embodiments include (and other embodiments do not include) certain features, elements, and / or states. Thus, such conditional language is generally not intended to imply that features, elements, and / or states are in any way required for one or more embodiments, or that one or more embodiments necessarily include logic for determining, with or without author input or prompting, whether such features, elements, and / or states are included or will be performed in any particular embodiment.
[0174] As used herein, the term "determine" (and its grammatical variations) may include at least: computing, calculating, processing, deriving, measuring, investigating, searching (e.g., searching in a table, database or other data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), obtaining, etc. Furthermore, "determining" may include solving, selecting, choosing, establishing, etc.
[0175] Although some embodiments have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the present disclosure. In fact, the devices, methods, and systems described herein may be embodied in various other forms; in addition, without departing from the spirit of the present disclosure, different omissions, substitutions, and changes in the form of the methods and systems described herein may be made. For example, although the blocks are presented in a given arrangement, alternative embodiments may perform similar design functions with different components and / or circuit topologies, and some blocks may be deleted, moved, added, subdivided, combined, and / or modified. At least one of these blocks may be implemented in a variety of different ways. The order of these blocks may also be changed. Any suitable combination of the elements and actions of some of the above-described embodiments may be combined to provide further embodiments. The attached claims and their equivalents are intended to cover such forms or modifications that fall within the scope and spirit of the present disclosure.
[0176] The abbreviations used in the specification and / or drawings are defined as follows: ACK BS Base Station DL Downlink eLCID Extended Logical Channel Identifier GEO Geosynchronous Orbit HARQ Hybrid Automatic Repeat Request LCID Logical Channel Identifier LCP Logical Channel Priority LEO Low Earth Orbit MAC-CE medium access control control element MEO Medium Earth Orbit NTN Non-Terrestrial Network RRC Radio Resource Control RTT Round Trip Time TA Timing Advance TB Transfer Block UE User Equipment UL Uplink
Claims
1. A terminal device, comprising: at least one processor; as well as at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the terminal device to execute: obtaining a transmission number configured by the network device for sending an uplink medium access control control element; and In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
2. The terminal device according to claim 1, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the terminal device to further execute: If the uplink MAC control element is sent in the hybrid automatic repeat request process of mode A, canceling the trigger event; and Further sending of the uplink medium access control control element is avoided.
3. The terminal device according to claim 1, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the terminal device to further execute: canceling the triggering event if a downlink medium access control control element confirming the decoding of the uplink medium access control control element is received from the network device; and Further sending of the uplink medium access control control element is avoided.
4. The terminal device according to claim 3, wherein the confirmation downlink medium access control control unit has a logical channel identifier or an extended logical channel identifier of the decoded confirmation that is specific to the uplink medium access control control unit.
5. The terminal device according to claim 4, wherein the logical channel identifier or the extended logical channel identifier is in a subheader of the confirmation downlink medium access control control unit, and the confirmation downlink medium access control control unit has no payload.
6. The terminal device according to claim 3, wherein the downlink medium access control control element has a reserved bit specific to the acknowledgement of the decoding of the uplink medium access control control element.
7. The terminal device according to claim 3, wherein the acknowledgment of the downlink medium access control control unit has a payload indicating the acknowledgment of decoding the uplink medium access control control unit through a bitmap.
8. The terminal device according to claim 1, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the terminal device to further execute: If the number of transmissions reaches the configured number of transmissions, the triggering event is cancelled.
9. The terminal device according to claim 8, wherein the number of transmissions is counted based on the number of initial transmissions and retransmissions of at least one transport block carrying the uplink medium access control control element.
10. The terminal device of claim 8, wherein the number of transmissions is counted based on the number of initial transmissions of at least one transport block carrying the uplink MAC control element.
11. The terminal device according to claim 1, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the terminal device to further execute: starting a timer configured by the network device for re-triggering the trigger event, and If the number of transmissions reaches the configured number of transmissions and no downlink medium access control control element confirming the decoding of the uplink medium access control control element is received from the network device before the timer expires, the triggering event is re-triggered when the timer expires.
12. The terminal device according to claim 11, wherein the timer is started at the last retransmission of the uplink medium access control control element.
13. The terminal device according to claim 11, wherein the timer is started upon initial transmission of the uplink medium access control control element.
14. The terminal device according to any one of claims 3 to 13, wherein the uplink medium access control control element is sent in the hybrid automatic repeat request process of mode B.
15. The terminal device according to any one of claims 1 to 14, wherein the transmission number is common to a plurality of uplink medium access control control elements.
16. The terminal device according to any one of claims 1 to 14, wherein the transmission number is specific to the uplink medium access control control unit.
17. A network device comprising: at least one processor; as well as at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the network device to execute: The number of transmissions configured for the terminal device to send uplink medium access control control elements, where In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
18. The network device of claim 17, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the network device to further execute: If the uplink medium access control control element is successfully decoded, a downlink medium access control control element for confirming the decoding of the uplink medium access control control element is transmitted to the terminal device.
19. The network device of claim 18, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the network device to further execute: The downlink medium access control control unit is configured.
20. The network device according to claim 18 or 19, wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the network device to further execute: configuring a timer for the terminal device to re-trigger the triggering event, If the number of transmissions reaches the number of transmissions and the terminal device does not receive the downlink medium access control control unit confirming the decoding of the uplink medium access control control unit from the network device before the timer expires, the trigger event is re-triggered when the timer expires.
21. A method performed by a terminal device, comprising: obtaining a transmission number configured by the network device for sending an uplink medium access control control element; as well as In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
22. The method according to claim 21, further comprising: If the uplink medium access control control element is sent in the hybrid automatic repeat request process of mode A, the triggering event is cancelled.
23. The method according to claim 21, further comprising: If a downlink medium access control control element is received from the network device confirming the decoding of the uplink medium access control control element, the triggering event is cancelled.
24. The method of claim 23, wherein the acknowledging downlink medium access control control element has a logical channel identifier or an extended logical channel identifier specific to the decoded acknowledgment of the uplink medium access control control element.
25. The method of claim 24, wherein the logical channel identifier or the extended logical channel identifier is in a subheader of the acknowledgment downlink medium access control control element, and the acknowledgment downlink medium access control control element has no payload.
26. The method of claim 23, wherein the downlink MAC control element has a reserved bit specific to the acknowledgment of the decoding of the uplink MAC control element.
27. The method of claim 23, wherein the acknowledging downlink MAC control element has a payload indicating the acknowledgment of decoding the uplink MAC control element via a bitmap.
28. The method of claim 21, further comprising: If the number of transmissions reaches the configured number of transmissions, the triggering event is cancelled.
29. The method of claim 28, wherein the number of transmissions is counted based on the number of initial transmissions and retransmissions of at least one transport block carrying the uplink medium access control control element.
30. The method of claim 28, wherein the number of transmissions is counted based on a number of initial transmissions of at least one transport block carrying the uplink MAC control element.
31. The method of claim 21, further comprising: starting a timer configured by the network device for re-triggering the trigger event, and If the number of transmissions reaches the configured number of transmissions and no downlink medium access control control element confirming the decoding of the uplink medium access control control element is received from the network device before the timer expires, the triggering event is re-triggered when the timer expires.
32. The method of claim 31, wherein the timer is started at the last retransmission of the uplink MAC control element.
33. The method of claim 31, wherein the timer is started upon initial transmission of the uplink MAC control element.
34. The method according to any one of claims 23 to 33, wherein the uplink medium access control control element is sent in the hybrid automatic repeat request process of mode B.
35. The method according to any one of claims 21 to 34, wherein the transmission number is common to a plurality of uplink medium access control control elements.
36. The method according to any one of claims 21 to 34, wherein the transmission number is specific to the uplink medium access control control element.
37. A method performed by a network device, comprising: The number of transmissions configured for the terminal device to send uplink medium access control control elements, where In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
38. The method of claim 37, further comprising: If the uplink medium access control control element is successfully decoded, a downlink medium access control control element for confirming the decoding of the uplink medium access control control element is transmitted to the terminal device.
39. The method of claim 38, further comprising: The downlink medium access control control unit is configured.
40. The method according to claim 38 or 39, further comprising: configuring a timer for the terminal device to re-trigger the triggering event, If the number of transmissions reaches the number of transmissions and the terminal device does not receive the downlink medium access control control unit confirming the decoding of the uplink medium access control control unit from the network device before the timer expires, the trigger event is re-triggered when the timer expires.
41. A device as a terminal device, comprising: means for obtaining a transmission number configured by a network device for sending an uplink medium access control control element; as well as A component for sending the uplink medium access control control element to the network device in a hybrid automatic repeat request process if the number of transmissions is less than the configured number of transmissions in response to a trigger event for the uplink medium access control control element.
42. An apparatus as a network device, comprising: means for configuring, for a terminal device, a transmission number for sending an uplink medium access control control element, wherein In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
43. A computer-readable medium comprising program instructions, wherein the program instructions are used to cause a terminal device to perform the following operations: obtaining a transmission number configured by the network device for sending an uplink medium access control control element; and In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
44. A computer readable medium comprising program instructions for causing a network device to perform the following operations: The number of transmissions configured for the terminal device to send uplink medium access control control elements, where In response to a trigger event for the uplink medium access control control element, if the number of transmissions is less than the configured number of transmissions, the uplink medium access control control element is sent to the network device in a hybrid automatic repeat request process.
