Terminal and communication method

Abstract

To control QoS (Quality of Service) in a physical layer in a radio communications system.SOLUTION: A terminal includes: a transmission unit for transmitting a notification including a physical layer QoS (Quality of Service) level indicator to a base station; and a reception unit for receiving an uplink grant from the base station. On the basis of the uplink grant, the transmission unit performs uplink transmission, to which a QoS level indicated by the QoS level indicator is applied, to the base station.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a terminal and a communication method in a wireless communication system.

Background Art

[0002] In a Universal Mobile Telecommunication System (UMTS) network, Long Term Evolution (LTE) has been standardized for the purpose of achieving a further high data rate, low latency, etc. Also, a successor system to LTE is being studied for the purpose of further broadband and high speed from LTE. Successor systems to LTE include, for example, systems called LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), New Radio (NR), etc.

[0003] In 5G, various wireless technologies and network architectures are being studied to meet the requirement of achieving a throughput of 10 Gbps or more while reducing the delay in the wireless section to 1 ms or less (for example, Non-Patent Document 1).

[0004] In NR, in the uplink (UL), PUSCH (CG PUSCH) based on CG (Configured Grant) is being studied, and in the downlink (DL), PDSCH (SPS PDSCH) based on SPS (Semi-Persistent Scheduling) is being studied.

[0005] In 3GPP Release 16, the configurations of CG PUSCH (Configured Grant Physical Uplink Shared Channel) and SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) are defined (for example, Non-Patent Document 2).

[0006] Also, in 3GPP Release 16, it is defined that the parameters of CG PUSCH and the parameters of SPS PDSCH are determined by RRC (Radio Resource Control) configuration or activation DCI (Downlink Control Information).

[0007] Also, in NR, in 3GPP Release 17, various technologies for systems called Ultra-Reliable and Low Latency Communications (URLLC) and Industrial Internet of Things (IIoT) are being studied.

[0008] In 3GPP Release 17, Extended Reality (XR) such as virtual reality (VR) and mixed reality (MX) is being studied, and XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods are being investigated. As requirements targeted by XR, aspects such as capacity, latency (delay), mobility, and energy saving are considered. Furthermore, in 3GPP Release 18, the above investigations are also being continuously carried out.

Prior Art Documents

Non-Patent Documents

[0009]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0010] XR traffic may include multiple data flows with different characteristics and requirements. For the transmission of XR traffic, it is necessary to flexibly support the required QoS (Quality of Service). However, the current QoS is mainly defined at the upper layer, making it difficult to perform flexible configuration.

[0011] The present invention has been made in view of the above points, and an object thereof is to control QoS (Quality of Service) at the physical layer in a wireless communication system.

Means for Solving the Problems

[0012] According to the disclosed technology, there is provided a terminal having a transmitter that transmits a notification including a QoS (Quality of Service) level indicator at the physical layer to a base station, and a receiver that receives an uplink grant from the base station, wherein the transmitter performs uplink transmission to the base station in which the QoS level indicated by the QoS level indicator is applied, based on the uplink grant.

Effects of the Invention

[0013] According to the disclosed technology, in a wireless communication system, QoS (Quality of Service) can be controlled at the physical layer.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

DETAILED DESCRIPTION OF THE INVENTION

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

[0016] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technology is, for example, existing LTE, but is not limited to existing LTE. In addition, the term "LTE" used in this specification shall have a broad meaning including LTE-Advanced and subsequent systems (e.g., NR) unless otherwise specified.

[0017] Also, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and signals, functions, etc. similar to these may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily specified as "NR-".

[0018] In addition, in the embodiments of the present invention, the duplex mode may be a TDD (Time Division Duplex) mode, an FDD (Frequency Division Duplex) mode, or another mode (e.g., Flexible Duplex, etc.).

[0019] In addition, in the embodiments of the present invention, the fact that wireless parameters, etc. are "configured" may mean that predetermined values are pre-configured, or that wireless parameters notified from the base station 10 or the terminal 20 are configured.

[0020] FIG. 1 is a diagram showing a configuration example of a wireless communication system in an embodiment of the present invention. As shown in FIG. 1, the wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20. Although one base station 10 and one terminal 20 are shown in FIG. 1, this is an example, and there may be a plurality of each.

[0021] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits the synchronization signal and the system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, by NR-PBCH and is also referred to as the broadcast information. The synchronization signal and the system information may be called an SSB (SS / PBCH block). As shown in FIG. 1, the base station 10 transmits the control signal or data to the terminal 20 in the DL (Downlink) and receives the control signal or data from the terminal 20 in the UL (Uplink). Both the base station 10 and the terminal 20 are capable of performing beamforming for signal transmission and reception. Also, both the base station 10 and the terminal 20 are capable of applying communication by MIMO (Multiple Input Multiple Output) to the DL or UL. Also, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) by CA (Carrier Aggregation). Further, the terminal 20 may communicate via the primary cell of the base station 10 and the primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 by DC (Dual Connectivity).

[0022] The terminal 20 is a communication device having a wireless communication function such as a smartphone, a mobile phone, a tablet, a wearable terminal, a communication module for M2M (Machine-to-Machine), etc. As shown in FIG. 1, the terminal 20 receives a control signal or data from the base station 10 in the DL and transmits a control signal or data to the base station 10 in the UL, thereby using various communication services provided by the wireless communication system. Further, the terminal 20 receives various reference signals transmitted from the base station 10 and performs measurement of the propagation path quality based on the reception result of the reference signal.

[0023] <CG PUSCH> Next, CG PUSCH will be described. CG PUSCH is a method of performing UL transmission using PUSCH based on a UL grant set by a higher layer (for example, it may be called a configured grant, a Configured UL Grant, etc.). In CG PUSCH, UL resources have already been allocated to the terminal 20, and the terminal 20 can spontaneously perform UL transmission using the set resources, so the realization of low-latency communication can be expected.

[0024] In 3GPP Release 16, two types of CG PUSCH, namely Type 1 and Type 2, were defined.

[0059] The activation / deactivation of Type 1 CG PUSCH depends only on RRC-configuration and does not depend on DCI. In Type 1 CG PUSCH, the parameters used for uplink transmission (which may also be referred to as CG parameters, Configured Grant Configuration information, etc.) are set for terminal 20 using only upper layer signaling. Specifically, the parameters of Type 1 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant". That is, the base station 10 uses "ConfiguredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant" to instruct terminal 20 of the uplink transmission parameters. Terminal 20 stores the received parameters as a configured grant.

[0025] When Type 1 CG PUSCH is activated, terminal 20 may determine that one or more configured grants are triggered (or activated), and perform PUSCH transmission without a dynamic grant using the configured resources (which may also be referred to as CG resources, transmission occasions, etc.).

[0026] The activation / deactivation of Type 2 CG PUSCH depends on RRC-configuration and DCI. One DCI can activate only one CG PUSCH and can deactivate multiple CG PUSCHs. In Type 2 CG PUSCH, the parameters used for uplink transmission are set for the terminal 20 using upper layer signaling. Also, some of the parameters used for uplink transmission are notified to the terminal by DCI. Specifically, the transmission parameters of Type 2 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config" and "activation DCI". That is, the base station 10 instructs the terminal 20 of the uplink transmission parameters using "ConfiguredGrantConfig", "pusch-Config" and "activation DCI". The terminal 20 stores the received parameters.

[0027] When the Type 2 CG PUSCH is activated and the activation DCI is notified, the terminal 20 may determine that one or more configured grants are triggered (or activated), and perform PUSCH transmission without a dynamic grant using the resources configured in the upper layer. The activation DCI may be CRC (Cyclic Redundancy Check) scrambled by a predetermined identifier (for example, CS-RNTI: Configured Scheduling RNTI). Note that the activation DCI may be used for control such as deactivation and retransmission of the configured grant.

[0028] Also, the terminal 20 may release (which may be called release, deactivate, etc.) the resources (PUSCH) corresponding to the configured grant based on a DCI that deactivates the configured grant or the expiration of a predetermined timer (elapse of a predetermined time).

[0029] <SPS PDSCH> Next, the SPS PDSCH will be described. In the SPS PDSCH, periodic resources for downlink (DL) Semi-Persistent Scheduling (SPS) are configured by the upper layer. The activation / deactivation (release) of transmission using the said resources in the SPS PDSCH depends on the activation DCI. The said activation DCI may be CRC (Cyclic Redundancy Check) scrambled by a predetermined identifier (for example, CS-RNTI: Configured Scheduling RNTI).

[0030] In the SPS PDSCH, parameters used for downlink transmission (which may also be called SPS parameters, Semi-Persistent Scheduling configuration information, etc.) are set for the terminal 20 using upper layer signaling. Also, a part of the parameters used for downlink transmission is notified to the terminal by the DCI. Specifically, the transmission parameters of the SPS PDSCH are provided by "sps-Config" and "activation DCI". That is, the base station 10 instructs the terminal 20 of the downlink transmission parameters using "sps-Config" and "activation DCI". The terminal 20 stores the received parameters.

[0031] <Parameters of CG PUSCH> For Type 1 and / or Type 2 CG PUSCH, the parameters in ConfiguredGrantConfig (hereinafter referred to as "CGC-CG parameter(s)") include, for example, the following. When the CGC-CG parameter is provided by both ConfiguredGrantConfig and pusch-Config, the terminal 20 may apply the CGC-CG parameter indicated in ConfiguredGrantConfig to PUSCH transmission. Also, when there is a CGC-CG parameter not provided by ConfiguredGrantConfig, the terminal 20 may apply the CGC-CG parameter indicated in pusch-Config to PUSCH transmission.

[0032] (Examples of CGC-CG parameters) ·periodicity: Used to indicate the period of PUSCH transmission corresponding to the configured grant. ·repK: Used to indicate the number of repetitions of PUSCH transmission. ·repK-RV: Used to indicate information regarding the redundancy version of repeated PUSCH transmission. ·frequencyHopping: Used to enable either in-slot frequency hopping or inter-slot frequency hopping. If this field does not exist, frequency hopping may not be applied. ·cg-DMRS-Configuration: Used to indicate the DMRS configuration of PUSCH corresponding to the configured grant. ·mcs-Table: Used to indicate the MSC table that the terminal 20 uses for PUSCH without transform precoding. If this field does not exist, the terminal 20 may use the 64QAM table. ·mcs-TableTransformPrecoder: Used to indicate the MSC table that terminal 20 uses for PUSCH with transform precoding. If this field does not exist, terminal 20 may use the 64QAM table. ·uci-OnPUSCH: Used to indicate information regarding the transmission of UCI using PUSCH. ·resourceAllocation: Used to indicate that any one of 'Resource Allocation Type 0', 'Resource Allocation Type 1', and 'Dynamic Switch' is set. ·rbg-Size: Used to indicate the RBG size of PUSCH. ·powerControlLoopToUse: Used to indicate the closed control loop applied to PUSCH transmission. ·p0-PUSCH-Alpha: Used to calculate the PUSCH transmission power. ·transformPrecoder: Used to indicate whether to select transform precoding for PUSCH transmission. ·phy-PriorityIndex: Used to indicate the PHY priority of CG PUSCH in at least PHY layer collision handling. Note that value p0 indicates low priority and value p1 indicates high priority. ·cg-nrofHARQ-Process: Used to indicate the HARQ process number. ·cg-nrofSlots: Used to indicate the number of allocated slots set by the grant period following the time instance set by the grant offset. ·betaOffsetCG-UCI: Used to indicate the beta offset of CG-UCI in CG-PUSCH. ·configuredGrantTimer: It is used to indicate the initial value of the configured grant timer as a multiple of the periodicity. When the cg-RetransmissonTimer is configured and different configured grants on the same BWP share the HARQ process, the same value is set for the periodicity of the configuredGrantTimer in the configuration that shares the HARQ process on this BWP.

[0033] For Type 1 CG PUSCH, the parameters in rrc-ConfiguredUplinkGrant (hereinafter referred to as "rrc-CUG-CG parameter(s)") are, for example, as follows. Note that rrc-ConfiguredUplinkGrant is used to indicate the information of the grant configured by Type 1 CG PUSCH.

[0034] (Examples of rrc-CUG-CG parameters) ·timeDomainOffset: It is used to indicate the offset related to the system frame numbered 0. ·timeDomainAllocation: It is used to indicate the combination of the mapping type of PUSCH, the start symbol of PUSCH, and the number of consecutive symbols to be allocated. ·frequencyDomainAllocation: It is used to indicate the frequency resource allocation of PUSCH. ·antennaPort: It is used to indicate the antenna port information for PUSCH transmission. ·dmrs-SeqInitialization: An identifier used for scrambling the DMRS sequence for PUSCH transmission. ·precodingAndNumberOfLayers: It is used to indicate the precoding and the number of layers for PUSCH transmission. ·srs-ResourceIndicator: It is used to indicate the SRS (Sounding Reference Signal) resource to be used. ·mcsAndTBS: It is used to indicate the modulation order, target coding rate, and size of the transport block. ·frequencyHoppingOffset: It is used to indicate the value of the frequency hopping offset. ·pathlossReferenceIndex: It is used to indicate the reference signal used for PUSCH path loss estimation. ·pusch-RepTypeIndicator: It is used by terminal 20 to indicate whether to follow the operation for PUSCH repetition type A or the operation for PUSCH repetition type B for each Type 1 configured grant configuration. value pusch-RepTypeA enables "PUSCH repetition type A", and value pusch-RepTypeB enables "PUSCH repetition type B". ·frequencyHoppingPUSCH-RepTypeB: It is used to indicate the frequency hopping pattern of Type 1 CG when pusch-RepTypeIndicator is set to "pusch-RepTypeB". Value interRepetition enables "Inter-repetition frequency hopping", and value interSlot enables "Inter-slot frequency hopping". Note that if this field does not exist, frequency hopping is not enabled for Type 1 CG.

[0035] For Type 2 CG PUSCH, the parameters indicated by the activation DCI (hereinafter referred to as "DCI-CG parameter(s)") include, for example, the following.

[0036] (Examples of DCI-CG parameters) ·timeDomainAllocation: Used to indicate the combination of start symbol and length and the PUSCH mapping type. ·frequencyDomainAllocation: Used to indicate the resource allocation in the frequency domain. ·MCS index: Used to indicate the index of MCS (Modulation and Coding Scheme). ·antenna port indication: Used to indicate the antenna port. ·precoding and number of layers indication: Used to indicate precoding and the number of layers. ·SRS resource indicator: Used to indicate the resource for SRS (Sounding Reference Signal). ·power control related parameter indication: Used to indicate the parameters related to transmission power control.

[0037] <Parameters of SPS PDSCH> For SPS PDSCH, the parameters in SPS-Config (hereinafter referred to as "SC-SPS parameter(s)") include, for example, the following.

[0038] (Examples of SC-SPS parameters) ·periodicity: Used to indicate the period of SPS PDSCH. ·n1PUCCH-AN: Used to indicate the HARQ-ACK (Hybrid automatic repeat request Acknowledgement) PUCCH resource for SPS PDSCH. ·mcs-Table: Used to indicate the MCS table applied to the reception of SPS PDSCH. · pdsch-AggregationFactor: It is used to indicate the number of repetitions of PDSCH transmission.

[0039] For SPS PDSCH, the parameters indicated by the activation DCI (hereinafter referred to as "DCI-SPS parameter(s)") include, for example, the following.

[0040] (Examples of DCI-SPS parameters) · timeDomainAllocation: It is used to indicate the combination of the start symbol and length and the PDSCH mapping type. · frequencyDomainAllocation: It is used to indicate the resource allocation in the frequency domain. · MCS index: It is used to indicate the index of MCS (Modulation and Coding Scheme). · TCI state indication: It is used to indicate the state of TCI (Transmission Configuration Indicator) for PDSCH. · antenna port indication: It is used to indicate the antenna port. · priority of HARQ-ACK: It is used to indicate the priority of HARQ-ACK. · K1: It is used to indicate the number of slots from the slot in which the data is scheduled on the PDSCH to the slot in which the HARQ-ACK for the PDSCH is transmitted.

[0041] <Other parameters> The parameters other than the above notified from the base station 10 to the terminal 20 (hereinafter referred to as "other-CG / SPS parameter(s)") include, for example, the following.

[0042] (Examples of other-CG / SPS parameters) ·PDSCH / PUSCH length: Used to indicate the length of PDSCH and / or PUSCH. ·number of PRBs: Used to indicate the number of PRBs (Physical Resource Blocks).

[0043] FIG. 2 is a diagram showing an example of the arrival timing of XR traffic and CG / SPS opportunities. FIG. 2 is a diagram showing an example of the relationship between the arrival timing of XR traffic and the transmitting occasion of CG-PUSCH and / or the monitoring occasion of SPS-PDSCH. Note that hereinafter, the "transmitting occasion of CG-PUSCH and / or the monitoring occasion of SPS-PDSCH" may be abbreviated as "CG / SPS opportunity" or "opportunity".

[0044] XR traffic is assumed to arrive periodically according to the FPS (frames per second). In NR, as shown in FIG. 2, while the arrival period of XR traffic is a non-integer value such as 16.67 ms, the periodicity of CG / SPS opportunities is defined to be an integer value such as 16 ms or 17 ms. Therefore, as shown in FIG. 2, waiting time may occur.

[0045] Here, XR traffic may include a plurality of data flows with different characteristics and requirements. It is necessary to flexibly support the required QoS (Quality of Service) for the transmission of XR traffic. However, the current QoS has mainly been defined at the upper layer. When data at the upper layer is transmitted by the physical layer, different XR traffic or XR flows are mixed at the physical layer.

[0046] If the determination of transmission parameters or physical layer processing (e.g., handling of UE internal collisions) is based on the data with the highest QoS level requirement among the mixed data, the resource utilization efficiency will decrease.

[0047] Also, when determining transmission parameters or performing physical layer processing (e.g., handling in-UE collisions) based on the data with the lowest QoS level requirement among the mixed data, the QoS requirements may not be satisfied in some data.

[0048] Therefore, by supporting a QoS level indicator in the physical layer, efficient physical layer processing (e.g., determining transmission parameters, handling inter-UE or in-UE collisions, etc.) for data flows with different QoS requirements can be achieved. As a result, an improvement in user experience and an increase in system capacity are expected.

[0049] The physical layer may perform differentiation for different QoS levels. A physical layer indicator indicating the QoS level may be introduced. For example, the physical layer QoS level indicator may be composed of up to X bits and may indicate QoS levels up to 2 to the power of X. X may be defined by the specification or set by RRC signaling.

[0050] Table 1 is an example of the physical layer QoS level indicator with X being 1. Table 2 is an example of the physical layer QoS level indicator with X being 2. Table 3 is an example of the physical layer QoS level indicator with X being 3.

[0051]

Table 1

[0052]

Table 2

[0053]

Table 3

[0054] As shown in Table 1, two QoS levels may be notified by the physical layer QoS level indicator. As shown in Table 2, four QoS levels may be notified by the physical layer QoS level indicator. As shown in Table 3, eight QoS levels may be notified by the physical layer QoS level indicator.

[0055] The mapping between the value of the physical layer QoS level indicator and the corresponding QoS level or QoS requirement may be defined by the specification or set by RRC signaling. The mapping may be one-to-one or one-to-many as shown in Table 1. When the number of bits of the physical layer QoS level indicator is different, the mapping may be set separately for each number of bits.

[0056] The physical layer QoS level indicator may be used for processing data flows with different QoS requirements. For example, scheduling assistance information, and / or determination of transmission parameters, and / or DL / UL collision handling within the UE, and / or DL / UL collision handling between UEs may be performed by the physical layer QoS level indicator.

[0057] FIG. 3 is a diagram for explaining an example (1) of communication related to QoS in an embodiment of the present invention. As shown in step S11, the terminal 20 may report the physical layer QoS level indicator to the base station 10 together with an SR (Scheduling request) or a BSR (Buffer status report). The base station 10 may determine the scheduling parameters and scheduling priority of the terminal 20 based on the reported information. In the subsequent step S12, the base station 10 transmits a UL grant to the terminal 20. In the subsequent step S13, the terminal 20 transmits a PUSCH to the base station 10.

[0058] FIG. 4 is a diagram for explaining an example (2) of communication related to QoS in an embodiment of the present invention. As shown in step S21, the base station 10 may notify the terminal 20 of a QoS level indicator together with a UL grant. Based on the notification, the terminal 20 may determine related scheduling parameters such as, for example, the interpretation of DCI fields with different QoS level values, or may perform UE-internal DL / UL collision processing with a finer granularity based on the QoS level for UL prioritization, or may perform UE-inter DL / UL collision processing with a finer granularity based on the QoS level for, for example, DL preemption or UL cancellation. In the subsequent step S22, the terminal 20 transmits a PUSCH to the base station 10.

[0059] FIG. 5 is a diagram for explaining an example (3) of communication related to QoS in an embodiment of the present invention. As shown in step S31, the base station 10 may notify the terminal 20 of a QoS level indicator together with a DL grant. Based on the notification, the terminal 20 may determine related scheduling parameters such as, for example, the interpretation of DCI fields with different QoS level values, or may perform UE-internal DL / UL collision processing with a finer granularity based on the QoS level for UL prioritization, or may perform UE-inter DL / UL collision processing with a finer granularity based on the QoS level for, for example, DL preemption or UL cancellation. In the subsequent step S32, the base station 10 transmits a PDSCH to the terminal 20.

[0060] FIG. 6 is a diagram for explaining an example (4) of communication related to QoS in an embodiment of the present invention. As shown in steps S41 and S42, the terminal 20 may notify the base station 10 of a QoS level indicator by means of a MAC-CE or CG-UCI associated with the PUSCH. The base station 10 may determine decoding parameters based on the received information.

[0061] The base station 10 may notify the terminal 20 of the physical layer QoS level indicator. The physical layer QoS level indicator may be set by RRC signaling. For example, the physical layer QoS level indicator may be set by RRC signaling for SPS-PDSCH or CG-PUSCH setting, or may be set by RRC signaling for a group of SPS-PDSCH or CG-PUSCH. The SPS-PDSCH or CG-PUSCH with the physical layer QoS level indicator indicates the QoS level of the DL or UL carrier by the SPS-PDSCH or CG-PUSCH. For the SPS-PDSCH or CG-PUSCH without the physical layer QoS level indicator, the default QoS level may be applied. For example, the highest, lowest, or intermediate QoS level may be applied.

[0062] The physical layer QoS level indicator may be set by RRC signaling for a DCI format. The physical layer QoS level indicator set for the DCI format may be applied to the PDSCH or PUSCH scheduled by the DCI format, or may be applied to the SPS-PDSCH or CG-PUSCH activated by the DCI format.

[0063] The DCI format with the physical layer QoS level indicator may be defined by the specification. For example, the physical layer QoS level indicator may be set for DCI format 1_1 / 0_1 and / or DCI format 1_2 / 0_2. For the DCI format without the physical layer QoS level indicator, the default QoS level may be applied to the PDSCH or PUSCH scheduled by the DCI format and / or the SPS-PDSCH or CG-PUSCH activated by the DCI format. For example, the highest, lowest, or intermediate QoS level may be applied.

[0064] The physical layer QoS level indicator may be notified by DCI. The DCI format for the physical layer QoS level indicator may be an existing DCI format that schedules PDSCH or PUSCH. For example, it may be DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, or DCI format 1_2. When accompanied by an existing RNTI, the physical layer QoS level indicator may be notified by a new DCI field. When accompanied by a new RNTI, the physical layer QoS level indicator may be explicitly notified by a DCI field. Alternatively, in the case of a new DCI format with an existing or new RNTI, the physical layer QoS level indicator may be explicitly notified by a DCI field.

[0065] For example, the DCI field of the physical layer QoS level indicator may notify one physical layer QoS level indicator value from a plurality of candidate values. The candidate values may be defined by the specification or set by RRC signaling. The bit length of the field of the physical layer QoS level indicator may be determined by the number of the candidate values. For example, the candidate values of the physical layer QoS level indicator may be defined by the specification. For example, the candidate values of the physical layer QoS level indicator may be notified by RRC signaling. The candidate values may be set for each DCI format or for each serving cell.

[0066] Whether a field for a physical layer QoS level indicator exists in a DCI format may be set by RRC signaling or may be defined by the specification. For example, a new RRC parameter may notify whether the field exists in the DCI format. For example, when the UE 20 reports to the base station 10 the UE capability indicating whether it supports the physical layer QoS level indicator, the UE 20 may assume that the field always exists in a predetermined DCI format (for example, DCI format 1_1 / 0_1 and / or DCI format 1_2 / 0_2).

[0067] The dynamic grant of PDSCH / PUSCH may be scheduled by a DCI format in which the physical layer QoS level indicator is set. The notified physical layer QoS level indicator may be applied to the scheduled PDSCH / PUSCH.

[0068] The dynamic grant of PDSCH / PUSCH may be scheduled by a DCI format in which the physical layer QoS level indicator is not set. A default QoS level may be applied to the scheduled PDSCH / PUSCH. For example, the highest, lowest, or intermediate QoS level may be applied. The default QoS level may be defined by the specification or may be set for each DCI format or for all DCI formats by RRC signaling. Also, the QoS level may be set for the scheduled PDSCH / PUSCH based on the last DCI format with the physical layer QoS level indicator. If there is no last DCI format with the physical layer QoS level indicator, the default QoS level may be applied.

[0069] When the physical layer QoS level indicator is not set for SPS / CG by RRC signaling, the terminal 20 may operate as shown in 1)-4) below in the SPS-PDSCH or CG-PUSCH activated by the DCI format in which the physical layer QoS level indicator is set.

[0070] 1) The terminal 20 may apply the physical layer QoS level indicator notified by the DCI format to all SPS-PDSCH or CG-PUSCH. That is, the physical layer QoS level indicator notified by the DCI format may be applied to the first SPS-PDSCH or CG-PUSCH after activation and subsequent SPS-PDSCH or CG-PUSCH. Note that the terminal 20 does not have to assume a predetermined value for the notified physical layer QoS level indicator, nor does it have to assume that it is not a predetermined value. For example, the terminal 20 may assume that the notified physical layer QoS level indicator is a predefined value, or it may assume that it is not a predefined value.

[0071] 2) The terminal 20 may apply the physical layer QoS level indicator notified by the DCI format only to the first SPS-PDSCH or CG-PUSCH after activation, and a default QoS level (highest, lowest, or intermediate QoS level) may be applied to subsequent SPS-PDSCH or CG-PUSCH.

[0072] 3) The terminal 20 does not have to apply the physical layer QoS level indicator notified by the DCI format to the SPS-PDSCH or CG-PUSCH. That is, the notified physical layer QoS level indicator may be ignored. The terminal 20 may apply a default QoS level (highest, lowest, or intermediate QoS level) to the SPS-PDSCH or CG-PUSCH.

[0073] 4) The terminal 20 does not have to assume such a case. That is, it does not have to assume that the physical layer QoS level indicator is notified by the DCI format.

[0074] When the physical layer QoS level indicator is not set in the SPS / CG by RRC signaling and the SPS-PDSCH or CG-PUSCH is activated by a DCI format in which the physical layer QoS level indicator is not set, the default QoS level may be applied to the SPS-PDSCH or CG-PUSCH. For example, the highest, lowest, or intermediate QoS level may be applied. The default QoS level may be defined by the specification or set by RRC signaling for each SPS / CG setting or for all SPS / CG settings.

[0075] When the physical layer QoS level indicator is set in the SPS / CG by RRC signaling, the terminal 20 may operate as shown in 1)-5) below in the SPS-PDSCH or CG-PUSCH activated by the DCI format in which the physical layer QoS level indicator is set.

[0076] 1) It does not have to assume different physical layer QoS level indicator values between the notification by the DCI format and the notification by the RRC signaling. The same value may be applied to all SPS-PDSCHs or CG-PUSCHs. That is, the same value may be applied to the first SPS-PDSCH or CG-PUSCH and subsequent SPS-PDSCHs or CG-PUSCHs.

[0077] 2) The notification by DCI format may overwrite the notification by RRC signaling. That is, the physical layer QoS level indicator notified by DCI format may be applied to all SPS-PDSCHs or CG-PUSCHs. That is, the physical layer QoS level indicator notified by DCI format may be applied to the first SPS-PDSCH or CG-PUSCH and subsequent SPS-PDSCHs or CG-PUSCHs.

[0078] 3) The notification by DCI format may overwrite the notification by RRC signaling only for the first SPS-PDSCH or CG-PUSCH. That is, the physical layer QoS level indicator notified by DCI format may be applied to the first SPS-PDSCH or CG-PUSCH. A default QoS level may be applied to subsequent SPS-PDSCHs or CG-PUSCHs, for example, the highest, lowest, or intermediate QoS level may be applied.

[0079] 4) The physical layer QoS level indicator by RRC signaling may be applied to all SPS-PDSCHs or CG-PUSCHs. That is, the physical layer QoS level indicator by RRC signaling may be applied to the first SPS-PDSCH or CG-PUSCH and subsequent SPS-PDSCHs or CG-PUSCHs.

[0080] 5) The terminal 20 does not have to assume such a case. That is, when the physical layer QoS level indicator is set in the SPS / CG setting by RRC signaling, it does not have to assume that the physical layer QoS level indicator is notified by DCI format.

[0081] When the physical layer QoS level indicator is set for SPS / CG by RRC signaling, in the SPS-PDSCH or CG-PUSCH activated by a DCI format without the physical layer QoS level indicator set, the terminal 20 may apply the physical layer QoS level indicator set by RRC signaling to all SPS-PDSCH or CG-PUSCH. That is, the physical layer QoS level indicator by RRC signaling may be applied to the first SPS-PDSCH or CG-PUSCH and subsequent SPS-PDSCH or CG-PUSCH.

[0082] Assume a case where multiple PDSCH / PUSCH are scheduled by DCI. For a predetermined DCI format (DCI format 1_1 / 0_1, and / or DCI format 1_2 / 0_2) with a TDRA (Time domain resource allocation) table set including at least one row having an SLIV (Start and length indicator value) exceeding 1, the terminal 20 may operate as shown in 1)-3) below.

[0083] 1) The terminal 20 does not have to assume that the field of the physical layer QoS level indicator is set in the DCI format.

[0084] 2) When the field of the physical layer QoS level indicator is set in the DCI format, the terminal 20 may assume only one field of the physical layer QoS level indicator. The physical layer QoS level indicator value by the field may be applied to all scheduled PDSCH / PUSCH, or may be applied only to the first PDSCH / PUSCH.

[0085] 3) When a field for a physical layer QoS level indicator is set in the DCI format, the terminal 20 may assume a plurality of fields for the physical layer QoS level indicator. Each of the fields may be individually applied to the scheduled PDSCH / PUSCH. The number of the fields may be determined based on the maximum number of PDSCHs or PUSCHs scheduled by the DCI format. Alternatively, each of the fields may be individually applied to a group of scheduled PDSCH / PUSCH. The number of the fields may be determined based on the maximum number of the groups of PDSCH / PUSCH for the physical layer QoS level indicator.

[0086] The physical layer QoS level indicator may be notified by a MAC-CE. For example, the MAC-CE associated with a preceding PDSCH may notify the physical layer QoS level indicator of one or more subsequent PDSCHs, or may notify the physical layer QoS level indicator of one or more PDSCHs in the first slot after the k-th slot of the MAC-CE slot, or may notify the physical layer QoS level indicator of one or more PDSCHs within a predetermined slot after the k-th slot of the MAC-CE slot.

[0087] The physical layer QoS level indicator may be notified from the terminal 20 to the base station 10. The terminal 20 may report the physical layer QoS level indicator to the base station 10 by an extended SR report. The SR-PUCCH may be extended to notify information other than requests. For example, in order to notify the base station of the QoS level of UL transmission data, the physical layer QoS level indicator may be included in the extended SR-PUCCH.

[0088] When the UL transmission data has a plurality of QoS levels, the extended SR may notify only the physical layer QoS level indicator value of one of the maximum, minimum, or intermediate levels among the plurality of QoS levels.

[0089] Also, when the UL transmission data has multiple QoS levels, the extended SR may notify the multiple QoS levels. For example, the extended SR may notify the physical layer QoS level indicator up to X. X may be defined in the specification or set by RRC signaling. When the number of actual physical layer QoS level indicators for the UL transmission data is m which is smaller than X, reserved values indicating multiple QoS levels may be defined for (X - m) blocks.

[0090] FIG. 7 is a diagram for explaining an example (1) of SR in an embodiment of the present invention. As shown in FIG. 7, for example, with a 3-bit length, together with a positive or negative SR, a physical layer QoS level indicator may be notified. In the example of FIG. 7, up to 4 QoS levels can be notified by a 2-bit physical layer QoS level indicator.

[0091] FIG. 8 is a diagram for explaining an example (2) of SR in an embodiment of the present invention. As shown in FIG. 8, for example, with a 5-bit length, together with a positive or negative SR, a 2-bit long physical layer QoS level indicator may be notified. In the example of FIG. 8, up to 4 QoS levels can be notified per 2-bit physical layer QoS level indicator.

[0092] FIG. 9 is a diagram for explaining an example (3) of SR in an embodiment of the present invention. As shown in FIG. 9, for example, with a 3-bit length, a physical layer QoS level indicator jointly coded with a positive or negative SR may be notified. In the example of FIG. 9, up to 7 QoS levels can be notified by the physical layer QoS level indicator.

[0093] FIG. 10 is a diagram for explaining an example (4) of SR in the embodiment of the present invention. As shown in FIG. 10, for example, a physical layer QoS level indicator joint-coded with two positive or negative SRs and having a 6-bit length may be notified. In the example of FIG. 10, up to seven QoS levels can be notified for each physical layer QoS level indicator.

[0094] The terminal 20 may report the physical layer QoS level indicator to the base station 10 by an extended BSR report. The BSR report may be extended to notify the base station 10 of the buffer status and the QoS level of the pending UL transmission data. The extended BSR report with the physical layer QoS level indicator may be a long BSR, a short BSR, or a new BSR format (i.e., a MAC-CE with a new LCID).

[0095] The terminal 20 may report one buffer status value and one physical layer QoS level indicator value to the base station 10. For example, the terminal 20 may report the total buffer status and one physical layer QoS level indicator value, which is the maximum, minimum, or intermediate one among the multiple physical layer QoS level indicator values of the buffered UL transmission data, to the base station 10.

[0096] The terminal 20 may report a plurality of buffer status values and a plurality of physical layer QoS level indicator values to the base station 10.

[0097] The terminal 20 may report the buffer status for each defined QoS level in the BSR report.

[0098] FIG. 11 is a diagram for explaining an example (1) of BSR in the embodiment of the present invention. As shown in FIG. 11, when there is no UL transmission data at a predetermined QoS level, the terminal 20 may report the BSR with the buffer size set to 0. The terminal 20 may report the BSR in ascending or descending order of the QoS level or QoS group index.

[0099] FIG. 12 is a diagram for explaining an example (2) of the BSR in the embodiment of the present invention. As shown in FIG. 12, when there is no UL transmission data at a predetermined QoS level, the buffer size at the predetermined QoS level may not be reported. The terminal 20 may report the BSR in ascending or descending order of the QoS level or the QoS group index.

[0100] The terminal 20 may report the buffer status for each group of QoS levels in the BSR report. When there is no UL transmission data in a group of a predetermined QoS level, the terminal 20 may report the BSR with the buffer size set to 0. When there is no UL transmission data in a group of a predetermined QoS level, the buffer size at the predetermined QoS level may not be reported.

[0101] FIG. 13 is a diagram for explaining an example (3) of the BSR in the embodiment of the present invention. As shown in FIG. 13, the terminal 20 may report a BSR including a plurality of buffer sizes corresponding to QoS level values in ascending or descending order of the buffer status values.

[0102] The terminal 20 may report a physical layer QoS level indicator to the base station 10 by means of a MAC-CE or CG-UCI associated with the PUSCH. Further, the terminal 20 may report a physical layer QoS level indicator for the PUSCH, or may report a mapping relationship between the physical layer QoS level indicator and the activated CG setting.

[0103] The terminal 20 may not assume a joint operation between the physical layer QoS level indicator and the physical layer priority. The DCI format described below may be, for example, DCI format 1_1 / 0_1 / 1_2 / 0_2).

[0104] When the physical layer priority is set in the DCI format, the terminal 20 does not have to assume that the field of the physical layer QoS level indicator is simultaneously set in the DCI format by RRC signaling.

[0105] Also, when the physical layer priority is set in the DCI format and the terminal 20 is such that the field of the physical layer QoS level indicator is simultaneously set by RRC signaling, the set physical layer QoS level indicator may be ignored. The terminal 20 may determine the priority index value 0 or the priority index 1 based on the DCI notification.

[0106] Also, when the physical layer QoS level indicator is set by RRC signaling for a group of SPS / CG settings, the terminal 20 does not have to assume that the SPS / CG setting is activated by a DCI format in which the physical layer priority field is set.

[0107] Also, when the physical layer QoS level indicator is set by RRC signaling for a group of SPS / CG settings and the SPS / CG setting is activated by a DCI format in which the physical layer priority field is set, the terminal 20 may ignore the physical layer QoS level indicator. The terminal 20 may determine the priority index value 0 or the priority index 1 based on the DCI notification.

[0108] When the physical layer priority is set by the DCI format, the terminal 20 does not have to assume that the field of the physical layer QoS level indicator is simultaneously set in the DCI format.

[0109] The physical layer QoS level indicator and the physical layer priority may be applied independently. The physical layer priority indicator is used to notify a physical layer priority index value of 0 or 1, and may be used for in-UE priority / multiplexing and / or inter-UE priority / multiplexing (e.g., DL preemption, UL cancellation). The physical layer QoS indicator is used to notify the QoS level of the physical layer, and may be used to differentiate QoS processing for multiple data flows, may be used for scheduling assistance, may be used for determining transmission parameters, or may be used for extended in-UE / inter-UE prioritization considering the physical layer QoS level.

[0110] Also, the physical layer QoS level indicator and the physical layer priority may be jointly operated. The physical layer priority indicator and the physical layer QoS level indicator may be combined to determine the QoS priority of data. For example, a 1-bit physical layer priority indicator (index 0 or index 1) and an X-bit physical layer QoS level indicator may be combined into an (X + 1)-bit QoS priority indicator value, and the 1 bit of the physical layer priority indicator may be added to the beginning or the end of the X bits of the physical layer QoS level indicator.

[0111] In the above embodiments, when the physical layer QoS level indicator is notified from the base station 10 to the terminal 20, or when the physical layer QoS level indicator is notified from the terminal 20 to the base station 10, the granularity of the QoS level may be different. Also, the number of bits of the physical layer QoS level indicator may be different. The mapping between the physical layer QoS level indicator value and the corresponding QoS level may be defined or set separately.

[0112] The physical layer QoS level indicator may be set by upper layer parameters, reported as UE capabilities by the terminal 20, defined in the specification, or determined by upper layer parameters and reported by UE capabilities.

[0113] The operation of the terminal 20 reporting the physical layer QoS level indicator to the base station 10 may be applied to the reporting of QoS level information in the upper layer.

[0114] UE capabilities indicating whether to support the physical layer QoS level indicator may be defined. UE capabilities indicating whether to support the notification of the physical layer QoS level indicator by RRC signaling, DCI, or MAC-CE may be defined. UE capabilities indicating whether to support the reporting of the physical layer QoS level indicator associated with SR, BSR, MAC-CE, or CG-UCI may be defined.

[0115] According to the above embodiments, by introducing the physical layer QoS level indicator and notifying from the base station 10 to the terminal 20 or from the terminal 20 to the base station 10, flexible QoS control can be performed in the physical layer.

[0116] That is, in a wireless communication system, QoS (Quality of Service) can be controlled in the physical layer.

[0117] (Device Configuration) Next, functional configuration examples of the base station 10 and the terminal 20 that execute the processes and operations described so far will be described. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each be provided with only some of the functions in the embodiments.

[0118] <Base Station 10> FIG. 14 is a diagram showing an example of the functional configuration of the base station 10 in the embodiment of the present invention. As shown in FIG. 14, the base station 10 includes a transmission unit 110, a reception unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in FIG. 14 is merely an example. As long as the operations according to the embodiment of the present invention can be executed, the functional classification and the names of the functional units may be any.

[0119] The transmission unit 110 includes a function of generating a signal to be transmitted to the terminal 20 side and wirelessly transmitting the signal. Further, the transmission unit 110 transmits an inter-network node message to another network node. The reception unit 120 includes a function of receiving various signals transmitted from the terminal 20 and obtaining information of, for example, a higher layer from the received signals. Further, the transmission unit 110 has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. Further, the reception unit 120 receives an inter-network node message from another network node.

[0120] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to QoS setting.

[0121] The control unit 140 performs control related to QoS setting as described in the embodiment. Further, the control unit 140 executes scheduling. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120.

[0122] <Terminal 20> FIG. 15 is a diagram showing an example of the functional configuration of the terminal 20 in the embodiment of the present invention. As shown in FIG. 15, the terminal 20 includes a transmission unit 210, a reception unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in FIG. 15 is merely an example. As long as the operations according to the embodiment of the present invention can be executed, the functional classification and the names of the functional units may be any.

[0123] The transmission unit 210 creates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The reception unit 220 wirelessly receives various signals and acquires signals of a higher layer from the received physical layer signals. Further, the reception unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. Also, for example, the transmission unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to another terminal 20 as D2D communication, and the reception unit 220 receives PSCCH, PSSCH, PSDCH, or PSBCH, etc. from another terminal 20.

[0124] The setting unit 230 stores various setting information received from the base station 10 by the reception unit 220. Also, the setting unit 230 stores preset setting information. The content of the setting information is, for example, information related to QoS setting.

[0125] As described in the embodiment, the control unit 240 performs control related to QoS setting. The functional unit related to signal transmission in the control unit 240 may be included in the transmission unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the reception unit 220.

[0126] (Hardware Configuration) The block diagrams (Figs. 14 and 15) used in the description of the above embodiments show blocks of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (e.g., using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0127] Functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication (communicating), forwarding, configuration (configuring), reconfiguration (reconfiguring), allocation (allocating, mapping), assignment (assigning), etc. For example, a functional block (component) that functions to transmit is referred to as a transmitting unit or a transmitter. In any case, as described above, the realization method is not particularly limited.

[0128] For example, the base station 10, the terminal 20, etc. in an embodiment of the present disclosure may function as a computer that performs the processing of the wireless communication method of the present disclosure. Fig. 16 is a diagram showing an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The above-described base station 10 and terminal 20 may physically be configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0129] In the following description, the term "apparatus" can be read as a circuit, device, unit, etc. The hardware configurations of the base station 10 and the terminal 20 may be configured to include one or more of each apparatus shown in the figure, or may be configured without including some apparatuses.

[0130] Each function in the base station 10 and the terminal 20 is realized by loading a predetermined software (program) onto hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs operations and controls communication by the communication device 1004, or controls at least one of reading and writing data in the storage device 1002 and the auxiliary storage device 1003.

[0131] The processor 1001 controls the entire computer by operating, for example, an operating system. The processor 1001 may be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, etc. For example, the above-described control units 140, 240, etc. may be realized by the processor 1001.

[0132] Further, the processor 1001 reads a program (program code), software module, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes according to these. As the program, a program for causing a computer to execute at least a part of the operations described in the above embodiments is used. For example, the control unit 140 of the base station 10 shown in FIG. 14 may be stored in the storage device 1002 and realized by a control program operating on the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in FIG. 15 may be stored in the storage device 1002 and realized by a control program operating on the processor 1001. Although it has been described that the above various processes 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. Note that the program may be transmitted from a network via a telecommunication line.

[0133] The storage device 1002 is a computer-readable recording medium, and may be constituted by at least one of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may be referred to as a register, cache, main memory (main storage device), etc. The storage device 1002 can store a program (program code), software module, etc. executable for implementing the communication method according to an embodiment of the present disclosure.

[0134] The auxiliary storage device 1003 is a computer-readable recording medium, which may be constituted by at least one of, for example, optical discs such as CD-ROM (Compact Disc ROM), hard disk drives, flexible disks, magneto-optical disks (e.g., compact disks, digital versatile disks, Blu-ray (registered trademark) disks), smart cards, flash memories (e.g., cards, sticks, key drives), floppy (registered trademark) disks, magnetic strips, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate media including at least one of the storage device 1002 and the auxiliary storage device 1003.

[0135] The communication device 1004 is hardware (a transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to implement at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission line interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be physically or logically separated into a transmission unit and a reception unit.

[0136] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) for receiving an external input. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) for performing an output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (e.g., a touch panel).

[0137] Also, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each device.

[0138] Also, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0139] FIG. 17 shows a configuration example of the vehicle 2001. As shown in FIG. 17, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and for example, may be applied to the communication module 2013.

[0140] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on an operation of the steering wheel operated by a user.

[0141] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0142] Signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotational speed signal of the front or rear wheels acquired by a rotational speed sensor 2022, an air pressure signal of the front or rear wheels acquired by an air pressure sensor 2023, a vehicle speed signal acquired by a vehicle speed sensor 2024, an acceleration signal acquired by an acceleration sensor 2025, a depression amount signal of the accelerator pedal acquired by an accelerator pedal sensor 2029, a depression amount signal of the brake pedal acquired by a brake pedal sensor 2026, an operation signal of the shift lever acquired by a shift lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, and the like.

[0143] The information service unit 2012 is composed of various devices for providing (outputting) various information such as driving information, traffic information, and entertainment information, such as a car navigation system, an audio system, speakers, a television, and a radio, and one or more ECUs for controlling these devices. The information service unit 2012 uses the information acquired from an external device via a communication module 2013 or the like to provide various multimedia information and multimedia services to the passengers of the vehicle 2001. The information service unit 2012 may include an input device for receiving external input (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.), or may include an output device for performing external output (for example, a display, a speaker, an LED lamp, a touch panel, etc.).

[0144] The driving assistance system unit 2030 is composed of various devices for providing functions to prevent accidents and reduce the driver's driving load, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, AI processors, and one or more ECUs for controlling these devices. Also, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0145] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via a communication port. For example, the communication module 2013 transmits and receives data with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 - 29 provided in the vehicle 2001 via the communication port 2033.

[0146] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it transmits and receives various information via wireless communication with external devices. The communication module 2013 may be either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, etc.

[0147] The communication module 2013 may transmit at least one of the signals from the various sensors 2021 - 2028 input to the electronic control unit 2010, the information obtained based on the signals, and the information based on the input from the external (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 - 2028, the information service unit 2012, etc. may be referred to as an input unit that receives the input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

[0148] The communication module 2013 receives various information (traffic information, signal information, inter - vehicle information, etc.) transmitted from an external device and displays it to the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be referred to as an output unit that outputs the information (for example, outputs the information to devices such as a display and a speaker based on the PDSCH received by the communication module 2013 (or the data / information decoded from the PDSCH)). Also, the communication module 2013 stores the various information received from the external device in the memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheels 2007, the rear wheels 2008, the axle 2009, the sensors 2021 - 2029, etc. provided in the vehicle 2001.

[0149] (Summary of the Embodiment) As described above, according to the embodiment of the present invention, there is provided a terminal having a transmitting unit that transmits a notification including a QoS (Quality of Service) level indicator in a physical layer to a base station, and a receiving unit that receives an uplink grant from the base station, and the transmitting unit performs uplink transmission to the base station to which the QoS level indicated by the QoS level indicator is applied based on the uplink grant.

[0150] With the above configuration, by introducing a physical layer QoS level indicator and notifying from the base station 10 to the terminal 20 or from the terminal 20 to the base station 10, flexible QoS control can be executed in the physical layer. That is, in a wireless communication system, QoS (Quality of Service) can be controlled in the physical layer.

[0151] The above notification may be an SR (Scheduling request). With this configuration, by introducing a physical layer QoS level indicator and notifying from the base station 10 to the terminal 20 or from the terminal 20 to the base station 10, flexible QoS control can be executed in the physical layer.

[0152] The above transmission unit may perform joint coding on the SR and the QoS level in the physical layer and transmit it to the base station. With this configuration, by introducing a physical layer QoS level indicator and notifying from the base station 10 to the terminal 20 or from the terminal 20 to the base station 10, flexible QoS control can be executed in the physical layer.

[0153] The above notification may be a BSR (Buffer status report). With this configuration, by introducing a physical layer QoS level indicator and notifying from the base station 10 to the terminal 20 or from the terminal 20 to the base station 10, flexible QoS control can be executed in the physical layer.

[0154] The above transmission unit may transmit the buffer status to the base station for each QoS level in the physical layer. With this configuration, by introducing a physical layer QoS level indicator and notifying from the base station 10 to the terminal 20 or from the terminal 20 to the base station 10, flexible QoS control can be executed in the physical layer.

[0155] Also, according to an embodiment of the present invention, a communication method is applied in which a terminal executes a transmission procedure for transmitting a notification including a QoS (Quality of Service) level indicator in a physical layer to a base station, a reception procedure for receiving an uplink grant from the base station, and a procedure for performing uplink transmission to the base station in which the QoS level indicated by the QoS level indicator is applied based on the uplink grant.

[0156] With the above configuration, by introducing a physical layer QoS level indicator and notifying the base station 10 from the terminal 20 or notifying the terminal 20 from the base station 10, flexible QoS control can be executed in the physical layer. That is, in a wireless communication system, QoS (Quality of Service) can be controlled in the physical layer.

[0157] (Supplement of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various variations, modifications, alternatives, substitutions, etc. Specific numerical examples have been used for the purpose of facilitating the understanding of the invention, but unless otherwise specified, those numerical values are merely examples and any appropriate values may be used. The classification of items in the above description is not essential to the present invention, and the matters described in two or more items may be used in combination as needed, or the matters described in one item may be applied to the matters described in another item (as long as there is no contradiction). The boundaries of the functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. The operations of a plurality of functional units may be physically performed by one component, or the operation of one functional unit may be physically performed by a 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 the sake of convenience in explaining the processing, the base station 10 and the terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software that operates by the processor included in the base station 10 according to the embodiment of the present invention and the software that operates by the processor included in the terminal 20 according to the embodiment of the present invention may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), an EPROM, an EEPROM, a register, a hard disk drive (HDD), a removable disk, a CD-ROM, a database, a server, or any other appropriate storage medium, respectively.

[0158] In addition, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and other methods may be used. For example, the notification of information may be implemented by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), notification information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, etc.

[0159] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication 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 suitable systems, and next-generation systems extended based thereon. Also, a plurality of systems may be combined (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) and applied.

[0160] The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this specification may be rearranged as long as there is no contradiction. For example, regarding the methods described in this disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

[0161] The specific operations assumed to be performed by the base station 10 in this specification may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by at least one of the base station 10 and other network nodes other than the base station 10 (for example, but not limited to, MME or S-GW, etc.). Although the case where there is one other network node other than the base station 10 is exemplified above, the other network node may be a combination of a plurality of other network nodes (for example, MME and S-GW).

[0162] The information or signals, etc. described in this disclosure can be output from an upper layer (or lower layer) to a lower layer (or upper layer). They may also be input and output via a plurality of network nodes.

[0163] The input and output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information, etc. can be overwritten, updated, or appended. The output information, etc. may be deleted. The input information, etc. may be transmitted to other devices.

[0164] The determination in this disclosure may be made based on a value represented by 1 bit (0 or 1), or may be made based on a Boolean value (true or false), or may be made based on a numerical comparison (for example, comparison with a predetermined value).

[0165] Software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether called software, firmware, middleware, microcode, a hardware description language, or by any other name.

[0166] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technologies (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.

[0167] 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., which may be referred to throughout the above description, may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0168] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of channel and symbol may be a signal (signaling). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

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

[0170] In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, relative values from a predetermined value, or using other corresponding information. For example, radio resources may be indicated by an index.

[0171] The names used for the above-described parameters are not limiting names in any way. Furthermore, the mathematical formulas, etc. using these parameters may be different from those explicitly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not limiting names in any way.

[0172] In this disclosure, terms such as "base station (BS: Base Station)", "radio base station", "base station device", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. The base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0173] A base station can accommodate one or more (e.g., three) cells. When the base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each of these smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

[0174] In the present disclosure, the base station transmitting information to the terminal may be read as the base station instructing the terminal to perform control / operations based on the information.

[0175] In the present disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" can be used interchangeably.

[0176] The mobile station may also be called by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terms.

[0177] At least one of the base station and the mobile station may be referred to as a transmission device, a reception device, a communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body refers to an object that can move, and the moving speed is arbitrary. Also, the case where the moving body is stopped is of course included. The moving body includes, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavator trucks, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, limousines, rickshaws, ships (ship and other watercraft), airplanes, rockets, artificial satellites, drones (registered trademark), multicopters, quadcopters, balloons, and things mounted on these, and is not limited thereto. Further, the moving body may be a moving body that autonomously travels based on an operation command. It may be a vehicle (e.g., a car, an airplane, etc.), a moving body that moves without a person (e.g., a drone, an autonomous driving vehicle, etc.), or a robot (humanoid or non-humanoid). Note that at least one of the base station and the mobile station also includes a device that does not necessarily move during a 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.

[0178] Also, the base station in the present disclosure may be read as a user terminal. For example, for a configuration in which communication between the base station and the user terminal is replaced with communication between a plurality of terminals 20 (which may be referred to as, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the above-described base station 10 may be configured to be functions of the terminal 20. Also, terms such as "uplink" and "downlink" may be read as terms corresponding to inter-terminal communication (e.g., "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0179] Similarly, the user terminal in the present disclosure may be rewritten by the base station. In this case, the functions of the above-described user terminal may be configured as functions of the base station.

[0180] The terms "determining" and "deciding" used in the present disclosure may include a variety of operations. "Determining" and "deciding" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database, or other data structure), ascertaining, and considering the ascertained facts as "determined" or "decided". Also, "determining" and "deciding" may include considering receiving (e.g., receiving information), transmitting (e.g., transmitting information), inputting, outputting, accessing (e.g., accessing data in a memory), and considering the accessed facts as "determined" or "decided". Further, "determining" and "deciding" may include considering resolving, selecting, choosing, establishing, comparing, etc., as "determined" or "decided". That is, "determining" and "deciding" may include considering any operation as "determined" or "decided". Also, "determining (deciding)" may be replaced with "assuming", "expecting", "considering", etc.

[0181] The terms "connected" or "coupled", or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed". As used in this disclosure, two elements can be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, and also, by way of some non-limiting and non-exhaustive examples, electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (both visible and invisible) regions.

[0182] The reference signal can also be abbreviated as RS (Reference Signal) and may be called a Pilot depending on the applicable standard.

[0183] As used in this disclosure, the description "based on" does not mean "based only on" unless otherwise specified. In other words, the description "based on" means both "based only on" and "based at least on".

[0184] Any reference to an element using designations such as "first", "second", etc. used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not mean that only two elements can be employed, or that the first element must precede the second element in any form.

[0185] The "means" in the configuration of each of the above devices may be replaced with a "section", "circuit", "device", etc.

[0186] In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive in the same manner as the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0187] The wireless frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be referred to as a subframe. The subframe may further be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) independent of numerology.

[0188] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

[0189] The slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. The slot may be a time unit based on numerology.

[0190] The slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, the mini-slot may be referred to as a sub-slot. The mini-slot may be composed of a smaller number of symbols than the slot. The PDSCH (or PUSCH) transmitted in a time unit larger than the mini-slot may be referred to as PDSCH (or PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the mini-slot may be referred to as PDSCH (or PUSCH) mapping type B.

[0191] The radio frame, sub-frame, slot, mini-slot, and symbol all represent time units when transmitting signals. Different names corresponding to each of them may also be used.

[0192] For example, one sub-frame may be referred to as a Transmission Time Interval (TTI), or a plurality of consecutive sub-frames may be referred to as TTI, or one slot or one mini-slot may be referred to as TTI. That is, at least one of the sub-frame and TTI may be the sub-frame (1 ms) in the existing LTE, or a period shorter than 1 ms (for example, 1 - 13 symbols), or a period longer than 1 ms. Note that the unit representing TTI may be referred to as a slot, mini-slot, etc. instead of a sub-frame.

[0193] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (such as the frequency bandwidth and transmission power that can be used in each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0194] The TTI may be a transmission time unit such as a channel-coded data packet (transport block), code block, codeword, etc., or may be a processing unit such as for scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (e.g., number of symbols) in which a transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

[0195] Note that when one slot or one mini-slot is called a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit for scheduling. Also, the number of slots (number of mini-slots) constituting the minimum time unit for the scheduling may be controlled.

[0196] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8 - 12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than the normal TTI may be called a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini-slot, sub-slot, slot, etc.

[0197] Note that a long TTI (e.g., normal TTI, subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, or a short TTI (e.g., shortened TTI, etc.) may be read as a TTI having a TTI length less than that of the long TTI and greater than or equal to 1 ms.

[0198] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may include one or a plurality of consecutive subcarriers. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0199] Also, the time domain of the RB may include one or more symbols, and may be the length of 1 slot, 1 mini-slot, 1 sub-frame, or 1 TTI. 1 TTI, 1 sub-frame, etc. may each be composed of one or more resource blocks.

[0200] Note that one or more RBs may be referred to as physical resource blocks (PRBs), sub-carrier groups (SCGs), resource element groups (REGs), PRB pairs, RB pairs, etc.

[0201] Also, the resource block may be composed of one or more resource elements (REs). For example, 1 RE may be a radio resource area of 1 sub-carrier and 1 symbol.

[0202] The bandwidth part (BWP) (which may also be called a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (common RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. The PRB is defined in a certain BWP and may be numbered within the BWP.

[0203] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). For a UE, one or more BWPs may be set within one carrier.

[0204] At least one of the set BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0205] The structures such as the above-mentioned radio frames, sub-frames, slots, mini-slots, and symbols are merely illustrative. For example, the number of sub-frames included in a radio frame, the number of slots per sub-frame or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols, symbol length, cyclic prefix (CP) length, etc. within a TTI can be changed in various ways.

[0206] In the present disclosure, for example, when articles are added by translation like a, an, and the in English, the present disclosure may include that the nouns following these articles are in the plural form.

[0207] In the present disclosure, the term "A is different from B" may mean that "A and B are different from each other". Note that the term may also mean that "A and B are each different from C". Terms such as "separate", "coupled", etc. may also be interpreted in the same way as "different".

[0208] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, the notification of predetermined information (for example, the notification of "being X") is not limited to being explicitly performed, and may be performed implicitly (for example, without performing the notification of the predetermined information).

[0209] As described in detail above regarding the present disclosure, 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 modified and changed aspects without departing from the spirit and scope of the present disclosure determined by the description of the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and does not have any restrictive meaning for the present disclosure.

Description of Reference Numerals

[0210] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Memory device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A transmitter that sends a notification including a QoS (Quality of Service) level indicator in the physical layer to a base station, and a receiver that receives an uplink grant from the base station, wherein the transmitter performs uplink transmission to the base station in which the QoS level indicated by the QoS level indicator is applied based on the uplink grant.

2. The terminal according to claim 1, wherein the notification is an SR (Scheduling request).

3. The terminal according to claim 2, wherein the transmitter jointly codes the SR and the QoS level in the physical layer and transmits the result to the base station.

4. The terminal according to claim 1, wherein the notification is a BSR (Buffer status report).

5. The terminal according to claim 4, wherein the transmitter transmits buffer statuses to the base station for each QoS level in the physical layer.

6. A communication method in which a terminal executes a transmission procedure for sending a notification including a QoS (Quality of Service) level indicator in the physical layer to a base station, a reception procedure for receiving an uplink grant from the base station, and a procedure for performing uplink transmission to the base station in which the QoS level indicated by the QoS level indicator is applied based on the uplink grant.

Images