WO2020245894A1

WO2020245894A1 - User terminal and wireless communication method

Info

Publication number: WO2020245894A1
Application number: PCT/JP2019/022058
Authority: WO
Inventors: 翔平吉岡; 聡永田; シャオホンジャン; リフェワン; シャオツェングオ; ギョウリンコウ
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2019-06-03
Filing date: 2019-06-03
Publication date: 2020-12-10

Abstract

The user terminal according to the present disclosure is provided with: a reception unit that receives information related to a plurality of scheduling request (SR) settings; and a control unit that, when a plurality of scheduling request transmissions using a plurality of resources respectively associated with the plurality of SR settings collide in the same time unit, controls the plurality of scheduling request transmissions on the basis of a priority of each of the plurality of scheduling requests. This makes it possible to appropriately control prioritizing the plurality of SRs corresponding to different service types.

Description

User terminal and wireless communication method

The present disclosure relates to a user terminal and a wireless communication method in a next-generation mobile communication system.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of further high-speed data rate, low latency, etc. (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel.10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

A successor system to LTE (for example, 5th generation mobile communication system (5G), 5G + (plus), New Radio (NR), 3GPP Rel.15 or later, etc.) is also being considered.

In a future wireless communication system (hereinafter, also referred to as NR), when uplink data is generated, the UE transmits a scheduling request (Scheduling Request (SR)) at a transmission opportunity (period) of a predetermined cycle. The UE transmits uplink data using an uplink shared channel (for example, Physical Uplink Shared Channel (PUSCH)) scheduled by downlink control information (Downlink Control Information (DCI)) transmitted from the base station according to the SR. To do.

In NR, transmission of multiple SRs (SR resources, etc.) corresponding to different service types (for example, high-reliability and low-latency communications (URLLC) and enhanced Mobile Broad Band (eMBB), etc.) It is assumed that (also referred to as) collide in the same time unit (for example, slot).

However, when the transmissions of a plurality of SRs corresponding to different service types collide within the same time unit, how to control the prioritization of the plurality of SRs becomes a problem. If the prioritization of the plurality of SRs is not properly controlled, it may not be possible to meet the requirements of different service types.

Therefore, one of the purposes of the present disclosure is to provide a user terminal and a wireless communication method capable of appropriately controlling the prioritization of a plurality of SRs corresponding to different service types.

The user terminal according to one aspect of the present disclosure can transmit a plurality of scheduling requests using a receiving unit that receives information on a plurality of scheduling request (SR) settings and a plurality of resources associated with the plurality of SR settings. When a collision occurs within the same time unit, the control unit that controls the transmission of the plurality of scheduling requests based on the priority of each of the plurality of scheduling requests is provided.

According to one aspect of the present disclosure, the prioritization of a plurality of SRs corresponding to different service types can be appropriately controlled.

FIG. 1 is a diagram showing an example of SR setting set information. FIG. 2 is a diagram showing an example of SR resource information. FIG. 3 is a diagram showing an example of SR transmission control. FIG. 4 is a diagram showing an example of LCH setting information. FIG. 5 is a diagram showing an example of a plurality of SR transmissions associated with different service types. FIG. 6 is a diagram showing an example of SR resource information according to the first aspect. FIG. 7 is a diagram showing an example of SR setting information of the first aspect. 8A and 8B are diagrams showing an example of SR priority information using the LCH priority information of the first aspect. FIG. 9 is a diagram showing an example of determining SR priority information according to the second aspect. FIG. 10 is a diagram showing an example of prioritization based on SR priority information according to the third aspect. 11A and 11B are diagrams showing an example of SR priority information notified from the MAC entity. FIG. 12 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 13 is a diagram showing an example of the configuration of the base station according to the embodiment. FIG. 14 is a diagram showing an example of the configuration of the user terminal according to the embodiment. FIG. 15 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.

(Scheduling request)
In the NR, the base station allocates uplink resources to the UE in response to a request (Scheduling Request (SR)) from the user terminal (User Equipment (UE)). The uplink resource is a resource (UL-SCH resource) for a logical uplink channel (for example, Uplink Shared Channel (UL-SCH)) or a physical uplink channel (for example, Physical Uplink). It may be paraphrased as a resource for Shared Channel)).

The UE may transmit the SR by using an uplink control channel (for example, Physical Uplink Control Channel (PUCCH)). The PUCCH format used for SR transmission may be, for example, PUCCH format (PUCCH format (PF)) 0 or 1. PF0 may be composed of 1 or 2 symbols. On the other hand, PF1 may be composed of 4 or more symbols.

A predetermined period for SR transmission using PUCCH (also referred to as transmission occasion, SR transmission opportunity, SR opportunity, transmission period, instance, etc.) may be provided at a predetermined cycle. The SR opportunity may be configured uniquely to the UE.

The UE (or the Medium Access Control (MAC) entity of the UE) may be set (configured with) with the settings for SR of 0 or 1 or more (SR configuration). One SR setting may configure (or be associated with) a set of resources (SR resources) for one or more SR transmissions. The SR resource is set over at least one of one or more bandwidth portions (Bandwidth Part (BWP)) and one or more cells (also referred to as serving cells, component carriers (CC), carriers, etc.). May be done. A maximum of one SR resource may be set for one logical channel per BWP.

Each SR setting may correspond to one or more logical channels (Logical Channel (LCH)). Each LCH may be mapped to 0 or 1 SR setting. The SR setting may be set in the UE by higher layer signaling (for example, Radio Resource Control (RRC) signaling). Each LCH may have a priority value. In the present disclosure, the SR setting may be simply referred to as SR.

The UE may receive information about one or more sets of SR settings (SR setting set information). The SR setting set information may be, for example, "SchedulingRequestConfig" of the RRC control element (Information Element (IE)). The SR setting set information may be set for each cell group, and may be included in, for example, "MAC-Cell Group Config" of RRC IE. Further, the SR setting set information may be set as a MAC parameter. The RRC IE may be referred to as an RRC parameter, an upper layer parameter, or the like.

FIG. 1 is a diagram showing an example of SR setting set information. As shown in FIG. 1, the SR setting set information is a list of information related to each SR setting to be added or updated (SR setting information, for example, "SchedulingRequestToAddMod" of RRC IE) (for example, "schedulingRequestToAddModList" of RRC IE). And at least one of the list of each SR setting information to be released (for example, "schedulingRequestToReleaseList" of RRC IE) may be included.

Each SR setting information (for example, "SchedulingRequestToAddMod" of RRC IE) may include at least one of the following parameters.
-SR setting information (or SR setting) identifier (SR-ID, for example, "schedulingRequestId" of RRC IE)
-Timer for SR transmission in PUCCH (for example, "sr-Prohibit Timer" of RRC IE)
-Maximum number of SR transmissions (for example, "sr-TransMax" of RRC IE)

The SR-ID in each SR setting information may be used to identify an SR instance (SR setting) in the MAC layer. The SR-ID may be included in the LCH setting information (LCH setting information, for example, "Logical Channel Config" of RRC IE). That is, the SR-ID may be used as an identifier for the SR setting associated with the LCH.

The UE may also receive information (SR resource information) regarding SR resources associated with each SR setting. The SR resource information may be, for example, "SchedulingRequestResourceConfig" of RRC IE.

The SR resource information may be set as a UE-specific PUCCH parameter. The SR resource information may be included in the PUCCH setting information for each BWP (PUCCH setting information, for example, "PUCCH-Config" of RRC IE). The PUCCH setting information may include a list of one or more SR resource information (for example, "schedulingRequestResourceToAddModList" of RRC IE).

FIG. 2 is a diagram showing an example of SR resource information. As shown in FIG. 2, the SR resource information may include, for example, at least one of the following parameters.
-SR resource information identifier (SR resource ID, for example, "schedulingRequestResourceId" of RRC IE)
-Identifier of SR setting information (or SR setting) using the SR resource (SR-ID, for example, "schedulingRequestID" of RRC IE)
-Information indicating at least one of the period and offset of the SR resource (also called SR opportunity, etc.) (period / offset information, for example, "periodicityAndOffset" of RRC IE).
-PUCCH resource identifier (PUCCH resource ID, for example, "PUCCH-ResourceId" of RRC IE)

The SR resource set by the SR resource information may be associated with the SR setting information (or SR setting) identified by the SR-ID. The SR resource may include at least one of the above SR opportunity and PUCCH resource.

Further, the cycle may be, for example, 2 or 7 symbols, 1, 2, 4, 5, 8, 10, 16, 20, 40, 80, 160, 320 or 640 slots. For the cycle, a set of possible values may be defined for each subcarrier spacing (SCS).

The UE may transmit an SR using the PUCCH resource indicated by the PUCCH resource ID at the SR opportunity of a predetermined cycle determined based on the cycle / offset information. The UE may control the transmission of the SR based on the SR setting information indicated by the SR-ID.

FIG. 3 is a diagram showing an example of SR transmission control. FIG. 3 shows, for example, an example in which SR opportunities associated with SR-ID in the LCH setting information of LCH # 0 are provided in a 4-slot cycle.

As shown in FIG. 3, when the uplink data arrives, the UE (or the MAC entity of the UE) performs SR at the next SR opportunity of SR-ID associated with LCH # 0 corresponding to the uplink data. You may send it.

When the UE (or the MAC entity of the UE) has not received the uplink grant from the base station, the SR opportunity of a predetermined cycle is reached until the maximum number of SR transmissions (for example, "sr-TransMax" of RRC IE) is reached. SR may be transmitted every time. The UE may transmit uplink data using an uplink shared channel (for example, Physical Uplink Shared Channel (PUSCH) or Uplink Shared Channel (UL-SCH)) assigned by the uplink grant.

The uplink grant is information used for PUSCH scheduling for the UE, and is called downlink control information (Downlink Control Information (DCI)), DCI format 0_0, 0_1, 0_x (x is an arbitrary character string), or the like. You may.

(Logical channel priority)
The UE receives the above LCH setting information (for example, "LogicalChannelConfig" or "mac-LogicalChannelConfig" of RRC IE). The LCH setting information may be included in the information related to the radio link control (Radio Link Control (RLC)) (RLC setting information, for example, "RLC-BearerConfig" of RRC IE). The RLC setting information corresponds to the logical channel in the MAC and is used to set the RLC entity that links to the Packet Data Convergence Protocol (PDCP) entity.

FIG. 4 is a diagram showing an example of LCH setting information. As shown in FIG. 4, the LCH setting information may include at least one of the following parameters.
-Information indicating the priority of LCH (LCH priority information, for example, "priority" of RRC IE)
-Information indicating the preferred bit rate (for example, "prioritised BitRate" of RRC IE)
-Information indicating the bucket size period (for example, "bucketSizeDuration" of RRC IE)
-A list of serving cells to which the MAC Service Data Unit (SDU) generated from the LCH is mapped (eg, "allowedServingCells" in RRC IE).
-Information indicating the neurology to which the MAC SDU generated from the LCH is mapped (for example, "allowed SCS-List" of RRC IE).
-The period of PUSCH in which the MAC SDU generated from LCH will be transmitted (for example, "maxPUSCH-Duration" of RRC IE).
-Identifier of the group to which the LCH belongs (for example, "maxPUSCH-Duration" of RRC IE)
-Identifier of SR setting information applied to LCH (SR-ID, for example, "schedulingRequestId" of RRC IE)
-SR trigger control information when

type

1 or 2 of the setting grant is set (for example, "schedulingRequestId" of RRC IE)
-Information indicating whether or not to apply the delay time for SR transmission for LCH (for example, "logicalChannel SR-DelayTimerApplied" of RRC IE).

The UE (the MAC entity of the UE) may prioritize the LCH based on the above LCH priority information. Specifically, the UE (the MAC entity of the UE) may control at least one such as mapping between the LCH and the transport channel, resource allocation, etc., based on the LCH priority information.

The LCH may be a channel for transmission in the RLC layer between the UE and the base station. The LCH includes, for example, an individual traffic channel (Dedicated Traffic Channel (DTCH)), an individual control channel (Dedicated Control Channel (DCCH)), a common control channel (Common Control Channel (CCCH)), and a paging control channel (Paging Control Channel (DCCH)). PCCH))), at least one of the broadcast control channel (Broadcast Control Channel (BCCH)) may be included.

The transport channel may be a channel that transmits in the MAC layer between the UE and the base station. The transport channels include, for example, a paging channel (Paging Channel (PCH)), a broadcast channel (Broadcast Channel (BCH)), a downlink shared channel (Downlink Shared Channel (DL-SCH)), and an uplink shared channel (Uplink Shared Channel (Uplink Shared Channel). UL-SCH))) and at least one of a random access channel (Random Access Channel (RACH)) may be included.

For example, in the uplink (UPlink (UL)), the MAC entity of the UE may map CCCH, DCCH, and DTCH to UL-SCH, respectively. On the other hand, in the downlink (Downlink (DL)), the MAC entity of the UE may separate the DL-SCH into CCCH, DCCH, and DTCH.

By the way, in NR, further advancement of mobile broadband (enhanced Mobile Broadband (eMBB)), machine type communication (massive Machine Type Communications (mMTC)) that realizes multiple simultaneous connections, highly reliable and low latency communication (Ultra-Reliable and) Service types (also called services, use cases, traffic types, etc.) such as Low-Latency Communications (URLLC) and Industrial IoT (Industrial Internet of Things (IIoT)) are assumed. At least one requirement, such as latency, reliability, packet size, etc., may differ between different service types.

In NR, it is assumed that transmissions of a plurality of SRs (also referred to as SR resources) corresponding to the different service types collide in the same time unit (for example, a slot).

However, when the transmissions (collide with) of a plurality of SRs corresponding to different service types collide within the same time unit, how to control the prioritization of the plurality of SRs becomes a problem. If the prioritization of the plurality of SRs is not properly controlled, it may not be possible to satisfy the requirements of different service types.

FIG. 5 is a diagram showing an example of a plurality of SR transmissions associated with different service types. In FIG. 5, for example, the SR opportunity for SR setting # 1 associated with the first service type (eg, URLLC data) is set in a 4-slot cycle and associated with the second service type (eg, eMBB data). It is assumed that the SR opportunity for SR setting # 2 is set in a cycle of 10 slots. Note that FIG. 5 is merely an example, and the service type, SR opportunity cycle, and the like are not limited to those shown.

For example, in FIG. 5, the SR opportunity for SR setting # 1 is associated with the SR-ID “1” in the LCH setting information for LCH # 1 associated with the first service type (eg, URLLC data). It may be set based on the SR resource information. Further, the SR opportunity for SR setting # 2 is the SR resource information associated with SR-ID "2" in the above LCH setting information for LCH # 2 associated with the second service type (for example, eMBB data). It may be set based on.

As shown in FIG. 5, when data of the second service type (eg, eMBB data) occurs in slot # n-6, the MAC entity of the UE is for LCH # 2 associated with the second service type. At the next SR opportunity (here, PUCCH resources of symbols # 4 to # 10 of slot # n), the physical layer is instructed to transmit SR of SR setting # 2.

Also, if the first service type (eg, URLLC data) occurs in slot # n-1, the MAC entity of the UE will have the next SR opportunity for LCH # 1 associated with that first service type (here). Then, the physical layer is instructed to transmit the SR of the SR setting # 1 in the PUCCH resources of the symbols # 7 and # 8 of the slot # n.

In the case shown in FIG. 5, the PUCCH resource # 1 for SR transmission of SR setting # 1 and the PUCCH resource # 2 for SR transmission of SR setting # 2 collide with each other in slot # n. In this case, the problem is how to control the prioritization between the SR of SR setting # 1 (for example, URLLC SR) and the SR of SR setting # 2 (for example, eMBB SR).

For example, in slot # n of FIG. 5, when priority is given to transmission of SR (for example, eMBB SR) of SR setting # 2 in which data is generated first, transmission of SR of SR setting # 1 (for example, URLLC SR) is given. Delays to the next SR opportunity (here, slot # n + 4). As a result, the requirements of the first service type (for example, URLLC) corresponding to the SR of SR setting # 1 may not be satisfied.

Thus, we present a plurality of SRs (or) in which the UE corresponds to different service types in the RRC layer (first aspect), physical layer (second aspect) or MAC layer (third aspect). The idea was to appropriately control the prioritization of the SR by defining the priority (SR priority) of the SR setting).

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings.

In this embodiment, the service type is recognized based on at least one of LCH, DCI format, Radio Network Temporary Identifier (RNTI), RLC bearer, PDCP layer, and Service Data Adaptation Protocol (SDAP) layer. It may be (decided, implicitly derived).

In the present embodiment, in the user plane of the UE and the base station, the protocol (layer) from the lower layer to the upper layer is arranged in the order of the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and the SDAP layer. It may be specified. Further, in the control plane of the UE and the base station, the protocol from the lower level to the upper level may be defined in the order of the PHY layer, the MAC layer, the RLC layer, the PDCP layer, and the RRC layer.

Information of the same layer may be recognized between the UE and the base station. For example, RRC parameters (eg, RRC IE) may be signaled between the UE and base station RRC entities. Similarly, MAC parameters (eg, MAC control elements, MAC Service Data Unit (SDU), etc.) may be signaled between the UE and the MAC entity of the base station. Also, physical channels (eg, PUCCH, PUSCH, etc.) may be signaled between the UE and base station PHY entities.

In addition, MAC signaling (MAC parameter), RRC signaling (RRC parameter), broadcast information (for example, information transmitted by Physical Broadcast Channel (PBCH) (for example, Master Information Block (MIB)) or system information (for example, System Information). At least one of Block (SIB))) and the like may be referred to as upper layer signaling (upper layer parameter) and the like. Broadcast information may be specified as an RRC parameter. Further, the PHY signaling (physical channel) may be referred to as lower layer signaling (lower layer) or the like.

(First aspect)
In the first aspect, the SR priority may be defined in the RRC layer, and the SR priority may be notified to the UE by RRC signaling (for example, RRC configuration or RRC re-configuration).

Information indicating the SR priority of each SR setting (SR priority information) may be determined based on at least one of the service type and the requirements of the service type. The SR priority information may be, for example, X integers, and may indicate a lower priority (priority level) as the value increases (a higher priority level may be indicated as the value decreases). ). Alternatively, an increasing value may indicate a higher priority (priority level) (a larger value may indicate a higher priority level).

The SR priority information is a parameter newly introduced for the SR priority of the SR setting having the SR-ID (for example, "SchedulingRequestID" of RRC IE) (for example, "SchedulingRequestPriority" of RRC IE). May be good. Alternatively, the SR priority information may be, for example, reusing the above-mentioned LCH priority information indicating the priority of the logical channel (for example, "priority" in "Logical Channel Config" of RRC IE).

<SR priority information included in SR resource information>
The SR priority information may be a newly introduced parameter (for example, "SchedulingRequestPriority" of RRC IE), or may be included in the SR resource information (for example, "SchedulingRequestResourceConfig" of RRC IE).

The SR priority information may be defined for each SR resource (for example, SR opportunity, at least one PUCCH resource for SR transmission). That is, SR priority information may be associated with the SR resource.

It is assumed that SR settings (SR setting information) of a plurality of SR-IDs associated with different service types (for example, URLLC and eMBB) are associated with different SR resources. Therefore, when a plurality of SR resources are duplicated in the same time unit (for example, a slot), the UE transmits SR using which SR resource based on the SR priority information associated with the plurality of SR resources. Can be decided whether to prioritize.

For example, in slot # n of FIG. 5, the SR priority information associated with the SR resource used for transmitting the URLLC SR (PUCCH resource # 1 in FIG. 5) is the SR resource (SR resource used for transmitting the eMBB SR). In FIG. 5, a priority (for example, a smaller value) higher than the SR priority information associated with the PUCCH resource # 2) may be shown.

FIG. 6 is a diagram showing an example of SR resource information according to the first aspect. The SR resource information shown in FIG. 6 (for example, “SchedulingRequestResourceConfig” of RRC IE) may differ from the SR resource information of FIG. 2 in that it includes SR priority information (for example, “SchedulingRequestPriority” of RRC IE).

For example, in FIG. 5, the SR priority information in the SR resource information including the PUCCH resource ID “1” indicating the PUCCH resource # 1 (here, for URLLC SR) is the PUCCH resource # 2 (here, for eMBB SR). ) May be higher than the SR priority information in the SR resource information including the PUCCH resource ID “2”.

In this way, when the SR resource information includes the SR priority information, the SR priority is associated with the SR resource. Therefore, when a plurality of SR resources associated with SRs of different service types are duplicated in the same time unit (for example, slot), the UE can appropriately prioritize the SRs.

<SR priority information included in SR setting information>
The SR priority information may be a newly introduced parameter (for example, "SchedulingRequestPriority" of RRC IE), and is included in the above SR setting information (for example, each "SchedulingRequestToAddMod" in "SchedulingRequestConfig" of RRC IE). It may be.

The SR priority information may be determined for each SR setting identified by the SR-ID (for example, "SchedulingRequestId" of RRC IE). That is, the SR priority information may be associated with the SR setting (SR setting information) identified by the SR-ID.

It is assumed that different service types (eg, URLLC and eMBB) are associated with SR settings (SR setting information) of different SR-IDs. Therefore, when a plurality of SR resources associated with different SR settings are duplicated in the same time unit (for example, slot), which SR is based on the SR priority information associated with each of the different SR settings. It is possible to decide whether to prioritize SR transmission using resources.

For example, in slot # n of FIG. 5, the SR priority information associated with the SR setting # 1 of the URLLC SR has a higher priority than the SR priority information associated with the SR setting # 2 of the eMBB SR (for example, Small value) may be indicated.

FIG. 7 is a diagram showing an example of SR setting information of the first aspect. Each SR setting information (for example, "SchedulingRequestToAddMod" of RRC IE) in the SR setting set information (for example, "SchedulingRequestConfig" of RRC IE) shown in FIG. 7 is SR priority information (for example, "SchedulingRequestPriority" of RRC IE). It may be different from the SR setting set information of FIG. 1 in that it includes.

For example, the SR priority information in the SR setting information including the SR-ID "1" indicating the SR setting # 1 of the URLLC SR in FIG. 5 is the SR-ID "2" indicating the SR setting # 2 of the SR for eMBB. It may indicate a higher priority than the SR priority information in the SR setting information including.

In this way, when the SR setting information includes the SR priority information, the SR priority is associated with the SR setting. Therefore, when a UE duplicates a plurality of SR resources associated with SR settings of SRs of different service types within the same time unit (for example, slot), prioritize the SRs appropriately. Can be done.

<SR priority information using LCH priority information>
The SR priority information may be derived (determined) from the LCH priority information of the LCH associated with the SR setting (for example, "priority" in the "Logical Channel Config" of the RRC IE). For example, the physical layer of the UE may determine the SR priority information from the LCH priority information set in the RRC layer.

The SR priority information may be the same as the LCH priority information indicating the priority of the logical channel associated with the SR setting, or the LCH priority information is mapped (converted) according to a predetermined rule. It may be. The SR priority may be associated with the LCH.

It is assumed that different service types (eg, URLLC and eMBB) are associated with different LCH, and the different LCH is associated with SR settings (SR setting information) of different SR-IDs. Therefore, when a plurality of SR resources associated with different SR settings are duplicated in the same time unit (for example, slot), the UE has SR priority information based on the LCH priority information associated with the different SR settings. It is possible to determine which SR resource is used to prioritize SR transmission based on.

For example, in slot # n of FIG. 5, the LCH priority information associated with the SR setting # 1 of the URLLC SR has a higher priority than the LCH priority information associated with the SR setting # 2 of the eMBB SR (for example, Small value) may be indicated. As a result, the SR priority information of SR setting # 1 may indicate a higher priority than the SR priority information of SR setting # 2.

8A and 8B are diagrams showing an example of SR priority information using the LCH priority information of the first aspect. As described with reference to FIG. 4, the LCH setting information (for example, "LogicalChannelConfig" of RRC IE) includes LCH priority information (for example, "priority" of RRC IE) and SR-ID (for example, "SchedulingRequestId" of RRC IE). )including. That is, an LCH having a predetermined LCH priority is associated with the SR setting identified by the SR-ID.

In FIG. 8A, the SR priority information may be the same as the LCH priority information of the LCH associated with the SR setting identified by the SR-ID. When a single SR setting is associated with one or more LCHs, the LCH priority information having a predetermined value from the LCH priority information of the one or more LCHs is the SR priority information of the single SR setting. May be selected as.

The LCH priority information of the predetermined value is, for example, the minimum value LCH priority information (for example, the highest priority level LCH priority information) or the maximum value LCH priority information (for example, the lowest priority level). LCH priority information) may be used.

In FIG. 8A, for example, since the SR setting # 1 identified by the SR-ID “1” is associated with the LCH # 1 of the LCH priority information “2”, the UE can use the SR priority information of the SR setting # 1. May be determined as "2".

Further, in FIG. 8A, LCH # 3 of LCH priority information "5" and LCH # 4 of LCH priority information "7" are associated with SR setting # 2 identified by SR-ID "2". In this case, the UE may determine, for example, the SR priority information of the SR setting as the LCH priority information “5” of the LCH # 3 having the highest priority level.

In FIG. 8B, a mapping rule between LCH priority information and SR priority information may be predetermined. In FIG. 8B, the values in the first range of the LCH priority information (for example, “1” to “8”) are mapped to the first values of the SR priority information (for example, “1”), and the LCH priority is given. Values in the second range of degree information (eg, "9" to "16") are mapped to second values in SR priority information (eg, "2"). The mapping shown in FIG. 8B is only an example, and is not limited to this. For example, the number of SR priority information values may be 2 or more.

As shown in FIG. 8B, for example, when LCH # 1 of LCH priority information "2" is associated with SR setting # 1, the UE sets the SR priority information of the SR setting # 1 to "" according to the above mapping rule. 1 "may be determined.

Further, in FIG. 8B, LCH # 3 of LCH priority information “10” and LCH # 4 of LCH priority information “12” are associated with SR setting # 2. In this case, the UE may determine, for example, the SR priority information of the SR setting # 2 as "2" corresponding to the LCH priority information "10" of the LCH # 3 having the highest priority level.

As described above, the UE determines the SR priority information of the SR setting based on the LCH priority information of the LCH associated with the SR setting identified by the SR-ID.

For example, in slot # n of FIG. 5, the LCH priority information of LCH # 1 associated with SR setting # 1 of SR for URLLC is the LCH priority information of LCH # 2 associated with SR setting # 2 of SR for eMBB. It may indicate a higher priority level. Therefore, when a plurality of SR resources associated with SR settings of SRs of different service types are duplicated in the same time unit (for example, slot), the LCH priority information of the LCH associated with the SR settings is duplicated. SR priority information can be determined based on the above, and prioritization based on the SR priority information can be appropriately controlled.

<Transmission control based on SR priority information>
The UE transmits the SR having the highest SR priority indicated by the SR priority information included in the SR resource information or the SR setting information, or the SR priority information determined based on the LCH priority information. It may be transmitted using the PUCCH resource or PUSCH. For example, in slot # n of FIG. 5, the UE may transmit the SR of SR setting # 1 having a high SR priority by the PUCCH resource # 1.

Alternatively, the UE multiplexes one or more SRs whose SR priority information satisfies a predetermined condition (for example, some SRs satisfying the condition among all the SRs that collide) in one PUCCH resource or PUSCH. May be sent.

Alternatively, if the UE overlaps multiple SR resources associated with SR settings for SRs of different service types within the same time unit (eg, slot), all overlapping SRs can be combined into a single PUCCH resource or PUSCH. May be transmitted using. For example, in slot # n of FIG. 5, the UE may multiplex both the SR of SR setting # 1 and the SR of SR setting # 2 in PUCCH resource # 1 or # 2 and transmit them.

As described above, in the first aspect, when the transmissions of a plurality of SRs corresponding to different service types collide within the same time unit based on the SR priority defined by the RRC layer, the plurality of SRs Can be properly controlled for prioritization.

(Second aspect)
In the second aspect, the SR priority may be defined in the physical layer. The UE may determine the SR priority of each SR setting based on the parameters for each SR setting.

Specifically, the UE may determine the SR priority value as a function of the parameters for each SR setting. For example, the UE may determine the SR priority value based on at least one of the following parameters:
-LCH priority information of LCH associated with SR setting-Period of SR resource (eg SR opportunity) associated with SR setting-Length of SR resource (eg PUCCH resource) associated with SR setting-Maximum SR setting SR transmission count

It should be noted that one LCH includes an SR setting, an SR opportunity cycle corresponding to the SR setting, a PUCCH resource used for SR transmission corresponding to the SR setting, other SR setting information, and parameters in the SR setting information (for example, maximum). SR transmission function), or at least two combinations thereof may be associated with each other.

For example, the UE may determine the SR priority P _{SR_ID} using the following equation (1).
(Equation 1)
P _{SR_ID} = a · x _{LC_priority} + b · x _{SR_periodicity} + c · y _{PUCCH_length} + d · z _maxSR

Here, a is a weighting factor for the LCH priority information of the LCH associated with the SR setting (for example, the value indicated by "priority" in the "Logical Channel Config" of RRC IE). a may be, for example, a constant constant with a value between 0 and 1.

B is a coefficient for weighting the SR opportunity cycle associated with the SR setting (for example, the cycle indicated by "periodicityAndOffset" in "SchedulingRequestResourceConfig" of RRC IE). b may be, for example, a predetermined constant having a value between 0 and 1.

c is a coefficient for weighting the length (number of symbols) of the PUCCH resource used for SR transmission associated with the SR setting (for example, the PUCCH resource indicated by "PUCCH-ResourceId" in "SchedulingRequestResourceConfig" of RRC IE). .. c may be, for example, a predetermined constant having a value between 0 and 1.

D is a coefficient for weighting the maximum number of SR transmissions in the SR setting (for example, the number of SR transmissions indicated by "sr-TransMax" in "SchedulingRequestToAddMod" of RRC IE). d may be, for example, a predetermined constant having a value between 0 and 1.

x _{LC_priority} may be a value based on the LCH priority information of the logical channel associated with the SR setting (eg, a value based on "priority" in the "Logical Channel Config" of the RRC IE).

x _{SR_periodicity} may be a value based on the cycle of SR opportunities associated with the SR settings (eg, a value based on the cycle indicated by "periodicityAndOffset" in "SchedulingRequestResourceConfig" of RRC IE).

y _{PUCCH_length} is a value based on the length (number of symbols) of the PUCCH resource used for SR transmission associated with the SR setting (for example, based on the length of the PUCCH resource indicated by "PUCCH-ResourceId" in "SchedulingRequestResourceConfig" of RRC IE. Value) may be.

z _maxSR may be a value based on the maximum number of SR transmissions in the SR setting (for example, a value based on the number of SR transmissions indicated by "sr-TransMax" in "SchedulingRequestToAddMod" of RRC IE).

Note that equation (1) is merely an example, and the function used to determine the SR priority _{PSR_ID} is not limited to equation (1). The SR priority P _{SR_ID} may be determined using at least one of the above parameters a, x _{LC_priority} , b, x _{SR_periodicity} , c, y _{PUCCH_length} , d, z _{max SR} .

When a plurality of SR priority P _{SR_ID} (also referred to as SR priority information) of different SR settings determined as described above have the same value, the UE can be selected from any of the following (1) to (5). It may work.

(1) As an error case, transmission of all multiple SRs with different SR settings may be stopped.

(2) One of the different SR settings may be selected and the SR of the selected SR settings may be transmitted. Which SR setting to select may depend on the implementation of the UE.

(3) One of the different SR settings may be selected based on at least one of the start symbol and the length of the PUCCH resource used for SR transmission, and the SR of the selected SR setting may be transmitted. For example, an SR setting in which the start symbol of the PUCCH resource is early or late, an SR setting in which the length of the PUCCH resource is short, or the like may be selected.

(4) One of the different SR settings may be selected based on the LCH priority information of the associated LCH, and the SR of the selected SR settings may be transmitted. For example, the SR setting may be selected in which the LCH priority information indicates the highest priority (for example, the lowest value).

(5) One of the different SR settings may be selected based on the SR opportunity cycle, and the SR of the selected SR settings may be transmitted. For example, an SR setting with a short SR opportunity cycle may be selected.

FIG. 9 is a diagram showing an example of determining SR priority information according to the second aspect. In FIG. 9, SR setting # 1 having SR-ID “1” (for example, SR setting for URLLC) and SR setting # 2 having SR-ID “2” (for example, SR setting for eMBB) are Shown. As shown in FIG. 9, at least one value of the parameters x _{LC_priority} , x _{SR_periodicity} , y _{PUCCH_length} , and z _maxSR related to the SR setting may be converted according to a predetermined rule.

For example, in FIG. 9, the x _{LC_priority} of SR settings # 1 and # 2 may be a value (here, 2 and 5) indicated by the LCH priority information of the logical channel associated with the SR setting.

In addition, the x _{SR_periodicity} of SR settings # 1 and # 2 _{converts the} SR opportunity cycle (here, 2 symbols and 1 slot (14 symbols)) associated with the SR setting so that the shorter the cycle, the higher the priority. The values (here, 0 and 2) may be used. Here, it is assumed that the smaller the value, the higher the priority, but the priority is not limited to this.

Further, y _{PUCCH_length} of SR settings # 1 and # 2 sets the length of the PUCCH resource (here, 2 symbols and 6 symbols) used for SR transmission associated with the SR setting to be higher in priority as the length is shorter. It may be a converted value (here, 1 and 5). Here, it is assumed that the smaller the value, the higher the priority, but the priority is not limited to this.

Further, the z _maxSR of SR settings # 1 and # 2 is a value obtained by converting the maximum number of SR transmissions (here, 4 and 4) of the SR setting into a predetermined rule (here, 0 and 0). May be good.

As shown in FIG. 9, when the constants a = 0, b = 0.5, c = 0.5, d = 0, the SR priority P _{SR_ID} of the SR settings # 1 and # 2 is the above equation (1). ) May be 0.5 and 3.5. SR priority P If the smaller the value of _{SR_ID,} the higher the priority, the UE may give priority to SR setting # 1.

For example, when PUCCH resources corresponding to SR settings # 1 and # 2 collide with each other in slot # n of FIG. 5, even if SR for URLLC using PUCCH resource # 1 corresponding to SR setting # 1 is transmitted. Good. In this case, the SR for eMBB using PUCCH resource # 2 may be dropped or postponed to the next SR opportunity. Alternatively, SRs of both SR settings # 1 and # 2 may be transmitted using PUCCH resources # 1 or # 2.

In the second aspect, since the SR priority can be determined in the physical layer, when a plurality of SR resources associated with different SR settings collide within the same time unit, the priority can be appropriately performed.

Also in the second aspect, the transmission control based on the SR priority information described in the first aspect can be applied. In this case, the priority information of the first aspect may be replaced with the SR priority P _{SR_ID} determined by the physical layer.

(Third aspect)
In the third aspect, the SR priority may be determined in the MAC layer. The MAC entity of the UE may deliver SR priority information indicating SR priority to the physical layer.

The SR priority information notified from the MAC layer to the physical layer is derived (determined) based on the LCH priority information of the LCH associated with the SR setting (for example, "priority" in "Logical Channel Config" of RRC IE). You may.

In the third aspect, the "MAC entity" determines the SR priority information based on the LCH priority information, and the "physical layer" determines the SR priority information based on the LCH priority information in the upper layer parameter. It may be different from the first aspect. More specifically, the third aspect may differ from the first aspect in that SR priority information notification occurs between the MAC entity and the physical layer of the UE.

FIG. 10 is a diagram showing an example of prioritization based on SR priority information according to the third aspect. In FIG. 10, as in FIG. 5, for example, the SR opportunity for SR setting # 1 associated with the first service type (eg, URLLC data) is set in a 4-slot cycle and the second service type (eg, URLLC data) is set. It is assumed that the SR opportunity for SR setting # 2 associated with (eMBB data) is set in a 10-slot cycle.

Further, in FIG. 10, it is assumed that the first service type (for example, URLLC data) is associated with LCH # 1 and the second service type (for example, eMBB data) is associated with LCH # 2. Note that FIG. 10 is merely an example, and the service type, SR opportunity cycle, and the like are not limited to those shown.

As shown in FIG. 10, when data for LCH # 2 (eg, eMBB data) occurs in slot # n-6, the MAC entity of the UE is the next for SR configuration # 2 associated with LCH # 2. Instruct the physical layer to transmit the SR of the SR setting # 2 at the SR opportunity (here, the PUCCH resource of the symbols # 2 to # 8 of the slot # n), and physically obtain the SR priority information of the SR setting # 2. Notify the layer.

Also, if the data for LCH # 1 (eg, URLLC data) occurs in slot # n-1, the MAC entity of the UE will have the next SR opportunity for SR setting # 1 associated with LCH # 1 (here). , The PUCCH resource of the symbols # 8 and # 9 of the slot # n) is instructed to transmit the SR of the SR setting # 1, and the SR priority information of the SR setting # 1 is notified to the physical layer.

The UE (physical layer of the UE) may control the prioritization of SR settings # 1 and # 2 in slot # n based on the SR priority information from the MAC entity.

11A and 11B are diagrams showing an example of SR priority information notified from the MAC entity. 11A and 11B show an example of SR priority information of SR settings # 1 and # 2 of FIG. The LCH priority information of LCH # 1 associated with SR setting # 1 in FIG. 10 is "1", and the LCH priority information of LCH # 2 associated with SR setting # 2 is "8". To do. The smaller the value of the LCH priority information, the higher the priority.

As shown in FIG. 11A, the MA entity of the UE uses the LCH priority information of LCH # 1 and # 2 associated with SR settings # 1 and # 2 as the SR priority information of SR settings # 1 and # 2. The physical layer may be notified. For example, in FIG. 11A, the MA entity of the UE provides LCH priority information “1” and “8” for LCH # 1 and # 2 associated with SR settings # 1 and # 2, respectively, to SR settings # 1 and # 2, respectively. The physical layer may be notified as the SR priority information of 2.

When a single SR setting is associated with one or more LCHs, the MAC entity of the UE has the LCH priority information of the one or more LCHs whose LCH priority information having a predetermined value is the single SR. It may be selected as SR priority information of the setting.

Alternatively, as shown in FIG. 11B, the MAC entity of the UE sets a predetermined value derived from the LCH priority information of LCH # 1 and # 2 associated with SR settings # 1 and # 2 to SR # 1 and # 2. The physical layer may be notified as SR priority information of.

In FIG. 11B, for example, as described in FIG. 8B, a mapping rule between the LCH priority information and the SR priority information may be predetermined. For example, in FIG. 11B, the MA entity of the UE is from the LCH priority information “1” and “8” of LCH # 1 and # 2 associated with SR settings # 1 and # 2, respectively, according to a predetermined mapping rule. The SR priority information "1" and "2" of the SR settings # 1 and # 2 may be derived, and the derived SR priority information may be notified to the physical layer.

When a single SR setting is associated with one or more LCHs, the MAC entity of the UE has a predetermined value (eg, the smallest or largest value) from the LCH priority information of the one or more LCHs. The SR priority information of the single SR setting may be derived from the LCH priority information according to the above mapping rule.

The UE (physical layer of the UE) is notified by the MAC entity when the PUCCH resources used for transmission of SR settings # 1 and # 2 collide in the same time unit (for example, slot # n in FIG. 10). Based on the SR priority information of # 1 and # 2, it may be determined which PUCCH resource is used for SR transmission.

The UE (physical layer of the UE) may transmit only the SR having the highest SR priority indicated by the SR priority information by the PUCCH resource for the SR transmission. For example, in FIG. 10, the UE uses the PUCCH resource # 1 corresponding to the SR setting # 1 based on the SR priority information of the SR settings # 1 and # 2 notified from the MAC entity, and uses the SR for URLLC. May be sent.

Alternatively, the UE (physical layer of the UE) may transmit one or more SRs whose SR priority indicated by the SR priority information satisfies a predetermined condition with the PUCCH resource.

Alternatively, the UE (physical layer of the UE) may transmit all the collided SRs with a PUCCH resource in which the SR priority indicated by the SR priority information satisfies a predetermined condition. For example, in FIG. 10, the UE sets both SRs corresponding to SR settings # 1 and # 2 to PUCCH resource # 1 based on the SR priority information of SR settings # 1 and # 2 notified from the MAC entity. Alternatively, it may be transmitted using # 2.

Alternatively, when the PUSCH is scheduled in the same time unit (for example, slot # n in FIG. 10), the UE (physical layer of the UE) transmits at least one of the conflicting SRs in the PUSCH. May be good.

As described above, in the third aspect, since the MAC entity of the UE notifies the SR priority information to the physical layer, it is appropriate to prioritize a plurality of SRs in which the physical layer of the UE collides in the same time unit. Can be controlled.

(Wireless communication system)
Hereinafter, the configuration of the wireless communication system according to the embodiment of the present disclosure will be described. In this wireless communication system, communication is performed using any one of the wireless communication methods according to each of the above-described embodiments of the present disclosure or a combination thereof.

FIG. 12 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by Third Generation Partnership Project (3GPP). ..

Further, the wireless communication system 1 may support dual connectivity between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC is dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E). -UTRA Dual Connectivity (NE-DC)) may be included.

In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is MN, and the LTE (E-UTRA) base station (eNB) is SN.

The wireless communication system 1 has dual connectivity between a plurality of base stations in the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both MN and SN are NR base stations (gNB). )) May be supported.

The wireless communication system 1 includes a base station 11 that forms a macro cell C1 having a relatively wide coverage, and a base station 12 (12a-12c) that is arranged in the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. You may prepare. The user terminal 20 may be located in at least one cell. The arrangement, number, and the like of each cell and the user terminal 20 are not limited to the mode shown in the figure. Hereinafter, when the

base stations

11 and 12 are not distinguished, they are collectively referred to as the base station 10.

The user terminal 20 may be connected to at least one of the plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (Carrier Aggregation (CA)) and dual connectivity (DC) using a plurality of component carriers (Component Carrier (CC)).

Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1 and the small cell C2 may be included in FR2. For example, FR1 may be in a frequency band of 6 GHz or less (sub 6 GHz (sub-6 GHz)), and FR2 may be in a frequency band higher than 24 GHz (above-24 GHz). The frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

Further, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

The plurality of base stations 10 may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between

base stations

11 and 12, the base station 11 corresponding to the upper station is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to a relay station (relay) is IAB. It may be called a node.

The base station 10 may be connected to the core network 30 via another base station 10 or directly. The core network 30 may include at least one such as Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, at least one of the downlink (Downlink (DL)) and the uplink (Uplink (UL)), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple. Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

The wireless access method may be called a waveform. In the wireless communication system 1, another wireless access system (for example, another single carrier transmission system, another multi-carrier transmission system) may be used as the UL and DL wireless access systems.

In the wireless communication system 1, as downlink channels, downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), and downlink control channels (Physical Downlink Control) shared by each user terminal 20 are used. Channel (PDCCH)) and the like may be used.

Further, in the wireless communication system 1, as the uplink channel, the uplink shared channel (Physical Uplink Shared Channel (PUSCH)), the uplink control channel (Physical Uplink Control Channel (PUCCH)), and the random access channel shared by each user terminal 20 are used. (Physical Random Access Channel (PRACH)) or the like may be used.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted by PDSCH. User data, upper layer control information, and the like may be transmitted by the PUSCH. In addition, Master Information Block (MIB) may be transmitted by PBCH.

Lower layer control information may be transmitted by PDCCH. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information of at least one of PDSCH and PUSCH.

The DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. The PDSCH may be read as DL data, and the PUSCH may be read as UL data.

A control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may be used to detect the PDCCH. CORESET corresponds to a resource that searches for DCI. The search space corresponds to the search area and search method of PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a search space based on the search space settings.

One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. The "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. of the present disclosure may be read as each other.

Depending on the PUCCH, channel state information (Channel State Information (CSI)), delivery confirmation information (for example, it may be called Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.) and scheduling request (Scheduling Request ( Uplink Control Information (UCI) including at least one of SR)) may be transmitted. The PRACH may transmit a random access preamble for establishing a connection with the cell.

In this disclosure, downlinks, uplinks, etc. may be expressed without "links". Further, it may be expressed without adding "Physical" at the beginning of various channels.

In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), and the like may be transmitted. In the wireless communication system 1, the DL-RS includes a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), and a demodulation reference signal (DeModulation). Reference Signal (DMRS)), positioning reference signal (Positioning Reference Signal (PRS)), phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), and the like may be transmitted.

The synchronization signal may be, for example, at least one of a primary synchronization signal (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)). The signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be referred to as SS / PBCH block, SS Block (SSB) and the like. In addition, SS, SSB and the like may also be called a reference signal.

Further, in the wireless communication system 1, even if a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), or the like is transmitted as an uplink reference signal (Uplink Reference Signal (UL-RS)). Good. The DMRS may be called a user terminal specific reference signal (UE-specific Reference Signal).

(base station)
FIG. 13 is a diagram showing an example of the configuration of the base station according to the embodiment. The base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140. The control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may each be provided with one or more.

Note that, in this example, the functional blocks of the feature portion in the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to the present disclosure.

The control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping) and the like. The control unit 110 may control transmission / reception, measurement, and the like using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140. The control unit 110 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the data to the transmission / reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of the communication channel, state management of the base station 10, management of radio resources, and the like.

The transmission / reception unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmission / reception unit 120 includes a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, and the like, which are described based on common recognition in the technical fields according to the present disclosure. be able to.

The transmission / reception unit 120 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

The transmitting / receiving antenna 130 can be composed of an antenna described based on common recognition in the technical field according to the present disclosure, for example, an array antenna.

The transmission / reception unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like. The transmission / reception unit 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.

The transmission / reception unit 120 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.

The transmission / reception unit 120 (transmission processing unit 1211) processes, for example, Packet Data Convergence Protocol (PDCP) layer processing and Radio Link Control (RLC) layer processing (for example, RLC) for data, control information, etc. acquired from control unit 110. RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.

The transmission / reception unit 120 (transmission processing unit 1211) performs channel coding (may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (Discrete Fourier Transform (DFT)) for the bit string to be transmitted. The base band signal may be output by performing processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, digital-analog transform, and other transmission processing.

The transmission / reception unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band via the transmission / reception antenna 130. ..

On the other hand, the transmission / reception unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, or the like on the signal in the radio frequency band received by the transmission / reception antenna 130.

The transmission / reception unit 120 (reception processing unit 1212) performs analog-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) Processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing are applied. User data and the like may be acquired.

The transmission / reception unit 120 (measurement unit 123) may perform measurement on the received signal. For example, the measuring unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, or the like based on the received signal. The measuring unit 123 has received power (for example, Reference Signal Received Power (RSRP)) and reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)). , Signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), and the like may be measured. The measurement result may be output to the control unit 110.

The transmission line interface 140 transmits and receives signals (backhaul signaling) to and from devices included in the core network 30, other base stations 10, and the like, and user data (user plane data) and control plane for the user terminal 20. Data or the like may be acquired or transmitted.

The transmitting unit and the receiving unit of the base station 10 in the present disclosure may be composed of at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140.

Note that the transmission / reception unit 120 may transmit information related to each scheduling request (SR) setting (SR setting information, for example, "SchedulingRequestToAddMod" of RRC IE).

Further, the transmission / reception unit 220 may transmit information regarding resources associated with each SR setting (SR resource information, for example, "SchedulingRequestResourceConfig" of RRC IE).

Further, the transmission / reception unit 220 may transmit information regarding the logical channel associated with each SR setting (LCH setting information, for example, "Logical Channel Config" of RRC IE).

Further, the transmission / reception unit 220 may transmit downlink control information for scheduling PUSCH based on the SR from the user terminal 20.

(User terminal)
FIG. 14 is a diagram showing an example of the configuration of the user terminal according to the embodiment. The user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. The control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may each be provided with one or more.

Note that this example mainly shows the functional blocks of the feature portion in the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to the present disclosure.

The control unit 210 may control signal generation, mapping, and the like. The control unit 210 may control transmission / reception, measurement, and the like using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the data to the transmission / reception unit 220.

The transmission / reception unit 220 may include a baseband unit 221 and an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmission / reception unit 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, and the like, which are described based on common recognition in the technical fields according to the present disclosure.

The transmission / reception unit 220 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit. The transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.

The transmitting / receiving antenna 230 can be composed of an antenna described based on common recognition in the technical field according to the present disclosure, for example, an array antenna.

The transmission / reception unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like. The transmission / reception unit 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.

The transmission / reception unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.

The transmission / reception unit 220 (transmission processing unit 2211) processes, for example, PDCP layer processing, RLC layer processing (for example, RLC retransmission control), and MAC layer processing (for example, for data, control information, etc. acquired from the control unit 210). , HARQ retransmission control), etc., to generate a bit string to be transmitted.

The transmission / reception unit 220 (transmission processing unit 2211) performs channel coding (may include error correction coding), modulation, mapping, filtering processing, DFT processing (if necessary), and IFFT processing for the bit string to be transmitted. , Precoding, digital-to-analog conversion, and other transmission processing may be performed to output the baseband signal.

Whether or not to apply the DFT process may be based on the transform precoding setting. The transmission / reception unit 220 (transmission processing unit 2211) described above for transmitting a channel (for example, PUSCH) using the DFT-s-OFDM waveform when the transform precoding is enabled. The DFT process may be performed as the transmission process, and if not, the DFT process may not be performed as the transmission process.

The transmission / reception unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. to the radio frequency band on the baseband signal, and transmit the signal in the radio frequency band via the transmission / reception antenna 230. ..

On the other hand, the transmission / reception unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, or the like on the signal in the radio frequency band received by the transmission / reception antenna 230.

The transmission / reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering processing, demapping, demodulation, and decoding (error correction) for the acquired baseband signal. Decoding may be included), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.

The transmission / reception unit 220 (measurement unit 223) may perform measurement on the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, or the like based on the received signal. The measuring unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like. The measurement result may be output to the control unit 210.

The transmission unit and the reception unit of the user terminal 20 in the present disclosure may be composed of at least one of the transmission / reception unit 220, the transmission / reception antenna 230, and the transmission line interface 240.

Note that the transmission / reception unit 220 may receive information related to each scheduling request (SR) setting (SR setting information, for example, "SchedulingRequestToAddMod" of RRC IE).

Further, the transmission / reception unit 220 may receive information regarding resources associated with each SR setting (SR resource information, for example, "SchedulingRequestResourceConfig" of RRC IE).

Further, the transmission / reception unit 220 may receive information regarding the logical channel associated with each SR setting (LCH setting information, for example, "Logical Channel Config" of RRC IE).

When the transmission of a plurality of scheduling requests using a plurality of resources associated with a plurality of SR settings conflicts within the same time unit, the control unit 210 describes the plurality of scheduling requests based on the priority of each of the plurality of scheduling requests. You may control the transmission of multiple scheduling requests.

The information indicating the priority may be included in the information (SR resource information) regarding the plurality of resources associated with the plurality of SR settings (first aspect). Alternatively, the information indicating the priority may be included in the information regarding the plurality of SR settings (SR setting information) (first aspect).

The control unit 210 has information indicating the priority of each of the plurality of scheduling requests (SR priority) based on the information indicating the priority of the plurality of logical channels associated with the plurality of SR settings (LCH priority information). Degree information) may be determined (first and third aspects).

The control unit 210 may determine the SR priority information based on the LCH priority set in the RRC layer (first aspect). The control unit 210 may be an entity of the physical layer. The control unit 210 may control the transmission of a plurality of SRs based on the SR priority information.

The control unit 210 may include a Medium Access Control (MAC) layer, a physical layer entity, and a physical layer entity. The entity of the MAC layer determines the information (SR priority information) indicating the priority of each of the plurality of scheduling requests based on the information (LCH priority information) indicating the priority of the plurality of logical channels. , The physical layer may be notified (third aspect). The entity of the physical layer may control the transmission of a plurality of SRs based on the SR priority information.

The control unit 210 has information indicating the priority of the plurality of logical channels associated with the plurality of SR settings, the period of each of the plurality of resources, the length of each of the plurality of resources, and the maximum of each of the plurality of scheduling requests. The information indicating the priority may be determined based on at least one of the number of transmissions of. The control unit 210 may be an entity of the physical layer.

The transmission / reception unit 220 may detect downlink control information that schedules PUSCH based on SR from the user terminal 20, and control transmission of uplink data using the PUSCH.

(Hardware configuration)
The block diagram used in the description of the above embodiment shows a block of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Further, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one physically or logically connected device, or directly or indirectly (for example, two or more physically or logically separated devices). , Wired, wireless, etc.) and may be realized using these plurality of devices. The functional block may be realized by combining the software with the one device or the plurality of devices.

Here, the functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and deemed. , Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (constituent unit) for functioning transmission may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like. As described above, the method of realizing each of them is not particularly limited.

For example, the base station, user terminal, and the like in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. FIG. 15 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment. The base station 10 and the user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. ..

In the present disclosure, the terms of devices, circuits, devices, sections, units, etc. can be read as each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

For example, although only one processor 1001 is shown, there may be a plurality of processors. Further, the processing may be executed by one processor, or the processing may be executed simultaneously, sequentially, or by using other methods by two or more processors. The processor 1001 may be mounted by one or more chips.

For each function of the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as the processor 1001 and the memory 1002, the processor 1001 performs an operation and communicates via the communication device 1004. It is realized by controlling at least one of reading and writing of data in the memory 1002 and the storage 1003.

The processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), and the like may be realized by the processor 1001.

Further, the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and may be realized in the same manner for other functional blocks.

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

The storage 1003 is a computer-readable recording medium, for example, a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disc (Compact Disc ROM (CD-ROM)), a digital versatile disk, etc.). At least one of Blu-ray® disks, removable disks, hard disk drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers, and other suitable storage media. It may be composed of. The storage 1003 may be referred to as an auxiliary storage device.

The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)). It may be configured to include. For example, the transmission / reception unit 120 (220), the transmission / reception antenna 130 (230), and the like described above may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be physically or logically separated from the transmission unit 120a (220a) and the reception unit 120b (220b).

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

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

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

(Modification example)
The terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channels, symbols and signals (signals or signaling) may be read interchangeably. Also, the signal may be a message. The reference signal can also be abbreviated as RS, and may be called a pilot, a pilot signal, or the like depending on the applied standard. Further, the component carrier (Component Carrier (CC)) may be referred to as a cell, a frequency carrier, a carrier frequency, or the like.

The wireless frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the wireless frame may be referred to as a subframe. Further, the subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (eg, 1 ms) that is independent of numerology.

Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel. Numerology includes, for example, subcarrier spacing (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, and wireless frame configuration. , A specific filtering process performed by the transmitter / receiver in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.

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

The slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain. Further, the mini slot may be called a sub slot. A minislot may consist of a smaller number of symbols than the slot. A PDSCH (or PUSCH) transmitted in time units larger than the minislot may be referred to as a PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (PUSCH) mapping type B.

The wireless frame, subframe, slot, mini slot and symbol all represent the time unit when transmitting a signal. The radio frame, subframe, slot, minislot and symbol may have different names corresponding to each. The time units such as frames, subframes, slots, mini slots, and symbols in the present disclosure may be read as each other.

For example, one subframe may be called TTI, a plurality of consecutive subframes may be called TTI, and one slot or one minislot may be called TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms. It may be. The unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units. The definition of TTI is not limited to this.

The TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation. When a TTI is given, the time interval (for example, the number of symbols) to which the transport block, code block, code word, etc. are actually mapped may be shorter than the TTI.

When one slot or one mini slot is called TTI, one or more TTIs (that is, one or more slots or one or more mini slots) may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like. TTIs shorter than normal TTIs may be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots, and the like.

The long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (for example, shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms. It may be read as a TTI having the above TTI length.

A resource block (Resource Block (RB)) is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain. The number of subcarriers contained in the RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers contained in the RB may be determined based on numerology.

Further, the RB may include one or more symbols in the time domain, and may have a length of 1 slot, 1 mini slot, 1 subframe or 1 TTI. Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.

One or more RBs are a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, and an RB. It may be called a pair or the like.

Further, the resource block may be composed of one or a plurality of resource elements (Resource Element (RE)). For example, 1RE may be a radio resource area of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (which may also be called partial bandwidth) represents a subset of consecutive common resource blocks (RBs) for a neurology in a carrier. May be good. Here, the common RB may be specified by the index of the RB with respect to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be set in one carrier for the UE.

At least one of the configured BWPs may be active, and the UE may not expect to send or receive a given signal / channel outside the active BWP. In addition, "cell", "carrier" and the like in this disclosure may be read as "BWP".

Note that the above-mentioned structures such as wireless frames, subframes, slots, mini slots, and symbols are merely examples. For example, the number of subframes contained in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in the RB. The number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

Further, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values from predetermined values, or using other corresponding information. It may be represented. For example, radio resources may be indicated by a given index.

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

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

In addition, information, signals, etc. can be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layers. Information, signals, etc. may be input / output via a plurality of network nodes.

The input / output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, signals, etc. can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

The notification of information is not limited to the mode / embodiment described in the present disclosure, and may be performed by using another method. For example, the notification of information in the present disclosure includes physical layer signaling (for example, downlink control information (DCI)), uplink control information (Uplink Control Information (UCI))), and higher layer signaling (for example, Radio Resource Control). (RRC) signaling, broadcast information (master information block (MIB), system information block (SIB), etc.), medium access control (MAC) signaling), other signals or combinations thereof May be carried out by.

Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), and the like. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, or the like. Further, MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).

In addition, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit notification, but implicitly (for example, by not notifying the predetermined information or another information). May be done (by notification of).

The determination may be made by a value represented by 1 bit (0 or 1), or by a boolean value represented by true or false. , May be done by numerical comparison (eg, comparison with a given value).

Software is an instruction, instruction set, code, code segment, program code, program, subprogram, software module, whether called software, firmware, middleware, microcode, hardware description language, or another name. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted to mean.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, a website where software uses at least one of wired technology (coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.). When transmitted from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.

The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may mean a device (eg, a base station) included in the network.

In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "pseudo-colocation (Quasi-Co-Location (QCL))", "Transmission Configuration Indication state (TCI state)", "space". "Spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", Terms such as "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel" are compatible. Can be used for

In the present disclosure, "base station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission point (Transmission Point (TP))", "Reception point (Reception Point (RP))", "Transmission / reception point (Transmission / Reception Point (TRP))", "Panel" , "Cell", "sector", "cell group", "carrier", "component carrier" and the like can be used interchangeably. Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.

The base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small indoor base station (Remote Radio)). Communication services can also be provided by Head (RRH))). The term "cell" or "sector" refers to part or all of the coverage area of at least one of the base stations and base station subsystems that provide communication services in this coverage.

In this disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" are used interchangeably. Can be done.

Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , Handset, user agent, mobile client, client or some other suitable term.

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

Further, the base station in the present disclosure may be read by the user terminal. For example, communication between a base station and a user terminal has been replaced with communication between a plurality of user terminals (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Each aspect / embodiment of the present disclosure may be applied to the configuration. In this case, the user terminal 20 may have the function of the base station 10 described above. In addition, words such as "up" and "down" may be read as words corresponding to communication between terminals (for example, "side"). For example, the uplink, downlink, and the like may be read as side channels.

Similarly, the user terminal in the present disclosure may be read as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

In the present disclosure, the operation performed by the base station may be performed by its upper node (upper node) in some cases. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal are performed by the base station and one or more network nodes other than the base station (for example,). Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. can be considered, but it is not limited to these), or it is clear that it can be performed by a combination thereof.

Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched with execution. In addition, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.

Each aspect / embodiment described in the present disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), LTE 802. 20, Ultra-WideBand (UWB), Bluetooth®, other systems that utilize suitable wireless communication methods, next-generation systems extended based on these, and the like. In addition, a plurality of systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

The phrase "based on" as used in this disclosure does not mean "based on" unless otherwise stated. In other words, the statement "based on" means both "based only" and "at least based on".

Any reference to elements using designations such as "first", "second", etc. as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted or that the first element must somehow precede the second element.

The term "determining" as used in this disclosure may include a wide variety of actions. For example, "judgment (decision)" means judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry) ( For example, searching in a table, database or another data structure), ascertaining, etc. may be considered to be "judgment".

In addition, "judgment (decision)" means receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), access (for example). It may be regarded as "judgment (decision)" of "accessing" (for example, accessing data in memory).

In addition, "judgment (decision)" is regarded as "judgment (decision)" of solving, selecting, choosing, establishing, comparing, and the like. May be good. That is, "judgment (decision)" may be regarded as "judgment (decision)" of some action.

In addition, "judgment (decision)" may be read as "assuming", "expecting", "considering", and the like.

The "maximum transmission power" described in the present disclosure may mean the maximum value of the transmission power, may mean the nominal UE maximum transmit power, or may mean the rated maximum transmission power (the). It may mean rated UE maximum transmit power).

The terms "connected", "coupled", or any variation thereof, as used herein, are any direct or indirect connection or connection between two or more elements. Means, and can include the presence of one or more intermediate elements between two elements that are "connected" or "joined" to each other. The connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access".

In the present disclosure, when two elements are connected, using one or more wires, cables, printed electrical connections, etc., and as some non-limiting and non-comprehensive examples, the radio frequency domain, microwaves. It can be considered to be "connected" or "coupled" to each other using frequency, electromagnetic energy having wavelengths in the light (both visible and invisible) regions, and the like.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". The term may mean that "A and B are different from C". Terms such as "separate" and "combined" may be interpreted in the same way as "different".

When "include", "including" and variations thereof are used in the present disclosure, these terms are as comprehensive as the term "comprising". Is intended. Furthermore, the term "or" used in the present disclosure is intended not to be an exclusive OR.

In the present disclosure, if articles are added by translation, for example, a, an and the in English, the disclosure may include that the nouns following these articles are in the plural.

Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as a modified or modified mode without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for purposes of illustration and does not bring any limiting meaning to the invention according to the present disclosure.

Claims

A receiver that receives information about multiple scheduling request (SR) settings,
When the transmission of a plurality of scheduling requests using a plurality of resources associated with the plurality of SR settings conflicts within the same time unit, the plurality of scheduling requests are based on the priority of each of the plurality of scheduling requests. Control unit that controls the transmission of
A user terminal characterized by comprising.
The user terminal according to claim 1, wherein the information indicating the priority is included in the information related to the plurality of resources associated with the plurality of SR settings or the information related to the plurality of SR settings.
The claim is characterized in that the control unit determines the information indicating the priority of each of the plurality of scheduling requests based on the information indicating the priority of the plurality of logical channels associated with the plurality of SR settings. Item 1. The user terminal according to item 1.
The control unit includes a medium access control (MAC) layer entity and a physical layer entity.
The entity of the MAC layer determines the information indicating the priority of each of the plurality of scheduling requests based on the information indicating the priority of the plurality of logical channels, and notifies the physical layer. The user terminal according to claim 3.
The control unit has information indicating the priority of the plurality of logical channels associated with the plurality of SR settings, the period of each of the plurality of resources, the length of each of the plurality of resources, and the maximum of each of the plurality of scheduling requests. The user terminal according to claim 1, wherein the information indicating the priority is determined based on at least one of the transmission times of the above.
The process of receiving information about multiple scheduling request (SR) settings, and
When the transmission of a plurality of scheduling requests using a plurality of resources associated with the plurality of SR settings conflicts within the same time unit, the plurality of scheduling requests are based on the priority of each of the plurality of scheduling requests. And the process of controlling the transmission of
A wireless communication method of a user terminal, characterized in that it has.