Patent Description:
The above information is presented as background information only, and to assist with an understanding of the disclosure. Document ""<NPL>, discloses a prioritization which is based on the priority of the grants when IchbasedPrioritization is configured and uplink grant addressed to Temporary C-RNTI or received in a RAR overlaps with configured uplink grant.

When uplink grants overlap on the time axis in an entity for which logical channel-based prioritization is configured based on priority, the terminal needs to check whether a MAC PDU is stored in the buffer and determine the radio resource to be selected for transmission accordingly.

Aspects of the disclosure are to address at least the above-mentioned problems and/or disadvantages, and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a method and apparatus for transmitting data efficiently in case that uplink grants overlap on the time axis in a mobile communication system.

It includes various specific details to assist in that understanding, but these are to be regarded as merely exemplary.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only, and not for the purpose of limiting the disclosure as defined by the appended claims.

It is to be understood that the singular forms "a," "an," and "the," include plural referents unless the context clearly dictates otherwise.

Likewise, in the drawings, some elements are exaggerated, omitted, or only outlined in brief. Also, the size of each element does not necessarily reflect the actual size. The same or similar reference symbols are used throughout the drawings to refer to the same or like parts.

Advantages and features of the disclosure and methods for achieving them will be apparent from the following detailed description of embodiments taken in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments disclosed below but may be implemented in various different ways, and the embodiments are provided only to complete the disclosure and to fully inform the scope of the disclosure to those skilled in the art to which the disclosure pertains. The disclosure is defined only by the scope of the claims. The same reference symbols are used throughout the description to refer to the same parts.

It will be appreciated that blocks of a flowchart and a combination of flowcharts may be executed by computer program instructions. These computer program instructions may be loaded on a processor of a general-purpose computer, special purpose computer, or programmable data processing equipment, and the instructions executed by the processor of a computer or programmable data processing equipment create a means for carrying out functions described in blocks of the flowchart. To implement the functionality in a certain way, the computer program instructions may also be stored in a computer usable or readable memory that is applicable in a specialized computer or a programmable data processing equipment, and it is possible for the computer program instructions stored in a non-transitory computer usable or readable memory to produce articles of manufacture that contain a means for carrying out functions described in blocks of the flowchart. As the computer program instructions may be loaded on a computer or a programmable data processing equipment, when the computer program instructions are executed as processes having a series of operations on a computer or a programmable data processing equipment, they may provide steps for executing functions described in blocks of the flowchart.

Each block of a flowchart may correspond to a module, a segment or a code containing one or more executable instructions for executing one or more logical functions, or to a part thereof. It should also be noted that functions described by blocks may be executed in an order different from the listed order in some alternative cases. For example, two blocks listed in sequence may be executed substantially at the same time or executed in reverse order according to the corresponding functionality.

Here, the word "unit," "module," or the like used in the embodiments, may refer to a software component or a hardware component such as a field programmable gate array (FPGA) or application-specific integrated circuit (ASIC) capable of carrying out a function or an operation. However, "unit" or the like is not limited to hardware or software. A unit or the like may be configured so as to reside in an addressable storage medium or to drive one or more processors. For example, units or the like may refer to components such as a software component, object-oriented software component, class component or task component, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. A function provided by a component and unit may be a combination of smaller components and units, and it may be combined with others to compose larger components and units. Components and units may be implemented to drive one or more processors in a device or a secure multimedia card.

In the following description of the disclosure, descriptions of functions and structures well known in the art may be omitted without obscuring the subject matter of the disclosure. Hereinafter, embodiments of the disclosure will be described with reference to the accompanying drawings.

<FIG> illustrates operations of a terminal that performs random access to a base station according to an embodiment of the disclosure.

Referring to <FIG>, a base station <NUM> may instruct a terminal <NUM> to perform random access (RA) when the terminal (or user equipment (UE)) performs initial attachment, or according to uplink synchronization or the need of the base station. When the terminal <NUM> needs to perform random access to the base station <NUM>, the terminal <NUM> may transmit a random access preamble (RA preamble) to the base station <NUM> at operation <NUM>.

Here, the random access preamble transmitted by the terminal <NUM> to the base station <NUM> may be a random access preamble set in advance by the base station <NUM>, and random access using such a preset random access preamble is referred to as contention-free random access (CFRA). Otherwise, terminals performing random access may share random access preambles, and a terminal may use one random access preamble available to the terminal. This random access is referred to as contention-based random access (CBRA). The base station can configure the type of random access to be used by a terminal, and if there is no random access preamble available to a terminal, the terminal may use contention-based random access.

When receiving the random access preamble transmitted by the terminal <NUM>, the base station <NUM> may calculate the time when the random access preamble has arrived and adjust the timing advance (TA) value indicating the time when the terminal <NUM> starts uplink transmission. In addition, the base station <NUM> may allocate an uplink grant so that the terminal <NUM> having transmitted the random access preamble may start data transmission. For the above-described purpose, the message transmitted by the base station to the terminal in reply to the random access preamble is called a random access response (RAR) at operation <NUM>.

The RAR message may include a timing advance value to be adjusted by the terminal, allocation information of an uplink grant that can be used by the terminal receiving the RAR to transmit data, and a temporary cell-radio network temporary identifier (temporary C-RNTI, TC-RNTI) to be used during the random access process. The uplink grant indicated by the radio resource allocation information included in the RAR message, as a resource that can be used by the terminal receiving the RAR to transmit data, is referred to as "uplink grant received in RAR.

In this case, when a message <NUM> generated for the purpose of a connection request or the like is to be transmitted in the random access process, a MAC protocol data unit (PDU) present in the message <NUM> buffer may be included in the uplink grant received in RAR and transmitted at operation <NUM>. However, when the uplink grant received in RAR is allocated, but there is no MAC PDU in the message <NUM> buffer, the terminal may generate a MAC PDU by applying a logical channel prioritization (LCP) procedure to data of another logical channel (LCH) or a medium access control-control element (MAC CE). The terminal may transmit the generated MAC PDU through the uplink grant received in RAR. If a MAC PDU present in the message <NUM> buffer is to be transmitted via the uplink grant received in RAR, the MAC PDU to be transmitted may be regarded as related to the random access process and regarded as more important information than regular data.

The base station may request retransmission due to a problem such as failure of uplink transmission using the uplink grant received in RAR. In this case, the base station may allocate a retransmission resource to the terminal by using a temporary C-RNTI included in the RAR <NUM> at operation <NUM>. The retransmission resource may be allocated by the base station to the terminal by using a downlink control information (DCI) format on the physical downlink control channel (PDCCH). Thereafter, the terminal may perform retransmission by using the allocated retransmission resource at operation <NUM>. In this way, even when data is transmitted using a temporary C-RNTI, as it may be required to transmit a MAC PDU present in the message <NUM> buffer, this uplink grant may be regarded as more important information than regular data.

In one embodiment, because the uplink grant at operation <NUM> allocated using a temporary C-RNTI is a retransmission resource of the uplink grant received in RAR, detailed operations may be described by treating the uplink grant allocated using a temporary C-RNTI as an uplink grant received in RAR.

<FIG> illustrates a scenario in which an uplink grant received in RAR overlaps with a dynamic grant according to an embodiment of the disclosure.

Referring to <FIG>, because the random access operation is triggered by a terminal or because multiple terminals share a random access preamble in contention-based random access, it is difficult for the base station to identify the terminal having transmitted a random access preamble. Hence, the base station may allocate another uplink grant to the terminal, and the uplink grant allocated by the base station may overlap with the uplink grant received in RAR on the time axis or the time and frequency axes. <FIG> shows an embodiment in which an uplink grant received in RAR <NUM> and a dynamic grant allocated with C-RNTI <NUM> overlap on a time axis.

In one embodiment, when a terminal needs to transmit only one uplink grant at the same time point in a single cell, the terminal may select one uplink grant randomly or according to a preset rule and perform transmission. The embodiment of <FIG> shows that the terminal performs transmission by selecting the uplink grant received in RAR <NUM>. Here, the uplink grant received in RAR may also include an uplink grant allocated with a temporary C-RNTI.

In this case, the terminal cannot use the uplink grant allocated with C-RNTI <NUM> overlapping with the uplink grant received in RAR <NUM> on the time axis. However, if there is another uplink grant <NUM> overlapping with the uplink grant allocated with C-RNTI <NUM>, the overlapping uplink grant <NUM> may be not prioritized (deprioritized) due to the uplink grant <NUM> that has become unusable, which may result in an uplink grant resource that cannot perform transmission. For example, if there is another uplink grant <NUM> that overlaps on the time axis or on the time and frequency axes with the uplink grant allocated with C-RNTI <NUM> that has become unusable, as the other uplink grant <NUM> is deprioritized due to the uplink grant allocated with C-RNTI <NUM> that has become unusable, a situation in which the terminal cannot perform uplink transmission through the other uplink grant <NUM> may occur.

Uplink grants allocated with C-RNTI, configured scheduling-radio network temporary identifier (CS-RNTI), or modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI) and configured grant (CG) resources, may overlap with each other in the time domain. When the uplink grants overlap, an uplink grant with a higher priority may be used. The priority value of an uplink grant may be determined to be the highest priority value of data included in a MAC PDU that is included or can be included in the uplink grant.

In the embodiment of <FIG>, as an example, it is assumed that the priority of the uplink grant allocated with C-RNTI <NUM> has a value of <NUM> and the priority of the configured grant <NUM> overlapping therewith on the time axis has a value of <NUM>. As a smaller value means a higher priority, the uplink grant allocated with C-RNTI has a higher priority. However, this uplink grant <NUM> is not used because the uplink grant received in RAR <NUM> is transmitted. Therefore, the situation in which the configured grant <NUM> is deprioritized due to the uplink grant <NUM> and cannot be used for transmission may result in waste of radio resources.

To prevent this, if there is an uplink grant that is not used because it overlaps on the time axis with the uplink grant received in RAR having been transmitted, such a resource may be ignored and considered as if the resource has not been allocated at operation <NUM>. Specifically, in the process of prioritization with other resources, such a resource may be excluded from the priority comparison with other resources overlapping on the time axis. For example, the uplink grant that is not used because it overlaps on the time axis with the uplink grant received in RAR having been transmitted may be excluded from objects of priority comparison in the process of prioritization with other resources. Then, it can be considered as if there is no uplink grant overlapping on the time axis with the configured grant having a priority value of <NUM>, and the configured grant can be transmitted if there is no other uplink grant that overlaps on the time axis with the configured grant and has a higher priority than the configured grant.

<FIG> is a flowchart illustrating operations of a terminal when an uplink grant received in RAR is selected according to an embodiment of the disclosure.

As shown in <FIG>, a certain uplink grant may overlap with the uplink grant received in RAR on the time axis or the time and frequency axes. Referring to <FIG>, the uplink grant received in RAR may overlap on the time axis with an uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI at operation <NUM>. For example, the terminal may identify that the uplink grant received in RAR overlaps on the time axis with an uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI. Here, the uplink grant received with CS-RNTI may be considered as a retransmission resource for the configured grant whose new data indicator (NDI) value of the downlink control information (DCI) is <NUM>.

If the terminal determines at operation <NUM> to perform uplink transmission by using the uplink grant received in RAR according to preset conditions or other implementation options, the terminal may ignore the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI in the subsequent uplink scheduling, multiplexing, or prioritization process. In one embodiment, the terminal may consider at operation <NUM> that the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping with the uplink grant received in RAR has not been allocated, and hence in the subsequent prioritization process, the terminal may have a result of preventing the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping with the uplink grant received in RAR from becoming a prioritized uplink grant.

In one embodiment, the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping with the uplink grant received in RAR may be excluded from the subsequent uplink scheduling, multiplexing, or prioritization process. According to an embodiment, upon determining to perform transmission using the uplink grant received in RAR, the terminal may regard the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping with the uplink grant received in RAR as a deprioritized uplink grant.

As another embodiment, if the terminal determines at operation <NUM> not to perform uplink transmission by using the uplink grant received in RAR, the terminal may determine to perform transmission by using the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI. In this case, the terminal may consider at operation <NUM> that the uplink grant received in RAR and overlapping on the time axis with the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI has not been allocated and may ignore it in the subsequent uplink scheduling, multiplexing, or prioritization process. According to an embodiment, the terminal may consider that the uplink grant received in RAR has not been allocated, and hence in the subsequent prioritization process, the terminal may have a result of preventing the uplink grant received in RAR and overlapping on the time axis with the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI from becoming a prioritized uplink grant.

In one embodiment, the uplink grant received in RAR and overlapping on the time axis with the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI may be excluded from the subsequent uplink scheduling, multiplexing, or prioritization process. According to an embodiment, the terminal may regard the uplink grant received in RAR and overlapping on the time axis with the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI as a deprioritized uplink grant.

<FIG> illustrates a problem that may occur when an uplink grant received in RAR is not used according to an embodiment of the disclosure.

Referring to <FIG>, because the random access operation is triggered by a terminal or because multiple terminals share a random access preamble in contention-based random access, it is difficult for the base station to identify the terminal having transmitted a random access preamble. Hence, the base station may allocate another uplink grant to the terminal, and the uplink grant allocated by the base station may overlap with the uplink grant received in RAR on the time axis or the time and frequency axes. <FIG> shows an embodiment in which the uplink grant received in RAR <NUM> and the dynamic grant allocated with C-RNTI <NUM> overlap on a time axis. Here, the uplink grant received in RAR may also include an uplink grant allocated with a temporary C-RNTI.

In one embodiment, when a terminal needs to transmit only one uplink grant at the same time point in a single cell, the terminal may select one uplink grant randomly or according to a preset rule and perform transmission. The embodiment of <FIG> shows that the terminal performs transmission by selecting the uplink grant allocated with C-RNTI <NUM>.

In this case, the terminal cannot use the uplink grant received in RAR <NUM>. When a message <NUM> generated for the purpose of a connection request or the like is to be transmitted in the random access process, a MAC PDU present in the message <NUM> buffer may be included in the uplink grant received in RAR and transmitted. However, when the uplink grant received in RAR is allocated, but there is no MAC PDU in the message <NUM> buffer, the terminal may generate a MAC PDU by applying a logical channel prioritization procedure to data of another logical channel or a MAC CE. The terminal may transmit the generated MAC PDU through the uplink grant received in RAR. If a MAC PDU present in the message <NUM> buffer is to be transmitted via the uplink grant received in RAR, the MAC PDU present in the message <NUM> buffer may be regarded as related to the random access process and regarded as more important information than regular data. Likewise, when data is transmitted using a temporary C-RNTI, as it may be required to transmit a MAC PDU present in the message <NUM> buffer, this uplink grant may be regarded as more important information than regular data.

However, as described above, when the terminal selects the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI without selecting the uplink grant received in RAR, the MAC PDU in the message <NUM> buffer may be not transmitted. If the MAC PDU in the message <NUM> buffer cannot be transmitted, this may cause a delay in the random access operation, and thus the quality of wireless communication may be degraded. Accordingly, a method of transmitting the MAC PDU present in the message <NUM> buffer without delay may be required. To this end, when determining the priority of the uplink grant, the terminal may assign a higher priority to the message <NUM> compared to data of other logical channels. In this case, when the uplink grant received in RAR overlaps with other uplink grants on the time axis or the time and frequency axes, the uplink grant received in RAR may become a prioritized uplink grant due to the message <NUM>. Uplink transmission may be actually performed by using the resource corresponding to the prioritized uplink grant.

<FIG> is a flowchart illustrating a method for a terminal to transmit a MAC PDU present in a message <NUM> buffer according to an embodiment of the disclosure.

Referring to <FIG>, if the MAC PDU in the message <NUM> buffer needs to be transmitted through the uplink grant received in RAR, the uplink grant received in RAR needs to be transmitted. In the embodiment of <FIG>, it is assumed that in a MAC entity in which logical channel-based prioritization is configured based on the highest priority of a logical channel included or to be included in an uplink grant, the uplink grant received in RAR overlaps on the time axis with the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI at operation <NUM>. For example, the terminal may identify that the uplink grant received in RAR overlaps on the time axis with the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI. In this case, the terminal needs to check whether a MAC PDU is stored in the message <NUM> buffer and determine the radio resource to be selected for transmission correspondingly at operation <NUM>.

If a MAC PDU is stored in the message <NUM> buffer, to transmit the MAC PDU in the message <NUM> buffer, the terminal may select the uplink grant received in RAR to perform transmission. In one embodiment, the terminal may perform transmission of the uplink grant received in RAR by considering the uplink grant received in RAR as a prioritized uplink grant at operation <NUM>. This is because if the operation <NUM> is not performed, data to which the message <NUM> belongs is given a lower priority than other uplink grants overlapping on the time axis in the prioritization process and may be not transmitted.

Then, the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping with the uplink grant received in RAR may be ignored in the subsequent uplink scheduling, multiplexing, or prioritization process. In one embodiment, the terminal may consider at operation <NUM> that the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR has not been allocated, and hence in the subsequent prioritization process, the terminal may have a result of preventing the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR from becoming a prioritized uplink grant.

In one embodiment, the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI may be ignored in the subsequent uplink scheduling, multiplexing, or prioritization process. In one embodiment, upon determining to perform transmission using the uplink grant received in RAR, the terminal may regard the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR as a deprioritized uplink grant. In addition, the terminal may transmit at operation <NUM> the uplink grant received in RAR including the MAC PDU stored in the message <NUM> buffer. Here, if the size of the uplink grant does not match the size of the MAC PDU in the message <NUM> buffer (the size of the MAC PDU is somewhat larger), the terminal may exclude the MAC CE or the like among the MAC PDU stored in the message <NUM> buffer and include the remaining portion of the MAC PDU matching the size of the uplink grant.

If no MAC PDU is stored in the message <NUM> buffer at operation <NUM>, the message <NUM> may not have to be transmitted first. Hence, the MAC entity of the terminal may perform transmission by selecting at operation <NUM> one of the uplink grant received in RAR and the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI according to a preset prioritization rule. In addition, the unselected uplink grant overlapping on the time axis may be considered to be unallocated and may be ignored in the uplink scheduling, multiplexing, or prioritization process.

According to an embodiment, the terminal may consider at operation <NUM> that the unselected uplink grant has not been allocated, and hence in the subsequent prioritization process, the terminal may have a result of preventing the unselected uplink grant from becoming a prioritized uplink grant. In one embodiment, the unselected uplink grant may be excluded from the subsequent uplink scheduling, multiplexing, or prioritization process. According to an embodiment, the terminal may regard the unselected uplink grant as a deprioritized uplink grant.

Referring to <FIG>, if the MAC PDU in the message <NUM> buffer needs to be transmitted via the uplink grant received in RAR, the uplink grant received in RAR needs to be transmitted. In the embodiment of <FIG>, it is assumed that in a MAC entity in which logical channel-based prioritization is configured based on the highest priority of a logical channel included or to be included in an uplink grant, the uplink grant received in RAR overlaps on the time axis with the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI at operation <NUM>.

In this case, the MAC entity of the terminal may perform at operation <NUM> processing by prioritizing the uplink grant received in RAR. As a MAC PDU may be stored in the message <NUM> buffer, there is an effect that the transmission priority is given to the uplink grant received in RAR. In one embodiment, the terminal may perform transmission of the uplink grant received in RAR by considering the uplink grant received in RAR as a prioritized uplink grant. It is proposed to prioritize and process the uplink grant received in RAR at operation <NUM>, but in an embodiment, only the uplink grant allocated with a temporary C-RNTI may be prioritized and processed.

Then, the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR may be ignored in the subsequent uplink scheduling, multiplexing, or prioritization process. In one embodiment, the terminal may consider at operation <NUM> that the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR has not been allocated, and hence in the subsequent prioritization process, the terminal may have a result of preventing the uplink grant received with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR from becoming a prioritized uplink grant. In one embodiment, the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI may be ignored in the subsequent uplink scheduling, multiplexing, or prioritization process. In one embodiment, upon determining to perform transmission using the uplink grant received in RAR, the terminal may regard the uplink grant allocated with C-RNTI (or MCS-C-RNTI) or CS-RNTI and overlapping on the time axis with the uplink grant received in RAR as a deprioritized uplink grant.

In addition, if there is a MAC PDU in the message <NUM> buffer, the terminal may include the MAC PDU stored in the message <NUM> buffer in the uplink grant received in RAR and perform transmission at operation <NUM>. Here, if the size of the uplink grant does not match the size of the MAC PDU in the message <NUM> buffer (the size of the MAC PDU is somewhat larger), the terminal may exclude the MAC CE or the like among the MAC PDU stored in the message <NUM> buffer and include the remaining portion of the MAC PDU matching the size of the uplink grant. Otherwise, if there is no MAC PDU in the message <NUM> buffer, the terminal may obtain a MAC PDU from the multiplexing and assembly entity and perform transmission.

<FIG> is a flowchart illustrating a method for a terminal to handle a configured grant resource that overlaps on a time axis with an uplink grant received in RAR according to an embodiment of the disclosure.

Referring to <FIG>, because the configured grant resource transmitted in the uplink may be a preconfigured periodic resource, if the configured grant resource overlaps on the time axis with the uplink grant received in RAR in the MAC entity in which logical channel-based prioritization is configured, the terminal may have to use the uplink grant received in RAR that is recently configured. Although the embodiment of <FIG> shows that the uplink grant received in RAR overlaps on the time axis with a dynamic grant, the configured grant other than a dynamic grant may also overlap on the time axis with an uplink grant received in RAR.

In the embodiment of <FIG>, a configured grant resource may be allocated in the MAC entity in which logical channel-based prioritization is configured based on the highest priority of a logical channel included in or to be included in the uplink grant at operation <NUM>. The terminal may check at operation <NUM> whether the configured grant and the uplink grant received in RAR overlap on the time axis. If the configured grant and the uplink grant received in RAR overlap on the time axis, the terminal may ignore at operation <NUM> the configured grant resource without configuring the configured grant resource. For example, the terminal may perform transmission with a recognition that there is no configured grant resource. In addition, for example, the terminal may not consider this configured grant resource in other prioritization operations. Accordingly, even if this configured grant resource overlaps on the time axis with another uplink grant or scheduling request (SR) transmission, it is possible to prevent the occurrence of a problem that the transmission of another uplink grant or scheduling request is deprioritized due to this configured grant. The uplink grant received in RAR at operation <NUM> may include an uplink grant allocated with a temporary C-RNTI.

If the configured grant and the uplink grant received in RAR do not overlap on the time axis at operation <NUM>, this may mean that the configured grant is usable. Hence, the HARQ (hybrid automatic repeat request) process ID set in the PUSCH (physical uplink shared channel) for this configured grant can be set at operation <NUM> to the HARQ process ID of the configured grant resource. For example, the terminal may set the HARQ process ID for this configured grant to HARQ process ID #<NUM>.

In addition, if ConfiguredGrantTimer is not running, the terminal may consider at operation <NUM> that the new data indicator (NDI) has been toggled and may prepare for configured grant transmission by transferring information related to the configuration information of the configured grant from the MAC entity to the HARQ entity.

Thereafter, the terminal may determine at operation <NUM> the priority of the uplink grant corresponding to the configured grant, and may determine whether this uplink grant is a prioritized uplink grant or a deprioritized uplink grant. A prioritized uplink grant may mean that it can be actually transmitted, but a deprioritized uplink grant may mean that it will be not transmitted.

<FIG> illustrates a scenario in which an uplink grant received in RAR overlaps with SR transmission according to an embodiment of the disclosure.

Referring to <FIG>, because the random access operation is triggered by a terminal or because multiple terminals share a random access preamble in contention-based random access, it is difficult for the base station to identify the terminal having transmitted a random access preamble. Hence, the base station may allocate a PUCCH (physical uplink control channel) resource for transmitting a scheduling request (SR) message to the terminal, and the PUCCH resource through which the terminal intends to perform SR transmission may overlap on the time axis with the uplink grant received in RAR.

The embodiment of <FIG> shows that the uplink grant received in RAR <NUM> and the SR transmission <NUM> overlap on a time axis. As the PUCCH transmission including the SR and the PUSCH transmission corresponding to the uplink grant received in RAR cannot occur simultaneously at the same time in the MAC entity, the RAR resource through which a message <NUM> can be transmitted needs to be transmitted first.

The embodiment of <FIG> shows that the terminal selects the uplink grant received in RAR <NUM> to perform transmission. Here, the uplink grant received in RAR may also include an uplink grant allocated with a temporary C-RNTI. In this case, the terminal cannot perform SR transmission <NUM> that overlaps on the time axis with the uplink grant received in RAR. However, if there is another uplink grant overlapping on the time axis with the SR transmission inside the MAC entity, this overlapping uplink grant may be deprioritized due to the uplink grant of the SR transmission that has become unusable, generating an uplink grant resource through which transmission cannot be performed.

The SR transmission resource may overlap in the time domain with an uplink grant allocated with C-RNTI, configured scheduling-radio network temporary identifier (CS-RNTI), or modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI) or a configured grant (CG) resource within the cell group configured in the MAC entity, and the terminal may compare the priority of the logical channel having triggered the SR with the priority of other uplink grants, where one with a higher priority among SR transmission and other uplink grants may be actually used for transmission. The priority value of an uplink grant may be determined to be the highest priority value of data included in a MAC PDU that is included or may be included in the uplink grant.

In the embodiment of <FIG>, the SR transmission <NUM> overlaps on the time axis with the uplink grant received in RAR <NUM>, in which case the uplink grant received in RAR may be transmitted. When the uplink grant received in RAR is transmitted, this SR transmission <NUM> may cause another uplink grant <NUM> overlapping on the time axis not to be prioritized and not to be used for transmission. The occurrence of a situation in which another uplink grant is deprioritized and cannot be used for transmission due to the SR transmission <NUM> that is not performed in such a way may result in waste of radio resources. To prevent this, if there is SR transmission that is not performed because it overlaps on the time axis with the uplink grant received in RAR having been transmitted, the terminal may ignore at operation <NUM> such SR transmission and consider as if the SR transmission has not occurred.

Specifically, in the process of prioritization with other uplink grants, the terminal may exclude such SR transmission that is not performed from priority comparison with the other uplink grants overlapping on the time axis. Hence, even if there is another uplink grant overlapping on the time axis with the SR transmission having been excluded from priority comparison, the other uplink grant can be transmitted. However, the uplink grant received in RAR <NUM> and the other uplink grant <NUM> cannot be transmitted simultaneously in the same cell, but can be transmitted simultaneously if they are resources allocated to different cells.

<FIG> is a flowchart illustrating a method for a terminal to handle SR transmission that overlaps on a time axis with an uplink grant received in RAR according to an embodiment of the disclosure.

Referring to <FIG>, if SR transmission transmitted in the uplink overlaps on the time axis with the uplink grant received in RAR, it may be required to use the uplink grant received in RAR according to the possibility of transmitting a MAC PDU present in the message <NUM> buffer. The embodiment of <FIG> shows that the uplink grant received in RAR overlaps with the SR transmission on the time axis.

In the embodiment of <FIG>, it can be assumed that SR transmission is triggered in a MAC entity in which logical channel-based prioritization is configured based on the highest priority of a logical channel included in or to be included in an uplink grant at operation <NUM>. For example, a terminal may identify that SR transmission is triggered in a MAC entity in which logical channel-based prioritization is configured based on the highest priority of a logical channel included or to be included in an uplink grant. However, this logical channel-based prioritization may be considered as the configuration indicating prioritization operation between uplink grants, and may be applied in the same way even when a separate configuration indicating prioritization of SR transmission and uplink grants is set. For example, logical channel-based prioritization may be applied in the same way even when separate information indicating prioritization of SR transmission and uplink grants is configured in the terminal.

The terminal may check at operation <NUM> whether the SR transmission and the uplink grant received in RAR overlap on the time axis within the MAC entity. If the SR transmission and the uplink grant received in RAR overlap on the time axis within the MAC entity, the terminal may deprioritize at operation <NUM> the SR transmission and ignore the SR transmission, and transmit the uplink grant received in RAR at operation <NUM>. As a result, even if the SR transmission that is not actually performed overlaps with another uplink grant on the time axis, it is possible to prevent the occurrence of a problem that the other uplink grant is deprioritized due to the SR transmission that is not actually performed. In addition, the uplink grant received in RAR at operation <NUM> may include an uplink grant allocated with a temporary C-RNTI.

If the SR transmission and the uplink grant received in RAR does not overlap on the time axis at operation <NUM>, this may mean that the SR transmission can be actually performed. However, only when the value of SR_COUNTER indicating the number of SR transmission attempts is less than a preset threshold sr-TransMax at operation <NUM>, may the terminal increment SR_COUNTER by <NUM> and the MAC entity may instruct the physical layer to perform SR transmission with the corresponding PUCCH resource. Additionally, the terminal may start sr-ProhibitTimer to prevent repetitive SR transmission at operation <NUM>.

If the value of SR_COUNTER is equal to sr-TransMax, as it is no longer possible to perform SR transmission, the terminal may notify at operation <NUM> the RRC layer to release PUCCH resources and SR resources of all serving cells. Also, the terminal may release at operation <NUM> PUSCH resources for all uplink configured grants, downlink semi-persistent scheduling (SPS), and semi-persistent channel status information (CSI) reporting. Then, the UE may cancel at operation <NUM> all pending SR transmissions and initiate a random access operation in the special cell (SpCell).

<FIG> is a block diagram illustrating a structure of a terminal according to an embodiment of the disclosure.

Referring to <FIG>, a terminal may include a transceiver <NUM>, a controller <NUM>, and storage <NUM>. In the disclosure, the controller <NUM> may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

The transceiver <NUM> may transmit and receive signals to and from another network entity. For example, the transceiver <NUM> may receive system information from a base station and may receive a synchronization signal or a reference signal.

The controller <NUM> may control the overall operation of the terminal according to embodiments proposed in the disclosure. For example, the controller <NUM> may control signal flows between blocks to execute operations according to the above-described flowcharts.

Specifically, the controller <NUM> may be configured to identify whether a medium access control (MAC) entity of the terminal is configured with a logical channel (LCH) - based prioritization, identify whether a first uplink grant is associated with a random access, in case that the MAC entity is configured with the LCH - based prioritization, determine to consider the first uplink grant as a prioritized uplink grant, in case that the first uplink grant is associated with the random access, and transmit, via the transceiver <NUM>, an uplink signal based on the prioritized uplink grant.

The storage <NUM> may store at least one of information transmitted and received through the transceiver <NUM> or information generated through the controller <NUM>.

<FIG> is a block diagram illustrating a structure of a base station according to an embodiment of the disclosure.

Referring to <FIG>, a base station may include a transceiver <NUM>, a controller <NUM>, and storage <NUM>. In the disclosure, the controller <NUM> may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

The transceiver <NUM> may transmit and receive signals to and from another network entity. For example, the transceiver <NUM> may transmit system information to a terminal and may transmit a synchronization signal or a reference signal.

The controller <NUM> may control the overall operation of the base station according to embodiments proposed in the disclosure. For example, the controller <NUM> may control signal flows between blocks to execute operations according to the above-described flowcharts.

Specifically, when a terminal needs to perform random access to the base station, the controller <NUM> may control the transceiver <NUM> to receive a random access preamble (RA preamble) from the terminal and may control the transceiver <NUM> to transmit a random access response (RAR) to the terminal. For example, the RAR message may include a timing advance value to be adjusted by the terminal, allocation information of an uplink grant that can be used by the terminal receiving the RAR to transmit data, and a temporary cell-radio network temporary identifier (C-RNTI) to be used during the random access process.

Claim 1:
A method performed by a terminal in a wireless communication system, the method comprising:
identifying that a scheduling request, SR, is triggered (<NUM>);
identifying whether a resource for an SR transmission associated with the triggered SR overlaps with an uplink grant received in a random access response, RAR, in case that the SR is triggered and a medium access control, MAC, entity of the terminal is configured with a logical channel, LCH,-based prioritization (<NUM>);
identifying whether a counter for the SR transmission is less than a threshold for SR, in case that the resource for the SR transmission does not overlap with the uplink grant received in the RAR (<NUM>); and
transmitting the SR based on the resource for the SR transmission, in case that the counter for the SR transmission is less than the threshold for SR (<NUM>).