WO2020161778A1

WO2020161778A1 - User device and communication method

Info

Publication number: WO2020161778A1
Application number: PCT/JP2019/003918
Authority: WO
Inventors: 徹内野; 高橋　秀明; リフェワン
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2019-02-04
Filing date: 2019-02-04
Publication date: 2020-08-13

Abstract

Provided is a user device comprising: a reception unit that receives allocation information for resources; and a transmission unit configured so that, if the type of the resources specified by the received resource allocation information corresponds to the type of data, the transmission unit transmits a buffer status report of the data using such resources.

Description

User equipment and communication method

The present invention relates to a user device and a communication method in a wireless communication system.

In 3GPP (3rd Generation Partnership Project), NR (New Radio) or 5G is used in order to further increase the system capacity, further increase the data transmission speed, and further reduce the delay in the wireless section. The so-called wireless communication system is being studied. In 3GPP, the main features of 5G are (1) further advanced mobile broadband (eMBB: enhanced Mobile BroadBand), (2) machine type communication (mMTC: massive Machine Communications), which realizes multiple simultaneous connections, (3) ) Highly reliable and ultra-low latency communication (URLLC: Ultra-Reliable and Low Latency Communications) is summarized.

In 5G, various wireless technologies are being studied in order to satisfy the requirement of achieving a throughput of 10 Gbps or more and a delay of a wireless section of 0.5 ms or less. URLLC aims to realize highly reliable and low delay communication (Ultra-Reliable and Low-Latency Communication). URLLC mainly targets services such as traffic control and remote control that require both high reliability and low delay. In Release 16, as an example of URLLC use cases, at least factory automation (Factor Automation), transportation industry, power distribution, augmented reality (AR: Virtual Reality) with a large packet (AR: Virtual Reality) Listed.

Currently, two working groups (WG) of 3GPP are performing standardization activities related to URLLC (Non-patent document 1, Non-patent document 2). One purpose is to support uplink intra-user equipment prioritization/multiplexing (UL intra-UE prioritization/multiplexing). For example, it has been considered to remove, delay or puncture lower priority services between different categories of traffic within a user equipment, including data signals and control signals.

According to Non-Patent Document 3, the BSR MAC CE is transmitted with a higher priority than any other data. Therefore, even if the priority of the content of the BSR is lower than the priority of the data, the transmission of the BSR is always prioritized. In this case, the BSR for low priority data delays the arrival of high priority URLLC data. There is a possibility that the BSR for the eMBB is prioritized, the data for the URLLC does not fit in the TB and is segmented, and as a result, the transmission of the URLLC packet is delayed. What is needed is a technique that avoids delays in sending URLLC packets.

According to an aspect of the present invention, a receiving unit that receives resource allocation information and a resource that is specified by the received resource allocation information and that uses the resource when the resource type corresponds to the data type A user equipment comprising: a transmitter for transmitting a buffer status report of the data.

According to the disclosed technology, a technology that enables avoiding a delay in URLLC packet transmission is provided.

It is a block diagram of a communication system in the present embodiment. It is a figure which shows the example of the subject 1. It is a figure which shows the example of the solution method of the subject 1. It is a figure which shows the example of the subject 2. It is a figure which shows the example of the solution method of the subject 2. It is a figure which shows the example of the subject 3. It is a figure which shows the example of the solution method of the subject 3. 3 is a diagram showing an example of a functional configuration of the user device 10. FIG. It is a figure which shows an example of a functional structure of the base station 20. FIG. 3 is a diagram showing an example of a hardware configuration of a user device 10 and a base station 20.

Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are merely examples, and embodiments to which the present invention is applied are not limited to the following embodiments.

It is assumed that the wireless communication system in the following embodiments basically complies with NR, but this is an example, and the wireless communication system in this embodiment partially or wholly has a wireless function other than NR. It may be based on a communication system (for example, LTE).

(Overall system configuration)
FIG. 1 shows a configuration diagram of a wireless communication system according to the present embodiment. The wireless communication system according to the present embodiment includes a user equipment 10 and a base station 20, as shown in FIG. Although one user apparatus 10 and one base station 20 are shown in FIG. 1, this is an example, and a plurality of each may be provided.

The user device 10 is a communication device having a wireless communication function such as a smart phone, a mobile phone, a tablet, a wearable terminal, a communication module for M2M (Machine-to-Machine), and the like, and is wirelessly connected to the base station 20 to establish a wireless communication system. Use various communication services provided by. The base station 20 is a communication device that provides one or more cells and wirelessly communicates with the user device 10.

In the present embodiment, the duplex system may be a TDD (Time Division Duplex) system or an FDD (Frequency Division Duplex) system.

3GPP defines major requirements for 5G wireless access technology (5G wireless) for each usage scenario. As mentioned above, the requirement for URLLC is a very low delay of 0.5 ms.

On the other hand, the requirements for eMBB are to achieve a downlink peak communication speed of 20 Gbps and an upstream peak communication speed of 10 Gbps. In particular, for eMBB, the requirement for C-plane latency is 10 ms, and the requirement for U-plane latency is 4 ms. That is, the requirement regarding the delay for the URLLC is different from the requirement regarding the delay for the eMBB.

(BSR)
The buffer status report (BSR) is a MAC Control Element (MAC CE) transmitted from the user equipment 10 to the network, and includes information indicating the amount of data to be transmitted in the buffer of the user equipment 10. In response to the reception of the BSR, in the network, if resources are available, the minimum required amount of uplink grant (UL Grant), that is, resources of the physical uplink shared channel (PUSCH), is set by the user equipment. Assign to 10.

(Scheduling Request (SR))
The Scheduling Request (SR) is a message of the physical layer (L1), and is a message for the user apparatus 10 to request the network to transmit the UL grant (DCI format 0) for transmitting the PUSCH. The user apparatus 10 transmits SR by the physical uplink control channel (PUCCH) or the UCI part of PUSCH.

Like the LTE, the NR defines the BSR procedure and the SR procedure in order to request the UL resource allocation for uplink data transmission from the user apparatus 10.

Below, a basic operation example of the BSR procedure (Buffer Status reporting procedure) is explained.

When data is generated inside the user device 10, the user device 10 starts (triggers) the BSR procedure and tries to notify the buffer status to the network.

When the BSR procedure is triggered, the user device 10 activates the SR procedure. When the PUCCH resource for SR is set, the user apparatus 10 transmits the SR to the network via the PUCCH resource that is set (hereinafter, transmitting the SR via the PUCCH resource, It may be expressed as "transmit PUCCH-SR"). When the PUCCH resource for SR is not set, the user apparatus 10 activates a random access procedure.

As a trigger for activating the BSR procedure, if the transmission of the BSR is periodically triggered at least in the presence of data inside the user device 10 in addition to the occurrence of data, the BSR is transmitted. It is possible that the UL grant cannot be received, and that the transport block size (TBS) is large after the data is included in the transport block (TB), and therefore there is still room for the TB to include the data.

In LTE, the SR procedure was performed for each user device 10. With Release 16 NR, one user equipment 10 may simultaneously provide multiple services. Therefore, the user device 10 can control scheduling settings and procedures for each service.

(About Challenge 1)
According to Non-Patent Document 3, the BSR MAC CE is transmitted at the shortest PUSCH transmission timing regardless of its content.

In this case, the BSR of the URLLC data may be reported on the PUSCH for eMBB, and as a result, the URLLC data transmission may be delayed. In other words, since the BSR MAC CE can be transmitted by any PUSCH, the BSR for URLLC is also transmitted by the PUSCH for eMBB, which delays the grasp of the buffer status on the network side, resulting in a URLLC packet Transmission may be delayed (Issue 1).

In Release 16, a service with lower delay is assumed, and it is considered that the impact on the service will increase if the above delay occurs. Therefore, there is a need for means for solving the above-mentioned problems.

Below, an example of Issue 1 will be explained with reference to FIG. As a premise of FIG. 2, the delay requirement for eMBB is less stringent than the delay requirement for URLLC. Therefore, the transmission timing cycle of PUCCH-SR for eMBB is the transmission of PUCCH-SR for URLLC. The transmission cycle of the PUCCH-SR for URLLC is set to be longer than the cycle of the timing (that is, the transmission timing of PUCCH-SR for eMBB is set to be shorter than the transmission timing cycle of PUCCH-SR).

First, data for eMBB is generated in the user device 10 (step S101). The user apparatus 10 triggers a BSR procedure and transmits PUCCH-SR in step S102 (uses PUCCH resources to transmit SR).

After that, the base station 20 transmits the UL grant to the user apparatus 10 in step S103 in response to receiving the PUCCH-SR.

Here, immediately before receiving the UL grant transmitted from the base station in step S103, data for URLLC is generated in the user device 10, and the user device 10 triggers the BSR procedure for the data for URLLC (step S103). S104).

As mentioned above, BSR MAC CE is transmitted at the shortest PUSCH transmission timing regardless of the content. In the example shown in FIG. 2, the UL grant transmitted in step S103 is received by the user apparatus 10, so that the shortest PUSCH transmission timing for the BSR procedure triggered in step S104 is determined. Accordingly, in step S105, the user device 10 cancels the BSR procedure for the data for the URLLC. Then, in step S106, the user apparatus 10 transmits the buffer status (BS) regarding the data for eMBB and the buffer status (BS) regarding the data for URLLC to the base station 20 via PUSCH.

The base station 20 detects the occurrence of the URLLC data in the user device 10 by receiving the buffer status regarding the URLLC data transmitted by the user device 10 in step S106, and in response to this, the base station 20 20 transmits UL grant regarding the data for the said URLCC to the user apparatus 10 (step S107).

In response to receiving the UL grant transmitted by the base station 20 in step S107, the user device 10 transmits the URLLC data to the base station 20 via the PUSCH in step S108. In addition, actually, the user apparatus 10 transmits the data for the eMBB to the base station 20 via the PUSCH, but in FIG. 2, the transmission of the data for the eMBB via the PUSCH is omitted for convenience of description. doing.

(Means for solving the problem 1)
In the procedure shown in FIG. 2, in response to receiving the UL grant transmitted in step S103, the user device 10 cancels the BSR procedure for the data for URLLC activated in step S105. On the other hand, even when the UL grant transmitted in step S103 is received, by preventing the user apparatus 10 from canceling the BSR procedure for the data for URLLC activated in step S105, Problem 1 can be solved.

Below, the solution to Problem 1 will be explained with reference to FIG.

First, data for eMBB is generated in the user device 10 (step S201). The user apparatus 10 triggers a BSR procedure and transmits PUCCH-SR in step S202.

After that, the base station 20 transmits the UL grant to the user device 10 in step S203 in response to receiving the PUCCH-SR transmitted from the user device 10 in step S202.

Here, immediately before receiving the UL grant transmitted from the base station in step S203, data for URLLC is generated in the user device 10, and the user device 10 triggers a BSR procedure for the data for URLLC (step S203). S204).

In the example shown in FIG. 3, even when the UL grant transmitted in step S203 is received by the user device 10, the user device 10 does not cancel the BSR procedure for the data for URLLC (S205). Then, in step S206, the user apparatus 10 transmits the buffer status (BS) regarding the data for the eMBB and the buffer status (BS) regarding the data for the URLLC to the base station 20 via the PUSCH for the eMBB.

In step S205, the BSR procedure for the URLLC data has not been canceled. Therefore, the user device 10 transmits the PUCCH-SR regarding the data for the URLLC at the shortest PUCCH-SR timing for the URLLC (step S207). Therefore, the base station 20 can detect the occurrence of the URLLC data in the user device 10 earlier than in the case shown in FIG.

Therefore, the base station 20 can transmit the UL grant for the buffer status report (BSR) regarding the URLLC data to the user equipment 10 earlier than the timing shown in FIG. 2 (step S208), and the user equipment 10 The BSR relating to the data for URLLC can be transmitted via the PUSCH for URLLC earlier than the timing shown in 2 (step S209). The user device 10 cancels the BSR procedure for the data for the URLLC after transmitting the BSR for the data for the URLLC via the PUSCH for the URLLC.

In addition, actually, the user apparatus 10 transmits the data for the eMBB to the base station 20 via the PUSCH, but in FIG. 3, the transmission of the data for the eMBB via the PUSCH is omitted for convenience of description. doing.

As described above, in the solution method of Problem 1, when data for a specific logical channel (LCH or logical channel group (LCG)) occurs, the buffer status (BS) is transmitted on the PUSCH corresponding to the LCH or LCG. Until then, the BSR procedure for the data for the specific LCH (LCG) is not canceled.

That is, as shown in FIG. 3, in the solution method of the problem 1, the user apparatus 10 transmits the BSR MAC CE at the latest PUSCH transmission timing when the BSR procedure for the data for the URLLC is triggered, but the URLLC The BSR procedure for the data for URLLC is not canceled until the BSR MAC CE of the data for URLLC is transmitted on the PUSCH for the target (in the example shown in FIG. 2, the user device 10 has the BSR MAC CE at the time of transmitting the BSR MAC CE). I have canceled the procedure).

-Additionally, the details of the control of the solution method of Issue 1 will be explained.

The user device 10 maps the LCH (or LCG) to a specific PUSCH.

The mapping of LCH (or LCG) to PUSCH may be explicitly notified to the user apparatus 10 by an RRC/MAC/L1 control signal or the like by considering the mapping as a group, and implicitly according to a specific rule. May be done.

As one example, when LCG is mapped to PUSCH, it is known that LCHs are grouped and then grouped to LCG, so the mapping may be used as it is. Further, LCHs having the same priority may be regarded as belonging to the same group, for example, LCHs having a specific QoS/QFI may be regarded as belonging to the same group.

If a group is not notified for an LCH, it may be implicitly recognized as belonging to a specific group.

Also, the group number may be implicitly assigned to multiple LCHs. For example, a group number may be allocated from an LCH having a shorter set time, an LCH having a smaller LCH/LCG identifier may be allocated, or a group number may be allocated from an LCH having a higher priority. May be.

For associating the group with the PUSCH, LCH restriction (PUSCH-duration, Configured grant Type, SCS, AllowedCell, MSC table) may be diverted, or LCH/LCG mapping/Restriction rules may be applied separately. Good.

The user apparatus 10 transmits the buffer status (BS) at the latest PUSCH transmission timing when the BSR process is triggered, but is triggered when the latest PUSCH is not the PUSCH corresponding to LCH/LCG. Maintain the state of BSR processing.

For example, the user device 10 does not have to cancel the BSR process and may alternatively trigger the BSR process again. When the user device 10 triggers the BSR process again, the Regular BSR process may be triggered (SR is triggered again). Alternatively, when the user equipment 10 triggers the BSR process again, it is not necessary to trigger the Regular BSR (the user equipment 10 may wait for allocation of additional UL resources from the base station 20 (gNB)). ).

When the user device 10 transmits a Buffer Status Report (BSR) at the latest PUSCH transmission timing, and when the PUSCH is not a PUSCH corresponding to LCH/LCG, the BSR transmitted by the user device 10 is the PUSCH. The content may notify that data of unsupported LCH/LCG still exists (eg, may be reported as a trunk BSR).

The user device 10 cancels the BSR process when the BSR is transmitted on the PUSCH corresponding to the LCH/LCG.

(About Challenge 2)
Another issue is that BSR for eMBB data is prioritized and URLLC data transmission is delayed (Problem 2).

Below, an example of Issue 2 will be explained with reference to FIG.

First, in the user device 10, data (200 bytes) for URLLC is generated (step S301).

The user device 10 triggers the BSR procedure and transmits PUCCH-SR in step S302.

After that, the base station 20 transmits the UL grant (200 bytes) to the user apparatus 10 in step S303 in response to receiving the PUCCH-SR.

Here, immediately before receiving the UL grant transmitted from the base station 20 in step S303, data for the eMBB is generated in the user apparatus 10, and the user apparatus 10 triggers the BSR procedure for the data for the eMBB ( Step S304).

In the case of FIG. 4, since the data for the eMBB is generated in step S304, the user device 10 tries to transmit the BSR regarding the data for the eMBB.

According to Non-Patent Document 3, the BSR MAC CE is transmitted with a higher priority than any other data. Therefore, even if the priority of the content of the BSR is lower than the priority of the data, the transmission of the BSR is always prioritized. For example, suppose that 5 bytes are required to transmit the BSR MAC CE.

In this case, since the transmission of the BSR has priority over the transmission of the data for URLLC, the user device 10 transmits the URLLC data of 195 bytes and the BSR MAC CE of 5 bytes in step S305. The content of the BSR MAC CE indicates that the size of the data for the eMBB and the rest of the URLLC data is 5 bytes.

In response to receiving the BSR MAC CE, the base station 20 transmits the UL grant corresponding to 5 bytes to the user device 10 because the remaining URLLC data is 5 bytes (step S306).

In response to receiving the UL grant transmitted in step S306, the user device 10 transmits the remaining 5 bytes of URLLC data in step S307.

In this way, in the example shown in FIG. 4, the arrival of URLLC data of high priority is delayed due to the BSR for data of low priority. In other words, according to Non-Patent Document 3, since BSR (BSR other than padding BSR) is prioritized over data (Dedicated Traffic Channel (DTCH)/Dedicated Control Channel (DCCH)), Transport Block Size (TBS) If not large enough, the BSR for eMBB is prioritized and the data for URLLC is segmented without filling TB, resulting in a delay in the transmission of URLLC packets.

(Means for solving the problem 2)
In the procedure shown in FIG. 4, in response to the generation of the data for the eMBB in step S304, the BSR procedure for the data for the eMBB is activated, and the MAC CE of the BSR has a higher priority than any other data. Since it is transmitted, the MAC CE of 5 bytes BSR is added to the data transmitted by PUSCH in step S305. On the other hand, since the PUSCH, which is the channel for transmitting data in step S305, is associated with the URLLC, the type of data transmitted via the PUSCH in step S305 should be limited to data related to URLLC. Then, the above-mentioned problem 2 can be solved.

Below, we will explain the solution to Problem 2 with reference to FIG.

First, data for eMBB is generated in the user device 10 (step S401). The user device 10 triggers the BSR procedure and transmits PUCCH-SR in step S402.

After that, the base station 20 transmits the UL grant (200 bytes) to the user apparatus 10 in step S403 in response to receiving the PUCCH-SR.

Here, immediately before receiving the UL grant transmitted from the base station 20 in step S403, data for the eMBB is generated in the user device 10, and the user device 10 triggers the BSR procedure for the data for the eMBB ( Step S404).

In the case of FIG. 5, since data for the eMBB is generated in step S404, the user device 10 attempts to transmit the BSR regarding the data for the eMBB. However, since the PUSCH that is the channel for transmitting data in step S405 is the PUSCH associated with the URLLC, the data transmitted in step S405 is limited to the data associated with the URLLC. That is, in step S405, the 5-byte BSR MAC CE regarding the data for the eMBB is not transmitted.

The user device 10 transmits the URLLC data of 200 bytes in step S405.

At this point, the user device 10 has not yet transmitted the BSR regarding the data for the eMBB. Therefore, the user apparatus 10 transmits the PUCCH-SR regarding the data for the eMBB at the latest PUCCH-SR timing for the eMBB (step S406).

The base station 20 transmits the UL grant to the user device 10 in response to receiving the SR transmitted in step S406 (step S407).

The user device 10 transmits the data for the eMBB via the PUSCH associated with the eMBB in response to the reception of the UL grant transmitted in step S407 (step S408).

-Additionally, the details of the control of the solution method of Issue 2 will be explained.

When the data for a specific LCH (LCG) is generated, the user device 10 limits the UL resource (PUSCH) that transmits the BS information.

When the BSR procedure is triggered, the user equipment 10 reports the BS information of the specific LCH (LCG) only by the UL resource corresponding to the specific LCH (LCG). That is, the BSR MAC CE of the specific LCH (LCG) is transmitted via the PUSCH corresponding to the specific LCH (LCG).

The user device 10 maps the LCH (or LCG) to a specific PUSCH.

The user device 10 executes the BSR procedure corresponding to a specific LCH (LCG) independently of the BSR procedure corresponding to another LCH (LCG). Additionally, the user equipment 10 may perform the BSR procedure corresponding to a specific LCH (LCG) according to the existing BSR procedure. In the example of FIG. 5, the BSR procedure for URLLC and the BSR procedure for eMBB are executed independently, the BSR procedure for URLLC is executed similarly to the existing BSR procedure, and the BSR procedure for eMBB is performed. The procedure will be performed similar to the existing BSR procedure.

Further, the individual BSR procedure may be applied only to a specific BSR (for example, high priority BSR such as regular BSR, Periodic BSR, Retx BSR) (other BSRs are not regarded as individual BSR procedures). Good).

In addition, when a BSR is reported in a certain BSR procedure, information about the BS information in the other BSR procedure may be reported (for example, LCG field corresponding to the other BSR procedure is set to 1 and Regular BSR is set). Even if it exists, it may be reported as a trunk BSR (BSR indicating that some information is omitted).

Note that the BSR procedure considering the LCH/LCG as shown in the

above solution methods

1 and 2 may be diverted to other procedures related to UL grant, such as PHR (Power Headroom).

(About Challenge 3)
According to Non-Patent Document 3, a Scheduling Request (SR) is triggered by a BSR trigger, and the SR is canceled when the BSR can be transmitted by the PUSCH resource allocated by the network in response thereto.

When PUSCH for transmitting BSR is limited as in the solution of the above-mentioned problem 2, if only high-priority data continues, SR for eMBB continues to be triggered and SR retransmission excess triggers RACH procedure, which is unnecessary. UL interference (Problem 3).

An example of task 3 will be described below with reference to FIG.

As shown in FIG. 6, the MAC layer of the user apparatus 10 instructs PUCCH-SR transmission to the L1 (physical layer) of the user apparatus 10 for MBB. The MAC layer of the user apparatus 10 increments the value of the counter by 1 every time the L1 of the user apparatus 10 is instructed to perform PUCCH-SR transmission. Here, the MAC layer of the user apparatus 10 counters every time the PUCCH-SR transmission is instructed to the L1 of the user apparatus 10 regardless of whether the PUCCH-SR transmission is actually performed in the L1 of the user apparatus 10. Increase the value of by 1. Therefore, when only high priority data continues, the user apparatus 10 prioritizes transmission of the high priority data and does not perform PUCCH-SR transmission. As a result, although the PUCCH-SR transmission is not performed, the counter value increases and the counter value exceeds the maximum transmission count.

(Means for solving the problem 3)
Problem 3 described above is that, when L1 of the user apparatus 10 actually performs PUCCH-SR transmission, feedback is provided to the MAC layer of the user apparatus 10, and the MAC layer of the user apparatus 10 sets the L1 of the user apparatus 10 to L1. It can be solved by increasing the value of the counter only when receiving feedback from.

Below, with reference to FIG. 7, the solution method of Problem 3 will be explained. The MAC layer of the user apparatus 10 instructs the L1 of the user apparatus 10 to transmit the PUCCH-SR, and when receiving feedback from the L1 of the user apparatus 10, increases the value of the counter by 1. According to this method, when the L1 of the user equipment 10 does not transmit the PUCCH-SR, the L1 of the user equipment 10 does not feed back to the MAC layer of the user equipment 10, so the value of the counter increases. do not do. In the example of FIG. 7, since the MAC layer receives the feedback from L1 in response to the first instruction at the first time, the value of the counter is incremented by 1. After that, PUCCH-SR is not transmitted for any of the five indications, and the MAC layer receives no feedback. Therefore, the value of the counter remains 1. In response to the sixth instruction, PUCCH-SR is transmitted, the MAC layer receives the feedback, and increments the counter value by 1.

-Additionally, the details of the control of the solution method of Issue 3 will be explained.

When the MAC layer of the user apparatus 10 instructs PUCCH-SR transmission to the L1 of the user apparatus 10, only when the information indicating that “transmission has been performed” is received from the L1 of the user apparatus 10 of the user apparatus 10. The MAC layer may increment the value of the counter. Alternatively, if the MAC layer of the user equipment 10 directs PUCCH-SR transmission to the L1 of the user equipment 10, if it does not receive information from the L1 of the user equipment 10 that "transmission has not been performed". Only, the MAC layer of the user equipment 10 may increment the value of the counter. Alternatively, the MAC layer of the user equipment 10 once increments the value of the counter at the time when the PUCCH-SR transmission is instructed to the L1 of the user equipment 10, and the “transmission has not been performed” from the L1 of the user equipment 10. The MAC layer of the user apparatus 10 may decrease the value of the counter when receiving the information indicating Whether or not the above control is applied may be set for each SR configuration.

Note that the above control may be applied regardless of whether or not the solution method of Issue 2 is applied. For example, in order to prioritize SR for URLLC between PUCCH-SR for eMBB and PUCCH-SR for URLLC, the above control is performed when PUCCH-SR for eMBB is not transmitted (drop/scaling). May be applied.

(Device configuration)
Next, a functional configuration example of the user apparatus 10 and the base station 20 that execute the processing operation described above will be described. The user device 10 and the base station 20 have all the functions described in this embodiment. However, the user apparatus 10 and the base station 20 may have only some of the functions described in the present embodiment. The user device 10 and the base station 20 may be collectively referred to as a communication device.

<User device>
FIG. 8 is a diagram illustrating an example of a functional configuration of the user device 10. As shown in FIG. 8, the user device 10 includes a transmission unit 110, a reception unit 120, and a control unit 130. The functional configuration shown in FIG. 10 is merely an example. As long as the operation according to the present embodiment can be executed, the function classification and the names of the function units may be any names.

The transmitter 110 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 120 wirelessly receives various signals and acquires higher-layer signal from the received physical-layer signal. The receiving unit 120 also includes a measuring unit that measures a received signal and obtains received power and the like.

The control unit 130 controls the user device 10. The function of the control unit 130 related to transmission may be included in the transmission unit 110, and the function of the control unit 130 related to reception may be included in the reception unit 120.

When the data to be transmitted is generated in the user device 10, the control unit 130 instructs the transmission unit 110 to transmit the PUCCH-SR. For example, when data for URLLC is generated in the user device 10, the control unit 130 activates the BSR procedure for data for URLLC. After that, even when the receiving unit 120 receives, for example, the UL grant for the eMBB, the BSR procedure for the data for the URLLC is maintained in the activated state. The control unit 130 cancels the BSR procedure for the data for the URLLC when the BSR transmission is performed on the PUSCH for the URLLC.

In addition, when the BSR procedure is activated and the transmission unit 110 transmits the data associated with the specific communication type, the control unit 130 transmits the data via the PUSCH associated with the specific communication type. Control is performed so that the data is transmitted.

In addition, the control unit 130, when instructing the transmission unit 110 to perform PUSCCH-SR transmission, receives the feedback indicating that the PUSCCH-SR transmission is actually performed from the transmission unit 110, only when the counter value is reached. To increase.

<Base station 20>
FIG. 9 is a diagram showing an example of the functional configuration of the base station 20. As shown in FIG. 9, the base station 20 includes a transmitter 210, a receiver 220, and a controller 230. The functional configuration shown in FIG. 9 is merely an example. As long as the operation according to the present embodiment can be executed, the function classification and the names of the function units may be any names.

The transmitting unit 210 includes a function of generating a signal to be transmitted to the user device 10 side and wirelessly transmitting the signal. The receiving unit 220 includes a function of receiving various signals transmitted from the user device 10 and acquiring, for example, information of a higher layer from the received signals. In addition, the receiving unit 220 includes a measuring unit that measures a received signal and obtains received power and the like.

The control unit 230 controls the base station 20. The function of the control unit 230 related to transmission may be included in the transmission unit 210, and the function of the control unit 230 related to reception may be included in the reception unit 220.

<Hardware configuration>
The block diagrams (FIGS. 8 to 9) used in the description of the above embodiments show functional unit blocks. These functional blocks (components) are realized by an arbitrary combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device physically or logically coupled, or directly or indirectly (for example, two or more devices physically or logically separated). , Wired, wireless, etc.) and may be implemented using these multiple devices. The functional block may be realized by combining the one device or the plurality of devices with software. Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, observation, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but not limited to these. I can't. For example, a functional block (component) that causes transmission to function is called a transmitting unit or a transmitter. In any case, as described above, the implementation method is not particularly limited.

Further, for example, both the user device 10 and the base station 20 according to the embodiment of the present invention may function as a computer that performs the processing according to the present embodiment. FIG. 10 is a diagram showing an example of a hardware configuration of the user equipment 10 and the base station 20 according to the present embodiment. Each of the user equipment 10 and the base station 20 described above may be physically configured as a computer equipment including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. Good.

Note that in the following description, the word "device" can be read as a circuit, device, unit, or the like. The hardware configurations of the user device 10 and the base station 20 may be configured to include one or a plurality of each of the devices 1001 to 1006 shown in the figure, or may be configured without including some devices. May be.

Each function in the user device 10 and the base station 20 causes a predetermined software (program) to be loaded on hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs an operation and controls communication by the communication device 1004. Alternatively, it is realized by controlling at least one of reading and writing of data in the memory 1002 and the storage 1003.

The processor 1001 operates an operating system to control the entire computer, for example. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, the baseband signal processing unit 104 and the call processing unit 105 described above may be realized by the processor 1001.

Also, the processor 1001 reads a program (program code), software module, data, and the like from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least part of the operations described in the above-described embodiments is used. For example, the control unit 401 of the user device 10 may be implemented by a control program stored in the memory 1002 and operating in the processor 1001, and may be implemented similarly for other functional blocks. Although it has been described that the various processes described above are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via an electric communication line.

The memory 1002 is a computer-readable recording medium, and is configured by, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. May be done. The memory 1002 may be called a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code) that can be executed to implement the wireless communication method according to the embodiment of the present disclosure, a software module, and the like.

The storage 1003 is a computer-readable recording medium, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (for example, a compact disc, a digital versatile disc, a Blu-ray disc). At least one of a (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, and a key drive), a floppy (registered trademark) disk, a magnetic strip, or the like. The storage 1003 may be called an auxiliary storage device. The storage medium described above may be, for example, a database including at least one of the memory 1002 and the storage 1003, a server, or another appropriate medium.

The communication device 1004 is hardware (transmission/reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of a frequency division duplex (FDD: Frequency Division Duplex) and a time division duplex (TDD: Time Division Duplex). May be composed of For example, the transmission/reception antenna 101, the amplifier unit 102, the transmission/reception unit 103, the transmission path interface 106, and the like described above may be realized by the communication device 1004. The transmitter/receiver 103 may be physically or logically separated from the transmitter 103a and the receiver 103b.

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured by using a single bus, or may be configured by using a different bus for each device.

Further, the user device 10 and the base station 20 respectively include a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), etc. It may be configured to include hardware, and a part or all of each functional block may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these hardware.

(Summary of Embodiments)
In this specification, at least the following communication device and communication method are disclosed.

A receiving unit that receives resource allocation information, and transmits a buffer status report of the data using the resource when the resource type specified in the received resource allocation information corresponds to the data type. A user device comprising: a transmitter.

According to the above configuration, for example, BSR for eMBB is prioritized, and data for URLLC is segmented without being fully stored in TB, and as a result, delay in transmission of URLLC packet can be avoided.

If the type of the resource designated by the received resource allocation information does not correspond to the type of the data, the transmitting unit does not have to transmit the buffer status report of the data.

When the type of the resource designated by the received resource allocation information does not correspond to the type of the data, the transmission unit uses the resource and outputs information that omits a part of the buffer status report of the data. You may send it.

The user apparatus further includes a control unit, and the control unit, when detecting that the transmission unit has transmitted information requesting allocation of transmission resources for transmitting the buffer status of the data, a counter You may change the value.

Receiving resource allocation information,
Transmitting a buffer status report of the data using the resource when the type of the resource designated by the received resource allocation information corresponds to the type of the data,
And a communication method in a user equipment.

(Supplement to the embodiment)
Although the embodiment of the present invention has been described above, the disclosed invention is not limited to such an embodiment, and those skilled in the art can understand various modifications, modifications, alternatives, and substitutions. Ah Although specific numerical values are used for the purpose of facilitating the understanding of the invention, unless otherwise specified, those numerical values are merely examples and any appropriate values may be used. The division of items in the above description is not essential to the present invention, items described in two or more items may be used in combination as necessary, and items described in one item may be different items. It may apply to the matters described in (as long as there is no conflict). The boundaries of the functional units or processing units in the functional block diagram do not always correspond to the boundaries of physical parts. The operation of the plurality of functional units may be physically performed by one component, or the operation of one functional unit may be physically performed by the plurality of components. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as there is no contradiction. For convenience of description of the process, the user equipment 10 and the base station 20 have been described using functional block diagrams, but such equipment may be implemented in hardware, software, or a combination thereof. The software operated by the processor included in the user equipment 10 according to the embodiment of the present invention and the software operated by the processor included in the base station 20 according to the embodiment of the present invention are random access memory (RAM), flash memory, and read-only, respectively. It may be stored in a memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

The notification of information is not limited to the aspect/embodiment described in the present disclosure, and may be performed using another method. For example, information is notified by physical layer signaling (eg, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (eg, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by notification information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration message, or the like.

Each aspect/embodiment described in the present disclosure is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system). system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), other systems using appropriate systems, and extensions based on these. It may be applied to at least one of the next-generation systems. Further, a plurality of systems may be combined and applied (for example, a combination of at least one of LTE and LTE-A and 5G).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps in a sample order, and are not limited to the specific order presented.

The specific operation that is performed by the base station 20 in the present disclosure may be performed by its upper node in some cases. In a network including one or a plurality of network nodes having the base station 20, various operations performed for communication with a terminal include the base station 20 and other network nodes other than the base station 20 (for example, , MME or S-GW, etc., but is not limited to these). Although the case where there is one network node other than the base station 20 has been described above, a combination of a plurality of other network nodes (for example, MME and S-GW) may be used.

Information that has been input and output may be stored in a specific location (for example, memory), or may be managed using a management table. Information that is input/output may be overwritten, updated, or added. The output information and the like may be deleted. The input information and the like may be transmitted to another device.

The determination may be performed by a value represented by 1 bit (0 or 1), may be performed by a boolean value (Boolean: true or false), and may be performed by comparing numerical values (for example, a predetermined value). (Comparison with the value).

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be switched according to execution. Further, the notification of the predetermined information (for example, the notification of “being X”) is not limited to the explicit notification, and is performed implicitly (for example, the notification of the predetermined information is not performed). Good.

Although the present disclosure has been described in detail above, it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and changes without departing from the spirit and scope of the present disclosure defined by the description of the claims. Therefore, the description of the present disclosure is for the purpose of exemplification, and does not have any restrictive meaning to the present disclosure.

Software, whether called software, firmware, middleware, microcode, hardware description language, or any other name, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules , Application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc. should be construed broadly.

Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, the software uses a wired technology (coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL: Digital Subscriber Line), etc.) and/or wireless technology (infrared, microwave, etc.) websites, When sent from a server, or other remote source, at least one of these wired and wireless technologies are included within the definition of transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description include voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any of these. May be represented by a combination of

Note that the terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). The signal may also be a message. Moreover, a component carrier (CC:Component Carrier) may be called a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

Further, the information, parameters, etc. described in the present disclosure may be represented by using an absolute value, may be represented by using a relative value from a predetermined value, or by using other corresponding information. May be represented. For example, the radio resources may be those indicated by the index.

-The names used for the above parameters are not limited in any way. Further, the mathematical formulas and the like using these parameters may differ from those explicitly disclosed in the present disclosure. Since different channels (eg PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the different names assigned to these different channels and information elements are in no way limited names. is not.

In the present disclosure, "base station (BS: Base Station)", "wireless base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", " "Access point", "transmission point", "reception point", "transmission/reception point", "cell", "sector", "cell group", " The terms "carrier", "component carrier" and the like may be used interchangeably. A base station may be referred to by terms such as macro cell, small cell, femto cell, and pico cell.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small indoor base station (RRH: Communication service can also be provided by Remote Radio Head.The term "cell" or "sector" means a part or the whole of the coverage area of at least one of the base station and the base station subsystem that perform communication service in this coverage. Refers to.

In the present disclosure, terms such as “mobile station (MS: Mobile Station)”, “user terminal”, “user device (UE: User Equipment)”, and “terminal” may be used interchangeably. ..

Mobile stations are defined by those skilled in the art as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless. It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmission device, a reception device, a communication device, or the like. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ). Note that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Also, the base station in the present disclosure may be replaced by the user terminal. For example, the communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (eg, may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the function of the above-described base station 20. Further, the words such as “up” and “down” may be replaced with the words corresponding to the communication between terminals (for example, “side”). For example, the uplink channel and the downlink channel may be replaced with the side channel.

Similarly, the user terminal in the present disclosure may be replaced by the base station. In this case, the base station 20 may have the function of the user terminal 20 described above.

The terms "connected," "coupled," or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled”. The connections or connections between the elements may be physical, logical, or a combination thereof. For example, “connection” may be read as “access”. As used in this disclosure, two elements are in the radio frequency domain, with at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-exhaustive examples. , Can be considered to be “connected” or “coupled” to each other, such as with electromagnetic energy having wavelengths in the microwave and light (both visible and invisible) regions.

The reference signal may be abbreviated as RS (Reference Signal) or may be referred to as a pilot (Pilot) depending on the applied standard.

As used in this disclosure, the phrase “based on” does not mean “based only on,” unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

Where the use of "include", "including" and variations thereof in this disclosure, these terms are inclusive, as is the term "comprising." Is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive or.

In the present disclosure, if translations add articles, such as a, an, and the in English, the disclosure may include that the noun that follows these articles is plural.

In the present disclosure, the term “A and B are different” may mean “A and B are different from each other”. The term may mean that “A and B are different from C”. The terms "remove", "coupled" and the like may be construed as "different" as well.

Although the present invention has been described in detail above, it is obvious to those skilled in the art that the present invention is not limited to the embodiments described in this specification. The present invention can be implemented as modified and changed modes without departing from the spirit and scope of the present invention defined by the description of the claims. Therefore, the description of the present specification is for the purpose of exemplifying explanation, and does not have any restrictive meaning to the present invention.

101 transmitter 102 receiver 103 controller 201 transmitter 202 receiver 203 controller 1001 processor 1002 memory 1003 storage 1004 communication device 1005 input device 1006 output device

Claims

A receiver for receiving resource allocation information,
A transmission unit that transmits a buffer status report of the data using the resource when the type of the resource designated by the received resource allocation information corresponds to the type of the data,
A user equipment comprising.
If the resource type specified in the received resource allocation information does not correspond to the data type, the transmission unit does not transmit a buffer status report of the data,
The user device according to claim 1.
When the type of the resource designated by the received resource allocation information does not correspond to the type of the data, the transmission unit uses the resource and outputs information that omits a part of the buffer status report of the data. Send,
The user device according to claim 1.
The user device further includes a control unit,
When the control unit detects that the transmission unit has transmitted information requesting allocation of transmission resources for transmitting the buffer status of the data, the control unit changes the counter value,
The user device according to claim 1.
Receiving resource allocation information,
Transmitting a buffer status report of the data using the resource when the type of the resource designated by the received resource allocation information corresponds to the type of the data,
And a communication method in a user equipment.