KR102283839B1 - Method and Apparatus for Sending Dynamic Scheduling Request for Uplink Data Transmission - Google Patents

Abstract

Disclosed are a method and apparatus for requesting dynamic scheduling for uplink data transmission.
According to an aspect of the present invention, in a method for requesting dynamic scheduling of a terminal for uplink data transmission, the terminal configures SR resources for each logical channel through RRC configuration with a base station, and the SR resources are in a plurality of buffer states. Including an index, the PUSCH resource range is divided for each buffer state index, and the dynamic scheduling request method includes: measuring an uplink data size; selecting a buffer status index based on the uplink data size and the PUSCH resource range; transmitting the SR of the selected index to the base station; receiving an uplink grant determined according to the SR of the selected index from the base station; and transmitting the uplink data to the base station using the PUSCH resource allocated by the uplink grant.

Description

Method and apparatus for requesting dynamic scheduling for uplink data transmission {Method and Apparatus for Sending Dynamic Scheduling Request for Uplink Data Transmission}

Embodiments of the present invention relate to a method and apparatus for a terminal requesting scheduling from a base station to transmit uplink data to a base station in a 5G new radio (NR) system.

The content described in this section merely provides background information on the present invention and does not constitute the prior art.

The 5G mobile communication system supports enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications.

In the 5G mobile communication system, in order to minimize data transmission/reception time and maximize resource utilization, a method of transmitting and receiving data through a resource allocation process based on base station scheduling is used.

Specifically, in order for the terminal to transmit uplink data, a physical uplink shared channel (PUSCH) resource must be allocated by transmitting a scheduling request (SR) to the base station and receiving an uplink grant (UL grant) from the base station. . That is, the base station transmits an uplink grant including PUSCH resource information set arbitrarily to the terminal, and the terminal transmits uplink data to the base station using the PUSCH resource.

However, since the base station does not know the size of uplink data to be transmitted by the terminal, there is a problem that the base station must arbitrarily determine the PUSCH resource to be allocated to the terminal.

In this case, when the size of uplink data to be transmitted by the terminal is larger than the PUSCH resource allocated from the base station, the terminal has to perform a buffer status reporting (BSR) process, so that there is a problem in that the uplink data transmission is delayed.

On the other hand, when the size of uplink data that the terminal intends to transmit is larger than the PUSCH resource allocated from the base station, the terminal transmits uplink data to the base station using more resources than the PUSCH resources required for uplink data transmission, so the resource utilization rate is low. has a problem.

Therefore, the base station needs to set the PUSCH resource allocation differently according to the size of uplink data that the terminal intends to transmit to the base station.

Meanwhile, it is necessary to reduce communication delay time or increase data transmission reliability by changing the uplink approval procedure of the base station according to the type of service supported by the uplink data that the terminal intends to transmit to the base station.

In the embodiments of the present invention, in a 5G mobile communication system, a terminal receives an uplink grant determined without considering an uplink data size from a base station to reduce time delay or resource utilization reduction due to an additional procedure, uplink data A main object of the present invention is to provide a scheduling request method in consideration of size and an apparatus therefor.

Another embodiment of the present invention provides a scheduling request method capable of reducing communication delay time or increasing data transmission reliability by changing an uplink approval procedure of a base station according to a service type of uplink data that a terminal intends to transmit to a base station, and It has one purpose to provide the device.

According to an aspect of the present invention, in a method for requesting dynamic scheduling of a terminal for uplink data transmission, the terminal configures SR resources for each logical channel through RRC configuration with a base station, and the SR resources are in a plurality of buffer states. Including an index, the PUSCH resource range is divided for each buffer state index, and the dynamic scheduling request method includes: measuring an uplink data size; selecting a buffer status index based on the uplink data size and the PUSCH resource range; transmitting the SR of the selected index to the base station; receiving an uplink grant determined according to the SR of the selected index from the base station; and transmitting the uplink data to the base station using the PUSCH resource allocated by the uplink grant.

According to another aspect of this embodiment, there is provided a terminal for transmitting a dynamic scheduling request for uplink data transmission to a base station, comprising: a memory; a communication unit for communicating with the base station; and a processor, wherein the SR resource configured for each logical channel through RRC configuration with the base station is stored in the memory, the SR resource includes a plurality of buffer status indexes, and a PUSCH resource range is divided for each buffer status index. , the processor measures the uplink data size, selects a buffer state index based on the uplink data size and the PUSCH resource range, transmits the SR of the selected index to the base station, and according to the SR of the selected index Provided is a terminal configured to receive the determined uplink grant from the base station, and transmit the uplink data to the base station by using the PUSCH resource allocated by the uplink grant.

As described above, according to an embodiment of the present invention, the terminal transmits an SR to the base station using a different scheduling request (SR) according to the uplink data size, and receives resources from the base station according to the uplink data size. By being allocated, it is possible to reduce time delay or resource waste due to uplink resource allocation.

According to another embodiment of the present invention, by changing the uplink approval procedure of the base station according to the type of service supported by the uplink data that the terminal intends to transmit to the base station, communication delay time can be reduced or data transmission reliability can be increased.

1 is a diagram for explaining a structure of a radio interface protocol for a control plane between a terminal, a base station, and a 5GC in a wireless communication system.
2 shows the structure of an uplink subframe in a wireless communication system.
3A and 3B are diagrams illustrating an uplink resource allocation process of a terminal in a wireless communication system.
4 is a diagram for explaining a scheduling request method of a terminal according to an embodiment of the present invention.
5 illustrates a block diagram of a terminal and a base station according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

In addition, in describing the components of the present invention, terms such as first, second, A, B, (a), (b), etc. may be used. These terms are only for distinguishing the components from other components, and the essence, order, or order of the components are not limited by the terms. Throughout the specification, when a part 'includes' or 'includes' a certain component, it means that other components may be further included, rather than excluding other components, unless otherwise stated. . In addition, terms such as '~ unit' and 'module' described in the specification mean a unit that processes at least one function or operation, which may be implemented as hardware or software or a combination of hardware and software.

In this specification, the base station has a meaning as a terminal node of a network that directly communicates with the terminal. A specific operation described as being performed by the base station in this document may be performed by an upper node of the base station in some cases. That is, it is obvious that various operations performed for communication with the terminal in a network including a plurality of network nodes including the base station may be performed by the base station or other network nodes other than the base station. 'Base station (BS: Base Station)' is a term such as gNB (g-NodeB), fixed station (fixed station), NodeB, eNB (evolved-NodeB), BTS (base transceiver system), access point (AP: Access Point), etc. can be replaced by In addition, 'terminal' may be fixed or have mobility, UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS ( Advanced Mobile Station), wireless terminal (WT), machine-type communication (MTC) device, machine-to-machine (M2M) device, device-to-device (D2D) device, and the like.

Hereinafter, downlink (DL: downlink) means communication from a base station to a terminal, and uplink (UL: uplink) means communication from a terminal to a base station. In the downlink, the transmitter may be a part of the base station, and the receiver may be a part of the terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of the base station.

Specific terms used in the following description are provided to help the understanding of the present invention, and the use of these specific terms may be changed to other forms without departing from the technical spirit of the present invention.

Meanwhile, embodiments of the present invention may be supported by standard documents disclosed in at least one of IEEE 802, 3GPP, and 3GPP2, which are wireless access systems. That is, steps or parts not described in order to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in this document may be explained by the standard document.

1 is a diagram for explaining a structure of a radio interface protocol for a control plane between a terminal, a base station, and a 5GC in a wireless communication system.

Referring to FIG. 1 , the 5G system includes a terminal 100 , a base station 110 , and a 5G core network 120 , and a radio interface protocol structure for a control plane between nodes is illustrated. Here, the control plane means a path through which control messages used by the terminal 100 , the base station 110 , and the 5G core network 120 to manage a call are transmitted.

The layers of the air interface protocol between the terminal 100 and the base station 110 are first based on the lower three layers of the well-known open system interconnection (OSI) standard model known in the art of communication systems. It may be divided into a layer (L1), a second layer (L2), and a third layer (L3).

The first layer is a physical layer (PHY), the second layer is a data link layer, and the third layer is a network layer.

A physical layer (PHY), which is the first layer (L1), provides an information transfer service to a higher layer by using a physical channel. The physical layer is connected to a medium access control (MAC) layer located at a higher level through a transport channel, and data is transmitted between the MAC layer and the physical layer through the transport channel.

The physical layer transmits data using a physical control channel, and the types of physical control channels include a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), and a physical uplink channel. It includes a link shared channel (PUSCH: physical uplink shared channel).

The PDCCH allocates resources of a downlink shared channel (DL-SCH) to the terminal 100 . The PDCCH may carry an uplink grant (UL grant) informing the UE of resource allocation of uplink transmission.

The PUCCH carries uplink control information such as a scheduling request, HARQ ACK/NACK for downlink transmission, and channel quality indicator (CQI). The terminal 100 allocated with the PUCCH resource may transmit a scheduling request or a buffer status reporting (BSR) to the base station by using the PUCCH resource.

PUSCH allocates PUSCH resources to the UE 100 . The terminal 100 allocated with the PUSCH resource may transmit uplink data to the base station 110 by using the PUSCH resource.

Meanwhile, the MAC layer of the second layer (L2) is a layer that provides a service to a radio link control (RLC) layer, which is an upper layer, through a logical channel. A packet data convergence protocol (PDCP) layer is a layer that performs user data transfer, header compression, and ciphering functions in a user plane.

A radio resource control (RRC) layer of the third layer (L3) is a layer of the control plane and serves to control radio resources between the terminal 100 and the base station 110 . To this end, the terminal 100 and the base station 110 exchange RRC messages with each other through the RRC layer.

The RRC layer controls a logical channel, a transport channel, and a physical channel in relation to configuration, re-configuration, and release of radio bearers. Here, the radio bearer means a logical path provided by the second layer (L2) for data transmission between the terminal and the network. Establishing a radio bearer means defining the characteristics of a radio protocol layer and channel to provide a specific service, and setting each specific parameter and operation method.

Specifically, through RRC message exchange between the terminal 100 and the base station 110 , an SR resource may be configured for each logical channel. Here, the SR resource includes at least one of an SR period, SR subframe offset information, or a PUCCH resource.

2 shows the structure of an uplink subframe in a wireless communication system.

Referring to FIG. 2 , an uplink subframe may be divided into a control region and a data region in the frequency domain. A PUCCH carrying uplink control information is allocated to the control region. The data area is allocated a PUSCH carrying user data. The PUCCH resource is configured by a SchedulingRequestConfig information element transmitted through a Radio Resource Control (RRC) message (eg, an RRC connection reconfiguration message).

When indicated by a higher layer, the UE may support simultaneous transmission of PUSCH and PUCCH. A resource block pair is allocated to a PUCCH or PUSCH for one UE in a subframe.

The base station can adjust the data rate by transmitting an uplink grant by setting resource blocks of PUSCH resources allocated to the terminal differently. That is, as the number of resource blocks of PUSCH resources allocated by the base station to the terminal increases, the transmission rate of uplink data transmitted by the terminal to the base station increases.

3A and 3B are diagrams illustrating an uplink resource allocation process of a terminal in a wireless communication system.

The 5G system uses a data transmission/reception method based on the base station's scheduling to maximize resource utilization. This means that, when there is data to be transmitted, the terminal first requests the uplink resource allocation from the base station, and can transmit data using only the uplink resource allocated from the base station.

In order to efficiently use uplink radio resources, the base station needs to know what type of data to transmit on the uplink and by how much for each terminal. Accordingly, the terminal directly transmits information about uplink data it wants to transmit to the base station, and the base station can allocate uplink resources to the corresponding terminal based on the information. In this case, the information on the uplink data transmitted by the terminal to the base station is the amount of uplink data stored in its buffer, and is referred to as a buffer status report (BSR).

Referring to FIG. 3A , when the terminal 100 is allocated a PUSCH resource smaller than the uplink data size from the base station 110 , a process of performing a buffer status reporting (BSR) procedure is exemplified.

The terminal 100 and the base station 110 preset SR resources through RRC message exchange. Here, the SR resource may include an SR periodicity, SR subframe offset information, and a PUCCH resource.

The terminal 100 transmits a scheduling request (SR) to the base station 110 in order to transmit uplink data to the base station 110 (S300). The terminal 100 may transmit the SR to the base station 110 using the PUCCH resource allocated from the base station 110 .

The base station 110 receiving the SR from the terminal 100 transmits an uplink grant (UL grant) to the terminal 100 (S302). The base station 110 may allocate a PUSCH resource to the terminal 100 through uplink grant. However, since the base station 110 cannot know the size of uplink data that the terminal 100 intends to transmit, it has no choice but to allocate an arbitrarily set PUSCH resource to the terminal 100 .

When the PUSCH resource allocated from the base station 110 is smaller than the uplink data size, the terminal 100 transmits a BSR to the base station 110 for additional resource allocation (S304). Here, the BSR includes information on the size of uplink data that the terminal 100 intends to transmit to the base station 110 .

The base station 110 confirms the size of data to be transmitted in the uplink by the terminal 100 through the BSR, and transmits an uplink grant for the PUSCH resource corresponding to the uplink data size to the terminal 100 (S306).

The terminal 100 transmits uplink data to the base station 110 by using the PUSCH resource allocated from the base station 110 (S308).

As a result, when the base station 110 allocates a PUSCH resource to the terminal 100 without considering the size of the uplink data, the BSR procedure must be additionally performed, so that the uplink data transmission of the terminal 100 may be delayed. there is.

Referring to FIG. 3B , when the terminal 100 is allocated a PUSCH resource larger than the uplink data size from the base station 110 , a process of performing the BSR procedure is exemplified.

The terminal 100 transmits an SR to the base station 110 in order to transmit uplink data to the base station 110 (S310).

The base station 110 transmits an uplink grant to the terminal 100 to allocate an arbitrarily set PUSCH resource (S312).

When the PUSCH resource allocated from the base station 110 is larger than the size of the uplink data, the terminal 100 transmits the uplink data to the base station 110 by using the PUSCH resource.

In this case, since the base station 110 allocates more PUSCH resources than the uplink data size to the terminal 100, resource loss occurs by the difference between the uplink data and the PUSCH resources. Accordingly, when the base station 110 allocates the PUSCH resource to the terminal 100 without considering the size of uplink data, the PUSCH resource may be wasted.

4 is a diagram for explaining a scheduling request method of a terminal according to an embodiment of the present invention.

The terminal according to an embodiment of the present invention configures an SR resource for each logical channel through RRC configuration with the base station. Here, the SR resource according to an embodiment of the present invention includes a plurality of buffer status indexes, and at least one of SR periodicity, SR sub-frame offset information, or PUCCH resources. may further include.

Table 1 is an example of SR resources configured according to an embodiment of the present invention.

logical channel SR resource buffer state index SR cycle SR subframe offset information PUCCH Resources One 0 One 2 3 2 One 4 5 6 3 2 4 5 7

Referring to Table 1, each number is only an example that does not consider a unit, but is not limited thereto. According to an embodiment of the present invention, an SR resource is configured for each logical channel, and at least one of an SR period, SR subframe offset information, or PUCCH resource may be differently configured for each buffer status index. For example, the values of the SR period, SR subframe offset information, and PUCCH resource of buffer state index 0 are 1, 2, and 3, respectively, and the values of the SR period, SR subframe offset information and PUCCH resource of buffer state index 1 are It is 4, 5, 6. In other words, the buffer status index is distinguished according to the SR period, SR subframe offset information, and the value of the PUCCH resource. The base station may recognize the buffer status index by receiving the SR according to the SR period, SR subframe offset information, and PUCCH resource, and may determine the PUSCH resource range according to the buffer status index. For example, when the base station receives an SR having an SR period, SR subframe offset information, and PUCCH resources of 4, 5, and 7, respectively, it is determined that the buffer status index is 2.

The buffer status index is a criterion for dividing the PUSCH resource range. That is, PUSCH resource ranges are divided for each buffer status index, and the UE transmits to the base station the SR of the buffer status index corresponding to the PUSCH resource range including the uplink data size, and the base station transmits the PUSCH resource range corresponding to the buffer status index. PUSCH resources are allocated to the UE based on

Table 2 is a buffer state index table set according to an embodiment of the present invention.

buffer state index PUSCH resource range 0 <10 One <100 2 <1000

Referring to Tables 1 and 2, a buffer state index table in which PUSCH resource ranges are divided for each buffer state index is exemplified. 4, Table 1 and Table 2, the terminal according to an embodiment of the present invention measures the size of uplink data to be transmitted to the base station (S400). Hereinafter, it will be described that the uplink data size is 50.

The UE selects a buffer status index based on the uplink data size and PUSCH resource range (S402). The uplink data size is 50, and the buffer state index of the PUSCH resource range including the uplink data size is 1. Accordingly, the terminal selects buffer state 1.

The terminal transmits the SR of the selected index to the base station (S404). The selected index is the buffer state index 1, and the corresponding values of the SR period, SR subframe offset information, and PUCCH resource are 4, 5, and 6, respectively. Accordingly, the UE transmits SRs having SR period, SR subframe offset information, and PUCCH resource values of 4, 5, and 6 to the base station, respectively.

The terminal receives an uplink grant determined according to the SR of the selected index from the base station (S406). In other words, the base station recognizes the buffer status index according to the SR period of the SR transmitted by the terminal, the SR subframe offset information, and the PUCCH resource value, and transmits an uplink grant to the terminal based on the corresponding PUSCH resource range. When the base station receives an SR having an SR period, SR subframe offset information, and PUCCH resource values of 4, 5, and 6, respectively, it allocates a PUSCH resource to the terminal based on the PUSCH resource range corresponding to the buffer state index 1.

The terminal according to an embodiment of the present invention may be allocated the maximum value of the PUSCH resource range corresponding to the selected buffer state index as the PUSCH resource. The base station may transmit to the terminal the maximum value of the PUSCH resource range corresponding to the buffer state index of the SR received from the terminal. When the buffer state index value of the SR received by the base station is 1, the base station may allocate a PUSCH resource of 100 to the terminal.

The terminal transmits uplink data to the base station by using the PUSCH resource allocated by the uplink grant (S408).

Accordingly, since the UE is dynamically allocated PUSCH resources according to the size of uplink data to be transmitted, since the frequency of performing the BSR procedure is small, the time delay is minimized, and since the UE is allocated an appropriate PUSCH resource, resource waste is also minimized.

Hereinafter, an uplink reception process according to a support service type of uplink data according to an embodiment of the present invention will be described.

The terminal according to an embodiment of the present invention configures an SR resource through RRC configuration with a base station, and the SR resource includes at least one of an SR period, SR subframe offset information, and a PUCCH resource.

In this case, at least one of the SR period, SR subframe offset information, and PUCCH resource may be set differently for each support service of uplink data that the terminal intends to transmit to the base station. That is, the terminal and the base station can distinguish the support service of uplink data according to the SR period, SR subframe offset information, and the value of the PUCCH resource.

When the uplink data according to an embodiment of the present invention supports enhanced mobile broadband (eMBB), the terminal may receive an uplink grant from the base station a predetermined number of times.

When the uplink data supports the eMBB service, the UE needs to be allocated many PUSCH resources from the base station because the size of the uplink data is large. That is, the terminal may receive an uplink grant from the base station multiple times, and each time receiving an uplink grant, the terminal may be allocated a PUSCH resource, and may transmit uplink data having a large data size to the base station using the allocated PUSCH resource. there is.

을 만족하도록 상향링크 MCS 레벨 및 상향링크 자원 블록(RB: resource block) 수를 할당 받고, 할당 받은 상향링크 MCS 레벨 및 상향링크 자원 블록 수를 이용하여 상향링크 데이터를 기지국에게 전송한다. 상향링크 데이터가 URLLC 서비스를 지원하는 경우, 상향링크 데이터 전송률을 높이기 위해 단말과 기지국은 낮은 target BLER을 만족하도록 자원을 할당해야 한다.When the uplink data according to an embodiment of the present invention supports an ultra-reliable and low latency communications (URLLC) service, the terminal receives a target block error rate (BLER) value from the base station.

An uplink MCS level and the number of uplink resource blocks (RBs) are allocated to satisfy , and uplink data is transmitted to the base station using the allocated uplink MCS level and the number of uplink resource blocks. When the uplink data supports the URLLC service, in order to increase the uplink data rate, the UE and the base station must allocate resources to satisfy a low target BLER.

5 illustrates a block diagram of a terminal and a base station according to an embodiment of the present invention.

Referring to FIG. 5 , a 5G wireless communication system includes a base station 500 and a plurality of terminals 510 located within an area of the base station 500 .

The base station 500 includes a processor 501 , a memory 502 , and a communication unit 503 . The processor 501 implements the functions, processes and/or methods previously proposed in FIGS. 1 to 4 . The layers of the air interface protocol may be implemented by the processor 501 . The memory 502 is connected to the processor 501 and stores various information for driving the processor 501 . The communication unit 503 is connected to the processor 501 to transmit and/or receive a radio signal.

The terminal 510 includes a processor 511 , a memory 512 , and a communication unit 513 . The processor 511 implements the functions, processes and/or methods previously proposed in FIGS. 1 to 4 . The layers of the air interface protocol may be implemented by the processor 511 . The memory 512 is connected to the processor 511 and stores various information for driving the processor 511 . The communication unit 513 is connected to the processor 511 to transmit and/or receive a radio signal.

The memories 502 and 512 may be internal or external to the processors 501 and 511 , and may be coupled to the processors 501 and 511 by various well-known means. In addition, the base station 500 and/or the terminal 510 may have a single antenna or multiple antennas.

The embodiments described above are those in which elements and features of the present invention are combined in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented in a form that is not combined with other components or features. It is also possible to configure embodiments of the present invention by combining some elements and/or features. The order of operations described in the embodiments of the present invention may be changed. Some features or features of one embodiment may be included in another embodiment, or may be replaced with corresponding features or features of another embodiment. It is obvious that claims that are not explicitly cited in the claims can be combined to form an embodiment or included as a new claim by amendment after filing.

Embodiments according to the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of implementation by hardware, an embodiment of the present invention provides one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), FPGAs ( field programmable gate arrays), a processor, a controller, a microcontroller, a microprocessor, and the like.

In the case of implementation by firmware or software, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that perform the functions or operations described above. The software code may be stored in the memory and driven by the processor. The memory may be located inside or outside the processor, and may transmit and receive data to and from the processor by various known means.

Although it is described in FIG. 4 that steps S400 to S408 are sequentially executed, this is merely illustrative of the technical idea of an embodiment of the present invention. In other words, one of ordinary skill in the art to which an embodiment of the present invention pertains may change the order described in FIG. 4 within a range that does not deviate from the essential characteristics of an embodiment of the present invention, or perform one of steps S400 to S408. Since the above process may be variously modified and modified by executing the above process in parallel, FIG. 4 is not limited to a time-series order.

Meanwhile, the processes shown in FIG. 4 can be implemented as computer-readable codes on a computer-readable recording medium. The computer-readable recording medium includes all types of recording devices in which data readable by a computer system is stored. That is, the computer-readable recording medium may be a non-transitory medium such as ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device, and also carrier wave (for example, , transmission over the Internet) and may further include a transitory medium such as a data transmission medium. In addition, the computer-readable recording medium is distributed in a network-connected computer system so that the computer-readable code can be stored and executed in a distributed manner.

The above description is merely illustrative of the technical idea of this embodiment, and various modifications and variations will be possible by those skilled in the art to which this embodiment belongs without departing from the essential characteristics of the present embodiment. Accordingly, the present embodiments are for explanation rather than limiting the technical spirit of the present embodiment, and the scope of the technical spirit of the present embodiment is not limited by these embodiments. The protection scope of this embodiment should be interpreted by the following claims, and all technical ideas within the equivalent range should be interpreted as being included in the scope of the present embodiment.

500: base station 501: processor
502: memory 510: terminal

Claims (14)

In a method of requesting a dynamic scheduling of a terminal for transmission of uplink data,
The terminal presets an SR resource for each logical channel through radio resource control (RRC) configuration with the base station, and the SR resource includes a plurality of buffer status indexes, SR periodicity, It includes at least one of SR sub-frame offset information and PUCCH resources, a physical uplink shared channel (PUSCH) resource range is divided for each buffer status index, and the SR period, the SR sub for each buffer status index At least one of the frame offset information or the PUCCH resource is set differently,
The dynamic scheduling request method includes:
measuring an uplink data size;
selecting a buffer status index based on the uplink data size and the PUSCH resource range;
transmitting the SR to the base station based on the SR resource corresponding to the selected index;
receiving, from the base station, an uplink grant determined according to the SR resource corresponding to the selected index; and
transmitting the uplink data to the base station using the PUSCH resource allocated by the uplink grant;
A dynamic scheduling request method comprising a. According to claim 1,
The selection process is
A dynamic scheduling request method for selecting a buffer state index corresponding to a PUSCH resource range including the uplink data size. 3. The method of claim 2,
The PUSCH resource is a dynamic scheduling request method in which the maximum value of the PUSCH resource range. delete According to claim 1,
A dynamic scheduling request method in which at least one of the SR period, the SR subframe offset information, and the PUCCH resource is differently configured for each supported service type of the uplink data. 6. The method of claim 5,
When the uplink data supports an enhanced mobile broadband (eMBB) service,
The receiving is a dynamic scheduling request method of receiving the uplink grant from the base station a predetermined number of times. 6. The method of claim 5,
When the uplink data supports an ultra-reliable and low latency communication (URLLC) service,
The target BLER (block error rate) value from the base station

receiving an uplink modulation and coding scheme (MCS) level and a number of uplink resource blocks to satisfy and
transmitting the uplink data to the base station using the uplink MCS level and the number of uplink resource blocks;
Dynamic scheduling request method further comprising a. In the terminal for transmitting a dynamic scheduling request for uplink data transmission to a base station,
Memory;
a communication unit for communicating with the base station; and
includes a processor;
SR resources set for each logical channel through RRC configuration with the base station are stored in the memory, and the SR resources include at least one of a plurality of buffer status indexes, SR periods, SR subframe offset information, or PUCCH resources, A PUSCH resource range is divided for each buffer status index, and at least one of the SR period, the SR subframe offset information, or the PUCCH resource is set differently for each buffer status index,
The processor measures the uplink data size,
selecting a buffer status index based on the uplink data size and the PUSCH resource range;
Transmitting the SR to the base station based on the SR resource corresponding to the selected index,
Receive an uplink grant determined according to the SR resource corresponding to the selected index from the base station, and
A terminal configured to transmit the uplink data to the base station using the PUSCH resource allocated by the uplink grant. 9. The method of claim 8,
The processor is
A terminal configured to select a buffer state index corresponding to a PUSCH resource range including the uplink data size. 10. The method of claim 9,
The PUSCH resource is the maximum value of the PUSCH resource range UE. delete 9. The method of claim 8,
At least one of the SR period, the SR subframe offset information, and the PUCCH resource is configured differently for each supported service type of the uplink data. 13. The method of claim 12,
When the uplink data supports an enhanced mobile broadband (eMBB) service,
The processor is configured to receive the uplink grant from the base station a predetermined number of times. 13. The method of claim 12,
When the uplink data supports an ultra-reliable and low latency communication (URLLC) service,
The target BLER (block error rate) value from the base station

to be allocated an uplink MCS level and the number of uplink resource blocks to satisfy and
A terminal configured to transmit the uplink data to the base station using the uplink MCS level and the number of uplink resource blocks.

Images