Terminal, radio communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives at least one of a first system information block (SIB) common to a plurality of terminal categories and a second SIB unique to the category of the terminal; and a control unit that controls an initial access operation on the basis of at least one of the first SIB and the second SIB. According to the one aspect of the present disclosure, advanced services that surpass 5G NR can be achieved.

Description

Terminal, Wireless Communication Method, and Base Station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of achieving further high data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was specified.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), 5G-A(advanced), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010

[0005] In future wireless communication systems (for example, Rel. 21 and later, 6G systems), in order to solve social issues in the 2030s and later, the realization of advanced services beyond the 5G NR system is expected.

[0006] To realize such services, it is being considered to define synchronization signals / system information, etc., to be common or different depending on the category of device (for example, terminals (user terminal, User Equipment (UE))).

[0007] However, detailed consideration of such regulations has not been sufficient. If this consideration is insufficient, proper cell connection / initial access operations may not be achieved, and there is a risk that advanced services beyond 5G NR will not be realized.

[0008] Therefore, one of the objectives of this disclosure is to provide a terminal, a wireless communication method, and a base station that can realize advanced services beyond 5G NR.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives at least one of a first system information block (SIB) common to a category of multiple terminals and a second SIB specific to the category of its own terminal, and a control unit that controls an initial access operation based on at least one of the first SIB and the second SIB.

[0010] According to one aspect of this disclosure, it is possible to realize advanced services that go beyond 5G NR.

[0011] Figure 1 is a diagram showing an example of carrier design in a future wireless communication system. Figure 2 is a diagram showing an example of MIB according to Embodiment 1-1A. Figure 3 is a diagram showing an example of MIB according to Embodiment 1-1B. Figure 4 is a diagram showing an example of MIB according to Embodiment 1-1C. Figure 5 is a diagram showing an example of SIB1 according to Embodiment 2-1A. Figure 6 is a diagram showing an example of SIB1 according to Embodiment 2-1B. Figure 7 is a diagram showing an example of SIB1 according to Embodiment 2-1C. Figure 8 is a diagram showing an example of SIB1 according to option 3-1-1. Figure 9 is a diagram showing an example of SIB1 according to option 3-1-2. Figure 10 is a diagram showing an example of SIB1 according to Embodiment 3-2. Figure 11 is a diagram showing another example of SIB1 according to Embodiment 3-2. Figure 12 is a diagram showing an example of the schematic configuration of a wireless communication system according to one embodiment. Figure 13 is a diagram showing an example of the configuration of a base station according to one embodiment. Figure 14 is a diagram showing an example of the configuration of a user terminal according to one embodiment. Figure 15 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 16 shows an example of a vehicle according to one embodiment.

[0012] (Examples of carrier design in future wireless communication systems) In future wireless communication systems (e.g., Rel. 21 and beyond, 6G systems), it is expected that advanced services exceeding those of 5G NR systems will be realized in order to solve social issues in the 2030s and beyond, as exemplified below: - Scalable network (NW). - Easy-to-operate NW. - Sustainable / resilient NW. - Improved performance (e.g., throughput / capacity) at lower bit costs. - Significant reduction in the cost / complexity / power consumption of cellular networks. - Increased revenue / creation of new value through cellular networks.

[0013] For scalable networks, it is desirable that the basic design of a 6G system be applicable not only to use cases within the 6G system but also to potential new use cases that may arise later. This is because it will be beneficial and practical for features that are expected to be released in the future.

[0014] For easily operable networks, it is desirable to avoid specifying multiple options for the same purpose.

[0015] For sustainable and fast-recovering networks, significant cost and energy consumption reductions are desirable for both the network side and the terminals (user terminals, user equipment (UE)). Furthermore, improved fault tolerance and rapid recovery capabilities against all kinds of events (e.g., operational errors, high traffic, disasters, etc.) are also desirable.

[0016] The following describes an example of carrier design in a future wireless communication system, with reference to Figure 1.

[0017] The UE may monitor multiple frequencies (for example, which may be called monitoring frequencies / synchronous rasters) to detect a first carrier (for example, which may be called a perch carrier).

[0018] If a first carrier is detected, the UE may perform a synchronous operation (which may be called a first synchronous operation) and receive / retrieve information (e.g., system information).

[0019] The UE may perform initial access / random access on a second carrier (which may be called an anchor carrier, for example) based on the received / acquired information (e.g., system information) and establish an RRC connection with the NW. At least a portion of the initial access / random access may be performed on the first carrier.

[0020] The UE may transmit / receive data on a third carrier (which may be called a data carrier, for example) that is set up by signals transmitted / received on a second carrier.

[0021] Please note that the names such as perch carrier, anchor carrier, and data carrier used in this disclosure are merely examples and are not limited to these names.

[0022] Figure 1 shows the low-frequency band (coverage band) and the high-frequency band (capacity band). In the example shown in Figure 1, after the UE is powered on, the UE performs a cell search using the monitoring frequency. Next, the monitoring frequency resource detected by the UE becomes the perch carrier (first carrier), and the perch carrier receives information about the anchor carrier (second carrier). The UE performs initial access (IA) using at least one of the perch carrier and the anchor carrier. From the cell search to the completion of IA, the UE is in idle mode.

[0023] After initial access is complete, the UE enters RRC connection (CONNECTED) mode. The UE receives information about the data carrier (third carrier) on the anchor carrier. The UE performs additional synchronization on the anchor carrier. The UE transmits / receives data on the data carrier for a specific use case (e.g., eMBB / other purposes).

[0024] In the example shown in Figure 1, if the UE returns to idle mode / inactive mode, RRC reconnection may be performed using LP-WUS / WUR and at least one of mobility operations.

[0025] In the example shown in Figure 1, carriers other than the perch carrier may be on-demand carriers (i.e., carriers that are not always on) from the viewpoint of reducing network energy. For example, at least one of the second carrier (anchor carrier) and the third carrier (data carrier) may support on-demand transmission / setting, where transmission is controlled based on a wake-up signal / trigger signal, while the first carrier (perch carrier) may not support on-demand transmission / setting.

[0026] For example, the UE may transmit a wake-up / trigger signal based on information about a second carrier received on the first carrier, and receive a signal transmitted on the second carrier in response to the wake-up / trigger signal. In another example, the UE may transmit a wake-up / trigger signal based on information about a third carrier received on the second carrier, and receive a signal transmitted on the third carrier in response to the wake-up / trigger signal.

[0027] In the example shown in Figure 1, the UE may obtain a first synchronization (or information about the first synchronization) on the first carrier and a second synchronization (or information about the second synchronization) on the second carrier. In this case, the UE may perform transmission and reception on the first carrier (or transmission and reception on the first carrier and transmission and reception on a portion of the second carrier) based on the first synchronization, and perform transmission and reception on the second and third carriers (or transmission and reception on a portion of the second carrier and transmission and reception on the third carrier) based on the second synchronization.

[0028] <Monitoring Frequency / Synchronization Raster> The monitoring frequency / synchronization raster may indicate the frequency position of the synchronization signal block (SSB) that the UE can use to acquire the system.

[0029] In existing NRs (e.g., up to Rel. 18), the frequency position (center frequency) of the synchronization signal block is expressed as N * 1200 kHz + M * 50 kHz (where N is an integer from 1 to 2499, and M is 1, 3, or 5) for frequencies from 0 to 3000 MHz (Frequency Range (FR) 1), and as 3000 MHz + N * 1.44 MHz (where N is an integer from 0 to 14756) for frequencies above 3000 MHz (FR 2).

[0030] Furthermore, during initial access to an existing NR, the order in which the UE searches for synchronized rasters depends on the UE implementation. For efficient searching, a Global Synchronization Channel Number (GSCN) is defined, and the GSCN range is notified to the UE. This GSCN is represented as 3N + (M - 3) / 2 in FR1 and as 7499 + N in FR2.

[0031] In this disclosure, the number of monitoring frequency / synchronous rasters may be more limited (e.g., smaller) than the number of monitoring frequency / synchronous rasters in existing NRs. In other words, the frequency spacing of the monitoring frequency / synchronous rasters may be wider than in existing NRs.

[0032] For example, the location of a synchronization raster may be defined based on its relationship to information relating to a frequency band (e.g., a frequency band index). The UE may monitor or search for the location of a synchronization raster associated with a frequency band index. Alternatively, the UE may assume that the location of a synchronization raster is associated with a frequency band index, and may monitor or search for synchronization rasters based on that assumption.

[0033] For example, the bandwidth in which a GSCN or synchronous raster is defined may be limited. A UE may monitor or search for the bandwidth in which a GSCN or synchronous raster is defined among the bandwidths supported by the UE. Alternatively, a UE may assume that a GSCN or synchronous raster is defined in only a specific bandwidth among the bandwidths supported by the UE, and may monitor or search for a GSCN or synchronous raster based on that assumption.

[0034] For example, in a given bandwidth, a GSCN or synchronous raster may be defined only at specific frequency positions. For example, in a given bandwidth, a GSCN or synchronous raster may be defined within X Hz (where X is any number) from the lower limit of that bandwidth. A UE may monitor or search for a GSCN or synchronous raster at (only) the specific frequency positions in which it is defined for each of the bandwidths it supports. Alternatively, a UE may assume that a GSCN or synchronous raster is defined only at (only) specific frequency positions in a given bandwidth, and may monitor or search for a GSCN or synchronous raster based on that assumption.

[0035] This allows for an extension of the time required for cell search per frequency (i.e., the period of the synchronization signal block per frequency), thereby reducing network energy consumption and shortening the time required for initial access.

[0036] The monitoring frequency resources detected by the UE may correspond to potential perch carriers (first carriers).

[0037] <Perch Carrier> The first carrier may be a carrier common to multiple UEs.

[0038] The first carrier could be a common carrier regardless of the use case / service / device type, for example.

[0039] In the first carrier, common signals (e.g., synchronization signal blocks / master information blocks / system information blocks) may be transmitted. Furthermore, the transmission and reception of data (e.g., application layer information) is not assumed in the first carrier. Also, the transmission and reception of information relating to a specific UE or a specific group of UEs (e.g., information other than that relating to the second carrier) is not assumed in the first carrier.

[0040] The first carrier (and the signal transmitted in it) may always be kept in the ON state.

[0041] Signals transmitted on the first carrier (e.g., synchronization signal blocks / master information blocks / system information blocks) may include information about an anchor carrier (second carrier) that is available in the system or used by the UE.

[0042] The first carrier may have a frequency lower than a specific value (for example, 800 MHz).

[0043] The first carrier may correspond to a single (base station) beam.

[0044] The UE may perform first synchronization in the first carrier. The first synchronization may mean the first step / level (e.g., coarse) synchronization among a plurality (e.g., two) of steps / levels of synchronization.

[0045] The first carrier may be included in, for example, a coverage band.

[0046] By defining / using the first carrier in this way, it is possible to cover all future use cases and contribute to the achievement of an extensible NW.

[0047] <Anchor Carrier> The second carrier may be a carrier / frequency used for NW connection / control.

[0048] The second carrier may be an individual carrier for each UE / group of multiple UEs (UE group) / use case / service. The UE may determine the second carrier corresponding to its own terminal based on the information obtained in the first carrier.

[0049] In the second carrier, at least one of the following transmissions / receptions / operations may be performed. ・Transmission / reception of a system information block for a specific use case (e.g., enhanced Mobile Broad Band (eMBB)). ・Connection establishment. ・Transmission / reception of a wake-up signal (WUS). ・Wake-up receiver (WUR) operation. ・Second synchronization. ・Information regarding the third carrier.

[0050] The wake-up signal (WUS) / wake-up receiver may be read as a low-power wake-up signal (LP-WUS) / low-power wake-up receiver (LP-WUR).

[0051] By performing operations related to LP-WUS / WUR using the second carrier, NW energy reduction / UE power reduction can be achieved.

[0052] The second carrier (and the signals transmitted on it) does not have to be always on (it may be in a dormant state). For example, the transmission of signals on the second carrier (DL transmission / UL transmission) may be supported to be performed on demand in response to a wake-up signal / trigger signal.

[0053] The second synchronization may refer to the second step / level (e.g., a more precise) synchronization among multiple (e.g., two) step / level synchronizations. For example, a UE may achieve the first synchronization on the first carrier and the second synchronization on the second carrier.

[0054] The second carrier may be included in the first carrier in certain cases (for example, in the case of a [narrowband] IoT device). Alternatively, the second carrier may be configured as a carrier that overlaps the same frequency band as the first carrier.

[0055] The second carrier may, for example, be included in a coverage band.

[0056] At least one operation performed on the second carrier may also be performed on the first / third carrier. Furthermore, at least one operation performed on the first / third carrier may also be performed on the second carrier.

[0057] <Data Carrier> The third carrier may be a carrier used for transmitting / receiving data.

[0058] The third carrier could be an individual carrier for each UE, for multiple UEs (UE groups), for each use case, or for each service.

[0059] The third carrier (and the signals transmitted on it) does not have to be always on (it may be in a dormant state). For example, the transmission of signals on the third carrier (DL transmission / UL transmission) may be supported to be performed on demand in response to a wake-up signal / trigger signal.

[0060] The third carrier may be included in both the coverage band and the capacity band, for example. The third carrier within the capacity band may be used as a surplus carrier.

[0061] The third career may include the first career.

[0062] UE / NW may use the first carrier as a third carrier only in specific cases. Such specific cases may be, for example, at least one of (re-)initial access, fallback cases, and mobility on the second carrier.

[0063] UE may use / monitor the first carrier as a third carrier. Also, U may use / monitor the first carrier as a third carrier in the case of mobility on the first carrier.

[0064] The first, second, and third carriers corresponding to terrestrial networks (TN) and the first, second, and third carriers corresponding to non-terrestrial networks (NTN) may be defined separately or in common.

[0065] Furthermore, certain devices (for example, devices that do not perform cell search / RRC connectivity (e.g., Ambient IoT (A-IoT))) do not need to use a second carrier.

[0066] (Analysis) The Master Information Blocks (MIBs) defined in existing NRs (e.g., up to Rel. 18) are common to RedCap (Reduced Capability) UEs, eRedCap (enhanced Reduced Capability) UEs, and regular UEs (non-RedCap / eRedCap UEs).

[0067] In this disclosure, RedCap / eRedCapUE may be a UE having reduced capacity than a typical UE.

[0068] For example, the RedCap / eRedCapUE may have a smaller maximum supported bandwidth compared to a standard UE. For example, in FR1, the RedCap / eRedCapUE may have a maximum bandwidth of 20 MHz during initial access and thereafter. For example, in FR2, the RedCap / eRedCapUE may have a maximum bandwidth of 100 MHz during initial access and thereafter.

[0069] For example, the RedCap / eRedCapUE may support fewer receive branches compared to a standard UE. For example, the RedCap / eRedCapUE may support one or two receive branches. Also, the RedCap / eRedCapUE may support a smaller maximum number of MIMO layers. For example, the RedCap / eRedCapUE may support one or two MIMO layers. Furthermore, the RedCap / eRedCapUE may support a smaller modulation order. For example, support for 256QAM in FR1 may be optional for the RedCap / eRedCapUE.

[0070] In existing systems (e.g., NR), the Master Information Block (MIB) is common regardless of the UE category (i.e., for regular UE, RedCapUE, and eRedCapUE). The MIB may include information indicating the system frame number (systemFrameNumber), information indicating the subcarrier spacing (SCS) for SIB1 / Message 2 / Message 4 / Message B / Paging / System Information (subCarrierSpacingCommon), information indicating the frequency offset between the SSB and the overall resource block grid (ssb-SubcarrierOffset), information indicating the DMRS position (dmrs-TypeA-Position), information indicating the PDCCH CORESET / Search Space for SIB1 (pdcch-ConfigSIB1), information indicating whether a cell is barred (information on barred cells, cellBarred), and information indicating whether selection / reselection of cells within the same frequency is permitted when the highest-ranked cell is barred (intraFreqReselection).

[0071] On the other hand, in existing systems, several parameters within the System Information Block (SIB, e.g., SIB1) (e.g., the parameter for prohibited cells for RedCapUE (cellBarredRedcap), the parameter for intra-frequency cell selection / re-selection for RedCapUE (intraFreqSelectionRedCap), and the parameter for initial BWP for RedCapUE (initialBWP-Redcap)) are usually defined separately from the UE. In other words, several other parameters within the SIB / SIB1 are common regardless of the UE category (i.e., for regular UE, RedCapUE, and eRedCapUE).

[0072] In future wireless communication systems (e.g., Rel. 21 and later / 6G systems), it is being considered that system information / SIB will be transmitted on at least one of the first / second / third carriers mentioned above.

[0073] In this case, it is expected that system information / SIB (information within it) will be shared or separate depending on the category of the device (e.g., UE), but the details of this have not been sufficiently considered.

[0074] If this consideration is insufficient, proper cell connection / initial access operations may not be achieved, potentially preventing the implementation of advanced services beyond 5G NR.

[0075] Therefore, the inventors conceived of a provision to solve this problem.

[0076] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0077] (Various substitutions) In this disclosure, words enclosed in parentheses () may indicate an explanation of the preceding word (e.g., an explanation of spelling), a paraphrase, a specific example, or supplementary explanation. Also, in this disclosure, words enclosed in square brackets [] may be interpreted as part of the overall meaning of the text, or they may be interpreted as being excluded (ignored). Note that parentheses () and square brackets [] may be used for purposes / meanings other than those described above.

[0078] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0079] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0080] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0081] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0082] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0083] In this disclosure, physical layer signaling may be, for example, layer (L)1 / L2 signaling, downlink control information (DCI), uplink control information (UCI), etc.

[0084] In this disclosure, terms such as drop, suspend, cancel, puncture, rate match, postpone, and not send may be interpreted interchangeably.

[0085] In this disclosure, signals, channels, information, information elements, parameters, data, messages, etc., may be interpreted interchangeably.

[0086] In this disclosure, carrier, frequency carrier, component carrier, frequency, band, frequency band, raster, synchronous raster, cell, channel, etc. may be interpreted interchangeably.

[0087] In this disclosure, "perch" and "1" may be interpreted as interchangeable. In this disclosure, "anchor" and "2" may be interpreted as interchangeable. In this disclosure, "data" and "3" may be interpreted as interchangeable.

[0088] In this disclosure, search, monitor, receive, etc. may be interpreted interchangeably.

[0089] In this disclosure, master information, system information, master information block (MIB), system information block (SIB), SIB1, SIBx (where x is any number), synchronization signal, synchronization signal block (SSB), broadcast information, broadcast channel, SS / PBCH block, information for cell connection / initial access, etc., may be interpreted as interchangeable.

[0090] In this disclosure, different device (UE) categories (which may also be called device categories / UE categories) may be defined from the perspective of UE capability.

[0091] The device category may be determined based on at least one of the following: bandwidth, peak data rate, transmit / receive rates, processing power, energy / power saving requirements, functionality, and vertical use cases.

[0092] For example, different device categories may differ in at least one of the following: bandwidth, peak data rate, transmit / receive rates, processing power, energy / power saving requirements, functionality, and vertical use cases.

[0093] The functional / vertical use case may be, for example, at least one of XR (Extended Reality), NCR (Non-Cellular Radio), IAB (Integrated Access and Backhaul), ATG (Air-to-Ground), and NTN (Non-Terrestrial Networks).

[0094] In this disclosure, device category, UE category, device type, UE type, use case, terminal category, terminal category, terminal type, etc., may be interpreted interchangeably.

[0095] In this disclosure, “all device categories” may mean all device categories supported by the corresponding network / base station / operator.

[0096] (Wireless communication method) A UE may receive at least one of a common MIB for multiple (e.g., all) device categories and a separate MIB for each device category (i.e., specific to the UE's category).

[0097] The UE may control the reception and initial access / reconnection operations of the corresponding SIB based on the MIB.

[0098] A UE may receive at least one of two SIBs: one common to multiple (e.g., all) device categories, and another separate SIB for each device category (i.e., one specific to the UE's own category).

[0099] The UE may control the initial access / reconnection operation based on the SIB.

[0100] <First Embodiment> The first embodiment relates to information transmitted using MIB.

[0101] <<Embodiment 1-1>> The MIB may be transmitted on the first carrier.

[0102] <<<Embodiment 1-1A>>> A single MIB transmission may contain information for multiple (e.g., all) device categories.

[0103] The information in question may be referred to as Information X below.

[0104] A single piece of information X may be transmitted within the MIB.

[0105] A single piece of information X may be common to multiple (for example, all) device categories (Option 1A-1).

[0106] A single piece of information X may be applicable (or may be applicable) to [only] one or more specific device categories (Option 1A-2).

[0107] For example, one or more specific device categories may be designed for a particular use case (e.g., for eMBBs).

[0108] For example, if there is information X required for a device category other than a specific one or more device categories, such information X may be set / indicated using another signal (e.g., SIBx).

[0109] Multiple pieces of information X may be transmitted within the MIB. Each of these pieces of information X may be transmitted to each of the multiple device categories (option 1A-3).

[0110] For example, in the MIB of the first carrier, information X for multiple (e.g., all) device categories may be transmitted.

[0111] For example, in the MIB of the first carrier, information X for one or more specific device categories may be transmitted / instructed. In this case, information X required for device categories other than the one or more specific device categories may be set / instructed using another signal (e.g., SIBx).

[0112] Information X may include at least one piece of information (the information described above) within the MIB in an existing NR (for example, as defined up to Rel. 18).

[0113] Different pieces of information X may be notified / configured in separate / common ways.

[0114] For example, at least one piece of information (the information mentioned above) within the MIB in an existing NR (e.g., as defined up to Rel. 18) may be common to multiple (e.g., all) device categories.

[0115] For example, of the information (the information described above) within the MIB in an existing NR (e.g., as defined up to Rel. 18), certain information (e.g., information about prohibited cells) may be for a specific device category (e.g., for eMBBs only).

[0116] For example, of the information (the information described above) within the MIB in an existing NR (for example, as defined up to Rel. 18), specific information (for example, information regarding prohibited cells) may be indicated separately for each device category (which may be one or more device categories).

[0117] Figure 2 shows an example of an MIB according to Embodiment 1-1A. In the example shown in Figure 2, information X for all device categories is included in a single MIB transmission. In the example shown in Figure 2, the MIB contains information for each device category (for example, information Y and information Z for device category a, and information Z for device category a).

[0118] The information Y / Z may be at least one piece of information (the information described above) within the MIB in an existing NR, or it may be new information.

[0119] <<<Embodiment 1-1B>>> Information for each device category (which may be one or more device categories) may be included in separate MIB transmissions.

[0120] The information contained within each MIB may be specific to each device category. In other words, MIBs and the information contained within them may be defined for each device category.

[0121] Figure 3 shows an example of an MIB according to Embodiment 1-1B. In the example shown in Figure 3, information for each device category is transmitted in separate MIBs. In the example shown in Figure 3, MIB-x (where x is a, b, ..., X) contains information for the corresponding device category (device category x).

[0122] This information may be at least one piece of information (the information described above) from the MIB in an existing NR, or it may be new information.

[0123] Furthermore, while the separate MIBs shown in Figure 3 are shown to not overlap in the time domain, this is merely an example. Therefore, the separate MIBs that are transmitted may overlap in at least part (or all) of the time domain. In this case, information regarding the frequency domain to which the MIB is transmitted may be pre-configured for the UE.

[0124] <<<Embodiment 1-1C>>> A single MIB transmission may contain information for multiple (e.g., all) device categories.

[0125] That single MIB may also be called a common MIB.

[0126] Each of the multiple MIBs [other than the common MIB] may contain information specific to each device category.

[0127] These multiple MIBs may also be called unique MIBs.

[0128] The information included in the common MIB may be the information described in Embodiment 1-1A above.

[0129] A single MIB transmission may contain information for multiple device categories (e.g., device category groups).

[0130] A common MIB may contain information for a specific device category (e.g., a typical UE). A unique MIB may not contain information for that specific device category.

[0131] Figure 4 shows an example of an MIB according to Embodiment 1-1C. In the example shown in Figure 4, a common MIB for all device categories and a specific MIB containing information for each device category are shown. In the example shown in Figure 4, each specific MIB (specific MIB-x (where x is a, b, ..., X)) contains information for the corresponding device category (device category x).

[0132] The information included in the common MIB / specific MIB may be at least one piece of information from an existing NR MIB (the information described above), or it may be new information.

[0133] Furthermore, while the separate MIBs shown in Figure 4 are shown to not overlap in the time domain, this is merely an example. Therefore, the separate MIBs that are transmitted may overlap in at least part (or all) of the time domain. In this case, information regarding the frequency domain to which the MIB is transmitted may be pre-configured for the UE.

[0134] According to Embodiment 1-1, even when the MIB is transmitted on the first carrier, information corresponding to the device category can be transmitted appropriately.

[0135] <<Embodiment 1-2>> The MIB may be transmitted on a second / third carrier.

[0136] A single second / third carrier may be dedicated to one / specific device category.

[0137] The MIB being transmitted may be intended for that one / specific device category.

[0138] In other words, the device category to which the MIB is intended may be determined based on the second / third carrier to which the MIB is transmitted.

[0139] A single second / third carrier may serve multiple device categories.

[0140] The above embodiment 1-1 may be applied to the MIB that is transmitted.

[0141] According to Embodiment 1-2, even when the MIB is transmitted on a second / third carrier, information corresponding to the device category can be transmitted appropriately.

[0142] <<Embodiment 1-3>> A portion of the MIB may be transmitted on the first carrier. The remaining portion of the MIB may be transmitted on the second / third carrier.

[0143] In this case, the above embodiments 1-1 / 1-2 may be applied to each carrier.

[0144] For example, information common to multiple (e.g., all) device categories may be transmitted in the MIB on a specific carrier (e.g., the first carrier).

[0145] For example, specific information for one or more device categories may be transmitted in the MIB on a specific carrier (e.g., a second or third carrier).

[0146] According to Embodiments 1-3, even when the MIB is transmitted on the first / second / third carrier, information corresponding to the device category can be transmitted appropriately.

[0147] In this disclosure, separate MIBs may be transmitted using different resources within the same (single) broadcast channel (e.g., SS / PBCH block), or they may be transmitted using different resources within separate broadcast channels (e.g., SS / PBCH blocks).

[0148] According to the first embodiment described above, information corresponding to the device category can be appropriately transmitted using MIB.

[0149] <Second Embodiment> The second embodiment relates to information transmitted using SIB.

[0150] The second embodiment may be applied by replacing "MIB" in the first embodiment with "SIB (for example, SIB1)".

[0151] In this disclosure, SIB1 will be used as the main example of an SIB, but this is merely an example, and SIB1 may be interpreted as SIB and SIBx (where X is any number).

[0152] <<Embodiment 2-1>> SIB1 may be transmitted on the first carrier.

[0153] <<<Embodiment 2-1A>>> A single SIB1 transmission may contain information for multiple (e.g., all) device categories.

[0154] The information in question may be referred to as Information X below.

[0155] A single piece of information X may be transmitted within SIB1.

[0156] A single piece of information X may be common to multiple (for example, all) device categories (Option 2A-1).

[0157] A single piece of information X may be applicable (or may be applicable) to [only] a specific one or more device categories (Option 2A-2).

[0158] For example, one or more specific device categories may be designed for a particular use case (e.g., for eMBBs).

[0159] For example, if there is information X required for a device category other than a specific one or more device categories, such information X may be set / indicated using another signal (e.g., a signal on a second / third carrier).

[0160] Multiple pieces of information X may be transmitted within SIB1. Each of these pieces of information X may be transmitted to each of the multiple device categories (option 2A-3).

[0161] For example, in the SIB1 of the first carrier, information X for multiple (e.g., all) device categories may be transmitted.

[0162] For example, in the SIB1 on the first carrier, information X for one or more specific device categories may be transmitted / transmitted / instructed. In this case, information X required for device categories other than the one or more specific device categories may be set / instructed using another signal (for example, a signal on the second / third carrier).

[0163] Information X may include at least one piece of information within SIB1 in an existing NR (for example, as defined up to Rel. 18).

[0164] Different pieces of information X may be notified / configured in separate / common ways.

[0165] For example, certain information (e.g., at least one of the following: transmit / receive settings on the first carrier, settings for monitoring synchronization signals / MIBs, time-division duplex (TDD) settings, synchronization / timing advance settings) may be common to multiple (e.g., all) device categories.

[0166] For example, specific information (e.g., settings for transmission / reception on a second / third carrier, settings for DL / UL channels (e.g., PDCCH / PDSCH / PUCCH / PUSCH / PRACH), at least one of these) may be set / instructed for each device category (which may be one or more).

[0167] Figure 5 shows an example of an SIB1 according to Embodiment 2-1A. In the example shown in Figure 5, information X for all device categories is included in a single SIB1 transmission. In the example shown in Figure 5, the SIB1 contains information for each device category (for example, information Y and information Z for device category a, and information Z for device category a).

[0168] <<<Embodiment 2-1B>>> Information for each device category (which may be one or more devices) may be included in separate SIB1 transmissions.

[0169] The information contained within each SIB1 may be specific to each device category. In other words, SIB1 and the information contained within SIB1 may be defined for each device category.

[0170] Figure 6 shows an example of an SIB1 according to Embodiment 2-1B. In the example shown in Figure 6, information for each device category is transmitted in separate SIB1s. In the example shown in Figure 6, SIB1-x (where x is a, b, ..., X) each contains information for the corresponding device category (device category x).

[0171] Furthermore, while the separate SIB1s shown in Figure 6 are shown not to overlap in the time domain, this is merely an example. Therefore, the separate SIB1s that are transmitted may overlap in at least part (or all) of the time domain. In this case, information regarding the frequency domain to which the SIB1 is transmitted may be pre-configured for the UE.

[0172] <<<Embodiment 2-1C>>> A single SIB1 transmission may contain information for multiple (e.g., all) device categories.

[0173] This single SIB1 may also be called a common SIB1.

[0174] Each of the multiple SIB1s [other than the common SIB1] may contain information for each device category.

[0175] These multiple SIB1s may also be called unique SIB1s.

[0176] The information included in the common SIB1 may be the information described in Embodiment 2-1A above.

[0177] A single SIB1 transmission may contain information for multiple device categories (e.g., device category groups).

[0178] The common SIB1 may contain information for a specific device category (e.g., a typical UE). The individual SIB1 does not necessarily contain information for that specific device category.

[0179] Figure 7 shows an example of SIB1 according to Embodiment 2-1C. In the example shown in Figure 7, a common SIB1 for all device categories and a specific SIB1 containing information for each device category are shown. In the example shown in Figure 7, each specific SIB1 (specific SIB1-x (where x is a, b, ..., X)) contains information for the corresponding device category (device category x).

[0180] Furthermore, while the separate SIB1s shown in Figure 7 are shown not to overlap in the time domain, this is merely an example. Therefore, the separate SIB1s that are transmitted may overlap in at least part (or all) of the time domain. In this case, information regarding the frequency domain to which the SIB1 is transmitted may be pre-configured for the UE.

[0181] According to Embodiment 2-1, even when SIB1 is transmitted on the first carrier, information corresponding to the device category can be transmitted appropriately.

[0182] <<Embodiment 2-2>> SIB1 may be transmitted on a second / third carrier.

[0183] A single second / third carrier may be dedicated to one / specific device category.

[0184] The transmitted SIB1 may be intended for that one / specific device category.

[0185] In other words, the device category to which the SIB1 transmitted on a second / third carrier is intended may be determined based on the second / third carrier on which the SIB1 is transmitted.

[0186] A single second / third carrier may serve multiple device categories.

[0187] The above embodiment 2-1 may be applied to the SIB1 that is transmitted.

[0188] According to Embodiment 2-2, even when SIB1 is transmitted on a second / third carrier, information corresponding to the device category can be transmitted appropriately.

[0189] <<Embodiment 2-3>> A portion of SIB1 may be transmitted on the first carrier. The remaining portion of SIB1 may be transmitted on the second / third carrier.

[0190] In this case, the above embodiments 2-1 / 2-2 may be applied to each carrier.

[0191] For example, information common to multiple (e.g., all) device categories may be transmitted / transmitted in SIB1 on a specific carrier (e.g., a first carrier).

[0192] For example, specific information for one or more device categories may be transmitted in SIB1 on a specific carrier (e.g., a second or third carrier).

[0193] According to Embodiment 2-3, even when SIB1 is transmitted on the first / second / third carrier, information corresponding to the device category can be transmitted appropriately.

[0194] <<Embodiment 2-4>> Embodiment 2-4 describes a combination of the first and second embodiments.

[0195] Hereinafter, Embodiment 1-1A and Embodiment 1-1A applied in Embodiments 1-2 / 1-3 will be referred to as Embodiment 1A. Also, Embodiment 2-1A and Embodiment 2-1A applied in Embodiments 2-2 / 2-3 will be referred to as Embodiment 2A.

[0196] Furthermore, Embodiment 1-1B, as applied in Embodiments 1-2 / 1-3, is referred to as Embodiment 1B. Also, Embodiment 2-1B, as applied in Embodiments 2-2 / 2-3, is referred to as Embodiment 2B.

[0197] Furthermore, Embodiment 1-1C, as applied in Embodiments 1-2 / 1-3, is referred to as Embodiment 1C. Also, Embodiment 2-1C, as applied in Embodiments 2-2 / 2-3, is referred to as Embodiment 2C.

[0198] For example, Embodiment 1A and Embodiment 2A may be applied in combination.

[0199] In this case, one MIB for multiple (e.g., all) device categories and one SIB for multiple (e.g., all) device categories may be sent.

[0200] For example, Embodiment 1A and Embodiment 2B may be applied in combination.

[0201] In this case, one MIB for multiple (e.g., all) device categories and separate SIBs for each different device category may be sent.

[0202] For example, Embodiment 1A and Embodiment 2C may be applied in combination.

[0203] In this case, one MIB for multiple (e.g., all) device categories, a common SIB for multiple (e.g., all) device categories, and individual SIBs for different device categories may be transmitted.

[0204] For example, Embodiment 1B and Embodiment 2B may be applied in combination.

[0205] In this case, separate MIBs for each different device category and separate SIBs for each different device category may be sent.

[0206] For example, Embodiment 1C and Embodiment 2C may be applied in combination.

[0207] In this case, a common MIB for multiple (e.g., all) device categories and a specific MIB for different device categories may be transmitted, as well as a common SIB for multiple (e.g., all) device categories and a specific SIB for different device categories.

[0208] Furthermore, other combinations not exemplified here may also be applied as appropriate.

[0209] According to the second embodiment described above, information corresponding to the device category can be appropriately transmitted using SIB.

[0210] <Third Embodiment> The third embodiment relates to the determination of resources in SIB1, including information for each device category.

[0211] This embodiment may also be applied to cases where SIB1 containing information for each device category is transmitted separately (for example, in embodiments 2-1B / 2-1C described above).

[0212] In this disclosure, the resources of SIB1 may include at least one of the monitoring opportunities for the PDCCH (SIB1-PDCCH) that transmits SIB1, and the time / frequency resources of the SIB1-PDCCH.

[0213] The resources for SIB1 may be specified in advance in the specifications.

[0214] For example, for SIB1 in the first / second / third carriers, at least one of the monitoring opportunities for SIB1-PDCCH and the time / frequency resources of SIB1-PDCCH may be predetermined.

[0215] The resources for SIB1 may be configured / instructed.

[0216] For example, in the case of SIB1 on a first carrier, at least one of the monitoring opportunity for SIB1-PDCCH and at least one of the time / frequency resources for SIB1-PDCCH may be set / instructed using the MIB on the first carrier and information / signaling that has been previously searched / received on another first / second / third carrier.

[0217] For example, in the case of SIB1 on the second / third carrier, signaling on the first / second / third carrier may set / indicate at least one of the monitoring opportunity for SIB1-PDCCH and the time / frequency resources of SIB1-PDCCH.

[0218] In this disclosure, settings for SIB1-PDCCH monitoring [on the first / second / third carriers] may be specified / configured / instructed.

[0219] The settings may include, for example, the setting of a set of resources (e.g., a control resource set (CORESET)). The settings may include settings for at least one of the following: the number of resource blocks, the number of symbols, and the start / center / end positions of the resource blocks.

[0220] The settings may include, for example, the search space settings. The settings may also include settings related to the location of system frames / subframes / slots / symbols related to PDCCH monitoring opportunities.

[0221] <<Embodiment 3-1>> Embodiment 3-1 may be applied, for example, in Embodiment 2-1B described above, or it may be applied independently.

[0222] Embodiment 3-1 may be broadly divided into the following options 3-1-1 and 3-1-2: • Option 3-1-1: SIB1-PDCCH for each device category is monitored in separate monitoring opportunities / time resources / frequency resources. • Option 3-1-2: SIB1-PDCCH for multiple (e.g., all) device categories is monitored in a common monitoring opportunity / time resources / frequency resources. The Radio Network Temporary Identifier (RNTI) / format / payload size for the SIB1-PDCCH differs for each device category.

[0223] Figure 8 shows an example of SIB1 related to option 3-1-1. In the example shown in Figure 8, SIB1-PDCCH for each device category is monitored using separate monitoring opportunities / time resources / frequency resources. In the example shown in Figure 8, SIB1 for device category a and SIB1 for device category b are monitored by the respective category's UE.

[0224] Figure 9 shows an example of SIB1 related to option 3-1-2. In the example shown in Figure 9, SIB1-PDCCH for each device category is monitored using common monitoring opportunities / time resources / frequency resources. In the example shown in Figure 9, SIB1 is monitored by the UE of device category a using RNTI (SI-RNTI-a) for device category a, and SIB1 is monitored by the UE of device category b using RNTI (SI-RNTI-b) for device category b.

[0225] The monitoring opportunities / time resources / frequency resources for SIB1-PDCCH for each device category may be predetermined. These monitoring opportunities / time resources / frequency resources may be applied to SIB1 on the first / second / third carriers.

[0226] In the case of option 3-1-1, separate monitoring opportunities / time resources / frequency resources may be defined for each device category.

[0227] In the case of option 3-1-2, common monitoring opportunities / time resources / frequency resources may be defined for each device category.

[0228] Monitoring opportunities / time resources / frequency resources for SIB1-PDCCH for each device category may be set / instructed. These monitoring opportunities / time resources / frequency resources may be applied to SIB1 on the first / second / third carriers.

[0229] In the case of option 3-1-1, separate monitoring opportunities / time resources / frequency resources may be set / instructed for each device category.

[0230] In the case of option 3-1-2, common monitoring opportunities / time resources / frequency resources may be set / instructed for each device category.

[0231] For example, in the case of SIB1 on a first carrier, the monitoring opportunity / time resource / frequency resource of SIB1-PDCCH may be set / instructed using at least one of the MIB on the first carrier and information / signaling that has been previously searched / received on another first / second / third carrier.

[0232] For example, in the case of SIB1 on the second / third carrier, the monitoring opportunities / time resources / frequency resources for SIB1-PDCCH may be set / instructed by signaling on the first / second / third carrier.

[0233] Different CORESETs may be determined by separate monitoring opportunities / time resources / frequency resources. In other words, different CORESETs may monitor SIB1-PDCCH for separate monitoring opportunities / time resources / frequency resources.

[0234] Different search spaces may be determined by separate monitoring opportunities / time resources / frequency resources. In other words, SIB1-PDCCH of separate monitoring opportunities / time resources / frequency resources may be monitored by separate search spaces.

[0235] A separate search space may be different from (or different from) a system frame, a subframe (in the same or different system frame), a slot (in the same or different frame / system frame / subframe), and a symbol (in the same or different slot).

[0236] The RNTI / format / payload size for SIB1-PDCCH may be predefined.

[0237] In the case of option 3-1-1, the RNTI / format / payload size may be specified for SIB1-PDCCH for a common device category.

[0238] In the case of option 3-1-2, the RNTI / format / payload size may be specified for SIB1-PDCCH for different device categories.

[0239] For example, common monitoring opportunities / time resources / frequency resources / RNTI / format / payload size related to SI1-PDCCH may be defined / configured / instructed for multiple device categories (a group of device categories).

[0240] For example, separate monitoring opportunities / time resources / frequency resources / RNTI / format / payload size for SI1-PDCCH may be defined / configured / instructed for different device categories.

[0241] According to Embodiment 3-1, even when SIBs are transmitted for each device category, the SIB resources can be appropriately identified.

[0242] <<Embodiment 3-2>> Embodiment 3-2 may be applied, for example, in Embodiment 2-1C described above, or it may be applied independently.

[0243] For each device category, the above embodiment 3-1 (options 3-1-1 / 3-1-2) may be applied.

[0244] For a common SIB1 for multiple (e.g., all) device categories, the SIB1-PDCCH for those multiple device categories may be monitored using common monitoring opportunities / time resources / frequency resources.

[0245] Furthermore, SIB1-PDCCH for these multiple device categories may use a common RNTI / format / payload size.

[0246] The above embodiment 3-1 (option 3-1-2) may be applied to the monitoring opportunities / time resources / frequency resources related to SIB1-PDCCH for the multiple device categories.

[0247] For example, common monitoring opportunities / time resources / frequency resources may be defined / configured / instructed for SIB1-PDCCH for the multiple device categories.

[0248] For PDCCH of a common SIB1 for different device categories, the RNTI / format / payload size may be defined in the same manner as in Embodiment 3-1 (Option 3-1-1) described above.

[0249] For example, a common RNTI / format / payload size may be defined for a common SIB1 PDCCH for different device categories.

[0250] Figure 10 shows an example of SIB1 according to Embodiment 3-2. In the example shown in Figure 10, a common SIB1 and four individual SIB1s (simply referred to as SIBs) are transmitted. In the example shown in Figure 10, the common SIB1 is monitored by UEs of all device categories (it contains information for all device categories). Also in the example shown in Figure 10, individual SIB1s for each device category are monitored in separate monitoring opportunities / time resources / frequency resources. In the example shown in Figure 10, the SIB1 for device category a and the SIB1 for device category b are monitored by the UEs of their respective categories.

[0251] Figure 11 shows another example of SIB1 according to Embodiment 3-2. In the example shown in Figure 11, a common SIB1 and four individual SIB1s (simply referred to as SIBs) are transmitted. In the example shown in Figure 11, the common SIB1 is monitored by UEs of all device categories (it contains information for all device categories). In the example shown in Figure 11, SIB1s for each device category are monitored using common monitoring opportunities / time resources / frequency resources. In the example shown in Figure 11, the UE of device category a monitors SIB1 using an RNTI for device category a (SI-RNTI-a), and the UE of device category b monitors SIB1 using an RNTI for device category b (SI-RNTI-b).

[0252] According to Embodiment 3-2, even when a common SIB / unique SIB is transmitted, the SIB resource can be appropriately identified.

[0253] According to the third embodiment described above, the resources to which the SIB is transmitted can be appropriately identified.

[0254] <Variations> In this disclosure, common / different embodiments / options may be applied to the operation during initial connection and the operation during reconnection.

[0255] For example, in the case of an initial connection, the operation / implementation / options that utilize predefined resources / CORESET / search space may be applied, and in the case of a reconnection, the operation / implementation / options that utilize configured / instructed resources / CORESET / search space may be applied.

[0256] <Supplement> <<Notification of Information to UE>> In the embodiments described above, notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE (in other words, reception of any information from the BS at the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0257] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

[0258] If the above notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble the Cyclic Redundancy Check (CRC) bits assigned to the DCI, or the format of the DCI.

[0259] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0260] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (in other words, transmission / reporting of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0261] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0262] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0263] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0264] <<Regarding the Application of Each Embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set. - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter. - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS. - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported. - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0265] The above-mentioned specific UE capabilities may include at least one of the following: • Supporting the above-mentioned specific processing / operation / control / assumption / information; • Supporting monitoring frequencies / first carrier / second carrier / third carrier (and related operations); • Supporting common MIB / common SIB / specific MIB / specific SIB.

[0266] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0267] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

[0268] If the above conditions are not met, UE / BS may follow the behavior specified in existing 3GPP releases.

[0269] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: • The information is set by one or more higher-layer parameters / RRC IEs. • The information is determined by one or more relevant higher-layer parameters / RRC IEs. • The information is indicated by MAC CE / DCI. • The information is based on one or more UE capabilities. • The information is described / defined in the specification. • The information is based on conditions described / defined in the specification. • The information is determined by a combination of several of the above. For example, the information is determined by the setting / indication of higher-layer parameters / MAC CE / DCIs and reported by UE capabilities.

[0270] The above multiple embodiments / options / choices may be combined into a single embodiment / option / choice.

[0271] (Note) The following inventions are added with respect to one embodiment of the present disclosure. [Note 1] A terminal having a receiving unit that receives at least one of a first system information block (SIB) common to a category of multiple terminals and a second SIB specific to the category of its own terminal, and a control unit that controls an initial access operation based on at least one of the first SIB and the second SIB. [Note 2] The terminal according to Note 1, wherein the first SIB is transmitted using common resources. [Note 3] The terminal according to Note 1 or Note 2, wherein the second SIB is transmitted using separate resources for each category of terminal. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the second SIB is transmitted using common resources and different Radio Network Temporary Identifiers (RNTIs).

[0272] (Wireless Communication System) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any of the wireless communication methods according to the above embodiments of this disclosure, or a combination thereof.

[0273] Figure 12 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0274] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0275] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0276] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0277] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0278] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

[0279] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

[0280] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

[0281] Furthermore, the user terminal 20 may communicate in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0282] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0283] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0284] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0285] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0286] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0287] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0288] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, which is shared by each user terminal 20.

[0289] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0290] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0291] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0292] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0293] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0294] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0295] PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgment information (for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0296] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[0297] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, the DL-RS may include a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc.

[0298] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0299] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0300] (Base Station) Figure 13 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0301] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0302] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0303] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 120, transmitting / receiving antenna 130, and transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of wireless resources, etc.

[0304] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0305] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0306] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0307] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0308] The transmitting / receiving unit 120 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0309] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), and the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), to generate a bit sequence to be transmitted.

[0310] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0311] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0312] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0313] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0314] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0315] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes that provide NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0316] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0317] The base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU may implement higher-level physical layer functions (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0318] In this disclosure, base station 10 may include a single device that implements all the functions of RU, DU, and CU, or it may include multiple devices that each implement some of the functions of RU, DU, and CU and are connected to each other. In this disclosure, base station 10 may be interpreted as RU / DU / CU.

[0319] The transmitting / receiving unit 120 may transmit at least one of a first system information block (SIB) common to multiple terminal categories, and a second SIB specific to its own terminal category. The control unit 110 may use at least one of the first SIB and the second SIB to instruct the control of the initial access operation (second embodiment).

[0320] (User Terminal) Figure 14 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0321] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0322] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0323] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0324] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0325] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0326] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0327] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0328] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0329] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0330] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0331] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0332] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

[0333] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0334] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0335] The transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0336] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may be, for example, Non Zero Power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0337] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0338] The transmitting / receiving unit 220 may receive at least one of a first system information block (SIB) common to a category of multiple terminals, and a second SIB specific to its own terminal's category. The control unit 210 may control the initial access operation based on at least one of the first SIB and the second SIB (second embodiment).

[0339] The first SIB may be transmitted using a common resource (second embodiment).

[0340] The second SIB may be transmitted using separate resources for each category of terminal (second / third embodiment).

[0341] The second SIB may be transmitted using common resources and different Radio Network Temporary Identifiers (RNTIs) (Second / Third Embodiments).

[0342] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0343] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0344] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 15 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0345] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0346] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, the processing may be performed by one processor, or it may be performed by two or more processors simultaneously, sequentially, or by other means. Note that the processor 1001 may be implemented using one or more chips.

[0347] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003.

[0348] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0349] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0350] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0351] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

[0352] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated transmitting unit 120a (220a) and receiving unit 120b (220b).

[0353] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0355] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0356] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0357] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0358] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0359] Here, the neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0360] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0361] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using minislots may be called a PDSCH (PUSCH) mapping type B.

[0362] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0363] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0364] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0365] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0366] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0367] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0368] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0369] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0370] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0371] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0372] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0373] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

[0374] A BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within a single carrier for a UE.

[0375] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0376] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0377] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0378] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0379] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0380] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0381] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0382] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0383] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0384] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0385] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0386] The determination may be made by a value represented by one bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0387] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0388] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0389] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0390] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0391] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0392] The above group may include, for example, at least one of the following: a spatial relationship group, a code division multiplexing (CDM) group, a reference signal (RS) group, a control resource set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, or a panel group.

[0393] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0394] Furthermore, in this disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc., may be interpreted interchangeably.

[0395] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

[0396] In this disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset may be interpreted interchangeably.

[0397] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0398] In this disclosure, terms such as “Base Station (BS),” “wireless base station,” “fixed station,” “NodeB,” “eNB (eNodeB),” “gNB (gNodeB),” “access point,” “Transmission Point (TP),” “Reception Point (RP),” “Transmission / Reception Point (TRP),” “panel,” “cell,” “sector,” “cell group,” “carrier,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0399] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0400] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0402] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0403] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0404] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0405] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0406] Figure 16 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0407] The drive unit 41 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

[0408] The electronic control unit 49 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0409] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0410] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of information / services (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

[0411] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0412] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver assistance functions or autonomous driving functions.

[0413] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[0414] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

[0415] The communication module 60 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 50-58 input to the electronic control unit 49, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include the information based on the above input.

[0416] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[0417] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

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

[0419] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0420] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0421] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0422] Each aspect / embodiment described in this disclosure is Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0423] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0424] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0425] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0426] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0427] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0428] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0429] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased as "An apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

[0430] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0431] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0432] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0433] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0434] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0435] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0436] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0437] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0438] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" may be interchangeable. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0439] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0440] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

Claims

1. A terminal having a receiving unit that receives at least one of a first system information block (SIB) common to a category of multiple terminals and a second SIB specific to the category of its own terminal, and a control unit that controls an initial access operation based on at least one of the first SIB and the second SIB.

2. The terminal according to claim 1, wherein the first SIB is transmitted using a common resource.

3. The terminal according to claim 1, wherein the second SIB is transmitted using separate resources for each category of terminal.

4. The terminal according to claim 1, wherein the second SIB is transmitted using common resources and different Radio Network Temporary Identifiers (RNTIs).

5. A wireless communication method for a terminal, comprising the steps of: receiving at least one of a first system information block (SIB) common to a category of multiple terminals, and a second SIB specific to the category of the terminal itself; and controlling an initial access operation based on at least one of the first SIB and the second SIB.

6. A base station having: a transmitting unit that transmits at least one of a first system information block (SIB) common to a category of multiple terminals and a second SIB specific to the category of its own terminal; and a control unit that instructs the control of the initial access operation using at least one of the first SIB and the second SIB.

Images