For a terminal before an RRC connection, all of the CORESET for monitoring of common search space type 1, the CORESET for monitoring of common search space type 2, and the CORESET for monitoring of common search space type 3 may correspond to different CORESETs. That is, the CORESET configured via a MIB and the CORESET configured via RMSI may imply that the CORESET configured via a MIB and the CORESET configured via RMSI are configured in different time and frequency resources or other pieces of configuration information (e.g., all or some pieces of information among the pieces of configuration information described in Table 2) are different.

In this example, common search space type 1, common search space type 2, and common search space type 3 may all be defined to be the same common search space. The definition of common search space type 1, common search space type 2, and common search space type 3 as the same common search space implies that a search space is defined at a predefined fixed position in a CORESET. That is, the BS may transmit each of a DCI format scrambled with an SI-RNTI, a DCI format scrambled with a RA-RNTI, and a DCI format scrambled with a P-RNTI to the terminal on a common search space defined by the same rule in a configured CORESET. The terminal may monitor and receive a DCI format scrambled with an SI-RNTI, a DCI format scrambled with a RA-RNTI, and a DCI format scrambled with a P-RNTI in common search spaces defined for CORESETs configured according to the respective common search space types. If a CORESET configured via a MIB and a CORESET configured via RMSI are identical, search spaces are identical by default.