Terminal and communication method

By introducing the physical layer QoS level indicator in the wireless communication system, the terminal sends the QoS level indicator to the base station and performs corresponding uplink transmission, solving the problem that QoS is difficult to set flexibly in the XR service, and realizing the physical layer Flexible QoS control and user experience improvement.

CN119174223APending Publication Date: 2024-12-20NTT DOCOMO INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202380039961.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-05-18
Filing Date
2023-04-20
Publication Date
2024-12-20

AI Technical Summary

Technical Problem

In the existing wireless communication system, the QoS of XR service is difficult to flexibly set, resulting in the inability to effectively support the transmission of multiple data streams with different characteristics and requirements in the physical layer.

Method used

A physical layer QoS level indicator is introduced in the wireless communication system, and the terminal sends a QoS level indicator to the base station, and performs uplink transmission of the corresponding QoS level based on the received uplink authorization.

Benefits of technology

It realizes flexible QoS control in the physical layer, improves user experience and system capacity, and ensures efficient processing of data streams of different QoS requirements during transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119174223A_ABST
    Figure CN119174223A_ABST
Patent Text Reader

Abstract

A terminal is provided with: a transmission unit that transmits, to a base station, a notification including a quality of service (QoS) level indicator in a physical layer; and a reception unit that receives an uplink grant from the base station, and the transmission unit performs, on the basis of the uplink grant, uplink transmission to which the QoS level indicated by the QoS level indicator is applied to the base station.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunication System (UMTS) network, Long Term Evolution (LTE) is standardized for the purpose of higher data rates, low latency, etc. In addition, the successor system of LTE is also being studied for the purpose of further broadband and high speed from LTE. Among the successor systems of LTE, there are systems called LTE-A (LTE-Advanced), future radio access (FRA: Future Radio Access), 5th generation mobile communication system (5G: 5th generation mobile communication system), 5G+ (5G plus), radio access technology (New-RAT; Radio Access Technology), new radio (NR: New Radio), etc.

[0003] In 5G, in order to meet the requirements of achieving a throughput of more than 10 Gbps and keeping the delay between wireless sections to less than 1 ms, various wireless technologies and network architectures have been studied (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] 3GPP (registered trademark) Release 16 specifies the configuration of CG PUSCH (Configured Grant Physical Uplink Shared Channel) and the configuration of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) (eg, Non-Patent Document 2).

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

[0007] In addition, in NR, in 3GPP Release 17, various technologies related to the method called Ultra-Reliable and Low Latency Communications (URLLC) and Industrial Internet of Things (IIoT) are studied.

[0008] In 3GPP version 17, extended reality (XR) such as virtual reality (VR) and mixed reality (MX) was studied, and the scenarios, requirements, key performance indicators (KPI) and evaluation methods of XR were studied. As the target requirements of XR, capacity, latency, mobility and energy saving are usually considered. Furthermore, in 3GPP version 18, the above research is also continuing.

[0009] Prior art literature

[0010] Non-patent literature

[0011] Non-patent document 1: 3GPP TS 38.300 V17.0.0 (2022-03)

[0012] Non-patent document 2: 3GPP TS 38.331 V16.8.0 (2022-03) Summary of the invention

[0013] Problems to be solved by the invention

[0014] XR services may include multiple data flows with different characteristics and requirements. The transmission of XR services needs to flexibly support the required QoS (Quality of Service). However, the current QoS is mainly defined by the high layer, making it difficult to flexibly set.

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

[0016] Means for solving problems

[0017] According to the disclosed technology, a terminal is provided, comprising: a sending unit, which sends a notification containing a QoS (Quality of Service) level indicator in a physical layer to a base station; and a receiving unit, which receives an uplink authorization from the base station, and the sending unit, based on the uplink authorization, performs an uplink transmission to the base station with the QoS level indicated by the QoS level indicator applied.

[0018] Effects of the Invention

[0019] According to the disclosed technology, in a wireless communication system, QoS (Quality of Service) can be controlled in a physical layer. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 It is a diagram showing a configuration example of a wireless communication system in an embodiment of the present invention.

[0021] Figure 2 This is a diagram showing an example of the arrival timing of XR services and CG / SPS opportunities.

[0022] Figure 3 This is a diagram for explaining example (1) of communication related to QoS in the embodiment of the present invention.

[0023] Figure 4 This is a diagram for explaining example (2) of communication related to QoS in the embodiment of the present invention.

[0024] Figure 5 This is a diagram for explaining example (3) of communication related to QoS in the embodiment of the present invention.

[0025] Figure 6 This is a diagram for explaining example (4) of communication related to QoS in the embodiment of the present invention.

[0026] Figure 7 This is a diagram for explaining example (1) of SR in the embodiment of the present invention.

[0027] Figure 8 This is a diagram for explaining example (2) of SR in the embodiment of the present invention.

[0028] Fig. 9 This is a diagram for explaining example (3) of SR in the embodiment of the present invention.

[0029] Fig.10 This is a diagram for explaining example (4) of SR in the embodiment of the present invention.

[0030] Fig.11 This is a diagram for explaining example (1) of the BSR in the embodiment of the present invention.

[0031] Fig.12 This is a diagram for explaining example (2) of the BSR in the embodiment of the present invention.

[0032] Fig.13 This is a diagram for explaining example (3) of the BSR in the embodiment of the present invention.

[0033] Fig.14 It is a diagram showing an example of the functional configuration of the base station 10 in the embodiment of the present invention.

[0034] Fig.15 This is a diagram showing an example of the functional configuration of the terminal 20 in the embodiment of the present invention.

[0035] Fig.16 This is a diagram showing an example of the hardware configuration of the base station 10 or the terminal 20 in the embodiment of the present invention.

[0036] Fig.17 1 is a diagram showing an example of the structure of a vehicle 2001 in the embodiment of the present invention. DETAILED DESCRIPTION

[0037] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0038] In the operation of the wireless communication system of the embodiment of the present invention, existing technologies are appropriately used. The existing technologies are, for example, existing LTE, but are not limited to existing LTE. In addition, unless otherwise specified, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and subsequent methods (e.g., NR) of LTE-Advanced.

[0039] In addition, in the embodiments of the present invention described below, the terms 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), PUSCH (Physical Uplink Shared Channel), etc. used in the existing LTE are used. These are for the convenience of recording, and the same signals, functions, etc. may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used for NR are not necessarily clearly recorded as "NR-".

[0040] Furthermore, in the embodiments of the present invention, the duplexing method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0041] In addition, in the embodiment of the present invention, “configuring” wireless parameters and the like may be pre-configuring predetermined values, or may be configuring wireless parameters notified from the base station 10 or the terminal 20 .

[0042] Figure 1 FIG. 1 is a diagram showing a configuration example of a wireless communication system in an embodiment of the present invention. Figure 1 As shown, the wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20. Figure 1 In the figure, one base station 10 and one terminal 20 are shown, but this is an example and a plurality of base stations 10 and a plurality of terminals 20 may be provided.

[0043] 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 can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or the number of resource blocks. The base station 10 sends a synchronization signal and system information to the terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is sent, for example, through NR-PBCH, and is also called broadcast information. The synchronization signal and system information may also be referred to as SSB (SS / PBCH block). As Figure 1 As shown, the base station 10 sends a control signal or data to the terminal 20 via DL (Downlink), and receives a control signal or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 can perform beamforming to send and receive signals. In addition, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output)-based communications to DL or UL. In addition, the base station 10 and the terminal 20 can also communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) based on CA (Carrier Aggregation). Furthermore, the terminal 20 can also communicate via the primary cell of the base station 10 based on DC (Dual Connectivity) and the primary and secondary cell group cells (PSCell: Primary SCG Cell) of other base stations 10.

[0044] The terminal 20 is a communication device having a wireless communication function, such as a smart phone, a mobile phone, a tablet computer, a wearable terminal, or an M2M (Machine-to-Machine) communication module. Figure 1 As shown, the terminal 20 receives a control signal or data from the base station 10 via DL and transmits a control signal or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. In addition, the terminal 20 receives various reference signals transmitted from the base station 10 and performs measurement of propagation path quality based on the reception result of the reference signal.

[0045] <CG PUSCH>

[0046] Next, CG PUSCH is described. CG PUSCH is a method of using PUSCH for UL transmission based on a UL grant configured by a higher layer (e.g., may also be referred to as a configured grant (Configured Grant), a configured UL grant (Configured UL Grant), etc.). For CG PUSCH, UL resources have been allocated to the terminal 20, and the terminal 20 can use the configured resources to spontaneously perform UL transmission, so low-latency communication can be expected.

[0047] In 3GPP Release 16, two types of CG PUSCH, Type 1 and Type 2, are specified.

[0048] The activation / deactivation of Type 1 CG PUSCH depends only on the RRC configuration (RRC-configuration) and does not depend on DCI. In Type 1 CG PUSCH, the parameters used for uplink transmission (also referred to as CG parameters, CG configuration (Configured Grant Configuration) information, etc.) are configured in the terminal 20 using only high-level signaling. Specifically, the parameters of Type 1 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config" and "rrc-Configur edUplinkGrant". That is, the base station 10 uses "Configu redGrantConfig", "pusch-Config" and "rrc-ConfiguredUplinkGrant" to indicate the parameters of uplink transmission to the terminal 20. The terminal 20 stores the received parameters as a configuration grant.

[0049] When type 1 CG PUSCH is activated, terminal 20 may determine that one or more configuration authorizations have been triggered (or activated), and use the configured resources (also referred to as CG resources, transmission opportunities, etc.) to perform PUSCH transmission without dynamic authorization.

[0050] The activation / deactivation of type 2 CG PUSCH depends on the RRC configuration (RRC-configurat ion) and DCI. One DCI can activate only one CG PUSCH and can deactivate multiple CG PUSCHs. In type 2CG PUSCH, the parameters for uplink transmission are configured in the terminal 20 using high-layer signaling. In addition, part of the parameters for uplink transmission is notified to the terminal through DCI. Specifically, the transmission parameters of type 2CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config" and "activation DCI". That is, the base station 10 uses "ConfiguredGrantConfig", "pusch-Config" and "activation DCI" to indicate the parameters of uplink transmission to the terminal 20. The terminal 20 stores the received parameters.

[0051] When type 2 CG PUSCH is activated and notified of the activation DCI, the terminal 20 can determine that one or more configuration grants have been triggered (or activated), and use the resources configured by the upper layer to send PUSCH without dynamic authorization. The activation DCI can be CRC (Cyclic Redundancy Check) scrambled by a predetermined identifier (for example, CS-RNTI (Configured Scheduling RNTI). In addition, the activation DCI can also be used for deactivation, retransmission and other controls of the configuration grant.

[0052] In addition, the terminal 20 may also release (also referred to as release, deactivate, etc.) the resources (PUSCH) corresponding to the configured grant (Configured Grant) based on the DCI that deactivates the configured grant (Configured Grant) or the expiration of a predetermined timer (after a predetermined time).

[0053] <SPS PDSCH>

[0054] Next, the SPS PDSCH is described. In the SPS PDSCH, periodic resources for semi-persistent scheduling (SPS) for downlink (DL) are configured by higher layers. The activation / deactivation (release) of the transmission using this resource in the SPS PDSCH depends on the activation DCI. This activation DCI can be CRC (Cyclic Redundancy Check) scrambled by a predetermined identifier (e.g., CS-RNTI (Configured Scheduling RNTI)).

[0055] In the SPS PDSCH, parameters for downlink transmission (which may also be referred to as SPS parameters, SPS configuration (Semi-Persistent Scheduling configuration) information, etc.) are configured for the terminal 20 using higher layer signaling. In addition, a part of the parameters for downlink transmission is notified to the terminal by DCI. Specifically, the transmission parameters of the SPS PDSCH are provided by "sps-Config" and "activation DCI". That is, the base station 10 uses "sps-Config" and "activation DCI" to indicate the parameters of downlink transmission to the terminal 20. The terminal 20 stores the received parameters.

[0056] <Parameters of the CG PUSCH>

[0057] Among the parameters in the ConfiguredGrantConfig for the type 1 and / or type 2 CG PUSCH (hereinafter referred to as "CGC-CG parameters (group)"), there are, for example, the following parameters. In addition, when the CGC-CG parameters are provided by both ConfiguredGrantConfig and pusch-Config, the terminal 20 can apply the CGC-CG parameters indicated by ConfiguredGrantConfig to the PUSCH transmission. Further, when there are CGC-CG parameters not provided by ConfiguredGrantConfig, the terminal 20 can apply the CGC-CG parameters indicated by pusch-Config to the PUSCH transmission.

[0058] (Examples of CGC-CG parameters)

[0059] ·periodicity: Used to indicate the period of PUSCH transmission corresponding to the configured grant.

[0060] repK: used to indicate the number of repeated PUSCH transmissions.

[0061] repK-RV: used to indicate information related to the redundancy version of repeated PUSCH transmission.

[0062] frequencyHopping: used to set either intra-slot frequency hopping or inter-slot frequency hopping to be valid. If this field does not exist, frequency hopping may not be applied.

[0063] cg-DMRS-Configuration: used to indicate the DMRS configuration of the PUSCH corresponding to the configured grant.

[0064] mcs-Table: used to indicate the MSC table used by the terminal 20 in the PUSCH without transform precoding. If this field does not exist, the terminal 20 can use the 64QAM table.

[0065] mcs-TableTransformPrecoder: used to indicate the MSC table used by the terminal 20 in the PUSCH with transform precoding. If this field does not exist, the terminal 20 can use the 64QAM table.

[0066] uci-OnPUSCH: used to indicate information related to transmission of UCI using PUSCH.

[0067] resourceAllocation: used to indicate whether to set any one of 'resource allocation type 0', 'resource allocation type 1', and 'dynamic switching'.

[0068] rbg-Size: used to indicate the RBG size of PUSCH.

[0069] powerControlLoopToUse: used to indicate the closed control loop to be used for PUSCH transmission.

[0070] p0-PUSCH-Alpha: used to calculate PUSCH transmit power.

[0071] ·transformPrecoder: used to indicate whether transform precoding is selected for PUSCH transmission.

[0072] phy-PriorityIndex: used to indicate the PHY priority of the CG PUSCH in at least the contention handling of the PHY layer. In addition, a value p0 indicates a low priority, and a value p1 indicates a high priority.

[0073] cg-nrofHARQ-Process: used to indicate the HARQ process number.

[0074] cg-nrofSlots: used to indicate the number of allocated time slots set by the grant period following the time instance set by the grant offset.

[0075] betaOffsetCG-UCI: used to indicate the beta offset of the CG-UCI in the CG-PUSCH.

[0076] · configuredGrantTimer: used to indicate the initial value of the configured grant timer in multiples of periodicity. If cg-RetransmissionTimer is set, when a HARQ process is shared between different configured grants on the same BWP, the same value is set for the configuration of the shared HARQ process on the BWP in the periodicity of configuredGrantTimer.

[0077] The parameters in rrc-ConfiguredUplinkGrant for Type 1 CG PUSCH (hereinafter referred to as "rrc-CUG-CG parameter (group)") include, for example, the following parameters: In addition, rrc-ConfiguredUplinkGrant is used to indicate grant information configured in Type 1 CG PUSCH.

[0078] (rrc-CUG-CG parameter example)

[0079] timeDomainOffset: used to indicate the offset associated with system frame number 0.

[0080] timeDomainAllocation: used to indicate the combination of the mapping type of the PUSCH, the starting symbol of the PUSCH, and the number of consecutive allocated symbols.

[0081] frequencyDomainAllocation: used to indicate the frequency resource allocation of PUSCH.

[0082] antennaPort: used to indicate the antenna port information for PUSCH transmission.

[0083] dmrs-SeqInitialization: An identifier used for scrambling the DMRS timing for PUSCH transmission.

[0084] precodingAndNumberOfLayers: used to indicate the precoding and number of layers used for PUSCH transmission.

[0085] srs-ResourceIndicator: used to indicate the SRS (Sounding Reference Signal) resource used.

[0086] mcsAndTBS: used to indicate the modulation order, target coding rate, and transport block size.

[0087] frequencyHoppingOffset: used to indicate the value of frequency hopping offset.

[0088] ·pathlossReferenceIndex: used to indicate the reference signal used in PUSCH path loss estimation.

[0089] pusch-RepTypeIndicator: used to indicate which of the actions for PUSCH repetition type A and PUSCH repetition type B the terminal 20 follows for each Type 1 configured grant configuration. The value pusch-RepTypeA enables "PUSCH repetition type A", and the value pusch-RepTypeB enables "PUSCH repetition type B".

[0090] frequencyHoppingPUSCH-RepTypeB: This field indicates the frequency hopping method of Type 1 CG when pusch-RepTypeIndicator is set to "pusch-RepTypeB". The value interRepetition enables "Inter-repetition frequency hop ping", and the value interSlot enables "Inter-slotfrequency hopping". If this field does not exist, frequency hopping is invalid in Type 1 CG.

[0091] Among the parameters indicated by activation DCI (hereinafter referred to as "DCI-CG parameters (group)") for type 2 CG PUSCH, there are, for example, the following parameters.

[0092] (Examples of DCI-CG parameters)

[0093] · timeDomainAllocation: Used to represent the combination of start symbol and length and the PUSCH mapping type.

[0094] · frequencyDomainAllocation: Used to represent the resource allocation in the frequency domain.

[0095] · MCS index: Used to represent the index of MCS (Modulation and Coding Scheme).

[0096] · antenna port indication: Used to represent the antenna port.

[0097] · precoding and number of layers indication: Used to represent precoding and the number of layers.

[0098] · SRS resource indicator: Used to represent the resource for SRS (Sounding Reference Signal).

[0099] · power control related parameter indication: Used to represent the parameters related to transmission power control.

[0100] <Parameters of SPS PDSCH>

[0101] Among the parameters in SPS-Config for SPS PDSCH (hereinafter referred to as "SC-SPS parameters (group)"), there are, for example, the following parameters.

[0102] (Examples of SC-SPS parameters)

[0103] · periodicity: Used to represent the period of SPS PDSCH.

[0104] · n1PUCCH-AN: Used to represent the HARQ-ACK (Hybrid automatic repeat request Acknowledgement) PUCCH resource for SPS PDSCH.

[0105] mcs-Table: used to indicate the MCS table applied to the reception of the SPS PDSCH.

[0106] pdsch-AggregationFactor: used to indicate the number of repeated PDSCH transmissions.

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

[0108] (Example of DCI-SPS parameters)

[0109] timeDomainAllocation: used to indicate the combination of the starting symbol and length and the PDSCH mapping type.

[0110] frequencyDomainAllocation: used to indicate resource allocation in the frequency domain.

[0111] MCS index: used to indicate the index of MCS (Modulation and Coding Scheme).

[0112] TCI state indication: used to indicate the state of TCI (Transmission Configuration Indicator) for PDSCH.

[0113] Antenna port indication: Used to indicate the antenna port.

[0114] priority of HARQ-ACK: used to indicate the priority of HARQ-ACK.

[0115] K1: indicates the number of slots from the slot in which data is scheduled on the PDSCH to the slot in which the HARQ-ACK for the PDSCH is transmitted.

[0116] <Other parameters>

[0117] The parameters other than those described above (hereinafter referred to as “other-CG / SPS parameters (group)”) notified from the base station 10 to the terminal 20 include, for example, the following parameters.

[0118] (Examples of other CG / SPS parameters)

[0119] PDSCH / PUSCH length: used to indicate the length of PDSCH and / or PUSCH.

[0120] ·number of PRBs: used to indicate the number of PRBs (Physical Resource Blocks).

[0121] Figure 2 This is a diagram showing an example of the arrival timing of XR services and CG / SPS opportunities. Figure 2 This is a diagram showing an example of the relationship between the arrival timing of the XR service and the transmission opportunity (transmitting occasion) of the CG-PUSCH and / or the monitoring opportunity (monitoring occasion) of the SPS-PDSCH. In addition, in the following, the "transmission opportunity of the CG-PUSCH and / or the monitoring opportunity of the SPS-PDSCH" is sometimes omitted and recorded as "CG / SPS opportunity" or "opportunity".

[0122] XR services are assumed to arrive periodically based on FPS (frames per second). Figure 2 As shown in FIG. 1 , the arrival period of XR services is defined as a non-integer value such as 16.67 ms, whereas the periodicity of CG / SPS opportunities is defined as an integer value such as 16 ms or 17 ms. Figure 2 As shown, sometimes waiting time occurs.

[0123] Here, XR services may contain multiple data streams with different characteristics and requirements. The transmission of XR services needs to flexibly support the required QoS (Quality of Service). However, the current QoS is mainly specified by the upper layer. When data in the upper layer is transmitted by the physical layer, different XR services or XR streams are mixed in the physical layer.

[0124] When the transmission parameter determination or physical layer processing (eg, processing of conflicts within the UE) is based on the data requiring the highest QoS level among the mixed data, resource utilization efficiency is reduced.

[0125] In addition, when the determination of transmission parameters or physical layer processing (for example, processing of conflicts within the UE) is based on the data with the lowest QoS level requirement among the mixed data, there may be cases where some data cannot meet the QoS requirements.

[0126] Therefore, by supporting the QoS level indicator in the physical layer, efficient physical layer processing (e.g., determination of transmission parameters, processing of conflicts between UEs or within UEs, etc.) can be achieved for data flows with different QoS requirements. This can be expected to improve user experience and increase system capacity.

[0127] The physical layer can differentiate different QoS levels. A physical layer indicator indicating the QoS level can be introduced. For example, the physical layer QoS level indicator can be composed of a maximum of X bits, indicating a maximum QoS level of 2 to the power of X. X can be defined by the specification or set by RRC signaling.

[0128] Table 1 is an example of a physical layer QoS level indicator in which X is set to 1. Table 2 is an example of a physical layer QoS level indicator in which X is set to 2. Table 3 is an example of a physical layer QoS level indicator in which X is set to 3.

[0129] [Table 1]

[0130] Physical layer indicator value QoS Level 0 QoS level 0, 1 1 QoS level 1, 2

[0131] [Table 2]

[0132] Physical layer indicator value QoS Level 00 QoS Level 0 01 QoS Level 1 10 QoS Level 2 11 QoS Level 3

[0133] [Table 3]

[0134] Physical layer indicator value QoS Level 000 QoS Level 0 001 QoS Level 1 …… …… 111 QoS Level 7

[0135] As shown in Table 1, 2 QoS levels may be notified by the physical layer QoS level indicator. As shown in Table 2, 4 QoS levels may be notified by the physical layer QoS level indicator. As shown in Table 3, 8 QoS levels may be notified by the physical layer QoS level indicator.

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

[0137] The physical layer QoS level indicator can be used for processing data streams with different QoS requirements. For example, scheduling auxiliary information, and / or determination of transmission parameters, and / or intra-UE DL / UL conflict processing, and / or inter-UE DL / UL conflict processing can be performed based on the physical layer QoS level indicator.

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

[0139] Figure 4 It is a diagram for illustrating example (2) of communication related to QoS in an embodiment of the present invention. As shown in step S21, the base station 10 can notify the terminal 20 of the QoS level indicator together with the UL authorization. Based on the notification, the terminal 20 can, for example, determine the associated scheduling parameters such as the interpretation of the DCI field of the values ​​of different QoS levels, and can also perform UE-to-UE DL / UL conflict processing with a granularity refined based on the QoS level for UL priority sorting, and can also perform UE-to-UE DL / UL conflict processing with a granularity refined based on the QoS level for DL ​​preemption or UL cancellation. In the next step S22, the terminal 20 sends a PUSCH to the base station 10.

[0140] Figure 5 It is a diagram for illustrating example (3) of communication related to QoS in an embodiment of the present invention. As shown in step S31, the base station 10 can notify the terminal 20 of the QoS level indicator together with the DL authorization. Based on the notification, the terminal 20 can, for example, determine the associated scheduling parameters such as the interpretation of the DCI field of the values ​​of different QoS levels, and can also perform UE-to-UE DL / UL conflict processing with a granularity refined based on the QoS level for UL priority sorting, and can also perform UE-to-UE DL / UL conflict processing with a granularity refined based on the QoS level for DL ​​preemption or UL cancellation. In the next step S32, the base station 10 sends a PDSCH to the terminal 20.

[0141] Figure 6 This is a diagram for explaining 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 the QoS level indicator through the MAC-CE or CG-UCI accompanying the PUSCH. The base station 10 may determine the decoding parameters based on the received information.

[0142] The base station 10 may also notify the terminal 20 of the physical layer QoS level indicator. The physical layer QoS level indicator may be set through RRC signaling. For example, the physical layer QoS level indicator may be set through RRC signaling for SPS-PDSCH or CG-PUSCH, or may be set through RRC signaling for a group of SPS-PDSCH or CG-PUSCH. The SPS-PDSCH or CG-PUSCH accompanied by the physical layer QoS level indicator indicates the QoS level of the DL or UL carrier based on the SPS-PDSCH or CG-PUSCH. The SPS-PDSCH or CG-PUSCH not accompanied by the physical layer QoS level indicator may apply a default QoS level, for example, the highest, lowest or middle QoS level may be applied.

[0143] The physical layer QoS level indicator may be set for the DCI format through RRC signaling. The physical layer QoS level indicator set in 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.

[0144] The DCI format accompanied by 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. With respect to the DCI format not accompanied by the physical layer QoS level indicator, a 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.

[0145] The physical layer QoS level indicator can be notified through DCI. The DCI format for the physical layer QoS level indicator can be an existing DCI format for scheduling PDSCH or PUSCH. For example, it can be DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2. In the case of accompanying an existing RNTI, the physical layer QoS level indicator can be notified through a new DCI field. In the case of accompanying a new RNTI, the physical layer QoS level indicator can be explicitly notified through the DCI field. Alternatively, in the case of a new DCI format accompanied by an existing or new RNTI, the physical layer QoS level indicator can also be explicitly notified through the DCI field.

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

[0147] Whether there is a field for the physical layer QoS level indicator in the DCI format can be set by RRC signaling or defined by a specification. For example, a new RRC parameter can notify whether the field exists in the DCI format. For example, in the case where the terminal 20 reports to the base station 10 the UE capability indicating whether the physical layer QoS level indicator is supported, the terminal 20 can assume that the field is always present in a predetermined DCI format (e.g., DCI format 1_1 / 0_1 and / or DCI format 1_2 / 0_2).

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

[0149] Dynamic grant of PDSCH / PUSCH may also be scheduled via 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 a specification or may be set for each DCI format or for all DCI formats via RRC signaling. In addition, the QoS level may be set for the scheduled PDSCH / PUSCH based on the last DCI format accompanied by the physical layer QoS level indicator. In the absence of the last DCI format accompanied by the physical layer QoS level indicator, the default QoS level may be applied.

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

[0151] 1) The terminal 20 may apply the physical layer QoS level indicator notified through the DCI format to all SPS-PDSCHs or CG-PUSCHs. That is, the physical layer QoS level indicator notified through the DCI format may be applied to the initial SPS-PDSCH or CG-PUSCH after activation, and the subsequent SPS-PDSCH or CG-PUSCH. In addition, the terminal 20 may not assume a predetermined value for the notified physical layer QoS level indicator, and may not assume a value that is not a predetermined value. For example, the terminal 20 may assume that the notified physical layer QoS level indicator is a predefined value, and may also assume that it is not a predefined value.

[0152] 2) The terminal 20 may apply the physical layer QoS level indicator notified through the DCI format only to the initial SPS-PDSCH or CG-PUSCH after activation, and may apply the default QoS level (highest, lowest or middle QoS level) to subsequent SPS-PDSCH or CG-PUSCH.

[0153] 3) The terminal 20 may not 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 (the highest, lowest or middle QoS level) to the SPS-PDSCH or CG-PUSCH.

[0154] 4) The terminal 20 may not assume this situation. In other words, it may not assume that the physical layer QoS level indicator is notified through the DCI format.

[0155] In the case where a physical layer QoS level indicator is not set for SPS / CG through RRC signaling, and in the case of SPS-PDSCH or CG-PUSCH activated by a DCI format in which a physical layer QoS level indicator is not set, a 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 a specification or may be set for each SPS / CG configuration or for all SPS / CG configurations through RRC signaling.

[0156] When the physical layer QoS level indicator is set for SPS / CG through RRC signaling, in the SPS-PDSCH or CG-PUSCH activated by the DCI format in which the physical layer QoS level indicator is set, the terminal 20 can act as shown in the following 1)-5).

[0157] 1) In notifications based on DCI format and notifications based on RRC signaling, different physical layer QoS level indicator values ​​may not be envisaged. The same value may be applied to all SPS-PDSCHs or CG-PUSCHs. That is, the same value may be applied to the initial SPS-PDSCH or CG-PUSCH and the subsequent SPS-PDSCH or CG-PUSCH.

[0158] 2) Notification based on the DCI format can overwrite notification based on RRC signaling. That is, the physical layer QoS level indicator notified through the DCI format can be applied to all SPS-PDSCH or CG-PUSCH. That is, the physical layer QoS level indicator notified through the DCI format can be applied to the initial SPS-PDSCH or CG-PUSCH and subsequent SPS-PDSCH or CG-PUSCH.

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

[0160] 4) The physical layer QoS level indicator based on RRC signaling can be applied to all SPS-PDSCHs or CG-PUSCHs. That is, the physical layer QoS level indicator based on RRC signaling can be applied to the initial SPS-PDSCH or CG-PUSCH, and the subsequent SPS-PDSCH or CG-PUSCH.

[0161] 5) The terminal 20 may not assume this situation. That is, when the physical layer QoS level indicator is set in the SPS / CG configuration through RRC signaling, it may not be assumed that the physical layer QoS level indicator is notified through the DCI format.

[0162] When the physical layer QoS level indicator is set for SPS / CG through RRC signaling, in the SPS-PDSCH or CG-PUSCH activated by the DCI format in which the physical layer QoS level indicator is not set, the terminal 20 can 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 based on RRC signaling can be applied to the initial SPS-PDSCH or CG-PUSCH, and the subsequent SPS-PDSCH or CG-PUSCH.

[0163] Assuming that multiple PDSCH / PUSCH are scheduled through DCI. Regarding a predetermined DCI format (DCI format 1_1 / 0_1 and / or DCI format 1_2 / 0_2) set according to a TDRA (Timedomain resource allocation) table including at least one row having a SLIV (Start and length indicator value) greater than 1, the terminal 20 can operate as shown in the following 1)-3).

[0164] 1) The terminal 20 may not assume that a field having a physical layer QoS level indicator is set in the DCI format.

[0165] 2) When a field for the physical layer QoS level indicator is set in the DCI format, the terminal 20 may assume only one field for the physical layer QoS level indicator. The physical layer QoS level indicator value based on the field may be applied to all scheduled PDSCH / PUSCHs or only to the initial PDSCH / PUSCH.

[0166] 3) In the case where a field for a physical layer QoS level indicator is set in the DCI format, the terminal 20 may assume multiple fields for a physical layer QoS level indicator. The fields may be independently 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, the fields may also be independently applied to the groups of scheduled PDSCH / PUSCHs. The number of the fields may be determined based on the maximum number of groups of PDSCH / PUSCHs for the physical layer QoS level indicator.

[0167] The physical layer QoS level indicator can be notified through MAC-CE. For example, the MAC-CE accompanying the preceding PDSCH can notify the physical layer QoS level indicator of the subsequent one or more PDSCHs, can also notify the physical layer QoS level indicator of the first one or more PDSCHs after k time slots of the MAC-CE time slot, and can also notify the physical layer QoS level indicator of one or more PDSCHs in a predetermined time slot after k time slots of the MAC-CE time slot.

[0168] 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 through an extended SR report. The SR-PUCCH may also be extended to include information other than a notification request. For example, in order to notify the base station of the QoS level of UL transmitted data, the physical layer QoS level indicator may be included in the extended SR-PUCCH.

[0169] In the case that UL transmission data has multiple QoS levels, the extended SR may only notify the maximum, minimum or middle physical layer QoS level indicator value among the multiple QoS levels.

[0170] In addition, in the case where the UL transmission data has multiple QoS levels, the extended SR may also notify multiple QoS levels. For example, the extended SR may notify up to X physical layer QoS level indicators. X may be defined by the specification or set by RRC signaling. In the case where the number of actual physical layer QoS level indicators for UL transmission data is m which is less than X, a reserved value representing multiple QoS levels may be defined for the (Xm) block.

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

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

[0173] Fig. 9 3 is a diagram for explaining example (3) of SR in an embodiment of the present invention. Fig. 9 As shown, the positive SR or negative SR and the physical layer QoS level indicator jointly encoded therewith can be notified with a length of 3 bits, for example. Fig. 9 In the example shown in FIG. 4 , up to seven QoS levels can be notified through the physical layer QoS level indicator.

[0174] Fig.10 4 is a diagram for explaining example (4) of SR in an embodiment of the present invention. Fig.10 As shown, two positive SRs or negative SRs and the physical layer QoS level indicator jointly encoded therewith can be notified with a length of 6 bits, for example. Fig.10 In the example shown in FIG. 4 , each physical layer QoS level indicator can notify up to seven QoS levels.

[0175] The terminal 20 may report the physical layer QoS level indicator to the base station 10 through an extended BSR report. The BSR report may also be extended to inform the base station 10 of the buffer status and the QoS level of the UL transmission data to be processed. The extended BSR report accompanied by 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).

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

[0177] The terminal 20 may also report multiple buffer status values ​​and multiple physical layer QoS level indicator values ​​to the base station 10 .

[0178] Terminal 20 may report the buffer status per defined QoS class in the BSR report.

[0179] Fig.11 1 is a diagram for explaining example (1) of BSR in an embodiment of the present invention. Fig.11 As shown, in the case where there is no UL transmission data of a predetermined QoS level, the terminal 20 may report the BSR by setting the buffer size to 0. The terminal 20 may report the BSR in ascending or descending order of the QoS level or QoS group index.

[0180] Fig.12 2 is a diagram for explaining Example (2) of BSR in an embodiment of the present invention. Fig.12 As shown, in the case where there is no UL transmission data of a predetermined QoS level, the buffer size of 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 QoS group index.

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

[0182] Fig.13 3 is a diagram for explaining example (3) of BSR in an embodiment of the present invention. Fig.13 As shown, 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.

[0183] The terminal 20 may report the physical layer QoS level indicator to the base station 10 via the MAC-CE or CG-UCI accompanying the PUSCH. In addition, the terminal 20 may report the physical layer QoS level indicator to the PUSCH, or report the mapping relationship between the physical layer QoS level indicator and the activated CG configuration.

[0184] The terminal 20 may not assume the 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).

[0185] When the physical layer priority is set in the DCI format, the terminal 20 may not assume that the field of the physical layer QoS level indicator is simultaneously set in the DCI format through RRC signaling.

[0186] In addition, when the physical layer priority is set for the DCI format, and the field of the physical layer QoS level indicator is simultaneously set in the DCI format through RRC signaling, the terminal 20 may ignore the set physical layer QoS level indicator. The terminal 20 may determine the priority index value 0 or the priority index 1 through the DCI notification.

[0187] In addition, when the physical layer QoS level indicator is set for the SPS / CG configuration group through RRC signaling, the terminal 20 may not assume that the SPS / CG configuration is activated by setting the DCI format with the physical layer priority field.

[0188] In addition, when a physical layer QoS level indicator is set for the SPS / CG configuration group through RRC signaling, and the SPS / CG configuration is activated by setting a DCI format with a physical layer priority field, the terminal 20 can ignore the physical layer QoS level indicator. The terminal 20 can determine the priority index value 0 or the priority index 1 through the DCI notification.

[0189] When the physical layer priority is set in the DCI format, the terminal 20 may not assume that the field of the physical layer QoS level indicator is simultaneously set in the DCI format.

[0190] The physical layer QoS level indicator and the physical layer priority can be applied independently. The physical layer priority indicator is used to notify the physical layer priority index value 0 or 1, and can also be used for intra-UE priority / multiplexing, and / or inter-UE priority / multiplexing (for example, DL preemption, UL cancellation). The physical layer QoS indicator is used to notify the QoS level of the physical layer, and can also be used to differentiate the QoS processing of multiple data streams, can also be used for scheduling assistance, can also be used for the determination of transmission parameters, and can also be used for the expanded intra-UE / inter-UE priority sorting that takes into account the physical layer QoS level.

[0191] In addition, the physical layer QoS level indicator and the physical layer priority can also be operated jointly. The physical layer priority indicator and the physical layer QoS level indicator can be combined to determine the QoS priority of the data. For example, a 1-bit physical layer priority indicator (index 0 or index 1) and an X-bit physical layer QoS level indicator can be combined to set a (X+1)-bit QoS priority indicator value, and the 1-bit physical layer priority indicator can be attached to the beginning of the X bits of the physical layer QoS level indicator, or it can be attached to the end.

[0192] In the above-mentioned embodiments, in the case where the physical layer QoS level indicator is notified from the base station 10 to the terminal 20, or in the case where 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. In addition, the number of bits of the physical layer QoS level indicator may be different. The mapping of the physical layer QoS level indicator value and the corresponding QoS level may be separately defined or set.

[0193] The physical layer QoS level indicator may be set by a higher layer parameter, may be reported by the terminal 20 as a UE capability, may be defined by a specification, or may be determined and set by a higher layer parameter and reported by the UE capability.

[0194] The action of the terminal 20 reporting the physical layer QoS level indicator to the base station 10 can be applied to the reporting of QoS level information in a higher layer.

[0195] A UE capability indicating whether a physical layer QoS level indicator is supported may be defined. A UE capability indicating whether notification of a physical layer QoS level indicator via RRC signaling, DCI, or MAC-CE may be supported. A UE capability indicating whether reporting of a physical layer QoS level indicator accompanied by SR, BSR, MAC-CE, or CG-UCI may be supported may be defined.

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

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

[0198] (Device Structure)

[0199] Next, the functional configuration examples of the base station 10 and the terminal 20 that execute the above-described processing and operation are 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 include only a part of the functions in the embodiments.

[0200] <Base station 10>

[0201] Fig.14 FIG. 1 is a diagram showing an example of a functional configuration of a base station 10 in an embodiment of the present invention. Fig.14 As shown, the base station 10 includes a transmission unit 110 , a reception unit 120 , a setting unit 130 , and a control unit 140 . Fig.14 The functional configuration shown is only an example, and any functional division and function unit name may be used as long as the operation of the embodiment of the present invention can be performed.

[0202] The transmitting unit 110 includes a function of generating a signal to be sent to the terminal 20 side and wirelessly transmitting the signal. In addition, the transmitting unit 110 sends network node messages to other network nodes. The receiving unit 120 includes a function of receiving various signals sent from the terminal 20 and obtaining, for example, higher layer information from the received signals. In addition, the transmitting unit 110 has a function of sending NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. In addition, the receiving unit 120 receives network node messages from other network nodes.

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

[0204] As described in the embodiment, the control unit 140 performs control related to QoS settings. In addition, the control unit 140 performs 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.

[0205] <Terminal 20>

[0206] Fig.15 FIG. 2 is a diagram showing an example of the functional structure of the terminal 20 in the embodiment of the present invention. Fig.15 As shown, the terminal 20 includes a transmitting unit 210 , a receiving unit 220 , a setting unit 230 , and a control unit 240 . Fig.15 The functional configuration shown is only an example, and any functional division and name of the functional unit may be used as long as the operation involved in the embodiment of the present invention can be performed.

[0207] The transmitting unit 210 generates a transmission signal according to the transmission data, and transmits the transmission signal wirelessly. The receiving unit 220 receives various signals wirelessly, and obtains a higher layer signal from the received physical layer signal. In addition, the receiving 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. And, for example, as D2D communication, the transmitting 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 other terminals 20, and the receiving unit 220 receives PSCCH, PSSCH, PSDCH or PSBCH, etc. from other terminals 20.

[0208] The setting unit 230 stores various setting information received by the receiving unit 220 from the base station 10. In addition, the setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to QoS setting.

[0209] As described in the embodiment, the control unit 240 performs control related to QoS settings. Functional units related to signal transmission in the control unit 240 may be included in the transmission unit 210, and functional units related to signal reception in the control unit 240 may be included in the reception unit 220.

[0210] (Hardware Structure)

[0211] The block diagram used in the description of the above embodiment ( Fig.14 and Fig.15 ) shows blocks in units of functions. These functional blocks (structural parts) are implemented by any combination of at least one of hardware and software. In addition, there is no particular limitation on the implementation method of each functional block. That is, each functional block can be implemented using one device that is physically or logically combined, or it can be implemented by connecting two or more physically or logically separated devices directly or indirectly (for example, using wires, wirelessly, etc.) and using these multiple devices. The functional blocks can also be implemented by combining software in the above-mentioned one device or the above-mentioned multiple devices.

[0212] Functions include judging, determining, judging, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but are not limited to these. For example, a functional block (structural unit) that performs a sending function is called a transmitting unit or a transmitter. In short, as mentioned above, there is no particular limitation on the implementation method.

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

[0214] In the following description, the word "device" may be replaced by "circuit", "device", "unit", etc. The hardware configuration of the base station 10 and the terminal 20 may include one or more of the devices shown in the figure, or may exclude some of the devices.

[0215] Each function in the base station 10 and the terminal 20 is implemented by the following method: predetermined software (program) is read into hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls the communication of the communication device 1004 or controls at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0216] The processor 1001 controls the entire computer by, for example, operating an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a computing device, registers, etc. For example, the control unit 140, the control unit 240, etc. may also be implemented by the processor 1001.

[0217] In addition, the processor 1001 reads a program (program code), a software module, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and performs various processes accordingly. As a program, a program that causes the computer to execute at least a part of the actions described in the above embodiments is used. For example, Fig.14 The control unit 140 of the base station 10 shown may also be implemented by a control program stored in the storage device 1002 and executed in the processor 1001. In addition, for example, Fig.15 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it is described that the above-mentioned various processes are performed by one processor 1001, the above-mentioned various processes can also be performed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by one or more chips. In addition, the program can also be sent from the network via a telecommunication line.

[0218] The storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing the communication method involved in one embodiment of the present disclosure.

[0219] The auxiliary storage device 1003 is a computer-readable recording medium, and may be composed of at least one of an optical disk such as a CD-ROM (CompactDisc ROM), a hard disk drive, a floppy disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk, a smart card, a flash memory (e.g., a card, a stick, a key drive), a Floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, and other appropriate media including at least one of the storage device 1002 and the auxiliary storage device 1003.

[0220] The communication device 1004 is hardware (transceiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex). For example, a transceiver antenna, an amplifier, a transceiver, a transmission path interface, etc. may also be implemented by the communication device 1004. The transceiver may also be implemented by physically or logically separating the transmitter and the receiver.

[0221] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that implements output to the outside (e.g., a display, a speaker, an LED light, etc.). In addition, the input device 1005 and the output device 1006 may also be integrally formed (e.g., a touch panel).

[0222] In addition, the processor 1001 and the storage device 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or different buses may be used between the devices.

[0223] In addition, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and a part or all of each functional block may be implemented by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

[0224] Fig.17 FIG. 2 shows a structural example of a vehicle 2001. Fig.17 As shown, the vehicle 2001 includes a driving 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 form / embodiment described in the present disclosure may also be applied to a communication device mounted on the vehicle 2001, for example, may also be applied to the communication module 2013.

[0225] The driving 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 referred to as a steering wheel), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by a user.

[0226] 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 referred to as an ECU (Electronic Control Unit).

[0227] As signals from various sensors 2021 to 2029, there are a current signal from a current sensor 2021 for sensing the current of a motor, a speed signal of a front wheel or a rear wheel obtained by a speed sensor 2022, an air pressure signal of a front wheel or a rear wheel obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028, and the like.

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

[0229] The driving assistance system unit 2030 is composed of various devices for preventing accidents or reducing the driver's driving load, such as millimeter wave radar, LiDAR (Light Detection and Ranging), camera, positioning device (such as GNSS, etc.), map information (such as high-definition (HD) map, autonomous driving vehicle (AV) map, etc.), gyroscope system (such as IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, AI processor, and one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 sends and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0231] The communication module 2013 can be controlled by the microprocessor 2031 of the electronic control unit 2010, and is a communication device that can communicate with an external device. For example, various information can be sent and received with the external device via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. The external device can also be, for example, a base station, a mobile station, etc.

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

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

[0234] (Summary of Implementation Methods)

[0235] As described above, according to an embodiment of the present invention, there is provided a terminal comprising: a sending unit, which sends a notification including a QoS (Quality of Service) level indicator in a physical layer to a base station; and a receiving unit, which receives an uplink authorization from the base station, and the sending unit performs an uplink transmission to the base station based on the uplink authorization, applying the QoS level indicated by the QoS level indicator.

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

[0237] The notification may be a Scheduling Request (SR). According to this configuration, by introducing a physical layer QoS level indicator and notifying the terminal 20 from the base station 10 or from the terminal 20 to the base station 10, flexible QoS control can be performed in the physical layer.

[0238] The transmitting unit may jointly encode the SR and the QoS level in the physical layer and transmit the SR to the base station. According to this structure, by introducing the physical layer QoS level indicator and notifying the terminal 20 from the base station 10 or notifying the base station 10 from the terminal 20, flexible QoS control can be performed in the physical layer.

[0239] The notification may be a BSR (Buffer Status Report). According to this structure, by introducing a physical layer QoS level indicator and notifying the terminal 20 from the base station 10 or from the terminal 20 to the base station 10, flexible QoS control can be performed in the physical layer.

[0240] The sending unit may send the buffer status to the base station for each QoS level in the physical layer. According to this structure, by introducing the physical layer QoS level indicator and notifying the terminal 20 from the base station 10 or from the terminal 20 to the base station 10, flexible QoS control can be performed in the physical layer.

[0241] In addition, according to an embodiment of the present invention, a communication method is applied, in which the terminal performs the following steps: a sending step of sending a notification containing a QoS (Quality of Service) level indicator in a physical layer to a base station; a receiving step of receiving an uplink authorization from the base station; and a step of performing an uplink sending step of applying the QoS level indicated by the QoS level indicator to the base station based on the uplink authorization.

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

[0243] (Supplementary Implementation Methods)

[0244] The above describes the embodiments of the present invention, but the disclosed invention is not limited to such embodiments, and those skilled in the art should understand various variations, modifications, alternatives, replacements, etc. In order to promote the understanding of the invention, specific numerical examples are used for description, but unless otherwise specified, these numerical values ​​are only examples, and any appropriate value can be used. The item distinction in the above description is not essential to the present invention. The items recorded in more than two items can be combined and used as needed, and the items recorded in a certain item can be applied to the items recorded 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 the physical components. The actions of multiple functional units can be performed by one physical component, or the actions of one functional unit can be performed by multiple physical components. Regarding the processing process described in the embodiment, the order of processing can be swapped without contradiction. In order to facilitate the description of the processing, the base station 10 and the terminal 20 are described using a functional block diagram, but such a device can also be implemented by hardware, software, or a combination thereof. The software that operates according to the implementation mode of the present invention through the processor of the base station 10 and the software that operates according to the implementation mode of the present invention through the processor of the terminal 20 can also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server and any other appropriate storage medium.

[0245] In addition, the notification of information is not limited to the form / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high-level signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals or a combination thereof. In addition, RRC signaling may be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0246] The various forms / implementations described in the present disclosure may also be applied to at least one of systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER3G, 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), CDMA 2000, 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 appropriate systems, and next-generation systems expanded upon these systems. In addition, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) can also be applied.

[0247] The processing procedures, timings, and flows of each form / implementation described in this specification may be reversed in order if there is no contradiction. For example, the methods described in this disclosure use the order in which the elements of various steps are presented, but are not limited to the specific order presented.

[0248] In this specification, specific actions performed by the base station 10 are sometimes also performed by its upper node according to the situation. In a network composed of one or more network nodes having the base station 10, various actions performed for communicating 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, MME or S-GW, etc., but not limited to these). In the above, the case where there is one other network node other than the base station 10 is illustrated, but the other network node may also be a combination of multiple other network nodes (for example, MME and S-GW).

[0249] The information or signals described in the present disclosure can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and can also be input or output via a plurality of network nodes.

[0250] The input or output information can be stored in a specific location (e.g., a memory) or managed using a management table. The input or output information can be rewritten, updated, or appended. The output information can also be deleted. The input information can also be sent to other devices.

[0251] The determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparison of numerical values ​​(for example, comparison with a predetermined value).

[0252] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be interpreted broadly to refer to commands, sets of commands, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0253] In addition, software, commands, information, etc. may be sent and received via a transmission medium. For example, when software is sent from a web page, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

[0254] The information, signals, etc. described in the present disclosure may also be represented by any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc. that may be involved in the above description as a whole may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0255] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may also be a signal (signaling). In addition, a signal may also be a message. In addition, a component carrier (CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, etc.

[0256] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0257] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values ​​to predetermined values, or other corresponding information. For example, a wireless resource may be indicated by an index.

[0258] The names used for the above parameters are non-restrictive in any respect. Furthermore, the formulas etc. using these parameters may sometimes differ from those explicitly disclosed in the present disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, and therefore the various names assigned to these various channels and information elements are non-restrictive in any respect.

[0259] In the present disclosure, the terms "base station (BS)", "wireless 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" and the like are used interchangeably. Sometimes, the base station is also referred to as macro cell, small cell, femto cell, pico cell and the like.

[0260] A base station can accommodate one or more (for example, 3) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through a base station subsystem (for example, a small base station for indoor use (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of ​​at least one of a base station and a base station subsystem that provide communication services within the coverage area.

[0261] In the present disclosure, the base station sending information to the terminal may be replaced by the base station instructing the terminal to perform control / action based on the information.

[0262] In the present disclosure, terms such as “mobile station (MS)”, “user terminal (user terminal)”, “user equipment (UE)”, and “terminal” may be used interchangeably.

[0263] For mobile stations, those skilled in the art sometimes also use the following terms: 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.

[0264] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to an object that can move, and the moving speed is arbitrary. In addition, of course, it also includes the situation where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, motorcycles, bicycles, networked cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, two-wheel trailers (rear car), rickshaws, ships (ships and other watercraft: ships and other ships), airplanes, rockets, artificial satellites, Drone (registered trademark), multi-rotor helicopters, quadcopters, balloons and objects mounted on them, and is not limited to this. In addition, the mobile body may also be a mobile body that drives autonomously based on an operation instruction. It can be a means of transportation (such as a car, an airplane, etc.), a mobile body that moves in an unmanned manner (such as a drone, an automatic driving car, etc.), or a robot (man-powered or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operations. 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.

[0265] In addition, the base station in the present disclosure may also be replaced by a user terminal. For example, a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple terminals 20 (for example, it may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) may also apply various forms / implementations of the present disclosure. In this case, it may also be configured that the terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" may also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. may also be replaced by side channels.

[0266] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station may have the functions of the user terminal.

[0267] The terms "determining" and "determining" used in the present disclosure sometimes include a variety of actions. "Determining" and "determining" may include, for example, considering matters that have been judged, calculated, calculated, processed, derived, investigated, searched (for example, searched in a table, database or other data structure), confirmed (ascertaining) as matters that have been "determined" or "determined", etc. In addition, "determining" and "determining" may include matters that have been received (for example, receiving information), transmitted (for example, transmitting information), input, output, accessed (for example, accessed data in memory) as matters that have been "determined" or "determined", etc. In addition, "determining" and "determining" may include matters that have been resolved (resolving), selected (selecting), chosen (choosing), established (establishing), compared (comparing), etc. as matters that have been "determined" or "determined". That is, "judgment" and "decision" may include certain actions that are considered to be "judged" or "decided". In addition, "judgment (decision)" may also be replaced by "assuming", "expecting", "considering", etc.

[0268] The terms "connected", "coupled" or all variations of these terms are intended to indicate any direct or indirect connection or combination between two or more elements, and may include the situation where there is one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be a physical combination or connection, a logical combination or connection, or a combination of these. For example, "access" may be used to replace "connection". In the context of the present disclosure, two elements may 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 as some non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible) region may be used to "connect" or "couple" to each other.

[0269] The reference signal may be referred to as RS (Reference Signal) for short, or may be referred to as a pilot signal (Pilot) according to the applied standard.

[0270] The phrase “based on” used in the present disclosure does not mean “only based on” unless otherwise explicitly stated. In other words, the phrase “based on” means both “only based on” and “at least based on”.

[0271] Any reference to an element using the designations "first", "second", etc. used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, a reference to a first element and a second element does not mean that only two elements can be used or that the first element must precede the second element in any form.

[0272] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section”, “circuit”, “device” or the like.

[0273] When the terms "include", "including" and their variations are used in the present disclosure, these terms are intended to be inclusive, just like the term "comprising". Furthermore, the term "or" used in the present disclosure does not mean an exclusive or.

[0274] A radio frame may be composed of one or more frames in the time domain. In the time domain, one or more frames may be referred to as a subframe. A subframe may also be composed of one or more time slots in the time domain. A subframe may be a fixed time length (e.g., 1 ms) that is independent of a numerology.

[0275] A parameter set may be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. The parameter set may, for example, represent at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, and the like.

[0276] A 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. A slot may be a time unit based on a parameter set.

[0277] A time slot may contain multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in units of time greater than a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type B.

[0278] A radio frame, a subframe, a time slot, a mini-time slot, and a symbol all represent time units for transmitting signals. A radio frame, a subframe, a time slot, a mini-time slot, and a symbol may be referred to by other corresponding names.

[0279] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, and one time slot or one mini time slot may be referred to as a TTI. That is, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. In addition, the unit representing a TTI may not be referred to as a subframe, but as a time slot, a mini time slot, or the like.

[0280] 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 wireless resources (frequency bandwidth, transmission power, etc. that can be used in each terminal 20) to each terminal 20 in units of TTI. In addition, the definition of TTI is not limited to this.

[0281] TTI can be a transmission time unit of data packets (transport blocks), code blocks, code words, etc. after channel coding, or a processing unit such as scheduling and link adaptation. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which the transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0282] In addition, when one time slot or one mini time slot is called TTI, one or more TTIs (i.e., one or more time slots or one or more mini time slots) can be the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit for scheduling can be controlled.

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

[0284] In addition, for a long TTI (for example, a normal TTI, a subframe, etc.), it can be replaced with a TTI having a time length exceeding 1ms, and for a short TTI (for example, a shortened TTI, etc.), it can be replaced with a TTI having a TTI length smaller than the long TTI (longTTI) and greater than 1ms.

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

[0286] In addition, the time domain of an RB may include one or more symbols, and may be the length of one slot, one mini slot, one subframe, or one TTI. One TTI, one subframe, etc. may be composed of one or more resource blocks, respectively.

[0287] In addition, one or more RBs may also be referred to as a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, etc.

[0288] In addition, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0289] A bandwidth part (BWP) (also referred to as partial bandwidth, etc.) may also represent a subset of contiguous common RBs (common resource blocks) for a parameter set in a carrier. Here, the common RBs may be identified by the index of the RBs relative to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0290] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0291] At least one of the set BWPs may be active, and the UE may not assume that a predetermined signal / channel is transmitted or received outside the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

[0292] The above structures of radio frames, subframes, time slots, mini-time slots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of time slots per subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length may be changed in various ways.

[0293] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure also includes a case where the noun following the article is in a plural form.

[0294] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". In addition, the term may mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same way as "different".

[0295] Each form / implementation described in the present disclosure may be used alone or in combination, and may be switched depending on the execution. In addition, notification of predetermined information (e.g., notification of "yes X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the predetermined information).

[0296] The present disclosure is described in detail above, but it should be clear 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 a modification and variation without departing from the subject matter and scope of the present disclosure as determined by the claims. Therefore, the purpose of the description of the present disclosure is to illustrate and not to have any limiting meaning on the present disclosure.

[0297] This international invention patent application claims priority based on Japanese invention patent application No. 2022-081937 filed on May 18, 2022, and all contents of Japanese invention patent application No. 2022-081937 are incorporated herein by reference.

[0298] Description of symbols

[0299] 10: Base Station

[0300] 110: Sending Department

[0301] 120: Receiving Department

[0302] 130: Setting department

[0303] 140: Control Department

[0304] 20: Terminal

[0305] 210: Sending Department

[0306] 220: Receiving Department

[0307] 230: Setting department

[0308] 240: Control Department

[0309] 1001: Processor

[0310] 1002: Storage device

[0311] 1003: Auxiliary storage device

[0312] 1004: Communication device

[0313] 1005: Input device

[0314] 1006: Output device

Claims

1. A terminal comprising: a sending unit, which sends a notification including a service quality level indicator (QoS level indicator) in a physical layer to a base station; and a receiving unit, which receives an uplink grant from the base station, The transmission unit performs uplink transmission to which the QoS level indicated by the QoS level indicator is applied to the base station based on the uplink grant.

2. The terminal according to claim 1, wherein: The notification is a scheduling request, SR.

3. The terminal according to claim 2, wherein: The transmitting unit jointly encodes the SR and the QoS level in the physical layer and transmits the encoded SR to the base station.

4. The terminal according to claim 1, wherein: The notification is a buffer status report, ie, a BSR.

5. The terminal according to claim 4, wherein: The transmitting unit transmits a buffer status to the base station for each QoS level in a physical layer.

6. A communication method, in which a terminal performs the following steps: A sending step, sending a notification including a service quality level indicator (QoS level indicator) in a physical layer to a base station; receiving an uplink grant from the base station; and Based on the uplink grant, a step of performing uplink transmission to the base station to which the QoS level indicated by the QoS level indicator is applied is performed.

Citation Information

Patent Citations

  • Saddle-riding type vehicle

    JP2022081937A