Terminal and communication method

Abstract

This terminal comprises: a reception unit that receives system information from a base station; and a control unit that, on the basis of the system information, sets individual common frequency resources (CFR) which pertain to a broadcast multicast-broadcast services (MBS) function and are for a terminal having reduced functionality. The reception unit monitors a search space in the CFR, receives downlink control information (DCI), and receives, from the base station, a group common physical downlink shared channel (PDSCH) scheduled by the DCI.

Description

Terminal and communication method

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

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that satisfy the requirements of a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (for example, Non-Patent Document 1).

[0003] In LTE or NR, UE categories or UE capabilities for IoT (Internet of Things) are defined that reduce functions that are mandatory for normal terminals, such as functions related to transmission and reception bandwidth and the number of antennas. For example, in LTE, eMTC (enhanced Machine Type Communication) and NB-IoT (Narrow Band IoT) are defined, and in NR, RedCap (Reduced Capability) and the like are defined.

[0004] Furthermore, studies have begun on future systems beyond 5G, or 6G, which are expected to further improve communication performance and diversify use cases.

[0005] 3GPP TS 38.300 V17.5.0(2023-06)3GPP TS 38.213 V17.6.0(2023-06)3GPP TS 38.214 V17.6.0(2023-06)3GPP TS 38.331 V17.5.0(2023-06)3GPP TS 38.321 V17.5.0(2023-06)

[0006] In future systems (e.g., NR Release 18 and 6G, the successor system to NR), eRedCap (enhanced Reduced Capability), which has even fewer functions than RedCap considered in NR Release 17, is being considered. For example, eRedCap terminals have limited baseband processing capabilities. Here, there is a possibility that they will not be able to properly transmit and receive channels with bandwidths exceeding their baseband processing capabilities.

[0007] In addition, NR supports the Multicast-Broadcast Services (MBS) function. In the MBS function, a Common Frequency Resource (CFR) is set, and a single DL transmission is received by multiple UEs on the CFR. Here, when an eRedCap terminal supports the MBS function, appropriate operation taking into account processing capabilities is required.

[0008] The present invention has been made in view of the above points, and has as its object to enable a terminal with reduced functionality in a wireless communication system to support MBS (Multicast-Broadcast Services) functionality.

[0009] According to the disclosed technology, a terminal is provided that includes a receiving unit from a base station that receives system information and a control unit that sets a common frequency resource (CFR) related to a broadcast multicast-broadcast services (MBS) function that is individual for a terminal with reduced functionality based on the system information, wherein the receiving unit monitors a search space within the CFR to receive downlink control information (DCI), and receives a group common physical downlink shared channel (PDSCH) scheduled by the DCI from the base station.

[0010] According to the disclosed technology, in a wireless communication system, a terminal with reduced functionality can support MBS (Multicast-Broadcast Services) functionality.

[0011] FIG. 1 is a diagram showing an example of the configuration of a wireless communication system. FIG. 2 is a diagram showing an example of MBS functions according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of CFR according to an embodiment of the present invention. FIG. 4 is a diagram showing an example of broadcasting according to an embodiment of the present invention. FIG. 5 is a diagram showing an example of multiplexing (1) according to an embodiment of the present invention. FIG. 6 is a diagram showing an example of multiplexing (2) according to an embodiment of the present invention. FIG. 7 is a diagram showing an example of HARQ feedback according to an embodiment of the present invention. FIG. 8 is a diagram showing an example of the functional configuration of a base station 10 according to an embodiment of the present invention. FIG. 9 is a diagram showing an example of the functional configuration of a terminal 20 according to an embodiment of the present invention. FIG. 10 is a diagram showing an example of the hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. FIG. 11 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

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

[0013] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR), unless otherwise specified.

[0014] In addition, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily stated as "NR-".

[0015] Furthermore, in the embodiment of the present invention, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0016] Furthermore, in the embodiments of the present invention, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0017] Fig. 1 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0018] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, transmitted via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may also be referred to as SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0019] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures propagation path quality based on the reception results of the reference signals.

[0020] The terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with the base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0021] First, we will explain the RedCap of the conventional NR Release 17. The maximum bandwidth supported by the RedCapUE considered in NR Release 17 is 20 MHz in FR1 (Frequency Range 1) and 100 MHz in FR2 (Frequency Range 2). In addition, RedCapUE is required to coexist with non-RedCapUE (hereinafter also referred to as "non-RedCapUE") within the system.

[0022] In addition, RedCap UE and non-RedCap UE may be able to share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth, and location) set by the MIB (Master Information Block), while an initial DL-BWP with separate or additional subcarrier spacing, bandwidth, and location may be set for the RedCap UE.

[0023] RedCapUEs can share the initial DL-BWP (hereinafter also referred to as "DL-BWP#0") for non-RedCapUEs if the maximum bandwidth supported by the RedCapUE is not exceeded.

[0024] In addition, in the NR Release 17 specifications, in order to avoid RF retuning, in the case of TDD, the DL-BWP and UL-BWP of the same index must have the same center frequency.

[0025] Also, after establishing or re-establishing a dedicated RRC connection, the RedCapUE assumes that the initial DL-BWP and active DL-BWP are less than or equal to the maximum DL bandwidth supported by the RedCapUE. The RedCapUE is provided with a DL-BWP by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB" and a UL-BWP by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB". If the "initialUplinkBWP" in "UplinkConfigCommonSIB" indicates a UL-BWP greater than the maximum UL-BWP supported by the RedCapUE, the RedCapUE assumes that the UL-BWP is provided by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB".

[0026] A RedCapUE may be provided with a DL-BWP by "BWP-DownlinkDedicated" in addition to the initial DL-BWP. A RedCapUE may be provided with a UL-BWP by "BWP-UplinkDedicated" in addition to the initial UL-BWP, which is less than the maximum UL bandwidth supported by the RedCapUE.

[0027] If the RedCapUE is provided with "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap", the RedCapUE uses the corresponding parameters to perform the initial access and random access procedures. Otherwise, the RedCapUE uses the corresponding parameters provided by "RACH-ConfigCommon" or "RACH-ConfigCommonTwoStepRA".

[0028] If a RedCapUE is provided with "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB" and has no dedicated PUCCH resource configuration, it will use the PUCCH resource set provided by "pucch-ResourceCommonRedCap" to transmit PUCCH using HARQ-ACK information. Note that if "disable-FH-PUCCH" is provided in "PUCCH-ConfigCommonRedCap", PUCCH transmission will be disabled.

[0029] For the initial DL-BWP provided by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB", if the RedCapUE monitors the PDCCH according to the CSS (Common search space) set of Type1-PDCCH and does not monitor the PDCCH according to the CSS set of Type2-PDCCH, it recognizes that the initial DL-BWP does not contain an SS / PBCH block or a CORESET (Control resource set) with index 0.

[0030] When a RedCapUE monitors the PDCCH according to the CSS set of Type2-PDCCH, it is assumed that the initial DL-BWP includes the SS / PBCH block and a CORESET with index 0 if the RedCapUE used the SS / PBCH block to acquire SIB1, and includes the SS / PBCH block, and does not include a CORESET with index 0 if the initial DL-BWP does not include the SS / PBCH block used by the RedCapUE to acquire SIB1.

[0031] For an active DL-BWP provided by "BWP-DownlinkDedicated", the RedCapUE shall assume that the active DL-BWP contains SS / PBCH blocks and does not contain a CORESET with index 0, unless the RedCapUE indicates the capability to operate in DL-BWP without receiving SS / PBCH blocks.

[0032] Next, the status of study on RedCap for NR Release 18 will be described. In NR Release 18, eRedCap is being studied to further reduce the complexity of RedCapUE for NR Release 17. Hereinafter, the reduced-function terminal for NR Release 17 will be referred to as RedCapUE, and the extended reduced-function terminal for NR Release 18 will be referred to as eRedCapUE, to distinguish between the two. RedCapUE is an example of a first reduced-function terminal. eRedCapUE is an example of a second reduced-function terminal. In other words, the first reduced-function terminal is a terminal in which a first function has been reduced, and the second reduced-function terminal is a terminal in which a second function different from the first function (including cases where some of the functions overlap) has been reduced.

[0033] Issues being considered include the impact on the network, coexistence of RedCap or eRedCap UEs with non-RedCap UEs in a cell, the impact on the UE, the impact on specifications, etc. Potential solutions to reduce device complexity, which may be complementary, focus on:

[0034] A first solution is being considered to reduce the UE bandwidth to 5 MHz in FR1, which may be specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.

[0035] A second solution being considered is to reduce the UE peak data rate for FR1, which may involve limited bandwidth for PDSCH and / or PUSCH, possibly specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.

[0036] It is considered necessary to pay attention to the following points for eRedCapUE: It is necessary to reuse the SSB specified in NR Release 15 and minimize changes to L1. It is also necessary to consider BWP operation with / without SSB and with / without RF retuning. It is also considered that some FR1 solutions may be applicable to FR2. Finally, it is considered that a type of reduced-function terminal for a single Release 18 will be defined to further reduce the complexity of the UE.

[0037] eRedCapUE may be defined as follows:

[0038] For example, in the random access procedure, a terminal 20 that notifies that it is an eRedCapUE in at least one of Msg1, Msg3, and MsgA may be defined as an eRedCapUE. For example, an eRedCapUE may transmit Msg1 or MsgA using resources defined or configured for the eRedCapUE, or may notify that it is an eRedCapUE in a notification field in Msg3 defined for the eRedCapUE.

[0039] For example, a terminal 20 that supports specific UE capabilities may be defined as an eRedCapUE. The specific UE capabilities may be, for example, 1) to 7) shown below.

[0040] 1) Supporting up to 5 MHz bandwidth for PDSCH and PUSCH in FR1. 2) Supporting relaxed UE processing time for PDSCH, PUSCH, and / or CSI. 3) Supporting reduced UE peak data rates in FR1. 4) Supporting one or two receive branches and the corresponding maximum number of DL-MIMO layers. 5) Supporting FD (Full Duplex)-FDD or Type A HD (Half Duplex)-FDD in the FR1 FDD band. 6) Supporting 64QAM (Quadrature amplitude modulation) or 256QAM in FR1. 7) Not supporting carrier aggregation or dual connectivity.

[0041] Furthermore, the terminal 20 that reports to the base station 10 that it supports the specific UE capability through a UE capability report may be defined as an eRedCapUE. Note that the existing terminal may be a terminal other than an eRedCapUE.

[0042] In addition, eRedCap terminals may support the operations shown in 1)-5) below to reduce the complexity associated with UE-BB.

[0043] 1) It may be possible to receive a DL allocation contained in a DCI that allocates unicast PDSCH resources with a bandwidth exceeding 5 MHz. 2) For a broadcast PDSCH carrying SIB1, the scheduling of SIB1 may exceed 5 MHz as in legacy operation. 3) For a broadcast PDSCH carrying Other System Information (OSI), the scheduling of OSI may exceed 5 MHz as in legacy operation. 4) For a broadcast PDSCH carrying Random Access Response (RAR), the scheduling of the RAR-PDSCH may exceed the maximum number of unicast PRBs that an eRedCap terminal can process per slot. 5) For a broadcast PDSCH carrying paging, the scheduling of the paging channel may exceed 5 MHz as in legacy operation.

[0044] 2 is a diagram illustrating an example of MBS functionality according to an embodiment of the present invention. In NR Releases 15 and 16, only unicast was supported. In NR Release 17, NR-MBS was introduced, supporting multicast and broadcast.

[0045] As shown in Figure 2, in the RRC_IDLE state and the RRC_INACTIVE state, the UE receives SIB20 and performs settings related to the MBS (Multicast-Broadcast Services) function, and the gNB transmits the logical channels MCCH (MBS Control Channel) and MTCH (MBS Traffic Channel) to the UE via the group common PDCCH and group common PDSCH. MTCH carries broadcast traffic.

[0046] When the UR transitions to the RRC_CONNECTED state by transmitting a RACH preamble to the gNB and the gNB transmitting a RACH response to the UE, multicast traffic becomes possible in addition to broadcast. The Common Frequency Resource (CFR) setting is transmitted from the gNB to the UE by UE-specific signaling. The UE receives the MTCH carrying multicast traffic via the group common PDCCH and group common PDSCH, and transmits HARQ-ACK feedback to the gNB.

[0047] 3 is a diagram showing an example of a CFR according to an embodiment of the present invention. As shown in FIG. 3, a search space and a group common PDSCH are arranged in the CFR (Common Frequency Resource). The type of search space is Type 0 or Type 0B-CSS for broadcast, and Type 3-CSS for multicast. The monitoring priority of the CSS is determined based on the index of the search space set. CORESET is set in the CFR.

[0048] The DCI placed in the search space schedules the group-common PDSCH. Regarding the DCI format, DCI format 4_0 is used for broadcast, and DCI format 4_1 or 4_2 is used for multicast. The "3+1" DCI size budget is maintained.

[0049] Regarding RNTI (Radio Network Temporary Identifier), in the case of broadcast, MCCH-RNTI is used to schedule MCCH, and G-RNTI is used to schedule MTCH (see Non-Patent Document 5). In the case of multicast, G-RNTI is used for dynamic scheduling, and G-CS-RNTI is used for semi-persistent scheduling (see Non-Patent Document 5).

[0050] In the case of broadcast, the group common PDSCH may support 1)-3) shown below.

[0051] 1) Semi-persistent or dynamic slot-level repetitive transmission, 2) RB symbol-level rate matching, and 3) RE-level rate matching, e.g., LTE-CRS.

[0052] In the case of multicast, the group common PDSCH may support 1)-3) shown below.

[0053] 1) Semi-persistent or dynamic slot-level repetitive transmission, 2) RB symbol-level rate matching, and 3) RE-level rate matching, e.g., LTE-CRS, ZP CSI-RS.

[0054] Here, the operation when an eRedCap terminal supports the MBS function, i.e., the operation for receiving broadcast PDSCH and / or multicast PDSCH, is unclear, and it is necessary to define an appropriate operation taking into account the processing capabilities of the eRedCap terminal.

[0055] Note that the RedCap in the embodiment of the present invention may be replaced with an eRedCap. The eRedCap in the embodiment of the present invention may be replaced with a RedCap. The RedCap in the embodiment of the present invention may be replaced with a first RedCap. The eRedCap in the embodiment of the present invention may be replaced with a second RedCap.

[0056] A single CFR for transmitting the broadcast MBS-PDSCH and the DCI scheduling the PDSCH is configured for each cell. The broadcast CFR may have the following features 1) to 4).

[0057] 1) Any bandwidth within the carrier bandwidth may be set as the CFR. 2) The CFR completely includes CORESET#0. 3) The same SCS and CP as the initial BWP are used. 4) One CORESET other than CORESET#0 may be set.

[0058] On the other hand, different initial BWPs may be set for RedCap and / or eRedCap terminals and non-RedCap terminals and / or non-eRedCap terminals. An initial BWP for RedCap or eRedCap terminals set separately from non-RedCap terminals and / or non-eRedCap terminals may be referred to as a RedCap and / or eRedCap individual initial BWP (separate initial BWP). The RedCap and / or eRedCap individual initial BWP may not include a band in which CORESET #0 is set.

[0059] Therefore, it may be possible to clarify how to set CFR in a cell that accommodates RedCap and / or eRedCap terminals and non-RedCap terminals and / or non-eRedCap terminals.

[0060] 4 is a diagram showing an example of broadcasting according to an embodiment of the present invention. As shown in FIG. 4, a UE receives SIB20 from a gNB. SIB20 may include information on the location and bandwidth of the frequency domain of the CFR (which may be notified using the information element locationAndBandwidth), CORESET, and PDSCH configuration for MCCH.

[0061] The MCCH is an MBS control channel and is scheduled by DCI format 4_0 with CRC scrambled with the MCCH-RNTI. The MCCH may include a G-RNTI for the MTCH, a PDSCH configuration for the MTCH, and a DRX configuration. The MTCH is an MBS traffic channel and is scheduled by DCI format 4_0 with CRC scrambled with the G-RNTI. The UE receives the MCCH and receives the MTCH based on DCI format 4_0 received via the MCCH.

[0062] For RedCap and / or eRedCap terminals, individual CFRs for broadcast MBSs may be configured, for example, one or more individual CFRs for broadcast MBSs may be configured for one cell.

[0063] For example, the individual CFR for broadcast MBS may be configured in SIB 20. The LocationAndBandwidth parameter of the CFR may be interpreted by a RedCap and / or eRedCap terminal as a setting in a RedCap and / or eRedCap individual initial BWP.

[0064] The individual CFR for broadcast MBS for a RedCap and / or eRedCap terminal may be assumed to be set within the band of the RedCap and / or eRedCap individual initial BWP. The individual CFR for broadcast MBS for a RedCap and / or eRedCap terminal may be assumed to be set to include the band of the RedCap and / or eRedCap individual initial BWP.

[0065] The individual CFR for Broadcast MBS for RedCap and / or eRedCap terminals may not include the band of the initial BWP for non-RedCap terminals and / or non-eRedCap terminals. The individual CFR for Broadcast MBS for RedCap and / or eRedCap terminals may not include CORESET#0.

[0066] If the individual broadcast MBS CFR for a RedCap and / or eRedCap terminal is not set, the RedCap and / or eRedCap terminal may use the CFR set for a non-RedCap terminal and / or a non-eRedCap terminal, and may not assume reception of DCI format 4_0, MCCH, and MTCH.

[0067] Also, an individual CORESET may be set for a RedCap and / or eRedCap terminal for broadcast MBS. The individual CORESET for a RedCap and / or eRedCap terminal may be set by SIB20. It may be assumed that the individual CORESET for a RedCap and / or eRedCap terminal is set within the band of a RedCap and / or eRedCap individual initial BWP.

[0068] The individual CORESET for a RedCap and / or eRedCap terminal may be included in the RedCap and / or eRedCap terminal's individual CFR, or may be included in a CFR shared with non-RedCap and / or non-eRedCap terminals.

[0069] If the individual CORESET for the RedCap and / or eRedCap terminal is not set, the RedCap and / or eRedCap terminal may use the CORESET or CORESET#0 set for the non-RedCap terminal and / or non-eRedCap terminal.

[0070] The CFR may be set to include an initial BWP and / or an initial BWP specific to a RedCap and / or eRedCap terminal. If the CFR does not include an initial BWP for a non-RedCap and / or non-eRedCap terminal, the CFR may not include CORESET#0.

[0071] Note that, when an individual initial BWP is configured for a RedCap and / or eRedCap terminal, the RedCap and / or eRedCap terminal may not assume the CFR setting, DCI format 4_0, and reception of the MCCH and MTCH. For example, the RedCap and / or eRedCap terminal may assume that the CFR setting, DCI format 4_0, and reception of the MCCH and MTCH can be configured only when the RedCap and / or eRedCap terminal shares an initial BWP with a non-RedCap terminal.

[0072] In addition, if an individual initial BWP is set for a RedCap and / or eRedCap terminal and the individual initial BWP does not include CORESET #0, the RedCap and / or eRedCap terminal does not need to assume the setting of CFR, DCI format 4_0, and reception of MCCH and MTCH.

[0073] In addition, it may be assumed that an MCCH-RNTI and / or G-RNTI is defined or configured for each RedCap and / or eRedCap terminal, and that the RedCap and / or eRedCap terminal scrambles DCI format 4_0 using the RNTI.

[0074] It may be assumed that a DCI format specific to a RedCap and / or eRedCap terminal is defined or configured, and that the MCCH and MTCH are scheduled for the RedCap and / or eRedCap terminal using this DCI format.

[0075] It may be assumed that a CSS specific to a RedCap and / or eRedCap terminal is defined or set, and that the RedCap and / or eRedCap terminal transmits DCI format 4_0 in that CSS.

[0076] The above-described operation allows for scheduling of MCCH and MTCH individually for RedCap and / or eRedCap terminals, and avoids band-restricted operation of RedCap and / or eRedCap terminals for non-RedCap and / or non-eRedCap terminals.

[0077] The PDSCH or PUSCH bandwidth that an eRedCap terminal can process per slot is limited to 5 MHz. To perform PDSCH reception processing, i.e., PDSCH decoding and ACK / NACK transmission preparation, in the same PDSCH processing time as a legacy terminal, the number of RBs allocated to a unicast PDSCH for an eRedCap terminal cannot exceed 5 MHz.

[0078] 5 is a diagram showing an example (1) of multiplexing according to an embodiment of the present invention. As shown in FIG. 5, for existing terminals, one unicast PDSCH and one broadcast MBS-PDSCH or one multicast MBS-PDSCH can be frequency-multiplexed in overlapping time resources within the same slot.

[0079] 6 is a diagram showing an example (2) of multiplexing according to an embodiment of the present invention. As shown in FIG. 6, the unicast PDSCH and the MBS-PDSCH may be time division multiplexed (TDM) or frequency division multiplexed (FDM) within a slot. For example, the unicast PDSCH and the multicast or broadcast group common PDSCH may be time division multiplexed within a slot. For example, the multicast or broadcast group common PDSCH and the multicast or broadcast group common PDSCH may be time division multiplexed within a slot. For example, the unicast PDSCH and the multicast or broadcast group common PDSCH may be frequency division multiplexed within a slot.

[0080] Here, even if the unicast PDSCH does not exceed 5 MHz, when the PDSCH band, i.e., the number of RBs, exceeds 5 MHz when combined with the broadcast MBS-PDSCH or multicast MBS-PDSCH multiplexed within the same slot, the frequency multiplexing of multiple PDSCHs within a slot must be appropriately set taking into account the processing capacity of the eRedCap terminal.

[0081] Therefore, restrictions may be defined for eRedCap terminals regarding multiplexing of multiple PDSCHs within the same slot and / or adjacent slots.

[0082] The unicast PDSCH may be a PDSCH scheduled by at least one of a C-RNTI, an MCS-C-RNTI, and a CS-RNTI, or a DCI with a scrambled CRC, but the RNTI is not limited to these.

[0083] The broadcast MBS-PDSCH may be a PDSCH scheduled by an MCCH-RNTI, a G-RNTI, or a DCI with a scrambled CRC, but is not limited to these. The broadcast MBS-PDSCH may be an MCCH or an MTCH.

[0084] The multicast MBS-PDSCH may be a PDSCH scheduled by at least one of a G-RNTI and a G-CS-RNTI or scheduled by a DCI with a scrambled CRC, but the RNTI is not limited to these.

[0085] Regarding multiplexing within a slot, the frequency-multiplexed PDSCHs may overlap partially in the time domain, or may overlap entirely in the time domain, or may be defined as being multiplexed within a slot when scheduled within the same slot even if they do not overlap in the time domain.

[0086] For eRedCap terminals, the following option 1) or option 2) may be implemented for restrictions on multiplexing of multiple PDSCHs within the same slot and / or adjacent slots.

[0087] Option 1) An eRedCap terminal may assume that any two of the unicast PDSCH, broadcast MBS-PDSCH, and multicast MBS-PDSCH may be scheduled in the same slot and / or adjacent slots. For example, it may assume that the scheduling may be performed over a total of more than 5 MHz, or may assume that the scheduling may be performed over a total of less than 5 MHz.

[0088] Note that 5 MHz may correspond to 25 RBs in the case of a 15 kHz SCS, and 12 RBs in the case of a 30 kHz SCS. In other words, exceeding 5 MHz may mean 26 RBs or more in the case of a 15 kHz SCS, or 13 RBs or more in the case of a 30 kHz SCS.

[0089] If any two of the unicast PDSCH, broadcast MBS-PDSCH, and multicast MBS-PDSCH are scheduled to exceed 5 MHz in total, the eRedCap terminal may perform the operations shown in 1)-8) below.

[0090] 1) An eRedCap terminal may not receive either or both PDSCHs, 2) An eRedCap terminal may not decode either or both PDSCHs, and 3) An eRedCap terminal may send a NACK for either or both PDSCHs.

[0091] 4) An eRedCap terminal may not assume that another PDSCH is scheduled in the adjacent N slots, where N may be 1, 2, 3, or 4. The other PDSCH may be any of a unicast PDSCH, a broadcast MBS-PDSCH, and a multicast MBS-PDSCH, or may be a PDSCH scheduled by another SI-RNTI, P-RNTI, RA-RNTI, MSGB-RNTI, or TC-RNTI.

[0092] 5) The eRedCap terminal may decode both PDSCHs. 6) The eRedCap terminal may receive both PDSCHs.

[0093] 7) A priority may be specified for determining which PDSCH an eRedCap terminal receives, decodes, and / or processes. For example, a high-priority PDSCH may always be received, decoded, and / or processed, and a low-priority PDSCH may be received, decoded, and / or processed. A NACK may be fed back for PDSCHs that were not received, decoded, and / or processed. Furthermore, the high-priority PDSCH may follow the existing HARQ feedback timeline, while the low-priority PDSCH may have an extended HARQ feedback timeline. For example, a priority may be set for each PDSCH, and a PDSCH to receive, decode, and / or process may be determined by comparing the priorities.

[0094] 8) The timeline for HARQ feedback for unicast PDSCH and / or multicast MBS-PDSCH may be extended, for example, by adding one slot to the existing timeline.

[0095] The above is option 1).

[0096] Option 2) An eRedCap terminal may not assume that two or more of a unicast PDSCH, a broadcast MBS-PDSCH, and a multicast MBS-PDSCH are scheduled in the same slot and / or in adjacent slots.

[0097] This concludes option 2).

[0098] For multicast MBS-PDSCH, the decision of whether to perform option 1) or option 2) may be based on whether HARQ feedback is enabled or disabled. UE capability signaling may be defined to indicate whether option 1) and / or option 2) are supported.

[0099] For example, the following operations 1)-3) may be performed.

[0100] 1) An eRedCap terminal may assume that unicast PDSCH and broadcast MBS-PDSCH may be scheduled in the same slot, totaling more than 5 MHz.

[0101] 2) An eRedCap terminal may assume that unicast PDSCH and multicast MBS-PDSCH with HARQ feedback disabled may be scheduled in the same slot and / or adjacent slots over a total of more than 5 MHz.

[0102] 3) An eRedCap terminal may assume that multicast MBS-PDSCH and broadcast MBS-PDSCH with HARQ feedback disabled may be scheduled in the same slot and / or adjacent slots over a total of more than 5 MHz.

[0103] Common to the above 1)-3), both PDSCHs may be received and / or decoded, or which PDSCH or both PDSCHs are received and / or decoded may differ depending on the UE capabilities, or which PDSCH or both PDSCHs are received and / or decoded may be determined based on the UE capabilities, or the priority of which PDSCH is received and / or decoded may be specified in the specifications.

[0104] In addition, in the above 1)-3), it may be assumed that no other PDSCH is scheduled in the adjacent slot.

[0105] If the operation is supported, the UE may report a capability indicating that the operation is supported.

[0106] Also, an eRedCap terminal may not assume that a unicast PDSCH and a multicast MBS-PDSCH with HARQ feedback enabled may be scheduled in the same slot and / or adjacent slots, totaling more than 5 MHz.

[0107] Furthermore, an eRedCap terminal may not assume that multicast MBS-PDSCH and broadcast MBS-PDSCH when HARQ feedback is enabled may be scheduled in the same slot and / or adjacent slots exceeding a total of 5 MHz.

[0108] 7 is a diagram showing an example of HARQ feedback according to an embodiment of the present invention. As shown in FIG. 7, when HARQ feedback is disabled for PDSCH in a non-terrestrial network (NTN), the processing time T ｐｒｏｃ，１ After the time has elapsed, the HARQ process number (HPN) can be used again. As shown in Figure 7, if HARQ feedback is enabled, the HPN can be used again after a PUCCH carrying HARQ feedback is received.

[0109] Here, a multicast MBS-PDSCH scheduled by a G-RNTI or a G-CS-RNTI is assigned an HPN. Since the multicast MBS-PDSCH can disable HARQ feedback, the network cannot know when the HPN assigned to the PDSCH can be reused.

[0110] Furthermore, when resources exceeding 5 MHz are allocated for multicast MBS-PDSCH, eRedCap terminals must assume processing times that are different from those of existing terminals.

[0111] Therefore, when the HARQ feedback of the multicast MBS-PDSCH is disabled for the eRedCap terminal, the time until the HPN of the PDSCH is released is set to T ｐｒｏｃ，１+X. The extended time until release of the HPN of the PDSCH may be applied to, but is not limited to, the cases shown in 1) or 2) below. That is, when HARQ feedback of the multicast MBS-PDSCH is disabled for an eRedCap terminal, the time until release of the HPN of the PDSCH may be extended beyond the processing time Tproc,1 related to PDSCH reception.

[0112] 1) This may be applied when the bandwidth of the multicast MBS-PDSCH is allocated to exceed 5 MHz. 2) This may be applied when the total bandwidth of the multicast MBS-PDSCH and the PDSCH multiplexed in the same slot is allocated to exceed 5 MHz.

[0113] The value of X may be in any of, but not limited to, microseconds, milliseconds, symbols, or slots. X may also be 1 slot. For example, T ｐｒｏｃ，１ +1ms applies to 15kHz SCS, T ｐｒｏｃ，１ +0.5ms may be applied in the case of 30kHz SCS.

[0114] The value of X may vary depending on the SCS of the PDSCH or may be determined based on the SCS of the PDSCH. For example, X = X' for a 15 kHz SCS and X = 2X' for a 30 kHz SCS. The value of X may be specified differently depending on the UE capabilities.

[0115] The value of X may be defined as a different value depending on the bandwidth of the multicast MBS-PDSCH, or may be determined based on the bandwidth. For example, it may be defined or determined as shown in 1)-4) below.

[0116] 1) X=X'×N_MuliticastPDSCH 2) X=X'×N_MuliticastPDSCH / N_XRB 3) X=X'×[N_MuliticastPDSCH / N_XRB]

[0117] 4) If 0<N_MulticastPDSCH≦N_RB1, X=X1; if N_RB1<N_MulticastPDSCH≦N_RB2, X=X2; ...; if N_RBn-1<N_MulticastPDSCH≦N_RBn, X=Xn. Note that X may be X'×Floor(N_MulticastPDSCH / N_XRB) or X'×Ceil(N_MulticastPDSCH / N_XRB).

[0118] Note that N_MulticastPDSCH may be the number of RBs allocated to the multicast MBS-PDSCH. N_XRB may be the number of RBs corresponding to 5 MHz (25 RBs for 15 kHz SCS, 12 RBs for 30 kHz SCS), or may be the number of RBs specified in other specifications.

[0119] X' may be greater than 0. The unit of the value of X' may be any of microseconds, milliseconds, symbols, and slots, but is not limited to these.

[0120] The value of X may be specified as a single value regardless of the SCS and / or PDSCH band, etc.

[0121] For example, when the HARQ feedback of the multicast MBS-PDSCH is disabled for an eRedCap terminal, the time until the HPN of the PDSCH is released is set to T ｐｒｏｃ，１ may be multiplied by a constant value, for example, X×T ｐｒｏｃ，１ may be extended to

[0122] Furthermore, for an eRedCap terminal, if HARQ feedback for a multicast MBS-PDSCH is disabled, the HPN field may not be assumed for the DCI that schedules the PDSCH. The HPN field may be assumed to be 0 bits, or the value notified in the HPN field may be ignored.

[0123] According to the above-described embodiment, the terminal 20, which is an eRedCap UE, can individually set a CFR according to the terminal capability and receive transmissions from the base station 10 using the MBS function. Furthermore, the eRedCap terminal can properly receive multiplexed PDSCH. Furthermore, the eRedCap terminal can properly perform operations related to HARQ feedback of multicast MBS-PDSCH.

[0124] That is, in a wireless communication system, a terminal with reduced functionality can support MBS (Multicast-Broadcast Services) functionality.

[0125] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0126] <Base Station 10> Figure 8 is a diagram showing an example of the functional configuration of the base station 10 according to the embodiment of the present invention. As shown in Figure 8, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 8 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations according to the embodiment of the present invention.

[0127] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

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

[0129] The control unit 140 performs control to realize the functions described in the embodiments. Also, as described in the embodiments, the control unit 140 performs control related to the MBS function. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0130] <Terminal 20> Fig. 9 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Fig. 9, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 9 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0131] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0132] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to the MBS function.

[0133] The control unit 240 performs control to realize the functions described in the embodiments. Also, as described in the embodiments, the control unit 240 performs control related to the MBS function. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

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

[0135] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, 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 these functions are implemented.

[0136] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 10 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0137] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 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.

[0138] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0139] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0140] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 8 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. For example, the control unit 240 of the terminal 20 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also 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 also be transmitted from a network via a telecommunications line.

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

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

[0143] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0144] The input device 1005 is an input device (e.g., 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 (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

[0146] Furthermore, the base station 10 and the terminal 20 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.

[0147] Fig. 11 shows an example configuration of a vehicle 2001. As shown in Fig. 11, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0148] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. 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.

[0149] 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 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0150] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal 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.

[0151] 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 (outputting) 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 acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0152] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, 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. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0154] 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.

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

[0156] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from 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 the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0157] (Summary of embodiment) As described above, according to the embodiment of the present invention, there is provided a terminal including a receiving unit from a base station that receives system information and a control unit that sets a CFR (Common Frequency Resource) related to a broadcast MBS (Multicast-Broadcast Services) function that is individual for a terminal with reduced functionality based on the system information, wherein the receiving unit monitors a search space within the CFR to receive DCI (Downlink Control Information), and receives a group common PDSCH (Physical Downlink Shared Channel) scheduled by the DCI from the base station.

[0158] With the above configuration, the terminal 20, which is an eRedCapUE, can individually set a CFR according to the terminal capability and receive transmissions from the base station 10 using the MBS function. That is, in a wireless communication system, a terminal with reduced functionality can support the MBS (Multicast-Broadcast Services) function.

[0159] The control unit may set the CFR within a band of an individual initial bandwidth part (BWP) for a terminal with reduced functionality. With this configuration, an individual CFR can be set for the eRedCap terminal.

[0160] The control unit may set the CFR to a band other than the initial BWP for terminals other than the terminal with reduced functionality. With this configuration, an individual CFR can be set for each eRedCap terminal.

[0161] The control unit may set an individual control resource set (CORESET) for a terminal with reduced functionality for broadcast MBS based on the system information. With this configuration, an individual CORESET can be set for an eRedCap terminal.

[0162] The control unit may assume that the CFR does not include a control resource set (CORESET #0) if the CFR does not include a bandwidth of an initial BWP for a terminal other than a terminal with reduced functionality. With this configuration, the eRedCap terminal can assume that the CFR does not include CORESET #0.

[0163] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the following procedures: a procedure for receiving system information from a base station; a procedure for setting a common frequency resource (CFR) related to a broadcast multicast-broadcast services (MBS) function that is individual for a terminal with reduced functionality based on the system information; and a procedure for monitoring a search space within the CFR to receive downlink control information (DCI), and receiving a group common physical downlink shared channel (PDSCH) scheduled by the DCI from the base station.

[0164] With the above configuration, the terminal 20, which is an eRedCapUE, can individually set a CFR according to the terminal capability and receive transmissions from the base station 10 using the MBS function. That is, in a wireless communication system, a terminal with reduced functionality can support the MBS (Multicast-Broadcast Services) function.

[0165] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0166] 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., Radio Resource Control (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.

[0167] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal number)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0168] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged 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.

[0169] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, 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 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0170] The information, signals, etc. described in the present disclosure 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.

[0171] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0172] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0173] 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.

[0174] 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.

[0175] 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.

[0176] Note that terms described 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.

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

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

[0179] 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.

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

[0181] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). 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.

[0182] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0184] 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.

[0185] At least one of the base station and the mobile station may be referred to as 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 object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

[0187] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0188] 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.

[0189] 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.

[0190] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0191] 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."

[0192] 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 or that the first element must in some way precede the second element.

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

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

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

[0196] Numerology may be communication parameters that apply to the transmission and / or 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 the transceiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, etc.

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

[0198] 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.

[0199] 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.

[0200] 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 (for example, 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.

[0201] 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 wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0202] 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.

[0203] 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.

[0204] 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.

[0205] 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 greater than or equal to 1 ms.

[0206] A resource block (RB) is a resource allocation unit in the time domain and the 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 the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0207] 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.

[0208] 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, etc.

[0209] 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.

[0210] 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 BWP and numbered within the BWP.

[0211] 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.

[0212] 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."

[0213] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to 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.

[0214] 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.

[0215] 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."

[0216] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0217] 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.

[0218] REFERENCE SIGNS LIST 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 30 Core network 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire 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 system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal comprising: a receiver unit for receiving system information from a base station; and a control unit for setting a common frequency resource (CFR) for an individual broadcast MBS (Multicast-Broadcast Services) function for a terminal with reduced functionality based on the system information, wherein the receiver unit monitors a search space within the CFR to receive downlink control information (DCI), and receives a group common physical downlink shared channel (PDSCH) scheduled by the DCI from the base station.

2. The terminal according to claim 1, wherein the control unit sets the CFR within a band of an individual initial BWP (Bandwidth part) for a terminal with reduced functionality.

3. The terminal according to claim 1, wherein said control unit sets said CFR to a band other than the initial BWP for terminals other than the terminal with reduced functionality.

4. The terminal according to claim 1, wherein the control unit sets an individual CORESET (control resource set) for a terminal with reduced functionality for a broadcast MBS based on the system information.

5. The terminal according to claim 1, wherein the control unit assumes that the CFR does not include CORESET#0 (control resource set #0) if the CFR does not include a bandwidth of an initial BWP for a terminal other than a terminal with reduced functionality.

6. A communications method in which a terminal executes the following procedures: a procedure for receiving system information from a base station; a procedure for setting a common frequency resource (CFR) for an individual broadcast MBS (Multicast-Broadcast Services) function for a terminal with reduced functionality based on the system information; and a procedure for monitoring a search space within the CFR to receive downlink control information (DCI), and receiving a group common physical downlink shared channel (PDSCH) scheduled by the DCI from the base station.

Images