Communication device and communication method

Abstract

A communication device (40) includes a communication unit (41) and a control unit (45). The communication unit (41) monitors a PBCH and receives a signal. The control unit (45) decides whether a first CORESET setting or a second CORESET setting is to be applied for communication based on one or more bits included in the signal received on the PBCH.

Description

Technical Field

[0001] This disclosure relates to communication equipment and communication methods. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) studied radio access schemes and radio networks for cellular mobile communications (hereinafter also referred to as "Long Term Evolution (LTE)," "LTE-A," "LTE-A Pro," "5G," "New Radio (NR)," "New Radio Access Technology (NRAT)," "Evolved Universal Terrestrial Radio Access (EUTRA)," or "Future EUTRA (FEUTRA)"). It should be noted that in the following descriptions, LTE includes LTE-A, LTE-A Pro, and EUTRA, while NR includes NRAT and FEUTRA. In LTE and NR, base station equipment (base stations) is also referred to as Evolved Node B (eNodeB) in LTE and gNode B (gNB) in NR, and terminal equipment (mobile stations, mobile station equipment, or terminals) is also referred to as User Equipment (UE). LTE and NR are cellular communication systems in which multiple areas covered by base stations are arranged in a cellular pattern. A single base station can manage multiple cells.

[0003] NR is a next-generation radio access solution for LTE and is a different radio access technology (RAT) from LTE. NR is an access technology that can support a variety of use cases, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). NR has been studied within a technical framework addressing the use cases, requirements, deployment scenarios, and so on in these use cases.

[0004] On the other hand, there is a need to extend NR to use cases such as industrial wireless sensors, surveillance cameras, and wearable devices. These use cases require a new type of low-end device (which may be called a low-capability NR device or a lightweight NR device) that offers lower performance, device cost, and complexity compared to high-end eMBB and URLLC, while maintaining several years of battery life, but meeting higher service requirements than LPWA (e.g., LTE-M / NB-IoT). Details of low-capability NR devices are disclosed in Non-Patent Literature 1 and Non-Patent Literature 2.

[0005] Reference List

[0006] Non-patent literature

[0007] Non-patent document 1: RP-193238, “New SID on support of reduced capability NR devices”, 3GPP TSG RAN Meeting #86, December 2019

[0008] Non-Patent Document 2: RP-190844, “NR-Lite for Rel-17 Qualcomm views”, 3GPP TSG RAN Meeting #84, June 2019 Summary of the Invention

[0009] Technical issues

[0010] However, the implementation of the initial access procedure for the low-capability NR devices described above has not been studied.

[0011] Therefore, this disclosure provides a communication device and communication method that can implement the initial access procedure even when mixed with low-capability NR devices.

[0012] It should be noted that the problems or objectives mentioned above are merely one of many problems or objectives that can be solved or achieved through the various embodiments disclosed in this specification.

[0013] Solutions to the problem

[0014] According to this disclosure, a communication device is provided. The communication device includes a communication unit and a control unit. The communication unit monitors the PBCH to receive signals. The control unit determines, based on one or more bits included in the signals received on the PBCH, which of the first CORESET configuration and a second CORESET configuration to apply for communication. Attached Figure Description

[0015] Figure 1 This is an illustration showing an example of the overall configuration of a communication system according to an embodiment of the present disclosure.

[0016] Figure 2 This is a diagram illustrating an example of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block.

[0017] Figure 3 This is a diagram illustrating an example of the arrangement of SS / PBCH blocks.

[0018] Figure 4 This is a diagram illustrating an example of an Information Element (IE) of the Main Information Block (MIB).

[0019] Figure 5 This is a diagram illustrating an example of an IE for the MIB.

[0020] Figure 6 This is a diagram illustrating a configuration example of messages for the Broadcast Control Channel (BCCH) and Broadcast Channel (BCH).

[0021] Figure 7A This is a diagram showing the table used to configure the control resource set (CORESET) #0.

[0022] Figure 7B This is a diagram showing the table used for CORESET#0 configuration.

[0023] Figure 7C This is a diagram showing the table used for CORESET#0 configuration.

[0024] Figure 7D This is a diagram showing the table used for CORESET#0 configuration.

[0025] Figure 7E This is a diagram showing the table used for CORESET#0 configuration.

[0026] Figure 7F This is a diagram showing the table used for CORESET#0 configuration.

[0027] Figure 7G This is a diagram showing the table used for CORESET#0 configuration.

[0028] Figure 7H This is a diagram showing the table used for CORESET#0 configuration.

[0029] Figure 7I This is a diagram showing the table used for CORESET#0 configuration.

[0030] Figure 7J This is a diagram showing the table used for CORESET#0 configuration.

[0031] Figure 7K This is a diagram showing the table used for CORESET#0 configuration.

[0032] Figure 7L This is a diagram showing the table used for CORESET#0 configuration.

[0033] Figure 8A This is a diagram showing a table for configuring the timing of physical downlink control channel (PDCCH) monitoring for the Type 0-PDCCH CSS set.

[0034] Figure 8B This is a diagram showing the table for configuring PDCCH monitoring timing for the Type0-PDCCH CSS set.

[0035] Figure 8C This is a diagram showing the table for configuring PDCCH monitoring timing for the Type0-PDCCH CSS set.

[0036] Figure 8D This is a diagram showing the table for configuring PDCCH monitoring timing for the Type0-PDCCH CSS set.

[0037] Figure 8E This is a diagram showing the table for configuring PDCCH monitoring timing for the Type0-PDCCH CSS set.

[0038] Figure 9A This is a diagram illustrating an example of SS / PBCH block and CORESET multiplexing.

[0039] Figure 9B This is a diagram illustrating an example of SS / PBCH block and CORESET multiplexing.

[0040] Figure 9C This is a diagram illustrating an example of SS / PBCH block and CORESET multiplexing.

[0041] Figure 10 This is an illustration showing an example of an IE in the MIB of LTE.

[0042] Figure 11 This is an illustration used to describe an example arrangement of CORESET#0 according to an embodiment of the present disclosure.

[0043] Figure 12 This is a block diagram illustrating a configuration example of a base station device according to an embodiment of the present disclosure.

[0044] Figure 13 This is an illustration showing a configuration example of a terminal device according to an embodiment of the present disclosure.

[0045] Figure 14 This is an illustration used to describe a secondary PBCH indication method according to an embodiment of the present disclosure.

[0046] Figure 15 This is a diagram illustrating the correspondence between reserved bits in the PBCH and resources of the secondary PBCH according to this embodiment of the present disclosure.

[0047] Figure 16This is a diagram illustrating the correspondence between a reserved bit in the PBCH and resources in the secondary PBCH according to an embodiment of this disclosure.

[0048] Figure 17 This is an illustration used to describe a method of indicating a second CORESET#0 according to an embodiment of the present disclosure.

[0049] Figure 18 This is a diagram illustrating the correspondence between reserved bits in the PBCH and resources of the second CORESET#0 according to this embodiment of the present disclosure.

[0050] Figure 19 This is a diagram illustrating the correspondence between a reserved bit in the PBCH and a resource of the second CORESET#0 according to an embodiment of this disclosure.

[0051] Figure 20A This is an illustration showing an example of a second table according to this embodiment of the disclosure.

[0052] Figure 20B This is an illustration showing an example of a second table according to this embodiment of the disclosure.

[0053] Figure 20C This is an illustration showing an example of a second table according to this embodiment of the disclosure.

[0054] Figure 20D This is an illustration showing an example of a second table according to this embodiment of the disclosure.

[0055] Figure 20E This is an illustration showing an example of a second table according to this embodiment of the disclosure.

[0056] Figure 20F This is an illustration showing an example of a second table according to this embodiment of the disclosure.

[0057] Figure 21 This is an illustration used to describe a method of indicating CORESET#0 according to an embodiment of the present disclosure.

[0058] Figure 22 This is a diagram illustrating an example of parameters associated with a synchronization grating.

[0059] Figure 23 This is an illustration showing an example of parameters related to the synchronization grating according to an embodiment of this disclosure.

[0060] Figure 24This is an illustration showing another example of parameters related to the synchronization grating according to this embodiment of the disclosure.

[0061] Figure 25 This is an illustration showing a configuration example of a secondary PBCH according to an embodiment of this disclosure.

[0062] Figure 26 This is an illustration of an example of a multiplexing method for secondary PBCH and SS / PBCH blocks according to an embodiment of this disclosure.

[0063] Figure 27 This is an illustration of another example of a multiplexing method for secondary PBCH and SS / PBCH blocks according to an embodiment of this disclosure.

[0064] Figure 28 This is an illustration of another example of a multiplexing method for secondary PBCH and SS / PBCH blocks according to an embodiment of this disclosure.

[0065] Figure 29 This is an illustration of another example of a multiplexing method for secondary PBCH and SS / PBCH blocks according to an embodiment of this disclosure.

[0066] Figure 30 This is an illustration of another example of a multiplexing method for secondary PBCH and SS / PBCH blocks according to an embodiment of this disclosure. Detailed Implementation

[0067] Exemplary embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that components having substantially the same functional configuration are identified by the same reference numerals in this specification and the drawings, therefore overlapping descriptions of these components are omitted.

[0068] In this specification and accompanying drawings, components with substantially the same functional configuration can be distinguished by adding different letters after the same reference numerals. For example, multiple components with substantially the same functional configuration may be distinguished when necessary, such as base station devices 20A and 20B. However, when there is no particular need to distinguish each of the multiple components with substantially the same functional configuration, only the same reference numerals are given. For example, when there is no need to specifically distinguish between base station devices 20A and 20B, it may simply be referred to as base station device 20.

[0069] Each of the one or more embodiments (including examples and modified examples) described below can be implemented independently. On the other hand, at least some of the plurality of embodiments described below can be implemented in combination with at least some other embodiments where appropriate. These plurality of embodiments may include novel features different from each other. Therefore, these plurality of embodiments can contribute to achieving or solving different purposes or problems and can produce different effects.

[0070] It should be noted that the description will be presented in the following order.

[0071] 1. Introduction

[0072] 1.1 System Configuration Example

[0073] 1.2 Related Technologies

[0074] 1.3 Technical Issues

[0075] 2. Configuration examples for each device

[0076] 2.1 Configuration Example of Base Station Equipment

[0077] 2.2 Configuration Example of Terminal Device

[0078] 3. Technical Features

[0079] 3.1 SS / PBCH Block

[0080] 3.2 RMSI (SIB1)

[0081] 3.3 RACH Procedure

[0082] 3.4 Initial DL BWP

[0083] 3.5. Configuration Example of Secondary PBCH

[0084] 4. Modify the example

[0085] 5. Conclusion

[0086] <<1. Introduction>>

[0087] <1.1 System Configuration Example>

[0088] Figure 1 This is an illustration showing an example of the overall configuration of a communication system 1 according to one embodiment of the present disclosure. Figure 1As shown, the communication system 1 includes multiple base station devices 20 (20A and 20B), multiple terminal devices 40 (40A and 40B), a core network 120, and a packet data network (PDN) 130. It should be noted that the number of corresponding devices is not limited to this; for example, the number of base station devices 20 or the number of terminal devices 40 can be one.

[0089] Base station equipment 20 is a communication device that operates cell 110 and provides wireless communication services to one or more terminal devices 40 located within the coverage area of ​​cell 110. Cell 110 can operate according to any wireless communication scheme such as LTE or New Radio (NR). Base station equipment 20 is connected to core network 120. Core network 120 is connected to packet data network (PDN) 130 through gateway device (not shown). It should be noted that base station equipment 20 can be implemented as a collection of multiple physical or logical devices. For example, in one embodiment of this disclosure, base station equipment 20 is classified as a collection of devices including baseband units (BBU) and radio units (RU), and can be interpreted as a collection of these multiple devices. Additionally or alternatively, in one embodiment of this disclosure, base station equipment 20 can be any one or both of BBU and RU. BBU and RU can be connected via a predetermined interface (e.g., eCPRI). Additionally or alternatively, RU can be referred to as remote radio unit (RRU) or radio DoT (RD). Additionally or alternatively, RU can correspond to gNB distributed unit (gNB-DU) described later. Alternatively or alternatively, the BBU may correspond to the gNB central unit (gNB-CU) described later. Alternatively or alternatively, the RU may be a device integrated with an antenna. The antenna of the base station device 20 (e.g., an antenna integrated with the RU) may employ an advanced antenna system and support MIMO (e.g., FD-MIMO) or beamforming. In an advanced antenna system, the antenna of the base station device 20 (e.g., an antenna integrated with the RU) may, for example, include 64 transmit antenna ports and 64 receive antenna ports.

[0090] Furthermore, multiple base station devices 20 can be interconnected. One or more base station devices 20 can be included in a radio access network (RAN). That is, base station devices 20 can be simply referred to as RAN, RAN node, access network (AN), or node. The RAN in LTE is called Enhanced Universal Terrestrial RAN (EUTRAN). The RAN in NR is called NGRAN. The RAN in W-CDMA (UMTS) is called UTRAN. The base station device 20 in LTE is called Evolved Node B (eNodeB) or eNB. That is, EUTRAN includes one or more eNodeBs (eNBs). Furthermore, the base station device 20 in NR is called gNodeB or gNB. That is, NGRAN includes one or more gNBs. In addition, EUTRAN can include gNBs (en-gNBs) connected to the core network (EPC) in the LTE communication system (EPS). Similarly, NGRAN can include ng-eNBs connected to the core network (5G core (5GC)) in the 5G communication system (5GS). In the case of base station equipment 20 being an eNB, gNB, etc., the base station may be referred to as a 3GPP access point. In the case of base station equipment 20 being a radio access point, the base station may be referred to as a non-3GPP access point. In the case of base station equipment 20 being a gNB, the base station may be referred to as a combination of or any one of the gNB CU and gNB DU described above. The gNB CU registers multiple higher layers of the access layer (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and PDCP) used for communication with the UE. On the other hand, the gNB DU registers multiple lower layers of the access layer (e.g., RLC, MAC, and PHY). In other words, in the messages and information described later, RRC signaling (e.g., various System Information Blocks (SIBs) including the Master Information Block (MIB) and SIB1, RRCSetup messages, and RRCReconfiguration messages) can be generated by the gNB CU, while downlink control indicators (DCIs) and various physical channels (e.g., PDCCH and PBCH) described later can be generated by the gNB-DU. Alternatively, for example, in RRC signaling, some configurations such as IE:cellGroupConfig can be generated by the gNB-DU, while other configurations can be generated by the gNB-CU. These configurations can be sent and received through the F1 interface described later. Base station device 20 can be configured to communicate with another base station device 20.For example, when multiple base station devices 20 are eNBs or a combination of eNBs and en-gNBs, the base station devices 20 can be connected via the X2 interface. Alternatively, when multiple base station devices 20 are eNBs or a combination of gn-eNBs and gNBs, the devices can be connected via the Xn interface. Alternatively, when multiple base station devices 20 are a combination of gNB CUs and gNB DUs, the devices can be connected via the F1 interface described above. Messages / information (RRC signaling, DCI information, or physical channels), which will be described later, can be transmitted between multiple base station devices 20 (e.g., via the X2, Xn, or F1 interfaces).

[0091] Furthermore, as described above, base station equipment 20 can be configured to manage multiple cells. The cells provided by base station equipment 20 are referred to as serving cells. Serving cells include primary cells (PCells) and secondary cells (SCells). In the case of providing dual connectivity for a UE (e.g., terminal equipment 40) (e.g., EUTRA-EUTRA dual connectivity, EUTRA-NR dual connectivity (ENDC), EUTRA-NR dual connectivity with 5GC, NR-EUTRA dual connectivity (NEDC), or NR-NR dual connectivity), the PCell provided by the dominant node (MN) and zero or more SCells are referred to as the primary cell group. Additionally, serving cells may include PSCells (primary secondary cells or primary SCG cells). That is, in the case of providing dual connectivity for a UE, the PSCell provided by the secondary node (SN) and zero or more SCells are referred to as the secondary cell group (SCG). Unless specifically configured (e.g., the Physical Uplink Control Channel (PUCCH) on the SCell), the PUCCH is transmitted by the PCell and PSCell, not by the SCell. Radio link failures are detected in the PCell and PSCell, but not in the SCell (which is unnecessary). As described above, the PCell and PSCell are also called special cells (SpCells) because they have special roles in (multiple) serving cells. A downlink component carrier and an uplink component carrier can be associated with a cell. Furthermore, the bandwidth corresponding to a cellular system can be divided into multiple bandwidth portions. In this case, one or more bandwidth portions (BWPs) can be set in the UE, and one bandwidth portion can be used as the active BWP in the UE. In addition, the radio resources (e.g., frequency bands, parameter sets (subcarrier spacing), and time slot configurations) that can be used by the terminal device 40 can be different for each cell, each component carrier, or each BWP.

[0092] In the case that the core network 120 is an NR core network (5G core (5GC)), the core network 120 may include access and mobility management functions (AMF), session management functions (SMF), user plane functions (UPF), policy control functions (PCF) and unified data management (UDM).

[0093] In the case where the core network 120 is an LTE core network (Evolved Packet Core (EPC)), the core network 120 may include a Mobility Management Entity (MME), Serving Gateway (S-GW), PDN Gateway (P-GW), Policy and Charging Rule Function (PCRF), and Home Subscriber Server (HSS). The AMF and MME are control nodes that handle control plane signals and manage the mobility of terminal equipment 40. The UPF and S-GW / P-GW are nodes that handle user plane signals. The PCF / PCRF is a control node that implements policy-related controls, such as Quality of Service (QoS) for PDU sessions or carrier and charging. The UDM / HSS is a control node that handles subscriber data and implements service controls.

[0094] Terminal device 40 is a communication device that wirelessly communicates with base station device 20 under the control of base station device 20. For example, terminal device 40 measures downlink signals from base station device 20 and reports measurement information indicating the measurement results to base station device 20. Base station device 20 controls wireless communication with terminal device 40 based on the reported measurement information. Alternatively, terminal device 40 can send uplink signals for measurement to base station device 20. In this case, base station device 20 measures the uplink signals from terminal device 40 and controls wireless communication with terminal device 40 based on the measurement information.

[0095] As described above, base station devices 20 can send and receive information to each other using an inter-base station interface. In the case of a 5GC core network, the inter-base station interface can be an Xn interface. In the case of an EPC core network, the inter-base station interface can be an X2 interface. For example, base station device 20 sends measurement information (e.g., measurement results for a cell managed by the source base station device or for an adjacent cell) related to the terminal device 40 that is predicted to be handed over to another neighboring base station device 20. The result is a stable handover and ensures the stability of wireless communication for terminal device 40.

[0096] It should be noted that, although not in Figure 1As shown, in addition to the cellular communication surrounding communication system 1, there may be communication equipment that provides wireless communication services operating via another radio access technology (RAT), such as Wi-Fi (registered trademark) or MulteFire. Such communication equipment is typically connected to PDN 130.

[0097] Here, the terminal device 40 according to an embodiment of this disclosure includes a first terminal device 40A and a second terminal device 40B. The first terminal device 40A may be a high-end terminal device corresponding to use cases such as enhanced mobile broadband (eMBB) or ultra-reliable low-latency communication (URLLC). The first terminal device 40A may be referred to as a traditional NR device (e.g., a regular NR UE or traditional NR UE) to distinguish it from the second terminal device 40B.

[0098] Furthermore, the second terminal device 40B is a terminal device with lower performance, lower equipment cost and complexity, and lower power consumption compared to the first terminal device 40A. In other words, it has lower capabilities than the first terminal device 40A. The second terminal device 40B can be referred to as a low-capability NR device (e.g., a lightweight NR UE) to distinguish it from the first terminal device 40A.

[0099] [First Terminal Equipment]

[0100] The first terminal device 40A is a terminal device whose maximum supported receiving bandwidth is greater than a predetermined value. The predetermined value is, for example, the minimum supported receiving bandwidth (5MHz in FR1 and 50MHz in FR2).

[0101] Specifically, the supported receive bandwidth of the first terminal device 40A is determined in FR1 based on the supported operating frequency bands and subcarrier spacing within the range of 5MHz or more and 100MHz or less, and in FR2 it is within the range of 50MHz or more and 400MHz or less. For example, the first terminal device 40A supporting NR band n1 supports receive frequency bands of 5, 10, 15, and 20MHz, and the first terminal device 40A supporting NR band n41 supports receive frequency bands of 10, 15, 20, 40, 50, 60, 80, 90, and 100MHz. Furthermore, the first terminal device 40A supporting NR bands n257, n258, n260, and n261 supports receive frequency bands of 50, 100, 200, and 400MHz.

[0102] In the FR1 case, the first terminal device 40A supports at least two receiving antennas in a frequency band of 2.5 GHz or less. Furthermore, in the FR1 case, the first terminal device 40A supports at least four receiving antennas in a frequency band above 2.5 GHz. Additionally, the first terminal device 40A supports 4-layer MIMO in a frequency band above 2.5 GHz.

[0103] The first terminal device 40A supports full-duplex communication in frequency division duplex (FDD).

[0104] User Equipment (UE) processing time is determined based on UE processing capabilities. Two types of processing capabilities are defined in the first terminal device 40A: UE processing capability 1 and UE processing capability 2. UE processing capability 1 defines the default processing capability of the terminal device 40 (NR device). Furthermore, UE processing capability 2 defines a higher processing capability than UE processing capability 1.

[0105] [Second Terminal Device]

[0106] The second terminal device 40B, for example, has a narrower supported bandwidth than the first terminal device 40A. In the case of FR1, the second terminal device 40B supports a receive band with a bandwidth narrower than 100MHz. In the case of FR2, the second terminal device 40B supports a receive band with a bandwidth narrower than 200MHz. That is, the second terminal device 40B is a terminal device whose maximum supported receive bandwidth is a predetermined value or less. The predetermined value is, for example, the minimum supported receive bandwidth of the first terminal device 40A (5MHz in FR1 and 50MHz in FR2).

[0107] For example, in FR1, the upper limit for the second terminal device 40B supporting a subcarrier spacing (SCS) (parameter set) of 15 kHz is a bandwidth of 5 MHz or 10 MHz. For example, in FR1, the upper limit for the second terminal device 40B supporting a subcarrier spacing of 30 kHz is a bandwidth of 10 MHz or 20 MHz. For example, in FR2, the upper limit for the second terminal device 40B supporting a subcarrier spacing of 60 kHz or 120 kHz is 50 MHz.

[0108] Furthermore, the second terminal device 40B has fewer supporting antennas than the first terminal device 40A. For example, the second terminal device 40B supports one receiving antenna in FR1.

[0109] The second terminal device 40B, for example, supports half-duplex communication in FDD.

[0110] The second terminal device 40B, for example, has a longer UE processing time or a lower UE processing capability than the first terminal device 40A. That is, a lower processing capability than the previously described UE processing capability 1 can be applied in the second terminal device 40B. Alternatively, a longer processing time can be allowed in the second terminal device 40B for the previously described UE processing capability 1.

[0111] As one use case for such a low-capacity second terminal device 40B, consider, for example, its application in industrial wireless sensors that report environmental information such as temperature, humidity, and atmospheric pressure. Alternatively, consider its application in surveillance cameras for video monitoring in smart cities or factories. Furthermore, consider its application in wearable devices such as smartwatches, smart rings, or medical / healthcare devices. The second terminal device 40B can also be used in smart home devices.

[0112] <1.2 Related Technologies>

[0113] The following describes the technology related to the initial access (cellular connection) procedure in a communication system that includes only the first terminal device 40A and not the second terminal device 40B (hereinafter also referred to as a conventional communication system).

[0114] Figure 2 This is an illustration of an example of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block. The SS / PBCH (SSB block) comprises the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Physical Broadcast Channel (PBCH), and Demodulation Reference Signal (DMRS) for the PBCH. The PSS and SSS have 127 sequences and are arranged in 127 REs. The PSS is placed at the first symbol of the SS / PBCH block, and the SSS is placed at the third symbol. The PBCH is placed at the second and fourth symbols. The PBCH is arranged in 20 Physical Resource Blocks (PRBs) for the second and fourth symbols, and in the first four and last four PRBs of the SS / PBCH block for the third symbol.

[0115] The MIBs in SS / PBCH blocks with the same center frequency are identical. On the other hand, the MIBs of SS / PBCH blocks with different center frequencies can be different from each other.

[0116] Furthermore, multiple SS / PBCH blocks are placed on the same center frequency. A different SS / PBCH block index is assigned to each SS / PBCH block. The first terminal device 40A can assume that SS / PBCH blocks with the same block index placed on the same center frequency are quasi-common bits (QCLs). On the other hand, the terminal device 40 does not need to assume that SS / PBCH blocks placed on different center frequencies or SS / PBCH blocks with different block indices placed on the same center frequency are quasi-common bits (QCLs).

[0117] Figure 3 This is a diagram illustrating an example arrangement of SS / PBCH blocks. As an example, the SS / PBCH is arranged as follows: Figure 3 The layout is shown in the diagram. One or more SS / PBCH blocks are arranged in a half-frame (5 msec). Multiple SS / PBCH blocks in a half-frame are also referred to as an SS / PBCH block burst or an SSB burst.

[0118] The maximum number of SS / PBCH blocks arranged in a half-frame is defined as Lmax, which is four in FR1 and 3 GHz or less, eight in FR1 and 3 GHz or more, ten in unlicensed bands and 15 kHz SCS, twenty in unlicensed bands and 30 kHz SCS, and sixty-four in FR2. In other words, the number of multiple SSBs in an SSB burst can depend on the subcarrier spacing associated with the frequency band.

[0119] The first symbol of one or more SS / PBCH blocks is arranged in the following symbols.

[0120] Case A: {2, 8} + 14 × n

[0121] Case B: {4, 8, 16, 20} + 28 × n

[0122] Case C: {2, 8} + 14 × n

[0123] Case D: {4, 8, 16, 20} + 28 × n

[0124] Case E: {2, 8} + 14 × n

[0125] Here, n is any positive number.

[0126] The period of the SS / PBCH block burst can be set to any of 5, 10, 20, 40, 80, and 160 ms. On the other hand, in the initial cell selection, the terminal device 40 assumes that the period of the SS / PBCH block burst is 20 ms.

[0127] In the future, new frequency bands above 52600MHz (e.g., a 100GHz band) and frequency ranges (e.g., FR3) may be defined. In this case, due to the need for further beam narrowing to cover the same geographical area, 64 may not be sufficient for the maximum number of SSBs (Lmax) in a single SSB burst. For example, in a 100GHz band, Lmax = 64 is insufficient, and Lmax can be greater than 64, such as 128 or 256. Some embodiments, including this one, are also applicable to frequency ranges (e.g., FR3) and Lmaxes of 64 or more that may be defined in the future.

[0128] Figure 4 and 5 This is a diagram illustrating an example of an Information Unit (IE) in a MIB. The MIB in an NR consists of 23 bits. The MIB includes... Figure 4 and 5 The image shows IE.

[0129] Figure 6 This is a diagram illustrating a configuration example of messages on the Broadcast Control Channel (BCCH) and Broadcast Channel (BCH). The BCCH is mapped to the BCH. (Example...) Figure 6 As shown, BCH includes either MIB or messageClassExtension. In the case of MIB, BCH data consists of 24 bits (23 bits of MIB + 1 bit of the selected value).

[0130] In addition to the BCH data, the PBCH payload includes the first to fourth least significant bits (LSB) of the system frame number (SFN) and half-frame bits.

[0131] Furthermore, when Lmax is 64 (i.e., in FR2), the PBCH payload includes the fourth to sixth synchronization signal / PBCH block (SSB) indices, and the remainder (i.e., in FR1) includes K. SSB The most significant bit (MSB) and two reserved bits.

[0132] In NR, the remaining Minimal System Information (RMSI) (SIB1) is transmitted on the Physical Downlink Shared Channel (PDSCH) and the PDCCH that schedules the PDSCH. The PDCCH is arranged in the search space of the Type 0-PDCCH CSS set. In addition, a CRC scrambled with SI-RNTI is added to the PDCCH.

[0133] During initial cellular access (including cell search, cell selection / reselection, random access procedure, RRC connection establishment procedure, etc.), the terminal device 40 (UE) implements the configuration of the control resource set (CORESET) #0 (the CORESET for the Type 0-PDCCH search space set) and the Type 0-PDCCH CSS set through the MIB. Specifically, the terminal device 40 (UE) receives the SSB and also receives the MIB mapped to the PBCH included in the SSB. The CORESET #0 configuration and the PDCCH monitoring timing configuration for the Type 0-PDCCHCSS set are performed through the 8-bit PDCCH-ConfigSIB1 included in the MIB.

[0134] Figures 7A to 7L This is a diagram showing the table used for CORESET#0 configuration. Notifications regarding the CORESET#0 configuration via MIB are based on indexes and... Figures 7A to 7L The table shown in the figure indicates the SS / PBCH block and CORESET multiplexing mode, the number of resource blocks (RBs), the number of symbols, and the resource block offset from the SS / PBCH block of CORESET#0.

[0135] Figures 8A to 8E This is a diagram illustrating the table for configuring PDCCH monitoring timing for the Type0-PDCCH CSS set. Notifications regarding the PDCCH monitoring timing configuration for the Type0-PDCCH CSS set via MIB notifications are based on index and... Figure 8A The following items are indicated by the table shown in 8L: the value O indicating the starting slot for PDCCH monitoring, the number of search space sets in the slot, the value M indicating the relationship between the SS / PBCH block and the PDCCH monitoring time, and the first symbol index of the Type0-PDCCH CSS set.

[0136] Here we will describe an example of SS / PBCH block and CORESET multiplexing (SS / PBCH block and CORESET multiplexing mode). Figures 9A to 9C This is an example used to describe the multiplexing of SS / PBCH blocks and CORESET. For example... Figures 9A to 9C As shown, three SS / PBCH blocks and CORESET multiplexing modes are defined.

[0137] exist Figure 9A In Mode 1 shown, the SS / PBCH block and the PDSCH carrying CORESET#0 and SIB1 are multiplexed via Time Division Multiplexing (TDM). Figure 9BIn Mode 2 shown, the SS / PBCH block and CORESET#0 are multiplexed via TDM, and the SS / PBCH block and the PDSCH carrying SIB1 are multiplexed via Frequency Division Multiplexing (FDM). Figure 9C In Mode 3 shown, the SS / PBCH block and CORESET#0 are multiplexed by FDM, and the SS / PBCH block and the PDSCH carrying SIB1 are multiplexed by FDM.

[0138] It should be noted that after cellular connection is established (e.g., after transitioning to RRC-connected in PCell), the settings of CORESET#0 configuration and / or Type0-PDCCH CSS set can be overwritten via dedicated RRC signaling (i.e., RRCSetup message or RRCReconfiguration message).

[0139] In LTE, terminal devices capable of wide-bandwidth reception and terminal devices capable of narrow-bandwidth reception (called machine-type communication (MTC) terminals) can coexist in a single cell (e.g., the serving cell).

[0140] Such an MTC terminal may not be able to receive PDCCH segments that can be received by terminal devices capable of wide bandwidth reception. Therefore, in LTE, notification of receivable PDCCH segments (M-PDCCH segments) for MTC terminals is made using spare bits prepared in the PBCH.

[0141] Figure 10 This is an illustration of an example of the IE (Interface) of the MIB (Medium-Input Module) in LTE. Specifically, a terminal device capable of wide-bandwidth reception obtains dl-Bandwidth, phich-Config, and systemFrameNumber. On the other hand, an MTC terminal obtains schedulingInfoSIB1-BR in addition to dl-Bandwidth, phich-Config, and systemFrameNumber, and identifies the M-PDCCH segment.

[0142] <1.3 Technical Issues>

[0143] As described above, it is desirable for a communication device to have a first terminal device 40A as a legacy device and a second terminal device 40B with low capability to coexist therein. The coexistence mentioned here means that the second terminal device 40B can also connect to the cell / carrier to which the first terminal device 40A is connected, and can provide both services in the same cell / carrier using multiplexing of orthogonal and / or non-orthogonal resources such as time, frequency and space.

[0144] At this point, the second terminal device 40B is unable to implement the initial access procedures (including cell search, cell selection / reselection, random access procedures, RRC connection establishment procedures, etc.) in order to implement cellular connectivity simply by adding the low-capability second terminal device 40B to the traditional communication system.

[0145] For example, if the second terminal device 40B uses a bandwidth wider than the maximum supported receiving bandwidth to provide information related to initial access, the second terminal device 40B may have difficulty receiving the information.

[0146] For example, CORESET#0 (a CORESET for the Type 0-PDCCH search space set) is configured via MIB to receive the basic information (Minimum System Information (MSI)) necessary for cellular connectivity. In conventional communication systems, if the subcarrier spacing is 15 kHz, up to 96 PRBs can be used to configure CORESET#0. On the other hand, the second terminal device 40B has difficulty receiving CORESET#0 configured with a number of PRBs greater than the maximum supported bandwidth. Specifically, with a maximum supported bandwidth of 5 MHz, the second terminal device 40B has difficulty receiving CORESET#0 configured with a number of PRBs greater than 24. Specifically, with a maximum supported bandwidth of 1.6 MHz, the second terminal device 40B has difficulty receiving CORESET#0 configured with a number of PRBs greater than 6. Specifically, with a maximum supported bandwidth of 200 kHz, the second terminal device 40B has difficulty receiving CORESET#0 configured with a number of PRBs greater than 1.

[0147] Furthermore, for example, when CORESET#0 is shared by both the first terminal device 40A and the second terminal device 40B, its bandwidth is limited to 24 PRBs. Here, since the first terminal device 40A requires resources corresponding to 96 PRBs to receive the information necessary for the cellular connection, the time domain resources are increased due to the limitation of resources in the frequency domain. As a result, the time for the first terminal device 40A to receive the information necessary for the cellular connection becomes longer, and latency issues occur. Therefore, it is necessary to configure the bandwidth of CORESET#0 independently in each of the first terminal device 40A and the second terminal device 40B.

[0148] Here, for example, similar to LTE described above, consider a method that uses spare bits prepared in the PBCH to notify the second terminal device 40B of the PDCCH segments receivable by using spare bits independently of the first terminal device 40A. However, it is difficult to notify the second terminal device 40B of the resource information of the PDCCH segments using only one spare bit in the MIB of the PBCH included in the NR.

[0149] - Overview of the proposed technologies

[0150] Figure 11 This is an illustration used to describe an example arrangement of CORESET#0 according to an embodiment of this disclosure. In the technology of this disclosure, such as Figure 11 As shown, a first CORESET#0 (an example of a first CORESET configuration) applied to a first terminal device 40A and a second CORESET#0 (an example of a second CORESET configuration) applied to a second terminal device 40B are defined.

[0151] The first CORESET#0 is configured using up to 96 PRBs that can be received by the first terminal device 40A. On the other hand, the second CORESET#0 is configured using up to 24 PRBs that can be received by the second terminal device 40B.

[0152] In the technology of this disclosure, terminal device 40 determines whether to apply a first CORESET#0 or a second CORESET#0 based on one or more bits included in the signal received by monitoring the PBCH.

[0153] Alternatively, a primary PBCH for specifying the first CORESET#0 and a secondary PBCH for specifying the second CORESET#0 can be provided, and the first terminal device 40A can monitor the primary PBCH, while the second terminal device 40B can monitor the secondary PBCH. That is, the first terminal device 40A, which monitors the primary PBCH to receive signals, communicates by applying the first CORESET#0, and the second terminal device 40B, which monitors the secondary PBCH to receive signals, communicates by applying the second CORESET#0.

[0154] <2. Configuration examples for each device>

[0155] <2.1 Configuration Example of Base Station Equipment>

[0156] The configuration of base station device 20 will be described next. Figure 12This is an illustration showing a configuration example of a base station device 20 according to an embodiment of the present disclosure. The base station device 20 is a communication device (wireless system) that implements wireless communication with a terminal device 40. The base station device 20 is an information processing device.

[0157] The base station equipment 20 includes a wireless communication unit 21, a storage unit 22, a network communication unit 23, and a control unit 24. It should be noted that... Figure 12 The configuration shown is a functional configuration; the hardware configuration may differ. Furthermore, the functionality of base station equipment 20 can be distributed and implemented across multiple physically separate devices.

[0158] The wireless communication unit 21 is a wireless communication interface for communicating with other communication devices (such as terminal device 40 and another base station device 20). The wireless communication unit 21 operates under the control of the control unit 24. The wireless communication unit 21 can support multiple radio access schemes. For example, the wireless communication unit 21 can support both NR and LTE. The wireless communication unit 21 can support another cellular communication scheme, such as W-CDMA or cdma2000. Furthermore, in addition to cellular communication schemes, the wireless communication unit 21 can support wireless LAN communication schemes. Of course, the wireless communication unit 21 may only support one radio access scheme.

[0159] The wireless communication unit 21 includes a receiving processing unit 211, a transmitting processing unit 212, and an antenna 413. The wireless communication unit 21 may include multiple receiving processing units 211, multiple transmitting processing units 212, and multiple antennas 413. It should be noted that when the wireless communication unit 21 supports multiple radio access schemes, each unit of the wireless communication unit 21 can be configured separately for each radio access scheme. For example, if the base station equipment 20 supports NR and LTE, the receiving processing unit 211 and the transmitting processing unit 212 can be configured separately for each of NR and LTE.

[0160] The receiving and processing unit 211 processes the uplink signal received through the antenna 413. The receiving and processing unit 211 includes a wireless receiving unit 211a, a demultiplexing unit 211b, a demodulation unit 211c, and a decoding unit 211d.

[0161] The wireless receiving unit 211a performs down-conversion, removes unnecessary frequency components, controls amplification levels, performs quadrature demodulation, converts the uplink signal into a digital signal, removes guard intervals, and extracts frequency domain signals through Fast Fourier Transform, etc. For example, suppose the radio access scheme of the base station device 20 is a cellular communication scheme such as LTE. In this case, the demultiplexing unit 211b separates the uplink channel, such as the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH), and the uplink reference signal from the signal output from the wireless receiving unit 211a. The demodulation unit 211c demodulates the received signal using a modulation scheme such as Binary Phase Shift Keying (BPSK) or Quadrature Phase Shift Keying (QPSK) on the modulation symbols of the uplink channel. The modulation scheme used by the demodulation unit 211c can be multi-level QAM such as 16-QAM, 64-QAM, or 256-QAM. The decoding unit 211d decodes the encoded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 24.

[0162] The transmission processing unit 212 performs transmission processing of downlink control information and downlink data. The transmission processing unit 212 includes an encoding unit 212a, a modulation unit 212b, a multiplexing unit 212c, and a wireless transmission unit 212d.

[0163] Encoding unit 212a encodes the downlink control information and downlink data input from control unit 24 using encoding methods such as block coding, convolutional coding, or turbo coding. Modulation unit 212b modulates the encoded bits output from encoding unit 212a using a predetermined modulation scheme such as BPSK, QPSK, 16-QAM, 64-QAM, or 256-QAM. Multiplexing unit 212c multiplexes the modulation symbols and downlink reference signals for each channel and maps them to predetermined resource units. Wireless transmission unit 212d performs various signal processing on the signals from multiplexing unit 212c. For example, wireless transmission unit 212d performs processing such as converting to the time domain via fast Fourier transform, adding guard intervals, generating baseband digital signals, converting to analog signals, quadrature modulation, up-conversion, removing unnecessary frequency components, or power amplification. The signal generated by transmission processing unit 212 is transmitted from antenna 413.

[0164] Storage unit 22 is a storage device, such as DRAM, SRAM, flash memory, or hard disk, from which data can be read and written. Storage unit 22 serves as the storage device of base station equipment 20.

[0165] The network communication unit 23 is a communication interface used to communicate with other devices (such as another base station device 20). For example, the network communication unit 23 is a local area network (LAN) interface such as a network interface card (NIC). The network communication unit 23 can be a universal serial bus (USB) interface, including a USB host controller, USB port, etc. Furthermore, the network communication unit 23 can be a wired interface or a wireless interface. The network communication unit 23 acts as a network communication device for the base station device 20. The network communication unit 23 communicates with another device under the control of the control unit 24.

[0166] Control unit 24 is a controller that controls each unit of base station equipment 20. Control unit 24 is implemented, for example, by a processor such as a central processing unit (CPU) or a non-processing unit (MPU). For instance, control unit 24 is implemented by the processor executing various programs stored in storage devices within base station equipment 20 using RAM, etc., as a working area. It should be noted that control unit 24 can be implemented by an integrated circuit such as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA). CPUs, MPUs, ASICs, and FPGAs can all be considered controllers.

[0167] <2.2 Configuration Example of Terminal Device>

[0168] The configuration of terminal device 40 will be described next. Figure 13 This is an illustration showing a configuration example of a terminal device 40 according to an embodiment of the present disclosure. Terminal device 40 is a communication device (wireless system) that wirelessly communicates with base station device 20. Terminal device 40 is an information processing device.

[0169] The terminal device 40 includes a wireless communication unit 41, a storage unit 42, an input / output unit 44, and a control unit 45. It should be noted that... Figure 13 The configuration shown is a functional configuration; the hardware configuration may differ. Furthermore, the functions of the terminal device 40 can be distributed and implemented across multiple physically separate components.

[0170] The wireless communication unit 41 is a wireless communication interface for communicating with other communication devices (such as base station device 20 and another terminal device 40). The wireless communication unit 41 operates under the control of the control unit 45. The wireless communication unit 41 supports one or more radio access schemes. For example, the wireless communication unit 41 supports both NR and LTE. The wireless communication unit 41 may also support another radio access scheme, such as W-CDMA or cdma2000.

[0171] The wireless communication unit 41 includes a receiving processing unit 411, a transmitting processing unit 412, and an antenna 313. The wireless communication unit 41 may include multiple receiving processing units 411, multiple transmitting processing units 412, and multiple antennas 313. It should be noted that when the wireless communication unit 41 supports multiple radio access schemes, each unit of the wireless communication unit 41 can be configured separately for each radio access scheme. For example, the receiving processing unit 411 and the transmitting processing unit 412 can be configured separately for each of LTE and NR. The configuration of the receiving processing unit 411 and the transmitting processing unit 412 is similar to the configuration of the receiving processing unit 211 and the transmitting processing unit 212 of the base station device 20.

[0172] Storage unit 42 is a storage device, such as DRAM, SRAM, flash memory, or hard disk, from which data can be read and written. Storage unit 42 serves as the storage device of terminal device 40.

[0173] Input / output unit 44 is a user interface for exchanging information with a user. For example, input / output unit 44 may be an operating device for the user to perform various operations, such as a keyboard, mouse, operation keys, or touchpad. Alternatively, input / output unit 44 may be a display device such as a liquid crystal display (LCD) or an organic electroluminescent (EL) display. Input / output unit 44 may be an audio device such as a speaker or buzzer. Furthermore, input / output unit 44 may be a lighting device such as a light-emitting diode (LED) lamp. Input / output unit 44 acts as an input / output device (input device, output device, operating device, or notification device) of terminal device 40.

[0174] Control unit 45 is a controller that controls each unit of terminal device 40. Control unit 45 is implemented, for example, by a processor such as a CPU or MPU. For instance, control unit 45 is implemented by the processor executing various programs stored in storage devices within terminal device 40 using RAM, etc., as working areas. It should be noted that control unit 45 can be implemented by integrated circuits such as ASICs or FPGAs. CPUs, MPUs, ASICs, and FPGAs can all be considered controllers.

[0175] <<3. Technical Features>>

[0176] As described above, in order to allow the coexistence of a first terminal device 40A with traditional capabilities and a second terminal device 40B with low capabilities, it is necessary to define an initial access procedure that can be implemented by both the first terminal device 40A and the second terminal device 40B.

[0177] <3.1, SS / PBCH Block>

[0178] Therefore, in the embodiments of this disclosure, the first terminal device 40A applies a first CORESET configuration, and the second terminal device 40B applies a second CORESET configuration, thereby enabling terminal devices 40 with different capabilities to connect to the same cell.

[0179] Here, terminal device 40 obtains information for receiving CORESET#0 by receiving an SS / PBCH block. Accordingly, terminal device 40 receives CORESET#0. To enable the first terminal device 40A to receive the first CORESET#0 and the second terminal device 40B to receive the second CORESET#0 as in this embodiment, a method (common SS / PBCH block) is used: wherein the first and second terminal devices 40A and 40B respectively receive the first CORESET#0 and the second CORESET#0 by using an SS / PBCH block. Alternatively, a method (separate SS / PBCH block) can also be envisioned: wherein the first terminal device 40A receives the first SS / PBCH block for receiving the first CORESET#0, and the second terminal device 40B receives the second SS / PBCH block.

[0180] <Common SS / PBCH block>

[0181] First, the case where the first and second terminal devices 40A and 40B use a common SS / PBCH block will be described.

[0182] (Secondary PBCH)

[0183] In this case, a method can be envisioned for sending a secondary PBCH to transmit an additional MIB to the second terminal device 40B. The secondary PBCH includes information for at least receiving an RMSI (SIB1) for the second terminal device 40B.

[0184] Examples of receiving RMSI information for the second terminal device 40B include the second CORESET configuration (CORESET#0 for the second terminal device 40B and CORESET for the Type0-PDCCH CSS set for the second terminal device 40B), the second Type0-PDCCH CSS set configuration, and so on.

[0185] In addition, the physical configuration and information of the secondary PBCH will be described later.

[0186] The secondary PBCH indication method will be described here. Figure 14 This is an illustration used to describe a secondary PBCH indication method according to an embodiment of the present disclosure.

[0187] like Figure 14As shown, the first CORESET#0 is indicated by the SS / PBCH block, and the first terminal device 40A receives the SS / PBCH block to obtain information for receiving the first CORESET#0.

[0188] Furthermore, the secondary PBCH is indicated by one or more bits included in the SS / PBCH block, and the second terminal device 40B receives the one or more bits included in the SS / PBCH block to obtain information for receiving the secondary PBCH. Additionally, the second CORESET#0 is indicated by the secondary PBCH, and the second terminal device 40B receives the secondary PBCH to obtain information for receiving the second CORESET#0.

[0189] More specifically, the presence of a secondary PBCH is indicated, for example, by a spare bit (reserved bit or extended bit) included in the PBCH payload or MIB. For instance, the presence of a secondary PBCH is indicated by a spare bit included in the MIB. When transmitting a secondary PBCH corresponding to an SSB, base station device 20 uses the spare bit to indicate the presence of the secondary PBCH. Terminal device 40 determines whether the secondary PBCH has been transmitted based on the spare bit. When indicated by the spare bit, second terminal device 40B attempts to receive the secondary PBCH.

[0190] Additionally or alternatively, when the maximum number of SSBs is 4, 8, or 10, the presence of a secondary PBCH or its resources is indicated by reserved bits included in the PBCH.

[0191] Specifically, when the maximum number of SSBs (Lmax) is 4 or 8, based on Figure 15 The table shown indicates the four resources of the minor PBCH through the reserved bits of the PBCH. Figure 15 This is a table illustrating the correspondence between reserved bits in the PBCH and resources of the secondary PBCH according to embodiments of this disclosure.

[0192] like Figure 15 As shown, four resources are indicated by two reserved bits, namely secondary PBCH resources A to D.

[0193] Furthermore, when the maximum number of SSBs (Lmax) is 10, based on Figure 16 The table shown indicates the two resources of the secondary PBCH through the reserved bits of the PBCH. Figure 16 This is a table illustrating the correspondence between reserved bits in the PBCH and resources of the secondary PBCH according to embodiments of this disclosure.

[0194] like Figure 16As shown, two resources, namely secondary PBCH resources A and B, are indicated by a reserved bit.

[0195] Candidates for resources for the secondary PBCH can be indicated by a combination of the following: the period of the secondary PBCH, the time offset (frame offset, half-frame offset, slot offset, etc.) and / or frequency offset (PRB offset or subcarrier offset) of the resources with the SSB or the resources of the first CORESET#0 and Type0-PDCCH CSS sets.

[0196] The candidate resources for the secondary PBCH can be overridden via RRC signaling (e.g., arbitrary system information (SIB-X), RRCSetup message, or RRCReconfiguration message). That is, secondary PBCH resources A to D are configured via RRC signaling, and the second terminal device 40B, upon receiving the RRC signaling, refers to the configured positions of secondary PBCH resources A to D. On the other hand, the default positions of the candidate resources for the secondary PBCH are pre-defined, and the second terminal device 40B refers to these default positions before setting them via RRC signaling.

[0197] Here, base station device 20 transmits a secondary PBCH, but this disclosure is not limited thereto. For example, if the first CORESET#0 is configured to fall within the supported bandwidth of the second terminal device 40B by including CORESET#0 in the secondary PBCH, it is not necessary to transmit the secondary PBCH. In this case, the absence of the secondary PBCH is indicated. Or, the presence of the secondary PBCH is not indicated. Therefore, the second terminal device 40B monitors the PDCCH of CORESET#0 and obtains the RMSI (SIB1) in a similar manner to the first terminal device 40A. It should be noted that in this case, the same CORESET#0 is applied to both the first terminal device 40A and the second terminal device 40B, but as will be described later, it is possible to provide a second terminal device 40B-specific RMSI (second SIB1) by making the search space, RNTI, and / or DCI different.

[0198] It should be noted that the base station device 20 notifies the first terminal device 40A of the actual transmission location of the secondary PBCH. This notification can be used for rate matching of the PDSCH of the first terminal device 40A. Specifically, this allows the first terminal device 40A to identify the resources of the secondary PBCH. During PDSCH reception, the first terminal device 40A can attempt decoding while avoiding the resources of the secondary PBCH, thereby improving PDSCH reception characteristics. It should be noted that this notification can also serve as information about the non-actual transmission location of the secondary PBCH.

[0199] As a method for notification, there exists, for example, the method using ratematchPattern. For instance, after an RRC connection, base station device 20 configures a secondary PBCH in which a resource element is arranged for the rate matching mode of the first terminal device 40A. The first terminal device 40A can recognize that the resource specified by ratematchPattern is not a physical channel addressed to the first terminal device 40A. Alternatively, if the cell to which the first terminal device 40A is connected is a TDD cell, there exists a method for notification using UL symbols or flexible symbols. In this case, the secondary PBCH is arranged in a resource where the TDD-DL-UL-config notified to the first terminal device 40A via SIB is indicated as a UL symbol. Furthermore, as a method for notification, there exists, for example, the method using SSBBurstPosition (or SSBBositionsInBurst). In this case, for example, the secondary PBCH is arranged in a resource element on which SSBs are not actually transmitted. When using SSBBurstPosition as a method for notification, SSBBurstPosition (or SSBPositionsInBurst) for SS / PBCH blocks (SSBs) including the primary PBCH and SSBBurstPosition (or SSBPositionsInBurst) indicating the arrangement of secondary PBCHs can be distinguished from each other and are included as different IEs in the RRC signaling used for notification.

[0200] (PBCH)

[0201] In addition to indicating the second CORESET#0 from the PBCH via a secondary PBCH, there is also a method of directly indicating the second CORESET#0. In this case, the base station device 20 directly indicates the existence of the second CORESET#0 and its resources.

[0202] The method for indicating the second CORESET#0 will be described here. Figure 17 This is an illustration of a method for illustrating a second CORESET#0 according to an embodiment of the present disclosure.

[0203] like Figure 17 As shown, the first CORESET#0 is indicated by the SS / PBCH block, and the first terminal device 40A receives the SS / PBCH block to obtain information for the first CORESET#0.

[0204] Furthermore, the second CORESET#0 is indicated by one or more bits included in the SS / PBCH block, and the second terminal device 40B receives one or more bits included in the SS / PBCH block to obtain information for receiving the second CORESET#0.

[0205] More specifically, the presence of a second CORESET#0 and resources is indicated by using the spare bits of the MIB and the reserved bits of the PBCH.

[0206] Similar to the case of the secondary PBCH, the presence of the second CORESET#0 is indicated by a spare bit (reserved bit or extended bit) included in the PBCH payload or MIB. For example, the presence of the second CORESET#0 is indicated by a spare bit included in the MIB. When transmitting the second CORESET#0 corresponding to the SSB, the base station device 20 uses the spare bit to indicate the presence of the second CORESET#0. The terminal device 40 determines whether the second CORESET#0 has been transmitted based on the spare bit. When indicated by the spare bit, the second terminal device 40B attempts to receive the second CORESET#0.

[0207] Furthermore, when the maximum number of SSBs is 4, 8, or 10, the resource of the second CORESET#0 is indicated by the reserved bits included in the PBCH.

[0208] Specifically, when the maximum number of SSBs (Lmax) is 4 or 8, based on Figure 18 The table shown indicates the four resources of the second CORESET#0 through the reserved bits of PBCH. Figure 18 This is a diagram illustrating the correspondence between reserved bits in the PBCH and resources of the second CORESET#0 according to an embodiment of this disclosure.

[0209] like Figure 18 As shown, four resources are indicated by two reserved bits, namely the second CORESET#0 resources A to D.

[0210] Furthermore, when the maximum number of SSBs (Lmax) is 10, based on Figure 19 The table shown indicates the two resources of the second CORESET#0 through the reserved bits of PBCH. Figure 19 This is a diagram illustrating the correspondence between reserved bits in the PBCH and resources of the second CORESET#0 according to an embodiment of this disclosure.

[0211] like Figure 19 As shown, two resources, namely the second CORESET#0 resource A and B, are indicated by a reserved bit.

[0212] Candidates for resources for the second CORESET#0 can be indicated by a combination of the following: time offsets (frame offsets, half-frame offsets, slot offsets, etc.) and / or frequency offsets (PRB offsets or subcarrier offsets) with resources of the SS / PBCH block or resources of the first CORESET#0 and the first Type0-PDCCH CSS set. As a specific example, the resources of the second CORESET#0 are arranged in the next slot of the resources of the first CORESET#0.

[0213] (Selective reading of MIB information)

[0214] Furthermore, in the first and second terminal devices 40A and 40B, there is a method for selectively reading MIB information used to send information about CORESET#0 (CORESET for Type0-PDCCH search space set) and Type0-PDCCH CSS set (PDCCH monitoring timing for Type0-PDCCH CSS set).

[0215] - Device type

[0216] First, the method by which terminal device 40 selectively reads the table to be referenced based on its device type will be described. Device type indicates whether the device has conventional capabilities or capabilities below conventional capabilities.

[0217] The first terminal device 40A with conventional capabilities refers to the table of conventional CORESET for the Type 0-PDCCH search space set and conventional PDCCH monitoring timing for the Type 0-PDCCH CSS set (hereinafter also referred to as the first table) (see...). Figures 7A to 7L ).

[0218] On the other hand, the second terminal device 40B, which has lower capabilities than the conventional one, refers to a table (also referred to as the second table below) that is different from the conventional table for the CORESET for the Type0-PDCCH search space set and / or for the PDCCH monitoring timing for the Type0-PDCCH CSS set. The details of the table will be described later.

[0219] In this way, terminal device 40 can receive CORESET#0 according to its device type by selectively reading the table to be referenced based on the device type.

[0220] -Instructions via PBCH

[0221] Alternatively, the table to be referenced by terminal device 40 may be selectively read according to the instruction via PBCH. In this case, terminal device 40 may selectively read the table to be referenced, for example, according to the spare bits included in the MIB.

[0222] Specifically, if the spare bits included in the MIB indicate reference to the second table, terminal device 40 (specifically, the first terminal device 40A and the second terminal device 40B after Rel-17) refers to the second table; otherwise, terminal device 40 (specifically, the first terminal device 40A and the second terminal device 40B after Rel-17) refers to the first table. On the other hand, the first terminal device 40A before Rel-16 refers to the first table regardless of the indication via the spare bits.

[0223] In this way, by indicating the table to be referenced via PBCH, terminal device 40 can receive the appropriate CORESET#0.

[0224] - Configuration example of the reference table

[0225] This will refer to Figures 20A to 20F Here is a configuration example to describe the second table. Figures 20A to 20F This is an illustration of an example of a second table according to an embodiment of the present disclosure.

[0226] In the table (second table) of the CORESET used for the Type0-PDCCH search space set, for all indexes, the number of PRBs is defined as equal to or less than the bandwidth supported by the second terminal device 40B.

[0227] Specifically, with the SCS of the SS / PBCH block and PDCCH at 15kHz and 15kHz respectively, the second terminal device 40B refers to a table where the number of RBs in the CORESET is set to 24 or less. As an example, the second terminal device 40B refers to... Figure 20A The table shown is shown below. It should be noted that, except for the RBs at indices 6 to 14, which have a count of 24, Figure 20A The table shown in the middle is the same as Figure 7A The table shown is the same.

[0228] With the SCS of the SS / PBCH block and PDCCH at 15kHz and 30kHz respectively, the second terminal device 40B refers to a table where the number of RBs in the CORESET is set to 12 or less. As an example, the second terminal device 40B refers to... Figure 20B The table shown is shown below. It should be noted that, except for indices 1 to 13, the number of RBs is 12. Figure 20B The table shown in the middle is the same as Figure 7C The table shown is the same.

[0229] With the SCS of the SS / PBCH block and PDCCH at 30kHz and 15kHz respectively, the second terminal device 40B refers to a table where the number of RBs in the CORESET is set to 48 or less. As an example, the second terminal device 40B refers to... Figure 20C The table shown is shown below. It should be noted that, except for the RBs at indices 6 to 8, which number 48, Figure 20C The table shown in the middle is the same as Figure 7D The table shown is the same.

[0230] With the SCS of the SS / PBCH block and PDCCH at 30kHz and 30kHz respectively, the second terminal device 40B refers to a table where the number of RBs in the CORESET is set to 24 or less. As an example, the second terminal device 40B refers to... Figure 20D The table shown is shown below. It should be noted that, except for the RBs at indices 10 to 15, which number 24, Figure 20D The table shown in the middle is the same as Figure 7E The table shown is the same.

[0231] With the SCS of the SS / PBCH block and PDCCH at 120kHz and 60kHz respectively, the second terminal device 40B references a table where the number of RBs in the CORESET is set to 48 or less. As an example, the second terminal device 40B references... Figure 20E The table shown is shown below. It should be noted that, except for the RB count of indices 10 to 11, which is 48, Figure 20E The table shown in the middle is the same as Figure 7I The table shown is the same.

[0232] With the SCS of the SS / PBCH block and PDCCH at 120kHz and 120kHz respectively, the second terminal device 40B refers to a table where the number of RBs in the CORESET is set to 24 or less. As an example, the second terminal device 40B refers to... Figure 20F The table shown is shown below. It should be noted that, except for indices 2, 3, 6, and 7, where the number of RBs is 24, Figure 20F The table shown in the middle is the same as Figure 7J The table shown is the same.

[0233] (CORESET#0 setup)

[0234] It is desirable to configure the first CORESET#0 and the second CORESET#0 to not overlap with each other. In the case of overlap, the base station device 20 can only transmit the first CORESET#0 or the second CORESET#0 in a time slot. Therefore, for example, it is desirable to configure the first CORESET#0 and the second CORESET#0 to not overlap with each other in time or frequency.

[0235] -Frequency axis

[0236] For example, when the first CORESET#0 and the second CORESET#0 are configured to not overlap with each other on the frequency axis, the base station device 20 applies a common offset (RB) to the first CORESET#0 and the second CORESET#0.

[0237] Alternatively, the table can be defined such that the offset (RB) of the table for the CORESET used in the Type0-PDCCH search space set is different between the first CORESET#0 and the second CORESET#0. In this case, a frequency offset that does not overlap with the first CORESET#0 is defined in the second table.

[0238] -Timeline

[0239] For example, when the first CORESET#0 and the second CORESET#0 are configured to not overlap with each other on the time axis, the base station device 20 applies a common time slot offset.

[0240] Alternatively, the table can be defined such that the "O" in the table for the CORESET used in the Type0-PDCCH search space set is different between the first CORESET#0 and the second CORESET#0. In this case, the time slot for PDCCH monitoring timing, which is different from that of the first CORESET#0, is set in the second table.

[0241] <Individual SS / PBCH block>

[0242] The preceding example described a scenario where the first and second terminal devices 40A and 40B receive the same SS / PBCH block; however, this disclosure is not limited thereto. The first and second terminal devices 40A and 40B can receive different SS / PBCH blocks.

[0243] Figure 21 This is an illustration used to depict a method for demonstrating CORESET#0 according to embodiments of this disclosure. (As shown) Figure 21 As shown, in this case, the first terminal device 40A receives the first SS / PBCH block, and the second terminal device 40B receives the second SS / PBCH block.

[0244] The first SS / PBCH block includes information indicating the first CORESET#0, and the second SS / PBCH block includes information indicating the second CORESET#0.

[0245] As described above, a first SS / PBCH for the first terminal device 40A and a second SS / PBCH for the second terminal device 40B are transmitted, thereby enabling the first and second terminal devices 40A and 40B to receive the first CORESET#0 and the second CORESET#0, respectively.

[0246] Here, as Figure 21 As shown, it is desirable to transmit the first SS / PBCH and the second SS / PBCH at different center frequencies.

[0247] For the first SS / PBCH and the second SS / PBCH, it is desirable to introduce a connection blocking (blocking) mechanism for each of the second terminal device 40B and the first terminal device 40A.

[0248] (Synchronization grating)

[0249] As one method for preventing the first terminal device 40A from connecting to the second SS / PBCH, there is a method of arranging the second SS / PBCH in a different synchronization grating than the first terminal device 40A.

[0250] By arranging the second SS / PBCH block for the second terminal device 40B at a frequency position different from the synchronization grating of the first terminal device 40A in this way, the first terminal device 40A does not perform a cellular search on the second SS / PBCH block. Therefore, the first terminal device 40A has difficulty detecting the second SS / PBCH block.

[0251] Figure 22 This is a diagram illustrating an example of parameters associated with the synchronization grating. The first SS / PBCH block can be arranged as follows: Figure 22 The table shows the SS block frequency location.

[0252] On the other hand, a frequency offset is given to the synchronization grating of the second terminal device 40B, so that it is different from the synchronization grating of the first terminal device 40A. Specifically, for example, a value corresponding to half of the grating interval is given as the frequency offset.

[0253] Figure 23 This is an illustration showing an example of parameters related to the synchronization grating according to an embodiment of the present disclosure. A second SS / PBCH block is arranged in... Figure 23 The SS block frequency location is shown in the diagram. Figure 23In the above, a frequency offset of 600 kHz is given when the frequency range is 3000 MHz or less, and a frequency offset of 0.72 MHz is given when the frequency range is 3000 MHz or more and 24250 MHz or less.

[0254] To reduce the burden of further cellular searching on the second terminal device 40B, the grating spacing can be increased. Figure 24 This is an illustration showing another example of parameters related to the synchronization grating according to an embodiment of this disclosure. A second SS / PBCH block is arranged in... Figure 24 The SS block frequency location is shown in the diagram. Figure 24 In the context of a frequency range of 3000MHz or less, a frequency offset of 2400kHz is given, and a frequency offset of 2.88MHz is given for a frequency range of 3000MHz or more and 24250MHz or less.

[0255] (Physical Configuration)

[0256] As one method for preventing the first terminal device 40A from connecting to the second SS / PBCH block, there exists a method in which the second SS / PBCH block has a different physical configuration than the first SS / PBCH block.

[0257] -Scramble

[0258] For example, the second SS / PBCH block is scrambled in a manner different from that of the first SS / PBCH block.

[0259] As an example, suppose the scrambling sequence of the PBCH included in the second SS / PBCH block is different between the first and second SS / PBCH blocks. Because different scrambling sequences are applied, the first terminal device 40A cannot decode the PBCH included in the second SS / PBCH block. Therefore, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block.

[0260] As an example of applying different scrambling sequences, the initial value (C) generated by the scrambling sequence before or after encoding for PBCH is... init The scrambled sequences used to generate the scrambled sequences before and after encoding the main PBCH for the first terminal device 40A are different. init ) is the cellular ID. On the other hand, the initial value (C) used to generate the scrambled sequence before or after encoding the secondary PBCH for the first terminal device 40A. init This is a value that is different from the cellular ID (e.g., cellular ID + predefined offset value).

[0261] Furthermore, as another example of applying different scrambling sequences, the header of the scrambling sequence prior to the encoding of the PBCH differs between the first SS / PBCH block and the second SS / PBCH block. For instance, the header of the scrambling sequence prior to the encoding of the primary PBCH is determined by the maximum number of SFN bits in the second and third LSBs and the SS / PBCH block. On the other hand, the header of the scrambling sequence prior to the encoding of the secondary PBCH is determined by the maximum number of SFN bits in the second and third LSBs and the SS / PBCH block, along with a predetermined value.

[0262] Furthermore, as another example of applying different scrambling sequences, the header of the scrambling sequence after PBCH encoding differs between the first SS / PBCH block and the second SS / PBCH block. For instance, the header of the scrambling sequence after the primary PBCH encoding is determined by the SS / PBCH block index. On the other hand, the header of the scrambling sequence after the secondary PBCH encoding is determined by the SS / PBCH block index and a predetermined value.

[0263] By applying a scrambling sequence different from that of the first SS / PBCH block in this manner, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block.

[0264] Furthermore, as an example, a scrambling mask can be applied to the CRC to prevent the first terminal device 40A from connecting to the second SS / PBCH block. Because the CRC bits are scrambled with a predetermined mask, the first terminal device 40A cannot decode the PBCH included in the second SS / PBCH block. Therefore, it is possible to prevent the first terminal device 40A from using the second SS / PBCH to implement a cellular connection.

[0265] As an example of a CRC mask bit sequence, the base station device 20 does not apply a mask to the CRC bits of the first SS / PBCH block, but applies a predetermined mask consisting of 24 bits (e.g., 00000000000000000000001) to the CRC bits of the second SS / PBCH block.

[0266] -sequence

[0267] In addition to the scrambling described above, different sequences can be used for the PBCH DMRS of the first SS / PBCH block and the PBCH DMRS of the second SS / PBCH block, thereby preventing the first terminal device 40A from connecting to the second SS / PBCH block. By applying different sequences to the PBCH DMRS of the first SS / PBCH block and the PBCH DMRS of the second SS / PBCH block, the first terminal device 40A cannot demodulate the secondary PBCH. Therefore, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block.

[0268] As an example of applying different DMRS sequences, the initial value (C) used for DMRS sequence generation init The initial value (C) used to generate the DMRS sequence for the first terminal device 40A is different between the first SS / PBCH block and the second SS / PBCH block. init The initial value (C) used to generate the DMRS sequence for the first terminal device 40A is determined by the SS / PBCH block index and the cellular ID. init This is a value that differs from the value determined by the SS / PBCH block index and the cell ID.

[0269] By applying different DMRS sequences to the first SS / PBCH block and the second SS / PBCH block, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block.

[0270] - Synchronization signal

[0271] Furthermore, for example, by using different sequences for the synchronization signal (hereinafter referred to as the first synchronization signal) for the first terminal device 40A and the synchronization signal (hereinafter referred to as the second synchronization signal) for the second terminal device 40B, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block. By applying different sequences to the first synchronization signal (at least one of PSS and SSS) and the second synchronization signal (at least one of PSS and SSS), the first terminal device 40A cannot acquire the second synchronization signal. Therefore, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block.

[0272] As an example of applying different synchronization signal sequences, the cellular ID value differs between the first and second synchronization signals. For instance, the cellular ID for the first synchronization signal is set to any value from 0 to 1005, while the cellular ID for the second synchronization signal is set to a value of 1006 or higher.

[0273] By applying different synchronization signal sequences to the first SS / PBCH block and the second SS / PBCH block, it is possible to prevent the first terminal device 40A from connecting to the second SS / PBCH block.

[0274] (Information Notification)

[0275] As one method for preventing a first terminal device 40A from connecting to a second SS / PBCH block, there is a method for notifying the first terminal device 40A of predetermined information. Examples of the predetermined information include information about blocking the first terminal device 40A and information indicating that the second SS / PBCH block is a non-cellular defined SSB for the first terminal device 40A.

[0276] -Information regarding obstruction

[0277] For example, base station device 20 includes and notifies information about cell-barred protection for first terminal device 40A in its MIB. Specifically, the MIB for second terminal device 40B includes information about cell-barred protection for first terminal device 40A. This information about cell-barred protection is placed in the same bits as the bits containing the cell-barred protection information included in the MIB for first terminal device 40A.

[0278] When a second SS / PBCH block is received, the first terminal device 40A identifies the cellBarred of the SS / PBCH block and stops using the cellular connection of the SS / PBCH block. When a second SS / PBCH block is received, the second terminal device 40B ignores the cellBarred information of the SS / PBCH block and continues to use the cellular connection of the SS / PBCH block.

[0279] It should be noted that, apart from the information regarding the blocking (cellBarred) for the first terminal device 40A, the information for the second terminal device 40B (at least the information regarding the CORESET for the second terminal device 40B) is placed in the bits included in the MIB for the second terminal device 40B.

[0280] It should be noted that the base station device 20 can notify information about blocking through the selection bits included in the BCH.

[0281] Specifically, when the selected bits indicate that the received MIB is for the first terminal device 40A, the first terminal device 40A uses the received SS / PBCH block to implement a cellular connection. On the other hand, when the selected bits indicate that the received MIB is different from the MIB for the first terminal device 40A (for example, the MIB is for the second terminal device 40B), the first terminal device 40A does not use the received SS / PBCH block to implement a cellular connection.

[0282] On the other hand, if it is notified that the received MIB is for the second terminal device 40B, the second terminal device 40B uses the received MIB to implement cellular connectivity. Specifically, it attempts to acquire the SIB using the information about CORESET#0 included in the received MIB.

[0283] In this way, by implementing cellular connectivity based on information about the blockage, the first terminal device 40A can be prevented from connecting to the second SS / PBCH.

[0284] -Non-cellular definition SSB information

[0285] For example, base station device 20 notifies that the second SS / PBCH is information for the non-cellular defined SS / PBCH block (SSB) of the first terminal device 40A.

[0286] A non-cellular defined SSB is an SS / PBCH block that is not used for cellular connections. By notifying the second SS / PBCH block that it is a non-cellular defined SSB, the first terminal device 40A identifies the second SS / PBCH block as a non-cellular defined SSB and does not implement a cellular connection. On the other hand, the second terminal device 40B determines whether the second SS / PBCH block is a cellular defined SSB or a non-cellular defined SSB based on information different from the non-cellular defined SSB notification information.

[0287] Specifically, in FR1, K SSB In the case of >23, the first terminal device 40A identifies the detected SS / PBCH block as a non-cellular defined SS / PBCH block. In FR2, at K SSB In cases where the threshold is >11, the first terminal device 40A identifies the detected SS / PBCH block as a non-cellular defined SS / PBCH block. In this case, the first terminal device 40A determines, based on the detected MIB, that there is no CORESET#0 for the Type0-PDCCH CSS set. On the other hand, the second terminal device 40B determines, based on K... SSB Other information besides this determines whether the SS / PBCH block is a cellular defined SSB or a non-cellular defined SSB.

[0288] It should be noted that information concerning the second terminal device 40B (at least information regarding CORESET#0 for the second terminal device 40B) is placed in the second SS / PBCH block for notifying K. SSB Of the bits other than the first bit.

[0289] (Obstruction by the second terminal device)

[0290] The previous example described a method in which the first terminal device 40A could not connect to the second SS / PBCH, but similarly, it is desirable to configure the second terminal device 40B to not connect to the first SS / PBCH.

[0291] For example, if the number of PRBs in the first CORESET#0 is set to be equal to or greater than the supported bandwidth of the second terminal device 40B in the CORESET configuration, the second terminal device 40B will not connect to the first SS / PBCH.

[0292] In this scenario, assume that the second terminal device 40B is blocked from connecting to the first SS / PBCH. In this case, the second terminal device 40B performs a cellular search by moving to a grating of a different frequency than the grating arranged in the first SS / PBCH.

[0293] In other words, the number of PRBs in CORESET#0 is set to be equal to or greater than the SS / PBCH block with the supported bandwidth of the second terminal device 40B, which is the first SS / PBCH block.

[0294] <3.2、RMSI(SIB1)>

[0295] A separate SIB1 (hereinafter referred to as the second SIB1) for the second terminal device 40B can be provided, distinct from the SIB1 for the first terminal device 40A. By providing the second SIB1 separately from the first SIB1, system information different from that in the first terminal device 40A can be set in the second terminal device 40B. The provision of the second SIB1 will be described later.

[0296] (Configuration Example)

[0297] Here is a configuration example describing the parameters of the second SIB1. The second SIB1 includes some or all of the following information included in the first SIB1.

[0298] - Information about cell selection (cellSelectionInfo)

[0299] - Information about cellular access (cellAccessRelatedInfo)

[0300] - Information regarding connection establishment failure control (connEstFailureControl)

[0301] -SI scheduling information (Si-SchedulingInfo)

[0302] - Service Cellular Configuration (Service CellConfigCommon)

[0303] - Information regarding support for IMS Emergency Carrier Service (Ims-Emergency Support)

[0304] - Information about the timers and constants used by the terminal (ue-TimersAndConstants)

[0305] - Information about access control parameters for each access category (uac-BarringInfo)

[0306] - Indicates whether a recovery identifier and recovery request message are used (useFullResumeID)

[0307] In addition to the information described above, the second SIB1 may include super SFN (HSFN) information. A super SFN is an extended SFN, and the extension extends the range of frame numbers (0 to 1023) that can be notified via the SFN. Furthermore, the second SIB1 may include information regarding extended discontinuous reception (eDRX).

[0308] Furthermore, the second SIB1 may include information indicating the actual transmission positions of the SS / PBCH blocks (SSB - PositionsInBurst). For example, if the first and second SS / PBCH blocks are transmitted separately, information indicating the actual transmission positions of the first and second SS / PBCH blocks (SSB - PositionsInBurst) may be transmitted. Alternatively, if a secondary PBCH is provided, information indicating the actual transmission positions of the secondary PBCH (SPBCH - PositionsInBurst) may be included.

[0309] When a secondary PBCH is provided, some of the parameters described above can be included in the secondary PBCH instead of the second SIB1.

[0310] (Methods provided)

[0311] A second SIB1 can be provided by using one or more of the following methods.

[0312] -Second Core Set #0

[0313] The second SIB1 is provided by a CORESET that is different from the first CORESET#0 (e.g., the second CORESET#0).

[0314] The first CORESET#0 configuration is provided via an SS / PBCH block, and the second CORESET#0 is provided via an SS / PBCH block or a secondary PBCH. As described above, the SS / PBCH block can be common to both the first and second CORESET#0, or it can be different for each of the first and second CORESET#0.

[0315] It should be noted that, as described above, the second CORESET#0 is configured to fall within the supported bandwidth of the second terminal device 40B. For example, for a 15kHz SCS, the second CORESET#0 is configured to have 24 PRBs or fewer.

[0316] - Search Space

[0317] The second SIB1 is provided through a different search space than the Type0-PDCCH CSS set for the first terminal device 40A (hereinafter also referred to as the first Type0-PDCCH CSS set). The first Type0-PDCCH CSS set is configured via a first SS / PBCH block, and the Type0-PDCCH CSS set for the second terminal device 40B (also referred to as the second Type0-PDCCH CSS set) is provided via a second SS / PBCH block or a secondary PBCH.

[0318] It should be noted that, when a secondary PBCH is provided, the period of the second Type0-PDCCH CSS set is preferably set to be the same as or longer than the period of the secondary PBCH.

[0319] -RNTI

[0320] The second SIB1 is provided using an RNTI different from the SI-RNTI (hereinafter referred to as the first SI-RNTI) for the first terminal device 40A. The value of the first SI-RNTI is "FFFF" in hexadecimal. In this case, the value of the SI-RNTI (hereinafter referred to as the second SI-RNTI) for the second terminal device 40B is any value other than "FFFF" in hexadecimal, that is, any value from "0001" to "FFFD".

[0321] -DCI

[0322] The second SIB1 is provided using a different DCI than the one used to schedule the first SIB1 (hereinafter also referred to as the first DCI). Specifically, the parameter set of the DCI used to schedule the second SIB1 (hereinafter also referred to as the second DCI) is different from the parameter set of the first DCI.

[0323] For example, the first DCI of scheduling the first SIB1 is configured to include the following information.

[0324] -Frequency domain resource allocation

[0325] -Time-domain resource assignment

[0326] VRB to PRB mapping

[0327] - Modulation and coding schemes

[0328] - Redundant version

[0329] -System Information Indicators

[0330] - Reserved bits

[0331] In addition to the parameter set of the first DCI described above, the second DCI used for scheduling the second SIB1 may include the number of repetitions of the transmission of the PDSCH carrying the second SIB1, and information about the SFN or HSFN (e.g., a portion of the information about the SFN or HSFN). Furthermore, in the case of applying cross-slot scheduling, in addition to the information described above, the first DCI may include information about the time slot of the PDSCH.

[0332] <3.3, RACH Procedure>

[0333] Configure the PRACH resources (hereinafter also referred to as the second PRACH resources) for the second terminal device 40B via the second SIB1.

[0334] The verification rules for the second PRACH resource are described below. The validity or invalidity of the second PRACH resource is determined based on the following conditions.

[0335] -A valid second PRACH resource is a resource on which PRACH can be sent for a second terminal device 40B.

[0336] - An invalid second PRACH resource is a resource on which PRACH for the second terminal device 40B should not be sent.

[0337] The second terminal device 40B selects a second PRACH resource from the available second PRACH resources for sending a PRACH for the second terminal device 40B.

[0338] In resources where the first SS / PBCH and the second SS / PBCH overlap, the second PRACH resource is invalid. In this case, the arrangement of the first SS / PBCH can be notified via the second SIB1.

[0339] <3.4 Initial DL BWP>

[0340] For example, in a frequency band with a narrow bandwidth, such as a bandwidth portion (BWP), the BWP becomes congested when a large number of second terminal devices 40B are connected to a cell.

[0341] Therefore, in the embodiments of this disclosure, the second terminal device 40B can switch the initial DL BWP. By switching the initial DL BWP at an earlier stage, the second terminal device 40B can eliminate band congestion.

[0342] The second terminal device 40B, for example, switches the initial DL BWP based on information about the BWP included in the RAR. Alternatively, the second terminal device 40B may switch to the initial DL BWP associated with the selected second PRACH resource.

[0343] Furthermore, in the event of congestion on the SS / PBCH to which the second terminal device 40B is connected, the core network 120 can notify the second SIB1 of the blocking information and the location of the SS / PBCH as the recommended connection destination. Based on the notified information, the second terminal device 40B performs a cellular reconnection to the SS / PBCH as the recommended connection destination.

[0344] Here, notifications regarding blocked connections and recommended connection destinations are delivered using an intra-frequency cellular reselection mechanism. For example, conventional intra-frequency cellular reselection provides notifications about recommended connection destinations based on device type (legacy device or low-capability NR device).

[0345] <3.5, Configuration Example of Secondary PBCH>

[0346] Here we will describe a physical configuration example of the secondary PBCH described above.

[0347] (Configuration)

[0348] The secondary PBCH includes an encoded additional MIB (MIB2 or MIB for low-capacity NR devices) (hereinafter also referred to as the second MIB) and DMRS for demodulating the payload of the secondary PBCH.

[0349] As described above, the second MIB includes at least the configuration information for the second CORESET#0. Furthermore, the secondary PBCH (second MIB, secondary PBCH payload, and / or secondary PBCH physical parameters) may include the following information.

[0350] - Connection blocking (blocking) information for a predetermined terminal device 40 (e.g., a terminal device 40 other than the second terminal device 40B).

[0351] - Information regarding QCL with SIB (Type 0 DMRS of PDCCH and DMRS of PDSCH)

[0352] - Extended bits (spare bits or reserved bits) for forward compatibility

[0353] -Information regarding the initial DL bandwidth portion (or default DL bandwidth portion) for the second terminal device 40B

[0354] -TDD configuration (information about uplink, downlink, and flexible symbols)

[0355] -Information regarding whether an SSB is a non-cellular defined SSB and the frequency location of a cellular defined SSB.

[0356] - Information regarding paging of the second terminal device 40B

[0357] -Information regarding cellular selection for the second terminal device 40B

[0358] -Information regarding the DRX of the second terminal device 40B

[0359] - Information about extended SFNs (e.g., Super SFN)

[0360] - Number of transmit antenna ports for secondary PBCH and SIB

[0361] Information regarding the QCL with the SIB may include, for example, the number of repetitions (repetition level) of transmissions from SIB1 and information regarding the status of the QCLs of the minor PBCH and SIB, and may be communicated using, for example, the TCI status. Furthermore, information regarding DRX may include the DRX period and DRX time period.

[0362] The physical parameters of the secondary PBCH include the CRC scrambling mask of the secondary PBCH, the scrambling sequence of the secondary PBCH payload, the resource location of the secondary PBCH, etc. Specifically, the number of transmit antenna ports of the secondary PBCH and information about the extended SFN are notified based on the pattern of the CRC scrambling mask of the secondary PBCH.

[0363] It should be noted that some of the parameters mentioned above are not included in the secondary PBCH, but can be included in the second SIB1.

[0364] Figure 25 This is an illustration showing a configuration example of a secondary PBCH according to an embodiment of the present disclosure. The secondary PBCH is configured to have a maximum supported bandwidth of 40B or less for the second terminal device. For example, the secondary PBCH includes 24 PRBs or less (in... Figure 25 (There are 24 PRBs in the middle).

[0365] In the secondary PBCH, the number of symbols is determined based on the amount of information and the coding rate of the second MIB. As an example, the secondary PBCH consists of two symbols and transmits a 24-bit second MIB. When the amount of information transmitted on the secondary PBCH is small, it may include one symbol. When the amount of information transmitted on the secondary PBCH is large, or when a low coding rate is required, it may include four or seven symbols. It should be noted that the number of symbols in the SS / PBCH block can be determined from the SS / PBCH block itself.

[0366] like Figure 25 As shown, the secondary PBCH is transmitted along with a reference signal (DMRS) used for demodulating the secondary PBCH. For example, the DMRS is placed every four REs on the frequency axis. The DMRS of the secondary PBCH does not need to be included in all symbols. Meanwhile, when the DMRS is included in the first symbol, the demodulation delay is reduced; therefore, it is preferable to include the DMRS in the first symbol. Figure 25 In the example, DMRS are arranged every two symbols. Figure 25 In the example, DMRS is included in the first and third symbols, but not in the second and fourth symbols.

[0367] (cycle)

[0368] The secondary PBCH is positioned at the same period as the SS / PBCH block, or at a period longer than the SS / PBCH block. As an example, in initial cellular selection, the secondary PBCH is positioned at the same period as the SS / PBCH block. In initial cellular selection, the second terminal device 40B assumes that the secondary PBCH occurs within a period of two radio frequency frames (20 subframes or 20 ms).

[0369] It should be noted that the cycle of the secondary PBCH can be notified separately from the cycle of the SS / PBCH block. Specifically, the cycle of the secondary PBCH can be set using parameters different from those used for the cycle of the SS / PBCH block for piglets (SSB Measurement Timing Configuration (SMTC)).

[0370] Furthermore, the secondary PBCH, positioned at the same center frequency, carries the same second MIB within a predetermined time period. This predetermined time period is 80 ms. It should be noted that the predetermined time period can be longer than 80 ms. For example, the predetermined time period could be 160 ms or 320 ms.

[0371] Furthermore, the number of SS / PBCHs and the number of secondary PBCHs in a burst can be different. In other words, information about the actual SSBs transmitted (ssb-PositionsInBurst) and information about the actual secondary PBCHs transmitted (SPBCH-PositionsInBurst) can be set separately.

[0372] (Time / Frequency Resources)

[0373] Secondary PBCHs are arranged by frequency division multiplexing or time division multiplexing with SS / PBCH blocks. Five examples will be used later to describe the methods of multiplexing for secondary PBCHs and SS / PBCH blocks.

[0374] Example 1

[0375] Figure 26 This is an illustration of an example of a method for multiplexing minor PBCH and SS / PBCH blocks according to embodiments of the present disclosure. Figure 26 This illustrates the case where the SS / PBCH block and secondary PBCH are frequency-division multiplexed. Figure 26 In the diagram, the horizontal direction represents time, and the vertical direction represents frequency.

[0376] For example, the secondary PBCH is placed in a different resource block on the same symbol as the corresponding SS / PBCH block. Figure 26 In the example, the secondary PBCH is placed in the resource block above the SS / PBCH block.

[0377] It should be noted that the arrangement of secondary PBCHs is not limited to Figure 26 For example, a secondary PBCH can be placed in a resource block below the SS / PBCH block. The header (or content or postscript) of the resource block configured with the secondary PBCH can be indicated by the SS / PBCH block.

[0378] Example 2

[0379] Figure 27 This is an illustration of another example of a method for multiplexing minor PBCH and SS / PBCH blocks according to embodiments of the present disclosure. Figure 27 This illustrates the case where the SS / PBCH block and secondary PBCH are time-division multiplexed. Figure 27 In the diagram, the horizontal direction represents time, and the vertical direction represents frequency.

[0380] For example, a minor PBCH is included in the next half-frame after the half-frame that includes the SS / PBCH block burst. Figure 27 In the example, the SS / PBCH block is placed in the first half-frame of the resource in which the SS / PBCH block is placed, and the secondary PBCH is placed in the second half-frame. It should be noted that the half-frame including the secondary PBCH can be a third or fourth half-frame. It should also be noted that the half-frame including the secondary PBCH can be indicated by the SS / PBCH block.

[0381] Example 3

[0382] Figure 28 This is an illustration of another example of a method for multiplexing minor PBCH and SS / PBCH blocks according to embodiments of the present disclosure. Figure 28 This illustrates a case where the SS / PBCH block and the secondary PBCH are time-division multiplexed, and the secondary PBCH includes one symbol. Figure 28 In the diagram, the horizontal direction represents time, and the vertical direction represents frequency.

[0383] In the case where the secondary PBCH includes a symbol, such as Figure 28 As shown, the minor PBCH is included in the half-frame that includes the SS / PBCH block burst. Specifically, the minor PBCH is arranged in the fifth subframe of the half-frame that includes the SS / PBCH block burst. The minor PBCHs corresponding to SS / PBCH block indices #0 to #3 are arranged in symbols #2, #3, #4, and #5, respectively, and the minor PBCHs corresponding to SS / PBCH block indices #4 to #7 are arranged in symbols #8, #9, #10, and #11, respectively.

[0384] -Example 4

[0385] Figure 29 This is an illustration of another example of a method for multiplexing minor PBCH and SS / PBCH blocks according to embodiments of the present disclosure. Figure 29 This illustrates a case where the SS / PBCH block and the secondary PBCH are time-division multiplexed, and the secondary PBCH includes one symbol. Figure 29In the diagram, the horizontal direction represents time, and the vertical direction represents frequency.

[0386] As another example of Example 3, some SS / PBCH blocks do not need to be sent, and the resources can be used to send secondary PBCHs. In this case, such as Figure 29 As shown, SS / PBCH blocks #6 and #7 are not sent; instead, six minor PBCHs corresponding to SS / PBCH block indices #0 to #5 are sent.

[0387] Example 5

[0388] Figure 30 This is an illustration of another example of a method for multiplexing minor PBCH and SS / PBCH blocks according to embodiments of the present disclosure. Figure 30 This illustrates a time-division multiplexing scenario where the SS / PBCH block and the secondary PBCH are time-division multiplexed, and the SS / PBCH block and the secondary PBCH have different periods. Figure 30 In the diagram, the horizontal direction represents time, and the vertical direction represents frequency.

[0389] In this example, the period of the SS / PBCH block is set to 20 msec, and the period of the minor PBCH is set to 40 msec. In this case, the minor PBCHs corresponding to SS / PBCH block indices #0 to #3 are arranged in the sixth and seventh subframes of the first period of the SS / PBCH block. The minor PBCHs corresponding to SS / PBCH block indices #4 to #7 are arranged in the sixth and seventh subframes (the 26th and 27th subframes counting from the header) of the second period of the SS / PBCH block.

[0390] (Precoding)

[0391] Random precoding can be applied to the transmission of the secondary PBCH. Specifically, different precodings can be applied to predetermined resources (e.g., six PRBs and one symbol or 24 PRBs and four symbols) within the secondary PBCH to implement transmission. The second terminal device 40B attempts to demodulate the precoded secondary PBCH using DMRS included in the predetermined resources. Different precodings are applied to different secondary PBCHs through random precoding. The second terminal device 40B does not assume that the same precoding is applied to two different secondary PBCHs.

[0392] Spatial Frequency Block Coding (SFBC) can be applied to the transmission of the secondary PBCH. For example, in the case of two antenna ports, the precoding shown in Equation (1) is applied to the secondary PBCH.

[0393] [Mathematical Expression 1]

[0394]

[0395] For example, in the case of four antenna ports, the precoding shown in formula (2) is applied to the secondary PBCH.

[0396] [Mathematical Expression 2]

[0397]

[0398] (Encoding / Scrambling)

[0399] The minor PBCH is encoded using polar codes. It should be noted that the minor PBCH can be encoded using other codes, such as low-density parity-check (LDPC) codes, convolutional codes, and turbo codes. The SS / PBCH block can indicate which encoding method was applied.

[0400] Preferably, the minor PBCH is scrambled using the SS / PBCH block index. For example, formula (3) is applied to the scrambling of the minor PBCH.

[0401] [Mathematical Expression 3]

[0402]

[0403] Here, b represents the information bits of the PBCH before scrambling, bˉ represents the information bits of the PBCH after scrambling, c represents the scrambling sequence, v represents the SS / PBCH block index, and M... bit Indicates the number of information bits in the PBCH.

[0404] (Quasi-common (QCL))

[0405] The secondary PBCH and SS / PBCH block are quasi-co-occupied. Specifically, from the perspective of one or more of Doppler spread, Doppler frequency shift, average delay, delay spread, and spatial Rx parameters, the second terminal device 40B can assume that the SS / PBCH block with a predetermined index and the DMRS of the secondary PBCH corresponding to the predetermined index are QCL (quasi-co-occupied).

[0406] An SS / PBCH block and a secondary PBCH can be QCLs, or an SS / PBCH block and multiple secondary PBCHs can be QCLs. In the case where an SS / PBCH block and multiple secondary PBCHs are QCLs, the second terminal device 40B can perform soft synthesis on the multiple secondary PBCHs.

[0407] Furthermore, the secondary PBCH is quasi-co-located with the PDCCH and PDSCH used to carry the corresponding second SIB1. Specifically, the second terminal device 40B may assume that the DMRS of the secondary PBCH is quasi-co-located (QCL) with the DMRS of the PDCCH and PDSCH used to carry the corresponding second SIB1 in one or more aspects of Doppler spread, Doppler frequency shift, average delay, delay spread, and spatial Rx parameter.

[0408] As described above, initial access procedures can be provided for both the first and second terminal devices 40A and 40B on a single carrier.

[0409] <4. Modification Example>

[0410] Some of the embodiments described above, or a portion thereof, can be applied to the dual connectivity described above (e.g., EUTRA-EUTRA dual connectivity, EUTRA-NR dual connectivity (ENDC), EUTRA-NR dual connectivity with 5GC, NR-EUTRA dual connectivity (NEDC), and NR-NR dual connectivity). For example, the reception of a second CORESET configuration (second CORESET#0) (e.g., information described above, such as spare bits (reserved bits or extended bits) included in the PBCH payload or MIB, information indicating the existence of a secondary PBCH or its resources, candidates for resources for the secondary PBCH, and the actual transmission location of the secondary PBCH) can be provided from the dominant node (MN) to the UE in a dual connectivity (e.g., by using RRC signaling), while the application target of the second CORESET configuration (second CORESET#0) can be a PDCCH provided by the secondary node (SN).

[0411] Additionally or alternatively, the previously described low-capability NR devices (NR lightweight UEs) can be categorized using multiple levels or modes defined in the low-capability NR device (NR lightweight UE). Among these levels or modes, the choice of which level or mode to apply can be based on the conditions required for the first terminal device 40A (a legacy NR device, such as a standard NR UE or a traditional NR UE) (e.g., low performance, low device cost, low complexity, and low power consumption), or on radio quality (e.g., RSRP, RSRQ, SINR, CSI, or RSSI) or quality of service (QCI or 5QI) during low-capability NR device operation (e.g., the previously described message information, such as physical channels like RRC signaling, DCI, or PBCH) or during the implementation of the previously described initial access. Among the several application methods described above for the second CORESET configuration (second CORESET #0), the choice of which method to apply can be determined based on multiple levels or modes.

[0412] The terminal device or base station device in this embodiment can be implemented using a dedicated computer system or a general-purpose computer system.

[0413] For example, a communication program for performing the operations described above is stored on and distributed on a computer-readable recording medium such as an optical disc, semiconductor memory, magnetic tape, or flexible disk. The control device is then implemented, for example, by installing the program in a computer and performing the processes described above. In this case, the control device may be a terminal device 40, a base station device 20, or other external device (e.g., a personal computer). Furthermore, the control device may be a device internal to the terminal device 40 and the base station device 20 (e.g., each control unit).

[0414] Furthermore, the communication program can be stored on a disk drive included in a server device on a network such as the Internet, and downloaded to a computer. Additionally, the functions described above can be implemented through cooperation between an operating system (OS) and application software. In this case, the portion outside the OS can be stored on a medium and distributed, or the portion outside the OS can be stored on a server device and downloaded to a computer.

[0415] Furthermore, in the processes described in the foregoing embodiments, all or part of the processes described as being automatically implemented can be performed manually. Alternatively, all or part of the processes described as being manually implemented can be automatically implemented by known methods. Moreover, unless otherwise specified, the processing procedures, specific names, and information including various data and parameters shown in the specification and drawings can be arbitrarily changed. For example, the various information shown in the drawings is not limited to those shown in the figures.

[0416] Furthermore, each component shown for each device is a functional concept and does not necessarily have to be physically configured as illustrated in the figures. That is, the specific distribution / integration patterns of the individual devices are not limited to those shown in the figures. All or some of these devices can be distributed / integrated in any unit, functionally or physically, depending on different loads or usage conditions.

[0417] Furthermore, the embodiments described above can be appropriately combined as long as the processed content does not conflict with each other.

[0418] <<5. Conclusion>>

[0419] As described above, preferred embodiments of the present disclosure have been described in detail with reference to the accompanying drawings; however, the technical scope of the present disclosure is not limited to such examples. Those skilled in the art will recognize that various modifications or alterations can be conceived within the scope of the technical ideas described in the claims, and it should be naturally understood that such modifications or alterations fall within the technical scope of the present disclosure.

[0420] Furthermore, the effects described in this specification are merely illustrative or exemplary and not restrictive. That is, as supplements to or alternatives to the effects described above, the technology according to this disclosure may exhibit other effects that will be obvious to those skilled in the art as described in this specification.

[0421] It should be noted that the following configurations also fall within the technical scope of this disclosure.

[0422] (1) A communication device, comprising:

[0423] The communication unit monitors the Physical Broadcast Channel (PBCH) to receive signals; and

[0424] The control unit determines, based on one or more bits included in the signal received on the PBCH, which of the first control resource set CORESET configuration and the second CORESET configuration to use for communication.

[0425] (2) According to the communication device of (1), wherein the second CORESET configuration is selected when the maximum supported bandwidth of the communication device is equal to or less than a predetermined value, and the first CORESET configuration is selected when the maximum supported bandwidth is greater than the predetermined value.

[0426] (3) The communication device according to (1) or (2), wherein the number of physical resource blocks in the second CORESET configuration is less than the number of physical resource blocks in the first CORESET configuration.

[0427] (4) A communication device according to any one of (1) to (3), wherein the communication unit monitors the secondary PBCH for receiving the second signal based on the one or more bits of the second CORESET configuration.

[0428] (5) The communication device according to (4), wherein the control unit determines whether there is a secondary PBCH based on the one or more bits.

[0429] (6) The communication device according to (4) or (5), wherein the control unit determines the resources configured with the secondary PBCH based on the one or more bits.

[0430] (7) A communication device according to any one of (4) to (6), wherein the secondary PBCH is arranged by time division multiplexing or frequency division multiplexing with the PBCH.

[0431] (8) A communication device according to any one of (1) to (3), wherein the control unit switches reference information for receiving a first CORESET configuration or a second CORESET configuration based on the one or more bits.

[0432] (9) A communication device according to any one of (1) to (8), wherein SystemInformationBlockType1 (SIB1) used for communication performed by applying the second CORESET configuration is transmitted using the second CORESET configuration.

[0433] (10) A communication device, comprising:

[0434] The communication unit monitors either the primary PBCH or the secondary PBCH to receive signals; and

[0435] The control unit controls the communication unit to communicate by applying a first CORESET configuration when monitoring the primary PBCH to receive signals, and to communicate by applying a second CORESET configuration when monitoring the secondary PBCH to receive signals.

[0436] (11) A communication device, comprising:

[0437] The communication unit transmits a signal comprising one or more bits via the PBCH, the one or more bits being used to determine whether the communication partner applies a first CORESET configuration or a second CORESET configuration for communication.

[0438] (12) A communication method, comprising:

[0439] Monitor the PBCH to receive signals; and

[0440] The decision to apply either the first CORESET configuration or the second CORESET configuration for communication is based on one or more bits included in the signal received on the PBCH.

[0441] (13) A communication method, comprising:

[0442] Monitoring either the primary PBCH or the secondary PBCH to receive signals; and

[0443] Communication is performed by applying the first CORESET configuration when the primary PBCH is monitored to receive signals, and by applying the second CORESET configuration when the secondary PBCH is monitored to receive signals.

[0444] List of reference numerals

[0445] 20 base station equipment

[0446] 21 Wireless communication unit

[0447] 24, 45 Control Units

[0448] 40 terminal devices

[0449] 41 Wireless Communication Unit

Claims

1. A communication device, comprising: The communication unit monitors the Physical Broadcast Channel (PBCH) to receive signals; as well as The control unit determines, based on one or more bits included in the signal received on the PBCH, which of the first control resource set CORESET configuration and the second CORESET configuration to apply for communication. The communication unit is based on one or more bits to monitor the secondary PBCH for receiving the second CORESET configuration in order to receive the second signal.

2. The communication device according to claim 1, wherein, If the maximum supported bandwidth of the communication device is equal to or less than a predetermined value, select the second CORESET configuration; if the maximum supported bandwidth is greater than a predetermined value, select the first CORESET configuration.

3. The communication device according to claim 1, wherein, The number of physical resource blocks in the second CORESET configuration is less than the number of physical resource blocks in the first CORESET configuration.

4. The communication device according to claim 1, wherein, The control unit determines whether a secondary PBCH is present based on one or more of the bits.

5. The communication device according to claim 1, wherein, The control unit determines the resources with secondary PBCHs based on the one or more bits.

6. The communication device according to claim 1, wherein, Secondary PBCHs are arranged by time-division multiplexing or frequency-division multiplexing with PBCHs.

7. The communication device according to claim 1, wherein, The control unit switches reference information for receiving a first CORESET configuration or a second CORESET configuration based on one or more bits.

8. The communication device according to claim 1, wherein, The SystemInformationBlockType1 (SIB1) used for communication performed by applying the second CORESET configuration is sent using the second CORESET configuration.

9. A communication system, comprising: The communication device according to claim 1; as well as The second communication device includes a communication unit that transmits a signal comprising one or more bits using the PBCH, the one or more bits being used to determine whether the communication partner is using a first CORESET configuration or a second CORESET configuration for communication.

10. A communication method, comprising: Monitor the PBCH to receive signals; The decision to apply either the first CORESET configuration or the second CORESET configuration for communication is based on one or more bits included in the signal received on the PBCH. as well as Based on the monitoring of one or more bits, a secondary PBCH is used to receive the second signal in the second CORESET configuration.

Images