Communication device and communication method

Abstract

This communication device comprises a transceiver and a processor. The processor is configured to transmit a Master Information Block (MIB), including first information, via a transceiver in a second frequency range different from a first frequency range. The first information corresponds to an index specifying a combination of second information and third information to be explicitly included in an MIB that is (to be) transmitted in the case of the first frequency range. The number of bits in the first information is less than the total number of bits in the second information and the third information.

Description

[Technical Field]

[0001] The present disclosure relates to a communication device and a communication method. [Background technology]

[0002] Radio access methods and radio networks for cellular mobile communications (hereinafter also referred to as "Long Term Evolution (LTE)," "LTE-Advanced (LTE-A)," "LTE-Advanced Pro (LTE-A Pro)," "5G (fifth generation)," "New Radio (NR)," "New Radio Access Technology (NRAT)," "Evolved Universal Terrestrial Radio Access (EUTRA)," or "Further EUTRA (FEUTRA)") are being studied by the 3rd Generation Partnership Project (3GPP). In the following description, LTE includes LTE-A, LTE-A Pro, and EUTRA, and NR includes NRAT and FEUTRA. In LTE and NR, a base station device (base station) is also referred to as an eNodeB (evolved NodeB) in LTE and a gNodeB (gNB) in NR, and a terminal device (mobile station, mobile station device, terminal) is also referred to as a UE (User Equipment). LTE and NR are cellular communication systems in which areas covered by base stations are arranged in the form of multiple cells. A single base station may manage multiple cells.

[0003] NR is a next-generation radio access technology (RAT) that is different from LTE. NR is an access technology that can support various use cases, including eMBB (Enhanced mobile broadband), mMTC (Massive machine-type communications), and URLLC (Ultra reliable and low latency communications). NR is being studied with the aim of creating a technology framework that can accommodate the usage scenarios, requirements, and deployment scenarios of those use cases.

[0004] Due to the demand for even wider bandwidth, the use of a high frequency band called millimeter waves, which is between 52.6 GHz and 71 GHz, is being considered. Various use cases are being considered for the frequency band between 52.6 GHz and 110 GHz, such as high data rate eMBB, mobile data offloading, and vertical industry factory applications. 3GPP's consideration of the use of millimeter waves is disclosed in Non-Patent Document 1. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] TR 38.808, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on supporting NR from 52.6 GHz to 71 GHz (Release 17),” v1.0.0, December 2020. Summary of the Invention [Problem to be solved by the invention]

[0006] However, no consideration has been given to how to implement the initial access procedure using millimeter waves.

[0007] Therefore, the present disclosure provides a communication device and a communication method capable of performing an initial access procedure using millimeter waves.

[0008] It should be noted that the above problem or object is merely one of multiple problems or objects that can be solved or achieved by multiple embodiments disclosed in this specification. [Means for solving the problem]

[0009] According to the present disclosure, there is provided a communication device. The communication device includes a transceiver and a processor. The processor is configured to transmit, via the transceiver, a Master Information Block (MIB) including first information in a second frequency range different from a first frequency range. The first information corresponds to an index specifying a combination of second information and third information explicitly included in the MIB to be transmitted in the first frequency range. The number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an example of an SS / PBCH block. [Figure 3] FIG. 10 is a diagram illustrating an example of an arrangement of SS / PBCH blocks. [Figure 4] FIG. 1 is a diagram illustrating an example of an IE (Information Element) of a MIB. [Figure 5] FIG. 1 is a diagram illustrating an example of an IE (Information Element) of a MIB. [Figure 6] FIG. 10 is a diagram illustrating an example of the structure of BCCH and BCH messages. [Figure 7A]10 is a diagram showing a table used to set CORESET #0. [Figure 7B] 10 is a diagram showing a table used to set CORESET #0. [Figure 7C] 10 is a diagram showing a table used to set CORESET #0. [Figure 7D] 10 is a diagram showing a table used to set CORESET #0. [Figure 7E] 10 is a diagram showing a table used to set CORESET #0. [Figure 7F] 10 is a diagram showing a table used to set CORESET #0. [Figure 7G] 10 is a diagram showing a table used to set CORESET #0. [Figure 7H] 10 is a diagram showing a table used to set CORESET #0. [Figure 7I] 10 is a diagram showing a table used to set CORESET #0. [Figure 7J] 10 is a diagram showing a table used to set CORESET #0. [Figure 7K] 10 is a diagram showing a table used to set CORESET #0. [Figure 7L] 10 is a diagram showing a table used to set CORESET #0. [Figure 8A] 10 is a diagram showing a table used to set a PDCCH monitoring occasion of a Type0-PDCCH CSS set. [Figure 8B] 10 is a diagram showing a table used to set a PDCCH monitoring occasion of a Type0-PDCCH CSS set. [Figure 8C] 10 is a diagram showing a table used to set a PDCCH monitoring occasion of a Type0-PDCCH CSS set. [Figure 8D] 10 is a diagram showing a table used to set a PDCCH monitoring occasion of a Type0-PDCCH CSS set. [Figure 8E] 10 is a diagram showing a table used to set a PDCCH monitoring occasion of a Type0-PDCCH CSS set. [Figure 9A] FIG. 10 is a diagram illustrating an example of multiplexing an SS / PBCH block and a CORESET. [Figure 9B] FIG. 10 is a diagram illustrating an example of multiplexing an SS / PBCH block and a CORESET. [Figure 9C] FIG. 10 is a diagram illustrating an example of multiplexing an SS / PBCH block and a CORESET. [Figure 10A] 10 is a diagram showing the relationship between kSSB, pdcchConfig-SIB1, and GSCN in FR1. [Figure 10B] 10 is a diagram showing the relationship between kSSB, pdcchConfig-SIB1, and GSCN in FR2. [Figure 11] This is a diagram showing the relationship between subCarrierSpacingCommon, the minimum bit of ssb-SubcarrierOffset, and NSSB QCL. [Figure 12] FIG. 2 is a block diagram illustrating an example of a configuration of a base station device according to an embodiment of the present disclosure. [Figure 13] FIG. 1 is a diagram illustrating a configuration example of a terminal device according to an embodiment of the present disclosure. [Figure 14] 10 is a diagram for explaining a method for indicating a secondary PBCH according to an embodiment of the present disclosure. FIG. [Figure 15] 10 is a diagram illustrating an example of a table used for PDCCH configuration when the SCS of {SS / PBCH block, PDCCH} is {120, 120} kHz according to an embodiment of the present disclosure. [Figure 16] 10 is a diagram illustrating an example of a table used for PDCCH configuration when the SCS of {SS / PBCH block, PDCCH} is {120, 120} kHz according to an embodiment of the present disclosure. [Figure 17]10 is a diagram illustrating an example of a table used for notifying GSCN in FR3 according to an embodiment of the present disclosure. [Figure 18] 10 is a diagram illustrating an example of a table of combinations of subCarrierSpacingCommon and ssb-SubcarrierOffset when the SS / PBCH block is 120 kHz according to an embodiment of the present disclosure. [Figure 19] 10 is a diagram illustrating an example of a table used for notifying GSCN in FR3 according to an embodiment of the present disclosure. [Figure 20] 10 is a diagram illustrating an example of a table used for notifying GSCN in FR3 according to an embodiment of the present disclosure. [Figure 21] FIG. 1 is a diagram illustrating an example configuration of a secondary PBCH according to an embodiment of the present disclosure. [Figure 22] 10A and 10B are diagrams illustrating an example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. [Figure 23] 10A and 10B are diagrams for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. [Figure 24] 10A and 10B are diagrams for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. [Figure 25] 10A and 10B are diagrams for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. [Figure 26] 10A and 10B are diagrams for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and the drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0012] Furthermore, in this specification and drawings, elements having substantially the same functional configuration may be distinguished by adding different letters after the same reference numeral. For example, multiple elements having substantially the same functional configuration may be distinguished as needed, such as base station devices 20A and 20B. However, if there is no need to particularly distinguish between multiple elements having substantially the same functional configuration, only the same reference numeral may be used. For example, if there is no need to particularly distinguish between base station devices 20A and 20B, they will simply be referred to as base station device 20.

[0013] One or more embodiments (including examples and modifications) described below can be implemented independently. However, at least a portion of the embodiments described below may be implemented in appropriate combination with at least a portion of another embodiment. These embodiments may include novel features that are different from one another. Therefore, these embodiments may contribute to solving different purposes or problems and may produce different effects.

[0014] <<Introduction>> <System configuration example> Fig. 1 is a diagram illustrating an example of the overall configuration of a communication system 1 according to an embodiment of the present disclosure. As illustrated in Fig. 1, the communication system 1 includes a plurality of base station devices 20 (20A and 20B), a plurality of terminal devices 40 (40A and 40B), a core network 120, and a PDN (Packet Data Network) 130. Note that the number of each device is not limited to this, and for example, there may be one base station device 20 and one terminal device 40.

[0015] The base station device 20 is a communication device that operates a cell 110 and provides wireless communication services to one or more terminal devices 40 located within the coverage of the cell 110. The cell 110 is operated according to any wireless communication scheme, such as LTE or NR. The base station device 20 is connected to a core network 120. The core network 120 is connected to a packet data network (PDN) 130 via a gateway device (not shown). The base station device 20 may be configured as a collection of multiple physical or logical devices. For example, in an embodiment of the present disclosure, the base station device 20 may be divided into multiple devices, a baseband unit (BBU) and a radio unit (RU), and may be interpreted as a collection of these multiple devices. Additionally or alternatively, in an embodiment of the present disclosure, the base station device 20 may be either or both of a BBU and a RU. The BBU and the RU may be connected via a predetermined interface (e.g., eCPRI). Additionally or alternatively, the RU may be referred to as a remote radio unit (RRU) or a radio DoT (RD). Additionally or alternatively, the RU may be compatible with the gNB-DU, which will be described later. Additionally or alternatively, the BBU may be compatible with the gNB-CU, which will be described later. Additionally or alternatively, the RU may be a device formed integrally with an antenna. The antenna of base station device 20 (for example, an antenna formed integrally with the RU) may employ an Advanced Antenna System and support MIMO (for example, FD-MIMO) and beamforming. In the Advanced Antenna System, the antenna of base station device 20 (for example, an antenna formed integrally with the RU) may be equipped with, for example, 64 transmitting antenna ports and 64 receiving antenna ports.

[0016] Furthermore, multiple base station devices 20 may be connected to each other. One or more base station devices 20 may be included in a Radio Access Network (RAN). That is, the base station device 20 may simply be referred to as a RAN, a RAN node, an Access Network (AN), or an AN node. The RAN in LTE is called EUTRAN (Enhanced Universal Terrestrial RAN). The RAN in NR is called NGRAN. The RAN in W-CDMA (UMTS) is called UTRAN. The LTE base station device 20 is called eNodeB (Evolved Node B) or eNB. That is, the EUTRAN includes one or more eNodeBs (eNBs). The NR base station device 20 is called gNodeB or gNB. That is, the NGRAN includes one or more gNBs. Furthermore, the EUTRAN may include a gNB (en-gNB) connected to a core network (EPC) in an LTE communication system (EPS). Similarly, the NGRAN may include an ng-eNB connected to a core network 5GC in a 5G communication system (5GS). Additionally or alternatively, if the base station device 20 is an eNB, gNB, or the like, it may be referred to as a 3GPP access. Additionally or alternatively, if the base station device 20 is a wireless access point (Access Point), it may be referred to as a non-3GPP access. Additionally or alternatively, the base station device 20 may be an optical extension device called an RRH (Remote Radio Head). Additionally or alternatively, if the base station device 20 is a gNB, it may be referred to as a combination of the gNB CU (Central Unit) and gNB DU (Distributed Unit) described above, or as either one of them. The gNB CU (Central Unit) hosts multiple upper layers (e.g., RRC, SDAP, PDCP) in the Access Stratum for communication with UEs. On the other hand, the gNB-DU hosts multiple lower layers (e.g., RLC, MAC, PHY) in the Access Stratum.That is, among the messages and information described below, RRC signaling (e.g., MIB, various SIBs including SIB1, RRC Setup message, RRC Reconfiguration message) may be generated by the gNB CU, while DCI and various physical channels (e.g., PDCCH, PBCH) described below may be generated by the gNB-DU. Alternatively, among the RRC signaling, some configurations, such as IE:cellGroupConfig, may be generated by the gNB-DU, and the remaining configurations may be generated by the gNB-CU. These configurations may be transmitted and received via the F1 interface described below. A base station device 20 may be configured to be able to communicate with other base station devices 20. For example, when multiple base station devices 20 are eNBs or a combination of an eNB and an en-gNB, the base station devices 20 may be connected to each other via an X2 interface. Additionally or alternatively, when multiple base station devices 20 are gNBs or a combination of a gn-eNB and a gNB, the devices may be connected to each other via an Xn interface. Additionally or alternatively, when multiple base station devices 20 are a combination of a gNB CU (Central Unit) and a gNB DU (Distributed Unit), the devices may be connected via the F1 interface described above. Message information (RRC signaling or DCI information, physical channel) described below may be communicated between multiple base station devices 20 (e.g., via X2, Xn, or F1 interfaces).

[0017] Furthermore, as described above, the base station device 20 may be configured to manage multiple cells. A cell provided by the base station device 20 is called a serving cell. The serving cell includes a PCell (Primary Cell) and an SCell (Secondary Cell). When dual connectivity (e.g., EUTRA-EUTRA Dual Connectivity, EUTRA-NR Dual Connectivity (ENDC), EUTRA-NR Dual Connectivity with 5GC, NR-EUTRA Dual Connectivity (NEDC), NR-NR Dual Connectivity) is provided to a UE (e.g., a terminal device 40), a PCell and zero or one or more SCell(s) provided by a Master Node (MN) are called a Master Cell Group. Furthermore, the serving cell may include a PSCell (Primary Secondary Cell or Primary SCG Cell). In other words, when dual connectivity is provided to a UE, a PSCell and zero or one or more SCell(s) provided by a Secondary Node (SN) are called a Secondary Cell Group (SCG). Unless special configuration (for example, PUCCH on SCell) is performed, the Physical Uplink Control Channel (PUCCH) is transmitted on the PCell and PSCell, but not on the SCell. Furthermore, Radio Link Failure is detected on the PCell and PSCell, but not on the SCell (it does not have to be detected). As such, the PCell and PSCell have special roles among the Serving Cell(s), and are therefore also called Special Cells (SpCells). One cell may be associated with one Downlink Component Carrier and one Uplink Component Carrier. Furthermore, the system bandwidth corresponding to one cell may be divided into multiple bandwidth parts.In this case, one or more Bandwidth Parts (BWPs) may be configured for the UE, and one Bandwidth Part may be used by the UE as an Active BWP. Furthermore, the radio resources (for example, frequency band, numerology (subcarrier spacing), slot format (Slot configuration)) that the terminal device 40 can use may differ for each cell, each component carrier, or each BWP.

[0018] When the core network 120 is an NR core network (5G Core (5GC)), the core network 120 may include an AMF (Access and Mobility Management Function), an SMF (Session Management Function), a UPF (User Plane Function), a PCF (Policy Control Function), and a UDM (Unified Data Management).

[0019] When the core network 120 is an LTE core network (Evolved Packet Core (EPC)), the core network 120 may include an MME (Mobility Management Entity), an S-GW (Serving gateway), a P-GW (PDN gateway), a PCRF (Policy and Charging Rule Function), and an HSS (Home Subscriber Server). The AMF and MME are control nodes that handle control plane signals and manage the mobility state (mobility) of the terminal device 40. The UPF and S-GW / P-GW are nodes that handle user plane signals. The PCF / PCRF are control nodes that perform control related to policies and charging, such as QoS (Quality of Service) for PDU sessions or bearers. The UDM / HSS are control nodes that handle subscriber data and perform service control.

[0020] The terminal device 40 is a communication device that performs wireless communication with the base station device 20 based on the control of the base station device 20. For example, the terminal device 40 measures downlink signals from the base station device 20 and reports measurement information indicating the measurement results to the base station device 20. The base station device 20 controls wireless communication with the terminal device 40 based on the reported measurement information. On the other hand, the terminal device 40 may transmit uplink signals for measurement to the base station device 20. In this case, the base station device 20 measures the uplink signals from the terminal device 40 and controls wireless communication with the terminal device 40 based on the measurement information.

[0021] As described above, base station devices 20 can transmit and receive information to each other using an inter-base station interface. If the core network is 5GC, the inter-base station interface may be an Xn interface. If the core network is EPC, the inter-base station interface may be an X2 interface. For example, the base station device 20 transmits measurement information (e.g., measurement results of cells managed by the source base station device, measurement results of neighboring cells) related to the terminal device 40 for which handover is predicted to occur to another adjacent base station device 20. This achieves stable handover and ensures stability in wireless communication of the terminal device 40.

[0022] 1, there may be communication devices around the communication system 1 that provide wireless communication services operated by other RATs than cellular communication, such as Wi-Fi (registered trademark) and MultiFire (registered trademark). Such communication devices are typically connected to the PDN 130.

[0023] Here, the terminal device 40 according to the embodiment of the present disclosure includes a first terminal device 40A and a second terminal device 40B. The first terminal device 40A is a terminal device that supports an operating band of a first frequency range (e.g., FR1 (Frequency Range 1) or FR2 (Frequency Range 2)).

[0024] The second terminal device 40B is a terminal device that supports an operating band in the band of 52.6 GHz or higher, the second frequency range (also called eFR2 (Extended FR2) or FR3 (Frequency Range 3)).

[0025] <Related technologies> Next, a technique for an initial access (cell connection) procedure in FR1 and FR2 communication systems will be described.

[0026] Figure 2 is a diagram showing an example of an SS / PBCH block. An SS / PBCH block (SSB block) consists of a PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal), PBCH (Physical Broadcast Channel), and PBCH DMRS (Demodulation Reference Signal). The PSS and SSS consist of 127 sequences and are arranged in 127 REs. The PSS is arranged in the first symbol of the SS / PBCH block, and the SSS is arranged in the third symbol of the SS / PBCH block. The PBCH is arranged in the second to fourth symbols. The second and fourth symbols of the PBCH are arranged in 20 PRBs (Physical Resource Blocks), and the third symbol is arranged in the four PRBs above and below the SS / PBCH block.

[0027] The MIB (Master Information Block) is the same for SS / PBCH blocks with the same center frequency, but may be different for SS / PBCH blocks with different center frequencies.

[0028] Furthermore, multiple SS / PBCH blocks are placed on the same center frequency. Each SS / PBCH block is assigned a different SS / PBCH block index. The first terminal device 40A may assume that SS / PBCH blocks with the same block index placed on the same center frequency are quasi-co-located (QCL). 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 indexes placed on the same center frequency are QCL.

[0029] Figure 3 shows an example of the arrangement of SS / PBCH blocks. As an example, the SS / PBCH is arranged as shown in Figure 3. One or more SS / PBCH blocks are arranged in a half frame (5 msec). Multiple SS / PBCH blocks within a half frame are also called an SS / PBCH block burst or SSB burst.

[0030] The maximum number of SS / PBCH blocks placed in one half-frame is defined as Lmax, which is 4 for FR1 and below 3 GHz, 8 for FR1 and above 3 GHz, 10 for unlicensed bands and 15 kHz SCS, 20 for unlicensed bands and 30 kHz SCS, and 64 for FR2. In other words, the number of SSBs in one SSB burst may depend on the subcarrier spacing associated with the frequency band.

[0031] The first symbol of one or more SS / PBCH blocks is located at the following symbol: Case A: {2,8}+14×n Case B: {4, 8, 16, 20} + 28 × n Case C: {2,8}+14×n Case D: {4,8,16,20}+28×n Case E: {2,8}+14×n Here, n is any positive number.

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

[0033] 4 and 5 are diagrams showing examples of MIB information elements (IEs). The NR MIB is composed of 23 bits. The MIB is composed of the IEs (Information Elements) shown in FIGS. 4 and 5.

[0034] Figure 6 is a diagram showing an example of the structure of BCCH and BCH messages. A BCCH (Broadcast Control Channel) is mapped to a BCH (Broadcast Channel). As shown in Figure 6, a BCH is composed of an MIB or messageClassExtension. In the case of an MIB, BCH data is composed of 24 bits, consisting of 23 bits for the MIB and 1 selection bit.

[0035] The PBCH payload includes the BCH data as well as the LSBs and half-frame bits of the 1st, 2nd, 3rd, and 4th SFNs.

[0036] Furthermore, if Lmax is 64 (i.e., in the case of FR2), the PBCH payload includes the 4th, 5th, and 6th SSB (Synchronization Signal / PBCH block) indexes, otherwise (i.e., in the case of FR1), k SSB It includes the MSB and two reserved bits.

[0037] In NR, RMSI (SIB1) is sent via the Physical Downlink Shared Channel (PDSCH) and the PDCCH that schedules the PDSCH. The PDCCH is located in the search space of the Type0-PDCCH CSS set. A CRC scrambled by the SI-RNTI is added to the PDCCH.

[0038] During initial cell access (including, for example, Cell Search, Cell selection / reselection, Random Access procedure, and RRC Connection Establishment procedure), the terminal device 40 (UE) configures CORESET #0 (CORESET for Type0-PDCCH search space set) and the Type0-PDCCH CSS set using the MIB. Specifically, the terminal device 40 (UE) receives an SSB and receives the MIB mapped to the PBCH included in the SSB. The 8-bit PDCCH configuration (pdcch-ConfigSIB1) included in the MIB configures the CORESET #0 configuration (controlResourceSetZero) and the PDCCH monitoring occasion configuration (SearchSpaceZero) of the Type0-PDCCH CSS set.

[0039] 7A to 7L are diagrams showing tables used for configuring CORESET #0. The configuration of CORESET #0 notified by the MIB is notified by an index represented by the most significant four bits of the PDCCH configuration (pdcch-ConfigSIB1) and the tables shown in Figs. 7A to 7L. The index represented by the most significant four bits of the PDCCH configuration (pdcch-ConfigSIB1) specifies the SS / PBCH block and CORESET multiplexing pattern, the number of RBs (Resource Blocks), the number of symbols, and the resource block offset from the SS / PBCH block of CORESET #0.

[0040] 8A to 8E are diagrams showing tables used to configure the PDCCH monitoring occasion of a Type0-PDCCH CSS set. The configuration of the PDCCH monitoring occasion of a Type0-PDCCH CSS set notified by the MIB is notified by an index represented by the four least significant bits of the PDCCH configuration (pdcch-ConfigSIB1) and the tables shown in Figures 8A to 8E. The index represented by the four least significant bits of the PDCCH configuration (pdcch-ConfigSIB1) specifies a value O that specifies the start slot of the PDCCH monitoring occasion of the Type0-PDCCH CSS set, the number of search space sets in the slot, a value M that indicates the relationship between the SS / PBCH block and the PDCCH monitoring occasion, and the first symbol index.

[0041] Here, an example of multiplexing an SS / PBCH block and a CORESET (SS / PBCH block and CORESET multiplexing pattern) will be described. Figures 9A to 9C are diagrams for explaining an example of multiplexing an SS / PBCH block and a CORESET. As shown in Figures 9A to 9C, three patterns of SS / PBCH block and CORESET multiplexing patterns are defined.

[0042] In pattern 1 shown in Figure 9A, the SS / PBCH block and the PDSCH carrying CORESET #0 and SIB1 are multiplexed using TDM (Time Division Multiplexing). In pattern 2 shown in Figure 9B, the SS / PBCH block and CORESET #0 are multiplexed using TDM, and the SS / PBCH block and the PDSCH carrying SIB1 are multiplexed using FDM (Frequency Division Multiplexing). In pattern 3 shown in Figure 9C, the SS / PBCH block and CORESET #0 are multiplexed using FDM, and the PDSCH carrying the SS / PBCH block and SIB1 are multiplexed using FDM.

[0043] After cell connection (for example, after transition to RRC_Connected on the PCell), the configuration of CORESET #0 and / or the configuration of Type0-PDCCH CSS set may be overwritten by dedicated RRC signaling (ie, RRCSetup message, RRCReconfiguration message).

[0044] SS / PBCH blocks can further be cell-defining SSBs and non-cell-defining SSBs. Cell-defining SSBs are defined as SS / PBCH blocks that have a CORESET for the Type0-PDCCH CSS set, and non-cell-defining SSBs are defined as SS / PBCH blocks that do not have a CORESET for the Type0-PDCCH CSS set.

[0045] The parameter k indicates whether the SSB is cell-defining or non-cell-defining. SSB In FR1, the detected SS / PBCH block is k SSB If k is 23 or less, it is a cell-defining SSB. SSB If k is 24 or more, it is a non-cell defining SSB. SSB If k is 12 or less, it is a cell-defining SSB. SSB If the value is 13 or more, it is a non-cell defining SSB.

[0046] If the detected SS / PBCH block is a cell-defining SSB, the terminal device attempts to receive SIB1 using pdcchConfig-SIB1 included in the MIB. On the other hand, if the detected SS / PBCH block is a non-cell-defining SSB, the terminal device attempts to detect the cell-defining SSB based on the frequency location (Global Synchronization Channel Number; GSCN) of the cell-defining SSB notified by Fig. 10A, Fig. 10B, and pdcchConfig-SIB1. In addition, in FR1, SSB is 31, and k in FR2 SSB indicates 15, it is notified that there is no cell-defining SSB in the frequency range that can be notified in FIGS. 10A and 10B.

[0047] In shared spectrum channel access (unlicensed band) operation, a discovery burst transmission window (DBTW) is set. Within the discovery burst transmission window, multiple SS / PBCH blocks of the same QCL can be transmitted. The terminal device (N DM-RS PBCH modN SSB QCL ) are assumed to have the same QCL for the SS / PBCH blocks of the serving cell within the same discovery burst transmission window. DM-RS PBCH is the index of the DMRS sequence of the PDCH, N SSB QCL is information indicating the number of QCLs of SSB, and is given by the LSB (Least Significant Bit) of subCarrierSpacingCommon and ssb-SubcarrierOffset according to FIG.

[0048] The discovery burst transmission window allows for more candidates for SS / PBCH blocks in shared spectrum channel access.

[0049] <FR3(Frequency Range 3)> In NR, frequency bands above 52.6 GHz can be supported. The frequency range from 52.6 GHz to 71 GHz is also called FR3.

[0050] In FR3, this may include both licensed and unlicensed bands.

[0051] Listen Before Talk (LBT) is implemented in the unlicensed band of FR3. When operating in an unlicensed band, a communication device performs sensing before transmitting a signal. If the power detected by sensing is lower than a predetermined threshold, the LBT is considered successful (the channel is clear) and signal transmission begins. On the other hand, if the power detected by sensing is higher than the predetermined threshold, the LBT is considered unsuccessful (the channel is busy) and signal transmission is stopped for a predetermined period of time.

[0052] In FR3, up to 64 different QCLs (different beams) of SS / PBCH blocks are provided, i.e., Lmax is 64 in FR3.

[0053] In FR3, uplink physical channels and downlink physical channels support subcarrier spacings (SCS) of 120 kHz, 480 kHz, and 960 kHz. In FR3, SS / PBCH blocks support all or some of the SCSs of 120 kHz, 240 kHz, 480 kHz, and 960 kHz.

[0054] As an example of the arrangement of SS / PBCH blocks for 480 kHz SCS, Case D or Case E may be applied. As an example of the arrangement of SS / PBCH blocks for 960 kHz SCS, Case D or Case E may be applied.

[0055] In FR3, bandwidths up to 2.16 GHz can be supported.

[0056] <Technical issues> At the 3GPP RAN1#104 meeting, it was agreed that the PBCH payload size and the number of PBCH DMRS sequences would not exceed the conventional sizes. That is, even in FR3, the SS / PBCH block will be designed so that the PBCH payload size does not exceed 32 bits and the number of PBCH DMRS sequences does not exceed 8.

[0057] On the other hand, in FR3 NR, a lot of system information can be sent in the MIB. Specifically, it is assumed that one or a combination of the following system information can be sent in the MIB: -systemFrameNumber - subCarrierSpacingCommon -ssb-SubcarrierOffset -dmrs-TypeA-Position -pdcch-ConfigSIB1 -cellBarred - intraFreqReselection -Information showing the number of SSB QCLs - Information indicating whether the operation is in a licensed or unlicensed band -spare

[0058] In particular, in FR3, the amount of information that can be notified, such as subCarrierSpacingCommon, ssb-SubcarrierOffset, information indicating the number of QCLs in an SSB, information indicating whether operation is in a licensed band or an unlicensed band, and candidate SSB index, may increase compared to the FR2 MIB.

[0059] subCarrierSpacingCommon is information indicating the SCS of the PDCCH of the Type0-PDCCH CSS set. In FR3, if SCSs of 120 kHz, 480 kHz, and 960 kHz are supported, two bits of information may be required.

[0060] ssb-SubcarrierOffset is information indicating the subcarrier offset between the SS / PBCH block and CORESET #0. In FR3, when specifying 960 kHz CORESET #0 from a 120 kHz SS / PBCH block, up to 96 different subcarrier offsets can be notified, so 7 bits of information may be required.

[0061] In FR3, seven different pieces of information, 1, 2, 4, 8, 16, 32, and 64, can be notified as information indicating the number of QCLs in SSB, so three bits of information may be required.

[0062] Information indicating whether the operation is in a licensed band or an unlicensed band is not present in the PBCH payload of FR2. By transmitting information indicating whether the operation is in a licensed band or an unlicensed band, the terminal device can switch between licensed and unlicensed operation from the initial connection. A specific example is the discovery burst transmission window. When notified of licensed band operation, the terminal device does not set (disable) the discovery burst transmission window and attempts to receive SS / PBCH blocks with up to 64 different indexes. On the other hand, when notified of unlicensed operation, the terminal device sets (enabled) the discovery burst transmission window and attempts to receive SS / PBCH blocks with 64 or more different indexes.

[0063] Note that operation in a licensed band may be an operation that does not require LBT even in an unlicensed band. For example, in an unlicensed band, if a transmission satisfies the conditions for not requiring LBT (e.g., the conditions for short control signaling), it may be considered an operation in a licensed band. Note that the condition for short control signaling is that the total transmission period of short control signaling is 10% (10 milliseconds) or less within 100 milliseconds.

[0064] Furthermore, if a discovery burst transmission window is configured, the total number of candidate SSB indices will be greater than 64. Therefore, more than 6 bits of information may be required to indicate the SSB index of FR2.

[0065] Due to the anticipated increase in the amount of information described above, if individual information bits are assigned, it will be difficult to design the SS / PBCH block in FR3 so that the PBCH payload size does not exceed 32 bits and the number of PBCH DMRS sequences does not exceed 8.

[0066] Overview of the proposed technology In the technology disclosed herein, two or more different fields (e.g., second information, third information) that specify configuration information included in the MIB are combined to form one field. An index (e.g., first information) of one field specifies two or more corresponding configuration information. By configuring the combination so that unnecessary states (e.g., reserved) are not specified, it is possible to reduce the number of bits or insert additional information into the MIB.

[0067] In another technique of the present disclosure, parameters that can be transmitted in the above-described MIBs are transmitted using two types of MIBs: a first MIB and a second MIB. The second MIB is transmitted in an SS / PBCH block different from the SS / PBCH block in which the first MIB is transmitted. Alternatively, the second MIB is transmitted in a Secondary PBCH. Alternatively, the second MIB is transmitted in DCI.

[0068] <<Configuration examples of each device>> <Configuration example of base station equipment> Next, a description will be given of the configuration of the base station device 20. Fig. 12 is a diagram illustrating an example configuration of the base station device 20 according to an embodiment of the present disclosure. The base station device 20 is a communication device (wireless system) that performs wireless communication with the terminal device 40. The base station device 20 is a type of information processing device.

[0069] Base station device 20 includes a signal processing unit 21, a storage unit 22, a network communication unit 23, and a control unit 24. Note that the configuration shown in Fig. 12 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of base station device 20 may be distributed and implemented in multiple physically separated devices.

[0070] The signal processing unit 21 is a wireless communication interface that performs wireless communication with other communication devices (for example, a terminal device 40 and another base station device 20). The signal processing unit 21 operates under the control of the control unit 24. The signal processing unit 21 may be compatible with multiple wireless access methods. For example, the signal processing unit 21 may be compatible with both NR and LTE. The signal processing unit 21 may be compatible with other cellular communication methods such as W-CDMA and cdma2000. Furthermore, the signal processing unit 21 may be compatible with a wireless LAN communication method in addition to the cellular communication method. Of course, the signal processing unit 21 may only be compatible with one wireless access method.

[0071] The signal processing unit 21 includes a reception processing unit 211, a transmission processing unit 212, and an antenna 113. The signal processing unit 21 may include a plurality of reception processing units 211, a plurality of transmission processing units 212, and a plurality of antennas 113. If the signal processing unit 21 supports a plurality of radio access methods, each unit of the signal processing unit 21 may be configured separately for each radio access method. For example, if the base station device 20 supports NR and LTE, the reception processing unit 211 and the transmission processing unit 212 may be configured separately for NR and LTE.

[0072] The reception processing unit 211 processes an uplink signal received via the antenna 113. The reception processing unit 211 includes a radio reception unit 211a, a demultiplexing unit 211b, a demodulation unit 211c, and a decoding unit 211d.

[0073] The radio receiving unit 211a performs down-conversion, removal of unnecessary frequency components, control of amplification level, quadrature demodulation, conversion to a digital signal, removal of guard intervals, extraction of frequency domain signals by fast Fourier transform, etc. on the uplink signal. For example, assume that the radio access method of the base station device 20 is a cellular communication method such as LTE. In this case, the demultiplexing unit 211b separates uplink channels such as PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) and uplink reference signals from the signal output from the radio receiving unit 211a. The demodulating unit 211c demodulates the received signal using a modulation method such as BPSK (Binary Phase Shift Keying) or QPSK (Quadrature Phase Shift Keying) for the modulation symbols of the uplink channel. The modulation method used by the demodulating unit 211c may be multi-level QAM such as 16QAM (Quadrature Amplitude Modulation), 64QAM, or 256QAM. The decoding unit 211d performs a decoding process on the coded bits of the demodulated uplink channel, and outputs the decoded uplink data and uplink control information to the control unit 24.

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

[0075] The encoder 212a encodes the downlink control information and downlink data input from the controller 24 using a coding method such as block coding, convolutional coding, or turbo coding. The modulator 212b modulates the coded bits output from the encoder 212a using a predetermined modulation method such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM. The multiplexer 212c multiplexes the modulation symbols of each channel and the downlink reference signal, and allocates the multiplexed signals to predetermined resource elements. The radio transmitter 212d performs various signal processing on the signal from the multiplexer 212c. For example, the radio transmitter 212d performs processing such as conversion to the time domain using fast Fourier transform, addition of a guard interval, generation of a baseband digital signal, conversion to an analog signal, quadrature modulation, up-conversion, removal of unnecessary frequency components, and power amplification. The signal generated by the transmission processor 212 is transmitted from the antenna 113.

[0076] The storage unit 22 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 22 functions as a storage means of the base station device 20.

[0077] The network communication unit 23 is a communication interface for communicating with other devices (e.g., other base station devices 20). For example, the network communication unit 23 is a LAN (Local Area Network) interface such as a NIC (Network Interface Card). The network communication unit 23 may be a USB (Universal Serial Bus) interface configured with a USB host controller, a USB port, etc. The network communication unit 23 may also be a wired interface or a wireless interface. The network communication unit 23 functions as a network communication means of the base station device 20. The network communication unit 23 communicates with other devices under the control of the control unit 24.

[0078] The control unit 24 is a controller that controls each unit of the base station device 20. The control unit 24 is realized by a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). For example, the control unit 24 is realized by a processor executing various programs stored in a storage device inside the base station device 20 using a RAM (Random Access Memory) or the like as a working area. The control unit 24 may also be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The CPU, MPU, ASIC, and FPGA can all be considered as controllers.

[0079] <Example of terminal device configuration> Next, a description will be given of the configuration of the terminal device 40. Fig. 13 is a diagram illustrating an example configuration of the terminal device 40 according to an embodiment of the present disclosure. The terminal device 40 is a communication device (wireless system) that performs wireless communication with the base station device 20. The terminal device 40 is a type of information processing device.

[0080] The terminal device 40 includes a signal processing unit 41, a storage unit 42, an input / output unit 44, and a control unit 45. Note that the configuration shown in Fig. 13 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the terminal device 40 may be distributed and implemented in multiple physically separated configurations.

[0081] The signal processing unit 41 is a wireless communication interface that performs wireless communication with other communication devices (for example, the base station device 20 and other terminal devices 40). The signal processing unit 41 operates under the control of the control unit 45. The signal processing unit 41 supports one or more wireless access methods. For example, the signal processing unit 41 supports both NR and LTE. The signal processing unit 41 may also support other wireless access methods, such as W-CDMA (registered trademark) and cdma2000 (registered trademark).

[0082] The signal processing unit 41 includes a reception processing unit 411, a transmission processing unit 412, and an antenna 213. The signal processing unit 41 may include a plurality of reception processing units 411, a plurality of transmission processing units 412, and a plurality of antennas 213. When the signal processing unit 41 supports a plurality of radio access methods, each unit of the signal processing unit 41 may be configured separately for each radio access method. For example, the reception processing unit 411 and the transmission processing unit 412 may be configured separately for LTE and NR. The configurations of the reception processing unit 411 and the transmission processing unit 412 are similar to those of the reception processing unit 211 and the transmission processing unit 212 of the base station device 20.

[0083] The storage unit 42 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 42 functions as a storage means of the terminal device 40.

[0084] The input / output unit 44 is a user interface for exchanging information with the user. For example, the input / output unit 44 is an operation device such as a keyboard, a mouse, operation keys, or a touch panel that allows the user to perform various operations. Alternatively, the input / output unit 44 is a display device such as a liquid crystal display (LCD) or an organic electroluminescence display (OLED). The input / output unit 44 may be an audio device such as a speaker or a buzzer. The input / output unit 44 may also be a lighting device such as an LED (Light Emitting Diode) lamp. The input / output unit 44 functions as input / output means (input means, output means, operation means, or notification means) of the terminal device 40.

[0085] The control unit 45 is a controller that controls each part of the terminal device 40. The control unit 45 is realized by a processor such as a CPU or MPU, for example. For example, the control unit 45 is realized by the processor executing various programs stored in a storage device inside the terminal device 40 with a RAM or the like as a work area. Note that the control unit 45 may be realized by an integrated circuit such as an ASIC or FPGA. Each of the CPU, MPU, ASIC, and FPGA can be regarded as a controller.

[0086] <<Technical Features>> As described above, since the upper limits of the number of bits that the PBCH payload and the MIB can carry are defined, it is necessary to define restricted or compressed system information.

[0087] <Configuration of MIB of FR3> Therefore, in an embodiment of the present disclosure, an SS / PBCH block of FR3 different from that of FR1 or FR2 is assumed. Specifically, at least the configuration of the MIB carried by the SS / PBCH block of FR3 is different from the configuration of the MIB of the SS / PBCH block of FR1 or FR2.

[0088] <PDCCH Setting> As an example of the configuration of the MIB of FR3, the information indicated by the PDCCH setting (pdcch-ConfigSIB1) is different from the PDCCH setting (pdcch-ConfigSIB1) included in the MIBs of FR1 and FR2.

[0089] As a specific example of information indicated by the PDCCH configuration (pdcch-ConfigSIB1) of FR3, the PDCCH configuration indicates one index. The PDCCH configuration index indicates a combination of the index of the CORESET #0 configuration and the index of the PDCCH monitoring occasion configuration of the Type0-PDCCH CSS set. In other words, the terminal device recognizes the combination of the index of the CORESET #0 configuration and the index of the PDCCH monitoring occasion configuration of the Type0-PDCCH CSS set from the PDCCH configuration indexes included in the received MIB. In yet another way, the base station device causes the terminal device to recognize the combination of the index of the CORESET #0 configuration and the index of the PDCCH monitoring occasion configuration of the Type0-PDCCH CSS set, using the PDCCH configuration index included in the MIB to be transmitted.

[0090] FIG. 15 is an example of a diagram showing a table used for PDCCH configuration when the SCS of {SS / PBCH block, PDCCH} is {120, 120} kHz. In the table of FIG. 15, 60 combinations of the index of the CORESET #0 configuration (controlResourceSetZero) and the index of the PDCCH monitoring occasion configuration (searchSpaceZero) of the Type0-PDCCH CSS set are specified. The CORESET #0 configuration and the PDCCH monitoring occasion configuration of the Type0-PDCCH CSS set notified by the MIB are notified by the index of the PDCCH configuration (pdcch-ConfigSIB1) and the tables shown in FIG. 15, FIG. 7J, and FIG. 8B and FIG. 8E. The index indicated by the PDCCH configuration (pdcch-ConfigSIB1) specifies the index of the CORESET #0 configuration and the index of the PDCCH monitoring occasion configuration of the Type0-PDCCH CSS set.

[0091] 15 does not include combinations of non-configurable CORESET #0 settings and PDCCH monitoring occasion settings of Type0-PDCCH CSS set. For example, it does not include combinations of CORESET #0 setting indexes 0 to 3 indicating that the multiplexing pattern of SS / PBCH blocks and CORESET is 1 and the PDCCH monitoring occasion setting of Type0-PDCCH CSS set when the multiplexing pattern of SS / PBCH blocks and CORESET is 3.

[0092] Furthermore, the table of Figure 15 does not include indexes indicated as Reserved in Figure 7J, Figure 8B, and Figure 8E. Specifically, indexes 8 to 15 in Figure 7J, indexes 14 and 15 in Figure 8B, and indexes 1 to 15 in Figure 8E are not included in the table of Figure A. That is, the table of Figure 15 is made up of 60 combinations represented by all combinations of the four states in Figure 7J where the multiplexing pattern of SS / PBCH blocks and CORESET indicates 1 and the 14 states in Figure 8B, and the combination of the four states in Figure 8E where the multiplexing pattern of SS / PBCH blocks and CORESET indicates 3 and the one state in Figure 8E.

[0093] By limiting the patterns of these combinations, it is possible to reduce the number of bits required for reporting the PDCCH configuration. Specifically, only 60 combinations are specified in the table of FIG. 15. Therefore, the PDCCH configuration for FR3 can be expressed in the table of FIG. 15 using 6 bits, which can reduce 2 bits from the 8-bit PDCCH configuration for FR1 and FR2. Note that while 64 combinations can be expressed using 6 bits, only 60 combinations are required in the table of FIG. 15. In other words, the remaining 4 combinations may be indexes for representing other settings (other parameters described above or below) or may be reserved.

[0094] Furthermore, the referenced CORESET #0 settings and the table for setting the PDCCH monitoring occasion of the Type0-PDCCH CSS set may be the same as those for FR2, or a table specific to FR3 may be defined.

[0095] As another specific example of information indicated by the PDCCH configuration (pdcch-ConfigSIB1) of FR3, the PDCCH configuration indicates one index. The index of the PDCCH configuration specifies PDCCH-related parameters (SS / PBCH block and CORESET multiplexing pattern, number of RBs (Resource Blocks), number of symbols, and resource block offset from the SS / PBCH block of CORESET#0, and, for Type0-PDCCH CSS set, value O specifying the start slot of the PDCCH monitoring occasion, number of search space sets in the slot, value M indicating the relationship between the SS / PBCH block and the PDCCH monitoring occasion, and first symbol index) without referring to other tables.

[0096] Figure 16 is an example of a diagram showing a table used for PDCCH configuration when the SCS of {SS / PBCH block, PDCCH} is {120, 120} kHz. The table in Figure 16 specifies 60 combinations of the SS / PBCH block and CORESET multiplexing pattern, the number of RBs (Resource Blocks), the number of symbols, and the resource block offset from the SS / PBCH block of CORESET#0, and the value O specifying the start slot of the PDCCH monitoring occasion, the number of search space sets in the slot, the value M indicating the relationship between the SS / PBCH block and the PDCCH monitoring occasion, and the first symbol index of the Type0-PDCCH CSS set. These PDCCH-related parameters are specified by an index indicated by the PDCCH configuration (pdcch-ConfigSIB1).

[0097] As shown in FIG. 16, by defining a table different from the table of parameter sets related to the PDCCH of FR2, it is possible to define parameters specific to FR3 without affecting the terminal device 40 of FR2.

[0098] As another specific example of information indicated by the PDCCH configuration (pdcch-ConfigSIB1) of FR3, the PDCCH configuration indicates one index. The index of one PDCCH configuration indicates a combination of the index of the CORESET #0 configuration and the index of the PDCCH monitoring occasion configuration of the Type0-PDCCH CSS set, and further indicates the SCS of the PDCCH.

[0099] The SCS of the PDCCH is associated with the multiplexing pattern of the SS / PBCH block and CORESET. For example, if the SCS of the SS / PBCH block and the PDCCH are the same, multiplexing pattern 2 is not applied and multiplexing pattern 3 is applicable. If the SCS of the SS / PBCH block and the PDCCH is double or half, multiplexing pattern 3 is not applied and multiplexing pattern 2 is applicable. If the SCS of the SS / PBCH block and the PDCCH is four times or more or one-quarter or less, multiplexing patterns 2 and 3 are not applied and only multiplexing pattern 1 is applied. By combining (linking) information related to these settings and specifying a table that excludes impossible patterns and expressing it as a single field, the amount of information bits required for the SCS of the PDCCH and PDCCH settings can be further reduced.

[0100] Note that even if the number of bits in the PDCCH configuration is reduced, when a non-cell defining SSB is indicated, the frequency location (GSCN) of the cell defining SSB may be indicated as the number of bits in the conventional PDCCH configuration. In this case, the frequency location (GSCN) of the cell defining SSB is indicated using other information bits in addition to the PDCCH configuration. Examples of other information bits include information related to unlicensed bands, subCarrierSpacingCommon, spare, etc. As a specific example, k SSB If the SS / PBCH block detected by is indicated as a cell-defining SSB, 6 bits of PDCCH configuration and 2 bits of information related to unlicensed bands are indicated. SSB If the SS / PBCH block detected by is determined to be a non-cell defining SSB, 8 bits of information indicating the frequency location of the cell defining SSB is displayed.

[0101] Alternatively, when the number of bits in the PDCCH configuration is reduced, the range in which the frequency position of the cell defining SSB (GSCN) can be reported may be reduced as well. As a specific example, when the number of bits in the PDCCH configuration is reduced from 8 bits to 6 bits, the range in which the frequency position of the cell defining SSB (GSCN) can be reported is reduced to a range from +64 to -64, as shown in Fig. 17.

[0102] <SCSとサブキャリアオフセット> An example of an FR3 MIB configuration would be the following two pieces of information: (a) SCS of PDCCH of Type0-PDCCH CSS set, (b) Subcarrier offset between SS / PBCH block and CORESET #0 is specified by one index. In FR3, subCarrierSpacingCommon and ssb-SubcarrierOffset are not notified by individual fields, and one new field (e.g., SCSandSsb-SubcarrierOffset) is included in the MIB. In other words, the terminal device recognizes the combination of (a) the SCS of the PDCCH of the Type0-PDCCH CSS set and (b) the subcarrier offset of the SS / PBCH block and CORESET #0 from one index (e.g., SCSandSsb-SubcarrierOffset) included in the received MIB. In further other words, the base station device causes the terminal device to recognize the combination of (a) the SCS of the PDCCH of the Type0-PDCCH CSS set and (b) the subcarrier offset of the SS / PBCH block and CORESET #0, using one index (e.g., SCSandSsb-SubcarrierOffset) included in the MIB it transmits.

[0103] FIG. 18 is an example of a table showing combinations of subCarrierSpacingCommon and ssb-SubcarrierOffset when the SS / PBCH block is 120 kHz. When the SCS of {SS / PBCH block, PDCCH} is {120, 120} kHz, the maximum number of possible subcarrier offsets is 12. When the SCS of {SS / PBCH block, PDCCH} is {120, 480} kHz, the maximum number of possible subcarrier offsets is 48. By expressing these related parameters using a single index, 60 patterns can be configured and signaled using 6 bits. In the conventional method of individual signaling, 1 bit is required to signal the SCS and 6 bits are required to signal the subcarrier offset. Compared to the conventional method of individual signaling, this method reduces the amount of information required by 1 bit.

[0104] Note that in FIG. 18 as well, the remaining indexes (60 to 63) that can be notified using 6 bits can be used to notify whether the SSB is a cell-defining SSB (an SS / PBCH block having a CORESET for the Type0-PDCCH CSS set) or a non-cell-defining SSB (an SS / PBCH block without a CORESET for the Type0-PDCCH CSS set). That is, when the index is notified as 61 or greater, the terminal device recognizes that a CORESET for the Type0-PDCCH CSS set is not set from the detected MIB. In other words, by notifying that the index is 61 or greater, the base station device can make the terminal device recognize that a CORESET for the Type0-PDCCH CSS set is not set from the MIB. Then, the index and pdcchConfig-SIB1 defined in FIG. 19 can be used to specify the frequency position (global synchronization channel number; GSCN) of the nearest cell-defining SSB in the frequency direction. Furthermore, when the index is specified as 63, it can be notified that no cell-defining SSB exists within the range that can be specified by the CSCN.

[0105] That is, one new field (e.g., SCSandSsb-SubcarrierOffset) contains the SCS and SS / PBCH block of the PDCCH in the Type0-PDCCH CSS set, and the subcarrier offset k SSB , and the frequency location of the cell-defining SSB.

[0106] Note that FIG. 18 has described combinations of subCarrierSpacingCommon and ssb-SubcarrierOffset when the SS / PBCH block is 120 kHz at 120 kHz or 480 kHz as possible settings for the SCS of the PDCCH in the Type0-PDCCH CSS set. However, the present method is not limited to these combinations and can also be applied to cases where the possible settings for the SCS of the PDCCH in the Type0-PDCCH CSS set are {120 kHz, 960 kHz}, {480 kHz, 960 kHz}, and {120 kHz, 480 kHz, 960 kHz}, and can achieve similar effects.

[0107] <Information related to unlicensed bands> Information related to unlicensed bands includes information indicating whether the operation is in a licensed band (operation without shared spectrum channel access, cell without CCA) or an unlicensed band (operation with shared spectrum channel access, cell with CCA), and the number of QCLs in SSB, N SSB QCLIn FR3, it is possible to define one table containing multiple indexes that specify a combination of this information. Using one table, settings related to two unlicensed bands are notified by the index of one new field. In other words, the terminal device can determine from one index (an index that specifies a combination of information indicating whether the operation is in a licensed band or an unlicensed band and information indicating the number of QCLs in the SSB) included in the received MIB, information indicating whether the operation is in a licensed band (operation without shared spectrum channel access, cell without CCA) or an unlicensed band (operation with shared spectrum channel access, cell with CCA) and the number of QCLs in the SSB, N SSB QCL In other words, the base station device uses one index (an index specifying a combination of information indicating whether the operation is in a licensed band or an unlicensed band and information indicating the number of QCLs in the SSB) to be included in the MIB to be transmitted, to recognize the combination of information indicating whether the operation is in a licensed band (operation without shared spectrum channel access, cell without CCA) or an unlicensed band (operation with shared spectrum channel access, cell with CCA) and the number of QCLs in the SSB, N SSB QCL The terminal device recognizes a combination of information indicating the above.

[0108] Figure 20 is an example of a table used for settings related to unlicensed bands. The index of a setting related to one unlicensed band includes information indicating whether the operation is a licensed band operation (operation without shared spectrum channel access, cell without CCA) or an unlicensed band operation (operation with shared spectrum channel access, cell with CCA), and the number of QCLs in SSB, N SSB QCL In licensed band operation, a discovery burst transmission window is not required, so the number of SSB QCLs, N SSB QCL On the other hand, in unlicensed band operation, a discovery burst transmission window is required, so the number of QCLs in SSB, N SSB QCL is also specified.

[0109] As shown in Figure 20, these combinations can be specified in 8 states and can be notified with 3 bits. When notifying individually, 1 bit indicates whether the operation is in a licensed band or an unlicensed band, and the number of QCLs in SSB, N SSB QCL Since three bits were required to notify the number, one bit can be reduced if it is composed of one field.

[0110] In addition, information related to unlicensed bands can also be defined as a single table, including information indicating candidate SSB indices.

[0111] <Second MIB> In another embodiment of the present disclosure, the FR3 MIB is divided into a first MIB and a second MIB. As the FR3 SS / PBCH block, the first SS / PBCH block carrying the first MIB and the second SS / PBCH block carrying the second MIB may be defined.

[0112] The first MIB and the second MIB have different configurations. The first and second SS / PBCH blocks are transmitted in a predetermined bandwidth. The SS / PBCH blocks allocated in the predetermined bandwidth carry either the first MIB or the second MIB. The terminal device acquires information on all MIBs by receiving both SS / PBCH blocks. The base station device provides information on all MIBs to the terminal device by transmitting both SS / PBCH blocks.

[0113] The SS / PBCH block in this embodiment includes at least information indicating whether it is the first MIB or the second MIB.

[0114] The first and second SS / PBCH blocks are multiplexed in the time or frequency axis.

[0115] An example of multiplexing the first and second SS / PBCH blocks is multiplexing in the time axis.

[0116] For example, the first SS / PBCH block is allocated to a radio frame with an odd SFN, and the second SS / PBCH block is allocated to a radio frame with an even SFN. In this case, the SFN is information that implicitly indicates whether it is the first MIB or the second MIB.

[0117] In another example, the first SS / PBCH block is placed in the earlier half frame and the second SS / PBCH block is placed in the later half frame, where the half frame index implicitly indicates whether it is the first or second MIB.

[0118] An example of multiplexing the first and second SS / PBCH blocks is multiplexing in the frequency axis.

[0119] For example, the first and second SS / PBCH blocks are transmitted at different frequencies within the band of the initial BWP. In this case, it is preferable that the first and second MIBs include a common PDCCH configuration. This makes it possible to recognize the initial BWP when either MIB is acquired.

[0120] As another example, the first SS / PBCH block is transmitted in a primary cell, and the second SS / PBCH block is transmitted in a secondary cell. The second MIB can be configured by utilizing the MIB area of ​​the SS / PBCH block operated as the secondary cell.

[0121] As another example, the first SS / PBCH block is a cell-defining SSB and the second SS / PBCH block is a non-cell-defining SSB.

[0122] The first MIB may include information notifying the location (frequency and / or time) of the SS / PBCH block carrying the second MIB. The second MIB may include information notifying the location of the SS / PBCH block carrying the first MIB. The terminal device first detects an SS / PBCH block including one of the MIBs and receives the first MIB or the second MIB. Based on information included in the MIB about the location of the SS / PBCH block carrying the other MIB, the terminal device attempts to receive the other SS / PBCH block. Then, if the terminal device has received both the first MIB and the second MIB, it attempts to receive the SIB.

[0123] If the terminal device receives the first or second MIB but fails to receive the other MIB within a predetermined time, the terminal device discards the information of the first or second MIB that it has received. The predetermined time may be specified by a standard, may be set from a higher layer (e.g., may be set by configuration information included in an RRC message transmitted from a base station device), or may be determined when the terminal device is manufactured.

[0124] <Secondary PBCH> Another embodiment of the present disclosure is a method of transmitting a second PBCH (secondary PBCH) to transmit an MIB to an FR3 terminal device 40. This secondary PBCH includes at least part of MSI (Minimum System Information) information for the FR3 terminal device. The secondary PBCH includes a second MIB.

[0125] Other details about the physical configuration and information of the secondary PBCH will be described later.

[0126] Here, a method for indicating a secondary PBCH will be described. Fig. 14 is a diagram for explaining a method for indicating a secondary PBCH according to an embodiment of the present disclosure.

[0127] More specifically, the presence of the secondary PBCH is indicated by, for example, a spare bit (reserved bit, extended bit) included in the PBCH payload or MIB. For example, the presence of the secondary PBCH is indicated by one spare bit included in the MIB. When transmitting a secondary PBCH corresponding to an SSB, the base station device 20 indicates the presence of the secondary PBCH using the spare bit. The terminal device 40 determines whether or not a secondary PBCH is being transmitted using the spare bit. If indicated by the spare bit, the terminal device 40 attempts to receive the secondary PBCH.

[0128] Candidate resources for the secondary PBCH may be indicated by a combination of the periodicity of the secondary PBCH, a time offset (frame offset, half-frame offset, slot offset, etc.) from the SSB resources or the resources of the first CORESET#0 and Type0-PDCCH CSS set, and / or a frequency offset (PRB offset, subcarrier offset).

[0129] Note that secondary PBCH resource candidates may be overwritten by RRC signaling (for example, any System Information (SIB-X), an RRC Setup message, or an RRC Reconfiguration message). That is, secondary PBCH resource A to secondary PBCH resource D are configured by RRC signaling, and after receiving the RRC signaling, second terminal device 40B refers to the positions of configured secondary PBCH resource A to secondary PBCH resource D. On the other hand, default positions are configured for secondary PBCH resource candidates, and before they are configured by RRC signaling, second terminal device 40B refers to the default positions of secondary PBCH resource A to secondary PBCH resource D.

[0130] The base station device 20 notifies the terminal device 40 of the position (actual transmission position) of the secondary PBCH that is actually transmitted. This notification may be used for rate matching of the PDSCH of the terminal device 40. Specifically, this allows the terminal device 40 to recognize the resources of the secondary PBCH. When receiving the PDSCH, the terminal device 40 can attempt decoding while avoiding the resources of the secondary PBCH, thereby improving the reception characteristics of the PDSCH. This notification may also be notified as information on the position of a secondary PBCH that is not actually transmitted.

[0131] As a method of notification, for example, there is a method using a ratematchPattern. For example, the base station device 20 sets, as a rate match pattern, a resource element where a secondary PBCH is arranged, for the first terminal device 40A after RRC connection. The first terminal device 40A can recognize that the resource specified by the ratematchPattern is not its own physical channel. Alternatively, when the cell to which the first terminal device 40A is connected is a TDD cell, there is a method of performing the notification using UL symbols or Flexible symbols. In this case, for the first terminal device 40A, a secondary PBCH is arranged in the resource indicated by the UL symbol according to the TDD-DL-UL-config notified by the SIB. Also, as a method of the notification, for example, there is a method using SSBBurstPosition (or SSBPositionsInBurst). In this case, for example, a secondary PBCH is arranged in a resource element where an SSB is not actually transmitted. When using SSBBurstPosition as the method of the notification, the SSBBurstPosition (or SSBPositionsInBurst) for the SS / PBCH block (SSB) including the primary PBCH and the SSBBurstPosition (or SSBPositionsInBurst) indicating the arrangement of the secondary PBCH may be included in the RRC signaling notified as being distinguished from each other (different IEs).

[0132] <Configuration example of secondary PBCH> Here, a physical configuration example of the secondary PBCH described above will be explained.

[0133] (Configuration) The secondary PBCH is composed of an encoded additional MIB (MIB2, MIB for low-capability NR devices, hereinafter also referred to as the second MIB) and DMRS used for demodulating the payload of the secondary PBCH.

[0134] As described above, the second MIB includes some of the parameters of the MIBs described above. In addition, the secondary PBCH (the second MIB, the secondary PBCH payload, and / or the physical parameters of the secondary PBCH) may include the following information: - Connection prohibition (barring) information for a predetermined terminal device 40 -Information about QCL with SIB (Type0-PDCCH DMRS and PDSCH DMRS) -Extension bits for forward compatibility (spare bits, reserved bits) Information regarding the initial DL bandwidth part (or default bandwidth part) for the second terminal device 40B -TDD configuration (uplink, downlink, and flexible symbol information) -Information on whether it is a non-cell defining SSB and the frequency location of a cell-defining SSB - Information regarding paging of the second terminal device 40B -Information about cell selection for the second terminal device 40B -Information regarding DRX of the second terminal device 40B -Extended SFN (e.g., hyper SFN) information - Number of transmit antenna ports for secondary PBCH and SIB

[0135] 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 for the secondary PBCH and extended SFN information are reported according to the pattern of the CRC scrambling mask of the secondary PBCH.

[0136] Note that some of the parameters that can be sent in the MIB described above may not be included in the secondary PBCH, but may instead be included in SIB1.

[0137] 21 is a diagram illustrating a configuration example of a secondary PBCH according to an embodiment of the present disclosure. For example, the secondary PBCH is configured with 24 PRBs or less (24 PRBs in FIG. 21).

[0138] In the Secondary PBCH, symbols are determined according to the amount of information in the second MIB and the coding rate. As an example, the Secondary PBCH is configured with two symbols, and a 24-bit second MIB is transmitted. If the amount of information transmitted in the Secondary PBCH is small, the Secondary PBCH may be configured with one symbol. Also, if the amount of information transmitted in the Secondary PBCH is large or if a low coding rate is required, the Secondary PBCH may be configured with four or seven symbols. The number of symbols in the Secondary PBCH may be indicated by the SS / PBCH block.

[0139] As shown in Fig. 21, the Secondary PBCH is transmitted together with a reference signal (DMRS) for demodulating the Secondary PBCH. For example, the DMRS is arranged every 4 REs on the frequency axis. The DMRS of the Secondary PBCH does not need to be included in every symbol. However, since including it at the beginning reduces demodulation delay, it is preferable to include it in the beginning symbol. In the example of Fig. 21, the DMRS is arranged every two symbols. In the example of Fig. 21, the DMRS is included in the first and third symbols, but not in the second and fourth symbols.

[0140] (period) The Secondary PBCH is arranged at a period equal to or longer than the period of the SS / PBCH block. As an example, in the initial cell selection, the Secondary PBCH is arranged at a period equal to the period of the SS / PBCH block. In the initial cell selection, the second terminal device 40B assumes that the Secondary PBCH occurs at a period of two radio frames (20 subframes, 20 msec).

[0141] The period of the Secondary PBCH may be notified separately from the period of the SS / PBCH block. Specifically, the period of the Secondary PBCH may be set using a parameter different from the parameter (SMTC: SSB Measurement Timing Configuration) that specifies the period of the SS / PBCH block.

[0142] Furthermore, the secondary PBCHs allocated to the same center frequency carry the same second MIB for a predetermined period of time. The predetermined period is 80 msec. However, the predetermined period may be longer than 80 msec. The predetermined period may be, for example, 160 msec or 320 msec.

[0143] In addition, the number of SS / PBCHs in one burst may differ from the number of secondary PBCHs. In other words, the information on the SSB that is actually being transmitted (ssb-PositionsInBurst) and the information on the secondary PBCH that is actually being transmitted (SPBCH-PositionsInBurst) may be set separately.

[0144] (Time / Frequency Resources) The secondary PBCH is frequency-multiplexed or time-multiplexed with the SS / PBCH block. Five examples of methods for multiplexing the secondary PBCH and the SS / PBCH block are described below.

[0145] Example 1 Fig. 22 is a diagram for explaining an example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. Fig. 22 shows a case where an SS / PBCH block and a secondary PBCH are frequency-multiplexed. In Fig. 22, the horizontal direction represents time, and the vertical direction represents frequency.

[0146] For example, the secondary PBCH is arranged in a different resource block in the same symbol as the corresponding SS / PBCH block. In the example of Figure 22, the secondary PBCH is arranged in a resource block above the SS / PBCH block.

[0147] The arrangement of the secondary PBCH is not limited to the example in Figure 22, and for example, the secondary PBCH may be arranged in a resource block below the SS / PBCH block. The beginning of the resource block where the secondary PBCH is arranged (or the center of the resource block, or the end of the resource block) may be indicated by the SS / PBCH block.

[0148] Example 2 Figure 23 is a diagram for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. Figure 23 illustrates a case where an SS / PBCH block and a secondary PBCH are time-multiplexed. In Figure 23, the horizontal direction represents time, and the vertical direction represents frequency.

[0149] For example, the secondary PBCH is included in the half frame following the half frame including the SS / PBCH block burst. In the example of FIG. 23, the SS / PBCH block is placed in the first half frame of the resources in which the SS / PBCH block is placed, and the secondary PBCH is placed in the second half frame. Note that the half frame including the secondary PBCH may be the third or fourth half frame. Note that the half frame including the secondary PBCH may be indicated by the SS / PBCH block.

[0150] Example 3 Figure 24 is a diagram for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. Figure 24 illustrates a case in which the SS / PBCH block and the secondary PBCH are time-multiplexed and the secondary PBCH is composed of one symbol. In Figure 24, the horizontal direction represents time and the vertical direction represents frequency.

[0151] When the Secondary PBCH is composed of one symbol, the Secondary PBCH is included in the half frame that includes the SS / PBCH block burst, as shown in Figure 24. Specifically, the Secondary PBCH is allocated to the fifth subframe of the half frame that includes the SS / PBCH block burst. The Secondary PBCHs corresponding to SS / PBCH block indices #0 to #3 are allocated to symbols #2, #3, #4, and #5, respectively, and the Secondary PBCHs corresponding to SS / PBCH block indices #4 to #7 are allocated to symbols #8, #9, #10, and #11, respectively.

[0152] Example 4 Figure 25 is a diagram for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. Figure 25 illustrates a case in which the SS / PBCH block and the secondary PBCH are time-multiplexed and the secondary PBCH is composed of one symbol. In Figure 25, the horizontal direction represents time and the vertical direction represents frequency.

[0153] As another example of the above example 3, some SS / PBCH blocks may not be transmitted and the resources may be used to transmit the secondary PBCH. In this case, as shown in FIG. 25, SS / PBCH blocks #6 and #7 are not transmitted, and instead, six secondary PBCHs corresponding to SS / PBCH block indexes #0 to #5 are transmitted.

[0154] Example 5 Figure 26 is a diagram for explaining another example of a method for multiplexing a secondary PBCH and an SS / PBCH block according to an embodiment of the present disclosure. Figure 26 illustrates a case in which the SS / PBCH block and the secondary PBCH are time-multiplexed and the periods of the SS / PBCH block and the secondary PBCH are different. In Figure 26, the horizontal direction represents time, and the vertical direction represents frequency.

[0155] In this example, the SS / PBCH block period is set to 20 msec, while the secondary PBCH period is set to 40 msec. In this case, the secondary PBCHs corresponding to SS / PBCH block indexes #0 to #3 are allocated to the sixth and seventh subframes of the first SS / PBCH block period. Furthermore, the secondary PBCHs corresponding to SS / PBCH block indexes #4 to #7 are allocated to the sixth and seventh subframes (the 26th and 27th subframes from the beginning) of the second SS / PBCH block period.

[0156] (precoding) Random precoding may be applied to the transmission of the secondary PBCH. Specifically, different precoding may be applied between predetermined resources (e.g., 6 PRBs and 1 symbol, 24 PRBs and 4 symbols) in the secondary PBCH for transmission. The second terminal device 40B attempts to demodulate the precoded secondary PBCH using the DMRS included in the predetermined resources. Furthermore, different precoding is applied to different secondary PBCHs due to random precoding. The second terminal device 40B does not assume that the same precoding is applied to two different secondary PBCHs.

[0157] Space Frequency Block Coding (SFBC) may 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.

[0158]

number

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

[0160]

number

[0161] (Encoding / Scrambling) The secondary PBCH is encoded using a polar code. However, the secondary PBCH may be encoded using other codes such as a low density parity check (LDPC) code, a convolutional code, or a turbo code. The SS / PBCH block may indicate which coding is being applied.

[0162] The secondary PBCH is preferably scrambled by the SS / PBCH block index. For example, Equation (3) is applied to scramble the secondary PBCH.

[0163]

Number

[0164] 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 Mbit represents the number of information bits of the PBCH.

[0165] (QCL (Quasi-Co-Location)) The secondary PBCH is QCL with the SS / PBCH block. Specifically, the terminal device 40 may assume that the SS / PBCH block having a predetermined index and the DMRS of the secondary PBCH corresponding to the predetermined index are QCL (quasi co-located) from one or more viewpoints of Doppler spread, Doppler shift, average delay, delay spread, and spatial Rx parameters.

[0166] Note that one SS / PBCH block and one secondary PBCH may be QCL, or one SS / PBCH block and a plurality of secondary PBCHs may be QCL. When one SS / PBCH block and a plurality of secondary PBCHs are QCL, the terminal device 40 can perform soft combining of the plurality of secondary PBCHs.

[0167] <Physical Parameters of PBCH> As another example, some of the information of the parameters that can be sent in the above-mentioned MIB is notified using the physical parameters of the PBCH other than the DMRS sequence.

[0168] An example of a PBCH physical parameter is the PBCH mask. Multiple masks can be defined for the PBCH CRC. MIB information is reported according to the mask that successfully decoded the PBCH.

[0169] An example of a PBCH physical parameter is the PBCH scrambling sequence. MIB information is notified in accordance with the scrambling sequence that was successfully decoded.

[0170] An example of a PBCH physical parameter is the position of the SS / PBCH block. MIB information is notified depending on the timing at which the SS / PBCH block is detected. More specifically, if a terminal device detects an SS / PBCH block whose candidate SS / PBCH block index is equal to or greater than the maximum number of SS / PBCH block indexes (64) for licensed band operation, the terminal device can recognize that it is operating in an unlicensed band.

[0171] <Other Downlink Physical Channels> As another example, in FR3, some of the parameters that may be sent in the MIB described above may be sent in other downlink physical channels received later, such as DCI and PDSCH.

[0172] Some of the parameters that can be sent in the MIB described above are sent, for example, in DCI format 1_0.

[0173] Some of the parameters that can be sent in the MIB described above are sent by the PDSCH, for example, included in SIB1.

[0174] As a result, the initial access procedure can be provided to the terminal device 40 of FR3.

[0175] The scope of application of the embodiments of the present disclosure is not limited to the FR3 terminal device 40. In the future, if the above-described problems arise in a new frequency range (for example, a frequency range FR0 lower than FR1 or a frequency range FR4 higher than FR3), the embodiments of the present disclosure may be applicable.

[0176] Furthermore, the scope of application of the embodiments of the present disclosure is not limited to the base station device 20 and the terminal device 40. The embodiments of the present disclosure are applicable as long as they are between a communication device that provides a MIB and a communication device that receives a MIB. As an example, the embodiments of the present disclosure are also applicable to backhaul communication between base station device 20 and base station device 20 in IAB (Integrated Access and Backhaul). As another example, the embodiments of the present disclosure are also applicable to sidelink communication between terminal device 40 and terminal device 40 as long as the terminal device 40 provides a MIB.

[0177] <Modification> Some of the above-described embodiments or parts thereof may be applied to the above-described dual connectivity (e.g., EUTRA-EUTRA dual connectivity, EUTRA-NR dual connectivity (ENDC), EUTRA-NR dual connectivity with 5GC, NR-EUTRA dual connectivity (NEDC), NR-NR dual connectivity). More specifically, the above-described operations in the physical layer (e.g., transmission of the PBCH, generation and configuration of various parameters (e.g., the above-described PDCCH configuration) in the PBCH (in the MIB)) may be performed by the base station device 20 as the master node, by the base station device 20 as the secondary node, or by both the MN and the SN. Additionally or alternatively, the above-described RRC signaling may be transmitted from the MN (base station device 20) to the UE (terminal device 40) even if the application destination is a cell managed by the SN. The SN (base station device 20) may establish an SRB3 between itself and the UE (terminal device 40) and transmit the signal directly via the SRB3.

[0178] The terminal device or base station device of this embodiment may be realized by a dedicated computer system or a general-purpose computer system.

[0179] For example, a communication program for executing the above-described operations is stored in a computer-readable recording medium such as an optical disk, a semiconductor memory, a magnetic tape, or a flexible disk and distributed. Then, for example, the program is installed in a computer, and the above-described processing is executed to configure a control device. In this case, the control device may be the terminal device 40, the base station device 20, or another external device (for example, a personal computer). Furthermore, the control device may be an internal device of the terminal device 40 or the base station device 20 (for example, the respective control units).

[0180] The communication program may also be stored in a disk device provided in a server device on a network such as the Internet, and may be downloaded to a computer. The above-mentioned functions may also be realized by cooperation between an OS (Operating System) and application software. In this case, the parts other than the OS may be stored on a medium and distributed, or may be stored in a server device and downloaded to a computer.

[0181] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0182] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0183] Furthermore, the above-described embodiments can be combined as appropriate in areas where the processing contents are not contradictory.

[0184] <<Summary>> Although the preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, the technical scope of the present disclosure is not limited to such examples. It is clear that a person skilled in the art of the present disclosure can conceive of various modified or altered examples within the scope of the technical idea described in the claims, and it is understood that these also naturally fall within the technical scope of the present disclosure.

[0185] Furthermore, the effects described herein are merely descriptive or exemplary and are not limiting. In other words, the technology according to the present disclosure may achieve other effects that will be apparent to those skilled in the art from the description of this specification, in addition to or in place of the above-described effects.

[0186] The following configurations also fall within the technical scope of the present disclosure. (1) A communication device, a transceiver and a processor; The processor: configured to transmit, via the transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information; Communication equipment. (2) The second information is information specifying a CORESET configuration for a Type0-PDCCH CSS set, The third information is information specifying a Type0-PDCCH CSS set configuration. A communication device according to (1). (3) the second information is information indicating a subcarrier spacing of a PDCCH of a Type0-PDCCH CSS set; The third information is information indicating a subcarrier offset between the SS / PBCH block and a CORESET for a Type0-PDCCH CSS set. A communication device according to (1). (4) the second information is information notifying whether the operation is in a licensed band or an unlicensed band, The third information is information notifying the number of QCLs in the SS / PBCH block. A communication device according to (1). (5) A communication device, a transceiver and a processor; The processor: configured to receive, via the transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in a MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information; Communication equipment. (6) The second information is information specifying a CORESET configuration for a Type0-PDCCH CSS set, The third information is information specifying a Type0-PDCCH CSS set configuration. (5) A communication device according to (5). (7) the second information is information indicating a subcarrier spacing of a PDCCH of a Type0-PDCCH CSS set; The third information is information indicating a subcarrier offset between the SS / PBCH block and a CORESET for a Type0-PDCCH CSS set. (5) A communication device according to (5). (8) the second information is information notifying whether the operation is in a licensed band or an unlicensed band, The third information is information notifying the number of QCLs in the SS / PBCH block. (5) A communication device according to (5). (9) 1. A method of a communication device, comprising: transmitting, via the transceiver, a Master Information Block (MIB) including the first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information; Communication method. (10) 1. A method of a communication device, comprising: receiving, via a transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in a MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information; Communication method. [Explanation of symbols]

[0187] 20 Base station equipment 21 Signal processing section 24, 45 Control section 40 Terminal Equipment 41 Signal processing section

Claims

1. A communication device, a transceiver and a processor; The processor: configured to transmit, via the transceiver, a Master Information Block (MIB) containing first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information specifying a CORESET configuration for a Type0-PDCCH CSS set, The third information is information specifying a Type0-PDCCH CSS set configuration. Communication equipment.

2. A communication device, a transceiver and a processor; The processor: configured to transmit, via the transceiver, a Master Information Block (MIB) containing first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information notifying a subcarrier spacing of a PDCCH of a Type 0-PDCCH CSS set, The third information is information indicating a subcarrier offset between the SS / PBCH block and a CORESET for a Type0-PDCCH CSS set. Communication equipment.

3. A communication device, a transceiver and a processor; The processor: configured to transmit, via the transceiver, a Master Information Block (MIB) containing first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, the second information is information notifying whether the operation is in a licensed band or an unlicensed band, The third information is information notifying the number of QCLs of the SS / PBCH block. Communication equipment.

4. A communication device, a transceiver and a processor; The processor: configured to receive, via the transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information specifying a CORESET configuration for a Type0-PDCCH CSS set, The third information is information specifying a Type0-PDCCH CSS set configuration. Communication equipment.

5. A communication device, a transceiver and a processor; The processor: configured to receive, via the transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information notifying a subcarrier spacing of a PDCCH of a Type 0-PDCCH CSS set, The third information is information indicating a subcarrier offset between the SS / PBCH block and a CORESET for a Type0-PDCCH CSS set. Communication equipment.

6. A communication device, a transceiver and a processor; The processor: configured to receive, via the transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, the second information is information notifying whether the operation is in a licensed band or an unlicensed band, The third information is information notifying the number of QCLs of the SS / PBCH block. Communication equipment.

7. 1. A method of a communication device, comprising: transmitting, via the transceiver, a Master Information Block (MIB) including the first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information specifying a CORESET configuration for a Type0-PDCCH CSS set, The third information is information specifying a Type0-PDCCH CSS set configuration. Communication method.

8. A method for a communication device, comprising: transmitting, via the transceiver, a Master Information Block (MIB) including the first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information notifying a subcarrier spacing of a PDCCH of a Type 0-PDCCH CSS set, The third information is information indicating a subcarrier offset between the SS / PBCH block and a CORESET for a Type0-PDCCH CSS set. Communication method.

9. A method for a communication device, comprising: transmitting, via the transceiver, a Master Information Block (MIB) including the first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be transmitted in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, the second information is information notifying whether the operation is in a licensed band or an unlicensed band, The third information is information notifying the number of QCLs of the SS / PBCH block. Communication method.

10. 1. A method of a communication device, comprising: receiving, via a transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information specifying a CORESET configuration for a Type0-PDCCH CSS set, The third information is information specifying a Type0-PDCCH CSS set configuration. Communication method.

11. A method for a communication device, comprising: receiving, via a transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, The second information is information notifying a subcarrier spacing of a PDCCH of a Type 0-PDCCH CSS set, The third information is information indicating a subcarrier offset between the SS / PBCH block and a CORESET for a Type0-PDCCH CSS set. Communication method.

12. A method for a communication device, comprising: receiving, via a transceiver, a Master Information Block (MIB) including first information in a second frequency range different from the first frequency range; the first information corresponds to an index specifying a combination of second information and third information explicitly included in an MIB to be received in the case of the first frequency range; the number of bits of the first information is smaller than the sum of the number of bits of the second information and the third information, the second information is information notifying whether the operation is in a licensed band or an unlicensed band, The third information is information notifying the number of QCLs of the SS / PBCH block. Communication method.

Images