Terminal, base station, and communication method
By setting flexible monitoring opportunities and CORESET#0 resource configuration for eRedCap terminals in NR version 18 and subsequent systems, the difficulty of receiving control signals is solved, the reception quality and coverage are improved, and the equipment complexity is reduced.
Patent Information
- Application Number
- CN202280094864.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-18
- Publication Date
- 2024-11-29
AI Technical Summary
In NR version 18 and subsequent systems, the question of how the eRedCap terminal properly receives control signals is not clear, especially in the case of functional reduction, the resource setting flexibility of CORESET#0 is limited, resulting in reduced reliability and coverage.
By repeatedly receiving control signals related to the search space with the same index in different monitoring opportunities in the terminal, and setting flexible resource configurations for eRedCapUE and non-eRedCapUE in the CORESET#0 resource table, including adjusting RB numbers and codes. Monomers and offsets, as well as new CORESET#0 resource tables specified in the standard to support lower bandwidth and less resource usage.
The ability to properly receive control signals in the functional reduction terminal is realized, the reception quality and coverage of eRedCapUE are improved, and the equipment complexity and operating costs are reduced.
Smart Images

Figure CN119054391A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a terminal, a base station and a communication method in a wireless communication system. Background Art
[0002] In NR (New Radio) (also called "5G"), which is the successor system to LTE (Long Term Evolution), technologies that meet the requirements of large-capacity systems, high data transmission speeds, low latency, simultaneous connection of multiple terminals, low costs, and power saving are studied (for example, non-patent document 1).
[0003] In LTE or NR, UE categories or UE capabilities for IoT (Internet of Things) are defined after reducing the functions that are usually mandatory for terminals to support, such as functions related to the 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) is defined.
[0004] In addition, research has begun on systems after 5G and 6G. In these and later systems, further improvements in communication performance and diversification of use cases are envisioned.
[0005] Prior art literature
[0006] Non-patent literature
[0007] Non-patent document 1: 3GPP TS 38.300 V16.8.0 (2021-12) Summary of the invention
[0008] Problems to be solved by the invention
[0009] In future systems (such as NR version 18 and NR's successor system, 6G), eRedCap (enhanced Reduced Cap ability) is being studied, which has further reduced functions than RedCap studied in NR version 17. However, it has been unclear how eRedCap receives control signals.
[0010] The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to enable a terminal to appropriately receive a control signal in a wireless communication system.
[0011] Means for solving problems
[0012] According to the disclosed technology, a terminal is provided, which includes: a receiving unit that receives a control signal in a downlink; and a control unit that assumes that the control signal related to a search space having the same index is repeatedly received in different monitoring opportunities.
[0013] Effects of the Invention
[0014] According to the disclosed technology, a technology is provided in which a terminal can appropriately receive a control signal in a wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 It is a diagram for explaining a wireless communication system according to an embodiment of the present invention.
[0016] Figure 2 This is the first figure for explaining the resource setting of the conventional CORESET#0.
[0017] Figure 3 FIG. 2 is a second diagram for explaining the resource setting of the conventional CORESET#0.
[0018] Figure 4 FIG. 3 is a diagram for explaining the resource setting of the conventional CORESET#0.
[0019] Figure 5 FIG. 4 is a diagram for explaining the resource setting of conventional CORESET#0.
[0020] Figure 6 FIG. 5 is a diagram for explaining the resource setting of conventional CORESET#0.
[0021] Figure 7 FIG. 6 is a diagram for explaining the resource setting of the conventional CORESET#0.
[0022] Figure 8 FIG. 7 is a diagram for explaining the resource setting of the conventional CORESET#0.
[0023] Fig. 9 FIG. 8 is a diagram for explaining the resource setting of the conventional CORESET#0.
[0024] Fig.10 This is a diagram for explaining the reception frequency band of conventional CORESET#0.
[0025] Fig.11 This is the first figure for explaining the resource configuration of CORESET#0 in Example 1-1 of the embodiment of the present invention.
[0026] Fig.12FIG. 2 is a second diagram for explaining resource configuration of CORESET#0 in Example 1-1 of the embodiment of the present invention.
[0027] Fig.13 FIG. 3 is a diagram for explaining resource configuration of CORESET#0 in Example 1-1 of the embodiment of the present invention.
[0028] Fig.14 This is a diagram for explaining the setting of monitoring opportunities in Example 1-2 of the embodiment of the present invention.
[0029] Fig.15 This is a diagram for explaining the setting of the number of PDCCH candidates according to Example 2-1 of the embodiment of the present invention.
[0030] Fig.16 FIG1 is a first diagram for explaining a PDCCH reception method according to Example 2-2 of an embodiment of the present invention.
[0031] Fig.17 FIG. 2 is a diagram for explaining a PDCCH reception method according to Example 2-2 of an embodiment of the present invention.
[0032] Fig.18 FIG. 3 is a diagram for explaining a PDCCH reception method according to Example 2-2 of an embodiment of the present invention.
[0033] Fig.19 FIG. 4 is a diagram for explaining a PDCCH reception method according to Example 2-2 of an embodiment of the present invention.
[0034] Fig. 20 This is a diagram for explaining a PDCCH reception method according to Example 3-1 of an embodiment of the present invention.
[0035] Fig.21 FIG. 1 is a first diagram showing the reception quality of the PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0036] Fig. 22 FIG. 2 is a diagram showing the reception quality of the PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0037] Fig.23 FIG. 3 shows the reception quality of the PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0038] Fig.24FIG. 4 shows the reception quality of the PDCCH obtained by simulating for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0039] Fig.25 FIG. 5 shows the PDCCH reception quality obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0040] Fig.26 FIG. 6 shows the reception quality of PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0041] Fig. 27 This is a diagram for explaining a PDCCH reception method according to Example 3-2 of an embodiment of the present invention.
[0042] Fig.28 This is a diagram showing an example of a functional configuration of a base station according to an embodiment of the present invention.
[0043] Fig.29 This is a diagram showing an example of a functional configuration of a terminal according to an embodiment of the present invention.
[0044] Fig.30 This is a diagram showing an example of the hardware configuration of a base station or a terminal according to an embodiment of the present invention.
[0045] Fig.31 It is a diagram showing an example of the structure of a vehicle according to an embodiment of the present invention. DETAILED DESCRIPTION
[0046] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, the embodiment described below is only an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0047] When the wireless communication system according to the embodiment of the present invention operates, existing technologies are appropriately used. However, the existing technologies are, for example, existing LTE, but are not limited to existing LTE. In addition, unless otherwise specified, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and methods after LTE-Advanced (such as NR).
[0048] In addition, in the embodiments of the present invention described below, the terms 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), PUSCH (Physical Uplink Shared Channel), etc. used in the existing LTE are used. These are for the convenience of recording, and the same signals, functions, etc. may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily marked as "NR-".
[0049] Furthermore, in the embodiments of the present invention, the duplexing method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).
[0050] In the embodiment of the present invention, “configuring” wireless parameters and the like may be pre-configuring predetermined values, or may be configuring wireless parameters notified from the base station 10 or the terminal 20 .
[0051] (System Structure)
[0052] Figure 1 1 is a diagram for explaining a wireless communication system in an embodiment of the present invention. Figure 1 As shown, the wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20. Figure 1 In the figure, one base station 10 and one terminal 20 are shown, but this is just an example, and a plurality of each may be provided.
[0053] 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 the wireless signal are defined by the time domain and the frequency domain. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. In addition, the TTI (Transmission Time Interval) in the time domain can be a time slot, and the TTI can be a subframe.
[0054] The base station 10 sends 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, sent via NR-PBCH, also known as broadcast information. The synchronization signal and system information may also be referred to as SSB (SS / PBCH block). Figure 1 As shown, the base station 10 sends a control signal or data to the terminal 20 via DL (downlink), and receives a control signal or data from the terminal 20 via UL (uplink). Both the base station 10 and the terminal 20 can perform beamforming to transmit and receive signals. In addition, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output)-based communications to DL or UL. In addition, both the base station 10 and the terminal 20 can communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) based on CA (Carrie r Aggregation). Moreover, the terminal 20 can also communicate via the primary cell of the base station 10 based on DC (Dual Connectivity) and the primary and secondary cell group cells (PSCell: Primary SCG Cell) of other base stations 10.
[0055] The terminal 20 is a communication device having a wireless communication function, such as a smart phone, a mobile phone, a tablet computer, a wearable terminal, or an M2M (Machine-to-Machine) communication module. Figure 1 As shown, the terminal 20 receives control signals or data from the base station 10 via DL and sends control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. In addition, the terminal 20 receives various reference signals sent from the base station 10 and measures the propagation path quality based on the reception result of the reference signal. In addition, the terminal 20 may be referred to as UE and the base station 10 may be referred to as gNB.
[0056] (About RedCap of NR version 17)
[0057] First, the existing RedCap of NR version 17 is explained. The maximum bandwidth supported by the RedCapUE studied in NR version 17 is 20MHz in FR1 (Frequency Range 1) and 100MHz in FR2 (Frequency Range 2). In addition, RedCapUE and non-RedCapUE (hereinafter also recorded as "non-RedCapUE") are required to coexist in the system.
[0058] In addition, RedCapUE and non-RedCapUE can share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth and position) set by MIB (Master Information Block). On the other hand, it is also possible to set the initial DL-BWP with a separate or additional subcarrier spacing, bandwidth and position for RedCapUE.
[0059] RedCap UE can share the initial DL-BWP (hereinafter also referred to as "DL-BWP#0") for non-RedCap UE without exceeding the maximum bandwidth supported by RedCap UE.
[0060] In addition, in the NR Release 17 standard, in order to avoid RF retuning, in the case of TDD, the center frequencies of the DL-BWP and UL-BWP of the same index must be the same.
[0061] Furthermore, the RedCapUE assumes that after the dedicated RRC connection is (re)established, the initial DL-BWP and the activated DL-BWP become below the maximum DL bandwidth supported by the RedCapUE. The DL-BWP is provided to the RedCapUE by "initialDownlinkBWP" of "DrownlinkConfigCommonRedCapSIB", and the UL-BWP is provided to the RedCapUE by "initialUplinkBWP" of "UplinkConfigCommonRedCapSIB". In the case where "initialUplinkBWP" of "Uplink ConfigCommonSIB" indicates a UL-BWP larger than the maximum UL-BWP supported by the RedCapUE, the RedCapUE assumes that the UL-BWP is provided by "initialUplinkBWP" of "UplinkConfigCommonRedCapSIB".
[0062] In addition to the initial DL-BWP, the RedCapUE can be provided with a DL-BWP by "BWP-DownlinkDedicated". In addition to the initial UL-BWP, the RedCapUE can be provided with a UL-BWP below the maximum UL bandwidth supported by the RedCapUE by "BWP-UplinkDedicated".
[0063] When the RedCapUE is provided with "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap," the RedCapUE uses the corresponding parameters to perform initial access and random access procedures. In other cases, the RedCapUE uses the corresponding parameters provided by "RACH-ConfigCommon" or "RACH-ConfigCommon TwoStepRA."
[0064] RedCapUE is provided with "initialUplinkBWP" by "UplinkConfigCommonRedCapSIB", and in the absence of dedicated PUCCH resource settings, uses the PUCCH resource set provided by "pucch-ResourceCommonRedCap" to send PUCCH using HARQ-ACK information. In addition, when "disable-FH-PUCCH" is provided by "PUCCH-Config CommonRedCap", PUCCH transmission becomes invalid.
[0065] For the initial DL-BWP provided by "initialDownlinkBWP" of "DownlinkConfigCommonRedCapSIB", RedCapUE identifies that the initial DL-BWP does not include SS / PBCH blocks or CORESET of index 0 when monitoring PDCCH according to the CSS set of Type1-PDCCH and not monitoring PDCCH according to the CSS set of Type2-PDCCH.
[0066] When monitoring PDCCH according to the CSS set of Type2-PDCCH, RedCapUE assumes that when Red CapUE uses SS / PBCH block to obtain SIB1, the initial DL-BWP includes SS / PBCH block and CORESET with index 0. It is assumed that when the initial DL-BWP includes SS / PBCH block and does not include SS / PBCH block used by RedCapUE to obtain SIB1, CORESET with index 0 is not included.
[0067] In the case of an activated DL-BWP provided by "BWP-DownlinkDedicated", in addition to showing the function of operating in DL-BWP without receiving SS / PBCH blocks, RedCapUE assumes that the activated DL-BWP contains SS / PBCH blocks and does not contain CORESET of index 0.
[0068] (About RedCap of NR version 18)
[0069] Next, the research status of RedCap for NR version 18 is described. In NR version 18, eRedCap is being studied to further reduce the complexity of RedCapUE for NR version 17. Hereinafter, the function-reduced terminal for NR version 17 is referred to as RedCapUE, and the extended function-reduced terminal for NR version 18 is referred to as eRedCapUE, thereby distinguishing the two. RedCapUE is an example of a first function-reduced terminal. eRedCapUE is an example of a second function-reduced terminal. That is, the first function-reduced terminal is a terminal from which the first function is reduced, and the second function-reduced terminal is a terminal from which the second function, which is different from the first function (including partial duplication), is reduced.
[0070] The impact on the network, the coexistence of RedCapUE or eRedCapUE and non-RedCapUE in a cell, the impact on UE, the impact on standards, etc. Potential solutions that may complement each other to reduce equipment complexity focus on the following aspects.
[0071] As a first solution, a reduction in UE bandwidth to 5 MHz in FR1 is under study. This solution considers standardization in combination with a relaxed UE processing timeline for PDSCH and / or PUSCH and / or CSI.
[0072] As a second solution, a study is underway to reduce the UE peak data rate in FR1. This solution considers the standardization of a restricted bandwidth that may include PDSCH and / or PUSCH, combined with a relaxed UE processing timeline for PDSCH and / or PUSCH and / or CSI.
[0073] In addition, in eRedCapUE, it is considered that the following should be noted. That is, it is necessary to reuse the SSB standardized in NR Release 15 and minimize the changes in L1. In addition, it is necessary to discuss BWP operation with / without SSB and with / without RF retuning. In addition, the study does not exclude that some solutions for FR1 can be applied to FR2. And in order to further reduce the complexity of UE, the definition of a type of reduced-function terminal for a single Release 18 is under study.
[0074] Next, resource settings of a conventional control resource set (particularly CORESET#0) will be described with reference to the drawings.
[0075] Figure 2 This is the first figure for explaining the resource setting of the conventional CORESET#0. Figure 2 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when both the SSB and the SCS of the PDCCH are set to 15 kHz in a frequency band with a minimum channel bandwidth of 5 MHz or 10 MHz.
[0076] Figure 3 FIG. 2 is a second diagram for explaining the resource setting of the conventional CORESET#0. Figure 3 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when both the SSB and the SCS of the PDCCH are set to 15 kHz in the frequency band operating in shared spectrum channel access.
[0077] Figure 4 FIG. 3 is a diagram for explaining the resource setting of the conventional CORESET#0. Figure 4 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when the SCS of the SSB is set to 15 kHz and the SCS of the PDCCH is set to 30 kHz in a frequency band with a minimum channel bandwidth of 5 MHz or 10 MHz.
[0078] Figure 5 FIG. 4 is a diagram for explaining the resource setting of conventional CORESET#0. Figure 5 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when the SCS of the SSB is set to 30 kHz and the SCS of the PDCCH is set to 15 kHz in a frequency band with a minimum channel bandwidth of 5 MHz or 10 MHz.
[0079] Figure 6 FIG. 5 is a diagram for explaining the resource setting of conventional CORESET#0. Figure 6 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when both the SSB and the SCS of the PDCCH are set to 30 kHz in a frequency band with a minimum channel bandwidth of 5 MHz or 10 MHz.
[0080] Figure 7 FIG. 6 is a diagram for explaining the resource setting of the conventional CORESET#0. Figure 7 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when the SCS of both the SSB and PDCCH are set to 30 kHz in the frequency band operating during shared spectrum channel access.
[0081] Fig.28 FIG. 7 is a diagram for explaining the resource setting of the conventional CORESET#0. Fig.28 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when the SCS of the SSB is set to 30 kHz and the SCS of the PDCCH is set to 15 kHz in a frequency band with a minimum channel bandwidth of 40 MHz.
[0082] Fig.29 FIG. 8 is a diagram for explaining the resource setting of the conventional CORESET#0. Fig.29 The diagram shows a set of resource blocks and slot symbols of the CORESET of the Type0-PDCCH search space when both the SSB and the SCS of the PDCCH are set to 30 kHz in a frequency band with a minimum channel bandwidth of 40 MHz.
[0083] In this way, the CORESET resources used for CSS reception of Type0-PDCCH are determined by the SSB and SCS of PDCCH and the minimum channel bandwidth.
[0084] (Past Problems)
[0085] Next, conventional problems will be described.
[0086] Fig.10 This is a diagram for explaining the reception band of the conventional CORESET#0. In the conventional standard, there is a problem that the CORESET band exceeds 5 MHz except when the SCS is 15 kHz and the number of RBs is 24. Therefore, the eRedCapUE cannot receive CORESET#0 when the maximum bandwidth is 5 MHz.
[0087] Specifically, as the first problem point, there is the following problem: when sharing CORESET#0 set by MIB with RedCapUE and non-RedCap UE (hereinafter, RedCapUE and / or non-RedCapUE will also be referred to as non-eRedCapUE), if CORESET#0 set by MIB is limited to 15kHzSCS / 24RB, the CORESET#0 setting of non-eRedCapUE is also limited.
[0088] As a second problem, there is a problem in that, depending on the solution to the first problem, the flexibility of CORESET#0 resource setting for eRedCapUE is impaired.
[0089] As the third problem, there is a problem that reliability or coverage may be reduced because AL (Aggregation Level) 16 of CCE (Control Channel Element) cannot be supported. In addition, for the second problem, it is also considered to introduce CORESET#0 with a smaller number of RBs such as punctu re of PDCCH or AL2, but in this case, there is a problem that the performance guaranteed in the previous standard may not be achieved.
[0090] (Overview of this embodiment)
[0091] Therefore, in this embodiment, the reception operation of the CORESET#0 resource of the eRedCapUE and the CSS of type0-PDCC H is described. Hereinafter, embodiments 1 to 3 are described. In addition, the terminal 20 of each embodiment is set to be an eRedCapUE unless otherwise specified.
[0092] First, the definitions of RedCapUE, eRedCapUE, and non-RedCapUE are explained.
[0093] The definition of RedCapUE can be any one of the following 1)-3) or other definitions.
[0094] 1) A UE notifies the network that the device is a RedCapUE through any one of Msg.1 / 3 / A. For example, Msg.1 / A may be sent through resources specified or set for RedCapUE, or the notification field in Msg3 specified or set for RedCapUE may be used to notify that the device is a RedCapUE.
[0095] 2) A UE that supports specific UE capabilities. For example, the specific UE capability may be a UE capability that supports a maximum bandwidth of 20 MHz in FR1 and a maximum bandwidth of 100 MHz in FR2. In addition, the specific UE capability may also be a UE capability that supports one or two receiving branches and a UE capability that supports the maximum number of DL-MIMO layers corresponding to the number of supported receiving branches. In addition, the specific UE capability may be a UE capability that supports either FD-FDD (Full Duplex-Frequency Division Duplex) or type A HD-FDD (Half Duplex-Frequency Division Duplex) in the FDD band of FR1. In addition, the specific UE capability may be a UE capability that supports either DL up to 64QAM (Quadrature amplitude modulation) or DL up to 256QAM in FR1. In addition, the specific UE capability may also be a UE capability that does not support CA and / or DC.
[0096] 3) A UE that reports to the network that it supports the specific UE capability shown in 2) above.
[0097] In addition, the definition of eRedCapUE can be any one of the following 1)-3) or other definitions.
[0098] 1) A UE notifies the network that the device is an eRedCapUE through any one of Msg.1 / 3 / A. For example, Msg.1 / A may be sent through resources specified or set for eRedCapUE, or the notification field in Msg3 specified or set for eRedCapUE may be used to notify that the device is an eRedCapUE.
[0099] 2) A UE that supports specific UE capabilities. For example, the specific UE capability may be a UE capability to support a maximum bandwidth of 5 MHz in FR1. In addition, the specific UE capability may be a UE capability to support a relaxed UE processing timeline for PDSCH and / or PUSCH and / or CSI. In addition, the specific UE capability may also be a UE capability to support a reduced UE peak data rate in FR1. In addition, the specific UE capability may also be a UE capability to support one or two receiving branches and a UE capability to support a maximum number of DL-MIMO layers corresponding to the number of supported receiving branches. In addition, the specific UE capability may be a UE capability to support either FD-FDD (Full Duplex-Frequency Division Duplex) or Type A HD-FDD (Half Duplex-Frequency Division Duplex) operations in the FDD band of FR1. Furthermore, the specific UE capability may be a UE capability that supports either DL up to 64QAM (Quadrature Amplitude Modulation) or DL up to 256QAM in FR1. Furthermore, the specific UE capability may be a UE capability that does not support CA and / or DC.
[0100] 3) A UE that reports to the network that it supports the specific UE capability shown in 2) above.
[0101] In addition, the terminal 20 may also report the UE capability indicating whether the functions shown in the embodiments described later are supported. For example, the terminal 20 may also report the UE capability indicating whether the function of using an initial DL / UL-BWP different from that of a non-RedCapUE or a RedCapUE is supported. In addition, the UE that reports support for the function may be an eRedCapUE, or an eRedCapUE that supports the function as an option.
[0102] In addition, the definition of non-RedCapUE can be a UE that meets neither the definition of RedCapUE nor the definition of eRedC apUE, or a UE that supports the functions that are mandatory for a normal UE, or a UE that supports a bandwidth exceeding the maximum bandwidth supported by RedCapUE.
[0103] (Example 1)
[0104] In this embodiment, an example of realizing flexible CORESET#0 resource configuration between eRedCap UE and non-eRedCap UE is described. This embodiment is mainly a solution to the above-mentioned first problem.
[0105] (Example 1-1)
[0106] Terminal 20 may assume that CORESET#0 resources are configured for eRedCap UEs separately from the configuration for non-eRedCap UEs.
[0107] Terminal 20 may also assume that the CORESET#0 resource for eRedCapUE is specified in the standard. For example, regardless of the value set by "pdcch-configSIB1" of MIB, terminal 20 may assume that the number of RBs is 24, the number of symbols is 2 or 3, and the RB offset is any one of 0 / 1 / 2 / 3 / 4 for CORESET#0 resource. In addition, the above-mentioned number of RBs, number of symbols, and number of RB offsets are examples and may be other numbers.
[0108] Terminal 20 may assume that different CORESET#0 resources are notified between eRedCap UE and non-eRedCap UE in the same CORESET#0 resource table. For example, it may assume that resources for eRedCap UE are newly specified in the reserved row.
[0109] For example, terminal 20 may assume that Figure 3 The reserved (Reserved) row of the CORESET#0 resource table shown specifies the CORESET#0 resource with 24 RBs.
[0110] In addition, the terminal 20 may also be configured to Figure 5 The reserved row of the CORESET#0 resource table shown in FIG. 1 specifies a CORESET#0 resource with 24 RBs.
[0111] Fig.11 This is the first figure for explaining the resource configuration of CORESET#0 in Example 1-1 of the embodiment of the present invention. Fig.11 Shown in Figure 5 The reserved (Reserved) rows, i.e. rows 9 to 15, of the CORESET#0 resource table shown define an example of CORESET#0 resources with 24 RBs.
[0112] In addition, the terminal 20 may also be configured to Figure 8 The reserved row of the CORESET#0 resource table shown in FIG. 1 specifies a CORESET#0 resource with 24 RBs.
[0113] Fig.12 FIG. 2 is a second diagram for explaining resource configuration of CORESET#0 in Example 1-1 of the embodiment of the present invention. Fig.12 Shown in Figure 8 The reserved (Reserved) row of the CORESET#0 resource table, i.e., rows 9-15, shows an example of CORESET#0 resources with 24 RBs specified.
[0114] In addition, the number of RBs of the specified CORESERT#0 resource may be 24, or a smaller value (eg, 12, etc.).
[0115] The terminal 20 may also assume that the notification method of the CORESET#0 resource index to the eRedCapUE is any of the following options.
[0116] <Option 1>
[0117] The terminal 20 may also use the reserved bit of the MIB to notify the resource index for the eRedCapUE. Figure 2 In the case of the CORESET#0 resource table shown, it can be assumed that the reserved 2 bits are used to notify which resource among indexes 0-3 is to be used.
[0118] In addition, the terminal 20 refers to Figure 5 or Figure 8 In the case of the CORESET#0 resource table shown, it is also conceivable that the two reserved bits are used to notify whether or not to use the resources of indexes 9 to 15 newly defined in the reserved row.
[0119] <Option 2>
[0120] Terminal 20 can replace the resource notified by "pdcch-configSIB1" of MIB. For example, terminal 20 refers to Figure 2 In the case of the CORESET#0 resource table shown, when any resource in index 6-14 is notified, the number of RBs may be replaced with 24.
[0121] In addition, the terminal 20 refers to Figure 5 or Figure 8 In the case of the CORESET#0 resource table shown, the number of RBs may be replaced with 24 regardless of the notified index.
[0122] In addition, the terminal 20 refers to Figure 2 In the case of the CORESET#0 resource table shown, when any resource in index 6-14 is notified, it can be replaced with any resource in index 0-5.
[0123] In addition, the terminal 20 refers to Figure 5 or Figure 8In the case of the CORESET#0 resource table shown, when any resource in index 0-8 is notified, it can be replaced with any resource newly specified in index 9-15.
[0124] <Option 3>
[0125] Terminal 20 may perform an operation that combines the operations of option 1 and option 2.
[0126] For example, the terminal 20 can determine the CO RESET#0 resource index by combining 4 bits including the reserved 2 bits and the 2 bits (Least Significant Bit (LSB) or Most Significant Bit (MSB)) notified by "pdcch-configSIB1".
[0127] In addition, the terminal 20 may refer to the COR ESET#0 resource table which is different between the eRedCap UE and the non-eRedCap UE.
[0128] The terminal 20 may assume a 15 kHz SCS for the SCS of CORESET#0 / SIB1 regardless of the value notified by "subCarrierSpaceCommon" of the MIB.
[0129] In addition, the terminal 20 may also assume that a new CORESET#0 resource table is specified in the standard for the eRedCapUE.
[0130] Fig.13 FIG3 is a diagram for explaining the resource configuration of CORESET#0 in Example 1-1 of the embodiment of the present invention. The number of RBs of the newly configured CORESET#0 resource may be 24 or a smaller value (such as 12).
[0131] It is also conceivable that a new CORESET#0 resource table is specified in the standard for any one or more of the following combinations of {SCS of SSB, SCS of PDCCH, minimum value of CBW (Channel Band Width)}.
[0132] {15kHz, 15kHz, 5MHz}
[0133] {15kHz, 15kHz, 5 or 10MHz}
[0134] {15kHz, 15kHz, 40MHz}
[0135] {30kHz, 15kHz, 5MHz}
[0136] {30kHz, 15kHz, 5 or 10MHz}
[0137] {30kHz, 15kHz, 40MHz}
[0138] The terminal 20 may also assume that the notification method of the CORESET#0 resource index to the eRedCapUE is any of the following options.
[0139] <Option 1>
[0140] Terminal 20 may also assume that the resource index for eRedCapUE is notified by a reserved bit of MIB.
[0141] <Option 2>
[0142] The terminal 20 may also apply the resource index notified by "pdcch-configSIB1" of the MIB.
[0143] <Option 3>
[0144] Terminal 20 may also perform an operation obtained by combining the above options. For example, terminal 20 may determine the CORESET#0 resource index by combining 4 bits including 2 bits of the reserved bit and 2 bits (LSB or MSB) notified by "pdcch-configSIB1".
[0145] (Example 1-2)
[0146] Terminal 20 may assume that the setting of search space #0 is notified to eRedCap UE separately from the setting for non-eRedCap UE.
[0147] <Option 1>
[0148] Terminal 20 may conceivably notify Fig.14 The table shown shows different settings of monitoring opportunities between eRedCapUE and non-eRedCapUE.
[0149] Fig.14 This is a diagram for explaining the setting of monitoring opportunities in Example 1-2 of the embodiment of the present invention. Fig.14 This is a table showing the relationship between the parameters of the PDCCH monitoring opportunity for the Type0-PDCCH CSS set, the SS / PBCH block, and the CO RESET multiplexing mode 1 and FR1.
[0150] <Option 2>
[0151] The terminal 20 may also assume that a monitoring opportunity related to the CSS of Type0-PDCCH is newly defined for the eRedCap UE. The terminal 20 may also assume that the notification method of the monitoring opportunity configuration parameter related to the CSS of Type0-PDCCH for the eRedCap UE is any of the following options.
[0152] <Option 2-1>
[0153] Terminal 20 may also assume that the index set for the monitoring opportunity of the eRedCapUE is notified by a reserved bit of the MIB.
[0154] <Option 2>
[0155] The terminal 20 may also apply the resource index notified by "pdcch-configSIB1" of the MIB.
[0156] <Option 3>
[0157] The terminal 20 may perform an operation obtained by combining the above options. For example, the terminal 20 may determine the index of the monitoring opportunity setting for the eRedCapUE by combining the 2 bits of the reserved bit and the 2 bits (LSB or MSB) notified by "pdcch-configSIB1" to obtain 4 bits.
[0158] According to the first embodiment, CORE SET#0 resources or search space#0 are configured for eRedCap UE separately from the configuration for non-eRedCap UE. This enables flexible configuration between eRedCap UE and non-eRedCap UE.
[0159] (Example 2)
[0160] In this embodiment, an example of realizing flexible settings for eRedCapUE is described.
[0161] First, the method for determining the monitoring opportunity of the CSS of Type0-PDCCH in the past is described. The association between the SSB in multiplexing mode 1 of NR version 15 and the time slot n0 of the CSS of Type0-PDCCH is defined as follows.
[0162] n0=(O·2 μ +[i·M])mod N slot frame,μ
[0163] Here, O and M are Fig.16 The table shown is used to determine N slot frame,μ The SCS is 2 μ The number of time slots per frame in the case of .
[0164] For multiplexing mode 1, the terminal monitors two consecutive time slots (ie, n0 and n0+1 time slots). For SSB / CO RESET#0 multiplexing mode 1, n0 and n0+1 time slots are monitored.
[0165] (Example 2-1)
[0166] The terminal 20 may also assume that the frequency resources of CORESET#0 are newly defined for the eRedCapUE.
[0167] The terminal 20 may assume that the number of RBs is set to be less than 24 for the frequency resource of CORESET#0. For example, it may assume that 12 RBs are set (even at 30 kHz SCS, CORESET#0 can be received).
[0168] The terminal 20 may also assume that the aggregation level of CCEs of the CSS of Type0a-PDCCH and / or the number of PDCC H candidates for each aggregation level of CCEs are newly defined for eRedCap UE.
[0169] Fig.15 This is a diagram for explaining the setting of the number of PDCCH candidates according to Example 2-1 of the embodiment of the present invention. Fig.15 The aggregation level of CCEs of the CSS set and the maximum number of PDCCH candidates per aggregation level of CCEs set by "searchSpaceSIB1" for eRedCapUE are set. Terminal 20 may assume that the aggregation level (AL) of CCEs of the CSS for Type 0-PDCCH supports AL1 and / or AL2.
[0170] (Example 2-2)
[0171] Terminal 20 can assume reception of the PDCCH in CORESET#0 exceeding 5 MHz.
[0172] <Option 1>
[0173] The terminal 20 receives a portion of punctured PDCCH / PDCCH-DMRS with a 5 MHz bandwidth.
[0174] <Option 2>
[0175] It is also possible that the terminal 20 receives the PDCCH in multiple times as specified in the standard. For example, regarding the CSS of type0-PDCCH in CORESET#0, the terminal 20 can receive the PDCCH through multiple different resources and synthesize them inside the terminal 20 to process them as one PDCCH reception.
[0176] Fig.16 FIG1 is a diagram for explaining a PDCCH reception method of Example 2-2 of an embodiment of the present invention. In this case, the terminal 20 can receive the PDCCH through two different resources for the CSS of type0-PDCCH in CORESET#0 and synthesize them inside the terminal 20, thereby processing them as one PDCCH reception.
[0177] Fig.17 FIG. 2 is a diagram for explaining a PDCCH reception method of Example 2-2 of an embodiment of the present invention. In this case, the terminal 20 can receive the PDCCH through four different resources for the CSS of type0-PDCCH in CORESET#0 and synthesize them inside the terminal 20, thereby processing them as one PDCCH reception.
[0178] In the case of a cell accommodating eRedCap UE (including a case where some of the accommodated terminals 20 are eRedCap UEs), the base station 10 may transmit a PDCCH having the same search space ID a plurality of times.
[0179] In addition, regarding the monitoring opportunity related to the CSS of Type0-PDCCH, the terminal 20 may also assume that it is sent in two or more time slots. The terminal 20 may also assume that in addition to the n0 time slot related to the ID of the received SSB, it is specified in the standard that one or more time slots are additionally monitored. In this case, the n0 time slot and the additionally monitored time slot may not be continuous.
[0180] Option 2 is not limited to PDCCH reception in CORESET#0, but can also be applied to PDCCH reception in other CORESETs.
[0181] The terminal 20 is not limited to being applied to PDCCH reception related to the CSS of type0-PDCCH, and may also be applied to other SSs (for example, at least any one of the CSS / USS of type0 / 0A / 1 / 2 / 3).
[0182] Fig.18 FIG3 is a third figure for explaining the PDCCH reception method of Embodiment 2-2. Fig.18 Show N symb COR ESETAn example of an interleaving scheme for PDCCH when L=3 and L=6.
[0183] Fig.19 FIG. 4 is a diagram for explaining the PDCCH receiving method of Embodiment 2-2. Fig.18 as well as Fig.19 As shown, the terminal 20 can restore the signals obtained through two receptions into one PDCCH.
[0184] Furthermore, the terminal 20 may assume non-interleaved mapping for the PDCCH in CORESET# 0. This can reduce the number of monitoring opportunities required to receive one entire PDCCH.
[0185] According to the second embodiment, flexible settings for eRedCapUE can be achieved.
[0186] (Example 3)
[0187] An example of implementing coverage supplementation related to PDCCH for eRedCap UE is described.
[0188] (Example 3-1)
[0189] Terminal 20 may repeatedly receive one PDCCH at different monitoring opportunities.
[0190] Fig. 20 This is a diagram for explaining a PDCCH reception method according to Example 3-1 of an embodiment of the present invention. For example, the terminal 20 may repeatedly receive a PDCCH related to a search space having the same index in four monitoring opportunities.
[0191] The terminal 20 may consider applying the actions of this embodiment only to PDCCH reception in CORESET#0, or may consider applying the actions of this embodiment to other CORESETs.
[0192] Terminal 20 may also assume that the number of repetitions of receiving the PDCCH to ensure coverage is specified in the standard or notified through a higher layer parameter. The number of repetitions received may vary depending on the type of AL / SS or the DCI format.
[0193] Fig.21 FIG. 1 is a first diagram showing the reception quality of the PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0194] Fig. 22 FIG. 2 is a diagram showing the reception quality of the PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0195] Fig.21 and Fig. 22 The simulation results of the reception quality of each AL are shown when SCS is 15kHz, CORESET 24RB, and 3 symbols, and the number of repetitions is 1, that is, when no repeated reception is performed.
[0196] Fig.23 FIG. 3 shows the reception quality of the PDCCH obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0197] Fig.24 FIG. 4 shows the reception quality of the PDCCH obtained by simulating for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0198] Fig.23 and Fig.24 The simulation results of the reception quality of each AL in the case of SCS15kHz, CORESET24RB, 3 code elements and the number of repetitions 2, that is, every 2 receptions, are shown.
[0199] Fig.25 FIG. 5 shows the PDCCH reception quality obtained by simulation for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0200] Fig.26 FIG. 6 shows the PDCCH reception quality obtained by simulating for each AL in the PDCCH reception method of Example 3-1 of the embodiment of the present invention.
[0201] Fig.25 and Fig.26 The simulation results of the reception quality of each AL in the case of SCS15kHz, CORESET24RB, 3 code elements and the number of repetitions being 4, i.e., every 4 receptions, are shown.
[0202] according to Figure 21-26 From the simulation results, as the number of repetitions increases from 1 to 2 and from 2 to 4, the accumulation of SINR is suppressed, resulting in improved reception quality.
[0203] (Example 3-2)
[0204] Terminal 20 may assume that the eRedCapUE supports CORESETs of more than 3 symbols.
[0205] Therefore, when frequency resources are limited, by increasing resources in the time direction, it is possible to support higher AL and improve reliability.
[0206] Embodiment 3-2 may be applied only to CORESET#0, and may also be applied to other CORESETs. For example, the terminal 20 may assume that the time resource of the CORESET newly introduced for the eRedCapUE is 4 and / or 6 symbols.
[0207] Fig. 27 This is a diagram for explaining the PDCCH reception method of Example 3-2 of the embodiment of the present invention. The terminal 20 may also assume that the bundle size L is extended for eRedCapUE. For example, Fig. 27 The interleaving mapping of the PDCCH in the case of extension to L=12 is shown.
[0208] According to Embodiment 3, it is possible to implement coverage supplementation related to the PDCCH for eRedCap UE.
[0209] The case where the CORESET#0 design or the PDCCH reception method of the present embodiment is applied may be limited to any one or more of the following cases (different options may be applied according to the following scenarios).
[0210] ·Serving cell, non-serving cell
[0211] The RRC connection state is idle, inactive, or connected mode.
[0212] CSS and USS of types 0, 0A, 1 (with RRC, without RRC), 2, and 3
[0213] DCI formats 0_0, 0_1, 1_0, 1_1, 0_2, 1_2, 2_0, 2_1, 2_2, 2_3, 2_4, 2_5, 2_6
[0214] (Device Structure)
[0215] Next, a functional configuration example of the base station 10 and the terminal 20 that execute the above-described processing and operation will be described.
[0216] <Base station 10>
[0217] Fig.28 1 is a diagram showing an example of the functional configuration of the base station 10. Fig.28 As shown, the base station 10 includes a transmitting unit 110 , a receiving unit 120 , a setting unit 130 , and a control unit 140 . Fig.28 The functional configuration shown is only an example. As long as the operations involved in the embodiments of the present invention can be implemented, the functional division and the names of the functional units can be arbitrary. In addition, the transmission unit 110 and the reception unit 120 can also be collectively referred to as a communication unit.
[0218] The transmitting unit 110 includes a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The receiving unit 120 includes a function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher layer information from the received signals. In addition, the transmitting unit 110 has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DCI based on PDCCH, data based on PDSCH, etc. to the terminal 20.
[0219] The setting unit 130 stores the preset setting information and various setting information to be transmitted to the terminal 20 in a storage device included in the setting unit 130 , and reads the information from the storage device as needed.
[0220] The control unit 140 schedules DL reception or UL transmission of the terminal 20 via the transmission unit 110. In addition, the control unit 140 includes a function of performing LBT. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120. In addition, the transmission unit 110 may be referred to as a transmitter, and the reception unit 120 may be referred to as a receiver.
[0221] <Terminal 20>
[0222] Fig.29 2 is a diagram showing an example of the functional structure of the terminal 20. Fig.29 As shown, the terminal 20 includes a transmitting unit 210 , a receiving unit 220 , a setting unit 230 , and a control unit 240 . Fig.29 The functional configuration shown is only an example. As long as the operation of the embodiment of the present invention can be performed, the functional division and the name of the functional unit can be arbitrary. The transmission unit 210 and the reception unit 220 can also be collectively referred to as a communication unit.
[0223] The transmitting unit 210 generates a transmission signal according to the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 receives various signals wirelessly and obtains a higher layer signal from the received physical layer signal. In addition, the receiving unit 220 has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, DCI based on PDCCH, data based on PDSCH, etc. sent from the base station 10. In addition, for example, the transmitting unit 210 can send PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to another terminal 20 as D2D communication, and the receiving unit 120 can receive PSCCH, PSSCH, PSDCH, PSBCH, etc. from another terminal 20.
[0224] The setting unit 230 stores various setting information received from the base station 10 or other terminals through the receiving unit 220 in a storage device provided by the setting unit 230, and reads it from the storage device as needed. In addition, the setting unit 230 also stores pre-set setting information. The control unit 240 controls the terminal 20. In addition, the control unit 240 includes a function of performing LBT.
[0225] The terminal of this embodiment may also be configured as the terminal shown in the following items. In addition, the following communication method may also be implemented.
[0226] <Structure Related to This Embodiment>
[0227] (Item 1)
[0228] A terminal having:
[0229] a receiving unit configured to receive a control signal in a downlink; and
[0230] The control unit assumes that the control signal related to the search space having the same index is repeatedly received in different monitoring opportunities.
[0231] (Item 2)
[0232] The terminal according to item 1, wherein:
[0233] The control unit assumes that, in the case of the control signal of a predetermined type, the control signal is repeatedly received at different monitoring opportunities.
[0234] (Item 3)
[0235] The terminal according to item 1 or 2, wherein:
[0236] The control unit assumes that a control resource set having a resource added in a time direction is individually set for the reduced-function terminal.
[0237] (Item 4)
[0238] A base station, comprising:
[0239] a sending unit that sends a control signal to a terminal; and
[0240] The control unit assumes that the control signal related to the search space having the same index is repeatedly received in different monitoring opportunities.
[0241] (Item 5)
[0242] A communication method, which is executed by a terminal, comprises the following steps:
[0243] receiving a control signal in a downlink; and
[0244] It is contemplated that a control signal related to a search space having the same index is repeatedly received in different monitoring opportunities.
[0245] According to any of the above structures, a technology can be provided for enabling a terminal in a wireless communication system to appropriately receive a control signal. According to item 1, it is conceivable that a control signal related to a search space having the same index is repeatedly received in different monitoring opportunities. According to item 2, in the case of a control signal of a predetermined type, it is conceivable that the control signal is repeatedly received in different monitoring opportunities. According to item 3, it is conceivable that a control resource set with resources added in the time direction is set separately for the function-reduced terminal.
[0246] (Hardware Structure)
[0247] The block diagram used in the description of the above embodiment ( Fig.28 as well as Fig.29 ) shows a block of functional units. These functional blocks (structural parts) are implemented by any combination of at least one of hardware and software. In addition, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using one device that is physically or logically combined, or it can be implemented by connecting two or more physically or logically separated devices directly or indirectly (for example, using wires, wirelessly, etc.) and using these multiple devices. The functional block can also be implemented by combining software with the above-mentioned one device or the above-mentioned multiple devices.
[0248] Functionally, it includes judging, deciding, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, solving, selecting, selecting, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but is not limited to these. For example, a functional block (structural unit) that enables the sending function is called a transmitting unit or a transmitter. In short, as mentioned above, there is no particular limitation on the implementation method.
[0249] For example, the base station 10 , the terminal 20 , and the like in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig.30 1 is a diagram showing an example of the hardware configuration of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 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, and the like.
[0250] In the following description, the word "device" may be replaced by "circuit", "device", "unit", etc. The hardware configuration of the base station 10 and the terminal 20 may include one or more of the devices shown in the figure, or may exclude some of the devices.
[0251] Each function in the base station 10 and the terminal 20 is implemented by the following method: predetermined software (program) is read into hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls the communication of the communication device 1004 or controls at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.
[0252] The processor 1001 controls the entire computer by, for example, running an operating system. The processor 1001 may also be composed of a central processing unit (CPU) including an interface with peripheral devices, a control device, a computing device, registers, etc. For example, the control unit 140, the control unit 240, etc. described above may also be implemented by the processor 1001.
[0253] In addition, the processor 1001 reads a program (program code), a software module, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and performs various processes accordingly. As a program, a program that causes the computer to execute at least a part of the actions described in the above-mentioned embodiments is used. For example, Fig.28 The control unit 140 of the base station 10 shown may also be implemented by a control program stored in the storage device 1002 and running in the processor 1001. In addition, for example, Fig.29 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and running in the processor 1001. Regarding the above-mentioned various processes, although it is described that the above-mentioned various processes are performed by one processor 1001, the above-mentioned various processes can also be performed simultaneously or sequentially by more than two processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via a telecommunication line.
[0254] The storage device 1002 is a computer-readable recording medium, and may be composed of at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc. The storage device 1002 may also be referred to as a register, a cache, a main memory (main storage device), etc. The storage device 1002 can store a program (program code), a software module, etc. that can be executed to implement the communication method of one embodiment of the present disclosure.
[0255] The auxiliary storage device 1003 is a computer-readable recording medium, and may be composed of at least one of an optical disk such as a CD-ROM (CompactDisc ROM), a hard disk drive, a floppy 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 stripe, etc. The above-mentioned storage medium may be, for example, a suitable medium such as a database or a server including at least one of the storage device 1002 and the auxiliary storage device 1003.
[0256] The communication device 1004 is hardware (transceiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called 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., for example, in order to realize at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex). For example, a transceiver antenna, an amplifier unit, a transceiver unit, a transmission path interface, etc. may also be realized by the communication device 1004. The transceiver unit may be installed physically or logically separately in the transmitting unit and the receiving unit.
[0257] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that implements output to the outside (e.g., a display, a speaker, an LED light, etc.). In addition, the input device 1005 and the output device 1006 may also be integrally formed (e.g., a touch panel).
[0258] In addition, the processor 1001 and the storage device 1002 and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or may be configured using different buses for each device.
[0259] In addition, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and a part or all of each functional block may be implemented by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.
[0260] Fig.31 FIG. 2 shows a structural example of a vehicle 2001. Fig.31As shown, the vehicle 2001 includes a driving 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 mode / embodiment described in the present disclosure may also be applied to a communication device mounted on the vehicle 2001, for example, may also be applied to the communication module 2013.
[0261] The driving unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also referred to as a handle), and is configured to steer at least one of the front wheels and the rear wheels according to the operation of the steering wheel operated by a user.
[0262] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2029 provided in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be referred to as an ECU (Electronic Control Unit).
[0263] As signals from various sensors 2021 to 2029, there are current signals from the current sensor 2021 for sensing the current of the motor, speed signals of the front and rear wheels obtained by the speed sensor 2022, air pressure signals of the front and rear wheels obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression amount signals obtained by the accelerator pedal sensor 2029, brake pedal depression amount signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, detection signals for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028, and the like.
[0264] The information service unit 2012 is composed of various devices such as a car navigation system, an audio system, a speaker, a television, and a radio for providing various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 provides various multimedia information and multimedia services to the passengers of the vehicle 2001 using information obtained from external devices via the communication module 2013 and the like.
[0265] The information service unit 2012 may include input devices for accepting input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.), and may also include output devices for implementing output to the outside (e.g., display, speaker, LED light, touch panel, etc.).
[0266] The driving assistance system unit 2030 is composed of various devices such as millimeter wave radar, LiDAR (Light Detection and Ranging), camera, locator (such as GNSS, etc.), map information (such as high-definition (HD) map, autonomous driving vehicle (AV) map, etc.), gyroscope system (such as IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, AI processor, etc., which are used to provide functions for preventing accidents in advance or reducing the driver's driving load, and one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 sends and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0267] The communication module 2013 can communicate with the microprocessor 2031 and the components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data with the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheel 2007, the rear wheel 2008, the axle 2009, the microprocessor 2031 and the memory (ROM, RAM) 2032 in the electronic control unit 2010, and the sensors 2021 to 29 via the communication port 2033.
[0268] The communication module 2013 can be controlled by the microprocessor 2031 of the electronic control unit 2010, and is a communication device capable of communicating with an external device. For example, various information is sent and received with the external device via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. The external device can also be, for example, a base station, a mobile station, etc.
[0269] The communication module 2013 may also transmit at least one of the signals from the various sensors 2021 to 2029 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. In addition, the electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may also be referred to as an input unit that receives input. For example, the PUSCH transmitted by the communication module 2013 may also include information based on the above input.
[0270] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device, and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be referred to as an output unit that outputs information (for example, outputs information to a display, a speaker, etc. based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).
[0271] In addition, the communication module 2013 stores various information received from the external device in the memory 2032 that can be used by the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, the steering unit 2003, the accelerator pedal 2004, the brake pedal 2005, the shift lever 2006, the front wheel 2007, the rear wheel 2008, the axle 2009, the sensors 2021 to 2029, etc. provided in the vehicle 2001 based on the information stored in the memory 2032.
[0272] (Supplementary Implementation Methods)
[0273] The above describes the embodiments of the present invention, but the disclosed invention is not limited to such embodiments, and those skilled in the art should understand various variations, modifications, substitutions, replacements, etc. In order to promote the understanding of the invention, specific numerical examples are used for description, but unless otherwise specified, these numerical values are only examples, and any appropriate value may also be used. The distinction between the items in the above description is not essential to the present invention. The matters recorded in more than two items can be combined and used as needed, and the matters recorded in a certain item can be applied to the matters recorded in other items (as long as there is no contradiction). The boundaries of the functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of the physical components. The actions of multiple functional units can be physically performed by one component, or the actions of one functional unit can be physically performed by multiple components. Regarding the processing process described in the embodiment, the order of processing can be swapped if there is no contradiction. In order to facilitate the description of the processing, the base station 10 and the terminal 20 are described using a functional block diagram, but such a device can also be implemented by hardware, software, or a combination thereof. The software that operates by the processor of the base station 10 according to the embodiment of the present invention and the software that operates by the processor of the terminal 20 according to the embodiment of the present invention may also be stored in any appropriate storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, etc.
[0274] In addition, the notification of information is not limited to the form / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high-layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals or a combination thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
[0275] The various modes / implementations described in the present disclosure may also be applied to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER3G, 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)), 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.20, UWB (Ultra-Wide Band), Band: ultra-wideband), Bluetooth (registered trademark), systems using other appropriate systems, and at least one of the next-generation systems expanded, modified, generated, and specified based on these systems. In addition, multiple systems may be combined (for example, a combination of at least one of LTE and LTE-A and 5G, etc.) for application.
[0276] The processing procedures, timings, flows, etc. of each form / implementation described in this specification may be changed in order without contradiction. For example, for the method described in this disclosure, the elements of various steps are presented in an illustrative order, but are not limited to the specific order presented.
[0277] In this specification, specific actions performed by the base station 10 are sometimes performed by its upper node according to the situation. In a network composed of one or more network nodes having the base station 10, various actions performed to communicate with the terminal 20 can be performed by at least one of the base station 10 and other network nodes other than the base station 10 (for example, MME or S-GW can be considered, but not limited to this). In the above, the case where there is only one other network node other than the base station 10 is illustrated, but the other network node can also be a combination of multiple other network nodes (for example, MME and S-GW).
[0278] The information or signals described in the present disclosure can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and can also be input or output via a plurality of network nodes.
[0279] The input or output information can be stored in a specific location (e.g., memory) or managed using a management table. The input or output information can be rewritten, updated, or appended. The output information can also be deleted. The input information can also be sent to other devices.
[0280] The determination in the present disclosure may be performed by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparison of numerical values (for example, comparison with a predetermined value).
[0281] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be interpreted broadly to refer to commands, sets of commands, codes, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions, or the like.
[0282] In addition, software, commands, information, etc. may be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these wired technology and wireless technology is included in the definition of transmission medium.
[0283] The information, signals, etc. described in the present disclosure may also be represented by any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, code elements, chips, etc. that may be involved in the above description as a whole may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.
[0284] In addition, the terms described in the present disclosure and the terms required for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may also be a signal (signaling). In addition, a signal may also be a message. In addition, a component carrier (CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, etc.
[0285] As used in this disclosure, the terms "system" and "network" may be used interchangeably.
[0286] In addition, the information, parameters, etc. described in the present disclosure may be represented by absolute values, relative values to predetermined values, or other corresponding information. For example, wireless resources may also be indicated by indexes.
[0287] The names used for the above parameters are not restrictive in any way. In addition, the formulas and the like using these parameters may sometimes differ from those explicitly disclosed in the present disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, the various names assigned to these various channels and information elements are not restrictive in any way.
[0288] In the present disclosure, the terms "base station (BS)," "wireless base station", "base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)," "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier" and the like are used interchangeably. Sometimes, the base station is also referred to as macro cell, small cell, femto cell, pico cell and the like.
[0289] A base station can accommodate one or more (for example, three) cells. 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 also provide communication services through a base station subsystem (for example, a small base station for indoor use (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a part or the entirety of the coverage area of at least one of a base station and a base station subsystem that provide communication services within the coverage area.
[0290] In the present disclosure, the base station sending information to the terminal may also be replaced by the base station instructing the terminal to control / action based on the information.
[0291] In the present disclosure, terms such as “mobile station (MS),” “user terminal,” “user equipment (UE),” and “terminal” may be used interchangeably.
[0292] For mobile stations, those skilled in the art sometimes also use the following terms: 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 appropriate terms.
[0293] 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. In addition, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and the moving speed is arbitrary. In addition, of course, it also includes the situation where the mobile body is stopping. The mobile body includes, for example, vehicles, transport vehicles, cars, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones (registered trademarks), multicopters, quadcopters, hot air balloons, and objects mounted on them, and are not limited to these. In addition, the mobile body may also be a mobile body that drives autonomously based on an operating instruction. The mobile body may be a means of transportation (for example, a car, an airplane, etc.), a mobile body that moves in an unmanned manner (for example, a drone, an autonomous driving car, etc.), or a robot (man- or unmanned). In addition, at least one of the base station and the mobile station may include 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.
[0294] In addition, the base station in the present disclosure may also be replaced by a user terminal. For example, with respect to a structure in which the communication between a base station and a user terminal is replaced by the communication between multiple terminals 20 (for example, it may also be referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), the various forms / implementations of the present disclosure may also be applied. In this case, it may also be configured that the terminal 20 has the functions possessed by the above-mentioned base station 10. In addition, the terms "uplink" and "downlink" may also be replaced by terms corresponding to the communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, etc. may also be replaced by a side channel.
[0295] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station may also have the functions of the user terminal described above.
[0296] The terms "determining" and "determining" used in the present disclosure sometimes also include a variety of actions. "Determining" and "determining" may include, for example, considering matters that have been judged, calculated, calculated, processed, derived, investigated, searched (for example, searched in a table, database or other data structure), confirmed (ascertaining) as matters that have been "judged" or "determined", etc. In addition, "determining" and "determining" may include matters that have been received (for example, receiving information), transmitted (for example, sending information), input, output, accessed (for example, accessed data in memory) as matters that have been "judged" or "determined", etc. In addition, "determining" and "determining" may include matters that have been resolved (resolving), selected (selecting), chosen (choosing), established (establishing), compared (comparing), etc. as matters that have been "judged" or "determined". That is, "judgment" and "decision" can include matters that are considered to have "judged" and "decided" certain actions. In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.
[0297] The terms "connected" and "coupled" or all variations of these terms are intended to indicate any direct or indirect connection or combination between two or more elements, and may include situations where there is one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be a physical combination or connection, a logical combination or connection, or a combination of these. For example, "access" may be used instead of "connection." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, and as some non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the wireless frequency domain, microwave region, and light (both visible and invisible) region may be used to "connect" or "couple" to each other.
[0298] The reference signal may be referred to as RS (Reference Signal) for short, or may be referred to as a pilot according to the applied standard.
[0299] The phrase "according to" used in the present disclosure does not mean "only according to" unless otherwise expressly stated. In other words, the phrase "according to" means both "only according to" and "at least according to".
[0300] Any reference to an element using the designations "first", "second", etc. used in this disclosure does not necessarily limit the number or order of these elements. These designations can be used as a simple method to distinguish between two or more elements in this disclosure. Therefore, a reference to a first element and a second element does not mean that only two elements can be taken or that the first element must precede the second element in any form.
[0301] The "unit" in the configuration of each of the above-mentioned devices may be replaced with a "section", "circuit", "device" or the like.
[0302] When the terms "include", "including" and their variations are used in the present disclosure, these terms mean inclusiveness like the term "comprising". Furthermore, the term "or" used in the present disclosure means not exclusive or.
[0303] A radio frame may be composed of one or more frames in the time domain. In the time domain, one or more frames may be referred to as subframes. A subframe may be further composed of one or more time slots in the time domain. A subframe may also be a fixed time length (e.g., 1 ms) that is not dependent on a parameter set (numerology).
[0304] A parameter set may also be a communication parameter applied to at least one of the transmission and reception of a certain signal or channel. The parameter set may, for example, represent at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame structure, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, and the like.
[0305] A slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. A slot may be a time unit based on a parameter set.
[0306] A time slot may contain multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may be composed of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in units of time greater than a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be referred to as a PDSCH (or PUSCH) mapping type B.
[0307] A radio frame, a subframe, a time slot, a mini-time slot, and a symbol all represent time units for transmitting signals. A radio frame, a subframe, a time slot, a mini-time slot, and a symbol may be referred to by other corresponding names.
[0308] For example, 1 subframe may also be referred to as a transmission time interval (TTI), multiple consecutive subframes may also be referred to as a TTI, and 1 time slot or 1 mini time slot may also be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1ms) in the existing LTE, or a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. In addition, the unit representing the TTI may not be a subframe, but may be referred to as a time slot, a mini time slot, or the like.
[0309] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station schedules the allocation of wireless resources (frequency bandwidth, transmission power, etc. that can be used in each terminal 20) to each terminal 20 in units of TTI. In addition, the definition of TTI is not limited to this.
[0310] TTI can be a transmission time unit for data packets (transport blocks), code blocks, code words, etc. after channel coding, and can also be a processing unit for scheduling, link adaptation, etc. In addition, when TTI is given, the time interval (e.g., the number of symbols) to which the transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.
[0311] In addition, when 1 time slot or 1 mini time slot is called TTI, more than one TTI (ie, more than one time slot or more than one mini time slot) can constitute the minimum time unit of scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of scheduling can be controlled.
[0312] A TTI with a time length of 1 ms may also be referred to as a normal TTI (TTI in LTE Rel.8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub time slot, a time slot, etc.
[0313] In addition, for long TTI (e.g., normal TTI, subframe, etc.), it can be replaced with a TTI with a time length exceeding 1ms, and for short TTI (e.g., shortened TTI, etc.), it can be replaced with a TTI length smaller than the long TTI and having a TTI length of more than 1ms.
[0314] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain. In the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers contained in an RB may be the same regardless of the parameter set, for example, it may be 12. The number of subcarriers contained in an RB may also be determined according to the parameter set.
[0315] In addition, the time domain of an RB may include one or more symbols, and may also be the length of 1 slot, 1 mini slot, 1 subframe, or 1 TTI. 1 TTI, 1 subframe, etc. may be composed of one or more resource blocks, respectively.
[0316] In addition, one or more RBs may also be referred to as a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, and the like.
[0317] In addition, a resource block may be composed of one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
[0318] A bandwidth part (BWP) (also referred to as a partial bandwidth, etc.) may represent a subset of contiguous common resource blocks (RBs) for a parameter set in a carrier. Here, a common RB may be identified by an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0319] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be set for the terminal 20 within one carrier.
[0320] At least one of the set BWPs may be active, and it is not assumed that the terminal 20 transmits and receives a predetermined signal / channel outside the activated BWP. In addition, "cell", "carrier" and the like in the present disclosure may be replaced with "BWP".
[0321] The above structures of radio frames, subframes, time slots, mini-time slots, and symbols are only examples. For example, the number of subframes included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP: Cyclic Prefix) length, etc. can be changed in various ways.
[0322] In the present disclosure, when an article is added by translation, such as a, an, and the in English, for example, the present disclosure may also include a case where the noun following the article is in plural form.
[0323] In the present disclosure, the term "A and B are different" may also mean "A and B are different from each other". In addition, the term may also mean "A and B are different from C, respectively". The terms "separate" and "combined" may also be interpreted in the same way as "different".
[0324] Each form / implementation described in the present disclosure may be used alone or in combination, and may be switched with execution. In addition, notification of predetermined information (e.g., notification of "yes X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the predetermined information).
[0325] The present disclosure is described in detail above, but it should be clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as a modification and variation without departing from the subject matter and scope of the present disclosure as determined by the claims. Therefore, the purpose of the description of the present disclosure is to illustrate and has no limiting meaning to the present disclosure.
[0326] Description of symbols
[0327] 10 Base Stations
[0328] 110 Sending Department
[0329] 120 Receiving Department
[0330] 130 Setting department
[0331] 140 Control Department
[0332] 20Terminal
[0333] 210 Sending Department
[0334] 220 Receiving Department
[0335] 230 Setting Department
[0336] 240 Control Department
[0337] 1001 Processor
[0338] 1002 Storage device
[0339] 1003 auxiliary storage device
[0340] 1004 communication device
[0341] 1005 Input device
[0342] 1006 Output device
[0343] 2001 Vehicle
[0344] 2002Drive Department
[0345] 2003 Steering
[0346] 2004 Accelerator pedal
[0347] 2005 Brake Pedal
[0348] 2006 gear lever
[0349] 2007 front wheel
[0350] 2008 rear wheel
[0351] 2009 Axles
[0352] 2010 Electronic Control Department
[0353] 2012 Information Services Department
[0354] 2013 Communication Module
[0355] 2021 Current Sensor
[0356] 2022 Speed sensor
[0357] 2023 Air Pressure Sensor
[0358] 2024 Vehicle speed sensor
[0359] 2025 Accelerometer
[0360] 2026 Brake pedal sensor
[0361] 2027 gear lever sensor
[0362] 2028 Object Detection Sensor
[0363] 2029 Accelerator pedal sensor
[0364] 2030 Driving Assistance Systems Division
[0365] 2031 Microprocessor
[0366] 2032 Memory (ROM, RAM)
[0367] 2033 communication port (IO port)
Claims
1. A terminal comprising: a receiving unit configured to receive a control signal in a downlink; and The control unit assumes that the control signal related to the search space having the same index is repeatedly received in different monitoring opportunities.
2. The terminal according to claim 1, wherein: The control unit assumes that, in the case of the control signal of a predetermined type, the control signal is repeatedly received at different monitoring opportunities.
3. The terminal according to claim 1, wherein: The control unit assumes that a control resource set having a resource added in a time direction is individually set for the reduced-function terminal.
4. A base station, comprising: a sending unit that sends a control signal to a terminal; and The control unit assumes that the control signal related to the search space having the same index is repeatedly received in different monitoring opportunities.
5. A communication method, which is executed by a terminal, comprising the following steps: receiving a control signal in a downlink; and It is contemplated that a control signal related to a search space having the same index is repeatedly received in different monitoring opportunities.
