JP7385339B2 - Terminals, wireless communication methods and systems - Google Patents

Description

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

In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified for the purpose of higher data rates, lower delays, etc. (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel. 15 or later) are also being considered.

3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

In future wireless communication systems (for example, NR), data transmission methods include broadcast transmission, which transmits system information, etc., to UEs within a cell, and unicast transmission, which transmits information individually to each user terminal (UE). It is being considered that multicast transmission, in which the transmission is performed for some UEs (eg, a group of UEs) within a cell, is supported.

Multicast transmissions (e.g., logical channels, Multicast Traffic Channels (MTCH), multicast data, etc.) are similar to broadcast or unicast transmissions, as well as physical downlink shared channels (e.g., Physical Downlink Shared Channels (PDSCH)). )) is being considered. Specifically, it is being considered that MTCH is mapped to a downlink shared channel (eg, Downlink Shared Channel (DL-SCH)), which is a transport channel, and that DL-SCH is mapped to PDSCH.

In this case, it is also assumed that data transmitted by multicast transmission (for example, PDSCH) or data transmitted by multicast transmission and data transmitted by unicast transmission or broadcast transmission overlap in the time domain. However, sufficient studies have not yet been made on how to control the reception processing of the UE when data overlaps with each other or with other data due to multicast transmission.

Therefore, one object of the present disclosure is to provide a terminal , a wireless communication method , and a system that can appropriately communicate even when multicast transmission is supported.

A terminal according to an aspect of the present disclosure is a terminal that uses a first downlink shared channel scheduled using a first type of RNTI (Radio Network Temporary Identifier) for multicast and another type of RNTI. a second downlink shared channel scheduled using the second downlink shared channel ; and a receiving unit configured to receive at least one of the first downlink shared channel and the second downlink shared channel. and a control unit that controls the first downlink that overlaps in the time domain based on the capability of the terminal when the other type of RNTI is a unicast RNTI. The present invention is characterized in that control is performed to perform decoding of both the shared channel and the second downlink shared channel .

According to one aspect of the present disclosure, communication can be performed appropriately even when multicast transmission is supported.

FIG. 1 is a diagram illustrating an example of multicast transmission in a single cell. FIG. 2 is a diagram illustrating an example of multicast transmission in multiple cells. FIG. 3 is a diagram illustrating an example of first scheduling of multicast transmission. FIG. 4 is a diagram illustrating an example of second scheduling of multicast transmission. FIG. 5 is a diagram illustrating an example of third scheduling of multicast transmission. FIGS. 6A and 6B are diagrams illustrating an example of allocation of multicast PDSCH and broadcast PDSCH. 7A and 7B are diagrams illustrating an example of reception processing for multicast PDSCHs that overlap in the time domain, or for a multicast PDSCH and a broadcast PDSCH. FIGS. 8A and 8B are diagrams illustrating an example of reception processing for multicast PDSCH and broadcast PDSCH that overlap in the time domain. 9A and 9B are diagrams illustrating an example of allocation of multicast PDSCH, unicast PDSCH, and broadcast PDSCH. FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment.

(UE status)
In future wireless communication systems (hereinafter also referred to as NR), terminals (also referred to as user terminals, user equipment (UE), devices, etc.) will have multiple states depending on traffic activity. ).

For example, an NR UE may have three states in the Radio Resource Control (RRC) layer: an idle state, an inactive state, and a connected state. This state is also called a UE state, RRC state, etc.

Here, the idle state is a state in which an RRC connection between the UE and the base station is not established, and is also called an RRC idle state (RRC_IDLE state), RRC idle (RRC_IDLE), etc. In order for a UE in an idle state to transition to a connected state in which data transfer is possible, reconfiguration of the RRC connection is required.

The inactive state is a state in which an RRC connection between the UE and the base station is established, but data transmission is not possible, and is also called an RRC inactive state (RRC_INACTIVE state), RRC inactive (RRC_INACTIVE), etc. Since the RRC connection has been established for the UE in the inactive state, the UE can transition to the connected state earlier than the idle state. Therefore, the delay time until the start of data transmission is shorter than that of an idle UE.

The connected state is a state in which an RRC connection between the UE and the base station is established and data transmission is possible, and is also called an RRC connected state (RRC_CONNECTED state), RRC connected state (RRC_CONNECTED), etc. A UE in a connected state monitors a downlink control channel (e.g., Physical Downlink Control Channel (PDCCH)) to determine whether data is scheduled or not, compared to an idle or inactive state. As a result, power consumption increases.

(Frequency range)
Furthermore, in NR, support for multiple frequency ranges (FR) is being considered. For example, the first FR (FR1) is 410 MHz to 7.125 GHz. The second FR (FR2) is 24.25 GHz to 52.6 GHz. The third FR (FR3) is 7.125 GHz to 24.25 GHz. The fourth FR (FR4) is 52.6 GHz to 114.25 GHz. The UE may support at least one of the plurality of FRs.

(multicast)
In addition, NR is considering supporting unicast, which is a one-to-one (Point To Point (PTP)) communication method, and broadcast and multicast, which are one-to-many (Point To Multipoint (PTM)) communication methods. ing.

In broadcasting, important information such as system information is transmitted to many UEs in a cell (eg, all UEs in the cell). Broadcast transmission is used not only for initial connection of the UE but also for transmitting information regarding changes in system information after entering the RRC connected state.

In multicasting, the same message is sent to one or more terminals (also called user terminals, user equipment (UE), devices, etc.) located in a specific area (for example, Multimedia Broadcast Multicast Service (MBMS) service area, etc.). content will be sent. The specific area may consist of a single cell or multiple cells. Multicast in which the specific area is configured with a single cell may be called single cell (SC)-based PTM (SC-PTM) or the like.

Multicast transmissions and other transmissions (e.g., broadcast or unicast transmissions) may occur in the same time unit (e.g., slot) within the same cell, or in different time units (e.g., time (may be multiplexed). The time unit for performing multicast transmission within a radio frame may be determined in advance by specifications, or may be configured (notified) to the UE by upper layer signaling.

Note that in the present disclosure, upper layer signaling includes at least one of Radio Resource Control (RRC) signaling, system information (for example, Remaining Minimum System Information (RMSI), Other system information (OSI), and System Information Block (SIB)). The information may be at least one of broadcast information (for example, Physical Broadcast Channel (PBCH), Master Information Block (MIB)), Medium Access Control (MAC) signaling, and Radio Link Control (RLC) signaling.

Alternatively, multicast transmissions and other transmissions (eg, broadcast or unicast transmissions) may occur within different cells. A UE capable of Carrier Aggregation (CA) or Dual Connectivity (DC) can receive multicast transmissions in one cell and receive or transmit unicast transmissions in other cells. Good too. Note that a UE that does not perform CA or DC may receive multicast transmission by handing over to a cell where multicast transmission is performed.

Note that the cell may be referred to as a serving cell, a component carrier (CC), a carrier, or the like.

In multicast transmission, for example, a multicast traffic channel (MTCH) or an MTCH and a multicast control channel (MCCH) may be used as a logical channel.

Data to be multicasted (also referred to as multicast data, traffic, etc.) may be transmitted on the MTCH. Control information necessary for reception of MTCH may be transmitted on MCCH. Note that in SC-PTM, MTCH and MCCH may be referred to as SC-MTCH, SC-MCCH, etc., respectively.

The MTCH and MCCH, which are logical channels, may be mapped to a downlink shared channel (DL-SCH), which is a transport channel, in a medium access control (MAC) layer. Further, the DL-SCH may be mapped to a physical downlink shared channel (PDSCH), which is a physical channel, in the physical (PHY) layer.

Note that in unicast transmission, for example, a dedicated traffic channel (DTCH), a dedicated control channel (DCCH), or the like may be used as a logical channel. DTCH and DCCH may be mapped to DL-SCH at the MAC layer, and DL-SCH may be mapped to PDSCH at the physical layer. In this way, multicast and unicast transmissions may be associated with the same transport channel and physical channel (ie, DL-SCH and PDSCH).

<Multicast transmission in BWP units>
Furthermore, in NR, it is assumed that one or more partial bands (Bandwidth Part (BWP)) are provided within a cell. Therefore, in NR, multicast transmission may be performed not only on a cell-by-cell basis but also on a BWP-by-BWP basis within a cell. The same type of multicast transmission may be performed between different BWPs within a cell, or different types of multicast transmission may be performed between them.

FIG. 1 is a diagram illustrating an example of multicast transmission in a single cell. In FIG. 1, for example, it is assumed that the UE performs CA or DC using a plurality of cells (here, cells #0 to #2). Here, it is assumed that a certain type (here, type a) of multicast transmission (or multicast service) is supported in cell #0, which is the PCell.

As shown in FIG. 1, cell #0 includes one or more BWPs (here, BWPs #0 to #2). Multicast transmission may be supported in at least one BWP in cell #0 (here, BWP #1). For example, in FIG. 1, type a multicast transmission is supported in BWP #1 in cell #0.

Note that FIG. 1 is merely an example, and the number and types of BWPs for which multicast transmission is supported within a single cell are not limited to those shown. Further, in FIG. 1, cells #0 and #1 are provided in FR1, and cell #2 is provided in FR2, but this is merely an example and is not limited to what is illustrated. For example, cells #0 to #3 may belong to the same FR, or at least two of cells #0 to #3 may belong to different FRs.

FIG. 2 is a diagram illustrating an example of multicast transmission in multiple cells. In FIG. 2, for example, it is assumed that the UE performs CA or DC using a plurality of cells (here, cells #0 to #3). Here, it is assumed that one or more types of multicast transmission are supported in cell #0 and cell #2, which are PCells.

For example, in FIG. 2, cell #0 supports type a and b multicast transmissions, and cell #2 supports type c multicast transmissions. Further, BWP #1 of cell #0 supports multicast services of types a and b, while multicast service of type a is supported in BWP #2, and multicast service of type b is not supported. Furthermore, BWPs #0 to #2 of cell #2 in FIG. 2 support the same type c multicast service.

At least one of the types supported in each cell that supports multicast transmission may be supported in each BWP within each cell. The types supported between BWPs within the same cell may be the same or different.

Note that FIG. 2 is merely an example, and the number of cells that support multicast services, the number and types of BWPs that support multicast services within each cell, etc. are not limited to what is illustrated. In addition, in FIG. 2, cells #0 and #1 are FR1, and cells #2 and #3 are FR2, and a cell that supports multicast service is provided for each FR, but this is merely an example, and the illustrated Not limited. For example, cells supporting multicast services may be provided for each cell group.

<Scheduling multicast transmission>
Multicast transmission may be supported in at least one of the following groups determined based on the UE state (RRC state):
(1) a group that includes only UEs in a particular UE state (e.g., idle, inactive, or connected); (2) a group that includes UEs in a first UE state (e.g., idle/inactive); or (3) a first group containing UEs in a first UE state (e.g., idle/inactive state); a second group containing UEs in two UE states (e.g. connected state)

Scheduling of multicast transmission for the above groups (for example, (1) to (3) above) will be explained. For example, the following three scheduling methods are envisaged.

In the first scheduling, the UE receives system information for multicast (for example, step S11 in FIG. 3), and selects the MCCH based on configuration information regarding the MCCH (MCCH configuration information) included in the system information. MTCH may be received (for example, step S13 in FIG. 3) based on the information (MCCH information) transmitted by the MCCH (for example, step S13 in FIG. 3). The UE may be at least one of an idle UE, an inactive UE, and a connected UE.

Note that in the present disclosure, the information transmitted by MCCH may be information for receiving multicast transmission (for example, MTCH). The information for receiving the multicast transmission (MTCH) may be the information transmitted on the PDSCH, or may be referred to as RLC signaling information, etc., and is not necessarily the information transmitted on the MCCH. Not limited.

In the second scheduling, the UE may receive multicast system information (for example, step S21 in FIG. 4), and may receive MTCH based on multicast configuration information included in the system information (for example, in FIG. 4 step S22). The UE may be at least one of an idle UE, an inactive UE, and a connected UE.

In the third scheduling, the UE receives an RRC message (e.g., RRC reconfiguration message) (e.g., step S31 in FIG. 5), and receives the MTCH based on the multicast configuration information included in the RRC message. (For example, step S31 in FIG. 5). The UE may be a UE in a connected state.

In the first to third scheduling, the UE transmits the MTCH via a PDSCH scheduled by a PDCCH (or DCI) that is CRC-scrambled by a specific Radio Network Temporary Identifier (RNTI). You may receive it.

The specific RNTI may be an RNTI for each multicast transmission (for each type of multicast transmission). The particular RNTI may be called, for example, a group (G)-RNTI, a single cell (SC)-RNTI, a multicast (M or MC)-RNTI, a group cast RNTI, etc. The G-RNTI value may be the same between UEs belonging to the same group (eg, (1) to (3) above).

One or more G-RNTIs may be installed in a given UE. Each G-RNTI may be associated with one or more types of multicast transmissions supported by the UE in a cell or cells.

For example, for a UE in an idle or inactive state, one or more G-RNTIs may transmit at least one of system information and L1 signaling for multicast (e.g., information transmitted on the MCCH and at least one of DCI). You may also be notified using

In addition, one or more G-RNTIs transmit at least one of multicast system information, L1 signaling (for example, at least one of information transmitted on MCCH and DCI), and RRC signaling to a UE in a connected state. You may also be notified using

The maximum number X of G-RNTIs that can be configured for a certain UE in a certain cell or a certain BWP may be defined in a specification, or may be configured based on the UE's capabilities. For example, the maximum number of G-RNTIs X may be set so as not to exceed the UE capability reported by the UE.

≪First scheduling≫
FIG. 3 is a diagram illustrating an example of first scheduling of multicast transmission. The first scheduling shown in FIG. 3 may be applied to groups that include at least UEs in an idle/inactive state. The group may or may not include UEs in a connected state.

As shown in FIG. 3, in step S11, the UE may receive multicast system information (for example, SIB20). Specifically, in step S111, the UE monitors a search space set including one or more search spaces, and selects a PDCCH (DCI) that is CRC scrambled by a specific RNTI (for example, System Information (SI)-RNTI). May be detected.

In step S112, the UE may acquire the system information via the PDSCH scheduled by the DCI. The system information may include configuration information regarding MCCH (MCCH configuration information).

The MCCH configuration information includes, for example, the period in which the MCCH is transmitted (repetition period), the time offset, and the period in which information transmitted on the MCCH is updated (modification period). It may include at least one.

In step S12, the UE receives the MCCH based on the MCCH configuration information in the system information. Specifically, in step S121, the UE may monitor the search space set and detect a PDCCH (DCI) that is CRC scrambled with a specific identifier.

The specific identifier may be a specific RNTI (eg, Single Cell (SC)-RNTI) or a Temporary Mobile Group Identifier. The specific identifier may be included in the MCCH configuration information.

In step S122, the UE may acquire the MCCH via the PDSCH scheduled by the DCI. MCCH may be repeatedly transmitted at the above-mentioned repetition period. The same information may be transmitted on the MCCH for each repetition period within the update period. When the information transmitted on the MCCH is changed, the immediately previous update cycle may notify that the information transmitted on the MCCH will be changed in the next update cycle. The notification may be called an SC-MCCH change notification or the like.

PDCCH may be used for the notification. The UE may control discontinuous reception (DRX) based on the notification. Specifically, the UE may be activated only for the time when the notification is made, and may transition to the DRX state if there is no change in the information transmitted on the MCCH.

In steps S13a and 13b, the UE receives the MTCH based on configuration information regarding the MTCH (MTCH configuration information) transmitted on the MCCH. The information transmitted as the MTCH configuration information may include, for example, information indicating at least one of the following.
・G-RNTI
・Cell that supports multicast transmission ・BWP that supports multicast transmission
・Multicast transmission type supported by each cell or BWP ・Control resource set (CORESET) in which PDCCH that schedules PDSCH that transmits MTCH is arranged
・Search space set used for monitoring the PDCCH ・Setting information regarding PDSCH that transmits MTCH (PDSCH setting information)

In steps S131a, 131b, the UE may monitor the search space set and detect a PDCCH (DCI) that is CRC scrambled with a specific RNTI (eg, G-RNTI). Note that the specific RNTI may be a different value for each type of multicast transmission. For example, in FIG. 3, G-RNTI_a corresponding to type a multicast transmission and G-RNTI_b corresponding to type b multicast transmission are shown.

In steps S132a and 132b, the UE may acquire MTCHs corresponding to types a and b, respectively, via the PDSCH scheduled by the DCI.

Note that steps S13a and 13b, S131a and 131b, and S132a and 132b assume different types of multicast transmission, but the operations may be the same.

≪Second scheduling≫
FIG. 4 is a diagram illustrating an example of second scheduling of multicast transmission. The second scheduling shown in FIG. 4 may be applied to groups that include at least idle/inactive UEs. The group may or may not include UEs in a connected state.

The operation in step S21 in FIG. 4 is similar to step S11 in FIG. On the other hand, the multicast system information (for example, SIB20) acquired in step S212 may include the MTCH setting information instead of the MCCH setting information. The information included in the MTCH configuration information is as described in the first scheduling.

In steps S22a and 22b, the UE receives the MTCH based on the MTCH configuration information in the system information acquired in step S21. Note that the details of steps S22a and S22b are the same as steps S13a and S13b in FIG. 3.

≪Third scheduling≫
FIG. 5 is a diagram illustrating an example of third scheduling of multicast transmission. The third scheduling shown in FIG. 5 may be applied to a group including UEs in a connected state. The group does not include idle/inactive UEs.

In step S31 of FIG. 5, the UE may receive the above MTCH configuration information via RRC signaling. Specifically, in step S311, the UE monitors a search space set that includes one or more search spaces, and selects a PDCCH (DCI) that is CRC scrambled using a UE-specific RNTI (for example, Cell (C)-RNTI). May be detected.

In step S312, the UE may acquire the MTCH configuration information via the PDSCH scheduled by the DCI. The MTCH configuration information may be included in an RRC reconfiguration message, for example. The information included in the MTCH configuration information is as described in the first scheduling.

In steps S32a and 32b, the UE receives the MTCH based on the MTCH configuration information in the system information acquired in step S31. Note that the details of steps S32a and S32b are the same as steps S13a and S13b in FIG. 3.

As described above, in NR, based on the MCCH, multicast system information, or MTCH configuration information included in the RRC message, the PDSCH is scheduled via the PDCCH (DCI) that is CRC scrambled with the G-RNTI. , MTCH (multicast data) is received.

In this case, it is also assumed that data transmitted by multicast transmission (for example, PDSCH) or data transmitted by multicast transmission and data transmitted by unicast transmission or broadcast transmission (for example, PDSCH) overlap in the time domain. However, sufficient studies have not yet been made on how to control the reception processing of the UE when data overlaps with each other or with other data due to multicast transmission.

Therefore, the present inventors focused on the fact that data transmitted through multicast transmissions, data transmitted through multicast transmissions, and data transmitted through unicast transmissions or broadcast transmissions overlap at least in the time domain. After studying the receiving operation, we arrived at the present invention.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Each of the following aspects may be applied alone or in combination. Furthermore, although the following description assumes PDSCH reception processing within the same cell, the present invention is not limited to this.

(First aspect)
In the first aspect, a process of receiving DL data (for example, PDSCH) multicast-transmitted while the UE is in an idle state (RRC_IDLE mode) or an inactive state (RRC_INACTIVE mode) will be described.

In an idle state or inactive state, a UE may receive a multicast PDSCH in addition to a broadcast PDSCH.

In such a case, it is conceivable that the PDSCHs transmitted in multicast or the PDSCH transmitted in multicast and the PDSCH transmitted in broadcast may overlap (or overlap) on the same resource. The resource may be at least one of a time domain resource and a frequency domain resource. In the following description, an example will be described in which a plurality of PDSCHs do not overlap in the frequency domain (for example, PRB) but partially or completely overlap at least in the time domain, but the present invention is not limited to this.

The UE may apply the UE operation shown in option 1 or option 2 below when the first PDSCH transmitted by multicast and the second PDSCH transmitted by multicast or broadcast overlap in the time domain. Note that in the following description, a case where two PDSCHs overlap is taken as an example, but the same may be applied to a case where three or more PDSCHs overlap.

In the following description, the first PDSCH to be multicast transmitted may be scheduled using the first type of RNTI used for terminal group-based (or multicast-based) transmission. The first type of RNTI may be a G-RNTI. That is, the first PDSCH may be read as, for example, a PDSCH scheduled using a PDCCH CRC-scrambled using G-RNTI.

Additionally, the second PDSCH that is broadcast-transmitted may be scheduled using a second type of RNTI that is used for broadcast-based transmission. The second type of RNTI may be at least one of SI-RNTI, P-RNTI, RA-RNTI, and TC-RNTI. That is, the second PDSCH may be read as a PDSCH scheduled using a PDCCH CRC-scrambled using at least one of SI-RNTI, P-RNTI, RA-RNTI, and TC-RNTI, for example. Note that when the second PDSCH is multicast transmitted, a first type RNTI having a different value from the RNTI applied to the first PDSCH may be applied.

<Option 1>
The UE controls to perform reception processing (for example, decoding processing) of the first PDSCH and the second PDSCH that overlap in the time domain (see FIGS. 6A and 6B).

In FIG. 6A, the UE controls to receive both the first PDSCH that is multicast transmitted and the second PDSCH that is broadcast transmitted.

In FIG. 6B, the UE selects a first PDSCH that is multicast transmitted (e.g., scheduled using G-RNTI ₁ ) and a second PDSCH that is multicast transmitted (e.g., scheduled using G-RNTI ₂₎ . and scheduled PDSCH). The first PDSCH and the second PDSCH may correspond to different service types (or traffic types).

The UE may be configured such that it is not required to transmit a retransmission control signal (eg, HARQ-ACK) for the first PDSCH (or second PDSCH) that is multicast transmitted. Thereby, even when performing reception processing (for example, decoding processing) for a plurality of PDSCHs, it is possible to suppress an increase in the processing load on the UE.

In option 1, the UE can receive both the first PDSCH and the second PDSCH that overlap in the time domain. Therefore, it becomes possible to eliminate restrictions on scheduling of multicast PDSCH and broadcast PDSCH, and to flexibly allocate a plurality of PDSCHs. Thereby, communication throughput can be improved.

<Option 2>
When the PDSCH scheduled using the first type of RNTI (e.g., G-RNTI) satisfies a predetermined condition, the UE schedules multiple PDSCHs that overlap in the time domain (e.g., the first PDSCH and the second PDSCH). PDSCH) (see FIG. 7A). The number of PDSCHs that can be received and processed may be defined in advance in the specifications, or may be set in the UE from the network (eg, base station).

The predetermined conditions may be conditions applied to PDSCH transmission or reception (transmission conditions, transmission parameters, or reception capabilities). For example, the UE may determine whether the first PDSCH and the second It may be determined whether to receive both PDSCHs.

For example, the predetermined conditions include the transport block size (TBS) applied to PDSCH transmission, the number of resource blocks (e.g., PRB) applied to PDSCH transmission, the processing latency allowed for PDSCH transmission, and the process capacity. (processing capability), and the presence or absence of a request for HARQ-ACK feedback.

For example, if the number of PRBs applied to the first PDSCH transmission is less than or equal to a predetermined value (e.g., 25), the UE performs reception processing (e.g., decoding processing) for both the first PDSCH and the second PDSCH. (See FIG. 7A).

On the other hand, if the number of PRBs applied to the first PDSCH transmission is larger than a predetermined value, the UE controls not to perform reception processing (for example, decoding processing) for both the first PDSCH and the second PDSCH. (See Figure 7B). In this case, the UE may be controlled to perform reception processing on either the first PDSCH or the second PDSCH (see FIGS. 8A and 8B).

In this way, when the number of PRBs to which PDSCHs are allocated is large, by receiving only one PDSCH, it is possible to suppress an increase in the reception processing load on the UE.

If a predetermined transmission condition (or reception condition) applied to the first PDSCH transmission (or reception) does not satisfy a predetermined value, the UE is configured to perform reception of a specific PDSCH based on a predetermined priority. may be controlled. The priority may be set based on at least one of the PDSCH transmission type and the PDSCH schedule timing. Alternatively, the UE may autonomously determine which PDSCH to receive (UE implementation).

For example, the priority of PDSCH transmitted by broadcast may be set higher than the priority of PDSCH transmitted by multicast. In this case, if the first PDSCH transmitted by multicast and the second PDSCH transmitted by broadcast overlap in the time domain, and the predetermined transmission condition of the first PDSCH does not satisfy the predetermined value, the UE control so as not to receive (for example, drop) the first PDSCH (see FIG. 8A).

Alternatively, the priority of PDSCH transmitted by multicast may be set higher than the priority of PDSCH transmitted by broadcast (see FIG. 8B).

Alternatively, the priority of PDSCH with early schedule timing may be set higher than the priority of PDSCH with late schedule timing (see FIG. 8A). Alternatively, the priority of a PDSCH with a late schedule timing may be set higher than the priority of a PDSCH with an early schedule timing (see FIG. 8B). The schedule timing may be determined based on the start timing of the PDSCH (see FIGS. 8A and 8B), or may be determined based on the reception timing of the PDCCH (or DCI) that schedules each PDSCH.

Furthermore, when the TBS applied to the first PDSCH transmission is less than or equal to a predetermined value, the UE performs control to perform reception processing (for example, decoding processing) for both the first PDSCH and the second PDSCH. Good too. On the other hand, if the TBS applied to the first PDSCH transmission is larger than a predetermined value, the UE performs reception processing (for example, decoding processing) on one of the first PDSCH and the second PDSCH. May be controlled. In such a case, the UE may perform control to receive a specific PDSCH based on the above-described predetermined priority.

In this way, by receiving only one PDSCH when the size of the PDSCH is large, it is possible to suppress an increase in the load on the reception processing of the UE.

Alternatively, if the process delay required for transmission and reception of the first PDSCH is equal to or greater than a predetermined value, the UE controls to perform reception processing (for example, decoding processing) for both the first PDSCH and the second PDSCH. You may. On the other hand, if the process delay required for transmission and reception of the first PDSCH is equal to or less than a predetermined value, the UE performs reception processing (for example, decoding processing) on one of the first PDSCH and the second PDSCH. It may be controlled to do so. In such a case, the UE may perform control to receive a specific PDSCH based on the above-described predetermined priority.

In this way, when the process delay allowed for PDSCH transmission and reception is short, by receiving only one PDSCH, it is possible to suppress an increase in the reception processing load on the UE.

Alternatively, if feedback of HARQ-ACK for the first PDSCH is not requested, the UE may perform control to perform reception processing (for example, decoding processing) for both the first PDSCH and the second PDSCH. On the other hand, if feedback of HARQ-ACK for the first PDSCH is requested, the UE controls to perform reception processing (for example, decoding processing) for one of the first PDSCH and the second PDSCH. You may. In such a case, the UE may perform control to receive a specific PDSCH based on the above-described predetermined priority.

In this way, when feedback of HARQ-ACK for PDSCH is requested, by receiving only one PDSCH, it is possible to suppress an increase in the load on the reception processing of the UE.

(Second aspect)
In a second aspect, a process of receiving DL data (for example, PDSCH) multicast-transmitted while the UE is in a connected state (RRC_connected mode) will be described.

In the connected state, the UE may receive a multicast PDSCH in addition to a broadcast PDSCH and a unicast PDSCH.

In such a case, the PDSCHs transmitted by multicast, the PDSCH transmitted by multicast and the PDSCH transmitted by broadcast, or the PDSCH transmitted by multicast and the PDSCH transmitted by unicast may overlap (or overlap) on the same resource. Conceivable.

The UE applies at least one of the following UE actions 1 to 3 when the first PDSCH transmitted by multicast and the second PDSCH transmitted by multicast, broadcast, or unicast overlap in the time domain. It's okay. Furthermore, if the first PDSCH transmitted by multicast, the second PDSCH transmitted by broadcast, and the third PDSCH transmitted by unicast overlap in the time domain, the UE applies UE operation 4 below. It's okay.

In the following description, the unicast transmitted PDSCH may be scheduled using the third type of RNTI used for UE-specific (or unicast-based) transmission. The third type of RNTI may be at least one of C-RNTI, MCS-C-RNTI, and CS-RNTI. That is, the third PDSCH may be read as a PDSCH scheduled using a PDCCH CRC scrambled with at least one of C-RNTI, MCS-C-RNTI, and CS-RNTI, for example.

<UE operation 1: Multicast PDSCH + Broadcast PDSCH>
If the first PDSCH transmitted by multicast and the second PDSCH transmitted by broadcast overlap in the time domain (see FIG. 6A), the UE transmits both the first PDSCH and the second PDSCH based on predetermined conditions. It may be determined whether or not to perform reception processing (for example, decoding processing) on the received information.

The second PDSCH transmitted by broadcast may be a PDSCH scheduled using SI-RNTI during a process of P-RNTI triggered SI acquisition. good.

For example, in the connected state, the UE receives a system information change notification via a PDCCH to which P-RNTI is applied (or a PDSCH scheduled on the PDCCH). In this case, assuming that the system information has been changed, the UE acquires the changed system information notified on the PDSCH scheduled on the SI-RNTI (eg, CRC-scrambled PDCCH on the SI-RNTI).

The predetermined condition may be a predetermined process time required for the first PDSCH scheduled using the G-RNTI. The predetermined process time may be referred to as a process time for UE capability 2, or Capability 2 processing time. Alternatively, the predetermined condition may be another condition.

The process time of a PDSCH may be a period from the end of the last symbol of the PDSCH transmitting a transport block to an uplink (UL) symbol. The UE may provide valid delivery confirmation information (eg, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)) in the same or subsequent symbols as the UL symbol.

The process time may be classified into two types: processing time for UE capability 1 and processing time for UE capability 2. The processing time for UE capability 2 is shorter than the processing time for UE capability 1.

The UE uses different UE capability information (for example, RRC parameter "pdsch-ProcessingType2" for the former and RRC parameter "pusch-ProcessingType2" for the latter) to determine whether it supports UE capability 2 for each of the PDSCH and PUSCH. , base station).

The network (eg, base station) may determine whether the UE performs processing based on UE capability 2 based on the UE capability information. The base station provides information indicating that UE capability 2 is applied (enabled) for each of PDSCH and PUSCH (for example, the former is the parameter "processingType2Enabled" included in the RRC information element "PDSCH-ServingCellConfig", and the latter is the RRC information The parameter "processingType2Enabled" included in the element "PUSCH-ServingCellConfig" may be set in the UE using upper layer signaling.

For example, if the first PDSCH to be multicast transmitted and the second PDSCH to be broadcasted overlap in the time domain, the UE may require processing time for UE capability 2 for the first PDSCH. Control may be performed to perform reception processing (for example, decoding processing) of the first PDSCH and the second PDSCH.

On the other hand, if a process time for UE capability 2 is required for the first PDSCH, reception processing (for example, decoding processing) is performed on one of the first PDSCH and the second PDSCH. May be controlled.

In such a case, the UE may perform control to receive a specific PDSCH based on priorities set to the first PDSCH and the second PDSCH. Note that the settings described in the first aspect may be applied to the priority settings. Alternatively, the UE may autonomously determine which PDSCH to receive (UE implementation).

In this way, by receiving both the multicast PDSCH and the broadcast PDSCH when the PDSCH process time required of the UE is equal to or greater than a predetermined value, it becomes possible to perform scheduling flexibly and improve throughput.

<UE operation 2: Multicast PDSCH + Multicast PDSCH>
When the first PDSCH transmitted by multicast and the second PDSCH transmitted by multicast overlap in the time domain (see FIG. 6B), the UE transmits both the first PDSCH and the second PDSCH based on predetermined conditions. It may be determined whether or not to perform reception processing (for example, decoding processing) on the received information. Here, a case is shown in which there are two multicast PDSCHs that overlap in the time domain, but the present invention can be similarly applied to a case where three or more multicast PDSCHs overlap in the time domain.

The first PDSCH and the second PDSCH may each be PDSCHs scheduled using the same type of RNTI (eg, G-RNTI). Further, the first PDSCH and the second PDSCH may correspond to different service types (or traffic types), and the applied G-RNTI values may be different.

If at least one of the first PDSCH and the second PDSCH, or both the first PDSCH and the second PDSCH satisfy a predetermined condition, the UE performs reception processing on both the first PDSCH and the second PDSCH. It may also be controlled to perform.

The predetermined conditions may be conditions applied to PDSCH transmission or reception (transmission conditions, transmission parameters, or reception capabilities). The UE transmits the first PDSCH and It may be determined whether to receive both of the second PDSCHs.

The predetermined conditions include the transport block size (TBS) applied to PDSCH transmission, the number of resource blocks (e.g., PRB) applied to PDSCH transmission, the processing latency allowed for PDSCH transmission, and the processing capacity (processing capacity). capability), and the presence or absence of a request for HARQ-ACK feedback.

For example, if the number of PRBs applied to multicast PDSCH transmission (at least one of the first PDSCH transmission and the second PDSCH transmission) is less than or equal to a predetermined value (for example, 25), the UE Control may be performed to perform reception processing for both PDSCHs. On the other hand, if the number of PRBs applied to multicast PDSCH transmission is larger than a predetermined value, the UE may perform control to perform reception processing on one of the first PDSCH and the second PDSCH. Alternatively, the UE may determine that it is an error case.

Alternatively, the UE may perform control to perform reception processing for both the first PDSCH and the second PDSCH when the TBS applied to multicast PDSCH transmission is less than or equal to a predetermined value. On the other hand, if the TBS applied to multicast PDSCH transmission is larger than a predetermined value, the UE may perform control to perform reception processing on one of the first PDSCH and the second PDSCH.

Alternatively, if the process delay required for multicast PDSCH reception is equal to or greater than a predetermined value, the UE may perform control to perform reception processing for both the first PDSCH and the second PDSCH. On the other hand, if the process delay required for multicast PDSCH reception is equal to or less than a predetermined value, the UE may perform control to perform reception processing on one of the first PDSCH and the second PDSCH.

Alternatively, if feedback of HARQ-ACK for multicast PDSCH is not required, the UE may perform control to perform reception processing for both the first PDSCH and the second PDSCH. On the other hand, when feedback of HARQ-ACK for the multicast PDSCH is requested, the UE may perform control to perform reception processing on one of the first PDSCH and the second PDSCH. Alternatively, the UE may determine that it is an error case.

When performing reception processing on either the first PDSCH or the second PDSCH, the UE performs control to receive a specific PDSCH based on the priorities set for the first PDSCH and the second PDSCH. It's okay. Note that the settings described in the first aspect may be applied to the priority settings. Alternatively, the UE may autonomously determine which PDSCH to receive (UE implementation).

For example, the UE may drop one of the multicast PDSCHs that are set to have a low priority. Alternatively, the UE may drop a PDSCH with an early schedule timing (or a PDSCH with a late schedule timing).

<UE operation 3: Multicast PDSCH + Unicast PDSCH>
When the first PDSCH transmitted by multicast and the second PDSCH transmitted by unicast overlap in the time domain (see FIG. 9A), the UE determines whether the first PDSCH and the second PDSCH are divided based on predetermined conditions. It may be determined whether or not to perform reception processing (for example, decoding processing) for both. Here, the case where there is one multicast PDSCH and one unicast PDSCH that overlap in the time domain is shown, but the same applies when two or more multicast PDSCHs or two or more unicast PDSCHs overlap in the time domain. Applicable.

The first PDSCH may be a PDSCH scheduled with a first type of RNTI (eg, G-RNTI). The second PDSCH may be a PDSCH scheduled using a third type of RNTI (eg, at least one of C-RNTI, MCS-C-RNTI, and CS-RNTI).

When one of the first PDSCH and the second PDSCH, or both the first PDSCH and the second PDSCH satisfy a predetermined condition, the UE performs reception processing on both the first PDSCH and the second PDSCH. It may be controlled to do so.

The predetermined conditions may be conditions (transmission conditions or transmission parameters) applied to PDSCH transmission or reception. The UE transmits both the first PDSCH and the second PDSCH based on at least one of predetermined transmission conditions applied to the first PDSCH transmission and predetermined transmission conditions applied to the second PDSCH transmission. You may decide whether or not to receive it.

For example, the predetermined conditions include the transport block size (TBS) applied to PDSCH transmission, the number of resource blocks (e.g., PRB) applied to PDSCH transmission, the processing latency allowed for PDSCH transmission, and the process capacity. (processing capability), and the presence or absence of a request for HARQ-ACK feedback.

For example, if the number of PRBs applied to at least one (for example, both) of the first PDSCH transmission and the second PDSCH transmission is equal to or less than a predetermined value, the UE transmits both the first PDSCH and the second PDSCH. It may also be controlled to perform reception processing. On the other hand, if the number of PRBs applied to at least one of the first PDSCH transmission and the second PDSCH transmission is larger than a predetermined value, the UE receives reception for one of the first PDSCH and the second PDSCH. It may also be controlled to perform processing. Alternatively, the UE may determine that it is an error case.

Alternatively, if the TBS applied to at least one (e.g., both) of the first PDSCH transmission and the second PDSCH transmission is less than or equal to a predetermined value, the UE It may also be controlled to perform reception processing. On the other hand, if the TBS applied to at least one of the first PDSCH transmission and the second PDSCH transmission is larger than a predetermined value, the UE performs reception processing on one of the first PDSCH and the second PDSCH. It may also be controlled to perform. Alternatively, the UE may determine that it is an error case.

Alternatively, if the process delay required for at least one (for example, both) of the first PDSCH transmission/reception and the second PDSCH transmission/reception is a predetermined value or more, the UE transmits both the first PDSCH and the second PDSCH. It may also be controlled to perform reception processing. On the other hand, when the process delay required for at least one of the first PDSCH transmission/reception and the second PDSCH transmission/reception is equal to or less than a predetermined value, the UE It may also be controlled to perform reception processing. Alternatively, the UE may determine that it is an error case.

Alternatively, the UE performs reception processing for both the first PDSCH and the second PDSCH if feedback of HARQ-ACK for at least one (e.g., both) of the first PDSCH and the second PDSCH is not required. It may be controlled as follows. On the other hand, if feedback of HARQ-ACK for at least one of the first PDSCH and the second PDSCH is requested, the UE performs reception processing for one of the first PDSCH and the second PDSCH. It may be controlled as follows. Alternatively, the UE may determine that it is an error case.

When performing reception processing on either the first PDSCH or the second PDSCH, the UE performs control to receive a specific PDSCH based on the priorities set for the first PDSCH and the second PDSCH. It's okay. Note that the settings described in the first aspect may be applied to the priority settings. Alternatively, the UE may autonomously determine which PDSCH to receive (UE implementation).

For example, the UE may drop either the multicast PDSCH or the unicast PDSCH that is set to have a low priority. Alternatively, the UE may drop a PDSCH with an early schedule timing (or a PDSCH with a late schedule timing).

<UE operation 4: Multicast PDSCH + Broadcast PDSCH + Unicast PDSCH>
When the first PDSCH transmitted in multicast, the second PDSCH transmitted in broadcast, and the third PDSCH transmitted in unicast overlap in the time domain (see FIG. 9B), the UE It may be determined which of the first PDSCH, second PDSCH, and third PDSCH should be subjected to reception processing (for example, decoding processing). Here, a case is shown in which there is one multicast PDSCH, one broadcast PDSCH, and one unicast PDSCH that overlap in the time domain, but it also applies when two or more multicast PDSCH, broadcast PDSCH, or unicast PDSCH overlap in the time domain. The same applies.

The first PDSCH may be a PDSCH scheduled with a first type of RNTI (eg, G-RNTI). The second PDSCH may also be a PDSCH scheduled using the SI-RNTI during a process of P-RNTI triggered SI acquisition. Additionally, the third PDSCH may be a PDSCH scheduled using a third type of RNTI (eg, at least one of C-RNTI, MCS-C-RNTI, and CS-RNTI).

If one of the first PDSCH and the third PDSCH, or both the first PDSCH and the third PDSCH satisfy a predetermined condition, the UE Control may be performed so that all reception processing is performed.

The predetermined conditions may be conditions (transmission conditions or transmission parameters) applied to PDSCH transmission or reception. The UE transmits the first PDSCH, the second PDSCH and the third PDSCH based on at least one of predetermined transmission conditions applied to the first PDSCH transmission and predetermined transmission conditions applied to the third PDSCH transmission. It may be determined whether to receive all or some of the three PDSCHs.

For example, the predetermined conditions may include the transport block size (TBS) applied to a given PDSCH transmission, the number of resource blocks (e.g., PRBs) applied to a PDSCH transmission, the processing latency allowed for a PDSCH transmission, It may be at least one of processing capability and the presence or absence of a request for HARQ-ACK feedback.

For example, if the number of PRBs applied to at least one (for example, both) of the first PDSCH transmission and the third PDSCH transmission is equal to or less than a predetermined value, the UE Control may be performed to perform all reception processing for PDSCH 3. On the other hand, if the number of PRBs applied to at least one of the first PDSCH transmission and the third PDSCH transmission is larger than a predetermined value, the UE , one or two PDSCHs may be controlled to perform reception processing. Alternatively, the UE may determine that it is an error case.

Alternatively, if the TBS applied to at least one (for example, both) of the first PDSCH transmission and the third PDSCH transmission is less than or equal to a predetermined value, the UE transmits the first PDSCH, the second PDSCH and the third PDSCH. control may be performed to perform all reception processing of PDSCHs. On the other hand, if the TBS applied to at least one of the first PDSCH transmission and the third PDSCH transmission is larger than a predetermined value, the UE may Control may be performed to perform reception processing on one or two PDSCHs. Alternatively, the UE may determine that it is an error case.

Alternatively, if the process delay required for at least one (for example, both) of the first PDSCH transmission/reception and the third PDSCH transmission/reception is a predetermined value or more, the UE Control may be performed to perform all reception processing for PDSCH 3. On the other hand, if the process delay required for at least one of the first PDSCH transmission/reception and the second PDSCH transmission/reception is equal to or less than a predetermined value, the UE transmits the first PDSCH, the second PDSCH, and the third PDSCH. Control may be performed to perform reception processing on one or two of the PDSCHs. Alternatively, the UE may determine that it is an error case.

Alternatively, the UE may detect all of the first PDSCH, the second PDSCH, and the third PDSCH if feedback of HARQ-ACK for at least one (e.g., both) of the first PDSCH and the third PDSCH is not required. It may also be controlled to perform reception processing. On the other hand, if feedback of HARQ-ACK for at least one of the first PDSCH and the third PDSCH is requested, the UE selects one of the first PDSCH, the second PDSCH, and the third PDSCH. Alternatively, control may be performed to perform reception processing on two PDSCHs. Alternatively, the UE may determine that it is an error case.

When performing reception processing on one or two of the first PDSCH, second PDSCH, and third PDSCH, the UE is configured to use the first PDSCH, second PDSCH, and third PDSCH. The reception of a specific PDSCH may be controlled based on the priority of the PDSCH. Note that the priority may be set based on at least one of the PDSCH transmission type and the PDSCH schedule timing. Alternatively, the UE may autonomously determine which PDSCH to receive (UE implementation).

For example, the UE may drop at least one of multicast PDSCH, unicast PDSCH and broadcast PDSCH. The reception priority may be unicast PDSCH>multicast PDSCH>broadcast PDSCH, but is not limited to this. Alternatively, the UE may drop one or two PDSCHs with early schedule timing (or one or two PDSCHs with late schedule timing).

<Variations>
The first aspect or the second aspect may be applied regardless of the frequency range, or may be applied in a predetermined frequency band. The predetermined frequency range may be FR1.

In this case, when the first PDSCH and the second PDSCH overlap at least in the time domain of the same cell in another frequency domain (for example, FR2), the UE performs reception processing (for example, decoding) for the first PDSCH. It may also be possible to control the process so that it does not occur.

The first PDSCH may be a multicast transmitted PDSCH scheduled with a first type of RNTI (eg, G-RNTI). The second PDSCH is a broadcast-transmitted PDSCH that is scheduled using a second type of RNTI (for example, at least one of SI-RNTI, P-RNTI, RA-RNTI, and TC-RNTI). There may be. Note that the second PDSCH that is broadcast-transmitted is a PDSCH scheduled using SI-RNTI during a process of P-RNTI triggered SI acquisition. It's okay.

Alternatively, the first PDSCH is a multicast transmitted PDSCH scheduled with a first type of RNTI (e.g. G-RNTI) and the second PDSCH is a multicast transmitted PDSCH scheduled with a first type of RNTI (e.g. The PDSCH may be unicast-transmitted and scheduled using at least one of C-RNTI, MCS-C-RNTI, and CS-RNTI).

Alternatively, the first PDSCH and the second PDSCH may be multicast transmitted PDSCHs scheduled with a first type of RNTI (eg, G-RNTI).

The UE may also assume that in other frequency domains (eg, FR2), the first PDSCH and the second PDSCH with different RNTI types are not overlapped in the same cell at least in the time domain.

Additionally, HARQ-ACK for the dropped PDSCH in this disclosure may or may not be transmitted (eg, as a NACK).

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

FIG. 10 is a diagram illustrating 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 the Third Generation Partnership Project (3GPP). .

Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC has 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)).

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

The wireless communication system 1 has dual connectivity between multiple base stations within the same RAT (for example, NR-NR Dual Connectivity (NN-DC) where both the 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 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macro cell C1 and form a small cell C2 that is narrower than the macro cell C1. You may prepare. User terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as 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 utilize at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

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)). Macro cell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and FR1 may correspond to a higher frequency band than FR2, for example.

Further, the user terminal 20 may communicate 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, base station 11, which is an upper-level station, is an Integrated Access Backhaul (IAB) donor, and base station 12, which is a relay station, is an IAB donor. May also be called a node.

Base station 10 may be connected to core network 30 via other base stations 10 or directly. The core network 30 may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

The user terminal 20 may be a terminal compatible with at least one of communication systems such as LTE, LTE-A, and 5G.

In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used. For example, in at least one of the downlink (DL) and 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.

A wireless access scheme may be referred to as a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single carrier transmission methods, other multicarrier transmission methods) may be used as the UL and DL radio access methods.

In the wireless communication system 1, downlink channels include a physical downlink shared channel (PDSCH) shared by each user terminal 20, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical downlink control channel). Channel (PDCCH)) or the like may be used.

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

User data, upper layer control information, System Information Block (SIB), etc. are transmitted through the PDSCH. User data, upper layer control information, etc. may be transmitted by PUSCH. Furthermore, a Master Information Block (MIB) may be transmitted via the PBCH.

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

Note that 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. Note that PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

A control resource set (CORESET) and a search space may be used to detect the PDCCH. CORESET corresponds to a resource for searching DCI. The search space corresponds to a search area and a search method for PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

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. Note that "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read interchangeably.

PUCCH allows channel state information (CSI), delivery confirmation information (for example, may be called Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and scheduling request ( Uplink Control Information (UCI) including at least one of SR)) may be transmitted. A random access preamble for establishing a connection with a cell may be transmitted by PRACH.

Note that in the present disclosure, downlinks, uplinks, etc. may be expressed without adding "link". Furthermore, various channels may be expressed without adding "Physical" at the beginning.

In the wireless communication system 1, a synchronization signal (SS), a 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 (CRS), a channel state information reference signal (CSI-RS), and a demodulation reference signal (DeModulation). Reference Signal (DMRS)), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc. may be transmitted.

The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

In addition, in the wireless communication system 1, measurement reference signals (Sounding Reference Signal (SRS)), demodulation reference signals (DMRS), etc. are transmitted as uplink reference signals (UL-RS). good. Note that DMRS may be called a user terminal-specific reference signal (UE-specific reference signal).

(base station)
FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. The base station 10 includes a control section 110, a transmitting/receiving section 120, a transmitting/receiving antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided.

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

The control unit 110 controls the base station 10 as a whole. The control unit 110 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.

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

The transmitting/receiving section 120 may include a baseband section 121, a radio frequency (RF) section 122, and a measuring section 123. The baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212. The transmitting/receiving unit 120 includes a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common understanding in the technical field related to the present disclosure. be able to.

The transmitter/receiver 120 may be configured as an integrated transmitter/receiver, or may be configured from a transmitter and a receiver. The transmitting section may include a transmitting processing section 1211 and an RF section 122. The reception section may include a reception processing section 1212, an RF section 122, and a measurement section 123.

The transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitter/receiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 120 may form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmitting/receiving unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, on the data, control information, etc. acquired from the 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 transmitting/receiving unit 120 (transmission processing unit 1211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, and discrete Fourier transform (DFT) on the bit string to be transmitted. A baseband signal may be output after performing transmission processing such as processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion.

The transmitting/receiving unit 120 (RF unit 122) may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 130. .

On the other hand, the transmitting/receiving section 120 (RF section 122) may perform amplification, filter processing, demodulation into a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.

The transmitting/receiving unit 120 (reception processing unit 1212) performs analog-to-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) processing (if necessary), applying reception processing such as filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing, User data etc. may also be acquired.

The transmitting/receiving unit 120 (measuring unit 123) may perform measurements regarding the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. The measurement unit 123 measures reception power (for example, Reference Signal Received Power (RSRP)), 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), etc. may be measured. The measurement results may be output to the control unit 110.

The transmission path interface 140 transmits and receives signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and transmits and receives user data (user plane data) for the user terminal 20, control plane It is also possible to acquire and transmit data.

Note that the transmitting unit and receiving unit of the base station 10 in the present disclosure may be configured by at least one of the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140.

Note that the transmitter/receiver 120 uses a first downlink shared channel that is scheduled using a first type of RNTI used for terminal group-based transmission, and a first downlink shared channel that is scheduled using a second type of RNTI that is used for broadcast transmission. and a third downlink shared channel scheduled using a third RNTI used for terminal-specific transmission. do.

The control unit 110 uses a first downlink shared channel scheduled using a first type RNTI, a second downlink shared channel scheduled using a second type RNTI, and a third type RNTI. Scheduling may be controlled such that at least two of the third downlink shared channels scheduled using the scheduled third RNTI overlap in the time domain.

(user terminal)
FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control section 210, a transmitting/receiving section 220, and a transmitting/receiving antenna 230. Note that one or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.

Note that this example mainly shows functional blocks that are characteristic of 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 unit described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.

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

The transmitting/receiving section 220 may include a baseband section 221, an RF section 222, and a measuring section 223. The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212. The transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field related to the present disclosure.

The transmitting/receiving section 220 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmitting section may include a transmitting processing section 2211 and an RF section 222. The reception section may include a reception processing section 2212, an RF section 222, and a measurement section 223.

The transmitting/receiving antenna 230 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitter/receiver 220 may receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transmitter/receiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 220 may form at least one of a transmitting beam and a receiving beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

The transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (e.g. RLC retransmission control), MAC layer processing (e.g. , HARQ retransmission control), etc., to generate a bit string to be transmitted.

The transmitting/receiving unit 220 (transmission processing unit 2211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, DFT processing (as necessary), and IFFT processing on the bit string to be transmitted. , precoding, digital-to-analog conversion, etc., and output a baseband signal.

Note that whether or not to apply DFT processing may be based on the settings of transform precoding. When transform precoding is enabled for a certain channel (for example, PUSCH), the transmitting/receiving unit 220 (transmission processing unit 2211) performs the above processing in order to transmit the channel using the DFT-s-OFDM waveform. DFT processing may be performed as the transmission processing, or if not, DFT processing may not be performed as the transmission processing.

The transmitting/receiving unit 220 (RF unit 222) may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 230. .

On the other hand, the transmitting/receiving section 220 (RF section 222) may perform amplification, filter processing, demodulation into a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 230.

The transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filter processing, demapping, demodulation, and decoding (error correction) on the acquired baseband signal. (which may include decoding), MAC layer processing, RLC layer processing, and PDCP layer processing may be applied to obtain user data and the like.

The transmitting/receiving section 220 (measuring section 223) may perform measurements regarding the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement 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 results may be output to the control unit 210.

Note that the transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting/receiving unit 220, the transmitting/receiving antenna 230, and the transmission path interface 240.

Note that the transmitter/receiver 220 uses a first downlink shared channel that is scheduled using a first type of RNTI used for terminal group-based transmission, and a first downlink shared channel that is scheduled using a second type of RNTI that is used for broadcast transmission. and a third downlink shared channel scheduled using a third RNTI used for terminal-specific transmission. do.

The control unit 210 controls a first downlink shared channel scheduled using the first type of RNTI used for terminal group-based transmission, and a first downlink shared channel scheduled using the first type or another type of RNTI. When two downlink shared channels overlap in the time domain, a downlink shared channel to be received is determined based on a predetermined condition.

The control unit 210 may determine whether to receive both the first downlink shared channel and the second downlink shared channel based on conditions applied to the transmission of the first downlink shared channel.

When the other type of RNTI is a second type of RNTI used for broadcast-based transmission, the control unit 210 controls the first downlink shared channel and the second type of RNTI based on the process time required for the first downlink shared channel. It may also be determined whether to receive both of the second downlink shared channels.

When the other type of RNTI is a third type of RNTI used for terminal-specific transmission, the control unit 210 controls the conditions applied to the transmission of the first downlink shared channel and the conditions applied to the second downlink shared channel. It may be determined whether to receive both the first downlink shared channel and the second downlink shared channel based on at least one condition applied to transmission.

The control unit 210 may control so as not to perform reception processing on the first downlink shared channel when the first downlink shared channel and the second downlink shared channel overlap in the time domain in a predetermined frequency range. .

(Hardware configuration)
It should be noted that the block diagram used to explain the above embodiment shows blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Here, functions include judgment, decision, judgement, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and consideration. , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (configuration unit) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The base station 10 and 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, etc. .

Note that in the present disclosure, words such as apparatus, circuit, device, section, unit, etc. can be read interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device 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 multiple processors. Also, the processing may be performed by one processor, or the processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Note that the processor 1001 may be implemented using one or more chips.

Each function in the base station 10 and the user terminal 20 is performed by, for example, loading predetermined software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and communicates via the communication device 1004. This is achieved by controlling at least one of reading and writing data in the memory 1002 and storage 1003.

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

Furthermore, the processor 1001 reads programs (program codes), software modules, data, and the like from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may also be realized in the same way.

Memory 1002 is a computer-readable storage medium, such as at least Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. It may be composed of one. Memory 1002 may be called a register, cache, main memory, or the like. The memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, such as a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (CD-ROM), etc.), a digital versatile disk, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium. It may be configured by Storage 1003 may also be called 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. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be configured to include. For example, the above-described transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004. The transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts 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 performs output to the outside. Note that 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 a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each device.

The base station 10 and the user terminal 20 also include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured to include hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

(Modified example)
Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal may be interchanged. Also, the signal may be a message. The reference signal may also be abbreviated as RS, and may be called a pilot, pilot signal, etc. depending on the applicable standard. Further, a component carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, or the like.

A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

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

A slot may be constituted by one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Furthermore, a slot may be a time unit based on numerology.

A slot may include multiple minislots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units for transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.

For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or minislot may be called a TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

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

The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI that is shorter than a normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, or the like.

Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.

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

Additionally, an RB may include one or more symbols in the time domain and may be one slot, one minislot, one subframe, or one TTI long. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

Note that one or more RBs include a physical resource block (Physical RB (PRB)), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, and an RB. They may also be called pairs.

Further, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (also called partial bandwidth, etc.) refers to a subset of contiguous common resource blocks (RBs) for a certain numerology in a certain carrier. Good too. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

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

At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

Note that the structures of the radio frame, subframe, slot, minislot, symbol, etc. described above are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, The number of subcarriers, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

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

The names used for parameters and the like in this disclosure are not limiting in any respect. Furthermore, the mathematical formulas etc. 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 designation, the various names assigned to these various channels and information elements are not in any way exclusive designations. .

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

Further, information, signals, etc. may be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layer. Information, signals, etc. may be input and output via multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (eg, memory) or may be managed using a management table. Information, signals, etc. that are input and output 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.

Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the information notification in this disclosure may be performed using physical layer signaling (e.g., Downlink Control Information (DCI), uplink control information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof. It may be carried out by

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

Further, notification of prescribed information (for example, notification of "X") is not limited to explicit notification, but may be made implicitly (for example, by not notifying the prescribed information or by providing other information) (by notification).

The determination may be made by a value expressed by 1 bit (0 or 1), or by a boolean value expressed by true or false. , may be performed by numerical comparison (for example, comparison with a predetermined value).

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

Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (such as infrared, microwave) to , a server, or other remote source, these wired and/or wireless technologies are included within the definition of a transmission medium.

As used in this disclosure, the terms "system" and "network" may be used interchangeably. "Network" may refer to devices (eg, base stations) included in the network.

In this disclosure, "precoding", "precoder", "weight (precoding weight)", "quasi-co-location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial "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", and "panel" are interchangeable. can be used.

In this disclosure, "Base Station (BS)", "Wireless base station", "Fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel" , "cell," "sector," "cell group," "carrier," "component carrier," and the like may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is divided into base station subsystems (e.g., small indoor base stations (Remote Radio Communication services can also be provided by the Head (RRH)). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides 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.

A mobile station is a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal. , handset, user agent, mobile client, client, or some other suitable terminology.

At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like. Note that at least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving object may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving object (for example, a drone, a self-driving car, etc.), or a robot (manned or unmanned). ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. 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.

Furthermore, the base station in the present disclosure may be replaced by a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions that the base station 10 described above has. Further, words such as "upstream" and "downstream" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be replaced with side channels.

Similarly, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station 10 may have the functions that the user terminal 20 described above has.

In this disclosure, the operations performed by the base station may be performed by its 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 may be performed by the base station, one or more network nodes other than the base station (e.g. It is clear that this can be done by a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc. (but not limited to these) or a combination thereof.

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

Each aspect/embodiment described in this disclosure is applicable to 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)), IEEE 802. 20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods, and next-generation systems expanded based on these may be applied. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may be applied.

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

As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.

As used in this disclosure, the term "determining" may encompass a wide variety of actions. For example, "judgment" can mean judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry ( For example, searching in a table, database, or other data structure), ascertaining, etc. may be considered to be "determining."

In addition, "judgment (decision)" includes receiving (e.g., receiving information), transmitting (e.g., sending information), input (input), output (output), access ( may be considered to be "determining", such as accessing data in memory (eg, accessing data in memory).

In addition, "judgment" is considered to mean "judging" resolving, selecting, choosing, establishing, comparing, etc. Good too. In other words, "judgment (decision)" may be considered to be "judgment (decision)" of some action.

Further, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

"Maximum transmit power" as described in this disclosure may mean the maximum value of transmit power, the nominal maximum transmit power (the UE maximum transmit power), or the rated maximum transmit power (the UE maximum transmit power). rated UE maximum transmit power).

As used in this disclosure, the terms "connected", "coupled", or any variations thereof refer to any connection or coupling, direct or indirect, between two or more elements. can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access."

In this disclosure, when two elements are connected, they may be connected using one or more electrical wires, cables, printed electrical connections, etc., as well as in the radio frequency domain, microwave can be considered to be "connected" or "coupled" to each other using electromagnetic energy having wavelengths in the light (both visible and invisible) range.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."

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

In this disclosure, when articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are plural.

Although the invention according to the present disclosure has been described in detail above, it is clear for 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 modifications and variations without departing from the spirit and scope of the invention as determined based on the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and does not have any limiting meaning on the invention according to the present disclosure.

Claims (6)

A terminal,
A first downlink shared channel scheduled using a first type of RNTI (Radio Network Temporary Identifier) for multicast , a second downlink shared channel scheduled using another type of RNTI , a receiving unit that receives at least one of the following ;
a control unit that controls reception of at least one of the first downlink shared channel and the second downlink shared channel ,
When the other type of RNTI is a unicast RNTI, the control unit controls whether the first downlink shared channel and the second downlink shared channel overlap in the time domain based on the capabilities of the terminal. A terminal characterized in that it is controlled to perform decoding on both channels . The terminal according to claim 1, wherein the control unit controls the first downlink shared channel not to be decoded when the other type of RNTI is an RA-RNTI . When the first downlink shared channel is multicast transmitted and the second downlink shared channel is broadcast transmitted , the control unit transmits the first downlink shared channel and the second downlink shared channel. The terminal according to claim 1, wherein the terminal is controlled so as not to simultaneously receive downlink shared channels. When the first downlink shared channel is multicast transmitted and the second downlink shared channel is multicast transmitted , the control unit transmits the first downlink shared channel and the second downlink shared channel. 2. The terminal according to claim 1, wherein the terminal is controlled not to perform simultaneous reception of the terminal. A wireless communication method for a terminal,
A first downlink shared channel scheduled using a first type of RNTI (Radio Network Temporary Identifier) for multicast , a second downlink shared channel scheduled using another type of RNTI , receiving at least one of the following;
controlling reception of at least one of the first downlink shared channel and the second downlink shared channel ,
When the other type of RNTI is a unicast RNTI, decoding both the first downlink shared channel and the second downlink shared channel that overlap in the time domain based on the capabilities of the terminal. A wireless communication method characterized by controlling to perform . A system including a terminal and a base station,
The terminal is
A first downlink shared channel scheduled using a first type of RNTI (Radio Network Temporary Identifier) for multicast, a second downlink shared channel scheduled using another type of RNTI, a receiving unit that receives at least one of the following;
a control unit that controls reception of at least one of the first downlink shared channel and the second downlink shared channel,
When the other type of RNTI is a unicast RNTI, the control unit controls whether the first downlink shared channel and the second downlink shared channel overlap in the time domain based on the capabilities of the terminal. control to do both decoding of the channel,
The base station is
A system comprising: a transmitter that transmits the first downlink shared channel and the second downlink shared channel.

Images