Terminal, wireless communication method, base station, and system

By using RNTI scrambled CRC bits in the new wireless communication system, the control problem of multicast transmission and reception in NR is solved, and efficient reception of multicast data is achieved.

CN114270981BActive Publication Date: 2025-07-04NTT DOCOMO INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN201980099514.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-06-21
Publication Date
2025-07-04
Estimated Expiration
2039-06-21

AI Technical Summary

Technical Problem

In wireless communication systems, how to appropriately control the reception of multicast transmission using physical downlink shared channels, especially in new wireless communication systems (NRs), there is a lack of effective control methods in the prior art.

Method used

The terminal device receives downlink control information using cyclic redundancy check (CRC) bits common to more than one terminals through the receiving unit, and schedules a physical downlink shared channel within more than one bandwidth portion of the cell to receive multicast traffic channel (MTCH) data.

Benefits of technology

Appropriate control of multicast transmission and reception of physical downlink shared channels is realized, and the efficiency and flexibility of multicast data reception are improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114270981B_ABST
    Figure CN114270981B_ABST
Patent Text Reader

Abstract

The terminal includes: a receiving unit that receives downlink control information in which cyclic redundancy check (CRC) bits are scrambled using a radio network temporary identifier (RNTI) common to one or more terminals; and a control unit that controls reception of data associated with a multicast traffic channel (MTCH) using a physical downlink shared channel scheduled by the downlink control information within one or more bandwidth parts in a cell. Accordingly, reception of multicast transmission using the physical downlink shared channel can be appropriately controlled.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a terminal, a wireless communication method, a base station, and a system in a next-generation mobile communication system. Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized for the purpose of further high-speed data rates, low latency, etc. (Non-Patent Document 1). In addition, for the purpose of further large capacity and high performance of LTE (3rd Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) has been standardized.

[0003] Subsequent systems of LTE are also being studied (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), New Radio (NR), 3GPP Rel. 15 and later, etc.)

[0004] Prior Art Documents

[0005] Non-Patent Documents

[0006] Non-Patent Document 1: 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 Summary of the Invention

[0007] Problems to be Solved by the Invention

[0008] In a future wireless communication system (hereinafter also referred to as NR), research is being conducted on multicast transmission (also referred to as, for example, Multicast Traffic Channel (MTCH) of a logical channel, multicast data, etc.) using the Physical Downlink Shared Channel (e.g., Physical Downlink Shared Channel (PDSCH)). Specifically, research is being conducted on mapping MTCH to the Downlink Shared Channel (e.g., Downlink Shared Channel (DL-SCH)) as a transport channel, and mapping DL-SCH to PDSCH.

[0009] However, in the existing LTE system, multicast transmission is performed using the Physical Multicast Channel (PMCH). Therefore, in NR, how a terminal controls the reception of multicast transmission using the Physical Downlink Shared Channel becomes a problem.

[0010] Therefore, one of the objects of the present inventors is to provide a terminal and a wireless communication method capable of appropriately controlling the reception of multicast transmission using the Physical Downlink Shared Channel.

[0011] Means for Solving the Problem

[0012] A terminal according to one aspect of the present disclosure is characterized by having: a receiving unit that receives downlink control information in which cyclic redundancy check (CRC) bits are scrambled using a radio network temporary identifier (RNTI) common to one or more terminals; and a control unit that controls reception of data associated with a multicast traffic channel (MTCH) using a Physical Downlink Shared Channel scheduled by the downlink control information within one or more bandwidth parts in a cell.

[0013] Advantageous Effects of the Invention

[0014] According to one aspect of the present disclosure, it is possible to appropriately control the reception of multicast transmission using the Physical Downlink Shared Channel. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a diagram showing an example of multicast transmission in a single cell according to the first aspect.

[0016] Figure 2 is a diagram showing an example of multicast transmission in a plurality of cells according to the first aspect.

[0017] Figure 3 is a diagram showing an example of a first scheduling of multicast transmission according to the second aspect.

[0018] Figure 4This is a diagram showing an example of the second scheduling for multicast transmission according to the second method.

[0019] Figure 5 This is a diagram showing an example of the third scheduling for multicast transmission according to the second method.

[0020] Figure 6 This is a diagram showing an example of beam control related to multicast transmission according to the third method.

[0021] Figure 7A And FIGS. 7B is a diagram showing an example of PDCP duplication according to another method.

[0022] Figure 8 This is a diagram showing an example of the schematic structure of a wireless communication system according to one embodiment.

[0023] Figure 9 This is a diagram showing an example of the structure of a base station according to one embodiment.

[0024] Figure 10 This is a diagram showing an example of the structure of a user terminal according to one embodiment.

[0025] Figure 11 This is a diagram showing an example of the hardware structure of a base station and a user terminal according to one embodiment. DETAILED DESCRIPTION

[0026] (UE State)

[0027] In a future wireless communication system (hereinafter also referred to as NR), it is envisioned that a terminal (also referred to as a user terminal, user equipment (UE), device, etc.) has multiple states corresponding to traffic activity.

[0028] For example, a UE in NR can also have three states in the Radio Resource Control (RRC) layer: an idle state, an inactive state, and a connected state. This state is also referred to as the UE state, RRC state, etc.

[0029] 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 referred to as the RRC idle state (RRC_IDLE state), RRC idle (RRC_IDLE), etc. A UE in the idle state needs to reconfigure the RRC connection in order to transition to the connected state where data transfer can be performed.

[0030] The inactive state is the state where the RRC connection between the UE and the base station is being established but data transmission is not possible, also known as the RRC inactive state (RRC_INACTIVE state), RRC inactive (RRC_INACTIVE), etc. Since the UE in the inactive state is establishing the RRC connection, it can migrate to the connected state faster compared to the idle state. Therefore, the latency until the start of data transmission is shorter compared to the UE in the idle state.

[0031] The connected state is the state where the RRC connection between the UE and the base station is established and data transmission is possible, also known as the RRC connected state (RRC_CONNECTED state), RRC connected (RRC_CONNECTED), etc. Since the UE in the connected state monitors the downlink control channel (e.g., Physical Downlink Control Channel (PDCCH, physical downlink control channel)) to determine whether to schedule data, the power consumption is higher compared to the idle state or the inactive state.

[0032] (Frequency range)

[0033] In addition, in NR, research is being conducted on supporting multiple frequency ranges (frequency range (FR)). 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 can also support at least one of these multiple FRs.

[0034] (Multicast)

[0035] In addition, in NR, research is being conducted on supporting unicast, which is a one-to-one (Point To Point (PTP)) communication method, and multicast, which is a one-to-many (Point To Multipoint (PTM)) communication method.

[0036] In multicast, the same content is transmitted to one or more terminals (also referred to as user terminals, user equipment (UE), devices, etc.) located in a specific area (also known as, for example, a Multimedia Broadcast Multicast Service (MBMS) service area, etc.). This specific area may also be composed of a single or multiple cells. Multicast with this specific area composed of a single cell may also be referred to as Single Cell (SC)-based PTM (SC-PTM), etc. In the case of SC-PTM, multiple cells may also be coordinated to form multicast.

[0037] Multicast transmission and unicast transmission may also be performed in different time units (e.g., time slots) within the same cell (time multiplexing may also be used). The time unit for performing multicast transmission within a radio frame may be determined in advance by a standard or may be configured (notified) to the UE by higher layer signaling.

[0038] In addition, in the present disclosure, the higher layer signaling may be at least one of, for example, Radio Resource Control (RRC) signaling, system information (e.g., at least one of Remaining Minimum System Information (RMSI), Other System Information (OSI), System Information Block (SIB)), broadcast information (e.g., Physical Broadcast Channel (PBCH), Master Information Block (MIB)), Medium Access Control (MAC) signaling, and Radio Link Control (RLC) signaling.

[0039] Alternatively, multicast transmission and unicast transmission may also be performed in different cells. A UE capable of Carrier Aggregation (CA) or Dual Connectivity (DC) may receive multicast transmission in one cell and receive or transmit unicast transmission in another cell. In addition, a UE that does not perform CA or DC may also switch to a cell for multicast transmission and receive the multicast transmission.

[0040] In addition, the cell can also be replaced with a serving cell, a component carrier (CC), a carrier, etc.

[0041] In multicast transmission, as a logical channel, for example, a multicast traffic channel (MTCH), or MTCH and a multicast control channel (MCCH) can also be used.

[0042] In MTCH, data for multicast transmission (also referred to as multicast data, services, etc.) can also be transmitted. In MCCH, control information required for the reception of MTCH can also be transmitted. In addition, in SC-PTM, MTCH and MCCH can also be referred to as SC-MTCH and SC-MCCH, respectively.

[0043] As logical channels, MTCH and MCCH can also be mapped to a downlink shared channel (DL-SCH) as a transport channel in the medium access control (MAC) layer. In addition, DL-SCH can be mapped to a physical downlink shared channel (PDSCH) as a physical channel in the physical (PHY) layer.

[0044] In addition, in unicast transmission, as logical channels, for example, a dedicated traffic channel (DTCH), a dedicated control channel (DCCH), etc. can also be utilized. DTCH and DCCH can also be mapped to DL-SCH in the MAC layer, and DL-SCH is mapped to PDSCH in the physical layer. In this way, multicast transmission and unicast transmission can also be associated with the same type of transport channel and physical channel (i.e., DL-SCH and PDSCH).

[0045] However, in the existing LTE system, multicast transmission is performed using a physical multicast channel (PMCH). In addition, in NR, it is envisaged to adopt a system structure different from the existing LTE system, such as setting one or more bandwidth parts (BWPs) in a cell. Therefore, in NR, how to control the reception of multicast transmission using PDSCH by a UE becomes a problem.

[0046] Therefore, the inventors of the present invention studied a method for appropriately controlling the reception of multicast transmission using PDSCH in NR, and obtained the present invention.

[0047] Hereinafter, embodiments related to the present disclosure will be described in detail with reference to the drawings. In the present disclosure, multicast transmission may also be interchangeable with at least one of multicast, multicast service, multicast data, service related to multicast and broadcast (multicast / broadcast), or multicast / broadcast, MBMS, MTCH, etc.

[0048] (First mode)

[0049] In the first mode, support for multicast transmission in a single or multiple cells will be described.

[0050] <Single cell>

[0051] A single cell that supports multicast transmission may be set for each cell group, may be set for a specific cell group (e.g., Master Cell Group (MCG) or Secondary Cell Group (SCG)), may be set for each FR, or may be set for a specific FR.

[0052] This single cell may also be a Primary Cell (PCell), a PrimarySecondary Cell (PSCell), a Special Cell (SpCell), a Secondary Cell (SCell) that transmits a Physical Uplink Control Channel (e.g., Physical Uplink Control Channel (PUCCH)) (PUCCH SCell), the cell with the smallest index within each cell group or each FR, or a cell configured by RRC signaling or multicast system information (e.g., SIB20).

[0053] In the case of DC, the SpCell may also be the PCell within the MCG or the PSCell within the SCG. In cases other than DC (e.g., CA or single cell), the SpCell may also be the PCell.

[0054] A certain type of multicast transmission may be supported in the entire single cell, or may be supported in one or more Bandwidth Parts (BWPs) within the single cell. A BWP is a partial band within a cell.

[0055] The BWP that supports multicast transmission can also be an initial BWP (also referred to as an initial downlink BWP, an initial downlink active BWP, etc.), or can also be a BWP designated by at least one of higher layer signaling and L1 signaling (physical layer signaling).

[0056] For example, the BWP that provides multicast transmission to at least one of the idle state and the inactive state (idle / inactive state) for one or more UEs (or a group including the one or more UEs) can also be any of the following.

[0057] · Initial BWP

[0058] · A BWP determined based on at least one of multicast system information (e.g., SIB20), information transmitted through MCCH (MCCH information), and DCI

[0059] The BWP that provides multicast transmission to one or more UEs (or a group including the one or more UEs) in the connected state can also be any of the following.

[0060] · Initial BWP

[0061] · The first BWP in the cell (the BWP with the smallest index (index value))

[0062] · A BWP determined based on at least one of multicast system information (e.g., SIB20), RRC signaling (also referred to as RRC parameters, RRC IE, RRC messages, etc.), and L1 signaling (e.g., information transmitted through MCCH (MCCH information) and DCI)

[0063] In addition, in the present disclosure, the information transmitted through MCCH only needs to be information for receiving multicast transmission (e.g., MTCH). The information for receiving this multicast transmission (MTCH) can also be information transmitted through at least one of PDCCH and PDSCH, or can be replaced with information for performing RLC signaling, etc., and is not necessarily limited to information transmitted through MCCH.

[0064] Figure 1 It is a diagram showing an example of multicast transmission in a single cell related to the first method. Figure 1 In this example, for instance, it is assumed that the UE performs CA or DC using multiple cells (here, cells #0 to #2). Here, it is assumed that in cell #0 as the PCell, a certain type (here, type a) of multicast transmission is supported.

[0065] As Figure 1 shown, cell #0 includes one or more BWPs. Multicast transmission can also be supported in at least one BWP within cell #0. For example, Figure 1In cell #0, it includes an initial BWP (BWP#0), BWP#1, and #2, and type a multicast service is supported in BWP#1.

[0066] In addition, Figure 1 For illustration only, the number and types of BWPs that support multicast transmission within a single cell are not limited to those shown in the figure. In addition, Figure 1 In [the figure], cell #0 and #1 are set in FR1, and cell #2 is set in FR2. However, for illustration only, it is not limited to the figure shown. 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.

[0067] <Multiple Cells / BWPs>

[0068] The multiple cells that support multicast transmission may also be multiple cells belonging to different cell groups, or may be multiple cells belonging to the same cell group or performing CA.

[0069] In each of these multiple cells, multicast transmission may also be supported in one or more BWPs. These one or more BWPs may be determined in the same way as the single cell that supports multicast transmission described above.

[0070] In addition, in these multiple cells, different types of multicast services may also be supported. In a certain carrier (or a certain BWP of that certain carrier), only a single type of multicast service may be supported. Or, in a certain carrier (or a certain BWP of that certain carrier), multiple types of multicast services may be supported.

[0071] Different types of multicast services may also be associated with different MTCHs. The type of multicast service used in each cell (or each BWP) may also be notified to the UE through at least one of high-layer signaling and L1 signaling.

[0072] Specifically, the UE may also receive information indicating the type of multicast service (multicast type information) for each cell (or each BWP). This multicast type information may be notified through RRC signaling (it may also be an RRC parameter), may be included in system information (such as SIB20), or may be included in the information transmitted through MCCH.

[0073] Figure 2 It is a diagram showing an example of multicast transmission in multiple cells related to the first method. Figure 2 In [the figure], for example, the UE is configured to perform CA or DC using multiple cells (here, cells #0 to #3). Here, it is assumed that in cell #0 and cell #2, which are PCells, a certain type of multicast service is supported.

[0074] For example,Figure 2 Among them, in cell #0, multicast services of types a and b are supported, and in cell #2, multicast services of type c are supported.

[0075] It is also possible to support at least one of the types supported in each cell that supports multicast transmission in more than one BWP. Among the BWPs within the same cell, the supported types may be the same or at least one type may be different.

[0076] For example, in Figure 2 BWP #1 of cell #0, multicast services of types a and b are supported. On the other hand, in BWP #2, multicast services of type a are supported and multicast services of type b are not supported. In addition, in Figure 2 BWP #0 to #2 of cell #2, multicast services of the same type c are supported.

[0077] In addition, Figure 2 For illustration only, the number of cells that support multicast transmission, the number and types of BWPs that support multicast transmission in each cell, etc. are not limited to the illustration. In addition, Figure 2 Among them, cell #0 and #1 are FR1, and cell #2 and #3 are FR2. Cells that support multicast transmission are set for each FR, but for illustration only, it is not limited to the illustration. For example, cells that support multicast transmission may also be set for each cell group.

[0078] As described above, according to the first method, multicast services can be supported in units of BWP. In addition, from at least one of the viewpoints of network management and resource utilization efficiency (usage), it is also possible to adjust (align) settings (configurations) related to BWP, such as BWP size, etc., among UEs with different capabilities (capability).

[0079] (Second method)

[0080] In the second method, the UE that receives multicast transmission and the operations of this UE are described.

[0081] Multicast transmission can also be supported for one or more UEs in at least one of the UE states of connected state, idle state, and inactive state. For example, multicast transmission can also be supported in at least one of the following UEs.

[0082] · One or more UEs in only the connected state

[0083] · One or more UEs in only the idle state

[0084] · One or more UEs in only the inactive state

[0085] One or more UEs in at least two UE states, namely, a connected state, an idle state, and an inactive state

[0086] One or more UEs that receive multicast transmissions may also support at least one of the following groups determined based on the UE state.

[0087] (1) A group that supports UEs in only a specific UE state (e.g., an idle state, an inactive state, or a connected state)

[0088] (2) Either a group that supports UEs in a first UE state (e.g., an idle / inactive state) or a group that supports UEs in a second UE state (e.g., a connected state)

[0089] (3) Both a first group that supports UEs in a first UE state (e.g., an idle / inactive state) and a second group that supports UEs in a second UE state (e.g., a connected state)

[0090] In the case of (3), the configuration information related to multicast transmission (multicast configuration information) may be the same (may be common) or different (may be dedicated) for the above-mentioned first group (e.g., UEs in an idle / inactive state) and second group (e.g., UEs in a connected state).

[0091] <Common multicast configuration information>

[0092] For example, common multicast configuration information may be notified to UEs in an idle / inactive state and UEs in a connected state through multicast system information (e.g., SIB20). In addition to this multicast system information, this common multicast configuration information may also be notified using L1 signaling (e.g., at least one of the information transmitted via MCCH and DCI), or may be notified only through multicast system information without using L1 signaling.

[0093] <Dedicated multicast configuration information>

[0094] The multicast configuration information for UEs in an idle / inactive state may also be notified through multicast system information (e.g., SIB20). In addition to this multicast system information, this multicast configuration information may also be notified using L1 signaling (e.g., at least one of the information transmitted via MCCH and DCI), or may be notified only through multicast system information without using L1 signaling.

[0095] On the other hand, the multicast setting information of the connected UE can also be notified by multicast system information (e.g., SIB20). In addition to this multicast system information, the multicast setting information can also be notified by using L1 signaling (e.g., at least one of the information transmitted via MCCH and DCI), or can be notified only by the multicast system information without using L1 signaling.

[0096] Alternatively, the multicast setting information of the connected UE can also be notified by RRC signaling. In addition to this RRC signaling, the multicast setting information can also be notified by using L1 signaling (e.g., at least one of the information transmitted via MCCH and DCI), or can be notified only by the RRC signaling without using L1 signaling.

[0097] <Multicast Transmission Reception Operation>

[0098] Next, the reception operation (scheduling) of the multicast transmission for the group as described above (e.g., the above (1) to (3)) will be described. For example, the following three scheduling methods are envisioned.

[0099] The scheduling of the multicast transmission for the group as described above (e.g., the above (1) to (3)) will be described. For example, the following three scheduling methods are envisioned.

[0100] In the first scheduling, the UE can also receive the multicast system information (e.g., Figure 3 step S11), receive the MCCH based on the configuration information related to MCCH (MCCH setting information) included in the system information (e.g., Figure 3 step S12), and receive the MTCH based on the information transmitted via the MCCH (e.g., multicast setting information) (e.g., Figure 3 step S13). The UE can be at least one of an idle state UE, a non-active state UE, and a connected state UE.

[0101] In the second scheduling, the UE can also receive the multicast system information (e.g., Figure 4 step S21), and receive the MTCH based on the information included in the system information (e.g., multicast setting information) (e.g., Figure 4 step S22). The UE can be at least one of an idle state UE, a non-active state UE, and a connected state UE.

[0102] In the third scheduling, the UE can also receive an RRC message (e.g., an RRC reconfiguration message) (e.g., Figure 5Step S31), receive MTCH (e.g., Figure 5 Step S31). The UE can also be a connected state UE.

[0103] In the first to third scheduling, the UE can also receive the above MTCH (multicast data) via the PDSCH scheduled by the DCI scrambled by CRC using a specific Radio Network Temporary Identifier (RNTI).

[0104] This specific RNTI can also be the RNTI for each multicast service (type of each multicast service). This specific RNTI can also be referred to as, for example, group (G or GC)-RNTI, single cell (SC)-RNTI, multicast (M or MC)-RNTI, multicast RNTI, etc. The G-RNTI value can also be the same among UEs belonging to the same group (e.g., the above (1) to (3)).

[0105] In a certain UE, more than one G-RNTI can be introduced. Each G-RNTI can also be associated with more than one type of multicast transmission supported by the UE in a certain cell or multiple cells.

[0106] For example, in an idle / inactive state UE, at least one of the multicast system information and L1 signaling (e.g., at least one of the information transmitted through MCCH and DCI) can be used to notify more than one G-RNTI.

[0107] In addition, in a connected state UE, at least one of the multicast system information, L1 signaling (e.g., at least one of the information transmitted through MCCH and DCI), and RRC signaling can be used to notify more than one G-RNTI.

[0108] The maximum number X of G-RNTIs that can be set for a certain UE in a certain cell or a certain BWP can be determined by a standard, or can also be configured based on the UE's capability. For example, the maximum number X of G-RNTIs can be set so as not to exceed the UE capability reported by the UE.

[0109] "First Scheduling"

[0110] Figure 3 It is a diagram showing an example of the first scheduling of the multicast transmission related to the second method. Figure 3 The first scheduling shown can also be applied to a group including at least an idle / inactive state UE. This group can also include a connected state UE, or may not.

[0111] As Figure 3 shown, in step S11, the UE may also receive system information for multicast (e.g., SIB20). Specifically, in step S111, the UE may also listen to a search space (SS) set including one or more search spaces, and detect a Physical Downlink Control Channel (PDCCH) (DCI) scrambled with a Cyclic Redundancy Check (CRC) using a specific Radio Network Temporary Identifier (RNTI) (e.g., System Information (SI)-RNTI).

[0112] In step S112, the UE may obtain the system information via a Physical Downlink Shared Channel (PDSCH) scheduled by the DCI. The system information may also include configuration information related to the Multicast Control Channel (MCCH) (MCCH configuration information).

[0113] The MCCH configuration information may include at least one of, for example, a period for transmitting the MCCH (repetition period), a time offset, and a period for updating information transmitted via the MCCH (modification period).

[0114] 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 also listen to the SS set and detect a PDCCH (DCI) scrambled with a CRC using a specific identifier.

[0115] The specific identifier may be a specific RNTI (e.g., Single Cell (SC)-RNTI), or may be a Temporary Mobile Group Identifier. The specific identifier may also be included in the above MCCH configuration information.

[0116] In step S122, the UE may obtain the MCCH via a PDSCH scheduled by the DCI. The MCCH may be transmitted repeatedly at the above repetition period. The same information may be transmitted in the MCCH for each repetition period within the modification period. When changing information transmitted via the MCCH, it may be notified in the immediately preceding modification period that the information transmitted via the MCCH will be changed in the next modification period. This notification may be referred to as an SC-MCCH change notification, etc.

[0117] In this notification, the PDCCH can also be utilized. The UE can also control Discontinuous Reception (DRX) based on this notification. Specifically, the UE can also start only at the time of this notification and, if not changed to the information transmitted through the MCCH, migrate to the DRX state.

[0118] In steps S13a and 13b, the UE also receives the MTCH based on the information transmitted through this MCCH (e.g., setting information related to MTCH (multicast) (also referred to as MTCH setting information, multicast setting information, etc.)). The information transmitted through this MTCH setting information can also include, for example, information indicating at least one of the following.

[0119] · G-RNTI

[0120] · Payload size of the DCI

[0121] · Cell corresponding to the multicast transmission

[0122] · BWP corresponding to the multicast transmission

[0123] · Multicast transmission type supported in each cell or BWP

[0124] · Control Resource Set (CORESET) configured for the PDCCH that schedules the PDSCH transmitting the MTCH

[0125] · SS set for monitoring this PDCCH

[0126] · Setting information related to the PDSCH transmitting the MTCH (PDSCH setting information)

[0127] In steps S131a and 131b, the UE can also monitor the SS set and detect the PDCCH (DCI) scrambled with a CRC using a specific RNTI (e.g., G-RNTI). Additionally, this specific RNTI can be different values for each type of multicast transmission. For example, Figure 3 shows G-RNTI_a corresponding to the type a multicast transmission and G-RNTI_b corresponding to the type b multicast transmission.

[0128] In steps S132a and 132b, the UE can also obtain the MTCH corresponding to types a and b respectively via the PDSCH scheduled by this DCI.

[0129] In addition, steps S13a and 13b, S131a and 131b, and S132a and 132b can each assume different types of multicast transmissions, but the operations are the same.

[0130] "Second Scheduling"

[0131] Figure 4 It is a diagram showing an example of the second scheduling of multicast transmission related to the second method. Figure 4 The second scheduling shown can also be applied to a group including at least UEs in the idle / inactive state. This group may or may not include UEs in the connected state.

[0132] Figure 4 The operation of step S21 is the same as Figure 3 step S11. On the other hand, the system information for multicast (e.g., SIB20) obtained in step S212 may also include the above MTCH setting information instead of the above MCCH setting information. The information included in this MTCH setting information is as described in the first scheduling.

[0133] In steps S22a and 22b, the UE receives the MTCH based on the MTCH setting information in the system information obtained in step S21. In addition, the details of steps S22a and S22b are the same as Figure 3 steps S13a and S13b.

[0134] "Third Scheduling"

[0135] Figure 5 It is a diagram showing an example of the third scheduling of multicast transmission related to the second method. Figure 5 The third scheduling shown can also be applied to a group including UEs in the connected state. This group does not include UEs in the idle / inactive state.

[0136] Figure 5 In step S31 of , the UE may also receive the above MTCH setting information via RRC signaling. Specifically, in step S311, the UE may listen to an SS set including one or more search spaces and detect PDCCH (DCI) scrambled with CRC using the UE's unique RNTI (e.g., Cell(C)-RNTI).

[0137] In step S312, the UE may obtain the MTCH setting information via the PDSCH scheduled by this DCI. This MTCH setting information may also be included in, for example, an RRC reconfiguration message. The information included in this MTCH setting information is as described in the first scheduling.

[0138] In steps S32a and 32b, the UE receives the MTCH based on the MTCH setting information in the system information obtained in step S31. In addition, the details of steps S32a and S32b are the same as Figure 3 steps S13a and S13b.

[0139] As described above, in NR, MTCH (multicast data) is received via a PDSCH scheduled by a PDCCH (DCI) scrambled with a G-RNTI based on MCCH, system information for multicast, or MTCH setting information included in an RRC message.

[0140] As described above, according to the second method, scheduling of multicast transmission can be appropriately performed for UEs in each UE state (e.g., idle state, inactive state, connected state).

[0141] (Third method)

[0142] In the third method, UE behavior related to reception of at least one of a PDCCH and a PDSCH related to multicast transmission is described. This UE behavior may be the same or different between at least two UEs in the idle state, inactive state, and connected state.

[0143] This UE behavior may also include, for example, setting of a Transmission Configuration Indicator (TCI) state (TCI state) for reception of MTCH (or MCCH and MTCH) and at least one of transmission control of Uplink Control Information (UCI).

[0144] <TCI state>

[0145] The TCI state refers to information related to, for example, quasi-co-location (QCL) of a target channel (in other words, a reference signal (RS) for this channel) and another signal (e.g., another reference signal (RS)). The TCI state may also be referred to as a spatial reception parameter, spatial relation information (SRI), etc. In addition, the TCI state may also be referred to as information indicating a beam for transmitting a target channel.

[0146] QCL refers to an indicator representing the statistical properties of at least one of a signal and a channel (signal / channel). For example, in the case where a certain signal / channel and other signal / channel are in a QCL relationship, it can also refer to that among these multiple different signals / channels, at least one of Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (such as spatial Rx parameter) can be set to be the same (QCL for at least one of these).

[0147] In addition, the spatial Rx parameter can also correspond to the receiving beam of the UE (such as the receiving analog beam), and the beam can also be determined based on spatial QCL. The QCL (or at least one element of QCL) in this disclosure can also be replaced by sQCL (spatial QCL).

[0148] The UE can also determine at least one of the transmission beam (Tx beam) and the receiving beam (Rx beam) of the signal / channel based on the TCI state or QCL relationship of the signal / channel.

[0149] The channel set (designated) with the TCI state or spatial relationship can also be at least one of, for example, PDSCH, PDCCH, uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and uplink control channel (Physical Uplink Control Channel (PUCCH)).

[0150] In addition, the RS in a QCL relationship with this channel can also be at least one of, for example, Synchronization Signal Block (SSB), Channel State Information Reference Signal (CSI-RS), Sounding Reference Signal (SRS), CSI-RS for tracking (also called Tracking Reference Signal (TRS)), QCL detection reference signal (also called QRS), etc.

[0151] An SSB is a signal block that includes at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0152] A UE receiving multicast transmission may also control the reception of a PDSCH associated with at least one of an MTCH and an MCCH (MTCH / MCCH) based on a PDSCH (or an antenna port of a Demodulation Reference Signal (DMRS) of the PDSCH) and information (TCI state) related to QCL with a specified RS.

[0153] For example, which beam (also referred to as a TCI state, QCL relationship) the UE in the idle / inactive state uses to receive the above PDSCH may also be an implementation of the UE, may be determined based on the detected SSB, or may be the same as system information for multicast (e.g., SIB20).

[0154] In addition, which beam (also referred to as a TCI state, QCL relationship) the UE in the connected state uses to receive the above PDSCH may be determined using at least one of RRC signaling, MAC signaling, and DCI. In addition, the TCI state (QCL relationship) of the UE in the connected state may also be determined based on information transmitted through system information for multicast.

[0155] Specifically, the UE may also notify (set) M (M≥1) TCI states (QCL information for M PDSCHs) for the PDSCH through RRC signaling. In addition, the number M of TCI states set for the UE may be restricted by at least one of UE capability and QCL type.

[0156] The DCI for scheduling the PDSCH may also include a field indicating the TCI state for the PDSCH (which may also be referred to as, for example, a TCI field, a TCI state field, etc.).

[0157] When setting a TCI state greater than a specified number (e.g., 8 when the TCI field is 3 bits) for a UE via higher-layer signaling, the MAC CE can also be used to activate (or specify) the specified number of TCI states. The value of the TCI field in the DCI can also represent one of the TCI states activated by the MAC CE.

[0158] Figure 6 FIG. is an example showing beam control related to multicast transmission according to the third method. As Figure 6 shown, the base station (e.g., gNB) can also perform multicast transmission by using beam cycling of multiple beams (here, beams #1 to #4). In addition, beam cycling is also referred to as beam scanning, etc., and the beam transmitted by the base station can also be switched in time.

[0159] As Figure 6 shown, each beam for multicast transmission can also be associated with a specified RS or resources for the specified RS (e.g., SSB or CSI-RS resources). For example, Figure 6 in, beams #1 to #4 can be associated with SSB #1 to #4, or CSI-RS resources #1 to #4, respectively.

[0160] For example, as Figure 6 shown, when an idle / inactive state UE detects SSB #1 and #2 transmitted by beams #1 and #2 respectively, it can also be set (assumed) that the DMRS of the PDSCH and SSB #1 and #2 transmitted by beams #1 and #2 are in a QCL relationship, and the reception of the PDSCH is controlled.

[0161] On the other hand, as Figure 6 shown, a connected state UE can also receive four TCI states indicating that the DMRS of the PDSCH and SSB #1 to #4 (or CSI-RS resources #1 to #4) transmitted by beams #1 to #4 are in a QCL relationship via RRC signaling.

[0162] The UE can also be set (assumed) that the DMRS of the PDSCH and SSB #3 (or CSI-RS resource #3) transmitted by beam #3 are in a QCL relationship based on the TCI state indicated by the value of a certain field (e.g., TCI field) in the DCI (DCI scrambled with CRC using the above G-RNTI) for scheduling the PDSCH, and the reception of the PDSCH is controlled.

[0163] <UCI Transmission Control>

[0164] The UCI may also include at least one of delivery confirmation information for the PDSCH (which may also be referred to as, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), Channel State Information (CSI), and Scheduling Request (SR).

[0165] In NR, HARQ-ACK for multicast transmission (HARQ-ACK for the PDSCH transmitting the MTCH or (MTCH and MCCH)) may also be supported, or may not be supported.

[0166] In addition, in NR, feedback of CSI for multicast transmission (CSI feedback for the PDSCH for the MTCH or (transmitting the MTCH and MCCH)) may also be supported, or may not be supported. In addition, the feedback (transmission) of CSI may also be referred to as a CSI report, etc.

[0167] In addition, in NR, transmission of RS (such as Sounding Reference Signal (SRS)) for estimating channel conditions for multicast transmission may also be supported in Time Division Duplex (TDD), or may not be supported.

[0168] For example, a UE in the idle / inactive state may also not perform at least one of the above HARQ-ACK, CSI report, and transmission of the above RS for channel condition estimation (such as SRS). On the other hand, a UE in the connected / inactive state may also perform at least one of the above HARQ-ACK, CSI report, and transmission of the above RS for channel condition estimation (such as SRS).

[0169] (Fourth method)

[0170] In the fourth method, restrictions in multicast transmission are described.

[0171] In multicast transmission, at least one of the following restrictions may be set, or may not be set, for the PDSCH associated with the MTCH.

[0172] (4.1) Number of Transport Blocks (TBs)

[0173] (4.2) Number of layers (also referred to as rank)

[0174] (4.3) Number of antenna ports of DMRS (DMRS ports)

[0175] (4.4) Sub - Carrier Spacing (SCS)

[0176] (4.5) Cyclic Prefix (CP) length

[0177] (4.6) At least one of modulation order and transport block size (TBS)

[0178] For example, when there are restrictions on the number of (4.1) TBs, in the PDSCH associated with MTCH, only a specific number of TBs (e.g., a single TB) can be transmitted.

[0179] When there are restrictions on the number of (4.2) layers, in the PDSCH associated with MTCH, only a specific number of layers (e.g., a single layer) can be transmitted.

[0180] When there are restrictions on the number of (4.3) DMRS ports, in the PDSCH associated with MTCH, only a specific number of DMRS ports (e.g., a single DMRS port) can be transmitted.

[0181] When there are restrictions on (4.4) SCS, in the PDSCH associated with MTCH, only a specific SCS (e.g., 120 kHz) is supported. On the other hand, when there are no restrictions on this SCS, in this PDSCH, not only this specific SCS but also other SCSs (e.g., 15 kHz, 30 kHz, 60 kHz, 240 KHz, 480 kHz, 960 kHz, etc.) can be supported.

[0182] In (4.5) specific SCSs (e.g., 15 kHz, 30 kHz, 120 kHz, 240 kHz, 480 kHz, 960 kHz), for the PDSCH associated with MTCH, normal CP is usually applied, but it is also possible not to apply enhanced CP which is longer than normal CP. Additionally, when enhanced CP is applied to this PDSCH, a specific SCS (e.g., 60 kHz) can also be applied to this PDSCH.

[0183] Alternatively, in the case of applying a specific SCS (e.g., 15 kHz, 30 kHz, 120 kHz, 240 kHz, 480 kHz, 960 kHz) to the PDSCH associated with MTCH, not only the normal CP but also the enhanced CP can be applied.

[0184] (4.6) The modulation order of the PDSCH associated with MTCH may also not be expected to be greater than 2 or 4. Here, the modulation order "2" is Quadrature Phase Shift Keying (QPSK), and the modulation order "4" is 16-Quadrature Amplitude Modulation (QAM). That is, for this PDSCH, 64QAM with a modulation order of "6" or 256QAM with a modulation order of "8" may not be applied either.

[0185] In addition, at least one of the Transport Block Size (TBS), modulation, and Modulation and Coding Scheme (MCS) index applied to the PDSCH associated with MTCH may also be specified based on at least one of the system information for multicast (e.g., SIB20), RRC signaling (e.g., RRC reset message or RRC resume message), and physical layer signaling (e.g., information transmitted through the PDSCH associated with MCCH or DCI). Additionally, the TBS may also be determined by the UE based on the MCS index, etc.

[0186] According to the fourth method, the transmission or reception of the PDSCH associated with MTCH can be appropriately controlled.

[0187] (Other methods)

[0188] In other methods, the enhancement in multicast transmission is described.

[0189] Multicast transmission may also be combined with at least one of the following.

[0190] (5.1) Multiple Transmission and Reception Points (TRP) (multi-TRP)

[0191] (5.2) Transmission based on Code Block Group (CBG)

[0192] (5.3) Semi-Persistent Scheduling (SPS)

[0193] (5.4) Duplication in the Packet Data Convergence Protocol (PDCP) layer

[0194] (5.1) In multi-TRP, the PDSCH associated with MTCH can also be sent by multiple TRPs.

[0195] (5.2) The CBG contains more than one code block (CB). Each CB is formed by setting 1 TB as a segment. It is also possible to support or configure the CBG-based transmission of the PDSCH associated with MTCH. This CBG-based transmission can also be set based on whether multicast transmission supports or sets HARQ-ACK feedback.

[0196] For example, in the case where multicast transmission supports or sets HARQ-ACK feedback, it is also possible to set the CBG-based transmission of the PDSCH associated with MTCH. On the other hand, in the case where multicast transmission supports or sets HARQ-ACK feedback, it is also possible not to set the CBG-based transmission of the PDSCH associated with MTCH.

[0197] (5.3) SPS is applied to the PDSCH associated with MTCH. In this case, it is also possible to support the DCI (group DCI) that activates or releases this SPS. This DCI can also be CRC scrambled using the above G-RNTI.

[0198] (5.4) The data involved in multicast transmission (data transmitted through MTCH) can also be duplicated in the PDCP layer and sent in multiple cells. Thus, the UE can also select the data sent in any one of these multiple cells, or can combine the data sent in at least two of these multiple cells.

[0199] Figure 7A And Figure 7B is an example showing PDCP duplication involved in other ways. For example, Figure 7A In Figure 7B, the multicast data associated with a certain radio bearer (such as a multicast bearer) can also be duplicated twice.

[0200] The two multicast data can also each be mapped to two MTCHs corresponding to different cells #1 and #2 in the RLC layer. These two MTCHs are respectively mapped to two DL-SCHs corresponding to different cells #1 and #2 in the MAC layer. These two DL-SCHs can also be respectively mapped to two PDSCHs corresponding to different cells #1 and #2 in the L1 layer.

[0201] As Figure 7A shown, it is also possible to multicast both the PDSCH corresponding to cell #1 and the PDSCH corresponding to cell #2.

[0202] Alternatively, as Figure 7B shown, it is also possible to multicast the PDSCH corresponding to cell #1, while unicasting the PDSCH corresponding to cell #2.

[0203] (Wireless communication system)

[0204] Hereinafter, the structure of a wireless communication system according to an embodiment of the present disclosure will be described. In this wireless communication system, communication is performed using one or a combination of the above-described wireless communication methods according to the respective embodiments of the present disclosure.

[0205] Figure 8 is a diagram showing an example of the schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may also be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., which are standardized by the Third Generation Partnership Project (3GPP).

[0206] In addition, the wireless communication system 1 may also support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple Radio Access Technologies (RATs). MR-DC may also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0207] In EN-DC, the base station (eNB) of LTE (E-UTRA) is the master node (MN), and the base station (gNB) of NR is the secondary node (SN). In NE-DC, the base station (gNB) of NR is the MN, and the base station (eNB) of LTE (E-UTRA) is the SN.

[0208] The wireless communication system 1 may also support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both the MN and the SN are base stations (gNBs) of NR (NR-NR dual connectivity (NN-DC))).

[0209] The wireless communication system 1 may also include: a base station 11 that forms a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a - 12c) that is disposed within the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration, number, etc. of each cell and the user terminal 20 are not limited to the manner shown in the figure. Hereinafter, the base stations 11 and 12 are collectively referred to as the base station 10 without distinction.

[0210] The user terminal 20 may also be connected to at least one of the multiple base stations 10. The user terminal 20 may also utilize at least one of carrier aggregation (CA) and dual connectivity (DC) that uses multiple component carriers (CCs).

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

[0212] Furthermore, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0213] Multiple base stations 10 can also be connected via wired (e.g., optical fibers based on the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is utilized as a backhaul between base stations 11 and 12, the base station 11 equivalent to the upper station can also be referred to as an Integrated Access Backhaul (IAB) donor, and the base station 12 equivalent to the relay station can also be referred to as an IAB node.

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

[0215] The user terminal 20 can also be a user terminal that supports at least one of communication methods such as LTE, LTE-A, 5G, etc.

[0216] In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) can also be utilized. For example, in at least one of the Downlink (DL) and the 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. can also be utilized.

[0217] The wireless access method can also be referred to as a waveform. Additionally, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be applied in the wireless access methods of the UL and the DL.

[0218] In the wireless communication system 1, as a downlink channel, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. can also be used.

[0219] In addition, in the wireless communication system 1, as an uplink channel, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. can also be used.

[0220] User data, high-layer control information, System Information Block (SIB), etc. are transmitted through the PDSCH. User data, high-layer control information, etc. can also be transmitted through the PUSCH. In addition, the Master Information Block (MIB) can be transmitted through the PBCH.

[0221] Low-layer control information can also be transmitted through the PDCCH. The low-layer control information can also include, for example, downlink control information (Downlink Control Information (DCI)), and the downlink control information includes scheduling information of at least one of the PDSCH and the PUSCH.

[0222] In addition, the DCI scheduling the PDSCH can also be referred to as DL allocation, DL DCI, etc., and the DCI scheduling the PUSCH can also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH can also be replaced by DL data, and the PUSCH can also be replaced by UL data.

[0223] In the detection of PDCCH, the control resource set (CORESET) and the search space can also be utilized. The CORESET corresponds to the resource for searching DCI. The search space corresponds to the search area and search method for PDCCH candidates. One CORESET can also be associated with one or more search spaces. The UE can also monitor the CORESET associated with a certain search space based on the search space setting.

[0224] One search space can also correspond to PDCCH candidates that match one or more aggregation levels. One or more search spaces can also be referred to as a search space set. Additionally, in the present disclosure, "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. can also be replaced with each other.

[0225] It is also possible to transmit uplink control information (Uplink Control Information (UCI)) including at least one of channel state information (Channel State Information (CSI)), delivery confirmation information (e.g., it can also be referred to as Hybrid Automatic Repeat Request (HARQ-ACK), ACK / NACK, etc.), and scheduling request (Scheduling Request (SR)) through PUCCH. It is also possible to transmit a random access preamble for establishing a connection with the cell through PRACH.

[0226] Furthermore, in the present disclosure, the downlink, uplink, etc. can also be expressed without "link". In addition, it can also be expressed that "Physical" is not included at the beginning of various channels.

[0227] In the wireless communication system 1, it is also possible to transmit a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. In the wireless communication system 1, as the DL-RS, it is also possible to transmit a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc.

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

[0229] In addition, in the wireless communication system 1, as an uplink reference signal (Uplink Reference Signal (UL-RS)), it is also possible to transmit a reference signal for measurement (sounding reference signal (Sounding Reference Signal (SRS))), a demodulation reference signal (DMRS), etc. In addition, DMRS may also be referred to as a user equipment-specific reference signal (UE-specific Reference Signal).

[0230] (Base station)

[0231] Figure 9FIG. 0 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission path interface (transmission line interface) 140. In addition, one or more of the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140 may be provided respectively.

[0232] In addition, in this example, the functional blocks of the characteristic parts in this embodiment are mainly shown, and the base station 10 may also be assumed to have other functional blocks required for wireless communication. A part of the processing of each unit described below may also be omitted.

[0233] The control unit 110 implements the overall control of the base station 10. The control unit 110 can be constituted by a controller, a control circuit, etc. that can be explained based on the common knowledge in the technical field related to the present disclosure.

[0234] The control unit 110 may also control the generation of signals, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission / reception, measurement, etc. using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140. The control unit 110 may also generate data, control information, sequence, etc. to be transmitted as signals, and forward them to the transmission / reception unit 120. The control unit 110 may also perform call processing (setting, releasing, etc.) of communication channels, state management of the base station 10, management of radio resources, etc.

[0235] The transmission / reception unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmission / reception unit 120 can be constituted by a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc. that can be explained based on the common knowledge in the technical field related to the present disclosure.

[0236] The transmission / reception unit 120 may be configured as an integrated transmission / reception unit, or may be constituted by a transmission unit and a reception unit. The transmission unit may be constituted by the transmission processing unit 1211 and the RF unit 122. The reception unit may be constituted by the reception processing unit 1212, the RF unit 122, and the measurement unit 123.

[0237] The transmission / reception antenna 130 can be composed of antennas that can be described based on common knowledge in the technical field related to the present disclosure, such as an array antenna.

[0238] The transmission / reception unit 120 can also transmit the above-mentioned downlink channels, synchronization signals, downlink reference signals, etc. The transmission / reception unit 120 can also receive the above-mentioned uplink channels, uplink reference signals, etc.

[0239] The transmission / reception unit 120 can also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. to form at least one of a transmission beam and a reception beam.

[0240] The transmission / reception unit 120 (transmission processing unit 1211) can also perform, for example, processing of the Packet Data Convergence Protocol (PDCP) layer, processing of the Radio Link Control (RLC) layer (e.g., RLC retransmission control), processing of the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0241] The transmission / reception unit 120 (transmission processing unit 1211) can also perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filter processing, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, digital-to-analog conversion, etc. on the bit string to be transmitted, and output a baseband signal.

[0242] The transmission / reception unit 120 (RF unit 122) can also perform modulation to a radio frequency band, filter processing, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmission / reception antenna 130.

[0243] On the other hand, the transmission / reception unit 120 (RF unit 122) can also perform amplification, filter processing, demodulation to a baseband signal, etc. on the radio frequency band signal received through the transmission / reception antenna 130.

[0244] The transmission / reception unit 120 (reception processing unit 1212) can also perform reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing on the acquired baseband signal, and obtain user data and the like.

[0245] The transmission / reception unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 can also perform measurements on received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

[0246] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30, other base stations 10, etc., and can also obtain and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0247] In addition, the transmission unit and reception unit of the base station 10 in the present disclosure can also be constituted by at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.

[0248] The transmitting and receiving unit 120 may also transmit downlink control information. In addition, the transmitting and receiving unit 120 may also transmit a downlink shared channel. The downlink control information may also scramble cyclic redundancy check (CRC) bits using a radio network temporary identifier (RNTI) common to one or more terminals.

[0249] The transmitting and receiving unit 120 may also transmit the RNTI for each type of multicast service.

[0250] When the user terminal 20 is in at least one of an idle state, an inactive state, and a connected state, the transmitting and receiving unit 120 may also transmit information for receiving the data (e.g., the above-mentioned MTCH setting information, multicast setting information) using a physical downlink shared channel associated with a multicast control channel (MCCH).

[0251] When the user terminal 20 is in at least one of an idle state, an inactive state, and a connected state, the transmitting and receiving unit 120 may also transmit information for receiving the data (e.g., the above-mentioned MTCH setting information, multicast setting information) using system information for multicast.

[0252] When the user terminal 20 is in a connected state, the transmitting and receiving unit 120 may also transmit information for receiving the data (e.g., the above-mentioned MTCH setting information, multicast setting information) using radio resource control (RRC) signaling.

[0253] (User terminal)

[0254] Figure 10 is a diagram showing an example of the structure of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting and receiving unit 220, and a transmitting and receiving antenna 230. In addition, one or more of the control unit 210, the transmitting and receiving unit 220, and the transmitting and receiving antenna 230 may be provided.

[0255] In addition, in this example, mainly the functional blocks of the characteristic parts in this embodiment are shown, and the user terminal 20 may also be assumed to have other functional blocks required for wireless communication. A part of the processing of each unit described below may also be omitted.

[0256] The control unit 210 implements overall control of the user terminal 20. The control unit 210 may be composed of a controller, a control circuit, etc. that can be explained based on common knowledge in the technical field related to the present disclosure.

[0257] The control unit 210 can also control the generation, mapping, etc. of signals. The control unit 210 can also control the transmission and reception, measurement, etc. using the transmission and reception unit 220 and the transmission and reception antenna 230. The control unit 210 can also generate data, control information, sequences, etc. to be transmitted as signals and forward them to the transmission and reception unit 220.

[0258] The transmission and reception unit 220 can also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 can also include a transmission processing unit 2211 and a reception processing unit 2212. The transmission and reception unit 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission and reception circuit, etc. described based on common knowledge in the technical field related to the present disclosure.

[0259] The transmission and reception unit 220 can be configured as an integrated transmission and reception unit or can be composed of a transmission unit and a reception unit. The transmission unit can also be composed of the transmission processing unit 2211 and the RF unit 222. The reception unit can also be composed of the reception processing unit 2212, the RF unit 222, and the measurement unit 223.

[0260] The transmission and reception antenna 230 can be composed of an antenna described based on common knowledge in the technical field related to the present disclosure, such as an array antenna.

[0261] The transmission and reception unit 220 can also transmit the above-mentioned downlink channels, synchronization signals, downlink reference signals, etc. The transmission and reception unit 220 can also receive the above-mentioned uplink channels, uplink reference signals, etc.

[0262] The transmission and reception unit 220 can also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc. to form at least one of a transmission beam and a reception beam.

[0263] The transmission and reception unit 220 (transmission processing unit 2211) can, for example, also perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on the data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0264] The transmission and reception unit 220 (transmission processing unit 2211) can also perform transmission processing such as channel coding (which can include error correction coding), modulation, mapping, filter processing, DFT processing (if necessary), IFFT processing, precoding, digital-to-analog conversion, etc. on the bit string to be transmitted and output a baseband signal.

[0265] In addition, regarding whether to apply DFT processing, it can also be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when the transform precoding is activated (enabled), the transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform DFT processing as the above-mentioned transmitting processing in order to transmit the channel using the DFT-s-OFDM waveform. In other cases, the transmitting and receiving unit 220 (transmitting processing unit 2211) can also not perform DFT processing as the above-mentioned transmitting processing.

[0266] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation to the radio frequency band, filter processing, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmitting and receiving antenna 230.

[0267] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also perform amplification, filter processing, demodulation to the baseband signal, etc. on the radio frequency band signal received through the transmitting and receiving antenna 230.

[0268] The transmitting and receiving unit 220 (receiving processing unit 2212) can also perform receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, etc. on the obtained baseband signal to obtain user data, etc.

[0269] The transmitting and receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 can also measure the received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 210.

[0270] In addition, the transmitting unit and receiving unit of the user terminal 20 in the present disclosure can also be constituted by at least one of the transmitting and receiving unit 220, the transmitting and receiving antenna 230, and the transmission path interface 240.

[0271] In addition, the transmitting and receiving unit 220 can also receive, commonly or dedicatedly for multiple service types, information (RBG size information) indicating the setting used in the determination of the size of the resource block group (RBG) for allocating frequency domain resources of the downlink shared channel or the uplink shared channel.

[0272] The transmitting and receiving unit 220 may also receive downlink control information. In addition, the transmitting and receiving unit 220 may also receive a downlink shared channel. The downlink control information may also scramble cyclic redundancy check (CRC) bits by using a radio network temporary identifier (RNTI) common to one or more terminals.

[0273] The transmitting and receiving unit 220 may also receive the RNTI for each type of multicast service.

[0274] When the user terminal 20 is in at least one of an idle state, an inactive state, and a connected state, the transmitting and receiving unit 220 may also receive information for receiving the data (e.g., the above-mentioned MTCH setting information, multicast setting information) by using a physical downlink shared channel associated with a multicast control channel (MCCH).

[0275] When the user terminal 20 is in at least one of an idle state, an inactive state, and a connected state, the transmitting and receiving unit 220 may also receive information for receiving the data (e.g., the above-mentioned MTCH setting information, multicast setting information) by using system information for multicast.

[0276] When the user terminal 20 is in a connected state, the transmitting and receiving unit 220 may also receive information for receiving the data (e.g., the above-mentioned MTCH setting information, multicast setting information) by using radio resource control (RRC) signaling.

[0277] The control unit 210 may also control receiving data associated with a multicast traffic channel (MTCH) by using a physical downlink shared channel scheduled by the downlink control information within one or more bandwidth parts in a cell.

[0278] The control unit 210 may also control the reception of the downlink control information.

[0279] (Hardware Structure)

[0280] In addition, the block diagrams used in the description of the above embodiments illustrate blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block may be implemented by a physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (e.g., by wire, wireless, etc.) connected and implemented by these multiple devices. The functional block may also be implemented by combining the above-mentioned one device or the above-mentioned multiple devices with software.

[0281] Here, in terms of functions, there are judgment, decision-making, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, establishment, comparison, assumption, expectation, regarded as, broadcasting, notifying, communicating, forwarding, configuration (setting), reconfiguration (re - setting), allocation (allocating, mapping), assignment, etc., but are not limited to these. For example, a functional block (structural unit) that implements the transmission function may also be referred to as a transmitting unit, a transmitter, etc. Any of them is as described above, and the implementation method is not particularly limited.

[0282] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure can also function as a computer that performs the processing of the wireless communication method of the present disclosure. Figure 11 FIG. is an example showing the hardware structure of a base station and a user terminal according to an embodiment. The above - mentioned base station 10 and user terminal 20 can also 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.

[0283] In addition, in the present disclosure, terms such as device, circuit, equipment, section, unit, etc. can be mutually replaced. The hardware structure of the base station 10 and the user terminal 20 can be configured to include one or more of each device shown in the figure, or can be configured not to include some devices.

[0284] For example, only one processor 1001 is shown in the figure, but there can be multiple processors. In addition, the processing can be executed by one processor, or can be executed simultaneously, sequentially, or by other means by two or more processors. In addition, the processor 1001 can also be implemented by one or more chips.

[0285] Regarding each function in the base station 10 and the user terminal 20, for example, by reading a specific software (program) into hardware such as the processor 1001 and the memory 1002, the processor 1001 performs operations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003, thereby realizing the function.

[0286] The processor 1001, for example, operates the operating system to control the entire computer. The processor 1001 may also be constituted by a central processing unit (Central Processing Unit (CPU)) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like. For example, at least a part of the above control unit 110 (210), transmission / reception unit 120 (220), etc. may also be implemented by the processor 1001.

[0287] In addition, the processor 1001 reads a program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes based on them. As the program, a program that causes the computer to execute at least a part of the operations described in the above embodiments can be used. For example, the control unit 110 (210) may also be implemented by a control program stored in the memory 1002 and operating in the processor 1001, and the same can be applied to other functional blocks.

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

[0289] The storage 1003 may also be a computer-readable recording medium, and may be constituted by at least one of, for example, a flexible disc, a floppy (registered trademark) disc, an optical disc (such as a compact disc (Compact Disc ROM (CD-ROM)), etc.), a digital versatile disc, a Blu-ray (registered trademark) disc, a removable disc, a hard disk drive, a smart card, a flash device (such as a card, a stick, a key drive), a magnetic stripe, a database, a server, and other appropriate storage media. The storage 1003 may also be referred to as an auxiliary storage device.

[0290] The communication device 1004 is hardware (a transmitting and receiving device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. In order to implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may also be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the above-described transmitting and receiving unit 120 (220), the transmitting and receiving antenna 130 (230), etc. may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be physically or logically separated and installed by a transmitting unit 120a (220a) and a receiving unit 120b (220b).

[0291] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs an output to the outside. In addition, the input device 1005 and the output device 1006 may also have an integrated structure (e.g., a touch panel).

[0292] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured by a single bus or may be configured by different buses between each device.

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

[0294] (Modification example)

[0295] In addition, terms described in this disclosure and terms required for understanding this disclosure may also be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may also be replaced with each other. In addition, a signal may also be a message. A reference signal can also be abbreviated as RS and can also be referred to as a pilot, a pilot signal, etc. according to the applied standard. In addition, a component carrier (Component Carrier (CC)) may also be referred to as a cell, a frequency carrier, a carrier frequency, etc.

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

[0297] Here, the numerology may also refer to communication parameters applied in at least one of the transmission and reception of a certain signal or channel. For example, the numerology may also represent at least one of a subcarrier spacing (SubCarrier Spacing (SCS)), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (Transmission Time Interval (TTI)), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transmitter-receiver in the frequency domain, a specific windowing process performed by a transmitter-receiver in the time domain, etc.

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

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

[0300] A radio frame, subframe, time slot, mini time slot, and symbol all represent time units for transmitting signals. A radio frame, subframe, time slot, mini time slot, and symbol may also use other corresponding names. In addition, time units such as frames, subframes, time slots, mini time slots, and symbols in the present disclosure may also be replaced with each other.

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

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

[0303] A TTI may also be a transmission time unit for a data packet (transport block), code block, codeword, etc. that has undergone channel coding, and may also become a processing unit for scheduling, link adaptation, etc. In addition, when a TTI is given, the time interval (e.g., number of symbols) in which a transport block, code block, codeword, etc. is actually mapped may also be shorter than the TTI.

[0304] In addition, in the case where a time slot or a mini time slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini time slots) may also become the minimum time unit for scheduling. In addition, the number of time slots (mini time slot numbers) constituting the minimum time unit of this scheduling may also be controlled.

[0305] A TTI having a time length of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel.8 - 12), standard TTI, long TTI, normal subframe, standard subframe, long subframe, time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini time slot, sub - time slot, time slot, etc.

[0306] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be replaced with a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be replaced with a TTI having a TTI length less than that of the long TTI and more than 1 ms.

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

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

[0309] In addition, one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0311] A bandwidth part (BWP) (which may also be referred to as a partial bandwidth, etc.) may also represent a subset of consecutive common RBs (common resource blocks) used for a certain parameter set in a certain carrier. Here, the common RBs may also be determined by the index of the RBs based on the common reference point of the carrier. A PRB may also be defined in a certain BWP and be additionally numbered within that BWP.

[0312] A UL BWP (BWP for UL) and a DL BWP (BWP for DL) may also be included in a BWP. For a UE, one or more BWPs may also be set within one carrier.

[0313] At least one of the set BWPs may be active, and the UE may not assume to transmit and receive specific signals / channels outside the active BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be replaced with "BWP".

[0314] In addition, structures such as the above-mentioned radio frames, subframes, time slots, mini time slots, and symbols are merely illustrative. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini time slots included in a time slot, the number of symbols and RBs included in a time slot or mini time slot, the number of subcarriers included in an RB, and the number of symbols, symbol length, Cyclic Prefix (CP) length, etc. within a TTI can be changed in various ways.

[0315] Furthermore, the information, parameters, etc. described in this disclosure can be represented by absolute values, relative values with respect to a specific value, or can also be represented by corresponding other information. For example, radio resources can also be indicated by a specific index.

[0316] In this disclosure, the names used for parameters, etc. are not restrictive names in all aspects. In addition, mathematical expressions using these parameters, etc. can also be different from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name. Therefore, the various names assigned to these various channels and information elements are not restrictive names in all aspects.

[0317] The information, signals, etc. described in this disclosure can also be represented using any one of various different technologies. For example, data, indications, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0318] In addition, information, signals, etc. can be output to at least one of the higher layer (upper layer) to the lower layer (lower layer) and from the lower layer to the higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

[0319] The input and output information, signals, etc. can be stored in a specific location (such as a memory), or can be managed using a management table. The input and output information, signals, etc. can be overwritten, updated, or appended. The output information, signals, etc. can also be deleted. The input information, signals, etc. can also be sent to other devices.

[0320] The notification of information is not limited to the manners / embodiments described in this disclosure, and other methods can also be used. For example, the notification of information in this disclosure can also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), high 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.

[0321] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. In addition, RRC signaling can also be referred to as an RRC message, and for example, it can also be an RRC Connection Setup message, an RRC Connection Reconfiguration (RRC Connection Re - setting) message, etc. In addition, MAC signaling can be notified, for example, by using a MAC Control Element (MAC CE).

[0322] In addition, the notification of specific information (e.g., the notification of "is X") is not limited to explicit notification, and can also be performed implicitly (e.g., by not performing the notification of the specific information, or by the notification of other information).

[0323] The determination can be made by a value represented by one bit (0 or 1), can also be made by a true - false value (Boolean value) represented by true or false, and can also be made by a numerical comparison (e.g., comparison with a specific value).

[0324] Software, whether referred to as software, firmware, middleware, micro-code, hardware description language, or by any other name, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, sub-programs, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, threads of execution, procedures, functions, and the like.

[0325] In addition, software, instructions, information, etc. can also be sent and received via a transmission medium. For example, in the case of sending software from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included in the definition of the transmission medium.

[0326] Terms such as "system" and "network" used in this disclosure can be used interchangeably. "Network" can also mean a device (e.g., a base station) included in the network.

[0327] In this disclosure, terms such as "precoding", "precoder", "weights (precoding weights)", "Quasi-Co-Location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel", etc. can be used interchangeably.

[0328] In the present disclosure, terms such as "Base Station (BS)", "radio 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" can be used interchangeably. There are also cases where base stations are referred to by terms such as macro cell, small cell, femto cell, pico cell, etc.

[0329] A base station can accommodate one or more (e.g., three) cells. In the case where a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each of the smaller areas can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services within that coverage range.

[0330] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "user terminal" can be used interchangeably.

[0331] In some cases, the mobile station is also referred to as a subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access user terminal, mobile user terminal, wireless user terminal, remote user terminal, hand set, user agent, mobile client, client, or several other appropriate terms.

[0332] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station may also be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), may also be a moving body that moves in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), and may also be a robot (humanoid or non-humanoid). Additionally, at least one of the base station and the mobile station also includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may also be an Internet of Things (IoT) device such as a sensor.

[0333] Furthermore, the base station in the present disclosure may also be replaced by a user terminal. For example, for a structure in which communication between a base station and a user terminal is replaced by communication between multiple user terminals (e.g., may also be referred to as Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), the various aspects / embodiments of the present disclosure may also be applied. In this case, it may also be configured such that the user terminal 20 has the functions of the above-mentioned base station 10. Additionally, expressions such as "uplink" and "downlink" may also be replaced by expressions corresponding to communication between user terminals (e.g., "side"). For example, an uplink channel, a downlink channel, etc. may also be replaced by a side channel.

[0334] Similarly, the user terminal in the present disclosure may also be replaced by a base station. In this case, it may also be configured such that the base station 10 has the functions of the above-mentioned user terminal 20.

[0335] In the present disclosure, an action performed by the base station may sometimes be performed by its upper node according to circumstances. Apparently, in a network including one or more network nodes having a base station, various actions performed for communication with a user terminal may be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0336] Each mode / embodiment described in the present disclosure can be used alone, in combination, or switched during execution. In addition, the processing procedures, sequences, flowcharts, etc. of each mode / embodiment described in the present disclosure can also be reordered as long as there is no contradiction. For example, for the methods described in the present disclosure, elements of various steps are presented in the illustrated order, but are not limited to the specific order presented.

[0337] Each mode / embodiment described in the present disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, the fourth generation mobile communication system (4G), the fifth 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), systems using other appropriate wireless communication methods, next-generation systems extended based on them, etc. In addition, multiple systems can also be combined (for example, a combination of LTE or LTE-A and 5G) for application.

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

[0339] Any reference to an element using terms such as "first", "second", etc. used in this disclosure does not comprehensively define the quantity or order of these elements. These terms can be used in this disclosure as a convenient method for distinguishing between more than two elements. Therefore, the reference to the first and second elements does not mean that only two elements can be adopted, or that the first element must be prior to the second element in a certain form.

[0340] The term "determining" used in this disclosure includes various actions in some cases. For example, "determining" can also consider judging, calculating, computing, processing, deriving, investigating, looking up (searching, inquiring) (such as searching in a table, database, or other data structure), ascertaining, etc. as cases of performing "determining".

[0341] In addition, "determining" can also consider receiving (for example, receiving information), transmitting (for example, transmitting information), input, output, accessing (for example, accessing data in a memory), etc. as cases of performing "determining".

[0342] In addition, "determining" can also consider resolving, selecting, choosing, establishing, comparing, etc. as cases of performing "determining". That is to say, "determining" can also consider some actions as cases of performing "determining".

[0343] In addition, "determining" can also be replaced by "assuming", "expecting", "considering", etc.

[0344] The "maximum transmit power" described in this disclosure may mean the maximum value of the transmit power, or may refer to the nominal maximum transmit power (the nominal UE maximum transmit power), or may refer to the rated maximum transmit power (the rated UE maximum transmit power).

[0345] Terms such as "connected" and "coupled" used in this disclosure, or all their variants, mean all direct or indirect connections or couplings between two or more elements, and can include the case where there is one or more intermediate elements between the two elements that are "connected" or "coupled" to each other. The coupling or connection between elements can be physical, logical, or a combination of these. For example, "connected" can also be replaced by "access".

[0346] In this disclosure, when connecting two elements, it can be considered that one or more wires, cables, printed electrical connections, etc. are used, and electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and optical (both visible and invisible) regions, etc., are used as several non-limiting and non-exhaustive examples to "connect" or "couple" to each other.

[0347] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other". In addition, this term can also mean "A and B are respectively different from C". Terms such as "separated" and "coupled" can also be interpreted as "different" in the same way.

[0348] In this disclosure, when using "include", "including", and their variants, these terms, like the term "comprising", are of an inclusive meaning. Further, the term "or" used in this disclosure does not mean the exclusive or meaning.

[0349] In this disclosure, for example, in the case where articles are added through translation such as a, an, and the in English, this disclosure can also include the case where the nouns following these articles are in the plural form.

[0350] As described above, the invention related to the present disclosure has been described in detail. However, for those skilled in the art, the invention related to the present disclosure is obviously not limited to the embodiments described in the present disclosure. The invention related to the present disclosure can be implemented in the form of amendments and changes without departing from the gist and scope of the present invention determined based on the description in the claims. Therefore, the description of the present disclosure is for the purpose of illustration and does not carry any restrictive meaning for the invention related to the present disclosure.

Claims

1. A terminal, comprising: a receiving unit that receives downlink control information in which cyclic redundancy check (CRC) bits are scrambled using a radio network temporary identifier (RNTI) common to one or more terminals; and a control unit that controls the receiving unit to receive data associated with a multicast traffic channel (MTCH) in a first physical downlink shared channel (PDSCH) scheduled by the downlink control information within one or more bandwidth parts in a cell, wherein, when the terminal is in an idle state or a connected state, the receiving unit receives first information for receiving the data using a second physical downlink shared channel (PDSCH) associated with a multicast control channel (MCCH), and the first information for receiving the data includes settings related to the first PDSCH for the MTCH, and when the terminal is in an inactive state, the receiving unit receives second information for receiving the data using system information, and the second information for receiving the data includes information indicating a control resource set (CORESET) for a physical downlink control channel (PDCCH) that schedules the first PDSCH for the MTCH.

2. The terminal according to claim 1, wherein a quasi-co-location (QCL) relationship used for receiving the second PDSCH associated with the MCCH is determined based on information transmitted through system information.

3. A wireless communication method, which is a wireless communication method of a terminal, comprising: a step of receiving downlink control information in which CRC bits are scrambled using an RNTI common to one or more terminals; a step of receiving data associated with an MTCH in a first PDSCH scheduled by the downlink control information within one or more bandwidth parts in a cell; when the terminal is in an idle state or a connected state, a step of receiving first information for receiving the data using a second PDSCH associated with an MCCH, wherein the first information for receiving the data includes settings related to the first PDSCH for the MTCH; and when the terminal is in an inactive state, a step of receiving second information for receiving the data using system information, wherein the second information for receiving the data includes information indicating a CORESET for a PDCCH that schedules the first PDSCH for the MTCH.

4. A base station, comprising: a transmitting unit that transmits downlink control information in which CRC bits are scrambled using an RNTI common to one or more terminals; and A control unit controls the transmission unit to transmit data associated with a multicast traffic channel (MTCH) in a first physical downlink shared channel (PDSCH) scheduled by the downlink control information in more than one bandwidth part within a cell. When the terminal is in an idle state or a connected state, the transmission unit uses a second PDSCH associated with a multicast control channel (MCCH) to transmit first information for receiving the data. The first information for receiving the data includes settings related to the first PDSCH for the MTCH. When the terminal is in an inactive state, the transmission unit uses system information to transmit second information for receiving the data. The second information for receiving the data includes information indicating a control resource set (CORESET) for a physical downlink control channel (PDCCH) that schedules the first PDSCH for the MTCH.

5. A system having a terminal and a base station The terminal has: A receiving unit that receives downlink control information scrambled with a cyclic redundancy check (CRC) bit using a radio network temporary identifier (RNTI) common to more than one terminal; and A control unit controls the receiving unit to receive data associated with a multicast traffic channel (MTCH) in a first physical downlink shared channel (PDSCH) scheduled by the downlink control information in more than one bandwidth part within a cell. When the terminal is in an idle state or a connected state, the receiving unit uses a second PDSCH associated with a multicast control channel (MCCH) to receive first information for receiving the data. The first information for receiving the data includes settings related to the first PDSCH for the MTCH. When the terminal is in an inactive state, the receiving unit uses system information to receive second information for receiving the data. The second information for receiving the data includes information indicating a control resource set (CORESET) for a physical downlink control channel (PDCCH) that schedules the first PDSCH for the MTCH. The base station has: A transmission unit that transmits the downlink control information.

Citation Information

Patent Citations

  • Method and apparatus for deciding numerology in a wireless communication system

    US20180192255A1

  • Method and apparatus for sending and receiving multicast service and dedicated service

    WO2017049544A1

  • Multicast-based wireless communication method, terminal device and base station

    WO2018028038A1