Terminal, base station, wireless communication system, and wireless communication method

Abstract

This terminal comprises: a reception unit that, in the distribution of data to a plurality of terminals, receives data via a downlink channel scheduled by shared downlink control information which is shared among the plurality of terminals; and a control unit that, on the basis of a shared upper layer parameter used in the shared downlink information, determines the size of at least one first field, among the fields included in the shared downlink control information. The shared upper layer parameter is defined separately from a unique upper layer parameter used in unique downlink information which is unique to each of the plurality of terminals.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal and a wireless communication method that support multicast / broadcast services. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release 17 targets simultaneous data transmission (which may also be called distribution) services (provisional name: MBS: Multicast and Broadcast Services) in NR to multiple specified or unspecified terminals (User Equipment, UE) (Non-Patent Document 1).

[0004] MBS supports a scheme (hereinafter referred to as PTM-1) in which a group-common PDSCH is scheduled using a group-common PDCCH (Physical Downlink Control Channel) that is common to a group of multiple UEs that receive data related to the MBS. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "New Work Item on NR support of Multicast and Broadcast Services", RP-193248, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 Summary of the Invention

[0006] Against this background, the inventors have conducted extensive research and found that in PTM-1, unless the size of a field included in downlink control information (DCI) transmitted by a group-common PDCCH is known to multiple UEs receiving MBS data, the UEs will not be able to properly decode the DCI transmitted by the group-common PDCCH.

[0007] Therefore, the present disclosure has been made in consideration of such circumstances, and aims to provide a terminal and a wireless communication method that can appropriately decode DCI used in scheduling data related to MBS.

[0008] One aspect of the disclosure is a terminal that, in data distribution to a plurality of terminals, comprises: a receiving unit that receives data via a downlink channel scheduled by common downlink control information common to the plurality of terminals; and a control unit that determines the size of at least one first field among the fields included in the common downlink control information based on common upper layer parameters used in the common downlink control information, wherein the common upper layer parameters are defined separately from specific upper layer parameters used in specific downlink information that is specific to each of the plurality of terminals.

[0009] One aspect of the disclosure is a wireless communication method comprising the steps of: receiving data via a downlink channel scheduled by common downlink control information common to a plurality of terminals in data distribution to the plurality of terminals; and determining a size of at least one first field among fields included in the downlink control information common to the plurality of terminals based on a common upper layer parameter used in the common downlink information, wherein the common upper layer parameter is defined separately from a specific upper layer parameter used in specific downlink information specific to each of the plurality of terminals. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 4] FIG. 4 is a functional block diagram of the UE 200. [Figure 5] Figure 5 is a functional block diagram of gNB100. [Figure 6] FIG. 6 is a diagram showing an example of the configuration of PTM transmission method 1 and PTM transmission method 2. In FIG. [Figure 7] FIG. 7 is a diagram for explaining upper layer parameters. [Figure 8] FIG. 8 is a diagram for explaining upper layer parameters. [Figure 9] FIG. 9 is a diagram illustrating the DCI field. [Figure 10] FIG. 10 is a diagram illustrating the DCI field. [Figure 11] FIG. 11 is a diagram for explaining the number of BWPs / Serving Cells. [Figure 12] FIG. 12 is a diagram showing an example of the hardware configuration of gNB100 and UE200. [Figure 13] FIG. 13 is a diagram showing an example of the configuration of a vehicle 2001. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0012] [Embodiment] (1) Overall configuration of wireless communication system 1 is a schematic diagram of the overall configuration of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE (User Equipment) 200).

[0013] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0014] The NG-RAN 20 includes a base station 100 (hereinafter, gNB 100). Note that the specific configuration of the wireless communication system 10, including the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG.

[0015] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may be simply referred to as a "network."

[0016] The gNB 100 is a radio base station conforming to 5G, and performs 5G radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates on two or more transport blocks between the UE and each of two NG-RAN nodes.

[0017] The wireless communication system 10 also supports a plurality of frequency ranges (FR).

[0018] 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows:

[0019] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz~52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz) and a bandwidth (BW) of 50 to 400 MHz.

[0020] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0021] Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands above 52.6 GHz up to 71 GHz or 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x."

[0022] To solve the problem of increased phase noise in high frequency bands, when using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.

[0023] FIG. 3 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. In FIG.

[0024] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used.

[0025] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0026] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, or a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0027] DMRS is a type of reference signal and is prepared for various channels. Here, unless otherwise specified, it may refer to a downlink data channel, specifically, a DMRS for a PDSCH (Physical Downlink Shared Channel). However, a DMRS for an uplink data channel, specifically, a PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as a DMRS for a PDSCH.

[0028] The DMRS may be used for channel estimation at the device, for example, as part of coherent demodulation at the UE 200. The DMRS may only be present in resource blocks (RBs) used for PDSCH transmission.

[0029] A DMRS may have multiple mapping types. Specifically, a DMRS has mapping type A and mapping type B. In mapping type A, the first DMRS is placed in the second or third symbol of a slot. In mapping type A, the DMRS may be mapped based on the slot boundary, regardless of where in the slot actual data transmission starts. The reason why the first DMRS is placed in the second or third symbol of a slot may be interpreted as being to place the first DMRS after a control resource set (CORESET).

[0030] In mapping type B, the first DMRS may be placed in the first symbol of the data allocation, i.e., the position of the DMRS may be given relative to where the data is placed, rather than relative to the slot boundary.

[0031] Furthermore, DMRS may have multiple types. Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

[0032] (2) Functional block configuration of wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.

[0033] First, the functional block configuration of the UE 200 will be described.

[0034] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.

[0035] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0036] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0037] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0038] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0039] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0040] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0041] DMRS is a reference signal (pilot signal) known between the base station and the terminal for estimating the fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0042] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0043] The channels include control channels and data channels, such as a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

[0044] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.

[0045] Here, the control signal and reference signal processor 240 may receive downlink control information (DCI). The DCI includes existing fields for storing DCI Formats, Carrier indicator (CI), BWP indicator, Frequency Domain Resource Assignment (FDRA), Time Domain Resource Assignment (TDRA), Modulation and Coding Scheme (MCS), HARQ Process Number (HPN), New Data Indicator (NDI), Redundancy Version (RV), etc.

[0046] The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by an RRC message or may be determined by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI field is an information element for specifying whether the data to which the DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

[0047] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0048] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0049] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on HARQ (Hybrid Automatic Repeat Request).

[0050] In the embodiment, the data transmitter / receiver 260 constitutes a receiver that receives data via a downlink channel in data distribution to multiple terminals (hereinafter, UEs 200). Data distribution to multiple terminals may be referred to as MBS (Multicast and Broadcast Services). The downlink channel may include a PDSCH (multicast) transmitted by multicast, or a PDSCH (unicast) transmitted by unicast. Hereinafter, PDSCH (multicast) and PDSCH (unicast) are collectively referred to as PDSCH (multicast / unicast). Reception of PDSCH (multicast / unicast) may be interpreted as reception of data via PDSCH (multicast / unicast). Specifically, in MBS, the data transmitter / receiver 260 receives data via a downlink channel (hereinafter, PDSCH) scheduled by common downlink control information (hereinafter, common DCI) common to multiple terminals. The common DCI may be referred to as DCI for MBS.

[0051] The control unit 270 controls each functional block constituting the UE 200. In the embodiment, the control unit 270 configures a control unit that determines the size of at least one first field among the fields included in the common DCI, based on a common upper layer parameter used in the common DCI. The common upper layer parameter is defined separately from a specific upper layer parameter used in downlink information specific to each of the multiple UEs 200 (hereinafter, specific DCI). The specific DCI may be referred to as a UE-dedicated DCI.

[0052] Here, the common DCI is DCI carried by a Group-common PDCCH in PTM-1, which will be described later. The Group-common PDCCH is a PDCCH common to two or more UEs 200 receiving data in an MBS, and the CRC of the Group-common PDCCH is scrambled by the G-RNTI. The common DCI may be considered as DCI scrambled by the G-RNTI. On the other hand, the specific DCI is DCI carried by a UE-specific PDCCH that is specific to a UE 200. The UE-specific PDCCH may be used in PTM-2, which will be described later. The CRC of the UE-specific PDCCH is scrambled by the UE-specific RNTI. The UE-specific RNTI may include a C (Cell)-RNTI, a CS (Configured Scheduling)-RNTI, or an MCS (Modulcation Coding Scheme)-C-RNTI. The common DCI may be considered as a DCI that is scrambled by a UE-specific RNTI.

[0053] Secondly, we will explain the functional block configuration of gNB100.

[0054] Fig. 5 is a functional block diagram of the gNB 100. As shown in Fig. 5, the gNB 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0055] The receiver 110 receives various signals from the UE 200. The receiver 110 may receive an UL signal via a PUCCH or a PUSCH. In an embodiment, the receiver 110 may receive the feedback described above.

[0056] The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit a DL signal via a PDCCH or a PDSCH. In the embodiment, the transmitter 120 may transmit a PDSCH (multicast / unicast) in an MBS. Transmission of a PDSCH (multicast / unicast) may be interpreted as transmission of data via a PDSCH (multicast / unicast).

[0057] The control unit 130 controls the gNB 100. In an embodiment, the control unit 130 may assume that the UE 200 determines the size of at least one first field among the fields included in the common DCI based on a common upper layer parameter used in the common DCI.

[0058] (3) Provision of MBS The wireless communication system 10 may provide multicast and broadcast services (MBS).

[0059] For example, in a stadium or a hall, it is assumed that a large number of UEs 200 are located within a certain geographical area and receive the same data simultaneously. In such a case, it is effective to use MBS instead of unicast.

[0060] Note that unicast may be interpreted as one-to-one communication with the network, in which a specific UE 200 is designated (identification information unique to the UE 200 may be designated).

[0061] Multicast may be interpreted as one-to-many (specified many) communication with a network, specifying a specific number of UEs 200 (identification information for multicast may be specified). Note that the number of UEs 200 receiving the received multicast data may ultimately be one.

[0062] Broadcasting may be interpreted as one-to-one communication between the network and all UEs 200. The multicast / broadcast data may be identical copies of the data, but some parts of the data, such as the header, may be different. The multicast / broadcast data may be transmitted (distributed) simultaneously, but strict simultaneity is not necessarily required, and propagation delays and / or processing delays within the RAN node may be included.

[0063] The target UE 200 may be in a radio resource control (RRC) layer state of an idle state (RRC idle), a connected state (RRC connected), or another state (e.g., an inactive state). The inactive state may be interpreted as a state in which some RRC settings are maintained.

[0064] In MBS, the following three methods are assumed for scheduling multicast / broadcast PDSCH, specifically, scheduling MBS packets (which may be read as data): Note that RRC connected UE may also be read as RRC idle UE or RRC inactive UE.

[0065] ·PTM transmission method 1 (PTM-1): Schedules group-common PDSCH using group-common PDCCH (Physical Downlink Control Channel) for MBS groups of RRC connected UEs. The CRC of the PDCCH and the PDSCH are scrambled by the group-common RNTI (also known as the Radio Network Temporary Identifier, G-RNTI). ·PTM transmission method 2 (PTM-2): Schedules group-common PDSCH using UE-specific PDCCH for MBS group of RRC connected UE The PDCCH CRC is scrambled by the UE-specific RNTI PDSCH is scrambled by the group-common RNTI ·PTP transmission method: Schedules UE-specific PDSCH using UE-specific PDCCH for RRC connected UE The CRC of the PDCCH and the PDSCH are scrambled by a UE-specific RNTI, which means that the MBS packet is transmitted by unicast. Fig. 6 shows configuration examples of PTM transmission method 1 and PTM transmission method 2. Note that the UE-specific PDCCH / PDSCH can be identified by the target UE, but does not need to be identified by other UEs in the same MBS group. The group-common PDCCH / PDSCH is transmitted in the same time / frequency resource and can be identified by all UEs in the same MBS group. The names of PTM transmission methods 1 and 2 are tentative, and they may be called by different names as long as the above-mentioned operations are performed.

[0066] Note that in point-to-point (PTP) delivery, the RAN node may deliver individual copies of the MBS data packet over the air to individual UEs, and in point-to-multipoint (PTM) delivery, the RAN node may deliver a single copy of the MBS data packet over the air to a set of UEs.

[0067] Furthermore, in order to improve the reliability of MBS, the following two feedback methods are envisaged for HARQ (Hybrid Automatic repeat request) feedback, specifically, HARQ feedback for multicast / broadcast PDSCH.

[0068] Option 1: Feedback both ACK and NACK (ACK / NACK feedback) UE that successfully receives and decodes PDSCH sends ACK · UEs that fail to receive and decode PDSCH send NACK PUCCH (Physical Uplink Control Channel) resource configuration: PUCCH-Config can be configured for multicast. PUCCH resources: shared / orthogonal between UEs, depending on network configuration HARQ-ACK CB (codebook): Supports type-1 and type-2 (CB decision algorithm (specified in 3GPP TS38.213)) Multiplexing: Unicast or multicast can be applied Option 2: NACK-only feedback · UE that successfully receives and decodes PDSCH does not send ACK (does not send a response) · UEs that fail to receive and decode PDSCH send NACK For a given UE, PUCCH resource configuration can be configured separately via unicast or groupcast (multicast) Note that ACK may be called a positive acknowledgement, and NACK may be called a negative acknowledgement. HARQ may be called an automatic repeat request.

[0069] To enable or disable option 1 or option 2, one of the following may be applied:

[0070] RRC and Downlink Control Information (DCI) RRC only Furthermore, the following is assumed for SPS (Semi-persistent Scheduling) of multicast / broadcast PDSCH.

[0071] ·SPS group-common PDSCH adopted Multiple SPS group-common PDSCHs can be configured as UE capabilities. HARQ feedback for SPS group-common PDSCH is possible Activation / deactivation is possible via at least the group-common PDCCH (downlink control channel) Note that deactivation may be interpreted as another synonymous term such as release. For example, activation may be interpreted as start, start, trigger, etc., and deactivation may be interpreted as end, stop, etc.

[0072] SPS is a scheduling method used in contrast to dynamic scheduling, and may also be called semi-fixed, semi-persistent, or semi-persistent scheduling, and may also be interpreted as Configured Scheduling (CS).

[0073] Scheduling may be interpreted as a process of allocating resources for transmitting data. Dynamic scheduling may be interpreted as a mechanism in which all PDSCHs are scheduled by DCI (e.g., DCI 1_0, DCI 1_1, or DCI 1_2). SPS may be interpreted as a mechanism in which PDSCH transmissions are scheduled by higher layer signaling, such as RRC messages.

[0074] Also, for the physical layer, there may be scheduling categories of time domain scheduling and frequency domain scheduling.

[0075] Furthermore, multicast, groupcast, broadcast, and MBS may be interchangeable. Multicast PDSCH and PDSCH scrambled with a group-common RNTI may be interchangeable.

[0076] Furthermore, the terms data and packet may be read interchangeably and may be interpreted as synonymous with terms such as signal, data unit, etc. Also, send, receive, transmit, and deliver may be read interchangeably.

[0077] (4) Issues In the embodiment, attention is focused on the above-mentioned PTM-1. In PTM-1, the Group-common PDCCH (common DCI) is scrambled by the G-RNTI. Therefore, if the size of a field included in the common DCI differs for each UE 200, each UE 200 cannot properly decode the common DCI. In other words, the size of a field included in the common DCI needs to be known to two or more UEs 200 receiving data in the MBS.

[0078] In consideration of such a problem, in the embodiment, common upper layer parameters used in common DCI common to a plurality of UEs 200 are defined separately from specific upper layer parameters used in specific DCI specific to each of the plurality of UEs 200.

[0079] (5) Upper layer parameters An example of the higher layer parameter will be described below. The higher layer parameter may be an RRC parameter set by an RRC message. Here, a Time Domain Resource Assignment (TDRA) field is exemplified as a field included in DCI. The higher layer parameter used in the TDRA field may be pdsch-TimeDomainAllocationList.

[0080] First, a description will be given of specific upper layer parameters used in a specific DCI specific to each of the multiple UEs 200. As shown in Fig. 7, the second higher layer parameter may be a pdsch-TimeDomainAllocationList included in pdsch-Config. The TDRA field of the specific DCI stores a value specifying a row index included in pdsch-TimeDomainAllocationList. That is, the size of the TDRA field of the specific DCI is determined by the pdsch-TimeDomainAllocationList included in pdsch-Config.

[0081] Second, a common upper layer parameter used in a common DCI common to a plurality of UEs 200 will be described. As shown in FIG. 8, the first upper layer parameter may be pdsch-TimeDomainAllocationList included in pdsch-Config-Multicast. The TDRA field of the common DCI stores a value specifying a row index included in pdsch-TimeDomainAllocationList. That is, the size of the TDRA field of the common DCI is determined by pdsch-TimeDomainAllocationList included in pdsch-Config-Multicast. Note that the name pdsch-Config-Multicast is an example and is not limited to this. It may also be set as an RRC parameter related to MBS, such as xx-Multicast or xx-Mbs (where xx is, for example, pdsch-Config or CFR-Config). In the following description, it is assumed that an RRC parameter named xx-Multicast is specified in Rel. 17, but the name of the RRC parameter (the name of "xx" or the name of "-Multicast") is not limited to the example in this specification. The xx-Multicast described in this specification may be read as an RRC parameter set in relation to an MBS (or set for an MBS).

[0082] As described above, the TDRA field of a specific DCI is determined by the pdsch-TimeDomainAllocationList included in pdsch-Config, and the size of the TDRA field of a common DCI is determined by the pdsch-TimeDomainAllocationList included in pdsch-Config-Multicast. In the embodiment, the same name (pdsch-TimeDomainAllocationList) is used as the name of the information element that determines the size of the TDRA field, but the information element that includes pdsch-TimeDomainAllocationList is different between the common upper layer parameters used in the common DCI and the specific upper layer parameters used in the specific DCI. In other words, the common upper layer parameters (pdsch-TimeDomainAllocationList included in pdsch-Config-Multicast) are defined separately from the specific upper layer parameters (pdsch-TimeDomainAllocationList included in pdsch-Config).

[0083] (6) DCI Field In the following, the fields of the common DCI will be described using DCI format 1_1 as an example. The common DCI may be DCI format 1_0 or DCI format 1_2. In such a case, the common DCI having DCI format 1_0 may be referred to as the first DCI, the common DCI having DCI format 1_1 may be referred to as the second DCI, and the common DCI having DCI format 1_2 may be referred to as the third DCI.

[0084] For example, a DCI having DCI format 1_1 may have fields shown in Figures 9 and 10. In Figures 9 and 10, min represents the minimum number of bits of the field size, and max represents the maximum number of bits of the field size. parameter represents a parameter that determines the size of each field, and IE represents an information element that includes the parameter. It may be considered that the upper layer parameter is defined by the parameter and the IE.

[0085] 9 and 10, a common DCI common to two or more UEs 200 receiving data in the PTM-1 MBS may include a first field whose size is determined by a common upper layer parameter. The first field may include the following fields:

[0086] The first field may include a Bandwidth Part Indicator field. The size of the Bandwidth Part Indicator may be determined based on the number of configured DL BWPs for the MBS. The number of configured DL BWPs is an example of a common upper layer parameter.

[0087] The first field may include a Frequency Domain Resource Assignment (FDRA) field. The size of the FDRA field may be determined based on the locationAndBandwidth-Multicast parameter included in the Common Frequency Resource (CFR)-Config-Multicast parameter. The locationAndBandwidth-Multicast parameter included in the CFR-Config-Multicast parameter is an example of a common upper layer parameter.

[0088] The resource allocation type used to determine the size of the FDRA field may be specified by a specific upper layer parameter or a common upper layer parameter. The resource allocation types that can be specified by the common upper layer parameter may be limited to specific resource allocation types.

[0089] The first field may include a TDRA (Time Domain Resource Assignment) field. The size of the TDRA field may be determined based on the pdsch-TimeDomainAllocationList included in the pdsch-Config-Multicast of the CFR-Config-Multicast. The pdsch-TimeDomainAllocationList included in the pdsch-config-Multicast of the CFR-Config-Multicast is an example of a common upper layer parameter. Note that the pdsch-TimeDomainAllocationList may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0090] The first field may include a VRB-toPRB mapping field. The size of the VRB-toPRB mapping field may be determined based on the resourceAllocation included in the pdsch-Config-Multicast of the CFR-Config-Multicast. The resourceAllocation included in the pdsch-config-Multicast of the CFR-Config-Multicast is an example of a common upper layer parameter. Note that the resourceAllocation may be the same as the name used in the specific upper layer parameter (pdsch-Config).

[0091] The first field may include a PRB bundling size indicator field. The size of the PRB bundling size indicator field may be determined based on the prb-Bundlingtype included in the pdsch-Config-Multicast of the CFR-Config-Multicast. The prb-Bundlingtype included in the pdsch-config-Multicast of the CFR-Config-Multicast is an example of a common upper layer parameter. Note that the prb-Bundlingtype may be the same as the name used in the specific upper layer parameter (pdsch-Config).

[0092] The first field may include a Rate matching indicator field. The size of the Rate matching indicator field may be determined based on rateMatchPatternGroup1 and rateMatchPatternGroup2 included in pdsch-Config-Multicast of CFR-Config-Multicast. rateMatchPatternGroup1 and rateMatchPatternGroup2 included in pdsch-config-Multicast of CFR-Config-Multicast are examples of common upper layer parameters. Note that rateMatchPatternGroup1 and rateMatchPatternGroup2 may be the same as the names used in the specific upper layer parameters (pdsch-Config).

[0093] The first field may include a ZP CSI-RS trigger field. The size of the ZP CSI-RS trigger field may be determined based on the aperiodic-ZP-CSI-RS-ResourceSetsToAddModList included in the pdsch-Config-Multicast of the CFR-Config-Multicast. The aperiodic-ZP-CSI-RS-ResourceSetsToAddModList included in the pdsch-config-Multicast of the CFR-Config-Multicast is an example of a common upper layer parameter. Note that the aperiodic-ZP-CSI-RS-ResourceSetsToAddModList may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0094] The first field may include a Modulation and coding scheme (TB2) field. The size of the Modulation and coding scheme (TB2) field may be determined based on maxNrofCodeWordsScheduledByDCI included in pdsch-Config-Multicast of CFR-Config-Multicast. maxNrofCodeWordsScheduledByDCI included in pdsch-config-Multicast of CFR-Config-Multicast is an example of a common upper layer parameter. Note that maxNrofCodeWordsScheduledByDCI may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0095] The first field may include a New data indicator (TB2) field. The size of the New data indicator (TB2) field may be determined based on maxNrofCodeWordsScheduledByDCI included in pdsch-Config-Multicast of CFR-Config-Multicast. maxNrofCodeWordsScheduledByDCI included in pdsch-config-Multicast of CFR-Config-Multicast is an example of a common upper layer parameter. Note that maxNrofCodeWordsScheduledByDCI may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0096] The first field may include a Redundancy version (TB2) field. The size of the Redundancy version (TB2) field may be determined based on maxNrofCodeWordsScheduledByDCI included in pdsch-Config-Multicast of CFR-Config-Multicast. maxNrofCodeWordsScheduledByDCI included in pdsch-config-Multicast of CFR-Config-Multicast is an example of a common upper layer parameter. Note that maxNrofCodeWordsScheduledByDCI may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0097] The first field may include a Downlink assignment index field. The size of the Downlink assignment index field may be determined based on the number of configured serving cells for the MBS, nfi-TotalDAI-Included-r16, pdsch-HARQ-ACK-Codebook-Multicast, CORESETPoolIndex, and ackNackFeedbackMode. The number of configured serving cells is an example of a common upper layer parameter. The pdsch-HARQ-ACK-Codebook-Multicast included in PhysicalCellGroupConfig is an example of a common upper layer parameter. The CORESETPoolIndex included in ControlResourceSet of pdcch-Config-Multicast is an example of a common upper layer parameter. Note that nfi-TotalDAI-Included-r16, CORESETPoolIndex, ackNackFeedbackMode, PhysicalCellGroupConfig, and ControlResourceSet may have the same names as those used in the specific upper layer parameters.

[0098] The first field may include a PDSCH-to-HARQ_feedback timing indicator field. The size of the PDSCH-to-HARQ_feedback timing indicator field may be determined by dl-DataToUL-ACK included in pucch-Config-ACK / NACK-Multicast. dl-DataToUL-ACK included in pucch-Config-ACK / NACK-Multicast is an example of a common upper layer parameter. Note that dl-DataToUL-ACK I may be the same as the name used in the specific upper layer parameter (pucch-Config-ACK / NACK).

[0099] The first field may include an Antenna port(s) field. The size of the Antenna port(s) field may be determined based on dmrs-type and maxLength included in DMRS-DownlinkConfig of pdsch-Config-Multicast. dmrs-type and maxLength included in DMRS-DownlinkConfig of pdsch-Config-Multicast are examples of common upper layer parameters. Note that dmrs-type, maxLength, and DMRS-DownlinkConfig may be the same as the names used in specific upper layer parameters.

[0100] The first field may include a Transmission configuration indication field. The size of the Transmission configuration indication field may be determined based on tci-PresentInDCI of ControlResourceSet of pdsch-Config-Multicast. tci-PresentInDCI of ControlResourceSet of pdsch-Config-Multicast is an example of a common upper layer parameter. Note that ControlResourceSet and tci-PresentInDCI may have the same names as those used in specific upper layer parameters.

[0101] The first field may include a Priority indicator field. The size of the Priority indicator field may be determined based on priorityIndicatorDCI-1-1-r16 included in pdsch-Config-Multicast. priorityIndicatorDCI-1-1-r16 included in pdsch-Config-Multicast is an example of a common upper layer parameter. Note that priorityIndicatorDCI-1-1-r16 may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0102] The first field may include a Minimum applicable scheduling offset indicator field. The size of the Minimum applicable scheduling offset indicator field may be determined based on minimumSchedulingOffsetK0 included in pdsch-Config-Multicast. minimumSchedulingOffsetK0 included in pdsch-Config-Multicast is an example of a common upper layer parameter. Note that minimumSchedulingOffsetK0 may have the same name as that used in the specific upper layer parameter (pdsch-Config).

[0103] Under this assumption, the common DCI having DCI format 1_1 may not have the following fields compared to the specific DCI having DCI format 1_1. In other words, some fields included in the specific DCI may be omitted in the common DCI.

[0104] For example, the common DCI may not include one or more fields selected from the following: Identifier for DCI formats, Carrier indicator, Bandwidth part indicator, One-shot HARQ-ACK request, PDSCH group index, New feedback indicator, Number of requested PDSCH group(s), SRS request, CBG transmission information (CBGTI), CBG flushing out information (CBGFI), ChannelAccess-Cpext, and SCell dormancy indication.

[0105] In such a case, fields that are not included in the common DCI may be predetermined in the wireless communication system 10. Alternatively, for a field whose minimum number of bits (min) is 0, the size of the field can be set to 0 by a higher layer parameter, so it is not necessary for the wireless communication system 10 to predetermine that the field is omitted.

[0106] Additionally, the common DCI may include a second field whose size is determined by the specific upper layer parameter, the second field being a different field from the first field whose size is determined by the common upper layer parameter.

[0107] For example, the second field may include a Carrier indicator field. The size of the Carrier indicator field may be determined based on CrossCarrierSchedulingConfig. CrossCarrierSchedulingConfig is an example of a specific upper layer parameter. In such a case, the common DCI shall include the Carrier indicator field.

[0108] Note that for fields whose size is not variable (e.g., Modulation and coding scheme (TB1), New data indicator (TB1), Redundancy version (TB1), HARQ process number, TPC command for scheduled PUCCH, PUCCH resource indicator, etc.), there is no need to specify the field size in the common upper layer parameters.

[0109] The following provides a supplementary explanation of TB (Transport Block). TB indicates a data block unit in HARQ transmission. TB may also be read as CW (Code Word).

[0110] For example, the fields related to TB1 (Modulation and coding scheme (TB1), New data indicator (TB1), Redundancy version (TB1)) may be fields used in PDSCHs of MIMO layers 1 to 4. The fields related to TB1 may be fields that are always included in DCI. The fields related to TB2 (Modulation and coding scheme (TB2), New data indicator (TB2), Redundancy version (TB2)) may be fields that are used in PDSCHs of MIMO layers 5 to 8. The fields related to TB2 may be fields that are included in DCI when maxNrofCodeWordsScheduledByDCI=2 is set.

[0111] Under this assumption, it may be assumed that PDSCHs of up to m MIMO layers are used in an MBS. For example, m may be 1. In other words, it may be assumed that only TB1 is used in an MBS. Therefore, the PDSCHs of an MBS may be controlled based on a common DCI that includes a field related to TB1. In other words, the common DCI may not include a field related to TB2.

[0112] 9 and 10 only show examples of DCI fields. Therefore, the common DCI only needs to include at least one field as a first field whose size is determined by a common upper layer parameter. The common DCI does not need to include a second field whose size is determined by a specific upper layer parameter.

[0113] (7) Number of BWPs and Serving Cells As described above, the size of the Bandwidth part indicator field included in the common DCI may be determined based on the number of BWPs configured for the MBS. Similarly, the size of the Downlink assignment index field included in the common DCI may be determined based on the number of Serving Cells configured for the MBS.

[0114] In such a case, it should be considered that the number of BWPs / Serving Cells used in MBS may be a value different from the number of BWPs / Serving Cells actually set in UE 200. In consideration of such a case, the following options may be adopted.

[0115] In the first option, the number of BWPs / Serving Cells used in the MBS may be set to be the same as the number of BWPs / Serving Cells actually set in the UE 200. The UE 200 may not assume that the number of BWPs / Serving Cells used in the MBS is set to a number of BWPs / Serving Cells different from the number of BWPs / Serving Cells actually set in the UE 200. In such a case, the number of BWPs / Serving Cells used in the MBS does not need to be set separately from the number of BWPs / Serving Cells actually set in the UE 200, and may be set separately from the number of BWPs / Serving Cells actually set in the UE 200.

[0116] In the second option, the number of BWPs / Serving Cells used in the MBS may be set separately from the number of BWPs / Serving Cells actually set in the UE 200. The number of BWPs / Serving Cells used in the MBS may be set by a higher layer parameter. The UE 200 may assume that the number of BWPs / Serving Cells used in the MBS is set to a number of BWPs / Serving Cells different from the number of BWPs / Serving Cells actually set in the UE 200. However, the number of BWPs / Serving Cells set for the MBS is not actually set in the UE 200, but is a parameter used to determine the size of the first field included in the common DCI. Note that the number of BWPs / Serving Cells set for the MBS may be set as part of an RRC parameter related to the MBS, such as xx-Multicast.

[0117] First, in the second option, a case may be considered in which the number of BWPs / Serving Cells configured for an MBS is greater than the number of BWPs / Serving Cells actually configured for UE 200. For example, as shown in FIG. 11, consider a case in which the number of BWPs / Serving Cells configured for an MBS is four (#1 to #4) and the number of BWPs / Serving Cells actually configured for UE 200 is two (#1 to #2). In such a case, UE 200 may ignore information elements #3 and #4 included in the common DCI and common upper layer parameters. The information elements ignored by UE 200 may be specified by the most significant bit (MSB) or the least significant bit (LSB).

[0118] Second, in the second option, it is not necessary to assume a case where the number of BWP / Serving Cells configured for an MBS is smaller than the number of BWP / Serving Cells actually configured for UE 200. Alternatively, it is possible to assume a case where the number of BWP / Serving Cells configured for an MBS is smaller than the number of BWP / Serving Cells actually configured for UE 200. In such a case, a BWP / Serving Cell to be used for an MBS may be selected from among the BWP / Serving Cells actually configured for UE 200 in ascending order of BWP / Serving Cell IDs, or a BWP / Serving Cell to be used for an MBS may be selected in descending order of BWP / Serving Cell IDs.

[0119] (8) Actions and Effects In an embodiment, in an MBS, the UE 200 determines a size of at least one first field among fields included in the common DCI based on a common upper layer parameter used in the common DCI common to two or more UEs 200. The common upper layer parameter is defined separately from a specific upper layer parameter used in a specific DCI specific to each of the two or more UEs 200. With this configuration, even in a case where the common DCI is carried by a PDCCH in which the CRC is scrambled by the G-RNTI, the UE 200 can identify the size of the first field included in the common DCI and can properly decode the common DCI.

[0120] (9) Other embodiments The present invention has been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0121] In the above disclosure, the names of the formats of the common DCI whose CRCs are scrambled by the G-RNIT are exemplified as DCI format 1_0 / 1_1 / 1_2. However, the above disclosure is not limited thereto. The names of the formats of the common DCI whose CRCs are scrambled by the G-RNIT may be other names.

[0122] Although not specifically mentioned in the above disclosure, the following UE capabilities may be defined. The UE capability may include an information element indicating whether or not a UE has the capability to support MBS. The UE capability may include an information element indicating whether or not a UE has the capability to support DCI format 1_1 used in MBS. The UE capability may include an information element indicating whether or not a UE has the capability to support DCI format 1_0 used in MBS. The UE capability may include an information element indicating whether or not a UE has the capability to support PTM-1. The UE capability may include an information element indicating whether or not a UE has the capability to support PTM-2. The UE capability may include an information element indicating whether or not a UE has the capability to support common DCI whose CRC is scrambled by the G-RNTI.

[0123] The above disclosure may be applied to a UE 200 that has reported UE capability having a function of supporting MBS. The above disclosure may be applied to a UE 200 that has reported UE capability having a function of supporting DCI format 1_1 used in MBS. The above disclosure may be applied to a UE 200 that has reported UE capability having a function of supporting PTM-1. The above disclosure may be applied to a UE 200 that has reported UE capability having a function of supporting common DCI in which the CRC is scrambled by the G-RNTI. The above disclosure may be applied to a UE 200 in which an operation related to MBS is configured.

[0124] In addition, although the above disclosure has been described using the MBS PDSCH as an example, at least one of the above-described operation examples may be applied to other downlink channels such as the MBS PDCCH. Furthermore, the above-described operation examples may be combined and applied in a composite manner as long as no contradiction occurs.

[0125] In the above disclosure, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0126] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0127] The block diagrams (FIGS. 4 and 5) used in the description of the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0128] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0129] Furthermore, the above-described gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 12 is a diagram showing an example of the hardware configuration of the device. As shown in Fig. 12, the device may be 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.

[0130] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0131] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0132] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0133] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0134] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0135] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0136] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0137] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0138] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0139] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0140] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

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

[0142] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0143] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), 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), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

[0144] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0145] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0146] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0147] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be sent to another device.

[0148] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0149] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0150] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0151] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0152] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

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

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

[0155] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

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

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

[0158] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0159] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0160] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0161] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0162] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0163] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as uplink channel and downlink channel may be read as side channel.

[0164] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0165] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

[0166] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0167] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

[0168] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may be a time unit based on numerology.

[0169] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0170] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0171] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

[0174] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

[0176] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0178] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0179] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

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

[0181] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

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

[0183] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

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

[0185] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

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

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

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

[0189] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0190] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

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

[0192] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

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

[0194] Fig. 13 shows an example of the configuration of a vehicle 2001. As shown in Fig. 13, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0195] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0196] The steering unit 2003 includes at least a steering wheel (also called a handle), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

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

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

[0199] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

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

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

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

[0203] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0204] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0205] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0206] 10. Wireless communication systems 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 communication port

Claims

1. In a multicast / broadcast service (MBS) in which data is distributed to a plurality of terminals, a receiving unit receives downlink control information (DCI) scrambled by an RNTI common to the plurality of terminals; a control unit that determines a size of a first field among fields included in the downlink control information based on the upper layer parameters for the multicast / broadcast service; The terminal, wherein the downlink control information includes a frequency domain resource allocation field different from the first field.

2. The terminal described in claim 1, wherein the first field includes one or more fields selected from a virtual resource block to physical resource block mapping field, a physical resource block bundling size indicator field, a rate matching field, a zero power channel estimation information reference signal trigger field, a priority indicator field, a transmission configuration indication field, and a timing indicator field from a dedicated downlink shared channel to an acknowledgment feedback.

3. In a multicast / broadcast service (MBS) in which data is distributed to a plurality of terminals, a first transmitter transmits downlink control information (DCI) scrambled by an RNTI common to the plurality of terminals; a second transmitter configured to transmit an upper layer parameter for the multicast / broadcast service, the upper layer parameter being used to determine a size of a first field among fields included in the downlink control information; The base station, wherein the downlink control information includes a frequency domain resource allocation field different from the first field.

4. A terminal and a base station, the base station comprises a transmitter that transmits downlink control information (DCI) scrambled by an RNTI common to the plurality of terminals in a multicast / broadcast service (MBS) in which data is distributed to the plurality of terminals; the terminal comprises a control unit that determines a size of a first field among fields included in the downlink control information based on the upper layer parameters for the multicast / broadcast service; The downlink control information includes a frequency domain resource allocation field different from the first field.

5. In a multicast / broadcast service (MBS) in which data is distributed to a plurality of terminals, receiving downlink control information (DCI) scrambled by an RNTI common to the plurality of terminals; determining a size of a first field among fields included in the downlink control information based on higher layer parameters for the multicast / broadcast service; The wireless communication method, wherein the downlink control information includes a frequency domain resource allocation field different from the first field.

Images